Richard1098 Posted June 3, 2008 Report Share Posted June 3, 2008 (edited) Soon after starting Gnome, the panel crashes. This is the error message: Distribution: Mandriva Linux release 2008.1 (Official) for i586 Gnome Release: 2.22.0 2008-03-26 (Mandriva) BugBuddy Version: 2.22.0 System: Linux 2.6.24.4-desktop-3mnb #1 SMP Mon May 5 18:09:09 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: Neu Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- SIOCETHTOOL: Operation not supported SIOCETHTOOL: Operation not supported SIOCETHTOOL: Operation not supported (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x8181b98' (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e800' (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e840' (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e880' (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e8c0' (gnome-panel:7119): GLib-GObject-WARNING **: gsignal.c:1669: signal `set-current' is invalid for instance `0x834e900' -------------------------------------------------- Seems to have been caused by a recent update of one of the following: gnome-themes-extras timezone timezone-java Edited June 3, 2008 by Richard1098 Quote Link to comment Share on other sites More sharing options...
yossarian Posted June 3, 2008 Report Share Posted June 3, 2008 I have exactly the same problem. I also updated my system, with the same updates, before the desktop crashing. If anyone knows what to do - many thanks. Quote Link to comment Share on other sites More sharing options...
Guest shartrec Posted June 3, 2008 Report Share Posted June 3, 2008 I have exactly the same problem. Same segmentation fault. Now I have no panels and can't restart them I did receive and install an update sometime earlier today, but I can't recall what it was for. Quote Link to comment Share on other sites More sharing options...
Richard1098 Posted June 3, 2008 Author Report Share Posted June 3, 2008 (edited) I've simply logged into KDE and installed the original rpms from the CD (copied to a new folder) using: rpm --Uvh --oldpackage * You will need to cd /home/ xxxx to that folder first. Edited June 3, 2008 by Richard1098 Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 3, 2008 Report Share Posted June 3, 2008 See comment 3 on bug 40525, relating to the timezone update... Quote Link to comment Share on other sites More sharing options...
yossarian Posted June 3, 2008 Report Share Posted June 3, 2008 Sorry for being thick, but I didn't understand from the bug report: Is there an immediate way for us to overcome this problem? I didn't quite understand what I should do with the solution suggested in comment #7. Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 3, 2008 Report Share Posted June 3, 2008 Download the packages shown to their own folder, then use the rpm command in that folder to overwrite the newer versions. Richard has done something similar using his CD packages (see above). Quote Link to comment Share on other sites More sharing options...
arctic Posted June 3, 2008 Report Share Posted June 3, 2008 I've simply logged into KDE and installed the original rpms from the CD (copied to a new folder) using: rpm --Uvh --oldpackage * You will need to cd /home/ xxxx to that folder first. Just a note for those who don't know this already: In case the system refuses to install the older package, use rpm -Uvh --force <packagename> Quote Link to comment Share on other sites More sharing options...
Guest pike Posted June 3, 2008 Report Share Posted June 3, 2008 This terminal command line I found in the comments from the Bug page worked for me: "urpmi --replacepkgs --allow-force timezone-2008b" Quote Link to comment Share on other sites More sharing options...
yossarian Posted June 3, 2008 Report Share Posted June 3, 2008 This terminal command line I found in the comments from the Bug page worked for me: "urpmi --replacepkgs --allow-force timezone-2008b" Worked for me too. -sigh- Of course, it is now important not to install the automatic update until this bug is fixed. Quote Link to comment Share on other sites More sharing options...
yossarian Posted June 3, 2008 Report Share Posted June 3, 2008 This terminal command line I found in the comments from the Bug page worked for me: "urpmi --replacepkgs --allow-force timezone-2008b" And welcome aboard! :) Quote Link to comment Share on other sites More sharing options...
adamw Posted June 4, 2008 Report Share Posted June 4, 2008 An update to fix this regression should hit very soon (it's already in /main/testing). Sorry for the screw up :( Quote Link to comment Share on other sites More sharing options...
Guest rivenought Posted June 4, 2008 Report Share Posted June 4, 2008 Does anyone want to post an "all-clear" message when it is safe to run the updates? That would be helpful. Quote Link to comment Share on other sites More sharing options...
adamw Posted June 4, 2008 Report Share Posted June 4, 2008 It already is, if your mirror is synced - the broken update has been removed from the repositories. Just make sure there's no 'timezone' package in the update list before going ahead. Quote Link to comment Share on other sites More sharing options...
Guest rivenought Posted June 4, 2008 Report Share Posted June 4, 2008 Thanks, Adam. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.