[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)

2014-04-17 Thread Adrian Frith
For me, at least, the bug is fixed in 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280881 Title: Does not detect hotplugged storage device (WD Elements 1TB) To manage notifications about

[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)

2014-03-05 Thread Adrian Frith
As requested, the output of sudo udevadm test /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1 is attached. ** Attachment added: UdevAdmTest.txt

[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)

2014-02-28 Thread Adrian Frith
As requested: # blkid -p /dev/sdb1 /dev/sdb1: LABEL=ElementsSmall UUID=6822170D55D13F29 TYPE=ntfs USAGE=filesystem PART_ENTRY_SCHEME=dos PART_ENTRY_TYPE=0x7 PART_ENTRY_NUMBER=1 PART_ENTRY_OFFSET=2048 PART_ENTRY_SIZE=1953456128 PART_ENTRY_DISK=8:16 There is definitely a partition and a

[Bug 1280881] [NEW] Does not detect hotplugged storage device (WD Elements 1TB)

2014-02-16 Thread Adrian Frith
Public bug reported: My WD Elements 1TB drive does not automatically mount when connected. Some things I have noticed: 1. While the device /dev/sdb1 (for the only partition on the drive) is created, it is given permissions 600 and belongs to group root, whereas for other drives the device is

[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)

2014-02-16 Thread Adrian Frith
** Description changed: - My WD Elements 1TB drive does not automatically mount when connected. + My WD Elements 1TB drive does not automatically mount when connected, + although I can mount it manually with 'mount'. Some things I have noticed: 1. While the device /dev/sdb1 (for the

[Bug 551752] [NEW] Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error

2010-03-30 Thread Adrian Frith
Public bug reported: Binary package hint: nautilus When I use the Safely Remove Drive command on a Kingston 8GB flash drive (USB ID 0930:6544), the following error dialog appears: Unable to stop drive Error detaching: helper exited with exit code 1: Detaching device /dev/sdb USB device:

[Bug 551752] Re: Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error

2010-03-30 Thread Adrian Frith
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42501020/Dependencies.txt ** Attachment added: usr_lib_nautilus.txt http://launchpadlibrarian.net/42501021/usr_lib_nautilus.txt -- Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error

[Bug 220969] Re: thinkpad t41 brightness buttons don't work as expected on hardy

2008-04-24 Thread Adrian Frith
Never mind about this; I've traced the root cause of this problem in hotkey-setup and filed it separately as bug #221571. Because of that bug, the hotkey mask doesn't get set correctly, so the 'brightness up' keypress isn't received by hal which causes the problem here. -- thinkpad t41

[Bug 221571] Re: /etc/init.d/hotkey-setup looks at xorg.conf to find what video driver is in use; this doesn't work any more

2008-04-24 Thread Adrian Frith
I should add: because this affects the setting of the thinkpad_acpi hotkey mask, it has irritating effects like those in bug #220969. -- /etc/init.d/hotkey-setup looks at xorg.conf to find what video driver is in use; this doesn't work any more https://bugs.launchpad.net/bugs/221571 You

[Bug 221571] [NEW] /etc/init.d/hotkey-setup looks at xorg.conf to find what video driver is in use; this doesn't work any more

2008-04-24 Thread Adrian Frith
Public bug reported: Binary package hint: hotkey-setup In the 'do_video' and 'do_thinkpad' methods in /etc/init.d/hotkey-setup, the following code is used to find out what video driver X is using: VIDEO=`sed -n -e '/^[ \t]*section[ \\t]*device/I,/^[ \t]*endsection/I{/^[ \t]*driver[ \t]*/I{s/^[

[Bug 220969] [NEW] thinkpad t41 brightness buttons don't work as expected on hardy

2008-04-23 Thread Adrian Frith
Public bug reported: Binary package hint: hal I've looked at all the various thinkpad-brightness-related bugs on launchpad, but this seems to be one that hasn't been reported yet. On my Thinkpad T41 (model 2668-F5G), when I press the 'brightness up' (Fn+Home) key, the screen brightness goes up

[Bug 215277] [NEW] typo in Locations.xml

2008-04-10 Thread Adrian Frith
Public bug reported: Binary package hint: libgweather-common On line 286355 of /usr/share/libgweather/Locations.xml, the tz-hint field for South Africa is listed as Africa/Johannesburt. This is a mistake - it should be Africa/Johannesburg. There is no such place (or timezone!) as Johannesburt.

[Bug 215277] Re: typo in Locations.xml

2008-04-10 Thread Adrian Frith
** Attachment added: patch for Locations.xml http://launchpadlibrarian.net/13338727/libgweather-locations-joburg-typo.patch -- typo in Locations.xml https://bugs.launchpad.net/bugs/215277 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 145071] Re: Darklooks gnome-panel msg unreadable

2007-10-23 Thread Adrian Frith
I've found a solution to this problem. Change the value of the gconf property '/apps/notification-daemon/theme' to 'standard' (instead of 'ubuntu'). Then the notifcation popups will use the default look instead of the Ubuntu look - one of the results being that they follow your selected colour

[Bug 145071] Re: Darklooks gnome-panel msg unreadable

2007-10-07 Thread Adrian Frith
For reference, it was the revision 461 in the GNOME SVN repository which changed the tooltip colours (and hence the notification popup background). You can see this change at http://svn.gnome.org/viewcvs /gnome-themes-extras/trunk/gtk- themes/Darklooks/gtk-2.0/gtkrc?r1=460r2=461 -- Darklooks

[Bug 149153] typo in /etc/init.d/tpb

2007-10-04 Thread Adrian Frith
Public bug reported: Binary package hint: tpb In line 16 of /etc/init.d/tpb there is a typo where two characters are inverted. It reads tbp -d where it should of course actually read tpb -d. This is with latest gutsy, tpb version 0.6.4-2.3ubuntu2. ** Affects: tpb (Ubuntu) Importance:

[Bug 77402] Re: hotkey-setup vs tpb

2007-10-04 Thread Adrian Frith
As a temporary workaround, you could install the metapackage at http://frith.co.za/hotkey-tpb_1.0_all.deb - it 'Depends' on tpb and 'Provides' and 'Replaces' hotkey-setup. Or you could create a similar package yourself with 'equivs'. -- hotkey-setup vs tpb https://bugs.launchpad.net/bugs/77402

[Bug 121921] Re: ubiquity crashes when first partition is set to dont use

2007-07-18 Thread Adrian Frith
I have also experienced this bug, on an IBM/Lenovo Thinkpad T43 (model 2668-F5G) which has a SATA HDD. Ubiquity doesn't actually crash, it just seems to get stuck in some kind of infinite loop - the cursor becomes the busy indication, and the GUI becomes completely unresponsive. It remained like

[Bug 121921] Re: ubiquity crashes when first partition is set to dont use

2007-07-18 Thread Adrian Frith
** Attachment added: /var/log/syslog http://launchpadlibrarian.net/8520185/syslog -- ubiquity crashes when first partition is set to dont use https://bugs.launchpad.net/bugs/121921 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 61822] Re: IBM Thinkpad volume keys handled wrong and made partly unusable

2007-04-04 Thread Adrian Frith
*** This bug is a duplicate of bug 51537 *** There is a workaround for this bug: install the kmilo-legacy package, and then delete the file /usr/share/services/kmilo/kmilo_generic.desktop. Then you have the good old behaviour of kmilo-thinkpad! -- IBM Thinkpad volume keys handled wrong and made

[Bug 76091] Re: kmilo-legacy needed to display brightness changes, zoom, etc, on Thinkpad T41p

2007-04-02 Thread Adrian Frith
As to the problem of the generic kmilo plugin interfering with kmilo- legacy, there is a workaround which I posted in bug #61822: just delete the file /usr/share/services/kmilo/kmilo_generic.desktop (or move it somewhere else, whatever). -- kmilo-legacy needed to display brightness changes,

[Bug 61822] Re: IBM Thinkpad volume keys handled wrong and made partly unusable

2007-04-02 Thread Adrian Frith
*** This bug is a duplicate of bug 51537 *** There is a workaround for this bug: install the kmilo-legacy package, and then delete the file /usr/share/services/kmilo/kmilo_generic.desktop. Then you have the good old behaviour of kmilo-thinkpad! -- IBM Thinkpad volume keys handled wrong and made