GNOME Bugzilla – Bug 480179
crash in gconf_client_remove_dir [UNMAINTAINED]
Last modified: 2011-06-13 11:15:12 UTC
Version: 2.20.0 What were you doing when the application crashed? started monodevelop after doing an update with synaptic Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 66498560 vsize: 66498560 resident: 9625600 share: 7983104 rss: 9625600 rss_rlim: 4294967295 CPU usage: start_time: 1190721262 rtime: 21 utime: 18 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b616c0 (LWP 4048)] (no debugging symbols found) 0xb75ffbf1 in waitpid () from /lib/libpthread.so.0
+ Trace 165333
Thread 1 (Thread 0xb6b616c0 (LWP 4048))
----------- .xsession-errors --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "panmanphil" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/cyber2:/tmp/.ICE-unix/3963 Window manager warning: 0 stored in GConf key /apps/metacity/general/num_workspaces is not a reasonable number of workspaces, current maximum is 36 Window manager warning: 0 stored in GConf key /desktop/gnome/peripherals/mouse/cursor_size is not a reasonable cursor_size; must be in the range 1..128 Usage - gnome-control-center [-h] Options: -h : hide on start Useful if you want to autostart the control-center singleton so it can get all its slow loading done No value set for `/desktop/gnome/applications/at/visual/exec' ** Message: failed to load session from /home/panmanphil/.nautilus/saved-session-O58RTT Unable to open desktop file /usr/share/applications/gaim.desktop for panel launcher: No such file or directory ** (gnome-panel:4047): WARNING **: panel-applet-frame.c:1278: failed to load applet OAFIID:GNOME_MultiLoadApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_4/prefs;background=none:;orient=up;size=x-small;locked_down=false --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 481738 has been marked as a duplicate of this bug. ***
*** Bug 482815 has been marked as a duplicate of this bug. ***
*** Bug 503500 has been marked as a duplicate of this bug. ***
*** Bug 503900 has been marked as a duplicate of this bug. ***
*** Bug 506417 has been marked as a duplicate of this bug. ***
*** Bug 512344 has been marked as a duplicate of this bug. ***
*** Bug 512480 has been marked as a duplicate of this bug. ***
*** Bug 512638 has been marked as a duplicate of this bug. ***
*** Bug 512789 has been marked as a duplicate of this bug. ***
*** Bug 515991 has been marked as a duplicate of this bug. ***
-> nautilus-actions. Better trace from bug #515991:
+ Trace 188980
This seems a crash in the nautilus-actions extension, so reassigning.
*** Bug 517604 has been marked as a duplicate of this bug. ***
*** Bug 517602 has been marked as a duplicate of this bug. ***
I think this could be the same crash as in bug #496332
*** Bug 520322 has been marked as a duplicate of this bug. ***
*** Bug 496332 has been marked as a duplicate of this bug. ***
Even better trace from dup bug #496332.
+ Trace 191300
*** Bug 520380 has been marked as a duplicate of this bug. ***
*** Bug 524063 has been marked as a duplicate of this bug. ***
*** Bug 524413 has been marked as a duplicate of this bug. ***
Confirming for the many duplicates.
*** Bug 524463 has been marked as a duplicate of this bug. ***
*** Bug 524462 has been marked as a duplicate of this bug. ***
*** Bug 524597 has been marked as a duplicate of this bug. ***
*** Bug 524803 has been marked as a duplicate of this bug. ***
*** Bug 524799 has been marked as a duplicate of this bug. ***
*** Bug 524794 has been marked as a duplicate of this bug. ***
*** Bug 525817 has been marked as a duplicate of this bug. ***
*** Bug 525819 has been marked as a duplicate of this bug. ***
*** Bug 525906 has been marked as a duplicate of this bug. ***
*** Bug 525925 has been marked as a duplicate of this bug. ***
*** Bug 525926 has been marked as a duplicate of this bug. ***
*** Bug 525933 has been marked as a duplicate of this bug. ***
*** Bug 525591 has been marked as a duplicate of this bug. ***
*** Bug 526184 has been marked as a duplicate of this bug. ***
*** Bug 526182 has been marked as a duplicate of this bug. ***
*** Bug 526847 has been marked as a duplicate of this bug. ***
*** Bug 526849 has been marked as a duplicate of this bug. ***
*** Bug 526764 has been marked as a duplicate of this bug. ***
*** Bug 526596 has been marked as a duplicate of this bug. ***
*** Bug 527322 has been marked as a duplicate of this bug. ***
*** Bug 527703 has been marked as a duplicate of this bug. ***
*** Bug 528001 has been marked as a duplicate of this bug. ***
*** Bug 528109 has been marked as a duplicate of this bug. ***
*** Bug 528391 has been marked as a duplicate of this bug. ***
*** Bug 529024 has been marked as a duplicate of this bug. ***
*** Bug 529292 has been marked as a duplicate of this bug. ***
*** Bug 529466 has been marked as a duplicate of this bug. ***
*** Bug 529688 has been marked as a duplicate of this bug. ***
*** Bug 529834 has been marked as a duplicate of this bug. ***
*** Bug 530256 has been marked as a duplicate of this bug. ***
*** Bug 530377 has been marked as a duplicate of this bug. ***
*** Bug 530468 has been marked as a duplicate of this bug. ***
*** Bug 531292 has been marked as a duplicate of this bug. ***
*** Bug 531244 has been marked as a duplicate of this bug. ***
*** Bug 531822 has been marked as a duplicate of this bug. ***
*** Bug 533556 has been marked as a duplicate of this bug. ***
*** Bug 534285 has been marked as a duplicate of this bug. ***
*** Bug 536064 has been marked as a duplicate of this bug. ***
*** Bug 536866 has been marked as a duplicate of this bug. ***
*** Bug 537136 has been marked as a duplicate of this bug. ***
*** Bug 537188 has been marked as a duplicate of this bug. ***
*** Bug 537307 has been marked as a duplicate of this bug. ***
*** Bug 537662 has been marked as a duplicate of this bug. ***
*** Bug 537870 has been marked as a duplicate of this bug. ***
*** Bug 537948 has been marked as a duplicate of this bug. ***
*** Bug 538487 has been marked as a duplicate of this bug. ***
*** Bug 538536 has been marked as a duplicate of this bug. ***
*** Bug 538702 has been marked as a duplicate of this bug. ***
*** Bug 539119 has been marked as a duplicate of this bug. ***
*** Bug 539299 has been marked as a duplicate of this bug. ***
*** Bug 539303 has been marked as a duplicate of this bug. ***
*** Bug 539407 has been marked as a duplicate of this bug. ***
*** Bug 539408 has been marked as a duplicate of this bug. ***
*** Bug 539409 has been marked as a duplicate of this bug. ***
*** Bug 539478 has been marked as a duplicate of this bug. ***
*** Bug 539742 has been marked as a duplicate of this bug. ***
Sorry to disappoint you, but there is very little chance for a fix of this bug since I have no more time to give to this project. The only solutions I can give you is : 1) Uninstall N-A 2) Become the new project leader of N-A and fix the bug by yourself (more info here : http://www.grumz.net/?q=node/318) Thanks for your understanding
*** Bug 541299 has been marked as a duplicate of this bug. ***
*** Bug 541317 has been marked as a duplicate of this bug. ***
*** Bug 541402 has been marked as a duplicate of this bug. ***
*** Bug 541778 has been marked as a duplicate of this bug. ***
*** Bug 543509 has been marked as a duplicate of this bug. ***
*** Bug 543543 has been marked as a duplicate of this bug. ***
*** Bug 543835 has been marked as a duplicate of this bug. ***
*** Bug 544087 has been marked as a duplicate of this bug. ***
*** Bug 544084 has been marked as a duplicate of this bug. ***
*** Bug 544742 has been marked as a duplicate of this bug. ***
*** Bug 545421 has been marked as a duplicate of this bug. ***
*** Bug 545922 has been marked as a duplicate of this bug. ***
*** Bug 546564 has been marked as a duplicate of this bug. ***
*** Bug 546566 has been marked as a duplicate of this bug. ***
*** Bug 547341 has been marked as a duplicate of this bug. ***
I am not sure how to verify this, but it seems that by installing gnome-core this problem seems to have gone away. Previously I was using a stripped down system and didn't have it, but tried this. If others could verify, it might just mean adding another dependency.
*** Bug 547517 has been marked as a duplicate of this bug. ***
*** Bug 548112 has been marked as a duplicate of this bug. ***
*** Bug 548323 has been marked as a duplicate of this bug. ***
*** Bug 549185 has been marked as a duplicate of this bug. ***
*** Bug 549190 has been marked as a duplicate of this bug. ***
*** Bug 549324 has been marked as a duplicate of this bug. ***
*** Bug 549384 has been marked as a duplicate of this bug. ***
*** Bug 549388 has been marked as a duplicate of this bug. ***
*** Bug 549391 has been marked as a duplicate of this bug. ***
*** Bug 481533 has been marked as a duplicate of this bug. ***
*** Bug 549842 has been marked as a duplicate of this bug. ***
*** Bug 550063 has been marked as a duplicate of this bug. ***
*** Bug 550094 has been marked as a duplicate of this bug. ***
*** Bug 550552 has been marked as a duplicate of this bug. ***
*** Bug 550958 has been marked as a duplicate of this bug. ***
*** Bug 551479 has been marked as a duplicate of this bug. ***
*** Bug 551462 has been marked as a duplicate of this bug. ***
Is somebody able to provide a valgrind log for this so we can track this down? Any volunteers' help really appreciated, because this module is unmaintained.
(In reply to comment #113) > Is somebody able to provide a valgrind log for this so we can track this down? > > Any volunteers' help really appreciated, because this module is unmaintained. > I can help out but need some directions. This bug manifests in more than one way. Sometimes a bug reporting window pops up, but often Nautilus simply vanishes from the Gnome desktop and takes down any other GUI applications that are running at the time (IceDove, Terminal, etc). When the crash takes place, the processes are often still running but no longer appear on the Gnome desktop. Nautilus must be manually killed to get it to restart. Can you tell me how to run a valgrind log on Nautilus? I'll be glad to run any other diagnostics you like to help locate this problem.
*** Bug 552495 has been marked as a duplicate of this bug. ***
*** Bug 552970 has been marked as a duplicate of this bug. ***
*** Bug 553039 has been marked as a duplicate of this bug. ***
This seems to be caused by incorrect declaration of NautilusActionsConfigGconfReader struct. The parent should be NautilusActionsConfigGconf instead of NautilusActionsConfig. Because of that a write to NautilusActionsConfigGconfReader->actions_notify_id overwrites NautilusActionsConfigGconf->conf_client which then causes a crash next time it is used. This is also apparently fixed in svn version over a year ago.
*** Bug 554062 has been marked as a duplicate of this bug. ***
*** Bug 554370 has been marked as a duplicate of this bug. ***
Heikki: Great, thanks for the investigations! Any SVN revision? Looks like we just need a (non-maintainer) release for nautilus-actions then if the fix is already in but no release containing it. grumz, do you have time for a last 1.4.2 release from the current SVN code? :-) Unfortunately, Nautilus-actions does not use ftp://ftp.gnome.org/pub/GNOME/sources/ , but http://www.grumz.net/index.php?q=node/5 . Otherwise might be easier to have a non-maintainer release if grumz doesn't have time at all...
(In reply to comment #121) > Heikki: Great, thanks for the investigations! Any SVN revision? It was fixed in 480
Ok, then we can close this as FIXED. I am in contact with Frederic (the main developer) and I think I'll make a release with this fix soon.
*** Bug 554955 has been marked as a duplicate of this bug. ***
*** Bug 555485 has been marked as a duplicate of this bug. ***
*** Bug 555059 has been marked as a duplicate of this bug. ***
*** Bug 555975 has been marked as a duplicate of this bug. ***
*** Bug 556366 has been marked as a duplicate of this bug. ***
*** Bug 556356 has been marked as a duplicate of this bug. ***
Just a comment: since the fixed code has not yet been released, is it correct to have the bug CLOSED/RESOLVED? I can understand it if the fixed code were to be released in a few days at most, but it's been more than 2 weeks now.
From a QA point of view: Bug fixed in the codebase means that bug is resolved. This is unrelated to any potential tarball releases.
*** Bug 557133 has been marked as a duplicate of this bug. ***
*** Bug 558052 has been marked as a duplicate of this bug. ***
*** Bug 558290 has been marked as a duplicate of this bug. ***
*** Bug 558758 has been marked as a duplicate of this bug. ***
*** Bug 559577 has been marked as a duplicate of this bug. ***
*** Bug 559609 has been marked as a duplicate of this bug. ***
*** Bug 560527 has been marked as a duplicate of this bug. ***
*** Bug 560689 has been marked as a duplicate of this bug. ***
*** Bug 562076 has been marked as a duplicate of this bug. ***
*** Bug 563514 has been marked as a duplicate of this bug. ***
*** Bug 563662 has been marked as a duplicate of this bug. ***
*** Bug 539328 has been marked as a duplicate of this bug. ***
*** Bug 563593 has been marked as a duplicate of this bug. ***
*** Bug 566271 has been marked as a duplicate of this bug. ***
*** Bug 566763 has been marked as a duplicate of this bug. ***
*** Bug 564085 has been marked as a duplicate of this bug. ***
*** Bug 566930 has been marked as a duplicate of this bug. ***
*** Bug 567075 has been marked as a duplicate of this bug. ***
*** Bug 568112 has been marked as a duplicate of this bug. ***
*** Bug 568247 has been marked as a duplicate of this bug. ***
*** Bug 568444 has been marked as a duplicate of this bug. ***
*** Bug 568918 has been marked as a duplicate of this bug. ***
*** Bug 569137 has been marked as a duplicate of this bug. ***
*** Bug 570935 has been marked as a duplicate of this bug. ***
*** Bug 570875 has been marked as a duplicate of this bug. ***
*** Bug 572654 has been marked as a duplicate of this bug. ***
*** Bug 572836 has been marked as a duplicate of this bug. ***
*** Bug 573872 has been marked as a duplicate of this bug. ***
*** Bug 573861 has been marked as a duplicate of this bug. ***
(In reply to comment #123) > Ok, then we can close this as FIXED. I am in contact with Frederic (the main > developer) and I think I'll make a release with this fix soon. If this happened, where is the tarball located exactly? I'm getting tired of the Debian noise here.
*** Bug 574313 has been marked as a duplicate of this bug. ***
*** Bug 575144 has been marked as a duplicate of this bug. ***
*** Bug 575979 has been marked as a duplicate of this bug. ***
*** Bug 576292 has been marked as a duplicate of this bug. ***
*** Bug 577068 has been marked as a duplicate of this bug. ***
*** Bug 582814 has been marked as a duplicate of this bug. ***
Hi all, I believed have read the bugzilla, but obviously I was missing this entry ;-( As the new nautilus-actions maintainer, I am currently preparing a new release. there will be No new features there, but hopefully we will find all fixes committed in svn/git since two years. Regards Pierre oh - yes, I'll try to distribute in ftp.gnome.org -
bug 599711 against 2.28.1 seems to be dupe of this bug. In this case bug 480179 should be reopened.
I do not agree What would be the rationale behind "I reopen a closed bug because someone always uses an old version" ?
@Pierre, I thought user has filed bug against 2.28.1 and in this version user is getting crash though it has fix applied.
Akhil, 2.28.1 is the Gnome version, but surely not the Nautilus Action version. I've asked the reporter for his exact version number. I would be amazed if this was a recent one. But, if there is a crash with the fix applied, shouldn't it be a new bug ? Regards Pierre
*** Bug 609061 has been marked as a duplicate of this bug. ***
bug 652319 against nautilus-actions-1.4.1
*** Bug 652445 has been marked as a duplicate of this bug. ***