[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
per what I know, testing resource block by intel cpu bug testing. -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+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: ubuntu automatically logs out when hovering sidebar
touché, after removing -intel I'm able to reproduce this \o/ -- 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: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: 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] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status 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 1742063] [NEW] Systemd taking long time to boot into desktop 18.04
Public bug reported: ubuntu desktop 18.04 development branch with gnome/xorg @ 9/1/2018 Systemd takes a long time to boot both from start to login and from login to desktop systemd-analyze blame showed apt daily services taking up to 1min and i disabled auto updates but it still takes a long time to boot to desktop, on a fast ssd here's the analyze log after apt.daily disabled: 18.598s plymouth-quit-wait.service 6.544s NetworkManager-wait-online.service 6.302s dev-sda1.device 1.126s udisks2.service 1.097s fwupd.service 1.092s systemd-udev-trigger.service 1.028s apparmor.service 786ms keyboard-setup.service 770ms systemd-journald.service 752ms swapfile.swap 750ms upower.service 743ms systemd-rfkill.service 731ms accounts-daemon.service 697ms ModemManager.service 679ms systemd-journal-flush.service 635ms grub-common.service 580ms apport.service 568ms preload.service 566ms networking.service 555ms NetworkManager.service 554ms systemd-resolved.service 503ms systemd-logind.service 412ms snapd.service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 07:57:20 2018 InstallationDate: Installed on 2017-12-18 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) Lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.family: Type1Family dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1742063 Title: Systemd taking long time to boot into desktop 18.04 Status in systemd package in Ubuntu: New Bug description: ubuntu desktop 18.04 development branch with gnome/xorg @ 9/1/2018 Systemd takes a long time to boot both from start to login and from login to desktop systemd-analyze blame showed apt daily services taking up to 1min and i disabled auto updates but it still takes a long time to boot to desktop, on a fast ssd here's the analyze log after apt.daily disabled: 18.598s plymouth-quit-wait.service 6.544s NetworkManager-wait-online.service 6.302s dev-sda1.device 1.126s udisks2.service 1.097s fwupd.service 1.092s systemd-udev-trigger.service 1.028s apparmor.service 786ms keyboard-setup.service 770ms systemd-journald.service 752ms swapfile.swap 750ms upower.service 743ms systemd-rfkill.service 731ms accounts-daemon.service 697ms ModemManager.service 679ms systemd-journal-flush.service 635ms grub-common.service 580ms apport.service 568ms preload.service 566ms networking.service 555ms NetworkManager.service 554ms systemd-resolved.service 503ms systemd-logind.service 412ms snapd.service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Curre
[Touch-packages] [Bug 1735594] Re: ubuntu automatically logs out when hovering sidebar
uwer: which xserver versions do these machines have? apt-cache policy xserver-xorg-core And do both have xserver-xorg-video-intel(-hwe-16.04) installed? One theory is that only machines installed with full HWE stack are affected, those do not have -intel installed but use the modesetting X driver (as intended). -- 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: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: 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] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status 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 1735594] Re: ubuntu automatically logs out when hovering sidebar
This issue seems to affect Blender. Blender fails to start, with the crash log being the following: # backtrace blender(BLI_system_backtrace+0x20) [0x1a6c8e0] blender() [0x107a525] /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f47797c04b0] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x5ddc16) [0x7f47650f0c16] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x5df30e) [0x7f47650f230e] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x5d1468) [0x7f47650e4468] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x5d2345) [0x7f47650e5345] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x3f34da) [0x7f4764f064da] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x3f3ddd) [0x7f4764f06ddd] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x42a333) [0x7f4764f3d333] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x17812e) [0x7f4764c8b12e] /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x17dda3) [0x7f4764c90da3] blender() [0x107e11d] blender(wm_draw_update+0x3fe) [0x107f7ae] blender(WM_main+0x28) [0x107b118] blender(main+0x3f8) [0x1018bd8] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f47797ab830] blender() [0x107747e] -- 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: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: 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] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status 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 1735594] Re: ubuntu automatically logs out when hovering sidebar
of course you can test ppa:paulo-miguel-dias/pkppa if mesa 17.3.1 fixes this for you too, as it did on 1741447 -- 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: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: 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] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status 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 1741874] Re: if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed
please run apport-collect 1741874 -- 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/1741874 Title: if I move the arrow to the Unity, all the unity disappear ,only the background still appear ,and all the action freezed Status in mesa package in Ubuntu: New Bug description: My OS is Ubuntu 16.04 lts,and I upgrader last week (2018/01/07),and whe I restart my computer,if I move the mouse arrow to the lift Unity ,the OS will freeze,all the icon disappear,it keeps for one minutes,if the arrow touch the Unity again ,as the same issue would happen ,so I cant touch the Unity, now I use the cairo-dock and terminal to control my Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jan 8 18:16:32 2018 InstallationDate: Installed on 2017-09-19 (110 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741874/+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 1741925] Re: Unity launcher disappears on mouse-over launcher
This is a dupe of 1735594, but since I have a similar laptop which doesn't suffer from this issue, let's keep it separate for now. Do you have an additional monitor connected? What is the display resolution you use? Do things still crash if you change the resolution to something smaller than the native one? -- 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/1741925 Title: Unity launcher disappears on mouse-over launcher Status in mesa package in Ubuntu: New Bug description: Move the mouse over the launcher and the EVERYTHING on the desktop disappears for a few seconds. Only the wallpaper remains. Failed immediately after the latest update (installed by me on 5 Jan 2018) and a reboot. Reboot doesn't help. Launcher and the other desktop displays return after a 10 to 30 second pause. No disk activity is observed during recovery. "ClassicMenu Indicator" is installed and it is the only way to start an application. Executing the bug and then immediately examining all the /var/log logs showed no recorded error or incident in any log. uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Abridged hardware list from sudo lshw description: Portable Computer product: Latitude D630 vendor: Dell Inc. width: 32 bits capabilities: smbios-2.4 dmi-2.4 configuration: boot=normal chassis=portable uuid=44454C4C-6E00-1039-8032-B2C04F376831 *-core description: Motherboard vendor: Dell Inc. physical id: 0 serial: .2n927h1. . *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A12 date: 06/20/2008 size: 64KiB capacity: 1984KiB capabilities: isa pci pcmcia pnp upgrade shadowing cdboot bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp smartbattery biosbootspecification netboot *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 version: 6.15.13 serial: -06FD---- slot: Microprocessor size: 2GHz capacity: 2001MHz width: 64 bits clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority dtherm ida cpufreq configuration: cores=2 enabledcores=2 id=0 threads=2 *-cache:0 description: L1 cache physical id: 700 size: 32KiB capacity: 32KiB capabilities: internal write-back data configuration: level=1 *-cache:1 description: L2 cache physical id: 701 size: 2MiB capacity: 2MiB clock: 66MHz (15.0ns) capabilities: pipeline-burst internal varies unified configuration: level=2 *-logicalcpu:0 description: Logical CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 width: 64 bits capabilities: logical *-memory description: System Memory physical id: 1000 slot: System board or motherboard size: 2GiB *-bank:0 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 0 serial: 07B02E7C slot: DIMM_A size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-bank:1 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 1 serial: E9AE2E7D slot: DIMM_B size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-pci description: Host bridge product: Mobile PM965/GM965/GL960 Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0c width: 3
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
Not quite sure now if apparmor upstream is found in launchpad[1] or
gitlab[2].
[1] https://launchpad.net/apparmor
[2] https://gitlab.com/apparmor
If it's launchpad then the URL is good.
If #2 & #3 are good (After your confirmation), then only #1, #4 and #5
are missing.
Im simply trying to anticipate & eliminate confusion before the final
upload.
- Eric
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
* Revision :
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
I apologize, for #2 above in comment#14, the good commit containing the
fix seems to be "630cb2a981cdc731847e8fdaafc45bcd337fe747", please make
sure #3 "Origin:" reflect that.
- Eric
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
-
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
+
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
- Allow seven digit pid
-
+ Allow seven digit pid
* Affecting releases : TXZA
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
- apparmor | 2.8.95~2430-0ubuntu5 | trusty
- apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
- apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
- apparmor | 2.10.95-0ubuntu2 | xenial
- apparmor | 2.10.95-0ubuntu2.6 | xenial-security
- apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
- apparmor | 2.11.0-2ubuntu4| zesty
- apparmor | 2.11.0-2ubuntu17 | artful
- apparmor | 2.11.0-2ubuntu18 | bionic
+ apparmor | 2.8.95~2430-0ubuntu5 | trusty
+ apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
+ apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
+ apparmor | 2.10.95-0ubuntu2 | xenial
+ apparmor | 2.10.95-0ubuntu2.6 | xenial-security
+ apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
+ apparmor | 2.11.0-2ubuntu4| zesty
+ apparmor | 2.11.0-2ubuntu17 | artful
+ apparmor | 2.11.0-2ubuntu18 | bionic
+
+ $ rmadison -u debian apparmor
+ apparmor | 2.11.1-4 | unstable
--
- * Revision :
+ * Revision :
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this should
work.
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
- * Affecting releases : TXZA
+ * Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
Hi Seyeong,
Here's some sponsoring notes that will require minor change. While
waiting for the build farm ...
#1 - Can you make sure (if not already) to forward/submit the patch to
debian upstream against apparmor ? Which is a requirement for the patch
to land in Ubuntu.
Then we can request a coredev to sponsor the devel release (bionic), and
then start the SRU.
#2 - Seems like the good upstream commit number for the change is
"ad94da321ba51e247b2df82a96cb9d83d47b887e" ? Can you double-check ?
If you confirm, please change the commit number where it applies.
#3 - Change "Origin:" in the DEP3 header
Origin: upstream,
https://gitlab.com/apparmor/apparmor/commit/ad94da321ba51e247b2df82a96cb9d83d47b887e
(or using the proper commit (see #2))
#4 - Change "Bug-Ubuntu:" in DEP3 header using the short LP bug url
From
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714
To
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1717714
#5 - Review the package versions. Worst case I'll do it myself later
when I'll be ready to upload.
Example taken from trusty debdiff:
Going from "2.10.95-0ubuntu2.6~14.04.1" to "2.10.95-0ubuntu2.7~14.04.1" is
wrong. It's preferable to use "2.10.95-0ubuntu2.6~14.04.2"
Thanks & let me know if you have any questions.
- Eric
** Tags added: sts-sponsor-slashd
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZA
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
--
* Revision :
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
Hi Seyeong,
As we speak the LP build farm and autopkgtest request.cgi are disabled for
maintenance; no ETA yet.
No new uploads are allowed during this temporary freeze cause by the
maintenance.
We will gladly review your patch when everything will back to normal.
- Eric
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZA
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
--
* Revision :
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
FWIW. I experience the same state of affairs on Ubuntu 17.10 Jan 9 00:07:13 planb colord[999]: failed to get session [pid 10836]: No data available > ps ax | grep 10836 10836 ?Ss 0:00 /usr/sbin/cupsd -l -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
- this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
+ this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
- revision : http://bazaar.launchpad.net/~apparmor-
- dev/apparmor/master/revision/3722
+ * Upstream commit:
+
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
+
+ * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
+ Author: Vincas Dargis
+ Date: Sat Sep 30 15:28:15 2017 +0300
+
+ Allow seven digit pid
+
+
+ * Affecting releases : TXZA
+ --
+ $ git describe --contains 630cb2a9
+ v2.11.95~5^2
+
+ $ rmadison apparmor
+ apparmor | 2.8.95~2430-0ubuntu5 | trusty
+ apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
+ apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
+ apparmor | 2.10.95-0ubuntu2 | xenial
+ apparmor | 2.10.95-0ubuntu2.6 | xenial-security
+ apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
+ apparmor | 2.11.0-2ubuntu4| zesty
+ apparmor | 2.11.0-2ubuntu17 | artful
+ apparmor | 2.11.0-2ubuntu18 | bionic
+ --
+
+ * Revision :
+ http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this should
work.
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZA
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6
[Touch-packages] [Bug 1731193] Re: DNS or HTTP misconfiguration for archive.canonical.com
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- 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/1731193 Title: DNS or HTTP misconfiguration for archive.canonical.com Status in apt package in Ubuntu: Expired Bug description: apt update returns the following error: Err:14 http://archive.canonical.com/ubuntu raring Release 404 Not Found [IP: 2001:67c:1562::1c 80] getent output is: getent hosts archive.canonical.com 2001:67c:1360:8c01::1b archive.canonical.com 2001:67c:1360:8c01::16 archive.canonical.com 2001:67c:1562::1c archive.canonical.com dig output is: dig archive.canonical.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> archive.canonical.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44026 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;archive.canonical.com. IN ;; ANSWER SECTION: archive.canonical.com.197 IN 2001:67c:1360:8c01::16 archive.canonical.com.197 IN 2001:67c:1360:8c01::1b archive.canonical.com.197 IN 2001:67c:1562::1c ;; Query time: 17 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Thu Nov 09 12:54:33 MSK 2017 ;; MSG SIZE rcvd: 134 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 9 12:50:27 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-20 (1633 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-04-20 (567 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1731193/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Also affects: apparmor (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Bionic)
Importance: Undecided
Assignee: Seyeong Kim (xtrusia)
Status: Confirmed
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
revision : http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1741770] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1741770 Title: I did a massive update today, and now my wifi connection is incredibly slow. Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I am running 16.04 on an Asus UX303LN. I had no problems until today I did a big update. After that, I have rebooted several times and re-booted my router as well. My wifi speed is so slow, I cannot even run the sourceforge speed test. Other devices connected to my wifi network access at normal speeds. I have no idea where to begin debugging this, but I am happy to try. Thanks, Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu Date: Sun Jan 7 18:07:00 2018 InstallationDate: Installed on 2015-05-11 (972 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2016-10-24T14:39:47.853679 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741770/+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 1741770] Re: I did a massive update today, and now my wifi connection is incredibly slow.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1741770 Title: I did a massive update today, and now my wifi connection is incredibly slow. Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: I am running 16.04 on an Asus UX303LN. I had no problems until today I did a big update. After that, I have rebooted several times and re-booted my router as well. My wifi speed is so slow, I cannot even run the sourceforge speed test. Other devices connected to my wifi network access at normal speeds. I have no idea where to begin debugging this, but I am happy to try. Thanks, Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu Date: Sun Jan 7 18:07:00 2018 InstallationDate: Installed on 2015-05-11 (972 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2016-10-24T14:39:47.853679 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741770/+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 1742024] Re: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1742024 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in pygobject-2 package in Ubuntu: New Bug description: any ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gobject-2 2.28.6-12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Jan 9 02:12:11 2018 DuplicateSignature: package:python-gobject-2:2.28.6-12ubuntu1 Setting up python-cairo (1.8.8-2) ... /var/lib/dpkg/info/python-cairo.postinst: 6: /var/lib/dpkg/info/python-cairo.postinst: pycompile: not found dpkg: error processing package python-cairo (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2018-01-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1742024/+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 1742024] [NEW] package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: any ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gobject-2 2.28.6-12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Jan 9 02:12:11 2018 DuplicateSignature: package:python-gobject-2:2.28.6-12ubuntu1 Setting up python-cairo (1.8.8-2) ... /var/lib/dpkg/info/python-cairo.postinst: 6: /var/lib/dpkg/info/python-cairo.postinst: pycompile: not found dpkg: error processing package python-cairo (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2018-01-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject-2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1742024 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in pygobject-2 package in Ubuntu: New Bug description: any ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gobject-2 2.28.6-12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Jan 9 02:12:11 2018 DuplicateSignature: package:python-gobject-2:2.28.6-12ubuntu1 Setting up python-cairo (1.8.8-2) ... /var/lib/dpkg/info/python-cairo.postinst: 6: /var/lib/dpkg/info/python-cairo.postinst: pycompile: not found dpkg: error processing package python-cairo (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2018-01-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1742024/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
I was wrong before. The ppa:paulo-miguel-dias/pkppa did corrected my problem, which is exactly as Jacob Opstad described in comment #50. To work it out, after installing the PPA I needed to restart the daemon, or reboot the system. Thank you all! It have been really frustrating working on my laptop these last few days. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+subscriptions -- Mailing list: https://
[Touch-packages] [Bug 1734477] Re: LubuntuNext 17.10 - When not run from terminal, fails upon "Install"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdebi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1734477 Title: LubuntuNext 17.10 - When not run from terminal, fails upon "Install" Status in gdebi package in Ubuntu: Confirmed Bug description: I recently installed Lubuntu Next 17.10. I have been using Flashpeak-SlimJet as a browser, but it is not in the repositories, so I download the .deb file and use gdebi to install it. The version of gdebi that Lubuntu Next installs is gdebi-kde, presumably because LN uses Qt. However, as described at: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1731803 gdebi-kde is not usable, and since I needed to install a .deb, I installed the gtk version, gebi. That seems to work, until one clicks on "Install", whereupon the window disappears with no message, never to return... When run from terminal, the window disappears, but another appears. This one asks for my password, and when provided one, runs to completion, installing the package. (I did run it without terminal, and looked amongst my other desktops, thinking that perhaps the password window was there, but displayed in the wrong desktop, but found nothing.) It is possible that adding "sudo " to the .desktop file "Exec" would solve the standalone menu invocation, but I am not sure that would help when using the right-click context menu from the desired .deb (and if not, how one would fix that (surely more common) situation). scott@scott-Asus-M2N68-AM-PLUS:~$ uname -a Linux scott-Asus-M2N68-AM-PLUS 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux scott@scott-Asus-M2N68-AM-PLUS:~$ lsb_release -dsc Ubuntu 17.10 artful scott@scott-Asus-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION QLubuntu scott@scott-Asus-M2N68-AM-PLUS:~$ apt-cache policy gdebi gdebi: Installed: 0.9.5.7+nmu1ubuntu3 Candidate: 0.9.5.7+nmu1ubuntu3 Version table: *** 0.9.5.7+nmu1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdebi 0.9.5.7+nmu1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 25 14:34:46 2017 InstallationDate: Installed on 2017-11-06 (19 days ago) InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Beta amd64 (20171014) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1734477/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
I proposed the fix at the packaging repository in https://github.com/mvo5/unattended-upgrades/pull/87 . Most likely it will be part of the next package update. ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => In Progress ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: In Progress Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
The same problem (Ubuntu 16.04). Unusable desktop after recent update. ppa:paulo-miguel-dias/pkppa works for me. No more crashes. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Description changed:
+ [Impact]
+
+ If PID is larger than 6 digits.
+
+ apparmor denies process.
+
+ this fix is committed, but not released. so all supporting version are
+ affected.
+
+ [Test Case]
+
+ 1. making pid over 6 digits
+ - i used touch command to do it
+ 2. snap install canonical-livepatch ( just picked this pkg )
+
+ you can see denied msg as original description
+
+ [Regression]
+ this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
+ denied services need to be restarted after fixing this.
+
+ [Others]
+
+ revision : http://bazaar.launchpad.net/~apparmor-
+ dev/apparmor/master/revision/3722
+
+ [Original Description]
+
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
- And is showing
+ And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this should
work.
** Tags removed: patch
** Tags added: sts-sru-needed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- i used touch command to do it
2. snap install canonical-livepatch ( just picked this pkg )
you can see denied msg as original description
[Regression]
this fix changes regex only, i don't think there is severe regression. also
if there is regression, we can revert manually temporarily.
denied services need to be restarted after fixing this.
[Others]
revision : http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3722
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 836616] Re: 100% cpu usage in lightdm
That screenshot shows Xorg (and compiz) running at 100% CPU, not LightDM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+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 1742011] Re: find can't find several files with unicode characters
For the case that the unicode character has been lost – here the hexdump: echo ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 |hexdump 000 5241 4554 435f 6e6f 6563 7472 2d5f 4a5f 010 7a61 2d7a 7641 7369 6168 5f69 6f43 6568 020 5f6e 415f 5f75 7247 73c3 645f 5f75 614a 030 7a7a 312d 3337 3534 3537 3332 2e36 706d 040 0a34 042 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1742011 Title: find can't find several files with unicode characters if --name is used Status in findutils package in Ubuntu: New Bug description: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) c42-bugnr: #3922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1742011/+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 1742011] [NEW] find can't find several files with unicode characters if --name is used
Public bug reported: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) c42-bugnr: #3922 ** Affects: findutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1742011 Title: find can't find several files with unicode characters if --name is used Status in findutils package in Ubuntu: New Bug description: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) c42-bugnr: #3922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1742011/+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 1742011] Re: find can't find several files with unicode characters
find -D search -name "*4" consider_visiting (early): ".": fts_info=FTS_D , fts_level= 0, prev_depth=-2147483648 fts_path=".", fts_accpath="." consider_visiting (late): ".": fts_info=FTS_D , isdir=1 ignore=0 have_stat=1 have_type=1 consider_visiting (early): "./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4": fts_info=FTS_NSOK, fts_level= 1, prev_depth=0 fts_path="./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4", fts_accpath="ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4" consider_visiting (late): "./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr\303s_du_Jazz-1734575236.mp4": fts_info=FTS_NSOK, isdir=0 ignore=0 have_stat=0 have_type=1 consider_visiting (early): ".": fts_info=FTS_DP, fts_level= 0, prev_depth=1 fts_path=".", fts_accpath="." consider_visiting (late): ".": fts_info=FTS_DP, isdir=1 ignore=1 have_stat=1 have_type=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1742011 Title: find can't find several files with unicode characters if --name is used Status in findutils package in Ubuntu: New Bug description: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) c42-bugnr: #3922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1742011/+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 1742011] Re: find can't find several files with unicode characters
Finally the proof that it is the one mystic unicode character: $ mv ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Grs_du_Jazz-1734575236.mp4 $ find . -name "*4" ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Grs_du_Jazz-1734575236.mp4 ** Summary changed: - find can't find several files with unicode characters + find can't find several files with unicode characters if --name is used ** Description changed: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 - find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 - But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) + + c42-bugnr: #3922 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1742011 Title: find can't find several files with unicode characters if --name is used Status in findutils package in Ubuntu: New Bug description: Downloading some files from ARTE via Mediathekview I retrieved files like this: ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4 find . is showing the the file: > $ find . > . > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4 But if I invoke `find . -name "*mp4"` nothing is found. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: findutils 4.6.0+git+20160126-2 ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 9 01:12:36 2018 SourcePackage: findutils UpgradeStatus: No upgrade log present (probably fresh install) c42-bugnr: #3922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1742011/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
I have the same problem.I reinstall 16.04 and work fine before updates, After updates everything is crashing.Some time I can open Mozilla but not home or something else.Some friend help me and I move some how all icons on the top bar. Is nothing on the right bar and looks like working this way. I have Application and Places on the left top corner on the bar and I can open from there everything.I'd like to return to normal but No ideea when will be fix this bug. I know this won't help you to much but at least you are not alone on this mater. Sorry about this ** Attachment added: "this is how is loking now my screen.Skype ,Mozila and qshutdown i move this shortcuts there" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+attachment/5033047/+files/Screenshot%20from%202018-01-08%2023-12-49.png -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
@Janghou thank m8 for the recomendations, I use Paulo Miguel PPA, but it doesn't works for me too. Now I update system with the official update, remove PPA and all is ok now. Thank for all hard work here and the official Ubuntu team! -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubsc
[Touch-packages] [Bug 1741602] Re: how to install display driver on xubuntu
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but you will receive more help if you raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** 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/1741602 Title: how to install display driver on xubuntu Status in xorg package in Ubuntu: Invalid Bug description: hello. my graphic card is intel on borad. i used from linux xubuntu. i want to install display driver. can you help me? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98 Uname: Linux 4.4.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 6 11:09:34 2018 InstallationDate: Installed on 2017-12-31 (5 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741602/+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 1624560] Re: Use XCB 64-bit sequence API
I am missing this fix for Xenial (as that is a LTS release) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1624560 Title: Use XCB 64-bit sequence API Status in libx11 package in Ubuntu: Confirmed Bug description: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives/xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1624560/+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 1624560] Re: Use XCB 64-bit sequence API
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libx11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1624560 Title: Use XCB 64-bit sequence API Status in libx11 package in Ubuntu: Confirmed Bug description: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives/xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1624560/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Similar problem but not the same. My system is usable. I log in to whatever account I want and everything looks normal. It's only a problem if I put the cursor over any icon in the launcher or press the super key or when the logout/shutdown dialog or the alt+tab image is supposed to come up. In any of those cases, the launcher and top bar flicker and seem to reset. I can't log out or open or switch programs using the normal methods. I can get by just fine using the terminal but it's interrupting my work flow. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubun
[Touch-packages] [Bug 961679] Re: gtkrc is producing light menus from dark elements
Edit: I examined another install on another machine with proposed off and do not have this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/961679 Title: gtkrc is producing light menus from dark elements Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: Fix Committed Bug description: [Impact] Menu items for apps using gtk2 use a light color, which is inconsistent with all other system apps using gtk3 and that are using dark menus. [Test case] Right click on any window's title bar In app window menus of gtk 2 apps, examples - synaptic, browsers where global menus aren't used, vlc with no global menu, ect. Right click in a browser's menu bar Systray right click menus The in app window context menu of gtk2 windows should be dark. [Regression potential] Menu items not usable or readable in some apps. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: light-themes 0.1.8.31-0ubuntu1 [modified: usr/share/themes/Ambiance/gtk-2.0/gtkrc usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css usr/share/themes/Ambiance/gtk-3.0/gtk.css usr/share/themes/Ambiance/gtk-3.0/settings.ini usr/share/themes/Ambiance/metacity-1/close.png usr/share/themes/Ambiance/metacity-1/close_focused_normal.png usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml] ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 21 17:42:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: light-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support
Having this in 18.04 LTS would be extremely useful for use by hosting operations to streamline required packages (avoiding the need for clvmd + dlm, and in some scenarios corosync). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1741986 Title: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support Status in lvm2 package in Ubuntu: Confirmed Bug description: I am extremely interesting in utilizing the following stack to host disks for KVM virtual machines: * lvm2 * lvmlockd * sanlock I believe in order to use lvmlockd, the lvm2 sources will need to be merged from Debian and the lvm2-lockd binary package will need to be built. Please could I request that this merge happen prior to the release of Beaver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support
** Summary changed: - Please merge lvmlockd and sanlock support + Please merge lvm2 from Debian unstable for lvmlockd and sanlock support ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed ** Changed in: lvm2 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: lvm2 (Ubuntu) Milestone: None => ubuntu-18.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1741986 Title: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support Status in lvm2 package in Ubuntu: Confirmed Bug description: I am extremely interesting in utilizing the following stack to host disks for KVM virtual machines: * lvm2 * lvmlockd * sanlock I believe in order to use lvmlockd, the lvm2 sources will need to be merged from Debian and the lvm2-lockd binary package will need to be built. Please could I request that this merge happen prior to the release of Beaver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1741986] [NEW] Please merge lvm2 from Debian unstable for lvmlockd and sanlock support
Public bug reported: I am extremely interesting in utilizing the following stack to host disks for KVM virtual machines: * lvm2 * lvmlockd * sanlock I believe in order to use lvmlockd, the lvm2 sources will need to be merged from Debian and the lvm2-lockd binary package will need to be built. Please could I request that this merge happen prior to the release of Beaver. ** Affects: lvm2 (Ubuntu) Importance: Wishlist Assignee: Nish Aravamudan (nacc) Status: Confirmed ** Summary changed: - Please merge lvmlockd with sanlock support + Please merge lvmlockd and sanlock support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1741986 Title: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support Status in lvm2 package in Ubuntu: Confirmed Bug description: I am extremely interesting in utilizing the following stack to host disks for KVM virtual machines: * lvm2 * lvmlockd * sanlock I believe in order to use lvmlockd, the lvm2 sources will need to be merged from Debian and the lvm2-lockd binary package will need to be built. Please could I request that this merge happen prior to the release of Beaver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Timo, don't hurt yourself with the scalpel. FYI: Glmark2 benchmark plummeted from 201 to 151 with PPA mesa 17.3 -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741925] Re: Unity launcher disappears on mouse-over launcher
** Package changed: ubuntu => mesa (Ubuntu) -- 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/1741925 Title: Unity launcher disappears on mouse-over launcher Status in mesa package in Ubuntu: New Bug description: Move the mouse over the launcher and the EVERYTHING on the desktop disappears for a few seconds. Only the wallpaper remains. Failed immediately after the latest update (installed by me on 5 Jan 2018) and a reboot. Reboot doesn't help. Launcher and the other desktop displays return after a 10 to 30 second pause. No disk activity is observed during recovery. "ClassicMenu Indicator" is installed and it is the only way to start an application. Executing the bug and then immediately examining all the /var/log logs showed no recorded error or incident in any log. uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Abridged hardware list from sudo lshw description: Portable Computer product: Latitude D630 vendor: Dell Inc. width: 32 bits capabilities: smbios-2.4 dmi-2.4 configuration: boot=normal chassis=portable uuid=44454C4C-6E00-1039-8032-B2C04F376831 *-core description: Motherboard vendor: Dell Inc. physical id: 0 serial: .2n927h1. . *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A12 date: 06/20/2008 size: 64KiB capacity: 1984KiB capabilities: isa pci pcmcia pnp upgrade shadowing cdboot bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp smartbattery biosbootspecification netboot *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 version: 6.15.13 serial: -06FD---- slot: Microprocessor size: 2GHz capacity: 2001MHz width: 64 bits clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority dtherm ida cpufreq configuration: cores=2 enabledcores=2 id=0 threads=2 *-cache:0 description: L1 cache physical id: 700 size: 32KiB capacity: 32KiB capabilities: internal write-back data configuration: level=1 *-cache:1 description: L2 cache physical id: 701 size: 2MiB capacity: 2MiB clock: 66MHz (15.0ns) capabilities: pipeline-burst internal varies unified configuration: level=2 *-logicalcpu:0 description: Logical CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 width: 64 bits capabilities: logical *-memory description: System Memory physical id: 1000 slot: System board or motherboard size: 2GiB *-bank:0 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 0 serial: 07B02E7C slot: DIMM_A size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-bank:1 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 1 serial: E9AE2E7D slot: DIMM_B size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-pci description: Host bridge product: Mobile PM965/GM965/GL960 Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0c width: 32 bits clock: 33MHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubs
[Touch-packages] [Bug 1741925] [NEW] Unity launcher disappears on mouse-over launcher
You have been subscribed to a public bug: Move the mouse over the launcher and the EVERYTHING on the desktop disappears for a few seconds. Only the wallpaper remains. Failed immediately after the latest update (installed by me on 5 Jan 2018) and a reboot. Reboot doesn't help. Launcher and the other desktop displays return after a 10 to 30 second pause. No disk activity is observed during recovery. "ClassicMenu Indicator" is installed and it is the only way to start an application. Executing the bug and then immediately examining all the /var/log logs showed no recorded error or incident in any log. uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Abridged hardware list from sudo lshw description: Portable Computer product: Latitude D630 vendor: Dell Inc. width: 32 bits capabilities: smbios-2.4 dmi-2.4 configuration: boot=normal chassis=portable uuid=44454C4C-6E00-1039-8032-B2C04F376831 *-core description: Motherboard vendor: Dell Inc. physical id: 0 serial: .2n927h1. . *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A12 date: 06/20/2008 size: 64KiB capacity: 1984KiB capabilities: isa pci pcmcia pnp upgrade shadowing cdboot bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp smartbattery biosbootspecification netboot *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 version: 6.15.13 serial: -06FD---- slot: Microprocessor size: 2GHz capacity: 2001MHz width: 64 bits clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority dtherm ida cpufreq configuration: cores=2 enabledcores=2 id=0 threads=2 *-cache:0 description: L1 cache physical id: 700 size: 32KiB capacity: 32KiB capabilities: internal write-back data configuration: level=1 *-cache:1 description: L2 cache physical id: 701 size: 2MiB capacity: 2MiB clock: 66MHz (15.0ns) capabilities: pipeline-burst internal varies unified configuration: level=2 *-logicalcpu:0 description: Logical CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 width: 64 bits capabilities: logical *-memory description: System Memory physical id: 1000 slot: System board or motherboard size: 2GiB *-bank:0 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 0 serial: 07B02E7C slot: DIMM_A size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-bank:1 description: DIMM DDR Synchronous 667 MHz (1.5 ns) product: V916765G24QCFW-F5 vendor: ProMOS/Mosel Vitelic physical id: 1 serial: E9AE2E7D slot: DIMM_B size: 1GiB width: 64 bits clock: 667MHz (1.5ns) *-pci description: Host bridge product: Mobile PM965/GM965/GL960 Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0c width: 32 bits clock: 33MHz ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Unity launcher disappears on mouse-over launcher https://bugs.launchpad.net/bugs/1741925 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
Test case proves correct. will not copy,paste. after proposed update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1741775] Re: bad symlink "/etc/resolvconf/resolv.conf.d/original"
On Sun, Jan 07, 2018 at 08:55:53PM -, Warren wrote: > I searched through /var/log/apt history files and resolvconf gets sucked > in as a dependency when I install the proprietary vpn-unlimited > application from Keepsolid. > If I remove resolvconf, is it necessary to re-install or re-configure > any other components? I realize that might break vpn-unlimited but > that's not a Ubuntu matter. I can't say for sure whether resolvconf will remove cleanly without requiring other reconfiguration, sorry. It should, but I don't know that this has been well tested for the 17.10 case. After removal of the resolvconf package, /etc/resolv.conf should be a symlink to ../run/systemd/resolve/stub-resolv.conf and name resolution should work. ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1741775 Title: bad symlink "/etc/resolvconf/resolv.conf.d/original" Status in resolvconf package in Ubuntu: Triaged Bug description: Ubuntu 17.10 amd_64 resolvconf 1.79ubuntu8 The symlink at "/etc/resolvconf/resolv.conf.d/original" points to "../run/systemd/resolve/stub-resolv.conf". This is a broken link as the relative path does not exist. This causes resolvconf to improperly (re-)generate "/run/resolvconf/resolv.conf". The link should probably instead point to the absolute path "/run/systemd/resolve/stub- resolv.conf". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1741775/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
@tedy58 https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-latest-updates-compiz-segfaults Use ppa:paulo-miguel-dias/pkppa -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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/L
[Touch-packages] [Bug 961679] Re: gtkrc is producing light menus from dark elements
Update, proposed. in ambiance, dark background menus, radiance, light. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/961679 Title: gtkrc is producing light menus from dark elements Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: Fix Committed Bug description: [Impact] Menu items for apps using gtk2 use a light color, which is inconsistent with all other system apps using gtk3 and that are using dark menus. [Test case] Right click on any window's title bar In app window menus of gtk 2 apps, examples - synaptic, browsers where global menus aren't used, vlc with no global menu, ect. Right click in a browser's menu bar Systray right click menus The in app window context menu of gtk2 windows should be dark. [Regression potential] Menu items not usable or readable in some apps. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: light-themes 0.1.8.31-0ubuntu1 [modified: usr/share/themes/Ambiance/gtk-2.0/gtkrc usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css usr/share/themes/Ambiance/gtk-3.0/gtk.css usr/share/themes/Ambiance/gtk-3.0/settings.ini usr/share/themes/Ambiance/metacity-1/close.png usr/share/themes/Ambiance/metacity-1/close_focused_normal.png usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml] ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 21 17:42:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: light-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1734104] Re: 'upgrade' in bionic should by default autoremove as well
** Changed in: apt (Ubuntu) Status: New => Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => Medium -- 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/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: Triaged Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1741940] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- 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/1741940 Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned Status in systemd package in Ubuntu: New Bug description: Upgrading from Artful ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 Uname: Linux 4.15.0-999-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Mon Jan 8 17:47:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-30 (435 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741940/+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 1741940] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrading from Artful ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 Uname: Linux 4.15.0-999-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Mon Jan 8 17:47:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-30 (435 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1741940 Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned Status in systemd package in Ubuntu: New Bug description: Upgrading from Artful ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 Uname: Linux 4.15.0-999-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Mon Jan 8 17:47:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-30 (435 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications a
[Touch-packages] [Bug 1741584] Re: comments in variables
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/1741584
Title:
comments in variables
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Nibaldo González discovered that AppArmor parses variable assignments
differently than many other lines and includes #comments if they are
on the same line in a surprising fashion:
https://lists.ubuntu.com/archives/apparmor/2018-January/011418.html
> 24| @{libreoffice_ext} = [tT][xX][tT] #.txt
> 25| @{libreoffice_ext} += {,f,F}[oO][dDtT][tTsSpPbBgGfF] #All the open
> document format
...
$ apparmor_parser -Qd < foo | grep '#'
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
Mode: rwak: Name:
({/home//*,/root,/mnt,/media}/**.{[tT][xX][tT],#.txt,{,f,F}[oO][dDtT][tTsSpPbBgGfF],#All,the,open,document,format,[xX][mMsS][lL],#.xml,and,xsl,[pP][dD][fF],#.pdf,[uU][oO][fFtTsSpP],#Unified,office,format,{,x,X}[hH][tT][mM]{,l,L},#(x)htm(l),[jJ][pP][gG],[jJ][pP][eE][gG],[pP][nN][gG],[sS][vV][gG],[sS][vV][gG][zZ]99251,[tT][iI][fF],[tT][iI][fF][fF],[dD][oO][cCtT]{,x,X},[rR][tT][fF],[xX][lL][sSwWtT]{,x,X},[dD][iIbB][fF],#.dif,dbf,[cCtT][sS][vV],#.tsv,.csv,[sS][lL][kK],[pP][pP][tTsS]{,x,X},[pP][oO][tT]{,m,M},[sS][wW][fF],#Flash,[pP][sS][dD],#Photoshop,[mM][mM][lL]})
I've filed a bug for this profile but perhaps the solution should be
to modify the AppArmor parser instead:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-
l10n/+bug/1741581
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1741584/+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 1741938] Re: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to instal
*** This bug is a duplicate of bug 1740542 *** https://bugs.launchpad.net/bugs/1740542 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1740542, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1740542 package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcursor in Ubuntu. https://bugs.launchpad.net/bugs/1741938 Title: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 -- Fourth try uising "Ubuntu WineHQ Wiki " Instructions. Fourth Fail. Status in libxcursor package in Ubuntu: New Bug description: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 -- Fourth try uising "Ubuntu WineHQ Wiki " Instructions. Fourth Fail. $ ubuntu-bug libxcursor Along with Errors were encountered while processing: /var/cache/apt/archives/libdb5.3_5.3.28-11ubuntu0.1_i386.deb /var/cache/apt/archives/libxcursor1_1%3a1.1.14-1ubuntu0.16.04.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In terminal Install. Synaptic fixed one broken package ""Had dependency problems" Still no joy, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 8 12:26:51 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libxcursor1:1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] Unpacking libdb5.3:i386 (5.3.28-11ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/libdb5.3_5.3.28-11ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdb5.3/changelog.Debian.gz', which is different from other instances of package libdb5.3:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:21de] MachineType: HP HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=3b8879a3-4801-456c-8faf-f053840ef3b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxcursor Title: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 233F dmi.board.vendor: Hewlett-Packard dmi.board.version: 06.27 dmi.chassis.asset.tag: Chass
[Touch-packages] [Bug 1741938] [NEW] package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to inst
*** This bug is a duplicate of bug 1740542 *** https://bugs.launchpad.net/bugs/1740542 Public bug reported: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64 -linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 -- Fourth try uising "Ubuntu WineHQ Wiki " Instructions. Fourth Fail. $ ubuntu-bug libxcursor Along with Errors were encountered while processing: /var/cache/apt/archives/libdb5.3_5.3.28-11ubuntu0.1_i386.deb /var/cache/apt/archives/libxcursor1_1%3a1.1.14-1ubuntu0.16.04.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In terminal Install. Synaptic fixed one broken package ""Had dependency problems" Still no joy, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 8 12:26:51 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libxcursor1:1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] Unpacking libdb5.3:i386 (5.3.28-11ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/libdb5.3_5.3.28-11ubuntu0.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdb5.3/changelog.Debian.gz', which is different from other instances of package libdb5.3:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:21de] MachineType: HP HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=3b8879a3-4801-456c-8faf-f053840ef3b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxcursor Title: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2 usr/share/doc/libxcursor1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxcursor1/changelog.Debian.gz', which is different from other instances of package libxcursor1:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 233F dmi.board.vendor: Hewlett-Packard dmi.board.version: 06.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd04/07/2016:svnHP:pnHP15NotebookPC:pvrType1-ProductConfigId:rvnHewlett-Packard:rn233F:rvr06.27:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jan 8 11:26:51 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: libxcursor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 package-conflict ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcursor in Ubuntu. https://bugs.launchpad.net/bugs/1741938 Title: package libxcursor1 1:1.1.14-1ubuntu0.16.04.1 [modified: usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
[Touch-packages] [Bug 1734104] Re: 'upgrade' in bionic should by default autoremove as well
** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- 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/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: New Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1741874] Re: if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu) -- 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/1741874 Title: if I move the arrow to the Unity, all the unity disappear ,only the background still appear ,and all the action freezed Status in mesa package in Ubuntu: New Bug description: My OS is Ubuntu 16.04 lts,and I upgrader last week (2018/01/07),and whe I restart my computer,if I move the mouse arrow to the lift Unity ,the OS will freeze,all the icon disappear,it keeps for one minutes,if the arrow touch the Unity again ,as the same issue would happen ,so I cant touch the Unity, now I use the cairo-dock and terminal to control my Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jan 8 18:16:32 2018 InstallationDate: Installed on 2017-09-19 (110 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741874/+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 1741629] Re: OEM install test case fails at user login
** Package changed: apport (Ubuntu) => kubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1741629 Title: OEM install test case fails at user login Status in kubuntu-meta package in Ubuntu: New Bug description: Testing Kubuntu 17.10.1 with test cases on http://iso.qa.ubuntu.com/qatracker/milestones/385/builds/164205/testcases/1305/results At step 33 the user login screen didn't show. It just stuck there without any reaction. I tested it on Virtual Box 5.1.30 r118389 (Qt5.6.1), the virtual machine contains 2 CPUs and 2GB ram, 40GB HDD, 16MB display ram. No 2D & 3D acceleration. UEFI turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1741629/+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 1741770] Re: I did a massive update today, and now my wifi connection is incredibly slow.
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager (Ubuntu) -- 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/1741770 Title: I did a massive update today, and now my wifi connection is incredibly slow. Status in network-manager package in Ubuntu: New Bug description: I am running 16.04 on an Asus UX303LN. I had no problems until today I did a big update. After that, I have rebooted several times and re-booted my router as well. My wifi speed is so slow, I cannot even run the sourceforge speed test. Other devices connected to my wifi network access at normal speeds. I have no idea where to begin debugging this, but I am happy to try. Thanks, Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu Date: Sun Jan 7 18:07:00 2018 InstallationDate: Installed on 2015-05-11 (972 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2016-10-24T14:39:47.853679 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1741770/+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 1740926] Re: Demote gitk to universe
You can demote gitk now if you like. I think idle is now the only thing keeping tcl/tk in main so I am trying to ask doko if that's needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1740926 Title: Demote gitk to universe Status in ubuntu-meta package in Ubuntu: New Bug description: tcl/tk is in main because of gitk. gitk was added to main with this commit: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/628 It is now in platform.bionic's supported-development-desktop seed. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop I propose we remote it from there and demote gitk to universe. I came across this while working on LP: #1720482 (tk8.6 recommends xterm which is one thing that appears to keep xterm in main). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1740926/+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 1741874] [NEW] if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed
You have been subscribed to a public bug: My OS is Ubuntu 16.04 lts,and I upgrader last week (2018/01/07),and whe I restart my computer,if I move the mouse arrow to the lift Unity ,the OS will freeze,all the icon disappear,it keeps for one minutes,if the arrow touch the Unity again ,as the same issue would happen ,so I cant touch the Unity, now I use the cairo-dock and terminal to control my Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jan 8 18:16:32 2018 InstallationDate: Installed on 2017-09-19 (110 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- if I move the arrow to the Unity, all the unity disappear ,only the background still appear ,and all the action freezed https://bugs.launchpad.net/bugs/1741874 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1741770] [NEW] I did a massive update today, and now my wifi connection is incredibly slow.
You have been subscribed to a public bug: I am running 16.04 on an Asus UX303LN. I had no problems until today I did a big update. After that, I have rebooted several times and re-booted my router as well. My wifi speed is so slow, I cannot even run the sourceforge speed test. Other devices connected to my wifi network access at normal speeds. I have no idea where to begin debugging this, but I am happy to try. Thanks, Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu Date: Sun Jan 7 18:07:00 2018 InstallationDate: Installed on 2015-05-11 (972 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2016-10-24T14:39:47.853679 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- I did a massive update today, and now my wifi connection is incredibly slow. https://bugs.launchpad.net/bugs/1741770 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- 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 1741675] Re: desktop screen
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ** This bug has been marked a duplicate of bug 1735594 ubuntu automatically logs out when hovering sidebar -- 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/1741675 Title: desktop screen Status in xorg package in Ubuntu: New Bug description: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741675/+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 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
The solution is indeed to install the qt5-default package. Maybe this package could be added as a dependency in newer releases? There is also perhaps an upstream bug where qtchooser could try the "other" qt version if one fails. (I had installed qdbus5, and qtchooser was trying qdbus4, which was not installed or wanted.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" Status in qt4-x11 package in Ubuntu: Confirmed Status in qtchooser package in Ubuntu: Confirmed Bug description: Release: Ubuntu 13.10 (32-bit) Package versions: qtdbus 4:4.8.4+dfsg-0ubuntu18 qtchooser 26-3ubuntu2 Expected behavior: The `qdbus` program runs, as does the related program `qdbusviewer`. Actual behavior: If I run the `qdbus` program, it always crashes: user@host:~$ qdbus --help qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file or directory The `qdbus` executable is actually: user@host:~$ ls --full-time $(which qdbus) lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus -> qtchooser Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to work if I invoke it directly. There's a `qdbus-qt5` package in the universe repository. It was not pulled in as a dependency, but manually installing it fixes the issue. Therefore it's either a packaging error or a bug in qtchooser. A similar thing happens if I run `qdbusviewer`: user@host:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No such file or directory except that installing `qdbus-qt5` doesn't fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qdbus 4:4.8.4+dfsg-0ubuntu18 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 09:34:24 2013 MarkForUpload: True SourcePackage: qt4-x11 UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
I think the lasted update solved my problem. After removing the ppa :paulo-miguel-dias/pkppa because it didn't worked for me, the unity stopped crashing. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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.
[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Agreed, ppa:paulo-miguel-dias/pkppa This also works here. No more crash events so far. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
I am affectef from the same issue and it is very nasty. I install lubunty as is suggested in the bug report bellow, but it is not mine desktop environment and it must be reconfigured a lot. I'm using Ubuntu 16.04-3 64-bit with Unity DE on Asus N53Jn. After last update I run over the same issue. I reported this, but still not have solution for that issue as mention Jacob Edward Opstad $uname -a Linux User-N53Jn 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux User-N53Jn:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial I reinstall unity DE, compiz and some other things that I think will resolve the problem, but still not have good solution for that issue. Really it is very annoying. Now I read GUI/Unity crashing in 16.04 LTS after latest updates, compiz segfaults My configuration is Intel-i3, 8Gb RAM, 240Gb SSD, Nvidia Optimus 1G All tips for resolving are welcome. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: l
[Touch-packages] [Bug 1741891] Re: The updated driver in this question causes Unity to crash on Intel graphics cards
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ** This bug has been marked a duplicate of bug 1735594 ubuntu automatically logs out when hovering sidebar -- 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/1741891 Title: The updated driver in this question causes Unity to crash on Intel graphics cards Status in mesa package in Ubuntu: New Bug description: Not sure what happened but hoping someone can help. Running Trusty Tahr on a Thinkpad T410. Ever since Thursday morning (October 26) when I applied the latest updates, Unity crashes every time I click the "Search your computer" icon at the top of the launcher. Pressing the "Super" key causes the same crash. The "Shutdown" and "Restart" buttons don't do anything (I have to open the terminal and enter "sudo shutdown" to shut down the computer). HELP! More than happy to provide ANY documentation you require. My desktop computer (an HP Pavilion) is at the exact same maintenance level and is not experiencing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741891/+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 1741891] Re: The updated driver in this question causes Unity to crash on Intel graphics cards
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ** Package changed: ubuntu => mesa (Ubuntu) ** Tags added: regression-update -- 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/1741891 Title: The updated driver in this question causes Unity to crash on Intel graphics cards Status in mesa package in Ubuntu: New Bug description: Not sure what happened but hoping someone can help. Running Trusty Tahr on a Thinkpad T410. Ever since Thursday morning (October 26) when I applied the latest updates, Unity crashes every time I click the "Search your computer" icon at the top of the launcher. Pressing the "Super" key causes the same crash. The "Shutdown" and "Restart" buttons don't do anything (I have to open the terminal and enter "sudo shutdown" to shut down the computer). HELP! More than happy to provide ANY documentation you require. My desktop computer (an HP Pavilion) is at the exact same maintenance level and is not experiencing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741891/+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 1741891] [NEW] The updated driver in this question causes Unity to crash on Intel graphics cards
You have been subscribed to a public bug: Not sure what happened but hoping someone can help. Running Trusty Tahr on a Thinkpad T410. Ever since Thursday morning (October 26) when I applied the latest updates, Unity crashes every time I click the "Search your computer" icon at the top of the launcher. Pressing the "Super" key causes the same crash. The "Shutdown" and "Restart" buttons don't do anything (I have to open the terminal and enter "sudo shutdown" to shut down the computer). HELP! More than happy to provide ANY documentation you require. My desktop computer (an HP Pavilion) is at the exact same maintenance level and is not experiencing this problem. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- The updated driver in this question causes Unity to crash on Intel graphics cards https://bugs.launchpad.net/bugs/1741891 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
The attachment "lp1717714_trusty.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Can we get this tested for artful as well? -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Have you, after starting CUPS again, completely closed and restarted the app (Firefox and Okular)? Die you try to restart the desktop (log out and log in again)? Or the system (reboot)? Does this make the printers appear again? Also note that DNS-Sd sometimes can have some delay. CUPS never reads cups-browsed.conf. I have introduced cups-browsed.conf as configuration file for cups-browsed. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Xenial) Status: New => Confirmed -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Artful) Status: New => Confirmed -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
** Description changed: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: - + .tmp.unity_support_test.1: - + ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] -Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] + Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] + Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Patch added: "lp1717714_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032828/+files/lp1717714_trusty.debdiff
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Patch added: "lp1717714_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032832/+files/lp1717714_bionic.debdiff
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Patch added: "lp1717714_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032829/+files/lp1717714_xenial.debdiff
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Patch added: "lp1717714_artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032831/+files/lp1717714_artful.debdiff
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Patch added: "lp1717714_zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032830/+files/lp1717714_zesty.debdiff
--
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/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
Hi Thiago, how did you fix the issue? On my 16.04 workstation i still have the issue. 2 Routers generate RAs, the routing table on the clients looks like: default via fe80::xx dev enp0s25 proto static metric 100 pref medium -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
cool, now it would need to be bisected :/ -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Yep, ppa:paulo-miguel-dias/pkppa seems fine. ;) -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
Made the quick check you suggested. Switching off cups, all printers disappear both in okular (QT) and firefox. So it looks like the driverless network printers come from cups. Weird enough now after the switch off - switch on sequence for cups, I do not have the driverless printers them in firefox either even with cups re-enabled which is weird. This means that there is nothing to disable in the GTK and QT dialogs which seems a good thing. Do you know if some kind of situation where stale files describing network printers could remain around explaining these inconsistent behaviors? If so where? Furthermore, it looks like cups is currently not passing the list of driverless network printers to the print dialog. May it be the case that cups (or the cups dbus notifier) happens to read the cups-browsed configuration file seeking the BrowseRemoteProtocols none configuration option if it is readable? Note that on my system the cups dbus notifier runs as lp and so it cannot read cups-browsed.conf by default since this file is owned by root.root and not readable by others. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
I tried the first ppa above and this worked for me. Screen handling is now stable, so thanks. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
@Till Thanks! This is a great explanation. I am sure that it took you some time to write it in this clear way and I would like to let you know that I really appreciate it. Things look a bit clearer to me right now. I am looking forward to seeing method (4) materialize as the current situation seems rather unsatisfactory to me. In fact, I think that when there was only (1) without (2) and (3) the situation was much better than it is right now, since you had a clear single place where to enable and disable things and consistent number and naming of printers across all dialogs. Particularly (3), with the dialogs grabbing the DNS-SD broadcasts, seems a rather poor choice leading to all sorts of inconsistencies among the different dialogs. Would it make sense to suggest that (3) is disabled in ubuntu's QT and GTK since we have cups-browsed anyway that is better (as it provides indication of the printer type)? Do you know if there is any way to disable (2) from some cups option? -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
** Also affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Artful) Importance: Undecided Status: New -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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.la
[Touch-packages] [Bug 1740926] Re: Demote gitk to universe
let's demote it. ping me once you commit the removal from the seed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1740926 Title: Demote gitk to universe Status in ubuntu-meta package in Ubuntu: New Bug description: tcl/tk is in main because of gitk. gitk was added to main with this commit: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/628 It is now in platform.bionic's supported-development-desktop seed. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop I propose we remote it from there and demote gitk to universe. I came across this while working on LP: #1720482 (tk8.6 recommends xterm which is one thing that appears to keep xterm in main). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1740926/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
ok, need to test later versions then, maybe best to try these ppa's (in this order) https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa/ and if 17.3.1 in this ppa doesn't work, try https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa which has a git snapshot -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries
FYI - Fix in bionic upload queue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1741227 Title: apparmor denial to several paths to binaries Status in ntp package in Ubuntu: In Progress Bug description: Issue shows up (non fatal) as: apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Since non crit this is mostyl about many of us being curious why it actually does do it :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1~1 Candidate: 17.2.8-0ubuntu0~16.04.1~1 Version table: *** 17.2.8-0ubuntu0~16.04.1~1 500 500 http://ppa.launchpad.net/canonical-x/x-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 -1 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 17.2.4-0ubuntu1~16.04.0 500 500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu xenial/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Tried both: logout, reboot still negative -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var
[Touch-packages] [Bug 1741906] [NEW] ubuntu 16.04LTS
Public bug reported: can reboot only in terminal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 8 15:25:16 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2017-11-27 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2089AZ9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=39d4b598-7ce6-4bc0-841c-1bc21b4114e5 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2089AZ9 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:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089AZ9:pvrThinkPadT500:rvnLENOVO:rn2089AZ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2089AZ9 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jan 8 14:46:59 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1741906 Title: ubuntu 16.04LTS Status in xorg package in Ubuntu: New Bug description: can reboot only in terminal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 8 15:25:16 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2017-11-27 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2089AZ9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=39d4b598-7ce6-4bc0-841c-1bc21b4114e5 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET9
[Touch-packages] [Bug 1740926] Re: Demote gitk to universe
** Summary changed: - Demote gitk to universe? + Demote gitk to universe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1740926 Title: Demote gitk to universe Status in ubuntu-meta package in Ubuntu: New Bug description: tcl/tk is in main because of gitk. gitk was added to main with this commit: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/628 It is now in platform.bionic's supported-development-desktop seed. https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop I propose we remote it from there and demote gitk to universe. I came across this while working on LP: #1720482 (tk8.6 recommends xterm which is one thing that appears to keep xterm in main). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1740926/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Did you log out or reboot after the install? Verify that you have the update by running: apt-cache policy libgl1-mesa-dri:amd64 -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
There are different methods for auto-discovering driverless IPP network printers. First, all these printers advertise themselves via DNS-SD, so that clients (computers, phones, TVs, ...) find them. The first step which then happens in your computer is that avahi-daemon picks up the printer's broadcasts. Therefore avahi-browse shows the printers. Every other program, like CUPS, cups-browsed, or print dialogs communicate with avahi-daemon to be able to list the printers. If you stop avahi- daemon the printers will disappear for sure, but other types of remote devices which your computer discovers will disappear, too. For getting the printers from avahi-daemon to the final print dialog there are three methods currently (in the order of how I assume that they appeared): 1. cups-browsed: This one I wrote when CUPS 1.6 came out and dropped its own broadcasting/browsing system to automatically make printers from CUPS servers appear on CUPS clients. CUPS replaced this by the same DNS- SD method which the the driverless IPP printers use but they did not do the client part, print dialogs were supposed to use it. But as in Linux GUI there is certain inertia in development and usually no one taking care of printing, I created cups-browsed to assure continuity in the functionality of Ubuntu. In the beginning cups-browsed did nothing more than picking up DNS-SD broadcasts of remote CUPS printers (with the help of avahi-daemon) and created local CUPS queues to make the printers listed locally and to be able to print on them. During the years I added more functionality, especially also creating local queues for driverless IPP printers. cups-browsed removes its local queues when the remote printer disappears or on (cups-browsed) daemon shutdown. This way I have overcome the lack of the print dialog's functionality and users die not complain about missing remote printers. 2. CUPS: Recently, CUPS added a mechanism to automatically have access to remote IPP printers (both driverless network printers and remote CUPS queues) by listing the printers even without having a local queue and auto-creating a temporary queue when trying to access the printer. The temporary queue is removed after 1 minute being idle or on (CUPS) daemon shutdown. Problem of this approach is that clients, like print dialogs need to use the correct CUPS API to see these printers. As not all of them do so I am keeping cups-browsed in the default installation of Ubuntu. 3. Print dialogs can follow the original idea of the time of CUPS 1.6, grabbing the DNS-SD broadcasts of the printers on its own (using only avahi-daemon) and this way list the printers. Now I do not know how exactly each print dialog is working and which of the three methods leads to the dialog listing the IPP printers. As you have already turned off cups-browsed as a first step, it must be (2) or (3) for the Qt dialog. You can try to turn off CUPS now, but only for testing as this way most probably printing will not work. If the dialog still shows the printers, the Qt dialog uses (3) for sure. Try to print even with CUPS still turned off. Does this work? Does the GTK dialog (for example evince) behave the same? Does also the print dialog of LibreOffice behave the same? Perhaps the dialogs behave all different. We have developed a new methods in which the dialogs stop accessing printers on their own and use GUI-independent print dialog backends. This new method (4) will hopefully soon make it into the Linux distributions. By the way, with your observation on Qt print dialog showing the printers as driverless only with cups-browsed running is due to how cups-browsed works. It creates local queues and marks them as "driverless" which the dialog shows. The dialog has a mechanism determining whether a remote printer has already a local queue to avoid duplicate listings. So you see the queue from cups-browsed if cups- browsed is running and you see the printer entry from CUPS or from the dialog itself if cups-browsed is not running. -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of tim
[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Tested you're ppa. Negative. Doesn't work, problems still there. an 8 14:48:41 1810 kernel: [10886.847038] compiz[22501]: segfault at 0 ip 7fd6cdf7a296 sp 7fffc1e6bf30 error 4 in i965_dri.so[7fd6cd9a3000+827000] -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
And I think that the conclusion is the following:
- The KDE print dialog bypasses cups-browsed to list the driverless
network printers, if cups-browsed is not running. In this case it fails
to gather some information such as the "type" of the printer, though.
- For the KDE print dialog not to show the driverless printers one needs
the cups-browsed.conf file to explicitly contain the
'BrowseRemoteProtocols none' entry and must be made *readable* by
everyone, plus a desktop restart seems to be needed
- lpstat -e always shows the driverless network printers regardless of
whether the cups-browsed is active or the BrowseRemoteProtocols none is
selected.
- the firefox print dialog keeps showing /some/ (but not all) of the
driverless network printers shown by lpstat -e and so does the gimp one
and inkscape (dont't think that I have many other apps to test that do
not use the kde print dialog)
The firefox print dialog gets some weird names for some of the network
printers ("print" "printer"), and shows "rejecting jobs" for them.
All this bypassing of cups-browsed does not seem very proper to me.
--
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/1738432
Title:
Regression, poor user experience, print dialogs garbled by
unidentifiable driverless printers
Status in cups package in Ubuntu:
Incomplete
Bug description:
Recently, my print dialogs have started to include network discoverd
printers in addition to those configured in cups even if the cups-
browsed service is disabled and the BrowseRemoteProtocols option is
set to none.
There does not seem to be any way to disable this behavior apart from
disabling avahi or its ability to talk to dbus, which causes side
effects on the system.
Yet, in some environments this behavior is a definite regression over
the old one and leads to an extremely poor user experience.
On some networks:
- The print dialogs takes 3-10 sec to open which is a huge amount of
time for an action that is expected to be instantaneous and for which
there is no visual feedback.
- The print dialog contains many tens of printer entries, all
identified by weird hex strings that cannot be related to any useful
location, that do not help identifying which entry corresponds to
which printer and that only mess up the list making it hard to find
the printers that are actually useful.
For instance, suppose that you work at some office that has recently
purchased a batch of new printers all the same model. In the print
dialog you may get many entries like:
HP_Laserjet_Pro_Mxxxdw_21ACF2
which only vary in the final hex string. How is one suppose to know
what is where?
Please make it possible to disable this driverless printer madness.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libcups2 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
CurrentDesktop: KDE
Date: Fri Dec 15 16:22:07 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1463 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: Notebook W740SU
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W740SU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
One weird phenomenon is that - if cups-browsed is active, the okular print dialog shows the driverless printers and indicates their type as driverless - if cups-browsed is not active, the okular print dialog shows the driverless printers but fails to indicate their type (type is empty). -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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 1741227] Re: apparmor denial to several paths to binaries
** Changed in: ntp (Ubuntu) Assignee: (unassigned) => ChristianEhrhardt (paelzer) ** Changed in: ntp (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1741227 Title: apparmor denial to several paths to binaries Status in ntp package in Ubuntu: In Progress Bug description: Issue shows up (non fatal) as: apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Since non crit this is mostyl about many of us being curious why it actually does do it :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
xenial users please test mesa 17.2.8 from a ppa: sudo apt-add-repository ppa:canonical-x/x-staging && apt update && apt upgrade -y -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers
One weird phenomenon is that - if cups-browsed is active, the okular print dialog shows the driverless printers and indicates their type as driverless - if cups-browsed is not active, the okular print dialog shows the driverless printers but fails to indicate their type (type is empty). -- 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/1738432 Title: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers Status in cups package in Ubuntu: Incomplete Bug description: Recently, my print dialogs have started to include network discoverd printers in addition to those configured in cups even if the cups- browsed service is disabled and the BrowseRemoteProtocols option is set to none. There does not seem to be any way to disable this behavior apart from disabling avahi or its ability to talk to dbus, which causes side effects on the system. Yet, in some environments this behavior is a definite regression over the old one and leads to an extremely poor user experience. On some networks: - The print dialogs takes 3-10 sec to open which is a huge amount of time for an action that is expected to be instantaneous and for which there is no visual feedback. - The print dialog contains many tens of printer entries, all identified by weird hex strings that cannot be related to any useful location, that do not help identifying which entry corresponds to which printer and that only mess up the list making it hard to find the printers that are actually useful. For instance, suppose that you work at some office that has recently purchased a batch of new printers all the same model. In the print dialog you may get many entries like: HP_Laserjet_Pro_Mxxxdw_21ACF2 which only vary in the final hex string. How is one suppose to know what is where? Please make it possible to disable this driverless printer madness. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcups2 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost CurrentDesktop: KDE Date: Fri Dec 15 16:22:07 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1463 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738432/+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
