Description of problem: When closing an MCC function window to go back to the MCC main window, MCC is closed instead. Version-Release number of selected component (if applicable): Beta 3 release, after a large (300+ packages) update How reproducible: Unknown. I have not been able to activate the Cauldron Core Release mirror on any of my test computers since getting the large update on one Beta 3 install, so have been unable to repeat the 300+ updates. Steps to Reproduce: 1. Install Mageia 5 Beta 3 from the i585 Classical DVD 2. Get a large update of 300+ packages 3. Hardware where the problem was seen: Dell Dimension E310 desktop, with a Pentium 4 processor, maxed out at 2GB of RAM. Stock audio and video. Wireless Internet connection, using a card with a Broadcom 4318 chip, using the B43 driver. Reproducible: Steps to Reproduce:
evident in Mageia-5-rc-i586-DVD. Wed Feb 25 20:41:46 CET 2015 fresh install of KDE, before and after updates( 67 ) applied. hardware: Intel core i5 / 8Gb ram, Asus mobo:P8B75-M lx onboard Intel Graphics - 810 or later
CC: (none) => westelSummary: MCC windows not closing properly => M5B3 MCC windows not closing properly
Please, could you try to update drakconf to 12.56-1 . Could you reproduce this issue with this last version ?
CC: (none) => lmenut
please advise which online media I need to enable to update drakconf. sorry for my ignorance.
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
Source RPM: Mageia Control Center => drakconf
drakconf-12.56-1 is in /core/release
The affected install was using drakconf 12.54-1 until about an hour ago. After successfully updating media for the first time in several attempts, It was updated to drakconf 12.56-1 as well as all other updates - kernel, glibc, and some 200 others. Orphaned packages were also removed. The behavior remains. Originally, with drakconf 12.54-1, I saw no error messages if I ran MCC from Konsole. However, I now see the following when MCC closes unexpectedly: "/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 831. "/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 831. "/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 831. "/usr/sbin/drakguard" is not executable [Parental Controls] at /usr/libexec/drakconf line 831. Something tells me that may narrow things down a bit...
Not at all. Those are not errors at all.
Rats. That's what I get for trying to be "clever." Happens every time... I finally was able to activate the core release medium and get all updates(439 packages!) on my second Beta 3 install, on different hardware. This is a homebrew desktop, Asus-made Fujitsu D1711 motherboard (Asus # K8V-MX/s), Sempron 3100+ processor, maxed out at 2GB RAM, GeForce 6200OC AGP video card, wired Internet connection. Using server kernel and nvidia 304 video driver, as installed by the installer DVD. After the updates, including drakconf 12.56-1, this install also shows the bug. I have noticed that MCC doesn't crash ALL the time, but does the vast majority of the time. Once or twice when trying different things, I saw the window that was supposed to appear do so briefly (a second or so at the most) before MCC crashed. I have not observed any obvious circumstances that I can use to predict when it will and will not crash.
after update to drakconf 12.65- and reboot, launch MCC, launch "update your system"window, no packages to update, closed "update your system"window- MCC closes completely. please advise if more info required
Indeed I can reproduce this too. I used drakconf to launch system-config-printer, and then when I exit s-c-p, drakconf exits too. This is a recent regression (within the last 6 weeks). I won't pretend to know what caused it.
Keywords: NEEDINFO => (none)CC: (none) => luigiwalser
I see it when closing most of the various tools, whether it is done with the window "close" button (the "X" in the corner), a normal exit button that says "Close" or "Done," or with one that says "Cancel."
is this helpful? The "drakconf" program has segfaulted with the following error: SEGV Glibc's trace: 4: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_sighandler+0x1cd) [0xb75dda0d] 5: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_csighandler+0x7e) [0xb75d94de] 6: linux-gate.so.1(__kernel_sigreturn+0) [0xb7714ba8] 7: [0x941d5d0] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/libexec/drakconf:1106 (eval)() called from /usr/libexec/drakconf:1106 Used theme: BlueMenta. i just updated system and closed the update window desktop is Mate.
Just updated my Virtualbox VM at home to current Cauldron as of Friday. I ran the hardware detection tool and closed it and drakconf crashed, but I didn't get a trace from it. Then I tried it again and drakconf didn't crash. Same thing with a few other tools in the Hardware section. Then I clicked configure printer (which I used to reproduce this at work on Friday on a physical machine) and got the crash. drakbug actually caught it and gave me this trace: SEGV Glibc's trace: 4: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_sighandler+0x1cd) [0xb75d2a0d] 5: /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so(Perl_csighandler+0x7e) [0xb75ce4de] 6: linux-gate.so.1(__kernel_sigreturn+0) [0xb7709b98] 7: [0x9538916] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/libexec/drakconf:1106 (eval)() called from /usr/libexec/drakconf:1106 Theme name: oxygen-gtk Kernel version = 3.19.0-desktop-4.mga5 Distribution=Mageia release 5 (Cauldron) for i586 CPU=Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
I ran drakconf again and attached gdb to the child drakconf process. I clicked the edit-urpm-media program in Software Management and clicked to close it and got the crash. gdb gave this backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00000001 in ?? () (gdb) bt #0 0x00000001 in ?? () #1 0xb588e7e8 in gdk_threads_dispatch_free () from /lib/libgdk-x11-2.0.so.0 #2 0x0a51c818 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0xb6dd8b4e in uw_frame_state_for () from /lib/libgcc_s.so.1 (gdb) bt #0 0xb6dd8b4e in uw_frame_state_for () from /lib/libgcc_s.so.1 #1 0xb6dd9a00 in _Unwind_Backtrace () from /lib/libgcc_s.so.1 #2 0xb739a883 in backtrace () from /lib/i686/libc.so.6 #3 0xb7541764 in XS_c__stuff_C_backtrace () from /usr/lib/libDrakX/auto/c/stuff/stuff.so #4 0xb760539c in Perl_pp_entersub () from /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so #5 0xb75fde57 in Perl_runops_standard () from /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so #6 0xb75893f5 in Perl_call_sv () from /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so #7 0xb75eda0d in Perl_sighandler () from /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so #8 0xb75e94de in Perl_csighandler () from /usr/lib/perl5/5.20.1/i386-linux-thread-multi/CORE/libperl.so #9 <signal handler called> #10 0x00000001 in ?? () #11 0xb588e7e8 in gdk_threads_dispatch_free () from /lib/libgdk-x11-2.0.so.0 #12 0x0a51c818 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) cont Continuing. [Thread 0xb1f2ab40 (LWP 14866) exited] [Thread 0xb13bbb40 (LWP 14869) exited] [Thread 0xb0a8cb40 (LWP 14870) exited] [Thread 0xaf732b40 (LWP 14875) exited] [Thread 0xade86b40 (LWP 14879) exited] [Thread 0xad685b40 (LWP 14880) exited] [Thread 0xace84b40 (LWP 14881) exited] [Thread 0xac683b40 (LWP 14882) exited] [Thread 0xaa653b40 (LWP 14896) exited] [Thread 0xa9e52b40 (LWP 14897) exited] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists.
It could be due to a regression with gtk+2 2.24.26. I reverted a commit from 2.24.26 in gtk+2.0-2.24.26-2.mga5. Please, could you try gtk+2.0 packages 2.24.26-2 from core/updates_testing: gtk+2.0-2.24.26-2 lib(64)gtk+2.0_0-2.24.26-2 lib(64)gtk+-x11-2.0_0-2.24.26-2 lib(64)gail18-2.24.26-2 I was able to frequently reproduce this bug on my old netbook (i586) today, and I can't reproduce the issue after reverting commit ee95f3d7259c0859ce41189b781b4339b4cd64aa "Make gdk_event_apply_filters safe against changes in filter list" .
CC: (none) => wilcal.int
Your package list got cut off it looks like. gtk+2.0-2.24.26-2.mga5 libgail18-2.24.26-2.mga5 libgail-devel-2.24.26-2.mga5 libgtk+2.0_0-2.24.26-2.mga5 libgtk+2.0-devel-2.24.26-2.mga5 libgtk-gir2.0-2.24.26-2.mga5 libgtk+-x11-2.0_0-2.24.26-2.mga5 Of course the -devel packages aren't central to the issue. I also don't have libgail18 installed at all. One thing that's a bit frustrating before the update is that it doesn't crash every single time, so it's not 100% reliably reproducible. After the update, I have been trying quite a bit and have been unable to trigger a crash. It looks like Luc got this one figured out.
I just replaced gtk+2.0-2.24.26, libgtk+2.0_0-2.24.26, and libgtk+-x11-2.0_0-2.24.26 on one of the affected machines. The other packages weren't installed at all. The problem looks like it has disappeared. Getting late here, will do more testing tomorrow morning and will try the other affected machine. But for now, I agree with David Walser - it looks like Luc has it.
Thanks Luc for the findings. @Olav: latest gtk+2.0 has a nasty regression that makes mcc to segfault.
Priority: Normal => release_blockerCC: (none) => olavSummary: M5B3 MCC windows not closing properly => M5B3 MCC windows not closing properly (gtk+2.0-2.24.26 regression)Source RPM: drakconf => gtk+2.0
Confirmed on my second affected 32-bit machine. Replacing the same gtk+2.0 packages listed in Comment 16 makes the problem disappear.
A quick look at my updated test client Vbox installs this morning: Mageia-5-rc-i586-DVD.iso Wed Feb 25 20:41:46 CET 2015 13e98ac12db9f3cd7562f7bda36ada53 Exhibits the M5B3(RC) MCC windows not closing properly problem. Mageia-5-rc-x86_64-DVD.iso Wed Feb 25 21:32:45 CET 2015 0e3ae4c152e16cd366b2110a0e4b2353 Seems to be ok. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64 M5 Cauldron i586 Long term Cauldron rolling updates install Exhibits the M5B3(RC) MCC windows not closing properly problem occasionally. Test platform: Intel, P4 530J 3.0 GHz, 800MHz FSB, 1MB L2, LGA 775 GigaByte GA-81915G Pro F4 i915G LGA 775 MoBo Marvel Yukon 88E8001 Gigabit LAN Intel High Def Audio, Azalia (C-Media 9880) (snd-hda-intel) Intel Graphics Media Accelerator 900 (Intel 82915G) Kingston 4GB (2 x 2GB) DDR400 PC-3200 250GB Seagate Kingwin KF-91-BK SATA Mobile Rack Kingwin KF-91-T-BK SATA Mobile Rack Tray Sony CD/DVD-RW DWQ120AB2
Will can you test packages in testing for gtk2 provided by Luc in testing?
CC: (none) => ennael1
Guys can you test with the packages in 5 core updates testing please and report back here. If the fix is Ok we can include it in next ISOs. See comment 14 Thanks
CC: (none) => eeeemail
In VirtualBox, M4, KDE, 32-bit Packages in update_testing repo: gtk+2.0 installed libgtk+2.0_0 installed libgtk+-x11-2.0_0 installed libgtk+2.0-devel not installed libgtk-gir2.0 not installed libgail18 not installed libgail18-devel not installed Package(s) installed and under test: gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 default install of gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 packages [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-1.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+2.0_0 Package libgtk+2.0_0-2.24.26-1.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+-x11-2.0_0 Package libgtk+-x11-2.0_0-2.24.26-1.mga5.i586 is already installed Exhibits the M5B3(RC) MCC windows not closing properly problem. install gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 from updates_testing [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-2.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+2.0_0 Package libgtk+2.0_0-2.24.26-2.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+-x11-2.0_0 Package libgtk+-x11-2.0_0-2.24.26-2.mga5.i586 is already installed Instant fix. No problems navigating through the MCC. Log out then Log in again problem still fixed. Fix survived a reboot. Nicely done. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
In VirtualBox, M4, KDE, 64-bit Packages in update_testing repo: gtk+2.0 installed lib64gtk+2.0_0 installed lib64gtk+-x11-2.0_0 installed lib64gtk+2.0-devel not installed lib64gtk-gir2.0 not installed lib64gail18 not installed lib64gail18-devel not installed Package(s) installed and under test: gtk+2.0 lib64gtk+2.0_0 lib64gtk+-x11-2.0_0 default install of gtk+2.0 lib64gtk+2.0_0 lib64gtk+-x11-2.0_0 packages [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-1.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi lib64gtk+2.0_0 Package lib64gtk+2.0_0-2.24.26-1.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi lib64gtk+-x11-2.0_0 Package lib64gtk+-x11-2.0_0-2.24.26-1.mga5.x86_64 is already installed Occasional/rarely exhibits the M5B3(RC) MCC windows not closing properly problem. install gtk+2.0 lib64gtk+2.0_0 lib64gtk+-x11-2.0_0 from updates_testing [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-2.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi lib64gtk+2.0_0 Package lib64gtk+2.0_0-2.24.26-2.mga5.x86_64 is already installed [root@localhost wilcal]# urpmi lib64gtk+-x11-2.0_0 Package lib64gtk+-x11-2.0_0-2.24.26-2.mga5.x86_64 is already installed No problems encountered navigating through the MCC. Log out then Log in again problem still fixed. Fix survived a reboot. Nicely done. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
On real hardware, M4, KDE, 32-bit Packages in update_testing repo: gtk+2.0 installed libgtk+2.0_0 installed libgtk+-x11-2.0_0 installed libgtk+2.0-devel not installed libgtk-gir2.0 not installed libgail18 not installed libgail18-devel not installed Package(s) installed and under test: gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 default install of gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 packages [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-1.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+2.0_0 Package libgtk+2.0_0-2.24.26-1.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+-x11-2.0_0 Package libgtk+-x11-2.0_0-2.24.26-1.mga5.i586 is already installed Exhibits the M5B3(RC) MCC windows not closing properly problem. install gtk+2.0 libgtk+2.0_0 libgtk+-x11-2.0_0 from updates_testing [root@localhost wilcal]# urpmi gtk+2.0 Package gtk+2.0-2.24.26-2.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+2.0_0 Package libgtk+2.0_0-2.24.26-2.mga5.i586 is already installed [root@localhost wilcal]# urpmi libgtk+-x11-2.0_0 Package libgtk+-x11-2.0_0-2.24.26-2.mga5.i586 is already installed I had to log out and log back in but the problem is fixed. No problems navigating through the MCC. Log out then Log in again problem still fixed. Fix survived a reboot. Intel, P4 530J 3.0 GHz, 800MHz FSB, 1MB L2, LGA 775 GigaByte GA-81915G Pro F4 i915G LGA 775 MoBo Marvel Yukon 88E8001 Gigabit LAN Intel High Def Audio, Azalia (C-Media 9880) (snd-hda-intel) Intel Graphics Media Accelerator 900 (Intel 82915G) Kingston 4GB (2 x 2GB) DDR400 PC-3200 250GB Seagate Kingwin KF-91-BK SATA Mobile Rack Kingwin KF-91-T-BK SATA Mobile Rack Tray Sony CD/DVD-RW DWQ120AB2
Looks good to go from here. Luc Menut is not crowned King of the GTK+2.0
Packages moved to release
Status: NEW => RESOLVEDCC: (none) => pterjanResolution: (none) => FIXED
s/not/now/
Thanks all for fixing this. Noticed that there's a newer 2.x gtk+: * Bug fixes: 696505 Segfault on Windows x64: gtkstatusicon.c tries to put 64-bit... 745052 Icon theme code assumes directories with mtime 0 don't exist Don't leak pixel data in some error paths 745536 gdk: Fix GdkWindowFilter internal refcounting but seems we cannot rely on 2.x being stable. :-( Something for my learning: I thought MCC used GTK+3, not 2? I broke the installer due to accidentally dropping a patch from GTK+3. This is now GTK+2. Using both seems dangerous and confusing?
mcc is the latest tool still using gtk+2 I'dn't push my gtk3 branch as I'd completed the migration to Cairo for rendering the animation while starting a tool
Can we remove the patch [1] added to fix this bug and update to latest gtk+2.0 in Cauldron? The patch doesn't apply cleanly anymore. [1] http://svnweb.mageia.org/packages?view=revision&revision=817290
CC: (none) => jani.valimaa
The following two commits I think fix that bug. So think safe to remove and move to latest gtk+2.0 https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=5efefdb6550b3f00d5ca159c2ff74326bfd0e94b https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=22eb70adab72a5c14f063ea15f8195087ff1dcd8
Submitted that. It should fix the build (perl changes).