[Bug 1948498] Re: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Seems to be fixed with linux-image-5.13.0-39-generic ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Seems fixed in linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Seems like it is fixed in kernel 5.14: https://gitlab.freedesktop.org/drm/amd/-/issues/1783 Any chance to get the fix backported to 20.04? ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1783 https://gitlab.freedesktop.org/drm/amd/-/issues/1783 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Problem can be reproduced with 5.13.0-28.31~20.04.1 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
** Summary changed: - After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking + After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
According to my logs in the past few days, these versions have worked fine: 5.10.0-1045.47-oem 5.11.0-37.41~20.04.2-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
** Attachment added: "IMG_20220120_073821207.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+attachment/771/+files/IMG_20220120_073821207.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] [NEW] After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
Public bug reported: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948498] [NEW] Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Public bug reported: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926790] [NEW] Gnome Network Manager crashes when trying to delete VPN config of a deleted plugin
Public bug reported: To reproduce: - sudo apt install network-manager-vpnc-gnome - Create and save a vpnc profile - sudo apt remove --purge network-manager-vpnc-gnome - Try to delete the created vpnc profile Expected: Profile can be deleted Actual result: Network Manager crashes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 30 17:55:39 2021 InstallationDate: Installed on 2020-09-24 (218 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926790 Title: Gnome Network Manager crashes when trying to delete VPN config of a deleted plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1926790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] Re: ExFAT Formatted SD Cards not mounted
This bug outlived my Zenbook and I reformatted all my exFAT SD cards to FAT32 in the meantime to be able to use them, so I can't help anymore. Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
alias remove-old-kernels='dpkg -l linux-{image,headers}-* | awk
'\''/^ii/{print }'\'' | egrep '\''[0-9]+\.[0-9]+\.[0-9]+'\'' | grep -v
4.4.0-79 | xargs sudo apt-get -y purge'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
Kernels not autoremoving, causing out of space error on LVM or
Encrypted installation or on any installation, when /boot partition
gets full
To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705813] Re: systemd upgrade to 229-4ubuntu19 fails
I even can't reboot the system: $ sudo reboot [sudo] password for sebastian: Failed to start reboot.target: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status reboot.target' for details. Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705813 Title: systemd upgrade to 229-4ubuntu19 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705813] [NEW] systemd upgrade to 229-4ubuntu19 fails
Public bug reported: systemd upgrade to 229-4ubuntu19 fails: Calculating upgrade... Done The following packages will be upgraded: libmysqlclient20 libnss-myhostname libpam-systemd libsystemd0 libudev1 mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server mysql-server-5.7 mysql-server-core-5.7 systemd systemd-sysv udev 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 23.8 MB of archives. After this operation, 106 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd-sysv amd64 229-4ubuntu19 [12.4 kB] Get:2 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libpam-systemd amd64 229-4ubuntu19 [115 kB] Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libsystemd0 amd64 229-4ubuntu19 [205 kB] Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libnss-myhostname amd64 229-4ubuntu19 [36.4 kB] Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu19 [3,811 kB] Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu19 [992 kB] Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu19 [55.0 kB] Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [6,020 kB] Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-common all 5.7.19-0ubuntu0.16.04.1 [15.7 kB] Get:10 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-client-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [1,654 kB] Get:11 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [2,463 kB] Get:12 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [7,588 kB] Get:13 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libmysqlclient20 amd64 5.7.19-0ubuntu0.16.04.1 [809 kB] Get:14 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 mysql-server all 5.7.19-0ubuntu0.16.04.1 [10.8 kB] Fetched 23.8 MB in 0s (32.4 MB/s) Preconfiguring packages ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu19_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu19) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu19_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../libsystemd0_229-4ubuntu19_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Setting up libsystemd0:amd64 (229-4ubuntu19) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... (Reading database ... 112119 files and directories currently installed.) Preparing to unpack .../libnss-myhostname_229-4ubuntu19_amd64.deb ... Unpacking libnss-myhostname:amd64 (229-4ubuntu19) over (229-4ubuntu17) ... Preparing to unpack .../systemd_229-4ubuntu19_amd64.deb ... Unpacking systemd (229-4ubuntu19) over (229-4ubuntu17) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu19) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Broadcast message from systemd-journ...@web01.fra.de.nohn.net (Sat 2017-07-22 09:07:52 UTC): systemd[1]: Freezing execution. Failed to try-restart systemd-networkd.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-resolved.service' for details. Failed to try-restart systemd-timesyncd.service: Failed to activate service 'org.freedesktop.systemd1': timed out See system logs and 'systemctl status systemd-timesyncd.service' for details. Failed to retrieve unit: Failed to activate service 'org.freedesktop.systemd1': timed out (Reading database ... 112121 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu19_amd64.deb ... Unpacking udev (229-4ubuntu19) over (229-4ubuntu17) ... Failed to execute operation: Failed to activate service 'org.freedesktop.systemd1': timed out Preparing to unpack .../libudev1_229-4ubuntu19_amd64.deb ... Unpacking libudev1:amd64 (229-4ubuntu19) over (229-4ubuntu17)
[Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
dpkg -l linux-{image,headers}-* | awk '/^ii/{print $2}' | egrep
'[0-9]+\.[0-9]+\.[0-9]+' | grep -v $(uname -r | cut -d- -f-2) | xargs
sudo apt-get -y purge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798414
Title:
update-initramfs should produce a more helpful error message when
there isn't enough free space
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578296] Re: check_memory broken with new /usr/bin/free output
Some information, how we can get this approved and pushed to the official 16.04 repos would be great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578296 Title: check_memory broken with new /usr/bin/free output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-contrib/+bug/1578296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] Re: ExFAT Formatted SD Cards not mounted
Yes, both are installed: $ dpkg -l | grep exfat ii exfat-fuse 1.2.3-1 amd64read and write exFAT driver for FUSE ii exfat-utils 1.2.3-1 amd64utilities to create, check, label and dump exFAT filesystem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] Re: ExFAT Formatted SD Cards not mounted
Seems like it's just an issue of "have you tried turning it off and on again": Nov 30 08:54:25 bnasws02 kernel: [17446.546905] usb 1-8: new high-speed USB device number 6 using xhci_hcd Nov 30 08:54:25 bnasws02 kernel: [17446.689489] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 30 08:54:25 bnasws02 kernel: [17446.689491] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 30 08:54:25 bnasws02 kernel: [17446.689492] usb 1-8: Product: Flash Card Reader/Writer Nov 30 08:54:25 bnasws02 kernel: [17446.689493] usb 1-8: Manufacturer: Generic Nov 30 08:54:25 bnasws02 kernel: [17446.689494] usb 1-8: SerialNumber: 058F63666485 Nov 30 08:54:25 bnasws02 kernel: [17446.689936] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 30 08:54:25 bnasws02 kernel: [17446.690043] scsi host4: usb-storage 1-8:1.0 Nov 30 08:54:25 bnasws02 mtp-probe: checking bus 1, device 6: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 30 08:54:25 bnasws02 mtp-probe: bus: 1, device: 6 was not an MTP device Nov 30 08:54:26 bnasws02 kernel: [17447.720553] scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 30 08:54:26 bnasws02 kernel: [17447.721271] sd 4:0:0:0: Attached scsi generic sg1 type 0 Nov 30 08:54:29 bnasws02 kernel: [17450.797969] sd 4:0:0:0: [sdb] Attached SCSI removable disk Nov 30 08:55:16 bnasws02 kernel: [17497.700513] usb 1-8: USB disconnect, device number 6 Nov 30 08:55:23 bnasws02 kernel: [17504.230075] usb 1-8: new high-speed USB device number 7 using xhci_hcd Nov 30 08:55:23 bnasws02 kernel: [17504.372672] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 30 08:55:23 bnasws02 kernel: [17504.372674] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 30 08:55:23 bnasws02 kernel: [17504.372676] usb 1-8: Product: Flash Card Reader/Writer Nov 30 08:55:23 bnasws02 kernel: [17504.372677] usb 1-8: Manufacturer: Generic Nov 30 08:55:23 bnasws02 kernel: [17504.372678] usb 1-8: SerialNumber: 058F63666485 Nov 30 08:55:23 bnasws02 kernel: [17504.373161] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 30 08:55:23 bnasws02 kernel: [17504.373266] scsi host4: usb-storage 1-8:1.0 Nov 30 08:55:23 bnasws02 mtp-probe: checking bus 1, device 7: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 30 08:55:23 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device Nov 30 08:55:24 bnasws02 kernel: [17505.387726] scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 30 08:55:24 bnasws02 kernel: [17505.388397] sd 4:0:0:0: Attached scsi generic sg1 type 0 Nov 30 08:55:24 bnasws02 kernel: [17505.848103] sd 4:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB) Nov 30 08:55:24 bnasws02 kernel: [17505.850019] sd 4:0:0:0: [sdb] Write Protect is off Nov 30 08:55:24 bnasws02 kernel: [17505.850021] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00 Nov 30 08:55:24 bnasws02 kernel: [17505.851955] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA Nov 30 08:55:24 bnasws02 kernel: [17505.870801] sdb: sdb1 Nov 30 08:55:24 bnasws02 kernel: [17505.875682] sd 4:0:0:0: [sdb] Attached SCSI removable disk Nov 30 08:55:24 bnasws02 mount.exfat: volume was not unmounted cleanly Nov 30 08:55:24 bnasws02 udisksd[1908]: Mounted /dev/sdb1 at /media/sebastian/497A-63F4 on behalf of uid 1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] Re: ExFAT Formatted SD Cards not mounted
OK, so reboot and try again: sebastian@bnasws02[0r/0s]:~ $ uptime 19:42:56 up 1 min, 1 user, load average: 1.50, 0.67, 0.25 sebastian@bnasws02[0r/0s]:~ $ uname -a Linux bnasws02 4.9.0-040900rc7-generic #201611271731 SMP Sun Nov 27 22:33:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux sebastian@bnasws02[0r/0s]:~ $ tail -f /var/log/syslog -n 0 Nov 29 19:43:13 bnasws02 kernel: [ 100.426823] usb 1-8: new high-speed USB device number 4 using xhci_hcd Nov 29 19:43:13 bnasws02 kernel: [ 100.569331] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 29 19:43:13 bnasws02 kernel: [ 100.569333] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 29 19:43:13 bnasws02 kernel: [ 100.569334] usb 1-8: Product: Flash Card Reader/Writer Nov 29 19:43:13 bnasws02 kernel: [ 100.569335] usb 1-8: Manufacturer: Generic Nov 29 19:43:13 bnasws02 kernel: [ 100.569336] usb 1-8: SerialNumber: 058F63666485 Nov 29 19:43:13 bnasws02 mtp-probe: checking bus 1, device 4: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 29 19:43:13 bnasws02 mtp-probe: bus: 1, device: 4 was not an MTP device Nov 29 19:43:13 bnasws02 kernel: [ 100.587751] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 29 19:43:13 bnasws02 kernel: [ 100.587857] scsi host4: usb-storage 1-8:1.0 Nov 29 19:43:13 bnasws02 kernel: [ 100.587975] usbcore: registered new interface driver usb-storage Nov 29 19:43:13 bnasws02 kernel: [ 100.589481] usbcore: registered new interface driver uas Nov 29 19:43:14 bnasws02 kernel: [ 101.596480] scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 29 19:43:14 bnasws02 kernel: [ 101.597113] sd 4:0:0:0: Attached scsi generic sg1 type 0 Nov 29 19:43:17 bnasws02 gnome-session[2011]: (gnome-software:2163): Gs-WARNING **: failed to get updates: no results to show Nov 29 19:43:17 bnasws02 kernel: [ 104.671058] sd 4:0:0:0: [sdb] Attached SCSI removable disk Nov 29 19:43:19 bnasws02 systemd[1]: powerd.service: Start operation timed out. Terminating. Nov 29 19:43:19 bnasws02 powerd[866]: SIGTERM recieved, cleaning up => Does not work. So adding kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] Re: ExFAT Formatted SD Cards not mounted
Yes, it worked in the past on 14.04. After installing upstream 4.9.0-040900rc7-generic it also works right after rebooting the machine: sebastian@bnasws02[0r/0s]:~ $ uname -a Linux bnasws02 4.9.0-040900rc7-generic #201611271731 SMP Sun Nov 27 22:33:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux sebastian@bnasws02[0r/0s]:~ $ tail -f -n 0 /var/log/syslog Nov 29 19:27:36 bnasws02 kernel: [ 144.317915] usb 1-8: new high-speed USB device number 4 using xhci_hcd Nov 29 19:27:36 bnasws02 kernel: [ 144.460527] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 29 19:27:36 bnasws02 kernel: [ 144.460529] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 29 19:27:36 bnasws02 kernel: [ 144.460531] usb 1-8: Product: Flash Card Reader/Writer Nov 29 19:27:36 bnasws02 kernel: [ 144.460532] usb 1-8: Manufacturer: Generic Nov 29 19:27:36 bnasws02 kernel: [ 144.460532] usb 1-8: SerialNumber: 058F63666485 Nov 29 19:27:36 bnasws02 mtp-probe: checking bus 1, device 4: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 29 19:27:36 bnasws02 mtp-probe: bus: 1, device: 4 was not an MTP device Nov 29 19:27:36 bnasws02 kernel: [ 144.481613] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 29 19:27:36 bnasws02 kernel: [ 144.481754] scsi host4: usb-storage 1-8:1.0 Nov 29 19:27:36 bnasws02 kernel: [ 144.481897] usbcore: registered new interface driver usb-storage Nov 29 19:27:36 bnasws02 kernel: [ 144.483526] usbcore: registered new interface driver uas Nov 29 19:27:37 bnasws02 kernel: [ 145.499448] scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 29 19:27:37 bnasws02 kernel: [ 145.500151] sd 4:0:0:0: Attached scsi generic sg1 type 0 Nov 29 19:27:38 bnasws02 kernel: [ 145.957000] sd 4:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB) Nov 29 19:27:38 bnasws02 kernel: [ 145.958944] sd 4:0:0:0: [sdb] Write Protect is off Nov 29 19:27:38 bnasws02 kernel: [ 145.958946] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00 Nov 29 19:27:38 bnasws02 kernel: [ 145.960815] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA Nov 29 19:27:38 bnasws02 kernel: [ 145.979677] sdb: sdb1 Nov 29 19:27:38 bnasws02 kernel: [ 145.984603] sd 4:0:0:0: [sdb] Attached SCSI removable disk Nov 29 19:27:38 bnasws02 udisksd[1929]: Mounted /dev/sdb1 at /media/sebastian/497A-63F4 on behalf of uid 1000 but after unplugging: ... Nov 29 19:40:02 bnasws02 kernel: [ 890.109441] usb 1-8: USB disconnect, device number 4 and replugging it's again: Nov 29 19:40:07 bnasws02 kernel: [ 894.938520] usb 1-8: new high-speed USB device number 5 using xhci_hcd Nov 29 19:40:07 bnasws02 kernel: [ 895.081014] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 29 19:40:07 bnasws02 kernel: [ 895.081016] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 29 19:40:07 bnasws02 kernel: [ 895.081017] usb 1-8: Product: Flash Card Reader/Writer Nov 29 19:40:07 bnasws02 kernel: [ 895.081018] usb 1-8: Manufacturer: Generic Nov 29 19:40:07 bnasws02 kernel: [ 895.081019] usb 1-8: SerialNumber: 058F63666485 Nov 29 19:40:07 bnasws02 kernel: [ 895.081510] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 29 19:40:07 bnasws02 kernel: [ 895.081636] scsi host4: usb-storage 1-8:1.0 Nov 29 19:40:07 bnasws02 mtp-probe: checking bus 1, device 5: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 29 19:40:07 bnasws02 mtp-probe: bus: 1, device: 5 was not an MTP device Nov 29 19:40:08 bnasws02 kernel: [ 896.092014] scsi 4:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 29 19:40:08 bnasws02 kernel: [ 896.092401] sd 4:0:0:0: Attached scsi generic sg1 type 0 Nov 29 19:40:11 bnasws02 gnome-session[2034]: (gnome-software:2174): Gs-WARNING **: failed to get updates: no results to show Nov 29 19:40:11 bnasws02 kernel: [ 899.145541] sd 4:0:0:0: [sdb] Attached SCSI removable disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366478] Re: 058f:6377 Alcor Micro Corp. Multimedia Card Reader don't work in Ubuntu 9.04/9.10
See #1644981 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366478 Title: 058f:6377 Alcor Micro Corp. Multimedia Card Reader don't work in Ubuntu 9.04/9.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/366478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644981] [NEW] ExFAT Formatted SD Cards not mounted
Public bug reported: ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards work perfectly on 12.04, 14.04 and Windows. Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB device number 7 using xhci_hcd Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card Reader/Writer Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 058F63666485 Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass Storage device detected Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 1-8:1.0 Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi generic sg1 type 0 Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached SCSI removable disk ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.47.50 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sebastian 2240 F pulseaudio /dev/snd/controlC1: sebastian 2240 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 26 11:22:03 2016 HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7 InstallationDate: Installed on 2015-08-06 (477 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago) dmi.bios.date: 07/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644981 Title: ExFAT Formatted SD Cards not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
As a workaround, add blacklist acpi_als to /etc/modprobe.d/blacklist.conf >From what I read, this auto brightness "feature" sucks anyway, so this may be the best whether you are affected by this bug or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
Does not look like this is fixed. I just upgraded from 14.04 to 16.04.1 and my syslog gets spammed with Nov 21 14:36:09 bnasws02 gnome-session[1536]: Error executing command as another user: Not authorized Nov 21 14:36:09 bnasws02 gnome-session[1536]: This incident has been reported. Nov 21 14:36:10 bnasws02 gnome-session[1536]: Error executing command as another user: Not authorized Nov 21 14:36:10 bnasws02 gnome-session[1536]: This incident has been reported. Nov 21 14:36:22 bnasws02 gnome-session[1536]: Error executing command as another user: Not authorized Nov 21 14:36:22 bnasws02 gnome-session[1536]: This incident has been reported. Nov 21 14:36:23 bnasws02 gnome-session[1536]: Error executing command as another user: Not authorized Nov 21 14:36:23 bnasws02 gnome-session[1536]: This incident has been reported. Nov 21 14:36:31 bnasws02 gnome-session[1536]: Error executing command as another user: Not authorized Nov 21 14:36:31 bnasws02 gnome-session[1536]: This incident has been reported. my auth.log with: Nov 21 14:36:43 bnasws02 pkexec[24666]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] Nov 21 14:36:43 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Nov 21 14:36:43 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session Nov 21 14:36:43 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Nov 21 14:36:43 bnasws02 pkexec[24667]: sebastian: Executing command [USER=root] [TTY=unknown] [CWD=/home/sebastian] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] Nov 21 14:36:47 bnasws02 pkexec[24675]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] Nov 21 14:36:47 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Nov 21 14:36:47 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session Nov 21 14:36:47 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Nov 21 14:36:47 bnasws02 pkexec[24676]: sebastian: Executing command [USER=root] [TTY=unknown] [CWD=/home/sebastian] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] Nov 21 14:36:50 bnasws02 pkexec[24685]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] Nov 21 14:36:50 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Nov 21 14:36:50 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session Nov 21 14:36:50 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Nov 21 14:36:50 bnasws02 pkexec[24686]: sebastian: Executing command [USER=root] [TTY=unknown] [CWD=/home/sebastian] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 927] ** Changed in: gnome-settings-daemon (Ubuntu Xenial) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626987] Re: openssl update may have broken puppet cert sign
See #1626883 ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released ** Changed in: puppet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626987 Title: openssl update may have broken puppet cert sign To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626987] Re: openssl update may have broken puppet cert sign
** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626987 Title: openssl update may have broken puppet cert sign To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614362] Re: SD Card not mounted
Same wroblem with 4.4.0-34-generic #53~14.04.1-Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614362 Title: SD Card not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1614362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614362] [NEW] SD Card not mounted
Public bug reported: Since a few days, my SD Card doesn't get mounted anymore on my Ubuntu 14.04 LTS machine. It works fine on my 12.04 LTS machine and can also be mounted on any Windows machine. Syslog output: Aug 18 06:42:29 bnasws02 kernel: [65330.017144] usb 1-8: new high-speed USB device number 13 using xhci_hcd Aug 18 06:42:30 bnasws02 kernel: [65330.148016] usb 1-8: New USB device found, idVendor=058f, idProduct=6366 Aug 18 06:42:30 bnasws02 kernel: [65330.148021] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 06:42:30 bnasws02 kernel: [65330.148023] usb 1-8: Product: Flash Card Reader/Writer Aug 18 06:42:30 bnasws02 kernel: [65330.148025] usb 1-8: Manufacturer: Generic Aug 18 06:42:30 bnasws02 kernel: [65330.148027] usb 1-8: SerialNumber: 058F63666485 Aug 18 06:42:30 bnasws02 kernel: [65330.148589] usb-storage 1-8:1.0: USB Mass Storage device detected Aug 18 06:42:30 bnasws02 kernel: [65330.148695] scsi6 : usb-storage 1-8:1.0 Aug 18 06:42:30 bnasws02 mtp-probe: checking bus 1, device 13: "/sys/devices/pci:00/:00:14.0/usb1/1-8" Aug 18 06:42:30 bnasws02 mtp-probe: bus: 1, device: 13 was not an MTP device Aug 18 06:42:31 bnasws02 kernel: [65331.147150] scsi 6:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 4 Aug 18 06:42:31 bnasws02 kernel: [65331.147528] sd 6:0:0:0: Attached scsi generic sg1 type 0 Aug 18 06:42:40 bnasws02 kernel: [65340.789407] sd 6:0:0:0: [sdb] Attached SCSI removable disk ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-77-generic 3.16.0-77.99~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 18 06:40:25 2016 InstallationDate: Installed on 2015-08-06 (377 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614362 Title: SD Card not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1614362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
Interpolating the number of bugs to the number of users affected, looking into Google searches for users looking for help solving the problems caused by this, my guess is these are amongst the most annoying open bugs in Ubuntu out there. Is there any chance that any of these bugs will be fixed in the current LTS releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Still reproducible with 4.6.0-040600rc6-generic: $ uname -a Linux bnasws02 4.6.0-040600rc6-generic #201605012031 SMP Mon May 2 00:33:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux AC connected $ sudo acpitool -a -b Battery #1 : Discharging, 98.02% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 50272 mWh, 98.02% Design capacity: 56041 mWh Last full capacity : 51290 mWh, 91.52% of design capacity Capacity loss : 8.478% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS AC disconnected $ sudo acpitool -a -b Battery #1 : Discharging, 98.02%, 04:23:32 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 50272 mWh, 98.02%, 04:32:25 Design capacity: 56041 mWh Last full capacity : 51290 mWh, 91.52% of design capacity Capacity loss : 8.478% Present rate : 11072 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
4.6-rc5 and rc6 only seem to be available for wily, not for trusty on http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Christopher M. Penalver, why are you marking this as incomplete? Which information do you require? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
Jarno Suni, OK. Too bad. My interpretation was, this is also fixed in 14.04. For some reason I don't know more header packages were installed than image packages. My guess is this is because of some incomplete manual kernel removal, I executed in the past. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
$ sudo apt-get remove --purge linux-headers-3.16.0-57 linux-headers-3.16.0-57-generic linux-headers-3.16.0-59 linux-headers-3.16.0-59-generic linux-headers-3.16.0-60 linux-headers-3.16.0-60-generic linux-headers-3.16.0-62 linux-headers-3.16.0-62-generic linux-image-3.16.0-62-generic linux-image-extra-3.16.0-62-generic linux-signed-image-3.16.0-62-generic [sudo] password for sebastian: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.16.0-57* linux-headers-3.16.0-57-generic* linux-headers-3.16.0-59* linux-headers-3.16.0-59-generic* linux-headers-3.16.0-60* linux-headers-3.16.0-60-generic* linux-headers-3.16.0-62* linux-headers-3.16.0-62-generic* linux-image-3.16.0-62-generic* linux-image-extra-3.16.0-62-generic* linux-signed-image-3.16.0-62-generic* 0 to upgrade, 0 to newly install, 11 to remove and 9 not to upgrade. After this operation, 515 MB disk space will be freed. Do you want to continue? [Y/n] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
Fix seems not released. My disk is again cluttered with old kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559924] Re: rsyslog shuts down too early, preventing logging of the other jobs shutting down
Sorry, I thought, systemd was default in Ubuntu 14.04, but it seems, upstart is still taking care of most init related things in Ubuntu 14.04. ** Description changed: - systemd kills rsyslog as one of the first jobs. So after that no other + upstart kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559924 Title: rsyslog shuts down too early, preventing logging of the other jobs shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1559924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559924] [NEW] systemd kills rsyslog as one of the first jobs, preventing logging of the other jobs shutting down
Public bug reported: systemd kills rsyslog as one of the first jobs. So after that no other jobs are logging that they are shutting down and what they are doing during shutdown. The default should be shutting down logging at the latest possible point in time when shutting down a machine. ** Affects: systemd (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/1559924 Title: systemd kills rsyslog as one of the first jobs, preventing logging of the other jobs shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1559924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
It is reproducible: When the AC adapter is connected and the battery is fully charged: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 51901 mWh, 100.0% Design capacity : 56041 mWh Last full capacity : 51901 mWh, 92.61% of design capacity Capacity loss : 7.387% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Yes, this is correct, Christopher -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
$ uname -a Linux bnasws02 4.5.0-040500rc5-lowlatency #201602201730 SMP PREEMPT Sat Feb 20 22:37:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux When the AC adapter is connected and the battery is not fully charged: $ sudo acpitool -a -b Battery #1 : Charging, 95.76%, 00:13:41 AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 49108 mWh, 95.79%, 00:14:08 Design capacity: 56041 mWh Last full capacity : 51268 mWh, 91.48% of design capacity Capacity loss : 8.517% Present rate : 9161 mW Charging state : Charging Battery type : Li-ion Model number : ASUS When the AC adapter is disconnected and the battery is not fully charged: $ sudo acpitool -a -b Battery #1 : Discharging, 95.79%, 04:31:57 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 49085 mWh, 95.74%, 05:03:52 Design capacity: 56041 mWh Last full capacity : 51268 mWh, 91.48% of design capacity Capacity loss : 8.517% Present rate : 9692 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS BUT: When the AC adapter is connected and the battery is fully charged: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 51901 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 51901 mWh, 92.61% of design capacity Capacity loss : 7.387% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When the AC adapter is disconnected and the battery is fully charged: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 05:55:17 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 51901 mWh, 100.0%, 05:59:55 Design capacity: 56041 mWh Last full capacity : 51901 mWh, 92.61% of design capacity Capacity loss : 7.387% Present rate : 8652 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Will the fix, that has been merged in the meantime make it into 14.04 LTS or do we have to wait for some future Ubuntu release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install
Change summary, because /boot is always to small on "LVM or Encrypted install". The former summary read like it was a user error, while it isn't. ** Summary changed: - Kernels not autoremoving, causing out of space error on LVM or Encrypted install with small /boot partition + Kernels not autoremoving, causing out of space error on LVM or Encrypted install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Reproducible on an ASUS UX305LA $ uname -a Linux bnasws02 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9 10:03:23 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date UX305LA.204 07/06/2015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Unfortunately, the BIOS update didn't fix this: When the AC adapter is connected: sebastian@bnasws02[0r/0s]:~ $ sudo acpitool -a -b Battery #1 : Discharging, 99.11% AC adapter : online sebastian@bnasws02[0r/0s]:~ $ sudo acpitool -B Battery #1 : present Remaining capacity : 54016 mWh, 99.11% Design capacity: 56041 mWh Last full capacity : 54502 mWh, 97.25% of design capacity Capacity loss : 2.746% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS AC adapter is disconnected: $ sudo acpitool -a -b Battery #1 : Discharging, 99.11%, 07:00:11 AC adapter : off-line sebastian@bnasws02[0r/0s]:~ $ sudo acpitool -B Battery #1 : present Remaining capacity : 54016 mWh, 99.11%, 06:22:35 Design capacity: 56041 mWh Last full capacity : 54502 mWh, 97.25% of design capacity Capacity loss : 2.746% Present rate : 8471 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS BIOS version info: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date UX305LA.204 07/06/2015 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
I guess, the kernel version also matters, so here it is: $ uname -a Linux bnasws02 3.16.0-49-generic #65~14.04.1-Ubuntu SMP Wed Sep 9 10:03:23 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388353] Re: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
/boot is just too small by default for the number of kernels kept if you are setting up Ubuntu 14.04 with encrypted disks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388353 Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388353] Re: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I convert this back to a bug. If you install Ubuntu 14.04 with encrypted disks, /boot is only 236M big. This is barely enough to keep 4 kernel versions. So either increase the default size of /boot so it can hold the number of old kernels, Ubuntu keeps by default or lower the number of old kernels, Ubuntu keeps by default to 2-3. ** Changed in: initramfs-tools (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388353 Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1388353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573653] Re: Since Upgrading to Ubuntu 10.04, changing counters of listings is not possible anymore
** Changed in: texlive-base (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/573653 Title: Since Upgrading to Ubuntu 10.04, changing counters of listings is not possible anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/573653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428605] Re: puppet-module-puppetlabs-apt does not work after installation via apt-get
** Changed in: puppet-module-puppetlabs-apt (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428605 Title: puppet-module-puppetlabs-apt does not work after installation via apt- get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet-module-puppetlabs-apt/+bug/1428605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
It is a new laptop with a fresh install, so I never had the chance to test it with an older kernel version. I did as you suggested test with the lastest 4.2 upstream kernel, unfortunately without success: AC connected: sebastian@bnasws02[0r/0s]:~ $ acpitool -a -B Battery #1 : present Remaining capacity : 52998 mWh, 98.80% Design capacity: 56041 mWh Last full capacity : 53643 mWh, 95.72% of design capacity Capacity loss : 4.279% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS AC adapter : online sebastian@bnasws02[0r/0s]:~ AC disconnected: $ acpitool -a -B Battery #1 : present Remaining capacity : 52998 mWh, 98.80%, 07:01:34 Design capacity: 56041 mWh Last full capacity : 53643 mWh, 95.72% of design capacity Capacity loss : 4.279% Present rate : 7543 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS AC adapter : off-line sebastian@bnasws02[0r/0s]:~ AC connected: $ acpitool -a -B Battery #1 : present Remaining capacity : 52998 mWh, 98.80%, 13:32:38 Design capacity: 56041 mWh Last full capacity : 53643 mWh, 95.72% of design capacity Capacity loss : 4.279% Present rate : 3913 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS AC adapter : online ** Tags added: kernel-bug-exists-upst ** Tags removed: kernel-bug-exists-upst ** Tags added: kernel-bug-exists-upst -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
Unfortunately the tags field is to small to add the full string kernel- bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482501] Re: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server
apport information ** Tags added: apport-collected trusty ** Description changed: sebastian@client[0r/0s]:~ $ mosh server.nohn.net mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] setlocale: No such file or directory Connection to server.nohn.net closed. /usr/bin/mosh: Did not find mosh server startup message. Locale settings on client: sebastian@client[0r/0s]:~ $ locale LANG=en_GB.UTF-8 LANGUAGE=en_GB:en LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Locale settings on server: $ ssh server.nohn.net locale locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_GB.UTF-8 LANGUAGE= LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Verify locale integrity on client: sebastian@client[0r/0s]:~ $ LANG=en_GB.UTF-8 locale LANG=en_GB.UTF-8 LANGUAGE=en_GB:en LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Verify locale integrity on server: sebastian@server:~$ LANG=en_GB.UTF-8 locale LANG=en_GB.UTF-8 LANGUAGE=en_GB.utf8 LC_CTYPE=en_GB.utf8 LC_NUMERIC=en_GB.utf8 LC_TIME=en_GB.utf8 LC_COLLATE=en_GB.utf8 LC_MONETARY=en_GB.utf8 LC_MESSAGES=en_GB.utf8 LC_PAPER=en_GB.utf8 LC_NAME=en_GB.utf8 LC_ADDRESS=en_GB.utf8 LC_TELEPHONE=en_GB.utf8 LC_MEASUREMENT=en_GB.utf8 LC_IDENTIFICATION=en_GB.utf8 LC_ALL=en_GB.utf8 It works, when I comment SendEnv LANG LC_* in /etc/ssh/ssh_config. + --- + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2015-08-06 (0 days ago) + InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) + Package: mosh 1.2.4a-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 + Tags: trusty + Uname: Linux 3.16.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1482501/+attachment/4440838/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482501 Title: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1482501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482506] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1482506/+attachment/4440836/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482506 Title: ASUS UX305LA, touchpad does not recognize two-finger-tap as middle mouse button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics-lts-utopic/+bug/1482506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482506] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1482506/+attachment/4440837/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482506 Title: ASUS UX305LA, touchpad does not recognize two-finger-tap as middle mouse button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics-lts-utopic/+bug/1482506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482501] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1482501/+attachment/4440839/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482501 Title: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1482501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482506] [NEW] ASUS UX305LA, touchpad does not recognize two-finger-tap as middle mouse button
Public bug reported:
After a fresh Ubuntu 14.04 install including all updates, the two-
finger-tap gesture is not recognized as middle mouse button.
A workaround to fix this is this script:
#!/usr/bin/env bash
ID=$(xinput | grep Touchpad | awk '{ print $6 }' | cut -d = -f 2)
WHATEVER=$(xinput list-props $ID | grep Tap Action | cut -d ( -f 2 | cut -d
) -f 1)
xinput set-int-prop $ID $WHATEVER 8 2 3 0 0 1 2 3
---
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2015-08-06 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
Package: xserver-xorg-input-synaptics-lts-utopic 1.8.1-1ubuntu1~trusty1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
Tags: trusty
Uname: Linux 3.16.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
** Affects: xserver-xorg-input-synaptics-lts-utopic (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected trusty
** Tags added: apport-collected trusty
** Description changed:
After a fresh Ubuntu 14.04 install including all updates, the two-
finger-tap gesture is not recognized as middle mouse button.
A workaround to fix this is this script:
#!/usr/bin/env bash
ID=$(xinput | grep Touchpad | awk '{ print $6 }' | cut -d = -f 2)
WHATEVER=$(xinput list-props $ID | grep Tap Action | cut -d ( -f 2 | cut
-d ) -f 1)
xinput set-int-prop $ID $WHATEVER 8 2 3 0 0 1 2 3
+ ---
+ ApportVersion: 2.14.1-0ubuntu3.11
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2015-08-06 (0 days ago)
+ InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64
(20150218.1)
+ Package: xserver-xorg-input-synaptics-lts-utopic 1.8.1-1ubuntu1~trusty1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
+ Tags: trusty
+ Uname: Linux 3.16.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482506
Title:
ASUS UX305LA, touchpad does not recognize two-finger-tap as middle
mouse button
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics-lts-utopic/+bug/1482506/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482501] Re: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server
I added your ppa and updated mosh on the server: sebastian@bxpcsr05:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed libio-socket-ip-perl libsocket-getaddrinfo-perl The following packages will be upgraded: mosh 1 to upgrade, 2 to newly install, 0 to remove and 0 not to upgrade. Need to get 400 kB of archives. After this operation, 393 kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://de.archive.ubuntu.com/ubuntu/ precise/universe libsocket-getaddrinfo-perl amd64 0.20-2build2 [30.3 kB] Get:2 http://de.archive.ubuntu.com/ubuntu/ precise/universe libio-socket-ip-perl all 0.07-1 [18.7 kB] Get:3 http://ppa.launchpad.net/keithw/mosh/ubuntu/ precise/main mosh amd64 1.2.5+1038-0ppa~ubuntu12.04.1 [351 kB] Fetched 400 kB in 0s (1,157 kB/s) (Reading database ... 425299 files and directories currently installed.) Preparing to replace mosh 1.1.3-1 (using .../mosh_1.2.5+1038-0ppa~ubuntu12.04.1_amd64.deb) ... Unpacking replacement mosh ... Selecting previously unselected package libsocket-getaddrinfo-perl. Unpacking libsocket-getaddrinfo-perl (from .../libsocket-getaddrinfo-perl_0.20-2build2_amd64.deb) ... Selecting previously unselected package libio-socket-ip-perl. Unpacking libio-socket-ip-perl (from .../libio-socket-ip-perl_0.07-1_all.deb) ... Processing triggers for man-db ... Processing triggers for ufw ... Setting up mosh (1.2.5+1038-0ppa~ubuntu12.04.1) ... Setting up libsocket-getaddrinfo-perl (0.20-2build2) ... Setting up libio-socket-ip-perl (0.07-1) ... After that, I uncommented the the SendEnv on the client again and tried to connect. The error message is the same as above. When commenting the line again on the client, I can connect as described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482501 Title: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1482501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440712/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440714/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] [NEW] ASUS UX305LA - Battery state not detected correctly
Public bug reported: Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 kB floppy services are supported (int 13h) 3.5/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 OUT OF SPEC (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description: USB 3.0 Controller On Board Device 8 Information Type: Other Status: Enabled Description: SMBus Controller On Board Device 9 Information Type: Other Status: Enabled Description: Card Reader On Board Device 10 Information Type: Other Status: Enabled Description: Cmos Camera On Board Device 11 Information Type: Other Status: Enabled Description: Bluetooth Handle 0x0005, DMI type 11, 5 bytes OEM Strings String 1: String 2: String 3: String 4: 90NB08T5-M00230 String 5: String 6: String 7: String 8: String 9: String 10: Handle 0x000C, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x000D, DMI type 7, 19 bytes Cache Information Socket Designation: L1 Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 32 kB Maximum Size: 32 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Parity System Type: Data Associativity: 8-way Set-associative Handle 0x000E, DMI type 7, 19 bytes Cache Information Socket Designation: L1 Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location:
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+attachment/4440692/+files/lspci-vnvn.log ** Description changed: Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b - Battery #1 : Discharging, 100.0% - AC adapter : online + Battery #1 : Discharging, 100.0% + AC adapter : online $ sudo acpitool -B - Battery #1 : present - Remaining capacity : 54027 mWh, 100.0% - Design capacity: 56041 mWh - Last full capacity : 53507 mWh, 95.48% of design capacity - Capacity loss : 4.522% - Present rate : 0 mW - Charging state : Discharging - Battery type : Li-ion - Model number : ASUS + Battery #1 : present + Remaining capacity : 54027 mWh, 100.0% + Design capacity: 56041 mWh + Last full capacity : 53507 mWh, 95.48% of design capacity + Capacity loss : 4.522% + Present rate : 0 mW + Charging state : Discharging + Battery type : Li-ion + Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b - Battery #1 : Discharging, 100.0%, 04:19:49 - AC adapter : off-line + Battery #1 : Discharging, 100.0%, 04:19:49 + AC adapter : off-line $ sudo acpitool -B - Battery #1 : present - Remaining capacity : 54005 mWh, 100.0%, 04:28:31 - Design capacity: 56041 mWh - Last full capacity : 53507 mWh, 95.48% of design capacity - Capacity loss : 4.522% - Present rate : 12067 mW - Charging state : Discharging - Battery type : Li-ion - Model number : ASUS + Battery #1 : present + Remaining capacity : 54005 mWh, 100.0%, 04:28:31 + Design capacity: 56041 mWh + Last full capacity : 53507 mWh, 95.48% of design capacity + Capacity loss : 4.522% + Present rate : 12067 mW + Charging state : Discharging + Battery type : Li-ion + Model number : ASUS System information: - $ sudo dmidecode + $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information - Vendor: American Megatrends Inc. - Version: UX305LA.202 - Release Date: 04/16/2015 - Address: 0xF - Runtime Size: 64 kB - ROM Size: 6464 kB - Characteristics: - PCI is supported - BIOS is upgradeable - BIOS shadowing is allowed - Boot from CD is supported - Selectable boot is supported - BIOS ROM is socketed - EDD is supported - 5.25/1.2 MB floppy services are supported (int 13h) - 3.5/720 kB floppy services are supported (int 13h) - 3.5/2.88 MB floppy services are supported (int 13h) - Print screen service is supported (int 5h) - 8042 keyboard services are supported (int 9h) - Serial services are supported (int 14h) - Printer services are supported (int 17h) - ACPI is supported - USB legacy is supported - Smart battery is supported - BIOS boot specification is supported - Targeted content distribution is supported - UEFI is supported - BIOS Revision: 5.6 + Vendor: American Megatrends Inc. + Version: UX305LA.202 + Release Date: 04/16/2015 + Address: 0xF + Runtime Size: 64 kB + ROM Size: 6464 kB + Characteristics: + PCI is supported + BIOS is upgradeable + BIOS shadowing is allowed + Boot from CD is supported + Selectable boot is supported + BIOS ROM is socketed + EDD is supported + 5.25/1.2 MB floppy services are supported (int 13h) + 3.5/720 kB floppy services are supported (int 13h) + 3.5/2.88 MB floppy services are supported (int 13h) + Print screen service is supported (int 5h) + 8042 keyboard services are supported (int 9h) + Serial services are supported (int 14h) + Printer services are supported (int 17h) + ACPI is supported + USB legacy is supported + Smart battery is supported + BIOS boot specification is supported + Targeted content distribution is supported + UEFI is supported + BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information - Manufacturer: ASUSTeK COMPUTER INC. - Product Name: UX305LA - Version: 1.0 - Serial Number: F6N0CJ005192234 - UUID: 8ACDCACA-23D7-6D4B-8403-68B4F242E258 - Wake-up Type: Power Switch - SKU Number: ASUS-NotebookSKU - Family: UX + Manufacturer: ASUSTeK COMPUTER INC. + Product Name: UX305LA + Version: 1.0 + Serial Number: xxx +
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
apport information ** Tags added: apport-collected trusty ** Description changed: Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 kB floppy services are supported (int 13h) 3.5/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx Asset Tag: xxx Features: Board is a hosting board Board is replaceable Location In Chassis: MIDDLE Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 25 bytes Chassis Information Manufacturer: ASUSTeK COMPUTER INC. Type: Notebook Lock: Not Present Version: 1.0 Serial Number: xxx Asset Tag: xxx Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 1 OUT OF SPEC (0) SKU Number: To be filled by O.E.M. Handle 0x0004, DMI type 10, 26 bytes On Board Device 1 Information Type: Video Status: Enabled Description: VGA On Board Device 2 Information Type: Ethernet Status: Enabled Description: GLAN On Board Device 3 Information Type: Ethernet Status: Enabled Description: WLAN On Board Device 4 Information Type: Sound Status: Enabled Description: Audio CODEC On Board Device 5 Information Type: SATA Controller Status: Enabled Description: SATA Controller On Board Device 6 Information Type: Other Status: Enabled Description: USB 2.0 Controller On Board Device 7 Information Type: Other Status: Enabled Description: USB 3.0 Controller On Board Device 8 Information Type: Other Status: Enabled Description: SMBus Controller On Board Device 9 Information Type: Other Status: Enabled Description: Card Reader On Board Device 10 Information Type: Other Status: Enabled Description: Cmos Camera On Board Device 11 Information Type: Other Status: Enabled Description: Bluetooth Handle 0x0005, DMI type 11, 5 bytes OEM Strings String 1: String 2: String 3: String 4: 90NB08T5-M00230 String 5: String 6: String 7: String 8: String 9: String 10: Handle 0x000C, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x000D, DMI type 7, 19 bytes Cache Information Socket Designation: L1 Cache Configuration: Enabled, Not Socketed, Level 1
[Bug 1482390] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440703/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440702/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440709/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440713/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440705/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440715/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440710/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440704/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440711/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440706/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440707/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1482390/+attachment/4440708/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482501] [NEW] Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server
Public bug reported: sebastian@client[0r/0s]:~ $ mosh server.nohn.net mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] mosh-server: invalid option -- 'l' Usage: mosh-server new [-s] [-i LOCALADDR] [-p PORT] [-c COLORS] [-- COMMAND...] setlocale: No such file or directory Connection to server.nohn.net closed. /usr/bin/mosh: Did not find mosh server startup message. Locale settings on client: sebastian@client[0r/0s]:~ $ locale LANG=en_GB.UTF-8 LANGUAGE=en_GB:en LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Locale settings on server: $ ssh server.nohn.net locale locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_GB.UTF-8 LANGUAGE= LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Verify locale integrity on client: sebastian@client[0r/0s]:~ $ LANG=en_GB.UTF-8 locale LANG=en_GB.UTF-8 LANGUAGE=en_GB:en LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Verify locale integrity on server: sebastian@server:~$ LANG=en_GB.UTF-8 locale LANG=en_GB.UTF-8 LANGUAGE=en_GB.utf8 LC_CTYPE=en_GB.utf8 LC_NUMERIC=en_GB.utf8 LC_TIME=en_GB.utf8 LC_COLLATE=en_GB.utf8 LC_MONETARY=en_GB.utf8 LC_MESSAGES=en_GB.utf8 LC_PAPER=en_GB.utf8 LC_NAME=en_GB.utf8 LC_ADDRESS=en_GB.utf8 LC_TELEPHONE=en_GB.utf8 LC_MEASUREMENT=en_GB.utf8 LC_IDENTIFICATION=en_GB.utf8 LC_ALL=en_GB.utf8 It works, when I comment SendEnv LANG LC_* in /etc/ssh/ssh_config. ** Affects: mosh (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/1482501 Title: Ubuntu 14.04 mosh client unable to connect to Ubuntu 12.04 mosh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1482501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428605] Re: puppet-module-puppetlabs-apt does not work after installation via apt-get
I was too dumb. Issue can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428605 Title: puppet-module-puppetlabs-apt does not work after installation via apt- get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet-module-puppetlabs-apt/+bug/1428605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428605] [NEW] puppet-module-puppetlabs-apt does not work after installation via apt-get
Public bug reported:
To reproduce:
sudo apt-get install puppet-common puppet-module-puppetlabs-apt
After that, I'd expect the puppet module to work, however it does not.
For example, I'd expect this to add a ppa:
apt::ppa { ppa:webupd8team/java:}
However I only get this error message:
Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type apt::ppa at .../puppet/modules/xxx/manifests/packages.pp:2 on
node xxx
Wrapped exception:
Invalid resource type apt::ppa
Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type apt::ppa at .../puppet/modules/xxx/manifests/packages.pp:2 on
node xxx
Similar error, If I try to use apt::source
$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
$ apt-cache policy puppet-common puppet-module-puppetlabs-apt
puppet-common:
Installed: 3.4.3-1
Candidate: 3.4.3-1
Version table:
*** 3.4.3-1 0
500 http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64
Packages
100 /var/lib/dpkg/status
puppet-module-puppetlabs-apt:
Installed: 1.4.0-2
Candidate: 1.4.0-2
Version table:
*** 1.4.0-2 0
500 http://gce.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64
Packages
100 /var/lib/dpkg/status
** Affects: puppet-module-puppetlabs-apt (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/1428605
Title:
puppet-module-puppetlabs-apt does not work after installation via apt-
get
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet-module-puppetlabs-apt/+bug/1428605/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043092] [NEW] xorg keeps segfaulting a least once a day (gnome3 shell)
Public bug reported: kern.log: . Aug 29 07:03:07 bnibws03 kernel: [204037.310903] wlan0: authenticate with 00:14:bf:c4:c8:bd (try 1) Aug 29 07:03:07 bnibws03 kernel: [204037.313611] wlan0: authenticated Aug 29 07:03:07 bnibws03 kernel: [204037.313811] wlan0: associate with 00:14:bf:c4:c8:bd (try 1) Aug 29 07:03:07 bnibws03 kernel: [204037.316188] wlan0: RX AssocResp from 00:14:bf:c4:c8:bd (capab=0x411 status=0 aid=1) Aug 29 07:03:07 bnibws03 kernel: [204037.316191] wlan0: associated Aug 29 07:03:07 bnibws03 kernel: [204037.322675] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Aug 29 07:03:19 bnibws03 kernel: [204048.613820] wlan0: no IPv6 routers present Aug 29 07:04:30 bnibws03 kernel: [204119.283824] type=1701 audit(1346216670.115:194): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=21199 comm=chrome reason=seccomp sig=0 syscall=2 compat=0 ip=0x7f9901857eb0 code=0x50002 Aug 29 07:04:30 bnibws03 kernel: [204119.283842] type=1701 audit(1346216670.115:195): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=21199 comm=chrome reason=seccomp sig=0 syscall=2 compat=0 ip=0x7f9901857eb0 code=0x50002 Aug 29 07:04:30 bnibws03 kernel: [204119.284969] type=1701 audit(1346216670.115:196): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=21205 comm=chrome reason=seccomp sig=0 syscall=59 compat=0 ip=0x7f9901831427 code=0x50002 Aug 29 07:05:18 bnibws03 kernel: [204167.685283] Xorg[5898]: segfault at 7f430011 ip 7f43858a21b8 sp 7fff4de09250 error 4 in Xorg[7f438577a000+1f] Xorg.0.log.old: [204281.117] (II) intel(0): Printing DDC gathered Modelines: [204281.117] (II) intel(0): Modeline 1600x900x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz) [204281.117] (II) intel(0): Modeline 1600x900x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz) [204284.984] (II) AIGLX: Suspending AIGLX clients for VT switch [204289.671] (II) Open ACPI successful (/var/run/acpid.socket) [204289.671] (II) AIGLX: Resuming AIGLX clients after VT switch [204289.728] (II) intel(0): EDID vendor AUO, prod id 8510 [204289.728] (II) intel(0): Printing DDC gathered Modelines: [204289.728] (II) intel(0): Modeline 1600x900x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz) [204289.728] (II) intel(0): Modeline 1600x900x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz) [204290.033] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found [204290.600] (II) XKB: reuse xkmfile /var/lib/xkb/server-E16957E33179DAE346AE559F1405BD02453DBF16.xkm [204292.935] (II) intel(0): EDID vendor AUO, prod id 8510 [204292.935] (II) intel(0): Printing DDC gathered Modelines: [204292.935] (II) intel(0): Modeline 1600x900x0.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz) [204292.935] (II) intel(0): Modeline 1600x900x0.0 73.33 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (36.5 kHz) [204405.756] (II) XKB: reuse xkmfile /var/lib/xkb/server-E16957E33179DAE346AE559F1405BD02453DBF16.xkm [204405.764] (II) XKB: reuse xkmfile /var/lib/xkb/server-E16957E33179DAE346AE559F1405BD02453DBF16.xkm [204407.085] (II) XKB: reuse xkmfile /var/lib/xkb/server-E16957E33179DAE346AE559F1405BD02453DBF16.xkm [204430.770] Backtrace: [204430.835] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f4385902846] [204430.835] 1: /usr/bin/X (0x7f438577a000+0x18c6ea) [0x7f43859066ea] [204430.835] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4384aa+0xfcb0) [0x7f4384aafcb0] [204430.835] 3: /usr/bin/X (XIGetDeviceProperty+0x40) [0x7f43858a2370] [204430.835] 4: /usr/bin/X (0x7f438577a000+0x128452) [0x7f43858a2452] [204430.835] 5: /usr/bin/X (0x7f438577a000+0x128a5a) [0x7f43858a2a5a] [204430.835] 6: /usr/bin/X (0x7f438577a000+0x4e8a1) [0x7f43857c88a1] [204430.835] 7: /usr/bin/X (0x7f438577a000+0x3d7ba) [0x7f43857b77ba] [204430.835] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f438393576d] [204430.835] 9: /usr/bin/X (0x7f438577a000+0x3daad) [0x7f43857b7aad] [204430.835] Segmentation fault at address 0x7f430019 [204430.835] Caught signal 11 (Segmentation fault). Server aborting [204430.835] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [204430.835] Please also check the log file at /var/log/Xorg.0.log for additional information. [204430.835] [204430.836] (II) evdev: Power Button: Close [204430.836] (II) UnloadModule: evdev [204430.836] (II) Unloading evdev [204430.840] (II) evdev: Video Bus: Close [204430.840] (II) UnloadModule: evdev [204430.840] (II) Unloading evdev [204430.848] (II) evdev: Sleep Button: Close [204430.848] (II) UnloadModule: evdev [204430.848] (II) Unloading evdev [204430.852] (II) evdev: Integrated Camera: Close [204430.852] (II) UnloadModule: evdev [204430.852] (II) Unloading evdev [204430.856] (II) evdev: AT Translated Set 2 keyboard: Close [204430.856] (II) UnloadModule: evdev [204430.856] (II) Unloading evdev Other occurences in Xorg
[Bug 1043092] Re: xorg keeps segfaulting a leaste once a day (gnome3 shell)
** Summary changed: - xorg keeps segfaulting a leaste once a day (gnome3 shell) + xorg keeps segfaulting a least once a day (gnome3 shell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043092 Title: xorg keeps segfaulting a least once a day (gnome3 shell) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1043092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798023] [NEW] apt-get update fails with error 416 Requested Range Not Satisfiable
Public bug reported: Binary package hint: apt Err http://de.archive.ubuntu.com maverick-updates/main i386 Packages 416 Requested Range Not Satisfiable [IP: 141.30.13.30 80] Fetched 5,079B in 2s (2,296B/s) W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/maverick-updates/main/binary-i386/Packages.gz 416 Requested Range Not Satisfiable [IP: 141.30.13.30 80] E: Some index files failed to download, they have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: apt 0.8.3ubuntu7.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 Architecture: i386 Date: Thu Jun 16 07:56:13 2011 ExecutablePath: /usr/bin/apt-get InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: apt ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798023 Title: apt-get update fails with error 416 Requested Range Not Satisfiable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/798023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798023] Re: apt-get update fails with error 416 Requested Range Not Satisfiable
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798023 Title: apt-get update fails with error 416 Requested Range Not Satisfiable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/798023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92482] Re: NumLock gets enabled unexpectedly on my laptop
Same Problem on t43p on Maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/92482 Title: NumLock gets enabled unexpectedly on my laptop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666455] Re: High power usage in hibernation mode
apport information ** Tags added: apport-collected ** Description changed: After an unsuccessful upgrade from Ubuntu 10.04 to Ubuntu 10.10 (hibernation didn't work at all), I did a complete new install of Ubuntu 10.10 on my IBM/Lenovo ThinkPad t43p. Since then, the systems seems to have a very high power consumption in Hibernation. Please see attached file: (1) Computer was removed from power while being Hibernated (btw it was fully charged when sent to hibernation some 12 hours before, so 20% discharge in 12 hours (2) Computer has been woken up and used for some minutes and put to hibernation again (3) Computer has been woken up and used for some more minutes and put to hibernation again (4) Computer has been put back to power and woken up - The rate hasn't been that high with Ubuntu 10.04 and before (I don't - know since when I'm using Ubuntu on that machine. Maybe 7.04 or 7.10. + The rate hasn't been that high with Ubuntu 10.04 and before (I don't know since when I'm using Ubuntu on that machine. Maybe 7.04 or 7.10. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: sebastian 1825 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22' +Mixer name : 'Analog Devices AD1981B' +Components : 'AC97a:41445374' +Controls : 26 +Simple ctrls : 18 + Card29.Amixer.info: + Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1YHT29WW-1.06' +Mixer name : 'ThinkPad EC 1YHT29WW-1.06' +Components : '' +Controls : 2 +Simple ctrls : 1 + Card29.Amixer.values: + Simple mixer control 'Console',0 +Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum +Playback channels: Mono +Limits: Playback 0 - 14 +Mono: Playback 2 [14%] [off] + DistroRelease: Ubuntu 10.10 + HibernationDevice: RESUME=UUID=3f9ad239-01d3-4a4e-8440-8cd2a567d2cb + InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) + MachineType: IBM 2668PEG + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=/dev/mapper/hostname-root ro quiet splash + ProcEnviron: + PATH=(custom, user) + LANG=en_US.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 + Regression: Yes + RelatedPackageVersions: linux-firmware 1.38 + Reproducible: Yes + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: maverick kernel-power suspend resume regression-release needs-upstream-testing + Uname: Linux 2.6.35-22-generic i686 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 05/18/2006 + dmi.bios.vendor: IBM + dmi.bios.version: 1YET62WW (1.27 ) + dmi.board.name: 2668PEG + dmi.board.vendor: IBM + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: IBM + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnIBM:bvr1YET62WW(1.27):bd05/18/2006:svnIBM:pn2668PEG:pvrThinkPadT43p:rvnIBM:rn2668PEG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: + dmi.product.name: 2668PEG + dmi.product.version: ThinkPad T43p + dmi.sys.vendor: IBM ** Attachment added: AcpiTables.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729391/+files/AcpiTables.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729392/+files/AlsaDevices.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729393/+files/AplayDevices.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729394/+files/ArecordDevices.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729395/+files/BootDmesg.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729397/+files/Card0.Amixer.values.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729398/+files/Card0.Codecs.codec97.0.ac97.0.0.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729399/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729400/+files/CurrentDmesg.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729401/+files/IwConfig.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729402/+files/Lspci.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729403/+files/Lsusb.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729404/+files/PciMultimedia.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729405/+files/ProcCpuinfo.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729406/+files/ProcInterrupts.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
[Bug 666455] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/666455/+attachment/1729407/+files/ProcModules.txt -- High power usage in hibernation mode https://bugs.launchpad.net/bugs/666455 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
