Apparently, I can define a custom "Launch Terminal" shortcut launching
gnome-terminal that does work (with the same key combination that's not
working for the original "Launch Terminal" shortcut). But I still can't
get around the not working window resizing shortcuts.
--
You received this bug not
** Project changed: gnome-shell => ubuntu
** Description changed:
After I updated packages a couple days ago some of my keyboard shortcuts
stopped working. "Launch Terminal" and "Maximize window
horizontally/vertically", for example, don't work anymore, no matter
what key combination I as
Thanks Pedro, disabling the mtp plugin immediately makes the mouse work
correctly again.
And yes - it's a case of an old Mighty Mouse so it seems related to
#559892, indeed.
--
Launching Rhythmbox disables external usb mouse
https://bugs.launchpad.net/bugs/663098
You received this bug notificati
** Description changed:
Binary package hint: rhythmbox
"Launched Rhythmbox for the first time after installing Ubuntu on this
machine. Can't move the cursor with my external usb mouse. Oh, wait, but
the touchpad works. Hmm, let's replug the mouse. Nope. Quit Rhythmbox -
yay, the exter
--
Launching Rhythmbox disables external usb mouse
https://bugs.launchpad.net/bugs/663098
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/listinf
Public bug reported:
Binary package hint: rhythmbox
"Launched Rhythmbox for the first time after installing Ubuntu on this
machine. Can't move the cursor with my external usb mouse. Oh, wait, but
the touchpad works. Hmm, let's replug the mouse. Nope. Quit Rhythmbox -
yay, the external mouse works
Since installing Karmic yesterday morning, happened twice for me, both
times on resume from a longerish suspend. On one shorter, ~2 minutes,
test suspend it didn't happen, though.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x80/0x90()
https://bug
The indicated error in the jockey- seems to be caused by
jockey-backend script not finishing it's initialization stage, thus
doesn't respond to frontend requests.
The jockey-backend script appears to be hanging in
jockey.detection._get_printers(), while waiting on
cups.Connection().getDevices(). I
The code doesn't expect the new_nl_handle() to fail and tries to do
wrong things with a null pointer. SIGSEGV occurs, code handles _that_
and retries the operation. Infinite loop ensues.
It seems the code is different on trunk, but the attached patch against
the 0.6.5-0ubuntu16.7.10.0 package's so
