[Bug 1289730] [NEW] systemd-udev fails to execute alsactl during start-up if /usr and/or /var are separate volumes
Public bug reported: During system startup systemd-udev will print the following error messages: [ 15.089778] systemd-udevd[683]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0': No such file or directory [ 15.090130] systemd-udevd[684]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1': No such file or directory alsactl is present: $ which alsactl /usr/sbin/alsactl but on a separate partition: $ df -h /usr/sbin/alsactl DateisystemGröße Benutzt Verf. Verw% Eingehängt auf /dev/mapper/scaleo-usr 12G6,6G 4,1G 62% /usr $ df -h /var DateisystemGröße Benutzt Verf. Verw% Eingehängt auf /dev/mapper/scaleo-var 7,3G2,5G 4,4G 37% /var This suggests that systemd-udev is called before all local partitions have been mounted. $ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 $ apt-cache policy udev udev: Installiert: 204-5ubuntu13 Installationskandidat: 204-5ubuntu13 Versionstabelle: *** 204-5ubuntu13 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Kind regards, Dominik ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289730 Title: systemd-udev fails to execute alsactl during start-up if /usr and/or /var are separate volumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1289730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1276327] Re: deja-dup/duplicity fails gpg encrypted backup in trusty
Am 22.02.2014 17:57, schrieb Launchpad Bug Tracker: > This bug was fixed in the package duplicity - 0.6.23-1ubuntu2 > > --- > duplicity (0.6.23-1ubuntu2) trusty; urgency=medium > > * debian/patches/getpass-encode.patch: > - Always pass getpass a bytes string, preventing a crash when > prompting the user for a passphrase in non-English locales. > LP: #1276327 > -- Michael TerrySat, 22 Feb 2014 10:39:21 -0500 > > ** Changed in: duplicity (Ubuntu) >Status: New => Fix Released > I can confirm that it works. Thanks for the good work! Regards, Dominik Kubla -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276327 Title: deja-dup/duplicity fails gpg encrypted backup in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1276327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1276327] Re: deja-dup/duplicity fails gpg encrypted backup in trusty
Am 05.02.2014 15:40, schrieb Michael Terry: > As a workaround, set LANG=en_US.UTF-8 > > Proper fix on the way. > Hi, thanks for the workaround. That works. Regards, Dominik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276327 Title: deja-dup/duplicity fails gpg encrypted backup in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1276327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276327] [NEW] deja-dup/duplicity fails gpg encrypted backup in trusty
Public bug reported:
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1489, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1483, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1332, in main
do_backup(action)
File "/usr/bin/duplicity", line 1414, in do_backup
globals.gpg_profile.passphrase = get_passphrase(1, action)
File "/usr/bin/duplicity", line 168, in get_passphrase
pass1 = getpass.getpass(_("GnuPG passphrase:")+" ")
File "/usr/lib/python2.7/getpass.py", line 83, in unix_getpass
passwd = fallback_getpass(prompt, stream)
File "/usr/lib/python2.7/getpass.py", line 118, in fallback_getpass
return _raw_input(prompt, stream)
File "/usr/lib/python2.7/getpass.py", line 128, in _raw_input
prompt = str(prompt)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position
10: ordinal not in range(128)
1) lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
2) apt-cache policy duplicity
duplicity:
Installed: 0.6.23-0ubuntu1
Candidate: 0.6.23-0ubuntu1
Version table:
*** 0.6.23-0ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
3) I expected the scheduled backups to succeed as the used to do in the past.
4) The backup aborts with the error message listed above
Additonally deja-dup-preferences vanished from System Preferences, but
that should perhaps be logged as a different bug.
Downgrading deja-dup/duplicity to the saucy versions restores
functionality.
** Affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276327
Title:
deja-dup/duplicity fails gpg encrypted backup in trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1276327/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 499006] [NEW] RFE: apt-build should default to architecture "native" with newer GCC releases
Public bug reported: Binary package hint: apt-build Since it is not really obvious which GCC architecture setting is the appropriate one, it would be better to always use "native" if the installed GCC version supports it. That should be the correct setting for most users. ** Affects: apt-build (Ubuntu) Importance: Undecided Status: New -- RFE: apt-build should default to architecture "native" with newer GCC releases https://bugs.launchpad.net/bugs/499006 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 365049] Re: NM applet should allow to set the CRDA domain
Hi folks, any progress on this? -- NM applet should allow to set the CRDA domain https://bugs.launchpad.net/bugs/365049 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 365052] Re: Disabling wireless connection should trigger rfkill
Hi folks! And progress? Any decision? -- Disabling wireless connection should trigger rfkill https://bugs.launchpad.net/bugs/365052 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 430374] Re: init: mountall main process terminated with status 1
Just updated to version 0.1.4 (among other updates) and that seems to fix it. Of course I had to boot from a USB stick and chroot to the environment on the harddisk to fix it. Would be nice if we could somehow come up with something along the line how Opensolaris handles updates: ZFS snapshot and alternate boot environment for the old version. -- init: mountall main process terminated with status 1 https://bugs.launchpad.net/bugs/430374 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 430374] Re: init: mountall main process terminated with status 1
+1 karmic (x86_64 & ext3 rootfs) and karmic-netbook-remix (i386 & ext4 rootfs) On the x86_64 I was able to get things going by booting through maintenance mode and resuming normal boot. -- init: mountall main process terminated with status 1 https://bugs.launchpad.net/bugs/430374 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
On Monday 03 August 2009 22:37:42 Martin Pitt wrote:
> So does it work with
>
> ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
> ENV{ID_CLASS}=="mouse", RUN=+"keymap $name usb-mosart-0102"
>
> ?
Hi Martin,
sorry about the delay.
Unfortunately this does not solve the problem. xev still reports the key as
XF86Tools.
Everything else works just fine. Since I have already replaced the keyboard for
daily work and no one else has come forward owning one of these, closing the
bug at this stage is fine from my point of view.
Many thanks for your efforts!
Dominik
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Am Sonntag, den 02.08.2009, 20:59 + schrieb Martin Pitt: > Also, to get current data on this, can you please give me the output of > these commands: > > udevadm info --query=all --name=/dev/input/event7 > udevadm info --attribute-walk --name=/dev/input/event7 > udevadm info --query=all --name=/dev/input/event8 > udevadm info --attribute-walk --name=/dev/input/event8 > > (assuming that the two devices in question are 7 and 8 at the moment). > Thanks! > The device number depends on whether the wireless keyboard is connected at boot time. If it is they are 6+7, otherwise 7+8. Here is the output as requested. Cheers, Dominik ** Attachment added: "attribute_walk_event6.txt" http://launchpadlibrarian.net/29833667/attribute_walk_event6.txt ** Attachment added: "attribute_walk_event7.txt" http://launchpadlibrarian.net/29833668/attribute_walk_event7.txt ** Attachment added: "query_all_event6.txt" http://launchpadlibrarian.net/29833669/query_all_event6.txt ** Attachment added: "query_all_event7.txt" http://launchpadlibrarian.net/29833670/query_all_event7.txt -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Am Sonntag, den 02.08.2009, 20:56 + schrieb Martin Pitt:
> > Is there a way to trace the whole sequence done during boot-up?
>
> Something like this. "udevadm test /devices/.../" (the sysfs path) will
> show the matches and commands run.
# udevadm
test /devices/pci:00/:00:1d.2/usb4/4-2/4-2:1.1/input/input7
run_command: calling: test
udevadm_test: version 145
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
...
parse_file: reading '/lib/udev/rules.d/95-keymap.rules' as rules file
add_rule: unknown key 'ID_CLASS' in /lib/udev/rules.d/95-keymap.rules:14
...
Line 14 of 95-keymap.rules is:
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
ID_CLASS=="kbd", RUN=+"keymap $name usb-mosart-0102"
After modifying it to:
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
ENV{ID_CLASS}=="kbd", RUN=+"keymap $name usb-mosart-0102"
The udevadm output looks better. But still no luck.
Cheers,
Dominik
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Am Sonntag, den 02.08.2009, 15:34 + schrieb Martin Pitt:
> Oops, another typo, it needs to be ID_CLASS==. Please replace the line
> with
>
> ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
> ID_CLASS=="kbd", RUN=+"keymap $name usb-mosart-0102"
>
> Now for real!
>
No luck. If I run the kbd command manually it works. I still think we
are trying to redefine on the wrong input device...
Is there a way to trace the whole sequence done during boot-up?
Dominik
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Am Dienstag, den 28.07.2009, 18:56 + schrieb Martin Pitt: > Hello Dominik, > > ok, so it seems that something in the chain doesn't like the > extraordinarily high scan code. Could you please do > > sudo strace -fvvo /tmp/keymap.trace /lib/udev/keymap input/event7 usb- > mosart-0102 > > and then attach /tmp/keymap.trace here? > > Thanks! > It seems to me that we are trying to load the keycode on the wrong input device. If I use the first one (event7) I get EVIOCGKEYCODE (see keymap.trace), if I use the second one (event8) it works (see keymap.trace2) Cheers, Dominik ** Attachment added: "keymap.trace" http://launchpadlibrarian.net/29785263/keymap.trace ** Attachment added: "keymap.trace2" http://launchpadlibrarian.net/29785264/keymap.trace2 -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Hi Martin, the mute key now works, but the media key still returns "config" which is translated to "XF86Tools": domi...@scaleo:~$ sudo /lib/udev/keymap -i input/event7 Press ESC to finish scan code: 0xC0183 key code: config scan code: 0xC0183 key code: config Cheers, Dominik -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
On Mo, 2009-06-29 at 10:57 +, Martin Pitt wrote: > Ugh, seems that input event enumeration changes severely with every > reboot. In the attached udev log and lsinput, event2 is the mouse. Can > you please attach lsinput output and then check with /lib/udev/keymap > which device outputs these keys in the same session, i. e. without > rebooting in between? > > Sorry that this takes so long, it is the first case which we fix which > involves an external USB keyboard. Thanks for bearing with me! > It changed because I unplugged my normal keyboard and attached this one. Now I have booted with both keyboards attached. The special keys show up on input/event7. ** Attachment added: "lsinput.out" http://launchpadlibrarian.net/28638448/lsinput.out -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
On Mi, 2009-06-24 at 06:06 +, Martin Pitt wrote: > Dominik, > > seems these keys are on a different input device then. Can you please > just try all from input/event1 to input/event5? (it's most likely 4 > then) > Yes, they were reported via the second event channel: scan code: 0xC00B7 key code: stopcd scan code: 0xC00E2 key code: min_interesting <--- This is the mute key scan code: 0xC0183 key code: config <--- This is the media player key scan code: 0xC018A key code: mail scan code: 0xC0227 key code: refresh scan code: 0xC0226 key code: stop scan code: 0xC0223 key code: homepage scan code: 0xC0225 key code: forward scan code: 0xC0224 key code: back scan code: 0xC0221 key code: search scan code: 0xC022A key code: bookmarks scan code: 0x10082 key code: sleep scan code: 0xC0194 key code: file scan code: 0xC0192 key code: calc scan code: 0xC00EA key code: volumedown scan code: 0xC00E9 key code: volumeup scan code: 0xC00B5 key code: nextsong scan code: 0xC00B6 key code: previoussong scan code: 0xC00CD key code: playpause Cheers, Dominik -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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
Re: [Bug 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
Martin, I tried "/lib/udev/keymap -i input/event3", but I don't get a keycode displayed for the multimedia keys. Not even for those that do work as expected. Cheers, Dominik -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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 94366] Re: X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
No problem and sorry about the delay. ** Attachment added: "udev" http://launchpadlibrarian.net/28208691/udev -- X-Tension XK-200 Multimedia Keyboard: Media Player key wrong https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
Martin, except for the "Media Player" key being mapped to XF86Tools instead of XF86Music everything works out of the box. All function keys, the scroll wheels (both mouse and keyboard) and all mouse buttons are recognized and work. Cheers, Dominik -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/26947088/dmesg.log -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
** Attachment added: "system.hardware.txt" http://launchpadlibrarian.net/26947077/system.hardware.txt -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/26947094/xkbcomp.txt -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
** Attachment added: "xkbmap.txt" http://launchpadlibrarian.net/26947105/xkbmap.txt -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
** Attachment added: "lsinput.log" http://launchpadlibrarian.net/26947092/lsinput.log -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
It appears to be that my keyboard is broken: It show the same behaviour on Windows Vista. In any case the configuration appears to be correct, but my original keycode list had an error: keycode 179 should be mapped to XF86Music, not keycode 129. Good news is that everything else works as expected. Great job! For completeness here are the debug outputs as recommended by the troubleshooting guide: ** Attachment added: "lshal.log" http://launchpadlibrarian.net/26947063/lshal.log -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
Martin, I attached the keyboard to my workstation. It was recognized correctly but somehow configured wrong (Shift key had no function and some other oddities), so I could not use it. I'll try again and give you the desired output. To answer your question how I determined the key codes: I ran xev and pressed all keys one by one. :-) Cheers, Dominik -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 210847] Re: Configuration dialog for WPA/EAP doesn't fit small in small screens
1. In Ubuntu 9.04 RC: Start your desktop in 800x480 pixels resolution (as on a Asus EeePC) or run Netbook Remix in a VM at this resolution. 2. Open network properties from the NM applet. 3. Select your network connection (actually any connection entry will do) and click on edit. 4. The resulting dialog will be cut off at the bottom. Cheers, Dominik -- Configuration dialog for WPA/EAP doesn't fit small in small screens https://bugs.launchpad.net/bugs/210847 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 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
Martin, sorry for not getting back to you. I have since replaced this keyboard with a wired one, but still own it. I'll connect it again and provide you with the necessary information, but this will take some days. Thanks for taking care... Dominik -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 365052] [NEW] Disabling wireless connection should trigger rfkill
Public bug reported: When disabling wireless networking in the network manager applet, the rfkill switch for the wireless card should be triggered. For two reasons: 1) No sense drawing power for the transmitter if the user does not want to use wireless. 2) On some systems (eg. EeePC) there is no hw switch, so disabling the wireless connectivity should kill all wireless activity. Furthermore due to 2) all wireless drivers should initialize with rfkill enabled and wait for NM to enable wireless communications. Otherwise booting a device without a hw switch on a plane could cause problems. (So this affects NM and the kernel as well). Perhaps this should be a configuration option: default to on, default to off, default to last status. Thanks, Dominik ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- Disabling wireless connection should trigger rfkill https://bugs.launchpad.net/bugs/365052 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 365049] [NEW] NM applet should allow to set the CRDA domain
Public bug reported: With recent Ubuntu kernels switching to userland CRDA it is no longer possible to set the correct CRDA domain for wireless cards. It can not be expected from casual users to install the optional "iw" package and write a init script to set the correct regulatory domain. Therefore the NetworkManger should take care of this and the NetworkManager applet should offer the configuration option for each configured WIFI connection. The initial configuration should set the default based on the entered location (timezone). Since violating the regulatory domain can cause legal problems for Ubuntu users, this is a major concern. Thanks, Dominik ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- NM applet should allow to set the CRDA domain https://bugs.launchpad.net/bugs/365049 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 210847] Re: Configuration dialog for WPA/EAP doesn't fit small in small screens
Is there any progress on this? This problem is still present on UNR 9.04 RC. With NM being standard on UNR and said variant being promoted for devices with a resolution as low as 800x480 this is a real problem. And it's not just the WPA dialog, it's every dialog except "connection information" which does not fit on small screens. That makes the applet pretty much unusable on Netbook Remix. Thanks, Dominik -- Configuration dialog for WPA/EAP doesn't fit small in small screens https://bugs.launchpad.net/bugs/210847 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
Re: [Bug 47081] Re: cupsd should use standard syslog by default
Am Dienstag 19 Februar 2008 schrieb Ralph Janke: > Thank you for your suggestion. However, the changes you are requesting > aren't really a bug and require more discussion, which should be done on > an appropriate mailing list or forum. > http://www.ubuntu.com/support/community/mailinglists might be a good > start for determining which mailing list to use. > > Therefore, I would like to close this report if this is acceptable. > > Thanks > > ** Changed in: cupsys (Ubuntu) > Assignee: (unassigned) => Ralph Janke (txwikinger) >Status: New => Incomplete I agree. Regards, Dominik -- cupsd should use standard syslog by default https://bugs.launchpad.net/bugs/47081 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
Re: [Bug 47085] Re: Wishlist: Support Epson-Kowa printers in Cups
Am Dienstag 19 Februar 2008 schrieb Ralph Janke: > Is this report still an issue, or can it be closed? > > Thanks > > ** Changed in: cupsys (Ubuntu) > Assignee: (unassigned) => Ralph Janke (txwikinger) >Status: New => Incomplete I think most printers are supported now. But the vendor tools support querying the ink level. This functionality is still missing. Regards, Dominik -- Wishlist: Support Epson-Kowa printers in Cups https://bugs.launchpad.net/bugs/47085 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
[Bug 191578] Re: [hardy] rendering issues
I can confirm the problem. The problem appears to be the rendering of background pictures. Looks like some function calculates the pointer to the image buffer wrongly, since it displays random other bitmaps from the same X display. -- [hardy] rendering issues https://bugs.launchpad.net/bugs/191578 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
Re: [Bug 94366] Re: Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
Am Dienstag 04 Dezember 2007 schrieb Brian Murray: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in recently. We were wondering if this is still and issue > for you? Thanks in advance. > > ** Changed in: ubuntu > Assignee: (unassigned) => Brian Murray (brian-murray) >Status: New => Incomplete Hi Brian, I suppose this is still an issue, since: * I always have to load my .Xmodmap file to activate the extra keys. * There is no profile for Kubuntu to use the multi-media keys consistently. BTW. * The "Windows" and "Menu" keys are mapped to modifiers, but they are also not used consistently throughout. Is there a usability team for *ubuntu? Regards, Dominik -- Spock: The odds of surviving another attack are 13562190123 to 1, Captain. -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://bugs.launchpad.net/bugs/94366 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 122999] Re: glxinfo crashed with SIGSEGV in viaXMesaWindowMoved()
Ditto with VIA CLE266. -- glxinfo crashed with SIGSEGV in viaXMesaWindowMoved() https://bugs.launchpad.net/bugs/122999 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 94366] Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard
Public bug reported: I would like to sumit the necessary information to recognize and support the X-Tension XK-200 wireless multimedia keyboard/mouse (and possibly others since it appears to be a OEM device). lsusb output: Bus 001 Device 003: ID 062a:0102 Creative Labs Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x062a Creative Labs idProduct 0x0102 bcdDevice1.00 iManufacturer 1 MOSART Semi. iProduct2 Wireless Keyboard & Mouse iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 181 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0005 1x 5 bytes bInterval 10 Device Status: 0x (Bus Powered) Recommended key mapping for the device: keycode 122 = XF86Search keycode 129 = XF86Music keycode 130 = XF86HomePage keycode 144 = XF86AudioPrev keycode 153 = XF86AudioNext keycode 160 = XF86AudioMute keycode 161 = XF86Calculator keycode 162 = XF86AudioPlay keycode 164 = XF86AudioStop keycode 174 = XF86AudioLowerVolume keycode 176 = XF86AudioRaiseVolume keycode 178 = XF86WWW keycode 198 = XF86MyComputer keycode 223 = XF86Standby keycode 230 = XF86Favorites keycode 231 = XF86Refresh keycode 232 = XF86Stop keycode 233 = XF86Forward keycode 234 = XF86Back keycode 236 = XF86Mail It should be mentioned that in Kubuntu Feisty the following special keys appear not to be mapped to functions or preferred applications: XF86Favourites XF86Standby XF86WWW (works partially: selects home page when focussed on konqueror. should start a web browser window in any other case) ProblemType: Bug Architecture: i386 Date: Wed Mar 21 10:56:47 2007 DistroRelease: Ubuntu 7.04 Uname: Linux duron.intern.kubla.de 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Wishlist: XKB Support for X-Tension XK-200 Multimedia Keyboard https://launchpad.net/bugs/94366 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Thursday 14 September 2006 16:26 schrieb Scott James Remnant: > Fabio should be uploading a fixed mdrun initramfs script after Knot 3 > freeze that at least works around the problem > > ** Changed in: udev (Ubuntu) > Sourcepackagename: udev => mdadm > Assignee: Scott James Remnant => Fabio Massimo Di Nitto After todays update booting by UUID works for straight MD RAID1. Good work! Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Thursday 14 September 2006 16:26 schrieb Scott James Remnant: > Fabio should be uploading a fixed mdrun initramfs script after Knot 3 > freeze that at least works around the problem > > ** Changed in: udev (Ubuntu) > Sourcepackagename: udev => mdadm > Assignee: Scott James Remnant => Fabio Massimo Di Nitto Ok. I'll check it then and let you know. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: LVM/MD root filesystem not found by uuid
Matt, it's true that Linux did and does a lot of things traditional Unices didn't and don't do. But that is neither here nor there and I shouldn't have mentioned this in the first place. I raised my objections regarding mount by UUID and it's up to you guys to check their validity regarding Ubuntu's goals. As for the problem at hand: I am willing to aid in resolving this issue, so if you want me to test something, let me know about it. Regards, Dominik -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: LVM/MD root filesystem not found by uuid
Scott, nobody does mount by UUID. Neither *BSD, Solaris, AIX, HP-UX, Tru64 does it. These Unix derivatives have pretty smart engineering teams around. That should tell you something... As for the valid configurations: Category A (Will probably never work): 1. loopback mounts (eg. crypto root) -> kills secure mobile devices 2. network mounts (eg. nfs root or raid with nbd) -> kills one half of thin client setups 3. layered mounts (eg. unionfs) -> kills the other half of thin client setups and one half of embedded devices 4. tmpfs root -> kills the other half of embedded devices Category B (Probably resolveable but changes expected behaviour) 5. disaster recovery with replicated root file systems (eg. rsync): there the UUIDs of both filesystem have to be different, otherwise they wouldn't be unique -> kills quite common DR strategy and effectively kills the use in corporate server environments 6. bare metal recovery: restore tape backup to newly installed system will result in a unbootable setup because UUID no longer matches... -> a support nightmare, effectively kills the use in corporate desktop environments Category C (Has severe side-effects) 7. systems with SAN/iSCSI storage: udev will scan all devices it sees to determine the UUID. this is likely to take a long time ((I know of hosts with several hundred SAN storage volumes assigned to them) and prone to disrupting the operation of other hosts (since Linux does not honor SCSI reservation)-> this kills the enterprise server setups. -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: [Bug 54002] LVM/MD root filesystem not found by uuid
Am Monday 11 September 2006 21:11 schrieb Scott James Remnant: > > break=mount on the kernel command-line. > Yup. Google already told me about that. Nice. > > 2. update-grub changes MD to mount by UUID even so it does not work at > > the moment. This one is rather easy to fix: > > I'd rather fix #1. and make mount-by-UUID work. I doubt that this is possible for all valid configurations. I could name at least six valid configurations/situations where it will not work out of the box, will not work ever or will have side-effects so severe that it will lead to an immediate ban of all Ubuntu installations by the authorities. But for the problem at hand I think I may have found it. It looks like you have a circular dependency in /scripts/local-top: I did a boot with break=mount, then sourced scripts/functions and executed run_scripts scripts/local-top. Then I checked /dev/disk. There were only directories by-id and by-path, no by-uuid. md depends on udev. So udev will be called first. But it will not create by-UUID entries for RAID components. mdrun has not been executed at this time so it will also not create by-uuid entries for the MD devices. Then md starts the RAID devices but udev already ran so the device links will never be created and the "mount root" step will wait forever for the device files to appear. So I think you will have top put /dev/md* on the exclusion list as well. And that pretty much limits your new booting scheme to desktop systems without fault-tolerance or recovery features. Given the fact that Ubuntu now also targets the Enterprise desktop and server markets I'd have to say: Forget mount by-uuid. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Monday 11 September 2006 00:24 schrieb Matt Zimmerman: > Reopening udev task, as md detection doesn't seem to be sorted yet. > > MD folks, please provide details. > > ** Changed in: udev (Ubuntu) >Status: Fix Released => Confirmed We have two issues at hand: 1. Mounting by UUID does not work for MD in initramfs. I am trying to track this one down (but I think this is a waste of time because there will always be rather common scenarios where mounting by UUID will never work. But this should be discussed elsewhere). I'll have to rig a serial terminal to capture the console output and create a custom initramfs which will drop to a shell right before it attempts to mount the root device so that I can do some debugging. 2. update-grub changes MD to mount by UUID even so it does not work at the moment. This one is rather easy to fix: --- update-grub.orig2006-09-11 20:49:34.0 +0200 +++ update-grub 2006-09-11 20:51:48.0 +0200 @@ -692,6 +692,9 @@ ;; /dev/evms/*) ;; + /dev/md*) # Don't convert MD for now since there is an + # unresolved bug preventing it from working. + ;; /dev/*) if [ -L "$DEV" ] && readlink | grep -q "^/dev/mapper/" then This can be backed-out when mounting by UUID for MD works. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: [Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Sunday 10 September 2006 21:02 schrieb Matt Zimmerman: > On Sun, Sep 10, 2006 at 06:26:50PM -0000, Dominik Kubla wrote: > > # egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub > > 751- > > 752:# Update the root device to mount-by-UUID > > 753-kopt=$(convert_kopt_to_uuid "$kopt") > > You're making assumptions about the behaviour of a 1000+-line program by > reading one comment. No, I am not making assumptions. You stated that grub-update will not convert LVM/devmapper entries anymore to avoid corruption of the system boot process. I demonstrated that the system boot process is still corrupted for the rather simple case of root disks being mirrored with MD. > If you read the convert_kopt_to_uuid function referenced above, you'll see > that it includes conditional code intended to exclude device-mapper (LVM) > and EVMS devices from the conversion. I went through this file line by line and I can say I have a rather good understanding what it attempts to do and what it does. You are the one making assumptions here: about how a system is configured. That is something you can not know reliably. So following the principle of least impact you should not change anything without explicit consent by the system administrator requesting the task. > If you have problems with the conversion, a constructive bug report with > details of your configuration would be appreciated. My problem is that you convert the file at all. I do not want this setting to be converted, even if mounting by UUID would be working. But as I understand now, the problem is not a technical one, so i will simply dpkg-divert /sbin/update-grub and disable the conversion stuff in my local copy and be done with it. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: LVM/MD root filesystem not found by uuid
Matt, I am not trying to be dense or malevolent. I am well aware that Edgy is a development release, etc. But I am also a computer professional who has to deal with incident reports on a daily basis, so I have a quite good understanging of the issues involved. In my opinion the handling of this bug report has not been adequate. Just to demonstrate the facts: # env COLUMNS=120 dpkg -l grub [...] ii grub 0.97-11ubuntu10 GRand Unified Bootloader # egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub 751- 752:# Update the root device to mount-by-UUID 753-kopt=$(convert_kopt_to_uuid "$kopt") # grep -c UUID /boot/grub/menu.lst 0 # /sbin/update-grub Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.17-7-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done # grep -c UUID /boot/grub/menu.lst 3 So as you can see, even your "fixed" version silently corrupts the system. Against the expressed intention of the system owner/administrator who changed the relevant configuration file. Sorry, but this is simply not acceptable. Especially since upstream Debian can detect manual changes of a config file and will not change it. -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] grub-update screws up the system
It's grub-update, which is part of grub. Any time a kernel package is installed/updated, this script is executed. For this reason I disagree with the rejection of this bug report by the grub maintainer! A grub script is changing a working system configuration into a non-working. This is most definitely a bug of the grub package. Now the root cause of this bug might well be in some other package but unless this has been determined _AND_ fixed, please stop converting the boot options. -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
$ ls -l /dev/mapper ls: /dev/mapper: No such file or directory Your making assumptions again... As I said in the earlier message: You simply can't know how a system looks like. So you'd better not change settings that might break it without the expressed consent of the system administrator. Regards, Dominik -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Don't know about LVM, but it certainly does not work with mirrored disks using MD. The system is unable to boot because it can not find the UUID before the MD device has been started. So the system just hangs "waiting for root device..." Silently converting the root device entry is VERY BAD! Even in a development branch: You simply can't know enough about the installation to do it reliably. So simply ask the user if he wants to convert the entry and don't touch the rescue entry unless the user has confirmed that the change worked. udev: 093-0ubuntu7 initramfs-tools: 0.69ubuntu6 Kind regards, Dominik -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47683] Re: ntpd not compiled with debugging support
ntpd must be compiled with debugging support since it is virtually impossible to track down NTP problems without. -- ntpd not compiled with debugging support https://launchpad.net/bugs/47683 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
