[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-23 Thread chriscoulson
One second actually, I've just realised I've rebooted since removing that extra rule. I'll try it again in a sec -- UUID's not correctly allocated for DMRAID devices in Gutsy https://bugs.launchpad.net/bugs/154834 You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-23 Thread chriscoulson
This is the output I get from udevmonitor: UEVENT[1193162136.861547] add /block/dm-1 (block) UDEV [1193162136.872177] add /block/dm-1 (block) -- UUID's not correctly allocated for DMRAID devices in Gutsy https://bugs.launchpad.net/bugs/154834 You received this bug notification because

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-23 Thread chriscoulson
I added ENV{DM_UUID}=="dmraid-*", OPTIONS="link_priority=50" to the file 65-dmsetup.rules, just underneath the line ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}", and it didn't make any difference. Not sure if this is the correct place to add it. -- UUID's not correctly allocat

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-23 Thread chriscoulson
Kay: [EMAIL PROTECTED]:~$ ls -l /dev/.udev/names/*B080F3DA80F3A54E* total 0 -rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fdm-1 -rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fsda\x2fsda1 So, it does seem there are two devices competing for the same name. I'll try adding that rule

[Bug 156193] Re: Tracker should search Tomboy Notes

2007-10-23 Thread chriscoulson
Maybe this should be requested as a feature over at the Tracker bugzilla, if it hasn't already. http://bugzilla.gnome.org/browse.cgi?product=tracker -- Tracker should search Tomboy Notes https://bugs.launchpad.net/bugs/156193 You received this bug notification because you are a member of Ubuntu

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-23 Thread chriscoulson
Kay, As requested: [EMAIL PROTECTED]:~$ sudo dd if=/dev/sda1 count=2 | hexdump -C 2+0 records in 2+0 records out 1024 bytes (1.0 kB) copied, 0.00038136 seconds, 2.7 MB/s eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS.| 0010 00 00 00 00 00 f8 00 00 3f 00 ff 00 3

[Bug 155884] Re: apport - No crash report notifications in Gutsy

2007-10-22 Thread chriscoulson
I do believe the intended behaviour of apport-gtk is that it will only report crash reports belonging to the current user. Nevertheless, it's not even doing that at the moment. -- apport - No crash report notifications in Gutsy https://bugs.launchpad.net/bugs/155884 You received this bug notifica

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-22 Thread chriscoulson
As requested: [EMAIL PROTECTED]:~$ sudo vol_id /dev/sda1 [sudo] password for chr1s: ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION= ID_FS_UUID=B080F3DA80F3A54E ID_FS_UUID_ENC=B080F3DA80F3A54E ID_FS_LABEL= ID_FS_LABEL_ENC= ID_FS_LABEL_SAFE= [EMAIL PROTECTED]:~$ sudo vol_id /dev/mapper/nvidia_

[Bug 155884] apport - No crash report notifications in Gutsy

2007-10-22 Thread chriscoulson
Public bug reported: Binary package hint: apport Apport is not notifying me of new crash reports, even though Compiz crashes frequently on my system. When I looked in /var/crash, there are crash reports from Compiz and other applications that I've never been notified about. Running /usr/share/ap

[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-20 Thread chriscoulson
** Attachment added: "fstab" http://launchpadlibrarian.net/10080275/fstab -- UUID's not correctly allocated for DMRAID devices in Gutsy https://bugs.launchpad.net/bugs/154834 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 154864] gparted truncates device names for /dev/mapper devices

2007-10-20 Thread chriscoulson
Public bug reported: Binary package hint: gparted GParted in Gutsy appears to truncate device names for /dev/mapper devices, omitting the partition number from the end. I've attached a screenshot, showing GParted listing 8 partitions on 1 device, all with apparently identical device names. Note,

[Bug 154864] Re: gparted truncates device names for /dev/mapper devices

2007-10-20 Thread chriscoulson
** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/10080828/Screenshot.png -- gparted truncates device names for /dev/mapper devices https://bugs.launchpad.net/bugs/154864 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 154834] UUID's not correctly allocated for DMRAID devices in Gutsy

2007-10-20 Thread chriscoulson
Public bug reported: When I upgraded from Feisty to Gutsy, I noticed that my NTFS partition was no longer being mounted at startup. The NTFS partition is on a striped array using DMRAID, along with several ext3 partitions (all of which mounted ok). The NTFS partition (/dev/mapper/nvidia_effeccbe1)

[Bug 153257] Re: gimp not in graphics menu

2007-10-16 Thread chriscoulson
** Changed in: gimp (Ubuntu) Status: New => Invalid -- gimp not in graphics menu https://bugs.launchpad.net/bugs/153257 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.co

[Bug 153257] Re: gimp not in graphics menu

2007-10-16 Thread chriscoulson
Your gimp.desktop is identical to mine. Do you have another gimp.desktop stored in ~/.local/share/applications ? -- gimp not in graphics menu https://bugs.launchpad.net/bugs/153257 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 153257] Re: gimp not in graphics menu

2007-10-16 Thread chriscoulson
Which Ubuntu version are you running? Can you post your gimp.desktop? -- gimp not in graphics menu https://bugs.launchpad.net/bugs/153257 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@list

[Bug 99508] Re: Window titlebar displayed not right with compiz enabled

2007-10-15 Thread chriscoulson
I've nominated this for Gutsy as this seems to be a long standing issue affecting quite a few users. With Compiz enabled by default, this bug will not leave very good first impressions with potentially new Ubuntu users. -- Window titlebar displayed not right with compiz enabled https://bugs.launc

[Bug 152648] Re: gdm_slave_xioerror_handler: Fatal X error

2007-10-14 Thread chriscoulson
Actually, it still appears to crash even after logging in the second user. This is up-to-date Gutsy RC with nvidia 100.14.19 drivers -- gdm_slave_xioerror_handler: Fatal X error https://bugs.launchpad.net/bugs/152648 You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 152648] gdm_slave_xioerror_handler: Fatal X error

2007-10-14 Thread chriscoulson
Public bug reported: When using the new fast user switch applet to login a second user on my system, X restarts when left at the login screen for more than a few seconds. The error in my syslog is: Oct 14 15:26:45 localhost gdm[13647]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarti

[Bug 67099] Re: blank message window when viewing a read msg from unread list

2007-10-13 Thread chriscoulson
Also confirmed on Gutsy RC. -- blank message window when viewing a read msg from unread list https://bugs.launchpad.net/bugs/67099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubunt

[Bug 145863] Re: compiz.real crashed with SIGSEGV in groupDrawTabAnimation()

2007-10-13 Thread chriscoulson
Marking as confirmed. This is repeatable on Gutsy RC x86-64 as well. I get the crash as soon as I close any window from a group. ** Changed in: compiz (Ubuntu) Status: New => Confirmed -- compiz.real crashed with SIGSEGV in groupDrawTabAnimation() https://bugs.launchpad.net/bugs/145863 Yo

[Bug 99508] Re: Window titlebar displayed not right with compiz enabled

2007-10-13 Thread chriscoulson
I can also confirm that this is not fixed in Gutsy RC - nvidia 7900GT 100.14.19 drivers. Screenshot attached. ** Attachment added: "Screenshot-1.png" http://launchpadlibrarian.net/9966577/Screenshot-1.png -- Window titlebar displayed not right with compiz enabled https://bugs.launchpad.net/bu

[Bug 99508] Re: Window titlebar displayed not right with compiz enabled

2007-10-13 Thread chriscoulson
This is still affecting users in Gutsy RC ** Changed in: compiz (Ubuntu) Status: Fix Released => Confirmed -- Window titlebar displayed not right with compiz enabled https://bugs.launchpad.net/bugs/99508 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 146840] Re: compiz.real crashed with SIGSEGV in groupHandleChanges()

2007-10-12 Thread chriscoulson
I am also seeing compiz.real crashed with SIGSEGV in groupHandleChanges() quite frequently when running applications with gksu and opening Pidgin. This is on Gutsy RC (AMD64) upgraded from Feisty. ** Changed in: compiz (Ubuntu) Status: New => Confirmed -- compiz.real crashed with SIGSEGV

[Bug 70235] Re: 6.06.1 upgrade of nvidia restricted modules fails

2006-11-08 Thread chriscoulson
I had this problem when I upgraded nvidia-glx and linux-restricted- modules a few days ago. The contents of /var/log/gdm/:0.log are in the file attached. The error reported is that there is a version mismatch between the kernel module (8762) and the X module (8776) This happens with kernel 2.6.15-

[Bug 42149] Re: USB devices are not powered off at shutdown (Dapper, 2.6.15)

2006-10-17 Thread chriscoulson
See bug #5410 over at http://bugzilla.kernel.org/ ** Changed in: linux-source-2.6.15 (Ubuntu) Status: Unconfirmed => Confirmed -- USB devices are not powered off at shutdown (Dapper, 2.6.15) https://launchpad.net/bugs/42149 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https:

[Bug 48773] Re: Mouse doesn't get turned off on system shutdown

2006-10-04 Thread chriscoulson
I'm also affected by this. I'm running Ubuntu 6.06 with kernel 2.6.15-26-amd64-k8, but can confirm it also happens with 2.6.15-25-amd64-generic, 2.6.15-26-amd64-generic and 2.6.15-27-amd64-k8. I've only ever had the problem since installing Dapper. My USB devices powered down correctly when shuttin

[Bug 42149] Re: USB devices are not powered off at shutdown (Dapper, 2.6.15)

2006-10-04 Thread chriscoulson
Note, this is still a problem for me with kernel 2.6.15-26-amd64-k8. If I suspend the system, all of my devices power down correctly. If I shutdown the system, everything appears to remain powered. There is a thread on the Ubuntu forums here: http://www.ubuntuforums.org/showthread.php?t=206385 an

[Bug 42149] Re: USB devices are not powered off at shutdown (Dapper, 2.6.15)

2006-08-16 Thread chriscoulson
I am seeing exactly the same problem on my machine. My motherboard is also an Asus A8N-E. I'm running Ubuntu Dapper with the 2.6.15.26-amd64-generic kernel. It used power down correctly under Breezy and powers down fully from other operating systems. -- USB devices are not powered off at shutdow