[Touch-packages] [Bug 1724803] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Expired -- 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/1724803 Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in unattended-upgrades package in Ubuntu: Expired Bug description: Fell into command execution loop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.8 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 17 12:16:36 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2015-07-31 (810 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.25 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: Upgraded to xenial on 2017-10-17 (1 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "7"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-08-04T07:41:06.559797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1724803/+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 1717247] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (mo
[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Expired -- 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/1717247 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) Status in unattended-upgrades package in Ubuntu: Expired Bug description: Dieser Fehler kommt immer wieder bei jeder Installation. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Sep 14 11:39:17 2017 ErrorMessage: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-08-19 (25 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) 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/1717247/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-hwe (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/1821533 Title: failure to detect and use Intel 620 graphics pci id 3ea0 Status in linux-hwe package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb install (also 18.10, also 19.04 daily) leads to black screen. Adding "nomodeset" to kernel boot parameter gives 800x600 video only and permits installing OS to disk. Applying updates and hardware enablement packages does not solve problem: the system will still only boot with nomodeset kernel option, and X is limited to using fbdev module at 800x600 resolution. The "modesetting" driver appears to be loaded and then unloaded during X startup. Trying to force intel module from xserver-xorg-video-intel by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not help. The PCI id for the graphics device appears to be 3ea0 and the place where that might be relevant is the i915 module. This problem occurs with every other Linux release I have tried including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest. The one open source OS that I have found where it might be fixed is DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have verified that the patch referenced in that bug report does make DragonFlyBSD boot past the video problem which I think is the same problem I experience with every Linux OS I have tried including Ubuntu. guest@guest-ZenBook-UX431FA:~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev" ii linux-generic-hwe-18.044.18.0.16.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-18.044.18.0.16.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-18.04 4.18.0.16.66 amd64Generic Linux kernel image ii linux-signed-generic-hwe-18.04 4.18.0.16.66 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 amd64X.Org X server -- fbdev display driver Expected result: Video at 1920x1080 Actual result: Video limited to 800x600 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 10:36:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FA 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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx:
[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Please try live booting 19.04: http://cdimages.ubuntu.com/daily-live/current/ and tell us if audio works there. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
** Tags added: bionic ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1821505] Re: screen cannot be turned back on after some time of inactivity
** Tags added: radeon ** Summary changed: - screen cannot be turned back on after some time of inactivity + [radeon] screen cannot be turned back on after some time of inactivity ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => New -- 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/1821505 Title: [radeon] screen cannot be turned back on after some time of inactivity Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. WORKAROUND: Type in a terminal: xset -display :0.0 dpms force off WORKAROUND: Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: gnome-screensaver-command -a WORKAROUND: When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+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 1821512] Re: Asus ZenBook UX433FN No output sound in Ubuntu 18.04
*** This bug is a duplicate of bug 1818802 *** https://bugs.launchpad.net/bugs/1818802 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1818802, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1818802 [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while -- 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/1821512 Title: Asus ZenBook UX433FN No output sound in Ubuntu 18.04 Status in alsa-driver package in Ubuntu: New Bug description: I've tried this solution: https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and so many solutions were similar to this. But they didn't work. I know that upgrading my kernel version from 4.18.5 to 4.20 will fix it. But I don't want to do that since 4.20 isn't a stable version. Is there any other way that someone could offer? I'll be grateful folks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.18.5-041805-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 16:26:57 2019 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1339 F pulseaudio hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821512/+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 1821397] Re: internal error when attempting to calibrate monitor using Spyder Pro 2
Can you please provide a screenshot or photo of the error you are seeing? Also, I notice your kernel keeps logging: [4.513233] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0 which means you might need to try a different DVI cable if not a different monitor to get the correct resolution. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1821397 Title: internal error when attempting to calibrate monitor using Spyder Pro 2 Status in xorg-server package in Ubuntu: Incomplete Bug description: ColorVision Spdyer 2 Pro was confirmed to work with Windows as I was able to calibrate another monitor 15 min after "internal error" message on Ubuntu, also tried using alt driver for GTX-970 video card (proprietary and x-org) The message occurs after being asked to place the Spyder Pro 2 on the screen and click NEXT to proceed. Ubuntu 18.04.2 LTS Kernel: Linux 4.15.0-46-generic (x86_64) Version : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27 Distribution : Ubuntu 18.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 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: Fri Mar 22 11:32:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] InstallationDate: Installed on 2019-03-21 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a8972fc6-077e-4117-a465-f0088a2989c9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: TUF Z390-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ390-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 To manage notifications about this bug go to:
[Touch-packages] [Bug 1821398] Re: cannot calibrate monitor with Spyder Pro 2
*** This bug is a duplicate of bug 1821397 *** https://bugs.launchpad.net/bugs/1821397 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1821397, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1821397 internal error when attempting to calibrate monitor using Spyder Pro 2 -- 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/1821398 Title: cannot calibrate monitor with Spyder Pro 2 Status in xorg package in Ubuntu: New Bug description: "Internal Error" when using x-org driver for NVIDIA GTX-980 video card when clicking on NEXT button after being asked to place the Spyder Pro 2 on the screen. Same error occurs if I use proprietary driver for video card. The Spyder Pro 2 has been testes confirmed to work with Windows after this fail in Ubuntu 18.04 Kernel: Linux 4.15.0-46-generic (x86_64) Version : #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27 Distribution : Ubuntu 18.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 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: Fri Mar 22 13:12:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] InstallationDate: Installed on 2019-03-21 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 005: ID 085c:0200 ColorVision, Inc. Spyder 2 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a8972fc6-077e-4117-a465-f0088a2989c9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: TUF Z390-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ390-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 To manage
[Touch-packages] [Bug 1821371] Re: starting
It appears Xorg can't open the GPU device: [ 125.196] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19 [ 125.196] (EE) open /dev/dri/card0: No such file or directory [ 125.196] (WW) Falling back to old probe method for modesetting [ 125.196] (EE) open /dev/dri/card0: No such file or directory which may or may not be related to this kernel error: [ 75.351253] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 75.351261] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 75.351263] nouveau :01:00.0: msvld: unable to load firmware data [ 75.351266] nouveau :01:00.0: msvld: init failed, -19 ** Tags added: nouveau ** Summary changed: - starting + [nouveau] Black screen with some icons flashing on start-up ** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) ** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux (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/1821371 Title: [nouveau] Black screen with some icons flashing on start-up Status in linux package in Ubuntu: Confirmed Bug description: when i start , i can't have ubuntu , but black screen with some icones flashing , my arrow of the mouse can move but do nothing , i'm french so excuse me for my language ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_36_39_generic_48 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Fri Mar 22 16:34:18 2019 DistUpgraded: 2018-07-23 08:19:08,090 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 740] [1458:368d] InstallationDate: Installed on 2017-05-19 (672 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Olidata S.p.A. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4bf32425-67a7-4926-91a8-f1fb1b97baaf ro splash quiet plymouth:debug=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-23 (242 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B85M DASH/OL R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd01/23/2015:svnOlidataS.p.A.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85MDASH/OLR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Sun Jul 22 08:14:02 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver MOUSE, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821371/+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 1821318] Re: FFe: Wayland 1.17 for disco
** Changed in: wayland (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1821318 Title: FFe: Wayland 1.17 for disco Status in wayland package in Ubuntu: Won't Fix Bug description: https://wayland.freedesktop.org/releases.html https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html --- Please upload the new version of Wayland (1.17) published on March 20, 2019, as it is complementary in the graphic, if there are usability problems you can stop using changing the configuration in GDM3. From Wayland to Xorg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821022] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Can you please run: dpkg -l > allpackages.txt and then attach 'allpackages.txt'? -- 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/1821022 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying alsa-base in options snd-hda-intel model=auto or options snd-hda-intel model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work perfectly when I connected to TV HDMI input (but could not steal TV 4 ever) https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858 https://streamable.com/5j96k BIOS setting in the video above ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1577 F pulseaudio /dev/snd/controlC0: hp 1577 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 20 15:42:37 2019 InstallationDate: Installed on 2016-09-07 (923 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1577 F pulseaudio /dev/snd/controlC0: hp 1577 F pulseaudio /dev/snd/seq:timidity 1083 F timidity Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa-base.conf: #options snd-hda-intel model=3stack-6ch mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-19T20:25:47.409210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821022/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)
Any news on when this will land in bionic proposed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour) Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: * Impact The focus gets removed from the search entry widget in the fileselector while typing which makes it difficult to use * Test case Steps: 1. Open Gedit 2. Choose Open -> Other Documents... to open a GtkFileChooserDialog 3. Press on the search button next to Open 4. Type what you are searching for Expected behaviour: Focus remains in the search input until I finish typing then results come up What happens instead: Searching stops after I enter the first characters because focus is lost from the search input * Regression potential The change is desactivating/reactivating typeahead in the gtk fileselector, check that this feature keeps working as it should (keyboard navigate by typing the first chars of a file/folder, that should move the focus to the first matching item and allows to navigate by hitting enter) I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. Upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/1572 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+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 1821508] Re: there is a lagging while i am accessing the software or browing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1821508 Title: there is a lagging while i am accessing the software or browing Status in xorg package in Ubuntu: New Bug description: i have serious issues while surfing in browsers. also video lags too much while i am playing any video in youtube. so tried to install intel drives.. thought it may solve my issue. any one could u please help me in solving this. also i have issue in processing fast i have system with following config please any one sugggest how can i speed up my application along with video lagging ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 16:45:03 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (primary) [1025:011f] Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1025:011f] InstallationDate: Installed on 2018-11-04 (140 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731) MachineType: Acer Extensa 5220 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=5d6083c5-92be-466a-b199-35f0ebb59423 ro quiet nomodeset splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.32 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.32:bd02/01/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5220 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 24 16:26:55 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputLenovo Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821508/+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 1821539] Re: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821539 Title: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: I have no idea. Just warned me about a system error. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: policykit-1 0.105-21ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Sun Mar 24 13:26:48 2019 ErrorMessage: new policykit-1 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: policykit-1 Title: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1821539/+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 1821539] [NEW] package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1
Public bug reported: I have no idea. Just warned me about a system error. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: policykit-1 0.105-21ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Sun Mar 24 13:26:48 2019 ErrorMessage: new policykit-1 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: policykit-1 Title: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821539 Title: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: I have no idea. Just warned me about a system error. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: policykit-1 0.105-21ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Sun Mar 24 13:26:48 2019 ErrorMessage: new policykit-1 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: policykit-1 Title: package policykit-1 0.105-21ubuntu0.3 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1821539/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
** Description changed: Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb install (also 18.10, also 19.04 daily) leads to black screen. Adding "nomodeset" to kernel boot parameter gives 800x600 video only and permits installing OS to disk. Applying updates and hardware enablement packages does not solve problem: the system will still only boot with nomodeset kernel option, and X is limited to using fbdev module at 800x600 resolution. The "modesetting" driver appears to be loaded and then unloaded during X startup. Trying to force intel module from xserver-xorg-video-intel by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not help. The PCI id for the graphics device appears to be 3ea0 and the place where that might be relevant is the i915 module. This problem occurs with every other Linux release I have tried including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest. The one open source OS that I have found where it might be fixed is - DragonFlyBSD (see bug report 3167 here - https://bugs.dragonflybsd.org/issues/3167). I have verified that the - patch referenced in that bug report does make DragonFlyBSD boot past the - video problem which I think is the same problem I experience with every - Linux OS I have tried including Ubuntu. + DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have + verified that the patch referenced in that bug report does make + DragonFlyBSD boot past the video problem which I think is the same + problem I experience with every Linux OS I have tried including Ubuntu. guest@guest-ZenBook-UX431FA:~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev" ii linux-generic-hwe-18.044.18.0.16.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-18.044.18.0.16.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-18.04 4.18.0.16.66 amd64Generic Linux kernel image ii linux-signed-generic-hwe-18.04 4.18.0.16.66 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 amd64X.Org X server -- fbdev display driver Expected result: Video at 1920x1080 Actual result: Video limited to 800x600 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 10:36:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] + Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FA 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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
[Touch-packages] [Bug 1821533] [NEW] failure to detect and use Intel 620 graphics pci id 3ea0
Public bug reported: Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb install (also 18.10, also 19.04 daily) leads to black screen. Adding "nomodeset" to kernel boot parameter gives 800x600 video only and permits installing OS to disk. Applying updates and hardware enablement packages does not solve problem: the system will still only boot with nomodeset kernel option, and X is limited to using fbdev module at 800x600 resolution. The "modesetting" driver appears to be loaded and then unloaded during X startup. Trying to force intel module from xserver-xorg-video-intel by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not help. The PCI id for the graphics device appears to be 3ea0 and the place where that might be relevant is the i915 module. This problem occurs with every other Linux release I have tried including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest. The one open source OS that I have found where it might be fixed is DragonFlyBSD (see bug report 3167 here https://bugs.dragonflybsd.org/issues/3167). I have verified that the patch referenced in that bug report does make DragonFlyBSD boot past the video problem which I think is the same problem I experience with every Linux OS I have tried including Ubuntu. guest@guest-ZenBook-UX431FA:~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev" ii linux-generic-hwe-18.044.18.0.16.66 amd64Complete Generic Linux kernel and headers ii linux-headers-generic-hwe-18.044.18.0.16.66 amd64Generic Linux kernel headers ii linux-image-generic-hwe-18.04 4.18.0.16.66 amd64Generic Linux kernel image ii linux-signed-generic-hwe-18.04 4.18.0.16.66 amd64Complete Signed Generic Linux kernel and headers (dummy transitional package) ii xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 amd64X.Org X server -- fbdev display driver Expected result: Video at 1920x1080 Actual result: Video limited to 800x600 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 10:36:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:17d1] InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FA 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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic resolution 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/1821533 Title: failure to detect
[Touch-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** Description changed: https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- - Watching movie 4k. + Watching movie 4k, forward and back. + ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed. Status in Mesa: Unknown Status in Totem: New Status in intel-vaapi-driver package in Ubuntu: New Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: Invalid Bug description: https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** Description changed: + https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed. Status in Mesa: Unknown Status in Totem: New Status in intel-vaapi-driver package in Ubuntu: New Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: Invalid Bug description: https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** Description changed: - https://gitlab.gnome.org/GNOME/totem/issues/315 + https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 + https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem) --- Watching movie 4k. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #110232 https://bugs.freedesktop.org/show_bug.cgi?id=110232 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=110232 Importance: Unknown Status: Unknown ** Changed in: totem (Ubuntu) Status: New => Invalid ** Description changed: https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 - https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem) + https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed. Status in Mesa: Unknown Status in Totem: New Status in intel-vaapi-driver package in Ubuntu: New Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: Invalid Bug description: https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop:
[Touch-packages] [Bug 682662] Re: pam-auth-update ignores debconf settings
...sorry ^^^ - %s/debconf-get-selections/debconf-set-selections/ of course :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/682662 Title: pam-auth-update ignores debconf settings Status in dpkg package in Ubuntu: Confirmed Status in pam package in Ubuntu: Triaged Status in pam package in Debian: Won't Fix Bug description: pam-auth-update ignores the current debconf-settings. This makes it impossible to do automatically configure pam in noninteractive installations. Demonstration: ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean true libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, ldap, tmpdir, gnome-keyring, consolekit libpam-runtimelibpam-runtime/you-had-no-auth error ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean false libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, winbind, ldap libpam-runtimelibpam-runtime/you-had-no-auth error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/682662/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
same here -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1821505] Re: screen cannot be turned back on after some time of inactivity
1) This has never been an issue, until upgrade to 16.04 LTS. 2) a) These are not workarounds, this are just ways of manually starting the screen blank, without triggering the bug. If you let the screen blank automatically, bug will still trigger. And once the bug is triggered, only restart of the desktop manager helps. b) Yes, I have tested these scenarios personally. 3) I've tested the daily build and the issue is not present there. -- 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/1821505 Title: screen cannot be turned back on after some time of inactivity Status in xorg package in Ubuntu: Incomplete Bug description: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. WORKAROUND: Type in a terminal: xset -display :0.0 dpms force off WORKAROUND: Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: gnome-screensaver-command -a WORKAROUND: When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821505/+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 1821528] [NEW] libedit applications segfault when passed long strings
Public bug reported: Applications using libedit to process user input segfault on Ubuntu 19.04 when they are passed a long input string. The issue can easily be reproduced with the example programs bundled with the library. The issue has been fixed in upstream NetBSD by this diff https://github.com/IIJ-NetBSD/netbsd- src/commit/2a926170e92dc4ab635b3c94c1e1bbbcc7f9494c , however the latest Linux port release (libedit-20181209-3.1.tar.gz) does not contain this fix. Applying it manually does indeed correct the issue, and the affected applications no longer crash. I have contacted the Linux port maintainer and I am awaiting for a response, however I would like to see this fixed in disco. Cosmic and older are not affected. I have attached a log demonstrating a crash, compiled with AddressSanitizer. ** Affects: libedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "libedit_asan.txt" https://bugs.launchpad.net/bugs/1821528/+attachment/5249080/+files/libedit_asan.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1821528 Title: libedit applications segfault when passed long strings Status in libedit package in Ubuntu: New Bug description: Applications using libedit to process user input segfault on Ubuntu 19.04 when they are passed a long input string. The issue can easily be reproduced with the example programs bundled with the library. The issue has been fixed in upstream NetBSD by this diff https://github.com/IIJ-NetBSD/netbsd- src/commit/2a926170e92dc4ab635b3c94c1e1bbbcc7f9494c , however the latest Linux port release (libedit-20181209-3.1.tar.gz) does not contain this fix. Applying it manually does indeed correct the issue, and the affected applications no longer crash. I have contacted the Linux port maintainer and I am awaiting for a response, however I would like to see this fixed in disco. Cosmic and older are not affected. I have attached a log demonstrating a crash, compiled with AddressSanitizer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1821528/+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 1821505] Re: screen cannot be turned back on after some time of inactivity
Hark, thank you for reporting this and helping make Ubuntu better. 1) To confirm a regression, has this always been an issue since you installed "Ubuntu-Server 10.04 LTS" or is this something that started to happen after an update? 2) To clarify, did you personally test the WORKAROUNDs noted in the Bug Description, and confirm this works for your hardware? 2) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Tags added: latest-bios-1.18 ** Description changed: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. - When I restart the display manager via ssh with another computer, the - screen then comes to life again and I can log back in. + WORKAROUND: Type in a terminal: + xset -display :0.0 dpms force off - There is no problem waking the screen when I type "xset -display :0.0 - dpms force off" in a terminal. Moreover typing gnome-screensaver-command - -a in a terminal turns my screen off and after typing this line, the - screen can be woken up by moving the mouse or by hitting a key. + WORKAROUND: Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: + gnome-screensaver-command -a + + WORKAROUND: When I restart the display manager via ssh with another + computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] + Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputLogitech USB Receiver KEYBOARD, id 8 - inputLogitech USB Receiver KEYBOARD, id 9 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputLogitech USB Receiver KEYBOARD, id 8
[Touch-packages] [Bug 1821512] [NEW] Asus ZenBook UX433FN No output sound in Ubuntu 18.04
Public bug reported: I've tried this solution: https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and so many solutions were similar to this. But they didn't work. I know that upgrading my kernel version from 4.18.5 to 4.20 will fix it. But I don't want to do that since 4.20 isn't a stable version. Is there any other way that someone could offer? I'll be grateful folks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.18.5-041805-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 16:26:57 2019 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1339 F pulseaudio hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "My system specs" https://bugs.launchpad.net/bugs/1821512/+attachment/5249016/+files/Screenshot%20from%202019-03-24%2016-32-41.png -- 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/1821512 Title: Asus ZenBook UX433FN No output sound in Ubuntu 18.04 Status in alsa-driver package in Ubuntu: New Bug description: I've tried this solution: https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and so many solutions were similar to this. But they didn't work. I know that upgrading my kernel version from 4.18.5 to 4.20 will fix it. But I don't want to do that since 4.20 isn't a stable version. Is there any other way that someone could offer? I'll be grateful folks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.18.5-041805-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 16:26:57 2019 InstallationDate: Installed on 2019-03-24 (0 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1339 F pulseaudio hmdvhb 1971 F pulseaudio hmdvhb 3050 F alsamixer /dev/snd/pcmC0D0c: hmdvhb 1971 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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:
[Touch-packages] [Bug 1821505] [NEW] screen cannot be turned back on after some time of inactivity
Public bug reported: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. There is no problem waking the screen when I type "xset -display :0.0 dpms force off" in a terminal. Moreover typing gnome-screensaver-command -a in a terminal turns my screen off and after typing this line, the screen can be woken up by moving the mouse or by hitting a key. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1821505 Title: screen cannot be turned back on after some time of inactivity Status in xorg package in Ubuntu: New Bug description: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. When I restart the display manager via ssh with another computer, the screen then comes to life again and I can log back in. There is no problem waking the screen when I type "xset -display :0.0 dpms force off" in a terminal. Moreover typing gnome-screensaver- command -a in a terminal turns my screen off and after typing this line, the screen can be woken up by moving the mouse or by hitting a key. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
[Touch-packages] [Bug 1821496] Re: Sennheiser GSX 1000/1200 Volume control is interpreted badly
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Sound(ALSA) -- 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/1821496 Title: Sennheiser GSX 1000/1200 Volume control is interpreted badly Status in systemd package in Ubuntu: New Bug description: These cards are picked up as having mute/VolUp/VolDown buttons, but they only ever report a VolDown. Windows behavior (without manually installed drivers) appears to match OS-side volume to the display on the card, which suggests the card tries to report its volume level as an absolute value. Ubuntu interprets it as turning the volume down (even if the volume was actually turned up). My workaround was to remap the "buttons" on the card to "reserved" using the hwdb and manage OS-side volume with media keys on my actual keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 90-pulseaudio-local.rules 70-snap.core.rules Date: Sat Mar 23 23:42:31 2019 InstallationDate: Installed on 2018-09-12 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=fec38878-ce70-47ad-a40b-7710266eb99b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E 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.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821496/+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 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
** Changed in: systemd Status: Unknown => 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/1790205 Title: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+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