GNOME Bugzilla – Bug 145877
Gnome Window Switcher crashes on screen1 when selecting 'Properties' in dual head config.
Last modified: 2020-11-06 20:26:24 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-panel Severity: normal Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: Gnome Window Switcher crashes on screen1 when selecting 'Properties' in dual head config. Bugzilla-Product: gnome-panel Bugzilla-Component: Workspace Switcher Applet Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: In Gnome, when using a dual head config (auto generated xorg.conf from gnome display settings), the workspace switcher applet produces an unexpected crash on both screen0 and screen1 if you choose 'Properties' by right clicking on the workspace switcher in the menubar. Steps to reproduce the crash: 1. Config for dual head in gnome display settings, use 'individual destops' 2. Place a workspace switcher on both pannels (screen0 and screen1) if they are not already present. 3. Right click on either workspace switcher and choose 'Properties' 4. Crash occurs when trying to change any settings in properties dialog box. Expected Results: While using FC2 Test3, I noticed this same behavior, however, after a few crashes it eventually let me configure them individually. How often does this happen? Each time 'Properties' is selected on the workspace switcher applet while using a dual head config in Gnome. Additional Information: Dell Inspiron 600m Laptop Dual Head ATI Radeon M9 64meg (OEM) Primary Monitor - 1400x1050 (OEM) 2nd Monitor - NEC MultiSync LCD 1830 FC2 Final - Fresh 'Everything' install Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -150249344 (LWP 3375)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0085a402 in ?? ()
+ Trace 47529
Thread 1 (Thread -150249344 (LWP 3375))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 16:44 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was sshirley@uark.edu. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
If this is still happening, could you install the gnome-panel debuginfo rpm (available at http://download.fedora.redhat.com/pub/fedora/linux/core/updates/2/i386/debug/) and paste the new stack trace here? Thanks
In panel_profile_remove_from_list(), a crash is possible if id == NULL. But I'm not sure this should be possible... So I'm wondering if I should add: g_assert (id != NULL); or g_return_if_fail (id != NULL); or if (id != NULL) return; Mark: what do you think?
*** Bug 301285 has been marked as a duplicate of this bug. ***
I also get this same error. Only debug information I get is the cause is a segmentation fault. I can get the properties of the panel itself, but not the properties of the launchers on my panel. I do have ONE launcher that does allow me to view the properties, but noting of specific note is different about the launcher. I created both launchers, and they both launch "su -c [some command] %u" I just realized am using The GNOME Panel 2.2.2.1. I will try and see if there is an update.
*** Bug 450280 has been marked as a duplicate of this bug. ***
*** Bug 453243 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.