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 ex
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 man
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:/
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 "/
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 (
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://lis
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
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
+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 t
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
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 -
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-
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 r
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
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-Tensio
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 ke
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 ke
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
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
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-2
** 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.
** 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 su
** 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 Ubun
** 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
** 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 Ubun
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 expecte
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
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
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-20
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
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.
There
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" wh
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 b
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
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/19157
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
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:
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:
bLeng
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
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
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 Ubunt
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) -
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
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 no
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
> > 7
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 bu
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 defin
$ 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.
Regar
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
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
50 matches
Mail list logo
