[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
If it helps anyone, I have suggested a workaround in this Ask Ubuntu answer: https://askubuntu.com/a/263510/77322 -- 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/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. Update 2: I just encountered this issue with Kernel 4.9. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1684902] Re: browser unity app crashes apparmor profile
apport information ** Tags added: apport-collected xenial ** Description changed: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. - Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) - updated grub file, (4) reboot + Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2017-04-12 (8 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: webbrowser-app + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 + ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 + Syslog: + Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled + Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled + Tags: xenial + Uname: Linux 4.8.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "ApparmorPackages.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866063/+files/ApparmorPackages.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] PstreeP.txt
apport information ** Attachment added: "PstreeP.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866068/+files/PstreeP.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866065/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866067/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866066/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] ApparmorStatusOutput.txt
apport information ** Attachment added: "ApparmorStatusOutput.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866064/+files/ApparmorStatusOutput.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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
Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile
Dear Seth Arnold, Thank you for answering so quickly. I ran the command set you requested via terminal, and my system complained it did not have all needed program bits for the collection set, so I ran that and the updates to verify completion, then it opened launchpad site and I authenticated through that port. I just received a OAuth bounce from launchpad, so I assume you got the logs you needed. I will leave my system authorized (V2410US, which is the model of this old machine in case you need the hardware specs, the only thing I have changed is the RAM to 2GB) in launchpad so you can get other data if needed, just please let me know when to de-authorize the link, and I will be patient, so no hurry, no worry! Have a great day, Carl Fitzpatrick On 04/20/2017 07:39 PM, Seth Arnold wrote: > Hello Carl, thanks for the report; can you please run apport-collect > 1684902 to upload some logs that may help diagnose the issue? > > Thanks > > ** Information type changed from Private Security to Public Security > > ** Package changed: ubuntu => webbrowser-app (Ubuntu) > > ** Also affects: apparmor (Ubuntu) > Importance: Undecided > Status: New > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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
Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile
Dear Seth Arnold, Thank you again for the quick reply. I signed up for the Code of Conduct in the system, and I can try to reproduce the activity. Is there a better way to capture the effects and give you a snapshot of the activities as they occur? F.Y.I. What I am describing never caused a system crash, so I think we are safe in that regard. Best Always, Carl On 04/21/2017 06:56 PM, Seth Arnold wrote: > Thanks Carl; sadly the logs don't give me any better idea of what might > have happened. Can you reproduce the issue? It'd be helpful to see a log > of the messages involved. > > The logs attached without trouble; feel free to unlink whenever. (I > don't think it really matters one way or another.) > > Thanks > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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
Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile
Dear Seth Arnold, Here is the current state of the machine. I left the webbrowser-app removed so what you see is what I have, then I can test stuff for repair. Best Always, Carl On 04/21/2017 09:15 PM, Seth Arnold wrote: > Hi Carl, ideally you can copy-and-paste output from a terminal or > similar window. After that it gets more complicated to upload e.g. > photos or videos. > > Thanks > ** Attachment added: "Carlsentthisforbug1684902.txt" https://bugs.launchpad.net/bugs/1684902/+attachment/4866309/+files/Carlsentthisforbug1684902.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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
Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile
Dear Seth Arnold, You are welcome, and if I can help troubleshoot the fix, please let me know. I have been around since Burroughs R4K and CPM-DOS 1.0, just as an operator, but a pretty fair hand (I can follow directions about 98% of the time... wish I could get above my life "average" of 85% LOL!). Sincerely, Carl On 04/23/2017 06:00 PM, Seth Arnold wrote: > Beautiful! Thanks Carl. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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
Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile
Hi Marc Deslauriers, Thanks for the reply. I had not heard from anyone for a time, so I went ahead and re-installed the browser app, then reconfigured apparmor to stop all the system errors. It seemed to have fixed the problem (short term), but I put the package in you said was missing in the system, and all seems well in the system. Did you need a snapshot of any system items to confirm? By the way, this package was never shown as a missing dependency nor did apparmor give any obvious error for this package, or even when the webbrowser-app was removed, and I reconfigured and reinstalled apparmor. Also, it was never (as far as I know) part of the original .iso for the install (maybe it was missing from the repository?), nor did the updates catch it as missing, so really weird. Thank you for your attention in this matter. My Best to you and yours, Carl On 05/05/2017 09:16 AM, Marc Deslauriers wrote: > Hi Carl, it looks like you're missing the apparmor-easyprof-ubuntu > package. That package is necessary for proper operation. Could you > please reinstall it and try again? > > Thanks! > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: Incomplete Status in webbrowser-app package in Ubuntu: Invalid Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1684902] Re: browser unity app crashes apparmor profile
Just a quick update: All is well, all features and security sets are normal and online. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: Incomplete Status in webbrowser-app package in Ubuntu: Invalid Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
~$ systemd-inhibit Who: NetworkManager (UID 0/root, PID 686/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: Telepathy (UID 1000/carl, PID 1923/mission-control) What: shutdown:sleep Why: Disconnecting IM accounts before suspend/shutdown... Mode: delay Who: carl (UID 1000/carl, PID 1805/gnome-settings-) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: GNOME handling keypresses Mode: block Who: carl (UID 1000/carl, PID 1805/gnome-settings-) What: sleep Why: GNOME needs to lock the screen Mode: delay 4 inhibitors listed. -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Incomplete Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
~$ xrandr --query Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767 LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1366x768 59.64*+ 1360x768 59.8059.96 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 680x384 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I don't think it is 'Wrong detection of closed lid' as '/proc/acpi/button/lid/LID0/state' reports the open and close state correctly. -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
This finally solved the problem I had spent hours on! The computer in question is an Acer Aspire 5538 with Realtek ALC269. -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1994077] [NEW] GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve
Public bug reported: Issue with graphics card fan running at max RPM if either cpu or gpu are put under slight stress. Usually when graphics card temp goes above 50 degrees celsius, but also if the CPU is performing some intensive work. This has started ever since upgrading to Ubuntu 22.04. The actual GPU fan speed reported is sometimes misreported during these errors, and does not respond to manual control through CoreCTRL or via command-line, but it is definitely the GPU fan which is making the noise. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.1.0-060100rc1-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 24 22:52:32 2022 DistUpgraded: 2022-09-11 18:48:47,235 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:e353] InstallationDate: Installed on 2018-03-19 (1680 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Micro-Star International Co., Ltd. MS-7A33 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.1.0-060100rc1-generic root=UUID=49a0c4fb-2e67-4829-992f-626d1d40dc33 ro rootflags=subvol=@ resume=UUID=0841c49c-0031-4984-a508-c94b1cd49dd3 amdgpu.vm_fragment_size=9 amdgpu.ppfeaturemask=0x SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-11 (43 days ago) dmi.bios.date: 05/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.L3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PLUS (MS-7A33) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.L3:bd05/25/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr3.0:rvnMSI:rnX370GAMINGPLUS(MS-7A33):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.2~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.2~kisak1~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Thu Apr 15 23:58:44 2021 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance third-party-packages 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/1994077 Title: GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve Status in xorg package in Ubuntu: New Bug description: Issue with graphics card fan running at max RPM if either cpu or gpu are put under slight stress. Usually when graphics card temp goes above 50 degrees celsius, but also if the CPU is performing some intensive work. This has started ever since upgrading to Ubuntu 22.04. The actual GPU fan speed reported is sometimes misreported during these errors, and does not respond to manual control through CoreCTRL or via command-line, but it is definitely the GPU fan which is making the noise. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.1.0-060100rc1-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 24 22:52:32
[Touch-packages] [Bug 1994077] Re: GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve
seems like a hardware problem affecting as it affects only one of the two GPU fans. I think that this bug report can be disregarded. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1994077 Title: GPU fan goes at 100% during mild-moderate activity, disregarding built fan curve or custom fan curve Status in xorg package in Ubuntu: Invalid Bug description: Issue with graphics card fan running at max RPM if either cpu or gpu are put under slight stress. Usually when graphics card temp goes above 50 degrees celsius, but also if the CPU is performing some intensive work. This has started ever since upgrading to Ubuntu 22.04. The actual GPU fan speed reported is sometimes misreported during these errors, and does not respond to manual control through CoreCTRL or via command-line, but it is definitely the GPU fan which is making the noise. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.1.0-060100rc1-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 24 22:52:32 2022 DistUpgraded: 2022-09-11 18:48:47,235 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:e353] InstallationDate: Installed on 2018-03-19 (1680 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Micro-Star International Co., Ltd. MS-7A33 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.1.0-060100rc1-generic root=UUID=49a0c4fb-2e67-4829-992f-626d1d40dc33 ro rootflags=subvol=@ resume=UUID=0841c49c-0031-4984-a508-c94b1cd49dd3 amdgpu.vm_fragment_size=9 amdgpu.ppfeaturemask=0x SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-11 (43 days ago) dmi.bios.date: 05/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.L3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PLUS (MS-7A33) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.L3:bd05/25/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr3.0:rvnMSI:rnX370GAMINGPLUS(MS-7A33):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.2~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.2~kisak1~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Thu Apr 15 23:58:44 2021 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1994077/+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 1903765] Re: Subwoofer mapped incorrectly on Macbook 2.1
This problem persists on the same system with all the latest updates. I
did however notice that in the "hardware" part of the GUI there is no
longer a "2.1" option, so defaulting to analogue stereo output.
I tried connecting an external speaker ("headphone") and it sounded as
it should.
--
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/1903765
Title:
Subwoofer mapped incorrectly on Macbook 2.1
Status in alsa-driver package in Ubuntu:
New
Bug description:
It seems the 2.0 speakers get mapped to Speaker and the subwoofer is
mapped to HEADPHONES, not LFE. I confirmed this by raising the volume
for "headphones" in alsamixer and getting the base to play along.
However, there seems to be no workaround in Ubuntu just using the
sound GUI. My guess is, if ALSA would do the mapping to LFE correctly,
I could use the 2.1 hardware map in the Ubuntu sound settings and all
would be well!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diskdoc3271 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Nov 10 21:33:29 2020
InstallationDate: Installed on 2020-10-08 (33 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Inbyggt ljud - HDA Intel
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HDA Intel, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias:
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.family: MacBook
dmi.product.name: MacBook2,1
dmi.product.sku: System SKUNumber
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+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 645404] Re: Support Private PPAs
please consider the CI case: headless process that runs periodically for months without user interaction. something like: deploy a private key (or similarly sensitive secret) file and a publicly readable script (apt-add-repository...) and it just runs, no browser, no user, no typing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Triaged Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1771358] [NEW] qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic
Public bug reported: I'm trying to build the CUBE gui using the PGU compiler. This depends on qt5-qmake. The amd64 / 16.04 build https://packages.ubuntu.com/xenial/qt5-qmake https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist contains these two files /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h but the and64 / 18.04 version does not https://packages.ubuntu.com/bionic/qt5-qmake https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist Is this an oversight? Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1771358 Title: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic Status in qtbase-opensource-src package in Ubuntu: New Bug description: I'm trying to build the CUBE gui using the PGU compiler. This depends on qt5-qmake. The amd64 / 16.04 build https://packages.ubuntu.com/xenial/qt5-qmake https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist contains these two files /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h but the and64 / 18.04 version does not https://packages.ubuntu.com/bionic/qt5-qmake https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist Is this an oversight? Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1771358/+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 1771358] Re: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic
Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1771358 Title: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic Status in qtbase-opensource-src package in Ubuntu: New Bug description: I'm trying to build the CUBE gui using the PGU compiler. This depends on qt5-qmake. The amd64 / 16.04 build https://packages.ubuntu.com/xenial/qt5-qmake https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist contains these two files /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h but the and64 / 18.04 version does not https://packages.ubuntu.com/bionic/qt5-qmake https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist Is this an oversight? Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1771358/+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 1771358] Re: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic
The file is also missing in the i386 / 18.04 build https://packages.ubuntu.com/bionic/i386/qt5-qmake https://packages.ubuntu.com/bionic/i386/qt5-qmake/filelist I haven't looked at the others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1771358 Title: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic Status in qtbase-opensource-src package in Ubuntu: New Bug description: I'm trying to build the CUBE gui using the PGU compiler. This depends on qt5-qmake. The amd64 / 16.04 build https://packages.ubuntu.com/xenial/qt5-qmake https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist contains these two files /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h but the and64 / 18.04 version does not https://packages.ubuntu.com/bionic/qt5-qmake https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist Is this an oversight? Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1771358/+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 1771358] Re: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic
Ok got it. Right now I'm looking at building the CUBE gui components with the system base=environment (g++) and building only the I/O libraries for each compiler, in which case I won't need to use the qmake/pgi combination. But if I find I do need it, I can try testing the pgcc files from 16.04 inside the new version of the package, and get back to you with the results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1771358 Title: qt5-qmake contains mkspecs/linux-pgcc in xenial but not bionic Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: I'm trying to build the CUBE gui using the PGU compiler. This depends on qt5-qmake. The amd64 / 16.04 build https://packages.ubuntu.com/xenial/qt5-qmake https://packages.ubuntu.com/xenial/amd64/qt5-qmake/filelist contains these two files /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qmake.conf /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-pgcc/qplatformdefs.h but the and64 / 18.04 version does not https://packages.ubuntu.com/bionic/qt5-qmake https://packages.ubuntu.com/bionic/amd64/qt5-qmake/filelist Is this an oversight? Also, when I tried to file this bug the first time, the tracker said "qt5-qmake" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know" This doesn't make any sense, since this is the name presented on your web-page. The search option gave me a list of packages that didn't look closely related, either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1771358/+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 1733487] [NEW] installer created invaid username
Public bug reported: Using this d-i passwd/user-fullname string Video Team User but not # d-i passwd/username string juser I am prompted for a username, defaults to "video" I accept that default, and it tells me it is invalid. I'm guessing thing that constructed the username should check against the blacklist mentioned here: "According to the comments in the list of reserved user names," https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450954 ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- 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/1733487 Title: installer created invaid username Status in debian-installer package in Ubuntu: New Bug description: Using this d-i passwd/user-fullname string Video Team User but not # d-i passwd/username string juser I am prompted for a username, defaults to "video" I accept that default, and it tells me it is invalid. I'm guessing thing that constructed the username should check against the blacklist mentioned here: "According to the comments in the list of reserved user names," https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450954 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1733487/+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 1733487] Re: installer created invaid username
policykit-1 ?! I will swear I picked debian-installer ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** No longer affects: policykit-1 (Ubuntu) -- 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/1733487 Title: installer created invaid username Status in debian-installer package in Ubuntu: New Bug description: Using this d-i passwd/user-fullname string Video Team User but not # d-i passwd/username string juser I am prompted for a username, defaults to "video" I accept that default, and it tells me it is invalid. I'm guessing thing that constructed the username should check against the blacklist mentioned here: "According to the comments in the list of reserved user names," https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450954 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1733487/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
I had the same issue. I found https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-updates-2018-01-04-compiz-segfaults first and followed the directions there. It resolved my problem. -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1476343] Re: Freeze on screensaver deactivate when set to lock on screensaver activate
apport information ** Tags added: apport-collected ubuntu ** Description changed: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light-locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.15 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: XFCE + DistUpgraded: Fresh install + DistroCodename: trusty + DistroRelease: Ubuntu 14.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] + NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] + InstallationDate: Installed on 2014-07-22 (461 days ago) + InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + LightdmGreeterLog: + ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory + init: indicator-power main process (3022) killed by TERM signal + init: indicator-application main process (3031) killed by TERM signal + LightdmGreeterLogOld: + ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory + init: indicator-power main process (2949) killed by TERM signal + init: indicator-application main process (2958) killed by TERM signal + MachineType: Micro-Star International Co., Ltd. GT70 2PC + Package: xorg 1:7.7+1ubuntu8.1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 + Tags: trusty ubuntu + Uname: Linux 3.13.0-65-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark + _MarkForUpload: True + dmi.bios.date: 02/12/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E1763IMS.70T + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: MS-1763 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:0.C + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: + dmi.product.name: GT70 2PC + dmi.product.version: REV:0.C + dmi.sys.vendor: Micro-Star International Co., Ltd. + version.compiz: compiz N/A + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 + version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 + version.xserver-xo
[Touch-packages] [Bug 1476343] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506099/+files/BootLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1476343] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506100/+files/CurrentDmesg.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2:
[Touch-packages] [Bug 1476343] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506102/+files/DpkgLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1476343] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506104/+files/LightdmLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: lib
[Touch-packages] [Bug 1476343] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506103/+files/LightdmDisplayLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A versio
[Touch-packages] [Bug 1476343] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506101/+files/Dependencies.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2:
[Touch-packages] [Bug 1476343] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506111/+files/UdevDb.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.
[Touch-packages] [Bug 1476343] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506114/+files/XorgLogOld.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: lib
[Touch-packages] [Bug 1476343] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506108/+files/ProcEnviron.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: l
[Touch-packages] [Bug 1476343] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506116/+files/xdpyinfo.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1476343] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506115/+files/Xrandr.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.
[Touch-packages] [Bug 1476343] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506106/+files/Lsusb.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60
[Touch-packages] [Bug 1476343] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506107/+files/ProcCpuinfo.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: l
[Touch-packages] [Bug 1476343] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506112/+files/UdevLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1476343] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506117/+files/xserver.devices.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.li
[Touch-packages] [Bug 1476343] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506109/+files/ProcInterrupts.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libd
[Touch-packages] [Bug 1476343] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506113/+files/XorgLog.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1476343] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506105/+files/Lspci.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60
[Touch-packages] [Bug 1476343] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1476343/+attachment/4506110/+files/ProcModules.txt -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo usrp wireshark _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1763IMS.70T dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1763 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A: dmi.product.name: GT70 2PC dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: l
[Touch-packages] [Bug 1476343] Re: Freeze on screensaver deactivate when set to lock on screensaver activate
Hi, Christopher. Thanks for all the helpful links! Indeed, I applied the BIOS update, and the hard freeze is now gone! It's not all working exactly as I expect, but at least the BIOS change cured the worst symptom. Changes made: Applied MSI BIOS update to version 71D. Changed light-locker back to activate on screensaver activate. New behavior when coming back to laptop with locked screen: Make a movement on the touchpad. Screen remains completely black, BUT computer is still running properly, as shown by network traffic. Click the mouse buttons. Same thing, screen remains completely black, but no hard crash; everything is still running. Press some non-typing keys (shift, ctrl, etc.). Same thing. Blindly type my password into the completely black screen. Screen turns on, unlocks, and shows me my full working X environment, exactly as I'd left it. Which is at least usable. Not ideal, and not what I think is expected behavior, but behavior I can deal with. chaz@cesium:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for chaz: E1763IMS.71D 04/17/2015 chaz@cesium:~$ -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: Incomplete Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1106] InstallationDate: Installed on 2014-07-22 (461 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:2919): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (3022) killed by TERM signal init: indicator-application main process (3031) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2831): WARNING **: Failed to load user image: Failed to open file '/home/chaz/.face': No such file or directory init: indicator-power main process (2949) killed by TERM signal init: indicator-application main process (2958) killed by TERM signal MachineType: Micro-Star International Co., Ltd. GT70 2PC Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@ rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Tags: trusty ubuntu Uname: Linux 3.13.0-65-generic x86_64
[Touch-packages] [Bug 1455132] [NEW] libdrm2 update causes xorg freeze with r128 driver
Public bug reported: Using Ubuntu's stable 14.04 branch; X.Org X Server 1.15.1; Ati Rage R128 module v. 6.9.2 , on restart after updating libdrm2 to version libdrm2_2.4.60-2~ubuntu14.04 xorg froze immediately after a reboot; Upon closer inspection, I was able to switch out to a virtual console, after pressing the appropriate keys, but only after a very unusually long delay. In another attempt starting Xorg I noticed that it seemed something was actually rendered, even if just a single frame in a few minutes.. Downgrading libdrm2 to version 2.4.52-1 restored Xorg to its usual behavior; therefore libdrm2 seems the likely culprit of this problem, which perhaps only occurs in conjunction with the usage of this not very common r128 module ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libdrm2 2.4.60-2~ubuntu14.04.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CurrentDesktop: LXDE Date: Thu May 14 17:31:39 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 InstallationDate: Installed on 2014-08-16 (271 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1455132 Title: libdrm2 update causes xorg freeze with r128 driver Status in libdrm package in Ubuntu: New Bug description: Using Ubuntu's stable 14.04 branch; X.Org X Server 1.15.1; Ati Rage R128 module v. 6.9.2 , on restart after updating libdrm2 to version libdrm2_2.4.60-2~ubuntu14.04 xorg froze immediately after a reboot; Upon closer inspection, I was able to switch out to a virtual console, after pressing the appropriate keys, but only after a very unusually long delay. In another attempt starting Xorg I noticed that it seemed something was actually rendered, even if just a single frame in a few minutes.. Downgrading libdrm2 to version 2.4.52-1 restored Xorg to its usual behavior; therefore libdrm2 seems the likely culprit of this problem, which perhaps only occurs in conjunction with the usage of this not very common r128 module ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libdrm2 2.4.60-2~ubuntu14.04.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CurrentDesktop: LXDE Date: Thu May 14 17:31:39 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 InstallationDate: Installed on 2014-08-16 (271 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1455132/+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 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out
I see this behavior when using the Intel Wireless 3160, however, when using a USB TP-Link TL-WN722N, I can connect just fine without getting the "wlan0: authentication with xx:xx:xx:xx:xx:xx timed out". @elopio, can you do a similar experiment? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1441893 Title: Can't connect to my wi-fi N network on vivid: authentication timed out Status in NetworkManager: New Status in network-manager package in Ubuntu: Incomplete Bug description: I can't connect to my wi-fi with my laptop. I get this error message in the syslog. Apr 8 22:25:35 ubuntu kernel: [ 793.89] wlan0: authentication with 10:bf:48:e5:d1:b8 timed out ubuntu@ubuntu:~$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: Ethernet Connection I217-V vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: eth0 version: 05 serial: 00:90:f5:f8:ef:86 size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff ioport:f080(size=32) *-network description: Wireless interface product: Wireless 3160 vendor: Intel Corporation physical id: 0 bus info: pci@:03:00.0 logical name: wlan0 version: 83 serial: a0:88:69:39:ae:d6 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn resources: irq:32 memory:f7c0-f7c01fff Attached is the full syslog. This machine has been working more or less ok on vivid for at least three months. Sometimes it refused to connect to the wi-fi, but after a restart it started working. Recently I changed the network from G to N, and recently did an upgrade to the latest vivid. I had some problems booting, so I also recently fully removed upstart. It boots fine with systemd, and everything else seem to be working. I've just tested with a daily vivid live USB, and the same problem happened. I'm connecting to the same network using the same password with my other machine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CasperVersion: 1.356 CurrentDesktop: Unity Date: Wed Apr 8 22:20:03 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.2.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.208 LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 cf5cb021-0df1-4f13-b74c-c3e9c6749a30 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1441893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1461713] [NEW] nvidia-173 fails to install
Public bug reported: I think software-properties should be tagged in this since it offers to install nvidia-173 (but fails to do so). One of these two packages should be changed so that the driver is installed or so it isn't offered. Terminal output: "root@sempron:~# LANG=EN && apt-get install nvidia-173 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-173 : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. root@sempron:~# " ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-common 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 01:55:02 2015 InstallationDate: Installed on 2015-04-03 (61 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all ProcEnviron: LANGUAGE=sv_FI:sv TERM=xterm PATH=(custom, no user) LANG=sv_FI.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1461713 Title: nvidia-173 fails to install Status in software-properties package in Ubuntu: New Bug description: I think software-properties should be tagged in this since it offers to install nvidia-173 (but fails to do so). One of these two packages should be changed so that the driver is installed or so it isn't offered. Terminal output: "root@sempron:~# LANG=EN && apt-get install nvidia-173 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-173 : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. root@sempron:~# " ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-common 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 01:55:02 2015 InstallationDate: Installed on 2015-04-03 (61 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all ProcEnviron: LANGUAGE=sv_FI:sv TERM=xterm PATH=(custom, no user) LANG=sv_FI.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1461713/+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 1450009] Re: suspends on closed lid, does not recognized external monitors/dock
Also seeing this issue when simply closing laptop lid (Razer Blade 2015). Clicking Suspend does not trigger this bug. It does NOT trigger if I click Suspend, close lid, re-open lid. It only seems to trigger when physically closing the lid while the machine is on. -- 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/1450009 Title: suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Confirmed Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1723470] [NEW] package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists
Public bug reported: windows bash update from 14.04 to 16.04 using sudo do-version-upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iptables 1.4.21-1ubuntu1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Fri Oct 13 10:01:29 2017 Dmesg: [0.00] DuplicateSignature: package:iptables:1.4.21-1ubuntu1:unable to install new version of '/lib/xtables/libipt_ttl.so': File exists ErrorMessage: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: iptables Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists UpgradeStatus: Upgraded to xenial on 2017-10-13 (0 days ago) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages uec-images xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1723470 Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists Status in iptables package in Ubuntu: New Bug description: windows bash update from 14.04 to 16.04 using sudo do-version-upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iptables 1.4.21-1ubuntu1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Fri Oct 13 10:01:29 2017 Dmesg: [0.00] DuplicateSignature: package:iptables:1.4.21-1ubuntu1:unable to install new version of '/lib/xtables/libipt_ttl.so': File exists ErrorMessage: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: iptables Title: package iptables 1.4.21-1ubuntu1 failed to install/upgrade: unable to install new version of '/lib/xtables/libipt_ttl.so': File exists UpgradeStatus: Upgraded to xenial on 2017-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1723470/+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 520546] Re: Alt-f2 switches to virtual terminal 2
Alt + f4 usually closes windows for me. But from time to time, it switches to tty 4. I am certain I am not accidentally hitting ctrl :) Dell Precision 5520 Ubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Confirmed Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 520546] Re: Alt-f2 switches to virtual terminal 2
@Andres It is not permanently like this. Most often Alt + f4 does not change to the tty. Only occasionally does it do it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Confirmed Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 257135] Re: notify-send(1) can't replace an existing notification
** Bug watch added: Debian Bug tracker #559544 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544 ** Also affects: libnotify (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/257135 Title: notify-send(1) can't replace an existing notification Status in libnotify package in Ubuntu: Confirmed Status in libnotify package in Debian: Unknown Bug description: Binary package hint: libnotify-bin Ubuntu 8.04, libnotify-bin 0.4.4-3build1. notify-send(1) is very useful but it doesn't tell me the notification ID that's been created, nor does it let me specify that to replace an earlier notification. See http://www.galago- project.org/specs/notification/0.9/x408.html#command-notify, in particular the replaces_id parameter and the return value. I'd like to be able to use it something like id=$(notify-send --show-id foo) sleep 60 notify-send --replace $id bar This would be great for long-running shell scripts that are monitoring something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
Suspend fixes problem for me. Dell Precision 5520. -- 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/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1609700] Re: username is not saved in openconnect connection dialog
I was having the same problem, and updating to 16.04.2 was the solution for me, specifically sudo apt-get -y dist-upgrade given that I was already running 16.04. The problem had also been reported here https://askubuntu.com/questions/835556/network-manager-doesnt- remember-login-username/913179?noredirect=1#comment1438576_913179 and solved the same way. I'd suggest that this bug be considered closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1824088] [NEW] unattended upgrade ran one day after schedule
Public bug reported: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Log data from apt" https://bugs.launchpad.net/bugs/1824088/+attachment/5254614/+files/history.txt ** Attachment removed: "Log data from apt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5254614/+files/history.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: New Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com
[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule
** Attachment added: "Log data from apt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5254618/+files/history.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: New Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The pulseaudio installed on my Ubuntu 20.04.1 systems is the following: pulseaudio - 1:13.99.1-1ubuntu3.5 deleting ~/.config/pulse and reboot fixed the problem of sound being directed to builtin speakers instead of the headphones although headphones were selected as the output device. Verified this on a Dell XPS labtop and an AMD desktop. Until 1:13.99.1-1ubuntu6 is released, I recommend deleting the config file and rebooting. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Released Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (Ubuntu) Importance: Undecided Status: 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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook Status in xorg package in Ubuntu: New Bug description: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver-xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+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 1903765] [NEW] Subwoofer mapped incorrectly on Macbook 2.1
Public bug reported: It seems the 2.0 speakers get mapped to Speaker and the subwoofer is mapped to HEADPHONES, not LFE. I confirmed this by raising the volume for "headphones" in alsamixer and getting the base to play along. However, there seems to be no workaround in Ubuntu just using the sound GUI. My guess is, if ALSA would do the mapping to LFE correctly, I could use the 2.1 hardware map in the Ubuntu sound settings and all would be well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc3271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 10 21:33:29 2020 InstallationDate: Installed on 2020-10-08 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Inbyggt ljud - HDA Intel Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.sku: System SKUNumber dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1903765 Title: Subwoofer mapped incorrectly on Macbook 2.1 Status in alsa-driver package in Ubuntu: New Bug description: It seems the 2.0 speakers get mapped to Speaker and the subwoofer is mapped to HEADPHONES, not LFE. I confirmed this by raising the volume for "headphones" in alsamixer and getting the base to play along. However, there seems to be no workaround in Ubuntu just using the sound GUI. My guess is, if ALSA would do the mapping to LFE correctly, I could use the 2.1 hardware map in the Ubuntu sound settings and all would be well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc3271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 10 21:33:29 2020 InstallationDate: Installed on 2020-10-08 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Inbyggt ljud - HDA Intel Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.sku: System SKUNumber dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+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/ListHel
[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule
If we look at lines 131 and 132 in /usr/lib/apt/apt.systemd.daily, we
will se the following:
interval="${interval%d}"
interval=$((interval*60*60*24))
I’m not 100% certain but I think that this time logic is what cause the
bug to occur, in accordance with what Magnus has pointed out in his
comments.
(It’s possible that lines 122-130 are also relevant.)
Any ideas on how to modify the code in order to avoid this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1824088
Title:
unattended upgrade ran one day after schedule
Status in apt package in Ubuntu:
Confirmed
Bug description:
I have noticed a strange behaviour in unattended upgrades. The host in
question is scheduled to run upgrades on Mondays every second week.
However, this week it ran upgrades on Tuesday instead (2019-04-09).
This is the first time I’ve noticed this behaviour. I checked the logs
in /var/log/apt/history.log* and I saw that worked as intended up
until this week. Upgrades ran as expected on 2019-03-11 and
2019-03-25, which where both Mondays.
The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
"14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.
Could it be daylight savings time that has caused skewing of the
schedule?
The server is located in Sweden and on 2019-03-31 we switched from CET
to CEST. If the time diff is calculated with hours instead of calendar
days passed, perhaps the missing hour on 2019-03-31 caused the
scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
had not yet passed.
ADDITIONAL INFO
Description:Ubuntu 16.04.6 LTS
Release:16.04
apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
1.2.31 500
500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
*** 1.2.29ubuntu0.1 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
1.2.10ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
*** 0.90ubuntu0.10 500
500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.29ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Apr 10 09:06:49 2019
InstallationDate: Installed on 2017-12-28 (467 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1824088] Re: unattended upgrade ran one day after schedule
How about this idea? What if we add this line to the beginning of usr/lib/apt/apt.systemd.daily: export TZ="UTC0" (I got this idea from the GNU Coreutils manual. See https://www.gnu.org/software/coreutils/manual/html_node/Relative-items- in-date-strings.html) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: Confirmed Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1824088] Re: unattended upgrade ran one day after schedule
Awesome work Magnus. Well done! Since the bug is related to APT, is Debian then considered the upstream of this source? Would it be appropriate to also file a bug in their bug tracker? If so, I can arrange that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: Confirmed Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1871182] Re: [RTL810xE] No ethernet connection
@Paolo, I have this too: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873526 your -25 test kernel did work for me. [0.930604] r8169 :01:00.0: can't disable ASPM; OS doesn't have ASPM control [0.930615] ahci :00:17.0: version 3.0 [0.937784] libphy: r8169: probed [0.938205] r8169 :01:00.0 eth0: RTL8106e, a0:8c:fd:7e:9a:37, XID 449, IRQ 125 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1881498] [NEW] Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
Public bug reported: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "After putting orienting the screens how I want them to be and click apply it gets scrambled like that" https://bugs.launchpad.net/bugs/1881498/+attachment/5379099/+files/Screenshot%20from%202020-05-31%2017-21-31.png -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: S
[Touch-packages] [Bug 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
** Attachment added: "The screens, how I order them before I click apply." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881498/+attachment/5379186/+files/Screenshot%20from%202020-05-31%2017-22-04.png -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
[Touch-packages] [Bug 1413411] [NEW] underscore in mounted drive name mishandled in menu
Public bug reported: If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct "host_S" name; the bug is only in the right-click menu. Note that right-clicking on the "Files" icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 22 11:51:46 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413411 Title: underscore in mounted drive name mishandled in menu Status in unity package in Ubuntu: New Bug description: If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct "host_S" name; the bug is only in the right-click menu. Note that right-clicking on the "Files" icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 22 11:51:46 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1413411/+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 1322589] Re: Screen flickers when running game Sins of a Solar Empire
Installing and using Wine 1.7.41-staging under PlayOnLinux (still in Ubuntu 14.10) seems to resolve this problem for me. As this is not the default Wine in Ubuntu, I guess this is still a bug.. -- 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/1322589 Title: Screen flickers when running game Sins of a Solar Empire Status in mesa package in Ubuntu: Confirmed Bug description: Problem appeared after update from Ubuntu 13.10 to 14.04. Game worked fine in Saucy with both radeon and fglrx. Now in Trusty only works with fglrx. Using radeon driver gives heavy flickering (about 0,5s intervals) when running the game (through PlayOnLinux/WINE). I expect some other games of other users will have the same problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libegl1-mesa 10.1.0-4ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,animation,workarounds,vpswitch,move,imgpng,expo,compiztoolbox,snap,unitymtgrabhandles,mousepoll,resize,grid,wall,fade,gnomecompat,place,ezoom,session,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 23 14:36:12 2014 DistUpgraded: 2014-04-19 17:11:14,002 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.11.0-19-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobility Radeon HD 5650 [1025:0364] InstallationDate: Installed on 2010-06-07 (1445 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) MachineType: Acer Aspire 3820 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8b7cae99-dae3-4d14-bbd3-24f82a9e0b57 ro quiet splash rootflags=data=writeback acpi_osi=Linux vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-19 (33 days ago) dmi.bios.date: 10/27/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.19 dmi.board.asset.tag: No Asset Tag dmi.board.name: JM31_CP dmi.board.vendor: Acer dmi.board.version: V1.19 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd10/27/2010:svnAcer:pnAspire3820:pvrV1.19:rvnAcer:rnJM31_CP:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.name: Aspire 3820 dmi.product.version: V1.19 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 23 13:44:19 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1322589/+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 1363070] Re: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected
I have a Dell Latitude E6500. I'd seen this problem with my 3-button IBM USB mouse, but it went away when I upgraded from Ubuntu 10.04 to 12.04. I have another external IBM USB mouse, this one with a wheel, and am still seeing the problem. So far I can temporarily stop the problem by un-plugging & re-plugging the mouse; I can also temporarily stop the problem with the command xinput set-prop 13 "Device Enabled" 0 One thing to note is that the temporary fix works even if the device number DOES NOT match the AlpsPS/2 ALPS DualPoint TouchPad. I don't believe the issue is a conflict between the two devices for this reason. I think that the mouse-driver is getting into some crudded-up state that gets reset when I unplug/replug the device or if I run the above "xinput" command. My best guess is that Ubuntu has real drivers for some mice and uses a buggy default-driver for anything else, and 12.04 included a driver for my first mouse but not my second mouse. Can anyone at Ubuntu confirm this? Or give us a better explanation? -- 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/1363070 Title: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected Status in “xorg” package in Ubuntu: New Bug description: This happens when two PS/2 devices are connected at the same time and a USB mouse is primarily used (eg using a Laptop with a PS/2 touchpad with an external USB mouse) Symptoms: after a while (can be 10 minutes or 1 hour) the mouse cursor starts randomly to jump (mostly down) and up and then the mouse buttons get deactivated (clicking does not have any effect). In that case, moving the mouse marks the underlying text (thus imitating a continuous left-click). This malbehaviour can be temporarily stopped when shortly using one PS/2 device. After a while the same symptoms reappear. Setup: Dell D430 docked to a Dell D/dock PD01x. The second PS/2 device is an (switched off) Logitech TrackMan Live! (infrared mouse connected via a PS/2 receiver). This bug appears under 12.04 LTS Unity and 14.04 with Xfce, KDE or Unity (always using the latest kernels). Using KDE the bug appears more often than when using XFCE. To resolve the issue: disconnect the external Trackman Live PS/2 device from the docking station. This bug drove me crazy. Only by accident I disconnected the Trackman and since then my USB mouse works well again. I verified that the bug reappears as soon as I connect the TrackMan again and I used different USB mice (as I thought that it might be a USB problem). It did not happen under Windows, so it is not hardware related. If this bug is going to be followed up I can test with a normal PS/2 mouse (instead of the TrackMan Live) if the same bug happens or would be happy to provide logging data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1363070/+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 1363070] Re: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected
Here's some info that actually makes sense, it says that the wheel-mice use a 4-byte protocol and the Touchpad uses a 3-byte protocol. This could explain how the driver could get confused. Anyone comment? http://blogs.msdn.com/b/oldnewthing/archive/2004/09/17/230839.aspx Yeah, this is a Windows-affiliated website, but the electronics sounds like an OS-independent issue. One question is whether the problem re-occurs the first time that you inadvertantly touch the Touchpad. -- 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/1363070 Title: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected Status in “xorg” package in Ubuntu: New Bug description: This happens when two PS/2 devices are connected at the same time and a USB mouse is primarily used (eg using a Laptop with a PS/2 touchpad with an external USB mouse) Symptoms: after a while (can be 10 minutes or 1 hour) the mouse cursor starts randomly to jump (mostly down) and up and then the mouse buttons get deactivated (clicking does not have any effect). In that case, moving the mouse marks the underlying text (thus imitating a continuous left-click). This malbehaviour can be temporarily stopped when shortly using one PS/2 device. After a while the same symptoms reappear. Setup: Dell D430 docked to a Dell D/dock PD01x. The second PS/2 device is an (switched off) Logitech TrackMan Live! (infrared mouse connected via a PS/2 receiver). This bug appears under 12.04 LTS Unity and 14.04 with Xfce, KDE or Unity (always using the latest kernels). Using KDE the bug appears more often than when using XFCE. To resolve the issue: disconnect the external Trackman Live PS/2 device from the docking station. This bug drove me crazy. Only by accident I disconnected the Trackman and since then my USB mouse works well again. I verified that the bug reappears as soon as I connect the TrackMan again and I used different USB mice (as I thought that it might be a USB problem). It did not happen under Windows, so it is not hardware related. If this bug is going to be followed up I can test with a normal PS/2 mouse (instead of the TrackMan Live) if the same bug happens or would be happy to provide logging data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1363070/+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 1372596] [NEW] /etc/cups/printers.conf rewritten with wrong information at every reboot
Public bug reported:
When I boot up my system, /etc/cups/printers.conf has the wrong device
URI for my printer. I've tried:
A) correcting it through the cups web GUI at localhost:631
B) substituting a corrected printers.conf by hand by performing:
service cups stop
cp -a /etc/cups/printers.conf.correct /etc/cups/printers.conf
service cups start
Both means correct the problem, and I can print again... UNTIL I reboot.
After the next boot, the incorrect URI is back in printers.conf and I
can't print again.
I can't find where the bad URI is respawning from.
find /etc /var /home -type d -exec grep -H '{}' \;
-print
comes up with nothing. It's got to be cached somewhere, though it appears not
in textual form. Where does this bad URI keep growing back from and how do I
stop it?!?!?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CupsErrorLog:
CurrentDesktop: XFCE
Date: Mon Sep 22 11:00:49 2014
InstallationDate: Installed on 2014-07-22 (61 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
KernLog:
Lpstat: device for Brother8680DN:
ipp://192.168.150.203:631/printers/Brother8680DN
MachineType: Micro-Star International Co., Ltd. GT70 2PC
Papersize: letter
PpdFiles: Brother8680DN: Brother MFC-8680DN BR-Script3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic
root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@
rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1763IMS.70T
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1763
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.C
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A:
dmi.product.name: GT70 2PC
dmi.product.version: REV:0.C
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cups printers.conf rewrite trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1372596
Title:
/etc/cups/printers.conf rewritten with wrong information at every
reboot
Status in “cups” package in Ubuntu:
New
Bug description:
When I boot up my system, /etc/cups/printers.conf has the wrong device
URI for my printer. I've tried:
A) correcting it through the cups web GUI at localhost:631
B) substituting a corrected printers.conf by hand by performing:
service cups stop
cp -a /etc/cups/printers.conf.correct /etc/cups/printers.conf
service cups start
Both means correct the problem, and I can print again... UNTIL I
reboot. After the next boot, the incorrect URI is back in
printers.conf and I can't print again.
I can't find where the bad URI is respawning from.
find /etc /var /home -type d -exec grep -H '{}' \;
-print
comes up with nothing. It's got to be cached somewhere, though it appears
not in textual form. Where does this bad URI keep growing back from and how do
I stop it?!?!?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CupsErrorLog:
CurrentDesktop: XFCE
Date: Mon Sep 22 11:00:49 2014
InstallationDate: Installed on 2014-07-22 (61 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
KernLog:
Lpstat: device for Brother8680DN:
ipp://192.168.150.203:631/printers/Brother8680DN
MachineType: Micro-Star International Co., Ltd. GT70 2PC
Papersize: letter
PpdFiles: Brother8680DN: Brother MFC-8680DN BR-Script3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic
root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@
rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1763IMS.70T
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1763
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.C
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.t
[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present
I don't want to revert the original fix because I don't think that gets us to a better place. With that fix in place, at least deployers have a chance of seeing from the sanity check that they need to update dnsmasq to a higher minimum version in order to use stateful IPv6. If they see it and update dnsmasq, then stateful IPv6 has a chance of working. If we revert then we have no chance of it working. Ideally, from a end user's point of view, we'd generate an API error if the agents aren't going to be able to handle a stateful IPv6 subnet. So, I think we should work toward that. But, to accomplish that, we'll end up with a fix that cannot be backported to Newton, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: In Progress Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1618288] [NEW] wget using "if-modified-since" is not idempotent and corrupts downloaded copy of website on second use
Public bug reported: I use wget to copy a web site from one server to another, adjusting file suffixes and paths. Since updating to 16.04 LTS from 14.04 the command that I used previously has begun corrupting the destination site on second and subsequent invocations. The options relevant to the problem seem to be -N (use timestamping), -k (convert links) and -E (adjust extensions). The problem arises with linked files whose names do not end in .html. On the first invocation everything is good: file foo.txt is downloaded and linked as foo.txt. On the second invocation the wget log (option -v) suggests that it has examined foo.txt on the server, but then it reports "File '/foo.txt.html' not modified on server. Omitting download." and then it changes the link in the referring file to foo.txt.html. I think this is a bug. Do others have an opinion? Workaround: include the option "--no-if-modified-since" which seems to restore the old, correct behavior. Thanks. P.S. The full command that misbehaves is: wget -nH -r -E -k -N -x -l inf -P "http://" ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => wget (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1618288 Title: wget using "if-modified-since" is not idempotent and corrupts downloaded copy of website on second use Status in wget package in Ubuntu: New Bug description: I use wget to copy a web site from one server to another, adjusting file suffixes and paths. Since updating to 16.04 LTS from 14.04 the command that I used previously has begun corrupting the destination site on second and subsequent invocations. The options relevant to the problem seem to be -N (use timestamping), -k (convert links) and -E (adjust extensions). The problem arises with linked files whose names do not end in .html. On the first invocation everything is good: file foo.txt is downloaded and linked as foo.txt. On the second invocation the wget log (option -v) suggests that it has examined foo.txt on the server, but then it reports "File '/foo.txt.html' not modified on server. Omitting download." and then it changes the link in the referring file to foo.txt.html. I think this is a bug. Do others have an opinion? Workaround: include the option "--no-if-modified-since" which seems to restore the old, correct behavior. Thanks. P.S. The full command that misbehaves is: wget -nH -r -E -k -N -x -l inf -P "http://" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1618288/+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 1602254] [NEW] mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1552315 *** https://bugs.launchpad.net/bugs/1552315 Public bug reported: Error occurs immediately on logging into Ubuntu 16.10. Doesn't appear to cause any issues while running the OS. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mediascanner2.0 0.111+16.10.20160526-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 12 09:58:29 2016 ExecutablePath: /usr/bin/mediascanner-service-2.0 InstallationDate: Installed on 2015-12-07 (217 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/mediascanner-service-2.0 ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_CA.UTF-8 LANGUAGE=en_CA:en XDG_RUNTIME_DIR= Signal: 6 SourcePackage: mediascanner2 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libmediascanner-2.0.so.4 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to yakkety on 2015-12-08 (217 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash yakkety ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1602254 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in mediascanner2 package in Ubuntu: New Bug description: Error occurs immediately on logging into Ubuntu 16.10. Doesn't appear to cause any issues while running the OS. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mediascanner2.0 0.111+16.10.20160526-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 12 09:58:29 2016 ExecutablePath: /usr/bin/mediascanner-service-2.0 InstallationDate: Installed on 2015-12-07 (217 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/mediascanner-service-2.0 ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_CA.UTF-8 LANGUAGE=en_CA:en XDG_RUNTIME_DIR= Signal: 6 SourcePackage: mediascanner2 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libmediascanner-2.0.so.4 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to yakkety on 2015-12-08 (217 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1602254/+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 552018] Re: Boot blocks after message fsck from util-linux
I found that if I disabled the proprietary graphic card and with the the open-source all works well except the cuda drivers. If you are using Blender, you are out of luck with the graphic decelerators. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/552018 Title: Boot blocks after message fsck from util-linux Status in util-linux package in Ubuntu: Fix Released Bug description: Binary package hint: util-linux System installed into re-formatted ext3 filesystem, no upgrade. (I know I'm testing a beta distribution) Upon installation the boot went OK, after which I've upgraded the system (apt-get update; apt-get upgrade). After that all normal boots keep blocking while displaying the same message. I've left the system as is for a longer period, but no progress is made. I'm only able to access the system via "recovery mode" and then first option. Text displayed on the monitor: fsck from util-linux-ng 2.17.2 /dev/sda1: clean, ... It could off course be the program after fsck is blocking. 1) :~$ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 2) :~$ apt-cache policy util-linux util-linux: Installed: 2.17.2-0ubuntu1 Candidate: 2.17.2-0ubuntu1 Version table: *** 2.17.2-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 3) I expect the boot to complete to the login: prompt (it is a server installation) 4) The boot blocked with the message previously described Gerben ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: util-linux 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Uname: Linux 2.6.32-16-generic x86_64 Architecture: amd64 Date: Tue Mar 30 21:59:30 2010 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/552018/+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 1611779] [NEW] packagekitd crashed with SIGSEGV in __cxxabiv1::__dynamic_cast()
Public bug reported: Error occurs immediately after login. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: packagekit 0.8.17-4ubuntu6~gcc5.4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Tue Aug 9 18:52:01 2016 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2015-12-07 (246 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7fc645055bb0 <__dynamic_cast+32>: mov (%rdi),%rax PC (0x7fc645055bb0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 pk_backend_get_filters () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so pk_engine_load_backend () Title: packagekitd crashed with SIGSEGV in __dynamic_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: packagekit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash yakkety ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1611779 Title: packagekitd crashed with SIGSEGV in __cxxabiv1::__dynamic_cast() Status in packagekit package in Ubuntu: New Bug description: Error occurs immediately after login. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: packagekit 0.8.17-4ubuntu6~gcc5.4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Tue Aug 9 18:52:01 2016 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2015-12-07 (246 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7fc645055bb0 <__dynamic_cast+32>:mov (%rdi),%rax PC (0x7fc645055bb0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 pkgSystem::ArchitecturesSupported[abi:cxx11]() const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 APT::Configuration::getArchitectures[abi:cxx11](bool const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 pk_backend_get_filters () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so pk_engine_load_backend () Title: packagekitd crashed with SIGSEGV in __dynamic_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1611779/+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 1482721] [NEW] thermald, apport and apport-gtk upgrade failure in ubuntu 15.04
Public bug reported: Failure to upgrade thermald, apport and apport-gtk. lsb_release -rd Description:Ubuntu 15.04 Release:15.04 apt-cache policy apport apport: Installed: 2.17.2-0ubuntu1.2 Candidate: 2.17.2-0ubuntu1.2 Version table: *** 2.17.2-0ubuntu1.2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.17.2-0ubuntu1.1 0 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 2.17.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages apt-cache policy apport-gtk apport-gtk: Installed: 2.17.2-0ubuntu1.2 Candidate: 2.17.2-0ubuntu1.2 Version table: *** 2.17.2-0ubuntu1.2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.17.2-0ubuntu1.1 0 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 2.17.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages apt-cache policy thermald thermald: Installed: 1.4.3-2~15.04.1 Candidate: 1.4.3-2~15.04.1 Version table: *** 1.4.3-2~15.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.3-9 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages sudo apt-get -f upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up apport (2.17.2-0ubuntu1.2) ... insserv: warning: script 'K25vpnagentd_init' missing LSB tags and overrides insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides insserv: There is a loop between service rc.local and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service rc.local and udev if started insserv: loop involving service udev at depth 1 insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore
[Touch-packages] [Bug 1482721] Re: thermald, apport and apport-gtk upgrade failure in ubuntu 15.04
Bug caused by Cisco Anyconnect. Removed anyconnect to resolve. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1482721 Title: thermald, apport and apport-gtk upgrade failure in ubuntu 15.04 Status in systemd package in Ubuntu: Invalid Bug description: Failure to upgrade thermald, apport and apport-gtk. lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 apt-cache policy apport apport: Installed: 2.17.2-0ubuntu1.2 Candidate: 2.17.2-0ubuntu1.2 Version table: *** 2.17.2-0ubuntu1.2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.17.2-0ubuntu1.1 0 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 2.17.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages apt-cache policy apport-gtk apport-gtk: Installed: 2.17.2-0ubuntu1.2 Candidate: 2.17.2-0ubuntu1.2 Version table: *** 2.17.2-0ubuntu1.2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.17.2-0ubuntu1.1 0 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 2.17.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages apt-cache policy thermald thermald: Installed: 1.4.3-2~15.04.1 Candidate: 1.4.3-2~15.04.1 Version table: *** 1.4.3-2~15.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.3-9 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages sudo apt-get -f upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up apport (2.17.2-0ubuntu1.2) ... insserv: warning: script 'K25vpnagentd_init' missing LSB tags and overrides insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides insserv: There is a loop between service rc.local and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service rc.local and udev if started insserv: loop involving service udev at depth 1 insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on rc.local and therefore on system fac
[Touch-packages] [Bug 1474103] [NEW] package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf
Public bug reported: liugt ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.1f-1ubuntu2.15 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 13 11:53:17 2015 DuplicateSignature: package:libssl1.0.0:i386:1.0.1f-1ubuntu2.15:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-03-26 (839 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: i386 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-04-23 (446 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1474103 Title: package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssl package in Ubuntu: New Bug description: liugt ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.1f-1ubuntu2.15 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 13 11:53:17 2015 DuplicateSignature: package:libssl1.0.0:i386:1.0.1f-1ubuntu2.15:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-03-26 (839 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: i386 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-04-23 (446 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1474103/+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 1476343] [NEW] Freeze on screensaver deactivate when set to lock on screensaver activate
Public bug reported: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light-locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1476343 Title: Freeze on screensaver deactivate when set to lock on screensaver activate Status in xorg package in Ubuntu: New Bug description: A few months ago, I started having a problem where my laptop would freeze and require a hard reboot when I tried to wake it from screensaver. I tried turning light-locker off; this fixed the problem. However, now due to company policy, I have to turn light- locker back on, and found that the problem still existed. After some searching, and trying different things, I've found that if I set light-locker to activate on screensaver *deactivate*, then everything works properly, and when I wake the laptop from screensaver, I'm presented with a blank X background and password dialog. If I set light-locker back to activate on screensaver *activate*, then my computer continues to run until I press a key or touch the touchpad, at which point it freezes. Note, I keep suspend and hibernate turned off completely on this laptop, and almost never run on battery. The above happens when plugged into AC power. It would appear to be purely in the realm of light-locker and the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jul 20 10:45:46 2015 InstallationDate: Installed on 2014-07-22 (362 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1476343/+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 1360303] [NEW] [SB-XFi - Creative X-Fi, playback] No automute when headphones are plugged in
Public bug reported: Dell XPS 720. fresh install 14.04 all updates. 10.04 was previous OS and did not have this problem. plugging in headphones has no effect on the sound coming from the speakers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 22 10:41:50 2014 InstallationDate: Installed on 2014-08-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Juniper HDMI Audio [Radeon HD 5700 Series] - HDA ATI HDMI Symptom_Type: No auto-mute between outputs Title: [SB-XFi - Creative X-Fi, playback] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YU822 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/01/2008:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS720 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1360303 Title: [SB-XFi - Creative X-Fi, playback] No automute when headphones are plugged in Status in “alsa-driver” package in Ubuntu: New Bug description: Dell XPS 720. fresh install 14.04 all updates. 10.04 was previous OS and did not have this problem. plugging in headphones has no effect on the sound coming from the speakers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 22 10:41:50 2014 InstallationDate: Installed on 2014-08-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Juniper HDMI Audio [Radeon HD 5700 Series] - HDA ATI HDMI Symptom_Type: No auto-mute between outputs Title: [SB-XFi - Creative X-Fi, playback] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YU822 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/01/2008:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS720 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360303/+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 2092680] [NEW] initramfs-tools btrfs failed with return 1
Public bug reported:
Bug Report
When I boot, I get the following error:
/dev/root: Can't open blockdev
After a forced restart, I can boot using the advanced boot options:
With Linux 6.8.0-51-generic, the system will not boot.
With Linux 5.15.0-130-generic, the system boots successfully.
I have tried updating and upgrading, but the issue persists.
(Note: For debugging, I added sed -ex to /usr/share/initramfs-
tools/hooks/btrfs.)
root@x:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
kpartx libsgutils2-1.46-2 sg3-utils
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up initramfs-tools (0.142ubuntu25.4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142ubuntu25.4) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-130-generic
+ PREREQ=
+ prereqs
+ echo
+ exit 0
+ PREREQ=
+ prereqs
+ echo
+ exit 0
+ PREREQ=
+ . /usr/share/initramfs-tools/hook-functions
+ [ -x /bin/btrfs ]
+ copy_exec /bin/btrfs /bin
+ local src target x nonoptlib ret
+ src=/bin/btrfs
+ target=/bin
+ copy_file binary /bin/btrfs /bin
+ local type src target link_target
+ type=binary
+ src=/bin/btrfs
+ target=/bin
+ [ -f /bin/btrfs ]
+ [ -d /var/tmp/mkinitramfs_SxPD4G//bin ]
+ target=/bin/btrfs
+ target=/usr/bin/btrfs
+ [ -e /var/tmp/mkinitramfs_SxPD4G//usr/bin/btrfs ]
+ mkdir -p /var/tmp/mkinitramfs_SxPD4G//usr/bin
+ [ -h /bin/btrfs ]
+ [ n = y ]
+ cp -pP /bin/btrfs /var/tmp/mkinitramfs_SxPD4G//usr/bin/btrfs
+ env --unset=LD_PRELOAD ldd /bin/btrfs
+ grep -P ^\t
+ sed -e
/\//!d;
/linux-gate/d;
/=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/
+ echo /lib/libgcwrap.so
+ sed -e
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ nonoptlib=/lib/libgcwrap.so
+ echo /lib/libgcwrap.so
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ nonoptlib=/lib/libgcwrap.so
+ [ -e /lib/libgcwrap.so ]
+ copy_file binary /lib/libgcwrap.so
+ local type src target link_target
+ type=binary
+ src=/lib/libgcwrap.so
+ target=/lib/libgcwrap.so
+ [ -f /lib/libgcwrap.so ]
+ return 2
+ ret=2
+ [ 2 = 1 ]
+ return 1
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15.0-130-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
initramfs-tools
Note: I also encountered an error with /usr/share/initramfs-tools/hooks/dhcpcd
which failed with return 1. I resolved this by reinstalling initramfs-tools.
Thank you in advance
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2092680
Title:
initramfs-tools btrfs failed with return 1
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Bug Report
When I boot, I get the following error:
/dev/root: Can't open blockdev
After a forced restart, I can boot using the advanced boot options:
With Linux 6.8.0-51-generic, the system will not boot.
With Linux 5.15.0-130-generic, the system boots successfully.
I have tried updating and upgrading, but the issue persists.
(Note: For debugging, I added sed -ex to /usr/share/initramfs-
tools/hooks/btrfs.)
root@x:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
kpartx libsgutils2-1.46-2 sg3-utils
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up initramfs-tools (0.142ubuntu25.4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142ubuntu25.4) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-130-generic
+ PREREQ=
+ prereqs
+ echo
+ exit 0
+ PREREQ=
+ prereqs
+ echo
+ exit 0
+ PREREQ=
+ . /usr/share/initramfs-tools/hook-functions
+ [ -x /bin/btrfs ]
+ copy_exec /bin/btrfs /bin
+ local src target x nonoptlib ret
+
[Touch-packages] [Bug 1928201] [NEW] [Envaya Mini, playback] Playback problem
Public bug reported: After using the bluetooth device (Denon Envaya Mini) for video calls (Teams, Google Meet), it gets stuck on "Headset Head Unit (HSP/HFP)" config. Switching the configuration back to A2DP does nothing, restarting the app (Spotify, Poddr) etc does nothing. This worked just fine in 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 1720 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 12:39:50 2021 InstallationDate: Installed on 2020-04-24 (382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Envaya Mini Symptom_Type: Only some of outputs are working Title: [Envaya Mini, playback] Playback problem UpgradeStatus: Upgraded to hirsute on 2021-04-27 (15 days ago) dmi.bios.date: 03/15/2019 dmi.bios.release: 1.28 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9 dmi.board.vendor: HUAWEI dmi.board.version: M12 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M12 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:br1.28:efr1.28:svnHUAWEI:pnMACH-WX9:pvrM12:rvnHUAWEI:rnMACH-WX9:rvrM12:cvnHUAWEI:ct10:cvrM12: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M12 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1928201 Title: [Envaya Mini, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: After using the bluetooth device (Denon Envaya Mini) for video calls (Teams, Google Meet), it gets stuck on "Headset Head Unit (HSP/HFP)" config. Switching the configuration back to A2DP does nothing, restarting the app (Spotify, Poddr) etc does nothing. This worked just fine in 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 1720 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 12:39:50 2021 InstallationDate: Installed on 2020-04-24 (382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Envaya Mini Symptom_Type: Only some of outputs are working Title: [Envaya Mini, playback] Playback problem UpgradeStatus: Upgraded to hirsute on 2021-04-27 (15 days ago) dmi.bios.date: 03/15/2019 dmi.bios.release: 1.28 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9 dmi.board.vendor: HUAWEI dmi.board.version: M12 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M12 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:br1.28:efr1.28:svnHUAWEI:pnMACH-WX9:pvrM12:rvnHUAWEI:rnMACH-WX9:rvrM12:cvnHUAWEI:ct10:cvrM12: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M12 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928201/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
See https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1306849/comments/42 for a workaround for the broken Firefox -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/802942 Title: printing PDFs (and other complex documents) from GTK applications fails Status in Mozilla Firefox: New Status in cups package in Ubuntu: Invalid Status in cups-filters package in Ubuntu: Invalid Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hello, I'm discovering a bug when printing complex PDFs or other complex documents from GTK applications. Printing complex PDFs from evince, or sometimes even printing comples webpages from firefox result in one error page being printed instead of the document content: +-+ | ERROR NAME;| | undefined| | COMMAND; | | Q| | OPERAND STACK; | +-+ My printer is a Brother HL 5270DN. It doesn't matter whether the printer is connected via USB or as network printer. In both cases the described bug does happen. The PPD I use is "Brother HL-5270DN BR- Script3", similar to the one at http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd I discovered this bug in up-to-date Debian unstable for several years already. Now I switched one of my laptops to Ubuntu Natty (fresh installation), and unfortunately discovered the same bug there as well. I'm pretty sure that this bug is related to bug #419143, and not really in CUPS, but rather in some library (poppler or cairo) used by GTK applications. The same PDFs that produce the described error in evince, print fine in okular. I attach an example PDF that doesn't print in evince, but prints fine in okular. It's sufficient to (try to) print page 1 of the document. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 28 13:13:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU MachineType: LENOVO 4180W1H Papersize: a4 PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3 ProcEnviron: LANGUAGE=de:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180W1H dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180W1H dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/802942/+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 1756053] [NEW] Thrown out of session into login screen with "inactivity" warning
Public bug reported: I upgraded to the 18.04 beta yesterday, which fixed all my problems with hibernation on my DELL XPS 9350. Most other things have been fine until ten minutes ago, when I was without warning thrown out (forcibly logged out) of my Gnome session. I was typing away on my keyboard in WebStorm when suddenly the screen went blank and I was back at the GDM login screen. There was a brief warning on screen about the system going into hibernation (or standby/suspend - don't remember). When I logged in again, it was a fresh new session, so all previously existing windows had been closed, which meant I lost work. I am not sure where to go about debugging this and providing more information. `dmesg` seemed pretty normal. I experienced something somewhat similar on 17.10, where I upon logging in would create _an additional session_ (I could still see the old processes in the process list), but this seems to be something different. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 15 12:41:47 2018 DistUpgraded: 2018-03-14 23:36:59,657 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Klarte ikke å kjøre underprosess «./xorg_fix_proprietary.py» (Fila eller mappa finnes ikke) (8)) DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2017-12-15 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=61769a4f-3eba-43c7-89c5-81986b7623f5 ro resume=/dev/disk/by-uuid/bead0e5c-11a9-426c-a7d3-bc0dd8ebc756 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-03-14 (0 days ago) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 06D13G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn06D13G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic single-occurrence third-party-packages 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/1756053 Title: Thrown out of session into login screen with "inactivity" warning Status in xorg package in Ubuntu: New Bug description: I upgraded to the 18.04 beta yesterday, which fixed all my problems with hibernation on my DELL XPS 9350. Most other things have been fine until ten minutes ago, when I was without warning thrown out (forcibly logged out) of my Gnome session. I was typing away on my keyboard in WebStorm when suddenly the screen went blank and I was back at the GDM login screen. There was a brief warning on screen about the system going into hibernation (or standby/suspend - don't remember). When I logged in again, it was a fresh new session, so all previously existing windows had been closed, which meant I lost work. I am not sure where to go about debugging this and providing more information. `dmesg` seemed pretty normal. I experienced something somewhat similar on 17.10, where I upon logging in would create _an additional session_ (I could still see the old processes in the process list), but this seems to be something different. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDe
[Touch-packages] [Bug 1756052] [NEW] Thrown out of session into login screen with "inactivity" warning
*** This bug is a duplicate of bug 1756053 *** https://bugs.launchpad.net/bugs/1756053 Public bug reported: I upgraded to the 18.04 beta yesterday, which fixed all my problems with hibernation on my DELL XPS 9350. Most other things have been fine until ten minutes ago, when I was without warning thrown out (forcibly logged out) of my Gnome session. I was typing away on my keyboard in WebStorm when suddenly the screen went blank and I was back at the GDM login screen. There was a brief warning on screen about the system going into hibernation (or standby/suspend - don't remember). When I logged in again, it was a fresh new session, so all previously existing windows had been closed, which meant I lost work. I am not sure where to go about debugging this and providing more information. `dmesg` seemed pretty normal. I experienced something somewhat similar on 17.10, where I upon logging in would create _an additional session_ (I could still see the old processes in the process list), but this seems to be something different. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1756053 Thrown out of session into login screen with "inactivity" warning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1756052 Title: Thrown out of session into login screen with "inactivity" warning Status in cups package in Ubuntu: New Bug description: I upgraded to the 18.04 beta yesterday, which fixed all my problems with hibernation on my DELL XPS 9350. Most other things have been fine until ten minutes ago, when I was without warning thrown out (forcibly logged out) of my Gnome session. I was typing away on my keyboard in WebStorm when suddenly the screen went blank and I was back at the GDM login screen. There was a brief warning on screen about the system going into hibernation (or standby/suspend - don't remember). When I logged in again, it was a fresh new session, so all previously existing windows had been closed, which meant I lost work. I am not sure where to go about debugging this and providing more information. `dmesg` seemed pretty normal. I experienced something somewhat similar on 17.10, where I upon logging in would create _an additional session_ (I could still see the old processes in the process list), but this seems to be something different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1756052/+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 1756052] Re: Thrown out of session into login screen with "inactivity" warning
*** This bug is a duplicate of bug 1756053 *** https://bugs.launchpad.net/bugs/1756053 Marked this as a duplicate and opened a new bug after finding how to produce debugging information at https://wiki.ubuntu.com/X/Troubleshooting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1756052 Title: Thrown out of session into login screen with "inactivity" warning Status in cups package in Ubuntu: New Bug description: I upgraded to the 18.04 beta yesterday, which fixed all my problems with hibernation on my DELL XPS 9350. Most other things have been fine until ten minutes ago, when I was without warning thrown out (forcibly logged out) of my Gnome session. I was typing away on my keyboard in WebStorm when suddenly the screen went blank and I was back at the GDM login screen. There was a brief warning on screen about the system going into hibernation (or standby/suspend - don't remember). When I logged in again, it was a fresh new session, so all previously existing windows had been closed, which meant I lost work. I am not sure where to go about debugging this and providing more information. `dmesg` seemed pretty normal. I experienced something somewhat similar on 17.10, where I upon logging in would create _an additional session_ (I could still see the old processes in the process list), but this seems to be something different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1756052/+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 520546] Re: Alt-f2 switches to virtual terminal 2
Never had this problem until recently, but seems to align with updates being installed. Using 18.04.1 and yes, "sudo kbd_mode -s" seems to fix it. Using Dell XPS 9350. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1493067] Re: ssh-copy-id fails by making assumptions about the default shell on the remote machine
This should definitely be fixed in ssh-copy-id - making these assumptions is just bad. However, I found a workaround that is convenient for me at least and that I think could be a stopgap for others too, until such time as ssh- copy-id is fixed. I wrote it up here: http://blog.duesenklipper.de/2015/10/05/interactive-fish-without- breaking-sh-scripts.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1493067 Title: ssh-copy-id fails by making assumptions about the default shell on the remote machine Status in openssh package in Ubuntu: Confirmed Bug description: ssh-copy-id 10.200.17.160 /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys foo@10.200.17.160's password: fish: Expected a command name, got token of type “Run job in background”. Did you mean “COMMAND; and COMMAND”? See the help section for the “and” builtin command by typing “help and”. Standard input: mkdir -p .ssh && cat >> .ssh/authorized_keys || exit 1 ; ^ I expected to be able to copy my key. An approach I see is for ssh-copy-id to run bash -c ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openssh-client 1:6.7p1-5ubuntu1.3 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 7 15:56:44 2015 RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.7p1-5ubuntu1.3 SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1493067/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Still not working..i hope someone can fix this problem... -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Also encountered this: $ uname -a Linux kaltop 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan mar 06 12:44:09 kaltop /usr/lib/gdm3/gdm-x-session[2575]: i965: Failed to submit batchbuffer: Bad address mar 06 12:44:09 kaltop gnome-shell[2782]: X IO Error mar 06 12:44:09 kaltop pulseaudio[2557]: X connection to :0 broken (explicit kill or server shutdown). mar 06 12:44:09 kaltop WebKitWebProces[18049]: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. mar 06 12:44:09 kaltop gnome-shell[2782]: Gdk-Message: 12:44:09.213: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+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 1323068] Re: -su: cannot set terminal process group (-1): Inappropriate ioctl for device
Umm, confirmed on Ubuntu 14.04.1 LTS, recently updated from 12... what's this about and how can I fix it? Seems harmless so far though. cj@rocksteady:~$ sudo su minecraft - [sudo] password for cj: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell minecraft@rocksteady:/mnt/data/home/cj$ script /dev/null Script started, file is /dev/null minecraft@rocksteady:/mnt/data/home/cj$ screen -dR I realize I get some nutty memory leak before the other dude though. I'll investigate. /CJ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1323068 Title: -su: cannot set terminal process group (-1): Inappropriate ioctl for device Status in “bash” package in Ubuntu: Confirmed Bug description: *Not* happening in Ubuntu 12.04.4 LTS ubuntu-precise-daily-amd64-server-20140522 (ami-c446aeac) ubuntu@ip-10-0-0-30:~$ sudo su - root@ip-10-0-0-30:~# su - ubuntu - ubuntu@ip-10-0-0-30:~$ Happening in Ubuntu 14.04 LTS ubuntu-trusty-14.04-amd64-server-20140416.1 (ami-018c9568) ubuntu@build:~$ sudo su - root@build:~# su - ubuntu - -su: cannot set terminal process group (-1): Inappropriate ioctl for device -su: no job control in this shell ubuntu@build:~$ *** test with zsh (ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/zsh) build% sudo su - root@build:~# su - ubuntu - build% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1323068/+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 1323068] Re: -su: cannot set terminal process group (-1): Inappropriate ioctl for device
Edit: that memory leak was due to https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186, which fixed (by removing libpam-smbpass) leaves the original ioctl error :-/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1323068 Title: -su: cannot set terminal process group (-1): Inappropriate ioctl for device Status in “bash” package in Ubuntu: Confirmed Bug description: *Not* happening in Ubuntu 12.04.4 LTS ubuntu-precise-daily-amd64-server-20140522 (ami-c446aeac) ubuntu@ip-10-0-0-30:~$ sudo su - root@ip-10-0-0-30:~# su - ubuntu - ubuntu@ip-10-0-0-30:~$ Happening in Ubuntu 14.04 LTS ubuntu-trusty-14.04-amd64-server-20140416.1 (ami-018c9568) ubuntu@build:~$ sudo su - root@build:~# su - ubuntu - -su: cannot set terminal process group (-1): Inappropriate ioctl for device -su: no job control in this shell ubuntu@build:~$ *** test with zsh (ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/zsh) build% sudo su - root@build:~# su - ubuntu - build% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1323068/+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 1307593] Re: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all
This happened to me when installing a new graphics card. -- 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/1307593 Title: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound was ok on 12.04.4 but I've had no sound on my headphones since upgrading to 13.10. Sound works on HDMI to screen. Have tried to fix problem by trying fixes listed in No sound in Ubuntu 13.10 web pages but nothing worked for me. Ubuntu 13.10 64-bit Memory 7.7 GiB CPU intel core i5-4570 Graphics Intel Haswell Desktop ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simon 9189 F pulseaudio /dev/snd/controlC0: simon 9189 F pulseaudio Date: Mon Apr 14 16:57:27 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-02 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True 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/controlC1: simon 9189 F pulseaudio /dev/snd/controlC0: simon 9189 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/07/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H87N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1307593/+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 1567841] Re: One of my two graphics cards has started to freeze the screen
I have tried the daily-current, and I could not reproduce the bug by running it for 20 hours, and usually I can trigger the bug within an hour. But, I could get the livecd to match my current setup exactly. For one thing it uses unity and not gnome-shell, and I can't install things temporarily with apt-get. So I had to use a statically compiled chromium instead of google chrome. I have found two ways of triggering the bug, and it is still there on "Ubuntu 14.04.5 LTS", and that is by letting one of these two links run for a long time in google chrome. http://xkcd.com/1663/ or https://vicandblood.itch.io/dopesmoker And it only happens with Chrome and not Firefox. -- 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/1567841 Title: One of my two graphics cards has started to freeze the screen Status in xorg package in Ubuntu: Expired Bug description: I run a setup of 2 radeon graphics cards, with 3 screens, in the following layout from left to right counting from 0: Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw I have been running this setup for a year and it has worked fine. This monday I updated some packages and did a reboot, and I usually reboot just once a month cause I patch my running kernel with uptrack. After the reboot I started noticing problems with the second card, Card 1 above. With a mean time between failures of about an hour, the second card freezes the screen, I usually notice that the mouse pointer isn't visible anymore when I move it across from one screen to the middle one. For future reference, the window I have on the middle screen is a fullscreen emacs window. I have tried the following kernels: vmlinuz-3.13.0-77-generic, vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic All have the same problem. And nothing shows up in dmesg when the freeze occurs, or in the Xorg.0.log, I made copies from before and after a freeze. If I move the mouse, that I can't see, onto the middle screen, make emacs the active window (again I can't see this), scroll around a bit with the arrow keys and take a screenshot, the screenshot shows the correctly scrolled window, so the big X buffer is actually correctly updated. If I CTRL-ALT-L to lock the screens, they all go black, but when you press enter only the screens on Card 0 shows the lock screen, the middle one again shows frozen emacs. CTRL-ALT-F1 shows two text terminals on the outermost screens, in the middle, you've guessed it, frozen emacs. If I go to the menu and select Switch user, surprise! Now the frozen screen is gone and it is a gray login screen with the login menu actually on the screen to the right. Log back into my still running user, boooh, it again shows the same frozen emacs. Switch to a completely new user, screen in middle is correct and working. And lastly if I log out completely from my user and log in again the screen is now unfrozen, but I have lots of work and it is really really annoying to have to log out 8 times during a day at work. I'm gonna try one more ancient kernel just to see if there have been some changes to drm or the radeon driver, but I am pretty stumped on this one. It all worked fine last week. Description: Ubuntu 14.04.4 LTS Release: 14.04 Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 8 10:38:17 2016 DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03f2] Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] [1002:6613] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04bb] InstallationDate: Installed on 2012
