is this a duplicate?

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/223912

mp wrote:
> Public bug reported:
> 
> After an upgrade to Hardy Heron - fresh, clean install - Nautilus hangs,
> freezes and
> 
> CPU usage rise to 100% and
> RAM to 88% at first (+50% swap use)
> and slowly eats more and more RAM - and after 10-15 minutes (I haven't tried 
> to let it hang any longer than that) almost all RAM is gone (1.256GB + 512MB 
> swap)
> 
> ....when opening, via: Places / Name_of_disk an USB ext. HDD.
> 
> on a: 2.6.24-16-generic #1 SMP / Toshiba Satellite Pro A120
> 
> /dev/sdb1    367G  336G   13G  97%   /media/disk_name
> 
> /dev/sdb1 on /media/disk_name type ext3 (rw,nosuid,nodev,uhelper=hal)
> 
> PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND 
> 7836 XX          20   0    601m  563m  14m R   77.6     49.6     5:58.56     
> nautilus 
> 
> All updates installed - incl. "Pre-released updates (hardy-proposed)"
> 
> It happens every time I try to view the HDD via Nautilus and
> 
>  ~/.xsession-errors outputs:
> 
> Initializing nautilus-image-converter extension
> Initializing nautilus-share extension
> seahorse nautilus module initialized
> ** (nautilus:7836): WARNING **: Unable to add monitor: Not supported
> Nautilus-Share-Message: Called "net usershare info" but it failed: 'net 
> usershare' returned error 255: net usershare: cannot open usershare directory 
> /var/lib/samba/usershares. Error No such file or directory
> Please ask your system administrator to enable user sharing.
> 
> ==========
> 
> The HDD is 400GB and opens fine on a Gutsy system - in the past on the
> machine where it now freezes as well as on a Gutsy installation on
> another machine.
> 
> The disk is also accessible via music players (I am listening to music
> as I type right now - CPU usage 100% and Nautilus is frozen) and from a
> terminal. The disk works fine, it seems.
> 
> When trying to close Nautilus the "Force quit" option appears and when
> clicked Nautilus disappears and restarts on location: /home/me
> 
> Other USB disks (with less storage space open fine).
> 
> I removed the "nautilus-share extension", but that made no difference
> apart from different output from .xsession:
> 
> Initializing nautilus-image-converter extension
> seahorse nautilus module initialized
> 
> ** (nautilus:8360): WARNING **: Unable to add monitor: Not supported
> Initializing nautilus-image-converter extension
> seahorse nautilus module initialized
> 
> ** (nautilus:8453): WARNING **: Unable to add monitor: Not supported
> 
> ===
> 
> Then I removed all other additional Nautilus plugins installed and tried
> a few times more: that gives this output:
> 
> Initializing nautilus-image-converter extension
> Initializing nautilus-share extension
> seahorse nautilus module initialized
> 
> ** (nautilus:8219): WARNING **: Unable to add monitor: Not supported
> Nautilus-Share-Message: Called "net usershare info" but it failed: 'net 
> usershare' returned error 255: net usershare: cannot open usershare directory 
> /var/lib/samba/usershares. Error No such file or directory
> Please ask your system administrator to enable user sharing.
> 
> Initializing nautilus-image-converter extension
> seahorse nautilus module initialized
> 
> ** (nautilus:8360): WARNING **: Unable to add monitor: Not supported
> Initializing nautilus-image-converter extension
> seahorse nautilus module initialized
> 
> ** (nautilus:8453): WARNING **: Unable to add monitor: Not supported
> 
> (synaptic:8047): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper:
> assertion `node != NULL' failed
> 
> ========
> 
> the output of /var/log/messages when plugging in the disk is:
> 
> May  4 21:56:05 taz kernel: [  764.546723] usb 3-2: new high speed USB device 
> using ehci_hcd and address 5
> May  4 21:56:05 taz kernel: [  764.681014] usb 3-2: configuration #1 chosen 
> from 1 choice
> May  4 21:56:05 taz kernel: [  764.688375] scsi4 : SCSI emulation for USB 
> Mass Storage devices
> May  4 21:56:10 taz kernel: [  769.693033] scsi 4:0:0:0: Direct-Access     
> HDS72404 0KLAT80          KFAO PQ: 0 ANSI: 0
> May  4 21:56:10 taz kernel: [  769.694509] sd 4:0:0:0: [sdb] 781421568 
> 512-byte hardware sectors (400088 MB)
> May  4 21:56:10 taz kernel: [  769.695644] sd 4:0:0:0: [sdb] Write Protect is 
> off
> May  4 21:56:10 taz kernel: [  769.696999] sd 4:0:0:0: [sdb] 781421568 
> 512-byte hardware sectors (400088 MB)
> May  4 21:56:10 taz kernel: [  769.697881] sd 4:0:0:0: [sdb] Write Protect is 
> off
> May  4 21:56:10 taz kernel: [  769.697891]  sdb: sdb1
> May  4 21:56:10 taz kernel: [  769.712854] sd 4:0:0:0: [sdb] Attached SCSI 
> disk
> May  4 21:56:10 taz kernel: [  769.712900] sd 4:0:0:0: Attached scsi generic 
> sg1 type 0
> May  4 21:56:10 taz kernel: [  770.107691] kjournald starting.  Commit 
> interval 5 seconds
> May  4 21:56:10 taz kernel: [  770.107996] EXT3-fs warning: maximal mount 
> count reached, running e2fsck is recommended
> May  4 21:56:10 taz kernel: [  770.112387] EXT3 FS on sdb1, internal journal
> May  4 21:56:10 taz kernel: [  770.112394] EXT3-fs: mounted filesystem with 
> ordered data mode.
> May  4 22:24:01 taz -- MARK --
> 
> =================
> 
> dmesg outputs:
> [  764.546723] usb 3-2: new high speed USB device using ehci_hcd and address 5
> [  764.681014] usb 3-2: configuration #1 chosen from 1 choice
> [  764.688375] scsi4 : SCSI emulation for USB Mass Storage devices
> [  764.695423] usb-storage: device found at 5
> [  764.695429] usb-storage: waiting for device to settle before scanning
> [  769.692155] usb-storage: device scan complete
> [  769.693033] scsi 4:0:0:0: Direct-Access     HDS72404 0KLAT80          KFAO 
> PQ: 0 ANSI: 0
> [  769.694509] sd 4:0:0:0: [sdb] 781421568 512-byte hardware sectors (400088 
> MB)
> [  769.695644] sd 4:0:0:0: [sdb] Write Protect is off
> [  769.695649] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [  769.695652] sd 4:0:0:0: [sdb] Assuming drive cache: write through
> [  769.696999] sd 4:0:0:0: [sdb] 781421568 512-byte hardware sectors (400088 
> MB)
> [  769.697881] sd 4:0:0:0: [sdb] Write Protect is off
> [  769.697885] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [  769.697887] sd 4:0:0:0: [sdb] Assuming drive cache: write through
> [  769.697891]  sdb: sdb1
> [  769.712854] sd 4:0:0:0: [sdb] Attached SCSI disk
> [  769.712900] sd 4:0:0:0: Attached scsi generic sg1 type 0
> [  770.107691] kjournald starting.  Commit interval 5 seconds
> [  770.107996] EXT3-fs warning: maximal mount count reached, running e2fsck 
> is recommended
> [  770.112387] EXT3 FS on sdb1, internal journal
> [  770.112394] EXT3-fs: mounted filesystem with ordered data mode.
> 
> and then starts outputting many of this errors:
> [  770.930584] APIC error on CPU0: 40(40)
> [  787.581040] APIC error on CPU0: 40(40)
> [  787.971311] APIC error on CPU0: 40(40)
> [  791.263433] APIC error on CPU0: 40(40)
> [  801.318227] APIC error on CPU0: 40(40)
> [  802.994016] APIC error on CPU0: 40(40)
> [  829.080801] APIC error on CPU0: 40(40)
> [  832.390041] APIC error on CPU0: 40(40)
> [  848.172154] APIC error on CPU0: 40(40)
> [  910.668443] APIC error on CPU0: 40(40)
> [  911.767848] APIC error on CPU0: 40(40)
> [  915.706377] APIC error on CPU0: 40(40)
> [  927.066955] APIC error on CPU0: 40(40)
> [  935.432496] APIC error on CPU0: 40(40)
> [  987.078945] APIC error on CPU0: 40(40)
> [ 1008.585550] APIC error on CPU0: 40(40)
> [ 1026.086893] APIC error on CPU0: 40(40)
> [ 1030.778036] APIC error on CPU0: 40(40)
> [ 1149.280791] APIC error on CPU0: 40(40)
> [ 1185.019258] APIC error on CPU0: 40(40)
> [ 1228.316456] APIC error on CPU0: 40(40)
> [ 1231.409653] APIC error on CPU0: 40(40)
> [ 1237.058403] APIC error on CPU0: 40(40)
> [ 1277.811659] APIC error on CPU0: 40(40)
> [ 1288.417867] APIC error on CPU0: 40(40)
> [ 1317.078241] APIC error on CPU0: 40(40)
> [ 1321.025546] APIC error on CPU0: 40(40)
> [ 1330.103862] APIC error on CPU0: 40(40)
> [ 1494.752175] APIC error on CPU0: 40(40)
> [ 1532.174969] APIC error on CPU0: 40(40)
> [ 2322.545857] APIC error on CPU0: 40(40)
> [ 2636.254855] APIC error on CPU0: 40(40)
> [ 2673.022566] APIC error on CPU0: 40(40)
> [ 2819.564332] APIC error on CPU0: 40(40)
> [ 2826.084504] APIC error on CPU0: 40(40)
> [ 2991.828197] APIC error on CPU0: 40(40)
> [ 3001.369860] APIC error on CPU0: 40(40)
> [ 3097.909787] APIC error on CPU0: 40(40)
> [ 3264.799749] APIC error on CPU0: 40(40)
> 
> ** Affects: nautilus (Ubuntu)
>      Importance: Undecided
>          Status: New
>

-- 
opening USB ext hdd causes nautilus to freeze
https://bugs.launchpad.net/bugs/226746
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to