[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1280881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)
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 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1280881/+attachment/4008125/+files/UdevAdmTest.txt -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1280881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)
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 filesystem there, since I can manually mount the filesystem using 'mount' on the commandline. Here is the partition table from 'fdisk': # fdisk -l /dev/sdb Disk /dev/sdb: 1000.2 GB, 1000170586112 bytes 38 heads, 40 sectors/track, 1285169 cylinders, total 1953458176 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x4d7da5b1 Device Boot Start End Blocks Id System /dev/sdb12048 1953458175 9767280647 HPFS/NTFS/exFAT -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1280881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280881] [NEW] Does not detect hotplugged storage device (WD Elements 1TB)
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 given permissions 660 and belongs to group disk. 2. The usual symlinks to the device are not created in /dev/disk/by-uuid/ or /dev/disk/by-label/. 3. This problem appeared with the out-of-the-box partition table; I have blanked the first 100MB of the disk with dd, recreated the partition table and reformatted, but it still happens. 4. 'udevadm info /dev/sdb1' gives very perfunctory output for this drive, compared to the copious output for other drives. 5. 'udisksctl info -b /dev/sdb1' responds 'Error looking up object for device /dev/sdb1'. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: udev 204-0ubuntu19.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 22:40:52 2014 HotplugNewDevices: /dev/sdb1 /dev/sdb HotplugNewMounts: InstallationDate: Installed on 2014-02-16 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 33667KG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=a5496a96-8572-4e2c-96ac-d8e36c7775d6 ro quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 33667KG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn33667KG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33667KG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33667KG dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: 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 given permissions 660 and belongs to group disk. 2. The usual symlinks to the device are not created in /dev/disk/by-uuid/ or /dev/disk/by-label/. 3. This problem appeared with the out-of-the-box partition table; I have blanked the first 100MB of the disk with dd, recreated the partition table and reformatted, but it still happens. 4. 'udevadm info /dev/sdb1' gives very perfunctory output for this drive, compared to the copious output for other drives. + 5. 'udisksctl info -b /dev/sdb1' responds 'Error looking up object for device /dev/sdb1'. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: udev 204-0ubuntu19.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 22:40:52 2014 HotplugNewDevices: /dev/sdb1 /dev/sdb HotplugNewMounts: - + InstallationDate: Installed on 2014-02-16 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 33667KG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=a5496a96-8572-4e2c-96ac-d8e36c7775d6 ro quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 33667KG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn33667KG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33667KG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33667KG dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO -- 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 this
[Bug 1280881] Re: Does not detect hotplugged storage device (WD Elements 1TB)
** 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 only partition on the drive) is created, it is given permissions 600 and belongs to group root, whereas for other drives the device is given permissions 660 and belongs to group disk. 2. The usual symlinks to the device are not created in /dev/disk/by-uuid/ or /dev/disk/by-label/. 3. This problem appeared with the out-of-the-box partition table; I have blanked the first 100MB of the disk with dd, recreated the partition table and reformatted, but it still happens. 4. 'udevadm info /dev/sdb1' gives very perfunctory output for this drive, compared to the copious output for other drives. 5. 'udisksctl info -b /dev/sdb1' responds 'Error looking up object for device /dev/sdb1'. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: udev 204-0ubuntu19.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 22:40:52 2014 HotplugNewDevices: /dev/sdb1 /dev/sdb HotplugNewMounts: InstallationDate: Installed on 2014-02-16 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 33667KG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=a5496a96-8572-4e2c-96ac-d8e36c7775d6 ro quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 33667KG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn33667KG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33667KG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33667KG dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1280881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551752] [NEW] Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error
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: /sys/devices/pci:00/:00:1d.7/usb2/2-3) SYNCHRONIZE CACHE: synchronize cache(10): Fixed format, current; Sense key: Key=9 Additional sense: Logical unit not ready, cause not reportable Info fld=0x0 [0] FAILED: No such file or directory (Continuing despite SYNCHRONIZE CACHE failure.) STOP UNIT: start stop unit: transport: Host_status=0x07 [DID_ERROR] Driver_status=0x00 [DRIVER_OK, SUGGEST_OK] FAILED: No such file or directory The drive is unmounted but not completely removed; I can still see it in the Computer display in nautilus. It only happens with this flash drive, and not with others. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-18-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Mar 30 16:33:37 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) ProcEnviron: LANG=en_ZA.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error https://bugs.launchpad.net/bugs/551752 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551752] Re: Safely Remove Drive of Kingston 8GB flash drive produces Unable to stop drive error
** 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 https://bugs.launchpad.net/bugs/551752 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220969] Re: thinkpad t41 brightness buttons don't work as expected on hardy
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 brightness buttons don't work as expected on hardy https://bugs.launchpad.net/bugs/220969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
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/^[ \t]*driver[ \t]**//I;s/*[
\t]*$//;p}}' /etc/X11/xorg.conf`
The value of $VIDEO is then tested to see if it is 'intel', 'ati', or
'radeon'. Unfortunately, with the new, less-configuration-required
X.Org, the xorg.conf doesn't actually contain a Driver line in the
Device section. The value of $VIDEO ends up being empty, and the code
that is conditional on the test doesn't get run when it should.
It doesn't seem like the configuration of the thinkpad_acpi hotkey mask
(at line 32 in hotkey-setup) should be dependent on the video driver in
use, in any case. Surely if the driver were 'fglrx', for example, the
hotkey mask should still be configured?
This is in hardy final, with hotkey-setup version 0.1-17ubuntu21, on an
IBM ThinkPad T43 model 2668F5G.
** Affects: hotkey-setup (Ubuntu)
Importance: Undecided
Status: New
--
/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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220969] [NEW] thinkpad t41 brightness buttons don't work as expected on hardy
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 by one step as it should, but gnome-power manager doesn't recognize the keypress - the popup display doesn't appear, and the slider in the brightness applet doesn't go up. On the other hand, when I press the 'brightness down' (Fn+End) key, the screen brightness goes all the way down to the minimum brightness - but the popup display does appear and the brightness applet's slider does go down to 0. This was all with GNOME; in KDE, there isn't the brightness-dropping-to-zero problem, but the 'brightness up' keypress still doesn't get recognized. I've filed this under hal, but there's probably a gnome-power-manager aspect too. ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- thinkpad t41 brightness buttons don't work as expected on hardy https://bugs.launchpad.net/bugs/220969 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215277] [NEW] typo in Locations.xml
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. This is on hardy, with latest version (2.22.1.1-0ubuntu1) of libgweather-common. A patch to Locations.xml is included. ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215277] Re: typo in Locations.xml
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145071] Re: Darklooks gnome-panel msg unreadable
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 scheme better. -- Darklooks gnome-panel msg unreadable https://bugs.launchpad.net/bugs/145071 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145071] Re: Darklooks gnome-panel msg unreadable
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 gnome-panel msg unreadable https://bugs.launchpad.net/bugs/145071 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149153] typo in /etc/init.d/tpb
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: Undecided Status: New -- typo in /etc/init.d/tpb https://bugs.launchpad.net/bugs/149153 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77402] Re: hotkey-setup vs tpb
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 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121921] Re: ubiquity crashes when first partition is set to dont use
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 this for at least ten minutes, at which point I became tired and killed it. I will attach the logfiles you ask for. ** Attachment added: /var/log/partman http://launchpadlibrarian.net/8520184/partman -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121921] Re: ubiquity crashes when first partition is set to dont use
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61822] Re: IBM Thinkpad volume keys handled wrong and made partly unusable
*** 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 partly unusable https://launchpad.net/bugs/61822 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76091] Re: kmilo-legacy needed to display brightness changes, zoom, etc, on Thinkpad T41p
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, zoom, etc, on Thinkpad T41p https://launchpad.net/bugs/76091 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61822] Re: IBM Thinkpad volume keys handled wrong and made partly unusable
*** 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 partly unusable https://launchpad.net/bugs/61822 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
