Bug 18906

Summary: drakrpm-update segfaulted (GTK+3.0 bug probably)
Product: Mageia Reporter: Fred Thuillier <fred.thuillier>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, thierry.vignaud
Version: 5   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: gtk+3.0, rpmdrake-6.20-1.mga5 CVE:
Status comment:
Attachments: lspcidrake -v

Description Fred Thuillier 2016-07-09 14:05:22 CEST
Created attachment 8144 [details]
lspcidrake -v

The "drakrpm-update" program crashed. Drakbug-16.104 caught it.

Le programme « drakrpm-update » a planté (SEGV) avec l'erreur suivante :

  SEGV
  Glibc's trace:
  4: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_sighandler+0x1cd) [0xb7649cad]
  5: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_csighandler+0x7e) [0xb764577e]
  6: linux-gate.so.1(__kernel_sigreturn+0) [0xb7780bec]
  7: /lib/libgtk-3.so.0(+0x27b549) [0xb4ca2549]
  8: /lib/libgtk-3.so.0(+0x282b23) [0xb4ca9b23]
  9: /lib/libgtk-3.so.0(+0x282bd1) [0xb4ca9bd1]
  10: /lib/libgtk-3.so.0(+0x28b40a) [0xb4cb240a]
  11: /lib/libgtk-3.so.0(+0x2a67dc) [0xb4ccd7dc]
  12: /lib/libgtk-3.so.0(+0x2a68b9) [0xb4ccd8b9]
  13: /lib/libglib-2.0.so.0(g_slist_foreach+0x23) [0xb5642893]
  14: /lib/libgtk-3.so.0(gtk_text_tag_table_foreach+0xa4) [0xb4ccdb64]
  15: /lib/libgtk-3.so.0(+0x2a703a) [0xb4cce03a]
  16: /lib/libgtk-3.so.0(+0x2849e5) [0xb4cab9e5]
  17: /lib/libgobject-2.0.so.0(g_object_unref+0x1d5) [0xb57161b5]
  18: /lib/libgtk-3.so.0(gtk_text_view_set_buffer+0x30c) [0xb4cd363c]
  19: /lib/libgtk-3.so.0(+0x2ae4d7) [0xb4cd54d7]
  
  Perl's trace:
  drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41
  drakbug::__ANON__() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:1179
  (eval)() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:1179
  Gtk3::TextBuffer::set_text() called from /usr/lib/libDrakX/mygtk3.pm:1423
  mygtk3::_text_insert() called from /usr/lib/libDrakX/ugtk3.pm:728
  ugtk3::gtktext_insert() called from /usr/libexec/drakrpm-update:247
  main::__ANON__() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:341
  (eval)() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:341
  Gtk3::main() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:294
  Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1521
  mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
  ugtk3::main() called from /usr/libexec/drakrpm-update:282
  main::run_treeview_dialog() called from /usr/libexec/drakrpm-update:293

Thème utilisé : oxygen-gtk

I was reading a few informations about the updates in drakrpm. So i cliked on the informations about a pkg (don't remember wich one,but I saw drakx-net and openoffice just before). 

sortie de  lspcidrake -v jointe
Comment 1 Fred Thuillier 2016-07-09 14:09:26 CEST
I tried again. The bug doesn't occurs a second time, drakrpm-update works fine, all pkg are updated. The pkg concerned was msec.
Comment 2 Marja Van Waes 2016-07-30 21:51:23 CEST
Thx for the feedback, Fred.

It might happen again for one or more other users, though, so I'll assign to the maintainer, anyway.

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Comment 3 Thierry Vignaud 2016-07-30 22:24:12 CEST
Looks like a gtk+3 bug...

CC: (none) => olav, thierry.vignaud
Assignee: thierry.vignaud => bugsquad
Source RPM: rpmdrake-6.20-1.mga5 => gtk+3.0, rpmdrake-6.20-1.mga5

Comment 4 Marja Van Waes 2016-07-30 22:32:31 CEST
(In reply to Thierry Vignaud from comment #3)
> Looks like a gtk+3 bug...

Thx :-)

(So bug 17176 is probably a gtk+3 bug, too)

Assigning to all packagers collectively, since gtk+3.0 has no registered maintainer.

Assignee: bugsquad => pkg-bugs

Comment 5 Olav Vitters 2016-09-19 10:00:27 CEST
If this is not reproducible plus the stracktrace is lacking, then there's unfortunately not much that can be done. It indeed looks like a GTK+3.0 bug.

CC: olav => (none)

Comment 6 Fred Thuillier 2016-09-19 23:43:28 CEST
So I don't know what's the procedure ? I'm not at ease with bugzilla. 

Should I close (unconfirmed, resolved ?) ? Change priority and severity ?
Comment 7 Samuel Verschelde 2016-09-20 10:28:55 CEST
(In reply to Fred Thuillier from comment #6)
> So I don't know what's the procedure ? I'm not at ease with bugzilla. 
> 
> Should I close (unconfirmed, resolved ?) ? Change priority and severity ?

We can keep it open for now. You can try to install debug packages for gtk+3.0 so that if it happens again the stacktrace is more meaningful.

Summary: drakrpm-update segfaulted => drakrpm-update segfaulted (GTK+3.0 bug probably)

Comment 8 Marja Van Waes 2018-04-24 18:24:16 CEST
Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Status: NEW => RESOLVED
Resolution: (none) => OLD