*** This bug is a duplicate of bug 1033727 ***
https://bugs.launchpad.net/bugs/1033727
Bug #1033727 is specifically about qemu-kvm 1.2.0 and higher, see
comment #8 on that bug for example. This bug is about earlier versions,
including the version in 12.04 LTS.
--
You received this bug
I don't recall saying there was a duplicate of this bug? I merely
objected to #1033727 being marked a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/685096
Title:
USB
Issue got fixed for me after applying recent updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764330
Title:
Move window annoying slow with compiz
To manage notifications about this bug go
Seeing this right now, all oneiric updates applied. Regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845325
Title:
Wallpaper shows through 1px line above panel
To manage notifications
I think this happens because the lvm2 commands are called from inside
udev, while lvm itself also waits for udev to complete. This creates an
obvious deadlock.
/lib/udev/rules.d/85-lvm2.rules should be changed to read:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==lvm*|LVM*, \
I think this happens because the lvm2 commands are called from inside
udev, while lvm itself also waits for udev to complete. This creates an
obvious deadlock.
/lib/udev/rules.d/85-lvm2.rules should be changed to read:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==lvm*|LVM*, \
What I'm seeing is a vgchange process that hangs until udev kills it.
When it is killed it has only initialized a few LV's and most symlinks
in /dev/vgname are missing. Perhaps this is a different bug, but the
symptoms are exactly those from the original bug report.
Also, I'm not preventing
I was a little overzealous with the application of --noudevsync there,
only vgchange accepts that.
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==lvm*|LVM*, \
RUN+=watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange --noudevsync -a y'
--
You received this bug notification because you
I was a little overzealous with the application of --noudevsync btw,
only vgchange accepts that option. Proper version:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==lvm*|LVM*, \
RUN+=watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange --noudevsync -a y'
--
You received this bug
vgchange will create the device mapper table entries before exiting, so
that part should be taken care of. After it's finished, udev will create
the device nodes and symlinks as it gets the information about the new
dm nodes from the kernel.
From the vgchange manpage:
--noudevsync
Regenerating the initrd fixed it for me:
update-initramfs -k all -u
hth hand
--
/dev/shm isn't writable, causing problems with glibc 2.2+ apps such as chromium
https://bugs.launchpad.net/bugs/566788
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The answer seems to be to work *with* powermizer, not against it. :)
Option RegistryDwordsPowerMizerEnable=0x1;
PerfLevelSrc=0x; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1
This enables it and tells it to use one speed only. The default values
tell it what speed
Pasted from #444563, which actually does seem to be the same bug:
I think I got it. In /lib/udev/rules.d/65-dmsetup.rules there's this
line:
ENV{DM_UUID}==LVM-*, PROGRAM=/bin/sh -c 'set `lvm lvdisplay -C -o
vg_name,lv_name --noheadings /dev/$name` ; echo $1/$2',
SYMLINK+=$result
which is a
You can create a file /etc/udev/rules.d/65-dmsetup.rules, which will
override the file in /lib/udev/rules.d/.
In lucid this seems to be handled completely differently (and much
better imho):
From /lib/udev/rules.d/56-lvm.rules:
# Use DM name and split it up into its VG/LV/layer constituents.
So, it looks like usb-storage wants to have the device from t+1 until
1+11 (counting from the moment of insertion). usb_modeswitch wants to
detach usb-storage at t+1 (exact numbers differ per chipset,
apparently). This looks like a race condition, caused by various parties
coding in arbitrary
I should note that I do not see any xHCI errors. There's simply nothing
happening, most notably the modeswitch. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979697
Title:
Modeswitching modem
Public bug reported:
Hi,
The pidgin wrapper script has an unnecessary dependency on bash and
can't handle arguments with spaces. Attached is a version that doesn't
have these problems.
cheers,
** Affects: account-plugins (Ubuntu)
Importance: Undecided
Status: New
** Attachment
*** This bug is a duplicate of bug 1033727 ***
https://bugs.launchpad.net/bugs/1033727
Bug #1033727 is specifically about qemu-kvm 1.2.0 and higher, see
comment #8 on that bug for example. This bug is about earlier versions,
including the version in 12.04 LTS.
--
You received this bug
Tried 1.0+noroms-0ubuntu14 from -proposed and (as far as the locking
goes) it works exactly as wished/expected/before. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023159
Title:
Locking
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023159
Title:
Locking fails
To manage notifications about this bug go to:
I don't recall saying there was a duplicate of this bug? I merely
objected to #1033727 being marked a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685096
Title:
USB Passthrough not
All right, I extracted the file 12d1:1446 from configPack.tar.gz, put it in
/etc/usb_modeswitch.d and added the line ReleaseDelay=3000. There was no
difference in the result. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually delay_use=2 is more than enough to fix things for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979697
Title:
Modeswitching modem not working with some USB 3.0 host controllers
To
Public bug reported:
The version of qemu-kvm that's in Precise fails to lock the pidfile like
it did in all previous versions, possibly leading to data corruption as
it might run twice on the same disk images (depending on the
configuration).
Upstream has already fixed this bug in
** Patch added: Upstreams patch that solves the issue
https://bugs.launchpad.net/bugs/1023159/+attachment/3218970/+files/qemu.git-93dd748b789202af4f5be75412c58ee1ed481b29.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue on an Asus UX21A (should be very similar to
Cristophes UX31A). These laptops have Intel Panther Point USB
controllers. So I doubt whether the problem is restricted to NEC
uPD720200 controllers.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Based on Christophe's post I modified /lib/udev/usb_modeswitch to wait
for a number of seconds before running the modeswitch_dispatcher. Some
experimenting determined the minimum number of seconds to be 11. My
modem is now detected and switched automatically, even if I have to wait
a few seconds
Could well be. Try increasing the delay to 30 though. If that doesn't
help, we might be experiencing different problems with the same result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979697
28 matches
Mail list logo
