I am using gnome 2.30 from gnome-overlay, It doesn't automount external devices, if I try to run palimpsest, I get: ** libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100) Abortito [ebuild R ] sys-fs/udisks-1.0.1 USE="nls -bash-completion -debug -doc -remote-access" 698 kB [0] [ebuild R ] gnome-base/nautilus-2.30.1 USE="gnome -doc -test -xmp" 6,013 kB [1] [ebuild R ] sys-apps/gnome-disk-utility-2.30.1 USE="nautilus -avahi -doc -remote-access" 1,958 kB [1] Total: 3 packages (3 reinstalls), Size of downloads: 8,668 kB Portage tree and overlays: [0] /usr/portage/tree [1] /usr/portage/dist/local/layman/gnome Reproducible: Always Steps to Reproduce: 1. emerge sys-apps/gnome-disk-utility 2. palimpsest 3.
*** Bug 321973 has been marked as a duplicate of this bug. ***
emerge -pv gvfs please.
(In reply to comment #2) > emerge -pv gvfs please. > [ebuild R ] gnome-base/gvfs-1.6.1 USE="cdda gdu gnome http udev -archive -avahi -bash-completion -bluetooth -doc -fuse -gnome-keyring -gphoto2 -hal -samba" 1,333 kB [1]
What's your udev version (with useflags) ? Can udisks mount the drive from command line ? Is CONFIG_SYSFS_DEPRECATED_V2 unset ?
[ebuild R ] sys-fs/udev-154 USE="extras (-selinux) -test" 0 kB Yes I can mount with "udisks --mount" but I can open the folders mounted only as root. This my .config ... # CONFIG_SYSFS_DEPRECATED_V2 is not set ...
I am totally unable to reproduce this, please try again on new crated user account with Gnome 2.30 from official tree (that should be completed in some hours). My working setup: [ebuild R ] sys-fs/udev-151-r4 USE="extras test -devfs-compat -old-hd-rules (-selinux)" 633 kB [0] [ebuild R ] sys-fs/udisks-1.0.1 USE="bash-completion nls -debug -doc -remote-access" 698 kB [0] [ebuild R ] sys-apps/gnome-disk-utility-2.30.1 USE="avahi nautilus -doc -remote-access" 0 kB [1]
(In reply to comment #6) > please try again on new crated user > account with Gnome 2.30 from official tree Gnome 2.30 isn't in portage tree, It's only on gnome overlay. "new crated user" I should create a new user with "useradd ..."?
As explained in my previous comment: gnome 2.30 is entering the tree just now ;-) And yes, useradd seems a good option to create that new user :-)
I have updated gnome to portage tree, deleted gnome-overlay, created a new user (useradd -m -G users,audio,cdrom,video,plugdev,usb,games,disk,cdrw,wheel,haldaemon), but it doesn't work. But I have notated that if I connect my iphone it is mounted normally, but If I run "udisks --monitor-details" if I connect my iphone nothing appears, if I connect an usb pen it show me all information about it but isn't automounted. If I run palimpsest: ** libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100) Abortito Thanks
Please report this directly to upstream: http://bugzilla.gnome.org And post a link to it here Thanks
Done Bug 622066 on bugzilla.gnome.org
(In reply to comment #11) > Done Bug 622066 on bugzilla.gnome.org > OK thanks, I hope they will know better where to find the problem, since it's annoying when a bug affects to some user but not to others (like me :-|)
What partitions does your system have? Some days ago I saw similar problems being "solved" by recreating some broken ntfs partitions and so :-/
# <fs> <mountpoint> <type> /dev/sda1 /boot ext3 /dev/sda2 / xfs /dev/sda3 /usr/portage/dist ext3 /dev/sda5 /usr/portage/tree reiserfs /dev/sda6 /media/Test ext4 /dev/sdc1 /media/Backup ntfs-3g /dev/sdb2 /media/Win7 ntfs-3g /dev/sdb3 /media/WinTest ntfs-3g tmpfs /var/tmp/portage tmpfs
Are you able to see all these partitions listed in "Places" ?
Yes. I can see all mounted folders
Is this a regression over g-d-u-2.28?
Which package contain gdu?
(In reply to comment #18) > Which package contain gdu? > Ups, g-d-u = gnome-disk-utility ;-)
Now I am using: [ebuild R ] sys-apps/gnome-disk-utility-2.30.1 USE="nautilus -avahi -doc -fat -remote-access" 0 kB
But, did this work with 2.28?
I think of yes
(In reply to comment #9) > if I connect my iphone > nothing appears, if I connect an usb pen it show me all information about it > but isn't automounted. > Is any error message shown in /var/log/messages after this occurs?
I don't have /var/log/messages
I use app-admin/syslog-ng for log messages, I don't know what file uses your log system
# cd /var/log cups emerge.log news wtmp .. dmesg faillog portage Xorg.0.log ConsoleKit emerge-fetch.log lastlog sandbox Xorg.0.log.old
Install then syslog-ng, start it and try to look for error messages there (I think it's explained in handbook also ;-))
I think that this is interesting: Jul 5 16:40:42 yellowhat gnome-session[1959]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name Jul 5 16:40:42 yellowhat gnome-session[1959]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name Jul 5 16:40:48 yellowhat polkitd[2130]: started daemon version 0.96 using authority implementation `local' version `0.96' [ebuild R ] sys-auth/consolekit-0.4.1 USE="pam policykit -debug -doc" 389 kB
That's what I get If I connect an usb pen: Jul 5 17:10:28 yellowhat dhcpcd[1782]: eth0: leased 37.234.80.137 for 1800 seconds Jul 5 17:24:00 yellowhat kernel: [ 2633.790044] hub 1-0:1.0: state 7 ports 10 chg 0000 evt 0010 Jul 5 17:24:00 yellowhat kernel: [ 2633.790068] ehci_hcd 0000:00:13.5: GetStatus port 4 status 001803 POWER sig=j CSC CONNECT Jul 5 17:24:00 yellowhat kernel: [ 2633.790180] hub 1-0:1.0: port 4, status 0501, change 0001, 480 Mb/s Jul 5 17:24:00 yellowhat kernel: [ 2633.894078] hub 1-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x501 Jul 5 17:24:00 yellowhat kernel: [ 2633.945144] ehci_hcd 0000:00:13.5: port 4 high speed Jul 5 17:24:00 yellowhat kernel: [ 2633.945150] ehci_hcd 0000:00:13.5: GetStatus port 4 status 001005 POWER sig=se0 PE CONNECT Jul 5 17:24:01 yellowhat kernel: [ 2633.996041] usb 1-4: new high speed USB device using ehci_hcd and address 4 Jul 5 17:24:01 yellowhat kernel: [ 2634.047072] ehci_hcd 0000:00:13.5: port 4 high speed Jul 5 17:24:01 yellowhat kernel: [ 2634.047080] ehci_hcd 0000:00:13.5: GetStatus port 4 status 001005 POWER sig=se0 PE CONNECT Jul 5 17:24:01 yellowhat kernel: [ 2634.110501] usb 1-4: default language 0x0409 Jul 5 17:24:01 yellowhat kernel: [ 2634.111001] usb 1-4: udev 4, busnum 1, minor = 3 Jul 5 17:24:01 yellowhat kernel: [ 2634.111004] usb 1-4: New USB device found, idVendor=1043, idProduct=8012 Jul 5 17:24:01 yellowhat kernel: [ 2634.111007] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jul 5 17:24:01 yellowhat kernel: [ 2634.111010] usb 1-4: Product: Flash Disk Jul 5 17:24:01 yellowhat kernel: [ 2634.111023] usb 1-4: Manufacturer: USB2.0 Jul 5 17:24:01 yellowhat kernel: [ 2634.111125] usb 1-4: usb_probe_device Jul 5 17:24:01 yellowhat kernel: [ 2634.111130] usb 1-4: configuration #1 chosen from 1 choice Jul 5 17:24:01 yellowhat kernel: [ 2634.111806] usb 1-4: adding 1-4:1.0 (config #1, interface 0) Jul 5 17:24:01 yellowhat kernel: [ 2634.111853] usb-storage 1-4:1.0: usb_probe_interface Jul 5 17:24:01 yellowhat kernel: [ 2634.111859] usb-storage 1-4:1.0: usb_probe_interface - got id Jul 5 17:24:01 yellowhat kernel: [ 2634.113606] scsi7 : usb-storage 1-4:1.0 Jul 5 17:24:01 yellowhat kernel: [ 2634.113747] drivers/usb/core/inode.c: creating file '004' Jul 5 17:24:02 yellowhat kernel: [ 2635.113744] scsi 7:0:0:0: Direct-Access USB2.0 USB Flash Drive 1.00 PQ: 0 ANSI: 2 Jul 5 17:24:02 yellowhat kernel: [ 2635.114164] sd 7:0:0:0: Attached scsi generic sg4 type 0 Jul 5 17:24:02 yellowhat kernel: [ 2635.121097] sd 7:0:0:0: [sdd] 4171776 512-byte logical blocks: (2.13 GB/1.98 GiB) Jul 5 17:24:02 yellowhat kernel: [ 2635.121904] sd 7:0:0:0: [sdd] Write Protect is off Jul 5 17:24:02 yellowhat kernel: [ 2635.121911] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00 Jul 5 17:24:02 yellowhat kernel: [ 2635.121917] sd 7:0:0:0: [sdd] Assuming drive cache: write through Jul 5 17:24:02 yellowhat kernel: [ 2635.131963] sd 7:0:0:0: [sdd] Assuming drive cache: write through Jul 5 17:24:02 yellowhat kernel: [ 2635.131975] sdd: sdd1 Jul 5 17:24:02 yellowhat kernel: [ 2635.138216] sd 7:0:0:0: [sdd] Assuming drive cache: write through Jul 5 17:24:02 yellowhat kernel: [ 2635.138226] sd 7:0:0:0: [sdd] Attached SCSI removable disk
Do you have consolekit daemon running? /etc/init.d/consolekit status
/etc/init.d/consolekit status * status: stopped
/etc/init.d/consolekit start * Starting ConsoleKit daemon ... * start-stop-daemon: /usr/sbin/console-kit-daemon is already running [ !! ] * ERROR: consolekit failed to start
/etc/init.d/consolekit stop * WARNING: consolekit is already stopped yellowhat vasco # /etc/init.d/consolekit start * Starting ConsoleKit daemon ... * start-stop-daemon: /usr/sbin/console-kit-daemon is already running [ !! ] * ERROR: consolekit failed to start
It's because some other process already launched it, I would simply add it to default runlevel, reboot and check "freshly"
rc-update add consolokit default, reboot, but nothing changed same error in messages and no automount
rc-update add consolekit default, reboot, but nothing changed, no automount
I have no idea what to check now :-( Maybe you could try to attach strace output of: $ strace palimpsest 2>out
Created attachment 238003 [details] strace palimpsest 2>out
Do you have RAID? Do you use mdadm?
I don't use RAID and mdadm
Please provide "fdisk -l" output (https://bugs.launchpad.net/bugs/571038)
# fdisk -l omitting empty partition (5) Disco /dev/sda: 150.0 GB, 150039945216 byte 255 testine, 63 settori/tracce, 18241 cilindri, totale 293046768 settori Unità = settori di 1 * 512 = 512 byte Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Identificativo disco: 0x104f104e Dispositivo Boot Start End Blocks Id System /dev/sda1 63 2104514 1052226 6 FAT16 /dev/sda2 2104515 149565149 73730317+ c W95 FAT32 (LBA) /dev/sda3 149565150 159814619 5124735 c W95 FAT32 (LBA) /dev/sda4 159814620 293046767 66616074 f W95 Esteso (LBA) /dev/sda5 159814683 164023649 2104483+ b W95 FAT32 /dev/sda6 164023713 293046767 64511527+ b W95 FAT32 Disco /dev/sdb: 320.1 GB, 320072933376 byte 255 testine, 63 settori/tracce, 38913 cilindri, totale 625142448 settori Unità = settori di 1 * 512 = 512 byte Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Identificativo disco: 0xa8ec58b5 Dispositivo Boot Start End Blocks Id System /dev/sdb1 * 63 625137344 312568641 7 HPFS/NTFS
Thanks, just forwarded to ubuntu people, hopefully they could know where the problem could be
Thanks to you
Can you attach "part.list" file from running: sfdisk -d /dev/sda ?
sfdisk -d /dev/sda # partition table of /dev/sda unit: sectors /dev/sda1 : start= 63, size= 2104452, Id= 6 /dev/sda2 : start= 2104515, size=147460635, Id= c /dev/sda3 : start=149565150, size= 10249470, Id= c /dev/sda4 : start=159814620, size=133232148, Id= f /dev/sda5 : start=159814683, size= 4208967, Id= b /dev/sda6 : start=164023713, size=129023055, Id= b
Created attachment 239841 [details] sfdisk -d /dev/sda
Interesting news,I don't know which packages I updated, but automount now WORKS. Also palimpsest WORKS.
[ebuild R ] sys-fs/udisks-1.0.1-r1 USE="nls -bash-completion -debug -doc -remote-access" 0 kB [ebuild R ] gnome-base/nautilus-2.30.1-r1 USE="gnome -doc -test -xmp" 6,013 kB [ebuild R ] sys-apps/gnome-disk-utility-2.30.1 USE="nautilus -avahi -doc -fat -remote-access" 1,958 kB
I have 3 hard disk: WD 320 GB 2.5 Backup (connected directly on mainboard), WD Raptor 150GB Gentoo (connected through an Enermax Mobil Rack), Seagate 320GB 3.5 Win7(connected through an Enermax Mobil Rack). Now for high temperature I use only WDs because on Seagate I have only Windows 7. WD raptor has always been connect to a rack (the upper one), but yesterday I connect WD Raptor to the other one and automount works. So today decided to return to previous configuration and gives me no automount and same palimpsest error. Both rack are connect to the red Sata ports, while HDD Backup and DVD-RW to the black ones.
(In reply to comment #50) > I have 3 hard disk: WD 320 GB 2.5 Backup (connected directly on mainboard), WD > Raptor 150GB Gentoo (connected through an Enermax Mobil Rack), Seagate 320GB > 3.5 Win7(connected through an Enermax Mobil Rack). > Now for high temperature I use only WDs because on Seagate I have only Windows > 7. > WD raptor has always been connect to a rack (the upper one), but yesterday I > connect WD Raptor to the other one and automount works. So today decided to > return to previous configuration and gives me no automount and same palimpsest > error. > Both rack are connect to the red Sata ports, while HDD Backup and DVD-RW to the > black ones. > Please explain this directly to upstream: https://bugzilla.gnome.org/show_bug.cgi?id=622066 And probably also to ubuntu people as there are more affected users on that distribution: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/571038 Thanks
We will follow this upstream since there are not much we can do downstream (and looks to affect only to people with certain setups)
