[Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
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 doesn't work after suspend" issue again. Right now I've un-commented the i2c_i801 in /etc/modprobe.d/blacklist.conf and I also feel like I had to REadd psmouse.synaptics_intertouch=0 in /etc/default/grub - could that have gotten overwritten on an upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778767] Re: iPhone doesn't charge when plugged in after disconnect
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 systemd[1]: Started Socket daemon for the usbmux
protocol used by Apple devices.
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.047][3] usbmuxd v1.1.0 starting
up
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.050][3] Successfully dropped
privileges to 'usbmux'
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.054][3] Could not get old
configuration descriptor for device 1-7: -5
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Connecting to new
device on location 0x10007 as ID 1
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Initialization complete
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Enabled exit on SIGUSR1
if no devices are attached. Start a new instance with "--exit" to trigger.
Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.063][3] Connected to v2.0
device 1 on location 0x10007 with serial number
a52283aea517ba99dbffee3bbeaee0cc2a244ee2
Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.277][3] Removed device 1 on
location 0x10007
Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.326][3] usbmuxd shutting down
Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.427][3] Shutdown complete
Nov 28 11:06:23 banana systemd[1]: Started Socket daemon for the usbmux
protocol used by Apple devices.
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.757][3] usbmuxd v1.1.0 starting
up
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.759][3] Successfully dropped
privileges to 'usbmux'
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.766][3] Could not get old
configuration descriptor for device 1-8: -5
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Connecting to new
device on location 0x10008 as ID 1
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Initialization complete
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Enabled exit on SIGUSR1
if no devices are attached. Start a new instance with "--exit" to trigger.
Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Connected to v2.0
device 1 on location 0x10008 with serial number
a52283aea517ba99dbffee3bbeaee0cc2a244ee2
}}}
--
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:
iPhone doesn't charge when plugged in after disconnect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778767] Re: iPhone doesn't charge when plugged in after disconnect
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 systemd[1]: Started Socket daemon for the usbmux protocol used by Apple devices. Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.047][3] usbmuxd v1.1.0 starting up Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.050][3] Successfully dropped privileges to 'usbmux' Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.054][3] Could not get old configuration descriptor for device 1-7: -5 Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Connecting to new device on location 0x10007 as ID 1 Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Initialization complete Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.062][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with "--exit" to trigger. Nov 28 11:06:11 banana usbmuxd[6899]: [11:06:11.063][3] Connected to v2.0 device 1 on location 0x10007 with serial number a52283aea517ba99dbffee3bbeaee0cc2a244ee2 Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.277][3] Removed device 1 on location 0x10007 Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.326][3] usbmuxd shutting down Nov 28 11:06:18 banana usbmuxd[6899]: [11:06:18.427][3] Shutdown complete Nov 28 11:06:23 banana systemd[1]: Started Socket daemon for the usbmux protocol used by Apple devices. Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.757][3] usbmuxd v1.1.0 starting up Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.759][3] Successfully dropped privileges to 'usbmux' Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.766][3] Could not get old configuration descriptor for device 1-8: -5 Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Connecting to new device on location 0x10008 as ID 1 Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Initialization complete Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with "--exit" to trigger. Nov 28 11:06:23 banana usbmuxd[7049]: [11:06:23.774][3] Connected to v2.0 device 1 on location 0x10008 with serial number a52283aea517ba99dbffee3bbeaee0cc2a244ee2 ``` -- 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: iPhone doesn't charge when plugged in after disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778767] Re: iPhone doesn't charge when plugged in after disconnect
** 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: iPhone doesn't charge when plugged in after disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778767] [NEW] iPhone doesn't chard when plugged in after disconnect
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: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Patch added: "add +RUN directive to rule" https://bugs.launchpad.net/bugs/1778767/+attachment/5156831/+files/39-usbmuxd.rules -- 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: iPhone doesn't chard when plugged in after disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069849] Re: Containers show expired objects
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 obvious improvement to the expierer was purposed, I think theres some other bugs open that could acctually be implemented, e.g. https://bugs.launchpad.net/bugs/1076202 There was a comment no-one seemed to respond to about 410 or special messaging - I'm guessing that was about the object response for a expired object vs. a deleted one (and has nothing to do with the container listings). I think that's a bad idea - but off topic for this bug, so I'm going to pretend I didn't see it. ** Changed in: swift Status: Confirmed => Invalid ** Changed in: swift (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069849] Re: Containers show expired objects
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 for a container listing being out of sync with the objects? Maybe there's a more general way to deal approach the problem that better jives with "eventual consistency"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968654] Re: can't start target (missing target_core_mod)
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968654 Title: can't start target (missing target_core_mod) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lio-utils/+bug/968654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968654] [NEW] can't start target (missing target_core_mod)
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.com/ubuntu/ precise/universe lio-utils amd64 3.1+git0.91b96103-2 [102 kB] Fetched 102 kB in 0s (104 kB/s) Selecting previously unselected package lio-utils. (Reading database ... 62630 files and directories currently installed.) Unpacking lio-utils (from .../lio-utils_3.1+git0.91b96103-2_amd64.deb) ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Setting up lio-utils (3.1+git0.91b96103-2) ... Loading target_core_mod/ConfigFS core: [FAILED]: 1 invoke-rc.d: initscript target, action "start" failed. dpkg: error processing lio-utils (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: lio-utils E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up lio-utils (3.1+git0.91b96103-2) ... Loading target_core_mod/ConfigFS core: [FAILED]: 1 invoke-rc.d: initscript target, action "start" failed. dpkg: error processing lio-utils (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: lio-utils root@precise:~# service target start Loading target_core_mod/ConfigFS core: [FAILED]: 1 root@precise:~# lsmod | grep target root@precise:~# root@precise:~# cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu precise (development branch)" root@precise:~# aptitude show lio-utils Package: lio-utils New: yes State: partially configured Automatically installed: no Version: 3.1+git0.91b96103-2 Priority: optional Section: universe/python Maintainer: Ubuntu Developers Uncompressed Size: 589 k Depends: python2.7, python (>= 2.7.1-0ubuntu2), python (< 2.8), libc6 (>= 2.7) Conflicts: lio-utils Description: configuration tool for LIO core target lio-utils provide a simple low-level configuration tool set for LIO Linux SCSI Target. This includes the target and its backstores including tcm_loop, and the iSCSI, FCoE and Fibre Channel fabric modules. Homepage: http://www.risingtidesystems.com/git/?p=lio-utils.git;a=summary ** Affects: lio-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968654 Title: can't start target (missing target_core_mod) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lio-utils/+bug/968654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672759] Re: open-iscsi duplicates exsiting block device on initiator login
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 will mount the first target onto /dev/sdb instead of conflicting. More information regarding the resolution in nattry: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/684875 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/672759 Title: open-iscsi duplicates exsiting block device on initiator login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/672759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672759] Re: open-iscsi duplicates exsiting block device on initiator login
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 --query=all --name=/dev/sda P: /devices/vbd-51712/block/sda N: sda S: block/202:0 S: disk/by-path/xen-vbd-51712 E: UDEV_LOG=3 E: DEVPATH=/devices/vbd-51712/block/sda E: SUBSYSTEM=block E: DEVNAME=sda E: ID_PATH=xen-vbd-51712 E: ID_PART_TABLE_TYPE=dos E: MAJOR=202 E: MINOR=0 E: DEVTYPE=disk E: DEVLINKS=/dev/block/202:0 /dev/disk/by-path/xen-vbd-51712 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/672759 Title: open-iscsi duplicates exsiting block device on initiator login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/672759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605567] Re: Extremely slow painting of launchpad.net bug details page with nvidia driver
*** 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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605567 Title: Extremely slow painting of launchpad.net bug details page with nvidia driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395167] Re: Please backport firefox-3.5
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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
