After a reboot applied an automatic system update I applied today to my
18.04.3 LTS IBM ThinkPad X1 Carbon my mouse wasn't working!
Some comments in scripts I'd left around helped me found my way back to
this bug and ...
modprobe -r i2c-i801
... fixed the immediate issue.
But I saw the "scroll
new package works great
{{{
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.494][3] Removed device 1 on
location 0x10006
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.534][3] usbmuxd shutting down
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.635][3] Shutdown complete
Nov 28 11:06:11 banana s
new package works great!
```
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.494][3] Removed device 1 on
location 0x10006
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.534][3] usbmuxd shutting down
Nov 28 11:06:04 banana usbmuxd[6612]: [11:06:04.635][3] Shutdown complete
Nov 28 11:06:11 banana
** Summary changed:
- iPhone doesn't chard when plugged in after disconnect
+ iPhone doesn't charge when plugged in after disconnect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778767
Title:
iPh
Public bug reported:
Plugging in the iPhone via usb will charge the iPhone after reboot, but
after disconnect usbmuxd's systemctl service is inactive and does not
start.
Problem and workaround documented here:
https://ubuntuforums.org/showthread.php?t=2376741&p=13779062#post13779062
** Affects:
nope, nope, nope - this is expected behavior.
Clients must reconcile with "objects in the listing may 404" i.e. object
listing is out of date - this is a basic tenant of the systems choice to
favor availability over consistency.
We can reduce the inaccuracies where possible, but in this case no
o
I really don't see why expired objects are such a special case that they
need to be solved? Anytime you iterate over a listing of objects from a
container there is a chance that one of those objects may 404 for a
number of reasons.
Is there an application level problem that simply can't account f
seems to be because I was running it on a vm
root@precise:~# uname -a
Linux precise 3.2.0-20-virtual #33-Ubuntu SMP Tue Mar 27 17:02:08 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
Works "ok" on a physical box (3.2.0-18-generic)
--
You received this bug notification because you are a member of Ubun
Public bug reported:
root@precise:~# aptitude install lio-utils
The following NEW packages will be installed:
lio-utils
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 102 kB of archives. After unpacking 589 kB will be used.
Get: 1 http://us.archive.ubuntu.co
I was mistaken, I'm only seeing this problem on maverick. FWIW running
lucid or natty on domU moves the first hd to /dev/xvda and iscsi works
just fine.
Also if I boot my maverick domU via HVM-boot-policy="BIOS order" instead
of pygrub, the first hd still goes to /dev/sda - but iscsi initiator
wi
I've run into the same issue with a lucid guest running on XCP.
Everything I can find says that the first block device *should* be xvda,
but mine is sda, and that causes the open-iscsi to sysfs error.
Is there a way to force xen or this udev to move the block device out of
the way?
# udevadm info
*** This bug is a duplicate of bug 223238 ***
https://bugs.launchpad.net/bugs/223238
This bug is much more recent than bug #223238 and describes my problem
more accurately. The only way I could get the problem to go away was to
uninstall the nvidia restricted driver.
--
You received this bu
Now that firefox-3.5 is stable and released in Karmic - would it be less
"risky" to add to hardy-backports?
--
Please backport firefox-3.5
https://bugs.launchpad.net/bugs/395167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
13 matches
Mail list logo
