I also see this behaviour. I use Metacity for my login session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630033
Title:
Logout always asks about rebooting to finish installing updates
To
And just for the record I'll add that in the week or so since I
installed the package from the -proposed repository I have had no
recurrence of either of the two symptoms (wrong window displayed on top,
all windows displayed behind desktop background) that I had previously
been encountering every
I have now installed the package from the -proposed repository. I was
suffering the effects of the bug every day or two (and did not know what
particular sequence of actions by me was triggering it), so I'll need a
week or more to become reasonably confident that the bug is no longer
affecting
I've pinned down the origin of the bug: the information being provided
by udev to usb_modeswitch is not what usb_modeswitch is expecting. If
my understanding of the udev documentation is correct, then there must
be a bug in udev that is causing it to perform its %b substitution
incorrectly. Only
I had decided that the next thing to do was to try to get debug output
from usb_modeswitch. In my efforts to find out how to do this I came
across
http://www.draisberghof.de/usb_modeswitch/#trouble
which includes a couple of notes about devices with ID 19d2:2000. The
K3520-Z is one such
I tried blacklisting the usb_storage module (as suggested by
http://www.draisberghof.de/usb_modeswitch/#trouble) to see if this bug
is caused by that kernel module. Unfortunately I then trip over this
bug:
https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/1035739
which means that
I've now ruled out kernel module usb_storage as the cause of the problem
and have found that usb_modeswitch is failing to read device information
even though lsusb shows me that the relevant information is available.
I'm not familiar with device naming, but I can't see how
I've now done a lot more investigating and I'm pretty sure this is a
problem in usb_modeswitch. If I knew how to modify this bug report to
point the finger at usb_modeswitch rather than network-manager I would
do so, but I can't see an obvious way to do so. Perhaps someone more
familiar with
The attached file is an extract from syslog that includes debug output
from udev when the K3520-Z is connected to the system.
udev finds a matching entry in /lib/udev/rules.d/40-usb_modeswitch.rules
at line 565. That line is
ATTRS{idVendor}==19d2, ATTRS{idProduct}==2000, RUN+=usb_modeswitch
The attached file is an extract from syslog that includes debug output
from udev when I manually use usb_modeswitch to switch the K3520-Z's
mode, i.e. when I issue the command
usb_modeswitch --default-vendor 0x19d2 --default-product 0x2000
--message-content
The attached file is an extract from syslog that includes debug output
from udev when the K3770 is connected to the system.
Note that /lib/udev/rules.d/40-usb_modeswitch.rules line 397 is
ATTRS{idVendor}==12d1, ATTRS{idProduct}==14d1, RUN+=usb_modeswitch
'%b/%k'
This is the line that one would
Having established that usb_modeswitch wasn't switching the K3520-Z's
mode when invoked by udev to do so, and suspecting
usb_modeswitch_dispatcher was to blame, I decided to write my own udev
rules file (/etc/udev/rules.d/kludge_k3520z.rules) so as to bypass
usb_modeswitch_dispatcher. It is
Attached is /lib/udev/kludge_k3520z.
** Attachment added: /lib/udev/kludge_k3520z to be invoked by udev after rule
hit in kludge_k3520z.rules
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1175093/+attachment/3671294/+files/kludge_k3520z
--
You received this bug
Having done some further investigation, I believe this is a udev issue,
not a network manager issue.
Having issued the command
udevadm control --log-priority=debug
I then inserted first the K3770 and then the K3520-Z. I've subsequently been
looking at the very copious debug output from udev
Public bug reported:
Ubuntu 12.04.2 LTS
Although I have logged this as a network-manager problem, it could well
turn out to be an issue with usb-modeswitch (usb-modeswitch
1.2.3+repack0-1ubuntu2) or usb-modeswitch-data (usb-modeswitch-data
20120120-0ubuntu1).
Expected behaviour (and what
15 matches
Mail list logo
