[Touch-packages] [Bug 1853786] Re: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.
Btw, after install I've made an update and upgrade before rebooting. Greetings! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853786 Title: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity. Status in lightdm package in Ubuntu: Fix Released Bug description: Ubuntu Release: Ubuntu 18.04.3 LTS Lightdm Version: 1.26.0-0ubuntu1 In some programs I can't get out of fullscreen. I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I simply don't like GNOME. The problem is that some programs get stucked in fullscreen, freezing the screen, not getting any response of any kind. The mouse moves, but that's it. Killing the process does not resolve the issue. This problem came with Ubuntu 18.04 or Unity since the release of Bionic Beaver. At this point I'm used to it. I get rid of it by going to terminal with ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with "sudo reboot now". But It's kind of a nuisance having to do this everytime. The programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be solved, but nothing happens. Weird thing: When I restart lightdm the problem dissapears until I sleep or reboot my notebook. Attached here is the "cat /var/log/syslog" output when the problem is ocurring using Whatdesk (at 19:53:01 I restart lightdm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853786] Re: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.
It turns out that if you installed Ubuntu 18.04 LTS using the .iso images released in April 2018, you may kept back with Linux 4.18 and old Xorg display server. I updated kernel 5.0, Xorg, and graphics drivers by opting-in to “hardware enablement” (HWE). In the terminal: sudo apt install --install-recommends linux-generic-hwe-18.04 xserver- xorg-hwe-18.04 It solved the problem. ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) => Diego (diego-luna-1711) ** Changed in: lightdm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853786 Title: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity. Status in lightdm package in Ubuntu: Fix Released Bug description: Ubuntu Release: Ubuntu 18.04.3 LTS Lightdm Version: 1.26.0-0ubuntu1 In some programs I can't get out of fullscreen. I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I simply don't like GNOME. The problem is that some programs get stucked in fullscreen, freezing the screen, not getting any response of any kind. The mouse moves, but that's it. Killing the process does not resolve the issue. This problem came with Ubuntu 18.04 or Unity since the release of Bionic Beaver. At this point I'm used to it. I get rid of it by going to terminal with ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with "sudo reboot now". But It's kind of a nuisance having to do this everytime. The programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be solved, but nothing happens. Weird thing: When I restart lightdm the problem dissapears until I sleep or reboot my notebook. Attached here is the "cat /var/log/syslog" output when the problem is ocurring using Whatdesk (at 19:53:01 I restart lightdm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853786] [NEW] Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.
Public bug reported: Ubuntu Release: Ubuntu 18.04.3 LTS Lightdm Version: 1.26.0-0ubuntu1 In some programs I can't get out of fullscreen. I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I simply don't like GNOME. The problem is that some programs get stucked in fullscreen, freezing the screen, not getting any response of any kind. The mouse moves, but that's it. Killing the process does not resolve the issue. This problem came with Ubuntu 18.04 or Unity since the release of Bionic Beaver. At this point I'm used to it. I get rid of it by going to terminal with ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with "sudo reboot now". But It's kind of a nuisance having to do this everytime. The programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be solved, but nothing happens. Weird thing: When I restart lightdm the problem dissapears until I sleep or reboot my notebook. Attached here is the "cat /var/log/syslog" output when the problem is ocurring using Whatdesk (at 19:53:01 I restart lightdm). ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: 18.04 fullscreen lightdm org.gnome.sessionmanager stuck unity ** Attachment added: "/var/log/syslog when it's happening." https://bugs.launchpad.net/bugs/1853786/+attachment/5307584/+files/LightDM%20Bug%20Report%20To%20Launchpad ** Package changed: xorg (Ubuntu) => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853786 Title: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity. Status in lightdm package in Ubuntu: New Bug description: Ubuntu Release: Ubuntu 18.04.3 LTS Lightdm Version: 1.26.0-0ubuntu1 In some programs I can't get out of fullscreen. I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I simply don't like GNOME. The problem is that some programs get stucked in fullscreen, freezing the screen, not getting any response of any kind. The mouse moves, but that's it. Killing the process does not resolve the issue. This problem came with Ubuntu 18.04 or Unity since the release of Bionic Beaver. At this point I'm used to it. I get rid of it by going to terminal with ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with "sudo reboot now". But It's kind of a nuisance having to do this everytime. The programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be solved, but nothing happens. Weird thing: When I restart lightdm the problem dissapears until I sleep or reboot my notebook. Attached here is the "cat /var/log/syslog" output when the problem is ocurring using Whatdesk (at 19:53:01 I restart lightdm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
** Changed in: yaru Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in Yaru Theme: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853780] Re: Failed to deactivate: Device or resource busy
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853780 Title: Failed to deactivate: Device or resource busy Status in cryptsetup package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Fails to deactivate on shutdown $ LC_ALL=C journalctl -b -1 Nov 23 18:49:13 jarnos-OptiPlex-745 systemd-cryptsetup[4335]: Failed to deactivate: Device or resource busy Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: systemd-cryptsetup@sda5_crypt.service: Control process exited, code=exited status=1 Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: systemd-cryptsetup@sda5_crypt.service: Failed with result 'exit-code'. Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: Stopped Cryptography Setup for sda5_crypt. Nov 23 18:49:13 jarnos-OptiPlex-745 systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. Seems to be this issue: https://github.com/systemd/systemd/issues/8472 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:2.0.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 24 23:43:10 2019 InstallationDate: Installed on 2019-07-08 (139 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/xubuntu--vg-root ro video=vesafb:mtrr:3,ywrap splash crypttab: sda5_crypt UUID=5ef951e6-e0fc-4377-be56-d63ec7a865be none luks,discard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1853780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in Yaru Theme: Unknown Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
** Bug watch added: github.com/ubuntu/yaru/issues #1621 https://github.com/ubuntu/yaru/issues/1621 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/1621 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in Yaru Theme: Unknown Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in Yaru Theme: Unknown Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853768] [NEW] Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
Public bug reported: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in qtbase-opensource-src package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853762] Re: Headphones stop working until pairing again
Full syslog : boot + unable to connect headphones + re-pairing and using headphones ** Attachment added: "full_syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307528/+files/full_syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853762] Re: Headphones stop working until pairing again
guillaume@massada:~$ bluetoothctl --version bluetoothctl: 5.50 guillaume@massada:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319956 acl:71 sco:0 events:45584 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'massada' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x100 LMP Version: 4.2 (0x8) Subversion: 0x100 Manufacturer: Intel Corp. (2) guillaume@massada:~$ bluetoothctl Agent registered [MID ANC]# show Controller 14:AB:C5:7E:41:26 (public) Name: massada Alias: massada Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no [MID ANC]# devices Device 2C:4D:79:46:E7:5D MID ANC Device CC:B8:A8:2D:B9:49 Somfy One B0F1EC0CE412 [MID ANC]# info 2C:4D:79:46:E7:5D Device 2C:4D:79:46:E7:5D (public) Name: MID ANC Alias: MID ANC Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308
[Touch-packages] [Bug 1853762] [NEW] Headphones stop working until pairing again
Public bug reported: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX
[Touch-packages] [Bug 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked
replacing light-locker with xfce4-screensaver has fixed my problem (also working in 19.04) thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1830408 Title: [nouveau][XFCE] Do not see login screen after screen is blanked Status in lightdm package in Ubuntu: New Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
Interestingly, at the moment if I start playing audio in user1 and switch to user2, the audio is still audible. Normally, it'd be silent unless user2 was playing something until switched back to user1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849859] Re: error when connecting to smb server
Hi, Nope I'm running 19.10. This bug exists in current version of ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 840333] Re: /etc/logrotate.d/unattended-upgrades should not have compress option
There is a relevant bug report against logrotate: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656060 I generally agree with the bug, but in practice u-u's logs compress well and in compressed form take one block: $ du -sh /var/log/unattended-upgrades/* 16K /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.1.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.2.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.3.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.4.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.5.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-dpkg.log.6.gz 0 /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 4.0K/var/log/unattended-upgrades/unattended-upgrades-shutdown.log.1.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades-shutdown.log.2.gz 24K /var/log/unattended-upgrades/unattended-upgrades.log 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.1.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.2.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.3.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.4.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.5.gz 4.0K/var/log/unattended-upgrades/unattended-upgrades.log.6.gz If logrotate switches to detect the need for compression automatically, I will stop overriding that in the package. ** Bug watch added: Debian Bug tracker #656060 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656060 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Opinion ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/840333 Title: /etc/logrotate.d/unattended-upgrades should not have compress option Status in unattended-upgrades package in Ubuntu: Opinion Bug description: I think that log files compression lowers the system performance on desktop computers which have now enough disk space for storing old logs. The "nocompress" and "compress" options of logrotate configure 2 different behaviours of logrotate. If the log file isn't compressed, logrotate will just rename it to something like 'log_file_name.log.1' with quite no disk input/output. If the log file is compressed, logrotate will read the file, compress it and rewrite the content into a new file with a name like 'log_file_name.log.1.gz'. I think that files compression is a good tradeoff only in case the compressed files have a longer lifetime than the log files (i. e. man pages, documentation, fonts, Debian package files, ...). Drawbacks of log files compression : - increases disk input/output - increases cpu and memory usage - increases energy consumption - slightly decreases the disk lifetime ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unattended-upgrades 0.72.1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sat Sep 3 15:16:34 2011 InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/840333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
KUbuntu 19.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1245624 Title: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hello I've been using the kernel Linux 3.0.100 kernel, and since then (subsequent versions), I don’t have support analog for this chipset. I ask whether you can solve. Thanks Regards Toni ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 2249 F pulseaudio /dev/snd/controlC1: toni 2249 F pulseaudio /dev/snd/controlC0: toni 2249 F pulseaudio Date: Mon Oct 28 19:29:17 2013 HibernationDevice: RESUME=UUID=146689ca-5189-4daa-87d7-b59d90ce4ac6 InstallationDate: Installed on 2013-05-07 (173 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: HP-Pavilion GJ306AA-ABE m8175.es MarkForUpload: True ProcEnviron: LANGUAGE=ca_AD:ca PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_AD.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=11a5f37e-f23e-4f05-8e78-0e1d97767d70 ro vga=791 acpi_sleep=s3_bios,s3_mode libata.atapi_enabled=1 combined_mode=libata RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (10 days ago) dmi.bios.date: 07/11/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.05 dmi.board.name: Berkeley dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GJ306AA-ABE m8175.es dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245624] Re: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog
A very old report. Yes, it is fixed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1245624 Title: [HP Pavilion Media Center TV m8175.es Desktop PC] Non support for ALC1200 Analog Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hello I've been using the kernel Linux 3.0.100 kernel, and since then (subsequent versions), I don’t have support analog for this chipset. I ask whether you can solve. Thanks Regards Toni ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 2249 F pulseaudio /dev/snd/controlC1: toni 2249 F pulseaudio /dev/snd/controlC0: toni 2249 F pulseaudio Date: Mon Oct 28 19:29:17 2013 HibernationDevice: RESUME=UUID=146689ca-5189-4daa-87d7-b59d90ce4ac6 InstallationDate: Installed on 2013-05-07 (173 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: HP-Pavilion GJ306AA-ABE m8175.es MarkForUpload: True ProcEnviron: LANGUAGE=ca_AD:ca PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_AD.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=11a5f37e-f23e-4f05-8e78-0e1d97767d70 ro vga=791 acpi_sleep=s3_bios,s3_mode libata.atapi_enabled=1 combined_mode=libata RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (10 days ago) dmi.bios.date: 07/11/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.05 dmi.board.name: Berkeley dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.05:bd07/11/2007:svnHP-Pavilion:pnGJ306AA-ABEm8175.es:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GJ306AA-ABE m8175.es dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853753] [NEW] Top Bar can't be changed
Public bug reported: After install and establishing email accounts, the top bar can't be changed. There is no "edit" function to add, delete or move the various icons. Kernel: 4.15.0-69-generic x86_64 bits: 64 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.3 LTS ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1853753 Title: Top Bar can't be changed Status in evolution-data-server package in Ubuntu: New Bug description: After install and establishing email accounts, the top bar can't be changed. There is no "edit" function to add, delete or move the various icons. Kernel: 4.15.0-69-generic x86_64 bits: 64 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1853753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
Most of the times, the first hit (namely the ipv4 address) is all that is used from the DNS query. In my case, it is essentially a testcase for Tcl's socket, which tries to establish a connection to an unlistened port, and expects a "connection refused" error. But Tcl in this case(namely that the connection gets refused) attempts the connect on the next address- result, which is then the bad ipv6-address. That one then caused an "EINVAL" from the connect() syscall, which it reported up, so the testcase expecting "connection refused" failed. I'm aware that the impact is not very big, but that just explains, why it wasn't already noticed long before. Conclusion is, that DNS should either not return an inet6 link-local address at all, as this cannot be used that way (namely without the name of the network-device), or it should only provide it together with the network-device, if that is possible in the DNS protocol. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: New Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852001] Re: Xorg freeze on high disk or cpu load or random
mouse lag. almost unusable - kernel 5.4.0-050400rc6-generic - medium load network traffic (20MB/s) and accompaning disk traffic - swap available - xserver-xorg-video-intel installed again, disabling swap solved the problem. this sucks because I hoped with the release of an official ubuntu 5.4 kernel the problem might disappear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: Xorg freeze on high disk or cpu load or random Status in xorg package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd.
[Touch-packages] [Bug 1850041] Re: Systemd-analyze blame returns "Bootup is not yet finished"
A lot of people seem to be suffering this if you search for "Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0)". Looks like plymouth is to blame, not systemd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1850041 Title: Systemd-analyze blame returns "Bootup is not yet finished" Status in systemd package in Ubuntu: Confirmed Bug description: Every time I run systemd-analyze blame, I get the message: Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. This, even if my laptop is on for several hours. Running systemctl list-jobs, returns: JOB UNIT TYPE STATE 1 graphical.target start waiting 95 systemd-update-utmp-runlevel.service start waiting 89 system-getty.slice start waiting 87 getty.target start waiting 21 setvtrgb.service start waiting 112 plymouth-quit-wait.service start running 88 getty@tty1.service start waiting 2 multi-user.targetstart waiting Boot time is about 90 seconds, before and after upgrading from 19.04 to 19.10. All applications start and run normally. My system is Ubuntu Budgie 19.10, working on a Dell Inspiron Laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 27 09:54:26 2019 MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2b7d5523-743f-465d-a24c-fadc4a3aa0f4 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2019-10-23 (3 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd11/30/2012:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1850041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849859] Re: error when connecting to smb server
In this days cups-filters, libcupsfilters1, cups-filters-core-driver, cups-browsed and libfontembed1 was upgraded. Since then nothing works anymore, printing per USB don't work anymore too. Error message: Filter failed @ Till Kamppeter The described bug in Fedora 30 seems to be the same. @daponz Do you use Ubuntu 20.04 too? Installing a prior version of smb client or cups is not possible, then you have to jump to an prior Ubuntu. In 18.04 it works fine. There is still plenty of time until April, I hope, this bug will be solved till then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853741] [NEW] system freezes randomly on boot, after loading initial ramdisk
Public bug reported: adding nomodeset to grub parameter negates the problem, not 100% but almost sure this has to do with graphics initialization. first appeared after a recent upgrade ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 13:42:39 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-66-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0457] InstallationDate: Installed on 2018-08-22 (458 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron N7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=5dd50c10-bb05-48da-af7d-ad4ca2d73eef ro quiet splash acpi_backlight=video vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853741 Title: system freezes randomly on boot, after loading initial ramdisk Status in xorg package in Ubuntu: New Bug description: adding nomodeset to grub parameter negates the problem, not 100% but almost sure this has to do with graphics initialization. first appeared after a recent upgrade ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 13:42:39 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-66-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0457] InstallationDate: Installed on 2018-08-22 (458 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron N7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=5dd50c10-bb05-48da-af7d-ad4ca2d73eef ro quiet splash acpi_backlight=video vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11:
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
To Robie Basak, specifically #22, You said, "I don't see how we created another problem. We changed the default, that's all." You seem to have concluded that merely a change of default functionally was made at some point. Perhaps that is the case. If so, what specifically was the default setting that was changed? For example, was it a kernel compilation time option? If so, can you please specify what setting can be changed back in order to re-enable Console blanking using DPMS (console display in power saving mode) for Ubuntu server 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853739] [NEW] normal usage then all apps stopped and UI dropped to desktop
Public bug reported: UI stopped responding ctrl +alt +f3 to htop 1 of the cpus at 100% I see whoopsie is at 100% then another app ctrl +alt +f2 back to desktop no apps are running terminal apport-bug xorg I know running apport-bug xorg from terminal will FAIL ubuntu 19.1 is crashing 5X per week at minimum! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 12:13:45 2019 DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (1553 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (32 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853739 Title: normal usage then all apps stopped and UI dropped to desktop Status in xorg package in Ubuntu: New Bug description: UI stopped responding ctrl +alt +f3 to htop 1 of the cpus at 100% I see whoopsie is at 100% then another app ctrl +alt +f2 back to desktop no apps are running terminal apport-bug xorg I know running apport-bug xorg from terminal will FAIL ubuntu 19.1 is crashing 5X per week at minimum! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 12:13:45 2019 DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated
[Touch-packages] [Bug 137314] Re: blkid shows outdated / wrong UUID
It's happening to me now on a RPI3 with Ubuntu 16.04 armhf. Yesterday evening I've deleted two old ext3 partitions to make room for a small BTRFS RAID1 2x 20 Gb partitions and now I was looking for the PARTUUID to write it in cmdline.txt. So blkid had plenty of time to reflect the new layout. ii util-linux2.27.1-6ubuntu3.6 armhf miscellaneous system utilities I've tried also with partprobe, to no avail. ii libparted2:armhf 3.2-15 armhfdisk partition manipulator - shared library ii parted 3.2-15 armhfdisk partition manipulator Both fdisk and parted print the correct layout. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/137314 Title: blkid shows outdated / wrong UUID Status in e2fsprogs package in Ubuntu: Invalid Bug description: Binary package hint: libblkid1 blkid shows outdated and wrong information on UUID and label for partitions that were reformatted after initial installation. After reformatting and relabeling partitions, blkid does not reflect the change (not even after reboot) and delivers misleading information about which UUID to put in /etc/fstab to mount the partition by UUID. This causes boot failures on systems which were restored by partition- imaging software that possibly changes the UUID of the restored partition (which is necessary, if there is already another partition present with the same UUID). Also installation of a second Linux system on the same Computer regularly reformats the swap-space, so the previously installed system doesn't find its swap anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/137314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 137314] Re: blkid shows outdated / wrong UUID
Oops, my fault, just running it with sudo refreshed its state to the correct values. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/137314 Title: blkid shows outdated / wrong UUID Status in e2fsprogs package in Ubuntu: Invalid Bug description: Binary package hint: libblkid1 blkid shows outdated and wrong information on UUID and label for partitions that were reformatted after initial installation. After reformatting and relabeling partitions, blkid does not reflect the change (not even after reboot) and delivers misleading information about which UUID to put in /etc/fstab to mount the partition by UUID. This causes boot failures on systems which were restored by partition- imaging software that possibly changes the UUID of the restored partition (which is necessary, if there is already another partition present with the same UUID). Also installation of a second Linux system on the same Computer regularly reformats the swap-space, so the previously installed system doesn't find its swap anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/137314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp