system bug: nautilus loops opening hundreds of new sessions on the system tray...
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
I was working with Nautilus coping and pasting images, and creating some icons shortcuts when nautilus crashed: it closed itself and after some seconds it reopened automatically without any user interaction, looping opening hundreds of new sessions on the system tray. I shout down my ACER Aspire PC and after the bootstrap the loop autostart again.., now I can't use my Intrepid ubuntu anymore!!
I went to check some system logs to discover what's happening and I discovered this one:
<<
Nov 18 20:08:28 hal-9000 kernel: [ 590.920844] nautilus[7804]: segfault at bf3e3ffc ip b759bf15 sp bf3e4000 error 6 in libglib-
Nov 18 20:08:30 hal-9000 kernel: [ 593.005564] nautilus[7809]: segfault at bf746ffc ip b737d9d5 sp bf747000 error 6 in libpthread-
Nov 18 20:08:32 hal-9000 kernel: [ 595.014264] nautilus[7815]: segfault at bf39dff8 ip b75db4c0 sp bf39dfd0 error 6 in libgobject-
Nov 18 20:08:34 hal-9000 kernel: [ 597.053554] nautilus[7821]: segfault at bf0ecfec ip b76a5f1c sp bf0ecff0 error 6 in libglib-
Nov 18 20:08:36 hal-9000 kernel: [ 599.159192] nautilus[7826]: segfault at bf0aefe0 ip b76ec4c3 sp bf0aefe0 error 6 in libgobject-
Nov 18 20:08:38 hal-9000 kernel: [ 601.209959] nautilus[7832]: segfault at bf0dbffc ip b7694f15 sp bf0dc000 error 6 in libglib-
Nov 18 20:08:40 hal-9000 kernel: [ 603.227614] nautilus[7838]: segfault at bf35afec ip b7693c81 sp bf35aff0 error 6 in libgobject-
Nov 18 20:08:42 hal-9000 kernel: [ 605.239629] nautilus[7844]: segfault at bf3bfff0 ip b75fd4c3 sp bf3bfff0 error 6 in libgobject-
Nov 18 20:08:44 hal-9000 kernel: [ 607.289872] nautilus[7850]: segfault at bf60dffc ip b73449d5 sp bf60e000 error 6 in libpthread-
Nov 18 20:08:46 hal-9000 kernel: [ 609.325501] nautilus[7855]: segfault at bf371fc8 ip b75af4c0 sp bf371fa0 error 6 in libgobject-
Nov 18 20:08:49 hal-9000 kernel: [ 611.419368] nautilus[7860]: segfault at bf500ffc ip b74b8f1c sp bf501000 error 6 in libglib-
Nov 18 20:08:51 hal-9000 kernel: [ 613.495158] nautilus[7866]: segfault at bf7bdfe8 ip b76fb4c0 sp bf7bdfc0 error 6 in libgobject-
Nov 18 20:08:53 hal-9000 kernel: [ 615.552716] nautilus[7873]: segfault at bf052fec ip b758bc81 sp bf052ff0 error 6 in libgobject-
Nov 18 20:08:55 hal-9000 kernel: [ 617.607494] nautilus[7878]: segfault at bf6adfe0 ip b75eb4c3 sp bf6adfe0 error 6 in libgobject-
Nov 18 20:08:57 hal-9000 kernel: [ 619.703394] nautilus[7884]: segfault at bf2effec ip b76a8f1c sp bf2efff0 error 6 in libglib-
Nov 18 20:08:59 hal-9000 kernel: [ 621.783968] nautilus[7890]: segfault at bf745ff0 ip b737c9d9 sp bf745ff4 error 6 in libpthread-
Nov 18 20:09:01 hal-9000 kernel: [ 623.838238] nautilus[7896]: segfault at bf58efe8 ip b75cc4c0 sp bf58efc0 error 6 in libgobject-
Nov 18 20:09:03 hal-9000 kernel: [ 625.957358] nautilus[7902]: segfault at bf76cfc8 ip b76aa4c0 sp bf76cfa0 error 6 in libgobject-
>>
I could paste thousands of lines exactly like the ones above...now my system is completely unusable because of this bug!! I tried to shutdown my PC a lot of times but every time I start "Intrepid" the Nautilus autostarting loop, make my PC unusable. Should I format and reinstall my root partition?
help me please!
My config:
Ubuntu 8.10
kernel 2.6.27-8
CPU: Intel Core 2 duo 2,4 Ghz
RAM: 1024 Mb
Nvidia 9500 GT with 500 Mb ram video
hdd: 250 gb free disk space
Alessandro
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
As you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Once you have done this, repeat the steps necessary to recreate the crash.
You may then get a crash report notification. If so, follow the on-screen instructions to submit the crash report. If you don't get a notification and you are using Ubuntu with the Gnome desktop environment - launch a terminal and submit the crash report using /usr/share/ apport/ apport- gtk --crash- file=/var/ crash/_ my_crash_ report. crash. If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
Also bear in mind that you should only flag a bug as a security vulnerability if you are reporting a specific security problem. You aren't reporting a security problem, so you shouldn't have flagged this bug as a security vulnerability.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.