** Summary changed: - Adding a user to a group modifies other users' groups and passwords + Changing users randomly affects other users and group memberships
** Description changed: - Nothing to do with 3270 but couldnt post with real problem package which is - pmount......? + Impact: + gnome-system-tools does not keep its internal model of users and groups consistent with the real world in /etc/passwd, /etc/shadow, and /etc/group. This leads to errors like deleting a different user than the one you chose in the UI, dropping unrelated users from groups like admin (thus making the system inaccessible for administration), and similar effects. - Overall description: My TAT CODISK 2.0 and MP3 player SigmaTel MSCN Music Player - and and CDs I put in my cd drive will not automount. This problem is repeatable - and mostly consistant. Having searced forums and this site it is similar to bug - #23770. This problem emerged after adding a new desktop user to the system and - changing the primary user password and has only occured on one of the two Ubuntu - systems I have. - Having worked through bug #23770 I have tried all the suggestions and am able to - mount USB drives with the command pmount -d /dev/sda1. - Attached is the terminal output from this command and from the id command. + Fix: + Update the internal world model with each operation, done in http://svn.gnome.org/viewvc/gnome-system-tools?view=revision&revision=4017. This needs some serious backporting for Feisty and earlier, I suppose; it should apply well to Gutsy. - Steps to reproduce: This problem is reproducable with both kernel versions I - run: 2.6.12-9-686 and my main kerenel 2.6.12-10-686 + Regression potential: The bug could not be fixed fully, there might be + more places which need update calls. Potentially the patch could mess up + the pam db even more. - Actual results: Drives will not auto mount and appear on the desktop. Connot be - opened via computer menu, delivering error message: + TEST CASE: + 1. launch users-admin + 2. create a test1 user + 3. create a test2 user (with admin rights) + 4. create a test3 user + 5. delete the test1 user + 6. delete the test3 user - mount: wrong fs type, bad option, bad superblock on /dev/sdb, - missing codepage or other error - In some cases useful info is found in syslog - try - dmesg | tail or so - - mount: wrong fs type, bad option, bad superblock on /dev/sdb, - missing codepage or other error - In some cases useful info is found in syslog - try - dmesg | tail or so - - Error: could not execute pmount - - The output from id is: - - [EMAIL PROTECTED]:~$ id - uid=1000(rick) gid=1000(rick) - groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(lpadmin),105(scanner),106(admin),1000(rick) - - There is some inconsistency in the error message as this is only generated after - the second time the USB is mounted. Upon reboot or the first time a device is - mounted the message is : - - Error: given UDI is not a mountable volume - - Here is my pmount output: - - [EMAIL PROTECTED]:~$ pmount -d /dev/sda1 - resolved /dev/sda1 to device /dev/sda1 - mount point to be used: /media/sda1 - no iocharset given, current locale encoding is UTF-8 - locale encoding uses UTF-8, setting iocharset to 'utf8' - Cleaning lock directory /var/lock/pmount/_dev_sda1 - device_whitelist: checking /etc/pmount.allow... - device_whitlisted(): nothing matched, returning 0 - find_sysfs_device: looking for sysfs directory for device 8:1 - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-5 (253:5) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-4 (253:4) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-3 (253:3) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-2 (253:2) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-1 (253:1) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/dm-0 (253:0) - find_sysfs_device: checking whether /dev/sda1 is on /sys/block/sda (8:0) - find_sysfs_device: major device numbers match - find_sysfs_device: minor device numbers do not match, checking partitions... - find_sysfs_device: checking whether device /dev/sda1 matches partition 8:0 - find_sysfs_device: checking whether device /dev/sda1 matches partition 8:1 - find_sysfs_device: -> partition matches, belongs to block device /sys/block/sda - device_removable: corresponding block device for /dev/sda1 is /sys/block/sda - get_blockdev_attr: value of /sys/block/sda/removable == 1 - policy check passed - spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks' '/dev/sda1' - spawn(): /sbin/cryptsetup terminated with status 255 - device is not LUKS encrypted, or cryptsetup with LUKS support is not installed - locking mount point directory - mount point directory locked - spawnv(): executing /bin/mount '/bin/mount' '-t' 'udf' '-o' - 'nosuid,nodev,user,async,atime,noexec,uid=1000,gid=1000,umask=007,iocharset=utf8' - '/dev/sda1' '/media/sda1' - spawn(): /bin/mount terminated with status 32 - spawnv(): executing /bin/mount '/bin/mount' '-t' 'udf' '-o' - 'nosuid,nodev,user,async,atime,noexec,uid=1000,gid=1000,umask=007' '/dev/sda1' - '/media/sda1' - spawn(): /bin/mount terminated with status 32 - spawnv(): executing /bin/mount '/bin/mount' '-t' 'iso9660' '-o' - 'nosuid,nodev,user,async,atime,noexec,uid=1000,gid=1000,iocharset=utf8' - '/dev/sda1' '/media/sda1' - spawn(): /bin/mount terminated with status 32 - spawnv(): executing /bin/mount '/bin/mount' '-t' 'iso9660' '-o' - 'nosuid,nodev,user,async,atime,noexec,uid=1000,gid=1000' '/dev/sda1' '/media/sda1' - spawn(): /bin/mount terminated with status 32 - spawnv(): executing /bin/mount '/bin/mount' '-t' 'vfat' '-o' - 'nosuid,nodev,user,quiet,shortname=winnt,async,atime,noexec,uid=1000,gid=1000,umask=077,iocharset=utf8' - '/dev/sda1' '/media/sda1' - spawn(): /bin/mount terminated with status 0 - unlocking mount point directory - mount point directory unlocked - - - Thanks - - Rick..... + This will either cause test2 to not be in group admin any more, or be + deleted in step 6 instead of user test3. -- Changing users randomly affects other users and group memberships https://bugs.launchpad.net/bugs/26338 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
