Bug 25322 - net_applet segfaulted during compiz restart
Summary: net_applet segfaulted during compiz restart
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-17 23:33 CEST by Herbert Poetzl
Modified: 2021-09-07 14:09 CEST (History)
3 users (show)

See Also:
Source RPM: drakx-net-2.42-1.mga7, gtk+3.0
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Herbert Poetzl 2019-08-17 23:33:22 CEST 
The "net_applet" program crashed. Drakbug-18.21 caught it.

restarted compiz

SEGV
Glibc's trace:
4: /lib64/libperl.so.5.28(Perl_sighandler+0x226) [0x7f7084ea08a6]
5: /lib64/libc.so.6(+0x3caf0) [0x7f7084c3baf0]
6: /lib64/libgdk-3.so.0(+0x5f8aa) [0x7f70828218aa]
7: /lib64/libgdk-3.so.0(+0x69938) [0x7f708282b938]
8: /lib64/libgdk-3.so.0(+0x694a5) [0x7f708282b4a5]
9: /lib64/libgdk-3.so.0(gdk_display_get_event+0x40) [0x7f70827f68a0]
10: /lib64/libgdk-3.so.0(+0x690c2) [0x7f708282b0c2]
11: /lib/../lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135) [0x7f70834b2665]
12: /lib/../lib64/libglib-2.0.so.0(+0x4d9e8) [0x7f70834b29e8]
13: /lib/../lib64/libglib-2.0.so.0(g_main_loop_run+0xb2) [0x7f70834b2cd2]
14: /lib64/libgtk-3.so.0(gtk_main+0x75) [0x7f7082aeafc5]
15: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f708365c77e]
16: /lib64/libffi.so.6(ffi_call+0x22f) [0x7f708365c14f]
17: /usr/lib64/perl5/vendor_perl/auto/Glib/Object/Introspection/Introspection.so(+0x10400) [0x7f70833ea400]
18: /usr/lib64/perl5/vendor_perl/auto/Glib/Object/Introspection/Introspection.so(+0x10ddd) [0x7f70833eaddd]
19: /lib64/libperl.so.5.28(Perl_pp_entersub+0x1f1) [0x7f7084ebbb21]

Perl's trace:
drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41
drakbug::__ANON__() called from /usr/share/perl5/vendor_perl/Gtk3.pm:578
(eval)() called from /usr/share/perl5/vendor_perl/Gtk3.pm:578
Gtk3::main() called from /usr/share/perl5/vendor_perl/Gtk3.pm:523
Gtk3::__ANON__() called from /usr/bin/net_applet:330

Theme name: TraditionalOk
Kernel version = 5.1.20-desktop-2.mga7
Distribution=Mageia release 7 (Official) for x86_64
CPU=Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Comment 1 Nicolas Nicolas 2019-08-18 12:35:41 CEST 
Hello,

Does this issue occurs when doing something particular ( restarted compiz is done before the bug or after the bug) ?

what is the used DE ?

CC: (none) => joe_c_moi

Nicolas Nicolas 2019-08-18 12:35:54 CEST

CC: joe_c_moi => (none)

Comment 2 Herbert Poetzl 2019-08-20 04:33:35 CEST 
The issue occurred during the compiz restart.

DE is Mate/Xfce session/panels, cairo dock and compiz with emerald.

Best,
Herbert

CC: (none) => herbert

Marja Van Waes 2019-08-24 18:43:37 CEST

CC: (none) => marja11, thierry.vignaud
Source RPM: drakx-net-applet-2.42-1.mga7 => drakx-net-2.42-1.mga7, gtk+3.0
Assignee: bugsquad => mageiatools
Summary: net_applet segfaulted => net_applet segfaulted during compiz restart

Comment 3 Aurelien Oudelet 2021-07-06 13:15:08 CEST 
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 4 Marja Van Waes 2021-09-07 14:09:27 CEST 
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.