[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
** Tags removed: yakkety ** Tags added: cosmic ** Changed in: gdm3 (Ubuntu) Status: Won't Fix => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
Please reopen the bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
This is not 16.10 bug, it's reproducible on all latest Ubuntu versions including 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
this will be fixed via the hwe backport ** Also affects: xorg-server-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-hwe-18.04 (Ubuntu Disco) Status: New => Invalid ** Changed in: xorg-server-hwe-18.04 (Ubuntu Cosmic) Status: New => Invalid ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server-hwe-18.04 source package in Cosmic: Invalid Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Status in xorg-server-hwe-18.04 source package in Disco: Invalid Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1813567] Re: cogl ftbfs in 18.04 LTS
1.22.2-3ubuntu1 built fine ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/1813567 Title: cogl ftbfs in 18.04 LTS Status in cogl package in Ubuntu: Fix Released Status in cogl source package in Bionic: Fix Committed Status in cogl package in Debian: Fix Released Bug description: * Impact the package fails to build, see http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html * Test case Check that the package once accepted is building without issue * Regression potential There is no code change but it's a rebuild so it could be impacted by a toolchain change, make sure that GNOME keeps working without rendering issue and that totem does play videos fine -- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html cogl ftbfs. dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libcogl20/DEBIAN/symbols doesn't match completely debian/libcogl20.symbols --- debian/libcogl20.symbols (libcogl20_1.22.2-3_amd64) +++ dpkg-gensymbolsclZaGi 2019-01-28 08:45:17.335924588 + @@ -174,6 +174,7 @@ cogl_feature_flags_get_type@Base 1.17.4 cogl_features_available@Base 1.17.4 cogl_fence_closure_get_user_data@Base 1.17.4 + cogl_filter_return_get_type@Base 1.22.2-3 cogl_fixed_atan2@Base 1.17.4 cogl_fixed_atan@Base 1.17.4 cogl_fixed_cos@Base 1.17.4 dh_makeshlibs: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1813567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813578] Re: duplicity ftbfs in 18.04 LTS
0.7.17-0ubuntu1.1 built fine ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1813578 Title: duplicity ftbfs in 18.04 LTS Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Bionic: Fix Committed Bug description: * Impact the package fails to build, see http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html * Test case Check that the package once accepted is building without issue * Regression potential The change is to add a gpg option, that's already in cosmic and shouldn't have any side effect, check that deja-dup backups still work as they should though --- duplicity ftbfs. == ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest) Test getting signature chain fileobjs from archive_dir -- Traceback (most recent call last): File "/<>/testing/unit/test_collections.py", line 188, in test_sigchain_fileobj self.sigchain_fileobj_check_list(self.sigchain_fileobj_get(None)) File "/<>/testing/unit/test_collections.py", line 180, in sigchain_fileobj_check_list test_fileobj(0, "Hello, world!") File "/<>/testing/unit/test_collections.py", line 177, in test_fileobj fileobjlist[i].close() File "/<>/duplicity/dup_temp.py", line 227, in close assert not self.fileobj.close() File "/<>/duplicity/gpg.py", line 304, in close self.gpg_failed() File "/<>/duplicity/gpg.py", line 271, in gpg_failed raise GPGError(msg) GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: starting migration from earlier GnuPG versions gpg: porting secret keys from '/<>/testing/gnupg/secring.gpg' to gpg-agent gpg: key 839E6A2856538CCF: secret key imported gpg: key BCEF1B4DB5FA894F: secret key imported gpg: key 453005CE9B736B2A: secret key imported gpg: migration succeeded gpg: CAST5 encrypted data gpg: encrypted with 1 passphrase gpg: WARNING: message was not integrity protected gpg: Hint: If this message was created before the year 2003 it is likely that this message is legitimate. This is because back then integrity protection was not widely used. gpg: Use the option '--ignore-mdc-error' to decrypt anyway. gpg: decryption forced to fail! gpg: WARNING: unsafe permissions on homedir '/<>/testing/gnupg' = End GnuPG log = -- Ran 418 tests in 881.428s FAILED (errors=1, skipped=9) Test failed: error: Test failed: debian/rules:11: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1813578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752844] Re: Graphical artifacts with antialiased lines in OpenGL
I'm assuming this is fixed in mesa 18.2.2 in cosmic, which also landed bionic last night if not, feel free to reopen ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752844 Title: Graphical artifacts with antialiased lines in OpenGL Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 16.04.3, as from the update fixing https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, antialiased line rendering in applications using Opengl is corrupt. Experienced using Intel GM45. Steps to reproduce: 1) Create an OpenGL application. 2) Enable GL_LINE_SMOOTH and set line width to any value below 1.5. 3) Draw a line (either by shaders or by glBegin). Blender and various games by Kenta Cho (tumiki-figthers, torus- trooper, parsec47, titanion) are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770271] Re: VegaM support
bionic has 18.2.2 now ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xorg-hwe-18.04 - 1:7.7+19ubuntu8~18.04.1 --- xorg-hwe-18.04 (1:7.7+19ubuntu8~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:10 +0200 ** Changed in: llvm-toolchain-7 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xf86-input-wacom-hwe-18.04 - 1:0.36.1-0ubuntu1~18.04.1 --- xf86-input-wacom-hwe-18.04 (1:0.36.1-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:14 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-input-evdev-hwe-18.04 - 1:2.10.6-1~18.04.1 --- xserver-xorg-input-evdev-hwe-18.04 (1:2.10.6-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:15 +0200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package libclc - 0.2.0+git20180917-2~ubuntu0.18.04.1 --- libclc (0.2.0+git20180917-2~ubuntu0.18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Thu, 11 Oct 2018 11:32:39 +0300 ** Changed in: xserver-xorg-input-evdev-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-qxl-hwe-18.04 - 0.1.5-2build2~18.04.1 --- xserver-xorg-video-qxl-hwe-18.04 (0.1.5-2build2~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:27 +0200 ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package llvm-toolchain-7 - 1:7-3~ubuntu0.18.04.1 --- llvm-toolchain-7 (1:7-3~ubuntu0.18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Thu, 22 Nov 2018 16:30:14 +0200 ** Changed in: libclc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-dummy-hwe-18.04 - 1:0.3.8-1build3~18.04.1 --- xserver-xorg-video-dummy-hwe-18.04 (1:0.3.8-1build3~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Fri, 14 Dec 2018 14:19:13 +0200 ** Changed in: xorg-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-fbdev-hwe-18.04 - 1:0.5.0-1ubuntu1~18.04.1 --- xserver-xorg-video-fbdev-hwe-18.04 (1:0.5.0-1ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:24 +0200 ** Changed in: xserver-xorg-video-qxl-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-input-joystick-hwe-18.04 - 1:1.6.3-1build1~18.04.1 --- xserver-xorg-input-joystick-hwe-18.04 (1:1.6.3-1build1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:17 +0200 ** Changed in: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-vmware-hwe-18.04 - 1:13.3.0-2build1~18.04.1 --- xserver-xorg-video-vmware-hwe-18.04 (1:13.3.0-2build1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:30 +0200 ** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 - 1:1.0.15-3~18.04.1 --- xserver-xorg-video-nouveau-hwe-18.04 (1:1.0.15-3~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:25 +0200 ** Changed in: xserver-xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-vesa-hwe-18.04 - 1:2.4.0-1~18.04.1 --- xserver-xorg-video-vesa-hwe-18.04 (1:2.4.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:28 +0200 ** Changed in: xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-input-libinput-hwe-18.04 - 0.28.1-1~18.04.1 --- xserver-xorg-input-libinput-hwe-18.04 (0.28.1-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:18 +0200 ** Changed in: xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xorg-server-hwe-18.04 - 2:1.20.1-3ubuntu2.1~18.04.1 --- xorg-server-hwe-18.04 (2:1.20.1-3ubuntu2.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:12 +0200 ** Changed in: xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 - 18.1.0-1~18.04.1 --- xserver-xorg-video-amdgpu-hwe-18.04 (18.1.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:21 +0200 ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 - 1:18.1.0-1~18.04.1 --- xserver-xorg-video-ati-hwe-18.04 (1:18.1.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:23 +0200 ** Changed in: xserver-xorg-video-vesa-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xserver-xorg-input-synaptics-hwe-18.04 - 1.9.1-1ubuntu1~18.04.1 --- xserver-xorg-input-synaptics-hwe-18.04 (1.9.1-1ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:19 +0200 ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1 --- libdrm (2.4.95-1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) libdrm (2.4.95-1) unstable; urgency=medium [ Timo Aaltonen ] * rules, control: Switch to meson. [ Andreas Boll ] * New upstream release. - Fixes WebGL on Firefox (Closes: #907698). * Update libdrm-amdgpu1.symbols and shlibs. * Drop static libdrm library from libdrm-dev. * Update extend-diff-ignore. libdrm (2.4.94-1) unstable; urgency=medium [ Guido Günther ] * Enable etnaviv on arm64 (Closes: #906915) [ Timo Aaltonen ] * New upstream release. (LP: #1789924) * Update libdrm-amdgpu1.symbols and shlibs. libdrm (2.4.93-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. libdrm (2.4.92-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. * control: Update to my Debian address. * Update Vcs-* URLs to point at salsa.debian.org. * Bump debhelper compat to 11. * Bump standards version to 4.1.4. -- Timo Aaltonen Thu, 22 Nov 2018 16:56:49 +0200 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: wayland (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that
[Desktop-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1 --- wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium * control: Bump Breaks/Replaces again to match reality. (LP: #1781440) -- Timo Aaltonen Tue, 27 Nov 2018 21:43:07 +0200 ** Changed in: xf86-input-wacom-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560286] Update Released
The verification of the Stable Release Update for cairo has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted Status in cairo package in Ubuntu: Fix Released Status in cairo source package in Bionic: Fix Released Status in cairo source package in Cosmic: Fix Committed Bug description: * Impact In some files images are printed with inverted colors * Test case open https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf in evince, click on the print preview, the colors should be right * Regression potential it's a change in the code dealing with specific adobe file, test opening the example in different document viewer and try with some other files (the bug has several example), they should display the correct image/colors I have several pdf files that when opened by evince, they appear to be fine until I try to print them. When I do, they print with the colors inverted (the printout looks like a photograph negative). This color inversion also occurs when viewed in the print preview screen. If I click on File > Properties, I get some information... Producer : Adobe Acrobat 15.10 Image Conversion Plug-in Creator : Adobe Acrobat 15.10 ... Format : PDF-1.6 ... I am running ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.2 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 21:01:45 2016 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2012-07-24 (1336 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This bug was fixed in the package cairo - 1.15.10-2ubuntu0.1 --- cairo (1.15.10-2ubuntu0.1) bionic; urgency=medium * debian/patches/git_adobe_cmykcolors.patch: - "Revert "Correctly decode Adobe CMYK JPEGs in PDF export" From further testing and investigation it appears that many PDF viewers already have a workaround to invert Adobe CMYK JPEGs, so our generated PDFs display incorrectly with those viewers due to double-inversion. (lp: #1560286) -- Sebastien Bacher Tue, 22 Jan 2019 15:17:42 +0100 ** Changed in: cairo (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted Status in cairo package in Ubuntu: Fix Released Status in cairo source package in Bionic: Fix Released Status in cairo source package in Cosmic: Fix Committed Bug description: * Impact In some files images are printed with inverted colors * Test case open https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf in evince, click on the print preview, the colors should be right * Regression potential it's a change in the code dealing with specific adobe file, test opening the example in different document viewer and try with some other files (the bug has several example), they should display the correct image/colors I have several pdf files that when opened by evince, they appear to be fine until I try to print them. When I do, they print with the colors inverted (the printout looks like a photograph negative). This color inversion also occurs when viewed in the print preview screen. If I click on File > Properties, I get some information... Producer : Adobe Acrobat 15.10 Image Conversion Plug-in Creator : Adobe Acrobat 15.10 ... Format : PDF-1.6 ... I am running ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.2 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 21:01:45 2016 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2012-07-24 (1336 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 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 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798597] Update Released
The verification of the Stable Release Update for llvm-toolchain-7 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1 --- libdrm (2.4.95-1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) libdrm (2.4.95-1) unstable; urgency=medium [ Timo Aaltonen ] * rules, control: Switch to meson. [ Andreas Boll ] * New upstream release. - Fixes WebGL on Firefox (Closes: #907698). * Update libdrm-amdgpu1.symbols and shlibs. * Drop static libdrm library from libdrm-dev. * Update extend-diff-ignore. libdrm (2.4.94-1) unstable; urgency=medium [ Guido Günther ] * Enable etnaviv on arm64 (Closes: #906915) [ Timo Aaltonen ] * New upstream release. (LP: #1789924) * Update libdrm-amdgpu1.symbols and shlibs. libdrm (2.4.93-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. libdrm (2.4.92-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. * control: Update to my Debian address. * Update Vcs-* URLs to point at salsa.debian.org. * Bump debhelper compat to 11. * Bump standards version to 4.1.4. -- Timo Aaltonen Thu, 22 Nov 2018 16:56:49 +0200 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libeg
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1 --- wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium * control: Bump Breaks/Replaces again to match reality. (LP: #1781440) -- Timo Aaltonen Tue, 27 Nov 2018 21:43:07 +0200 ** Changed in: wayland (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Bionic: Fix Released Status in wayland source package in Cosmic: Fix Released Bug description: [impact] upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was installed [test case] install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic [regression potential] none, the fix only changes the version numbers in Breaks/Replaces -- Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1781440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text
** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: gnome-shell (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on cogl_texture_get_height [ Test case ] No clear reproducer is know for such issue, crashes should be monitored in e.u.c checking that this is not happening anymore for the version in proposed. [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture
** Description changed: + https://gitlab.gnome.org/GNOME/mutter/issues/453 + + --- + This bug contains a crash related to bug 1795089. Local code is used for libmutter, to solve bug 1790525 and to display buffersizes at module setup_spans at cogl/cogl/cogl-texture-2d-sliced.c and at module allocate_from_bitmap at cogl/cogl/driver/gl/cogl-texture-2d-gl.c . Dual monitor is used without a monitors.xml files usable by gdm3 with wayland. After logging in using ubuntu with wayland both screens are shown, but crash after a short time without user doing anything. At syslog we see the displayed buffersizes which are too large before the crash: Oct 2 23:57:42 Gert2 gnome-shell[2636]: GK_allocate_from_bitmap 2560 1024 Oct 2 23:57:42 Gert2 gnome-shell[2636]: GK_cogl_set_error Failed to create texture 2d due to size/format constraints Oct 2 23:57:42 Gert2 gnome-shell[2636]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xwayland 2:1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic i686 ApportVersion: 2.20.10-0ubuntu11 Architecture: i386 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 23:57:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01c2] Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01c2] MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4ccc6cca-be3d-4471-9677-1012a53ebfd7 ro splash quiet vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () _start () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/11/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Changed in: mutter (Ubuntu) Status: Incomplete => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gert van de Kraats (gkraats) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795760 Title: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/format constraints\n") Status in mutter package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/453 --- This bug contains a crash related to bug 1795089. Local code is used for libmutter, to solve bug 1790525 and to display buffersizes at module setup_spans at cogl/cogl/cogl-texture-2d-sliced.c and at module allocate_from_bitmap at cogl/cogl/driver/gl/cogl-texture-2d-gl.c . Dual monitor is used without a monitors.xml files usable by gdm3 with wayland. After logging in using ubuntu with wayland both screens are shown, but crash after a short time without user doing anything. At syslog we see the displayed
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
Thanks. So the problem does seem to be with the Nvidia driver. You might want to start by trying to uninstall "i386" packages like: sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386 and if that doesn't clear it up then: sudo apt --fix-broken install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758721] Re: [nouveau] Screen corruption after suspend
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1758721 Title: [nouveau] Screen corruption after suspend Status in mesa package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1758721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
The attachment "0001-Allow-workspace-layout-to-be-overridden.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout Status in mutter package in Ubuntu: Triaged Bug description: Running up-to-date Ubuntu Cosmic. Since I am running a version with manually applied patched from below, I couldn't use the ubuntu-bug helper. Bug: When using GNOME extension “Workspace grid” that arranges workspaces in a grid, one can find that horizontal switch animation is replaced with a vertical one. This is caused by a bug in mutter itself, it's acknowledged and fixed in upsteam. Applying the patch for the current version in Ubuntu solves the issue as well. GIFs of the issue could be found here: https://medium.com/@hkdb/patch- gnome-3-30-for-workspace-grid-1ee8b1dd92f9. Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270. Upsteam fix: https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e (merged into master 3 months ago). The patch to fix is, literally, adding 1 meaningful line: From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001 From: Ron Yorston Date: Tue, 2 Oct 2018 12:47:05 +0100 Subject: [PATCH] Allow workspace layout to be overridden meta_workspace_manager_override_workspace_layout is implemented by calling meta_workspace_manager_update_workspace_layout which respects the workspace_layout_overridden flag. After the first call to meta_workspace_manager_override_workspace_layout all subsequent calls fail silently. Reset workspace_layout_overridden to FALSE before calling meta_workspace_manager_update_workspace_layout. Signed-off-by: Ron Yorston --- src/core/meta-workspace-manager.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/core/meta-workspace-manager.c b/src/core/meta-workspace-manager.c index 2670f4938..abc819db0 100644 --- a/src/core/meta-workspace-manager.c +++ b/src/core/meta-workspace-manager.c @@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout (MetaWorkspaceManager *workspac int n_rows, int n_columns) { + workspace_manager->workspace_layout_overridden = FALSE; + meta_workspace_manager_update_workspace_layout (workspace_manager, starting_corner, vertical_layout, -- 2.17.1 Hopefully this one is fast to test and apply ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758721] Re: [nouveau] Screen corruption after suspend
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1758721 Title: [nouveau] Screen corruption after suspend Status in mesa package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1758721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
frederick@graphMetrix-1:~$ sudo apt install --reinstall libwayland-server0 [sudo] password for frederick: Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri:i386 : Depends: libelf1:i386 (>= 0.142) but it is not going to be installed libnvidia-gl-390:i386 : Depends: libwayland-client0:i386 (>= 1.3.92) but it is not going to be installed Depends: libwayland-server0:i386 (>= 1.2.0) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom
Verified on cosmic that mutter version 3.30.2-1~ubuntu18.10.3 fixes the problem. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1779615 Title: Shell text and some icons have sharp edges during zoom Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [Impact] Shell text and some icons have sharp edges during zoom. Screenshot attached. https://gitlab.gnome.org/GNOME/gnome-shell/issues/387 [Test Case] 1. Settings > Universal Access > Zoom = ON 2. Click on the time/calendar and look closely at the font edges. Expect: the edges should be smooth when zoomed. [Regression Potential] Low potential effect on other parts of Gnome Shell. The code being changed is only used in shell popup menus at the moment. [Other Info] This is not an important bug at all. Its fix is just a happy consequence of fixing the more important bug 1767648, so that's why it is getting SRU'd - for bug 1767648. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
Hmm, thanks. That list shows the problematic package libwayland- server0:i386 is not installed (any more). But you do have the correct one libwayland-server0:amd64. Can you please run this command: sudo apt install --reinstall libwayland-server0 and send us the output you see? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Verified on cosmic that mutter version 3.30.2-1~ubuntu18.10.3 fixes the problem. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
It looks like maybe the Nvidia driver has pulled in some i386 dependencies despite being amd64 itself. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)
Can confirm that removing xserver-xorg-input-synaptics fixes the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1760338 Title: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic) Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: All the Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad. Does not toggle the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1) ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Mar 31 15:41:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed nvidia, 390.42, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
** Attachment added: "Thanks Daniel!" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+attachment/5234949/+files/allpackages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
Can you please run this command: dpkg -l > allpackages.txt and then send us the resulting file 'allpackages.txt'? ** Changed in: wayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814197] [NEW] package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which
Public bug reported: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: New Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019
[Desktop-packages] [Bug 1813921] Re: The ubuntu doesn't work when there is a second monitor and the user locks the screen.
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1813663, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1813663 External monitors does not work anymore 4.15.0-44 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813921 Title: The ubuntu doesn't work when there is a second monitor and the user locks the screen. Status in linux package in Ubuntu: New Bug description: Initial Setup to reproduce the first issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor. First bug Description: 1. Try to starts the Ubuntu. Actual Results: 1. The Ubuntu can't start. Initial Setup to reproduce the second issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor ready (not connected) to connect. Second bug description: 1. With the Ubuntu started, connect the second monitor and then lock the screen. 2. Try to unlock Ubuntu. Actual Results: 2. The mouse and keyboard don't work and the screen can't be unlocked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 07:16:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] MachineType: LENOVO 20B7008BBR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=e1c74834-7cc4-44fb-94a2-06206608a746 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET79WW (2.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7008BBR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B7008BBR:pvrThinkPadT440:rvnLENOVO:rn20B7008BBR:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7008BBR dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jan 29 14:59:13 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
** Tags added: fixed-in-mutter-3.31.2 fixed-upstream ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout Status in mutter package in Ubuntu: Triaged Bug description: Running up-to-date Ubuntu Cosmic. Since I am running a version with manually applied patched from below, I couldn't use the ubuntu-bug helper. Bug: When using GNOME extension “Workspace grid” that arranges workspaces in a grid, one can find that horizontal switch animation is replaced with a vertical one. This is caused by a bug in mutter itself, it's acknowledged and fixed in upsteam. Applying the patch for the current version in Ubuntu solves the issue as well. GIFs of the issue could be found here: https://medium.com/@hkdb/patch- gnome-3-30-for-workspace-grid-1ee8b1dd92f9. Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270. Upsteam fix: https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e (merged into master 3 months ago). The patch to fix is, literally, adding 1 meaningful line: From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001 From: Ron Yorston Date: Tue, 2 Oct 2018 12:47:05 +0100 Subject: [PATCH] Allow workspace layout to be overridden meta_workspace_manager_override_workspace_layout is implemented by calling meta_workspace_manager_update_workspace_layout which respects the workspace_layout_overridden flag. After the first call to meta_workspace_manager_override_workspace_layout all subsequent calls fail silently. Reset workspace_layout_overridden to FALSE before calling meta_workspace_manager_update_workspace_layout. Signed-off-by: Ron Yorston --- src/core/meta-workspace-manager.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/core/meta-workspace-manager.c b/src/core/meta-workspace-manager.c index 2670f4938..abc819db0 100644 --- a/src/core/meta-workspace-manager.c +++ b/src/core/meta-workspace-manager.c @@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout (MetaWorkspaceManager *workspac int n_rows, int n_columns) { + workspace_manager->workspace_layout_overridden = FALSE; + meta_workspace_manager_update_workspace_layout (workspace_manager, starting_corner, vertical_layout, -- 2.17.1 Hopefully this one is fast to test and apply ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: bionic ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to
[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814162] Re: Xorg freeze
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814162 Title: Xorg freeze Status in linux package in Ubuntu: Confirmed Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked
If you have any gnome-shell extensions installed, please try uninstalling them and tell us if the problem persists. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1814125 Title: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 16:19:16 2019 DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2018-06-08 (236 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago) dmi.bios.date: 10/13/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0502 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked
This might be a different issue, but your kernel log is also getting flooded with error messages about the touchpad(?) https://launchpadlibrarian.net/409195699/CurrentDmesg.txt ** Summary changed: - gnome-shell eats 100% cpu when seconds display is on and screen is locked + [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814125 Title: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 16:19:16 2019 DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2018-06-08 (236 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago) dmi.bios.date: 10/13/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0502 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814098] Re: Favorites cant be added or removed
If you have any gnome-shell extensions loaded, please uninstall (don't just disable) them and tell us if that fixes the problem. Please also run: apport-collect 1814098 because this bug is missing some information since it was reported to the wrong component. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1814098 Title: Favorites cant be added or removed Status in gnome-shell package in Ubuntu: Incomplete Bug description: Apps randomly stay on the sidebar even tho they are not added to favorites, also favorites cant be removed. Video: https://www.youtube.com/watch?v=5LUx3ljV83I Recreation: i cant, but restarting the system allways fixes it. Also the sidebar appears on the lockscreen ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 11:43:49 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39fa] InstallationDate: Installed on 2018-12-01 (60 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN41WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 520S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4QCN41WW(V2.05):bd12/12/2017:svnLENOVO:pn81BL:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB: dmi.product.family: ideapad 520S-14IKB dmi.product.name: 81BL dmi.product.sku: LENOVO_MT_81BL_BU_idea_FM_ideapad 520S-14IKB dmi.product.version: Lenovo ideapad 520S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814107] Re: Crash after fade to black (lock screen or screensaver)
Please also uninstall all of the extensions you have installed: 'openweather-extens...@jenslody.de' 'dash-to-d...@micxgx.gmail.com' 'user-th...@gnome-shell-extensions.gcampax.github.com' 'places-m...@gnome-shell-extensions.gcampax.github.com' 'redsh...@tommie-lie.de' 'system-moni...@paradoxxx.zero.gmail.com' 'nohotcor...@azuri.free.fr' 'suspend-button@laserb' 'topic...@phocean.net' 'workspace-isolated-dash@n-yuki' 'battery_sta...@milliburn.github.com' 'appindicatorsupp...@rgcjonas.gmail.com' 'extendedgestu...@mpiannucci.github.com' 'shell-volume-mi...@derhofbauer.at' and tell us if that fixes the problem. ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1814107 Title: Crash after fade to black (lock screen or screensaver) Status in gnome-shell package in Ubuntu: Incomplete Bug description: When leaving my laptop inactive for over 15min (screensaver settings), gnome-shell crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 31 14:56:34 2019 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-06-15 (229 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814088] Re: totem crashed with SIGSEGV in tcache_get()
** Information type changed from Private to Public ** Summary changed: - totem crashed with SIGSEGV in tcache_get() + totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1814088 Title: totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal] Status in totem package in Ubuntu: New Bug description: I made no attempt to run Videos. This just came up out of the blue. Maybe a video embedded in Tweetdeck tried to trigger it? (Firefox 66.0b4 from firefox-next ppa, installed for the working CSD when buttons on left.) ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 13:41:15 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-09-11 (141 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f609e404d36 <__GI___libc_malloc+422>: mov (%rdx),%rsi PC (0x7f609e404d36) ok source "(%rdx)" (0x561c1b1ae92000) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: tcache_get (tc_idx=1) at malloc.c:2927 __GI___libc_malloc (bytes=35) at malloc.c:3034 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strconcat () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to disco on 2019-01-13 (17 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1814088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813843] Re: [nouveau] Xorg crash
It sounds like step 2 failed. Please go to step 3 of comment #4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1813843 Title: [nouveau] Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: With the newest updates to 18 & with the HP VGA monitor attached I can enter the pswd but will NOT get to the home screen. It hangs at a black screen. If I detach the VGA cable I can power down and boot up to the internal Laptop screen then attach the VGA after logging into Ubuntu. All is fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 14:28:59 2019 DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e] InstallationDate: Installed on 2014-12-13 (1508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20BG0016US ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago) dmi.bios.date: 01/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET70WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jan 29 14:14:34 2019 xserver.configfile: default xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1813843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813511] Re: Gnome shell extensions disabled at every wakeup after sleep
elatllat, that request was for Div mainly. But also please don't use any 'kill' commands between 'pidof' commands because it makes that test useless. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813511 Title: Gnome shell extensions disabled at every wakeup after sleep Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 18.04, all gnome extensions get turned off after waking up from sleep Noticed since: past 1-2 week Workaround: Alt+F2 followed by 'r' - Turns on the extensions which I had on earlier --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-02 (180 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803271] Re: [regression] Much higher CPU during some gnome-shell operations
** Changed in: gjs (Ubuntu Bionic) Milestone: None => ubuntu-18.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Bionic: Fix Released Status in gjs source package in Cosmic: Fix Released Bug description: [Impact] Since fixing bug 1672297 in release 18.04 we experience much higher (almost double) CPU usage during gnome-shell JavaScript operations, such as the icon spring animation [1]. Even just moving the mouse is a little more expensive now [2]. [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 [2] https://gitlab.gnome.org/GNOME/mutter/issues/283 [Test Case] Use 'top' to measure the CPU usage of the gnome-shell process while tapping Super+A repeatedly. It should be much lower with the fix than without. [Regression Potential] Low. This particular fix is tiny (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been released and used in a couple of upstream gjs versions already without issue. [Other Info] The fix is already released to 19.04 as part of gjs version 1.54.2-1. And already released to 18.10 as part of gjs version 1.54.3-1~ubuntu18.10.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Changed in: mutter (Ubuntu Bionic) Milestone: None => ubuntu-18.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] In some early intel GPUs gdm can't start in wayland mode, and so gnome-shell [ Test case ] - Start the pc or logout/end session - Try to login with the "Ubuntu on Wayland" session - Ubuntu should start [ Regression potential ] Possible false positive on wayland support check on some cards --- https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic) Milestone: None => ubuntu-18.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1743976 Title: gnome-shell is wasting CPU repainting unchanging panels Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Fix Released Bug description: gnome-shell is wasting CPU repainting an unchanging panel and dock. Every time an app window changes all visible actors including the panel get repainted. But the panels mostly doesn't change, so should be cached via offscreen-redirect instead. [ Impact ] Ubuntu dock repaints the dock when a window changes [ Test case ] - Maximize a window - Change its content, by acting on it - Monitor gnome-shell CPU usage, and it should be lower than using previous dock version [ Possible regression ] The dock isn't repainted properly or it could produce artifacts in some scenarios To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1743976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813199] Re: Expose 'Last Updated' date to gnome-software for snaps
Oops, that last comment was meant for another bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1813199 Title: Expose 'Last Updated' date to gnome-software for snaps Status in gnome-software package in Ubuntu: Triaged Bug description: Please expose the 'Last Updated' date to gnome-software for snaps. That date is shown on the online store https://snapcraft.io/store for snaps. Rationale: Some snaps have not been updated since several months (example https://snapcraft.io/jabref, last updated on Aug 18 2017), so that date gives an indication to users whether the snap is still maintained by its uploader or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 24 20:29:01 2019 InstallationDate: Installed on 2018-11-29 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.4 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1813199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Debian) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Won't Fix Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813429] Re: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, c
android-udev-rules https://github.com/M0Rf30/android-udev-rules as installed exactly according to the directions did not fix the issue. Noticeably, however, the file transfer got further than average by a great margin. ** Attachment added: "journalctl_013119_latest.txt" https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1813429/+attachment/5234921/+files/journalctl_013119_latest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1813429 Title: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, copy/paste will stop and error reported. Status in libmtp package in Ubuntu: New Bug description: Steps to reproduce: 1) Plug phone into computer. 2) Copy a large number of directories with nested file structures to phone from computer hard drive, via Nautilus: [highlight files on computer, then ctrl-c; go to directory on phone, then ctrl-v]. Expected outcome: No copy errors. Actual Outcome: Usually, the expected outcome; randomly, Error: "Error while copying .m4a>. There was an error copying the file into mtp://LGE_LG-G710_LGG710PMd4...". Show more details : "File not found". Options: ["Cancel","Skip All","Skip"]. I can't force reproducibility, sometimes it won't complain, but larger copy/paste datasets correlate to more likely ending up with an error. Workarounds: At error, select 'Cancel'; delete the offending subdirectory/file from the phone; restart the copy-paste operation from the point of failure; repeat as necessary. lsb_release -rd: "Ubuntu 18.10" apt-cache policy nautilus: "nautilus: Installed: 1:3.26.4-0ubuntu7.1 Candidate: 1:3.26.4-0ubuntu7.1 Version table: *** 1:3.26.4-0ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.4-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 14:01:47 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+67+30'" InstallationDate: Installed on 2019-01-10 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1813429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-control-center (Ubuntu Bionic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667505] Re: Files and Trash hang
On Ubuntu 16.04.5, I still get the problem. ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1667505 Title: Files and Trash hang Status in nautilus package in Ubuntu: New Bug description: Clicking on Files or Trash icons in launcher occasionally does nothing. This is intermittent and not reproducible. It has happened twice since a recent fresh install of 16.04.2. The system generally seems to have to run all day before getting this bug. This behaviour is new to 16.04.2 and was not present in 16.04. The solution is to reboot. If someone can give instructions on what to analyze prior to shutdown, we may be able to solve this today. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 23 17:38:43 2017 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+1030+502'" InstallationDate: Installed on 2017-02-17 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1667505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Augustin, What version of ubuntu have you tested? Can you please paste here the output of the command apt-cache policy linux-image-generic upower gnome-control-center gnome-shell Are you also using a fixed kernel? ** Changed in: upower (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-control-center (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793298] Re: snapd-glib changes needed for pulseaudio snap policy module xenial backport
** Changed in: snapd-glib (Ubuntu) Importance: Undecided => High ** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu) Status: New => Fix Released ** No longer affects: snapd-glib (Ubuntu) ** Changed in: snapd-glib (Ubuntu Xenial) Status: New => Triaged ** Changed in: snapd-glib (Ubuntu Xenial) Importance: Undecided => High ** Description changed: + [Impact] + Older versions of Ubuntu are running older versions of snapd-glib. There have since been bug fixes and support for newer API that was added to snapd since release. + + [Test Case] + 1. Delete existing Snap credentials by deleting keys com.ubuntu.UbuntuOne.GnomeSoftware in Seahorse. + 2. Start GNOME Software + 3. Install a snap (e.g. moon-buggy) + + Expected result: + User is prompted for Ubuntu credentials and is able to install snap. + + Observed result: + Works as expected (i.e. only looking for regressions). + + [Regression Potential] + There is a risk of breaking existing use cases. This is reduced by the regression tests in the package and the newer versions of snapd-glib working in newer releases. + The xenial backport of the fix for 1781428 malfunctioned due to the use of snapd-glib behaviour introduced after the version included in xenial: namely auto-connection (and reconnection) to the snapd socket that was introduced in snapd-glib 1.24. With the policy module loaded, Pulse Audio will contact snapd to check the interfaces plugged by a client in order to decide whether to provide access to the microphone. As the Pulse Audio daemon is long lived, it is not uncommon for the socket connection to be disconnected (either due to a timeout, or because snapd is upgraded while the user is logged in). So simply adding a snapd_client_connect() call at module initialisation time is not sufficient. The specific snapd-glib calls that could be affected are: - * snapd_client_list_one_async - * snapd_client_get_interfaces_async + * snapd_client_list_one_async + * snapd_client_get_interfaces_async -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1793298 Title: snapd-glib changes needed for pulseaudio snap policy module xenial backport Status in snapd-glib source package in Xenial: Triaged Bug description: [Impact] Older versions of Ubuntu are running older versions of snapd-glib. There have since been bug fixes and support for newer API that was added to snapd since release. [Test Case] 1. Delete existing Snap credentials by deleting keys com.ubuntu.UbuntuOne.GnomeSoftware in Seahorse. 2. Start GNOME Software 3. Install a snap (e.g. moon-buggy) Expected result: User is prompted for Ubuntu credentials and is able to install snap. Observed result: Works as expected (i.e. only looking for regressions). [Regression Potential] There is a risk of breaking existing use cases. This is reduced by the regression tests in the package and the newer versions of snapd-glib working in newer releases. The xenial backport of the fix for 1781428 malfunctioned due to the use of snapd-glib behaviour introduced after the version included in xenial: namely auto-connection (and reconnection) to the snapd socket that was introduced in snapd-glib 1.24. With the policy module loaded, Pulse Audio will contact snapd to check the interfaces plugged by a client in order to decide whether to provide access to the microphone. As the Pulse Audio daemon is long lived, it is not uncommon for the socket connection to be disconnected (either due to a timeout, or because snapd is upgraded while the user is logged in). So simply adding a snapd_client_connect() call at module initialisation time is not sufficient. The specific snapd-glib calls that could be affected are: * snapd_client_list_one_async * snapd_client_get_interfaces_async To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/xenial/+source/snapd-glib/+bug/1793298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731612] Re: nautilus will not start from launch bar
No, but I am still on 16.04.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1731612 Title: nautilus will not start from launch bar Status in nautilus package in Ubuntu: Incomplete Bug description: nautilus lives under the top icon on my launch bar both 1 and clicking the icon results in a flashing icon the flashing stops after a little while and nothing further happens ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 [modified: usr/share/applications/nautilus.desktop] 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: Sat Nov 11 20:46:26 2017 GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+45+24'" b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 'none']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2017-07-27 (106 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814189] [NEW] login screen very long to start, then keyboard layout fallback to qwerty
Public bug reported: sometimes login screen is long to start (this time it was fstrim slowing down disks), then I must enter my password in qwerty (instead of azerty). desktop is ok (azerty). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 01:19:28 2019 InstallationDate: Installed on 2018-04-03 (303 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (101 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1814189 Title: login screen very long to start, then keyboard layout fallback to qwerty Status in gdm3 package in Ubuntu: New Bug description: sometimes login screen is long to start (this time it was fstrim slowing down disks), then I must enter my password in qwerty (instead of azerty). desktop is ok (azerty). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 01:19:28 2019 InstallationDate: Installed on 2018-04-03 (303 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1814189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813429] Re: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, c
Please Disregard last comment. It is listed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1813429 Title: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, copy/paste will stop and error reported. Status in libmtp package in Ubuntu: New Bug description: Steps to reproduce: 1) Plug phone into computer. 2) Copy a large number of directories with nested file structures to phone from computer hard drive, via Nautilus: [highlight files on computer, then ctrl-c; go to directory on phone, then ctrl-v]. Expected outcome: No copy errors. Actual Outcome: Usually, the expected outcome; randomly, Error: "Error while copying .m4a>. There was an error copying the file into mtp://LGE_LG-G710_LGG710PMd4...". Show more details : "File not found". Options: ["Cancel","Skip All","Skip"]. I can't force reproducibility, sometimes it won't complain, but larger copy/paste datasets correlate to more likely ending up with an error. Workarounds: At error, select 'Cancel'; delete the offending subdirectory/file from the phone; restart the copy-paste operation from the point of failure; repeat as necessary. lsb_release -rd: "Ubuntu 18.10" apt-cache policy nautilus: "nautilus: Installed: 1:3.26.4-0ubuntu7.1 Candidate: 1:3.26.4-0ubuntu7.1 Version table: *** 1:3.26.4-0ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.4-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 14:01:47 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+67+30'" InstallationDate: Installed on 2019-01-10 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1813429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1660568] Re: (Automatically) changing wallpaper crashes gksudo nautilus
I raised this a long time ago. I'm now on 18.04 using gnome and have no urge to return to unity. I will have double checked and walked through the steps I originally described so I suggest you try that. Sorry I can't be of more help but perhaps if there'd been a faster response... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1660568 Title: (Automatically) changing wallpaper crashes gksudo nautilus Status in nautilus package in Ubuntu: Invalid Status in variety package in Ubuntu: New Bug description: 16.04.1-64 variety: Installed: 0.6.3-0~581~201611011900~ubuntu14.04.1 nautilus: Installed: 1:3.18.4.is.3.14.3-0ubuntu5 gksudo nautilus force variety to change wallpaper with image > next, at change user nautilus along with desktop crashes open user nautilus and click on desktop to restore root nautilus crashes If I quit variety indicator before gksudo nautilus there's no crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1660568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813429] Re: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, c
I observed that libmtp contains a large listing of device/vendor information tied in with special flags for handling/mitigating errors. I noticed my device is not in the list. idVendor=1004, idProduct=631c https://sourceforge.net/p/libmtp/code/ci/master/tree/src/music-players.h Not sure if libmtp's adding of my device's info and related device flags would make a difference? https://sourceforge.net/p/libmtp/code/ci/master/tree/src/device- flags.h:314 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1813429 Title: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, copy/paste will stop and error reported. Status in libmtp package in Ubuntu: New Bug description: Steps to reproduce: 1) Plug phone into computer. 2) Copy a large number of directories with nested file structures to phone from computer hard drive, via Nautilus: [highlight files on computer, then ctrl-c; go to directory on phone, then ctrl-v]. Expected outcome: No copy errors. Actual Outcome: Usually, the expected outcome; randomly, Error: "Error while copying .m4a>. There was an error copying the file into mtp://LGE_LG-G710_LGG710PMd4...". Show more details : "File not found". Options: ["Cancel","Skip All","Skip"]. I can't force reproducibility, sometimes it won't complain, but larger copy/paste datasets correlate to more likely ending up with an error. Workarounds: At error, select 'Cancel'; delete the offending subdirectory/file from the phone; restart the copy-paste operation from the point of failure; repeat as necessary. lsb_release -rd: "Ubuntu 18.10" apt-cache policy nautilus: "nautilus: Installed: 1:3.26.4-0ubuntu7.1 Candidate: 1:3.26.4-0ubuntu7.1 Version table: *** 1:3.26.4-0ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.4-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 14:01:47 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+67+30'" InstallationDate: Installed on 2019-01-10 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1813429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted pygobject into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pygobject/3.26.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pygobject (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Fix Committed Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813567] Re: cogl ftbfs in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted cogl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cogl/1.22.2-3ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/1813567 Title: cogl ftbfs in 18.04 LTS Status in cogl package in Ubuntu: Fix Released Status in cogl source package in Bionic: Fix Committed Status in cogl package in Debian: Fix Released Bug description: * Impact the package fails to build, see http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html * Test case Check that the package once accepted is building without issue * Regression potential There is no code change but it's a rebuild so it could be impacted by a toolchain change, make sure that GNOME keeps working without rendering issue and that totem does play videos fine -- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html cogl ftbfs. dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libcogl20/DEBIAN/symbols doesn't match completely debian/libcogl20.symbols --- debian/libcogl20.symbols (libcogl20_1.22.2-3_amd64) +++ dpkg-gensymbolsclZaGi 2019-01-28 08:45:17.335924588 + @@ -174,6 +174,7 @@ cogl_feature_flags_get_type@Base 1.17.4 cogl_features_available@Base 1.17.4 cogl_fence_closure_get_user_data@Base 1.17.4 + cogl_filter_return_get_type@Base 1.22.2-3 cogl_fixed_atan2@Base 1.17.4 cogl_fixed_atan@Base 1.17.4 cogl_fixed_cos@Base 1.17.4 dh_makeshlibs: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1813567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662418] Re: Can't view photos on SD card from Canon SX610 because "windows is hibernated"?!
closing then since it's an user error, the windows/hibernate issue is already reported ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1662418 Title: Can't view photos on SD card from Canon SX610 because "windows is hibernated"?! Status in nautilus package in Ubuntu: Invalid Bug description: I got my wife a Canon SX610 HS camera for xmas. Alas, whenever she puts its SD card into our Ubuntu 16.04 computer to look at the pictures, she gets the error Unable to access "209 GB Volume" Error mounting /dev/sdb2 at /media/zilf/902C022F2C021140: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1003,gid=1003" "/dev/sdb2" "/media/zilf/902C022F2C021140"' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sdb2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Nautilus should do the mount readonly rather than throwing an error. (Yeah, she won't be able to delete photos, but at least she'd be able to see them.) (This is related to bug 1362840, but that one is really Windows; this is a camera.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 21:43:47 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+422'" InstallationDate: Installed on 2016-11-06 (92 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813578] Re: duplicity ftbfs in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted duplicity into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/duplicity/0.7.17-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1813578 Title: duplicity ftbfs in 18.04 LTS Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Bionic: Fix Committed Bug description: * Impact the package fails to build, see http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html * Test case Check that the package once accepted is building without issue * Regression potential The change is to add a gpg option, that's already in cosmic and shouldn't have any side effect, check that deja-dup backups still work as they should though --- duplicity ftbfs. == ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest) Test getting signature chain fileobjs from archive_dir -- Traceback (most recent call last): File "/<>/testing/unit/test_collections.py", line 188, in test_sigchain_fileobj self.sigchain_fileobj_check_list(self.sigchain_fileobj_get(None)) File "/<>/testing/unit/test_collections.py", line 180, in sigchain_fileobj_check_list test_fileobj(0, "Hello, world!") File "/<>/testing/unit/test_collections.py", line 177, in test_fileobj fileobjlist[i].close() File "/<>/duplicity/dup_temp.py", line 227, in close assert not self.fileobj.close() File "/<>/duplicity/gpg.py", line 304, in close self.gpg_failed() File "/<>/duplicity/gpg.py", line 271, in gpg_failed raise GPGError(msg) GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: starting migration from earlier GnuPG versions gpg: porting secret keys from '/<>/testing/gnupg/secring.gpg' to gpg-agent gpg: key 839E6A2856538CCF: secret key imported gpg: key BCEF1B4DB5FA894F: secret key imported gpg: key 453005CE9B736B2A: secret key imported gpg: migration succeeded gpg: CAST5 encrypted data gpg: encrypted with 1 passphrase gpg: WARNING: message was not integrity protected gpg: Hint: If this message was created before the year 2003 it is likely that this message is legitimate. This is because back then integrity protection was not widely used. gpg: Use the option '--ignore-mdc-error' to decrypt anyway. gpg: decryption forced to fail! gpg: WARNING: unsafe permissions on homedir '/<>/testing/gnupg' = End GnuPG log = -- Ran 418 tests in 881.428s FAILED (errors=1, skipped=9) Test failed: error: Test failed: debian/rules:11: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1813578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Today, as often, I installed Ubuntu to a new Linux user, coming from Windows. Everything is great and well designed, intuitive, and quick ... then ... this lady began to feel confortable and wanted to quickly jump to the photo named "IMG232.jpg"; so she started to type "IMG" on her folder, containing hundred of photos and sub-folder and ... yeah, I suddently remembered WHY I gave up using this software a bunch of years ago. How to explain this to this lady ? After a while she understood that those files that dissapeared and appeared under her eyes wasn't a deletion, but a search result. How to know WITCH IMG232.jpg was the one of the **current** folder ? The folder of the bro's weeding ? She logically asked me how to change this default strange behavior and I logically said to her "oh yeah, I remember this is a way old story; this MUST be an option to disable this". And ... WT-holly-F ? No, no option at all :/ I **CAN'T BELIEVE** that after more than 5 years there's still NO option to DECIDE what should be the default behavior of the default browser. And when I see the ridiculous patch [1] this implies, I can't believe it even less. What would be the cost of an option in program's preferences ?! 1. https://launchpadlibrarian.net/368070783/nautilus-restore-typeahead-patch.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1660568] Re: (Automatically) changing wallpaper crashes gksudo nautilus
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1660568 Title: (Automatically) changing wallpaper crashes gksudo nautilus Status in nautilus package in Ubuntu: Invalid Status in variety package in Ubuntu: New Bug description: 16.04.1-64 variety: Installed: 0.6.3-0~581~201611011900~ubuntu14.04.1 nautilus: Installed: 1:3.18.4.is.3.14.3-0ubuntu5 gksudo nautilus force variety to change wallpaper with image > next, at change user nautilus along with desktop crashes open user nautilus and click on desktop to restore root nautilus crashes If I quit variety indicator before gksudo nautilus there's no crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1660568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805444] Missing SRU information
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Bug description: Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687411] Re: If default zoom set to ≠ 100% icons have different sizes
Closing since the previous comment states it doesn't happen in newer versions ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1687411 Title: If default zoom set to ≠ 100% icons have different sizes Status in nautilus package in Ubuntu: Fix Released Bug description: Hi, In Nautilus 3.14.3 / Ubuntu Unity 16.04.2 If default zoom in Nautilus preferences is not 100%, icons have many sizes or if I manually zoom into a folder [ctrl]+[+]. Screenshots attached. ___ Is this https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407 the same problem ? ___ 2017-05-12 Problem happens with Humanity & Ubuntu icon themes ( the default ones ). Problem does not happen with other icon themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404537] Re: Make Desktop Background In Nautilus Makes No Sense and Bad Positioning
Issues resolved so closing Papercuts task. ** Changed in: hundredpapercuts Status: New => Fix Released ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1404537 Title: Make Desktop Background In Nautilus Makes No Sense and Bad Positioning Status in One Hundred Papercuts: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: When you right click on a picture in Nautilus there is a button "Make Desktop Background" but this is too close to "Move To The Rubbish Bin" countless times, when I am trying to get rid of a picture I have set it as my wallpaper, surely I can't be the only one to keep doing this. Also "Make Desktop Background" makes no sense as it should be more like "Set As Desktop Background" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
Hello Amr, or anyone else affected, Accepted gnome-settings-daemon into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.28.1-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: In Progress Status in gnome-settings-daemon source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667505] Re: Files and Trash hang
Do you still get that issue in newer Ubuntu versions? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1667505 Title: Files and Trash hang Status in nautilus package in Ubuntu: Incomplete Bug description: Clicking on Files or Trash icons in launcher occasionally does nothing. This is intermittent and not reproducible. It has happened twice since a recent fresh install of 16.04.2. The system generally seems to have to run all day before getting this bug. This behaviour is new to 16.04.2 and was not present in 16.04. The solution is to reboot. If someone can give instructions on what to analyze prior to shutdown, we may be able to solve this today. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 23 17:38:43 2017 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+1030+502'" InstallationDate: Installed on 2017-02-17 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1667505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668361] Re: Quieter PC with automatic Sleep State command to all HDDs
Thank you for your bug report, that's not something Ubuntu is going to work on, also nautilus is probably the wrong place for adding disk modes handling since it's only an application and not autostarted on boot ** Changed in: nautilus (Ubuntu) Importance: Undecided => Wishlist ** Changed in: nautilus (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1668361 Title: Quieter PC with automatic Sleep State command to all HDDs Status in nautilus package in Ubuntu: Won't Fix Bug description: * This is NOT a bug, but a feature request. * It is known that mechanical HDDs produce a lot of noise. I have several HDDs and mostly I use only one of them at every single moment. The problem is that ALL HDDs are working automatically when the PC starts. (I can hear them working even if the SATA port is disabled by the motherboard.) This not only wears down the HDDs, but also produces a lot of noise which shouldn't happen because that most of them aren't being used. It would be very helpful if Ubuntu would send a "Sleep State" command to all mechanical HDDs upon startup. (Sending that command to SSDs isn't required.) --- In addition, nautilus itself could verify upon each "unmount" action whether all HHDs are being used. If there are HDDs which aren't being used (doesn't contain mounted partitions) - then nautilus could send a Sleep State to those mechanical HDDs. By "unmount action", I mean to the unmounting that happens when clicking on the "up" arrow in the GUI of Nautilus where all available partitions are presented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1668361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662487] Re: Can't double click on folders during icon view with Wacom Stylus
Is that still an issue in newer versions? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1662487 Title: Can't double click on folders during icon view with Wacom Stylus Status in nautilus package in Ubuntu: Incomplete Bug description: When on icon view and using a Wacom Bamboo, opening folders via double-click doesn't work. The same happens on the desktop. It works when the folder is in list view. Ubuntu GNOME 16.04 Files 3.18.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663003] Re: The fuction "Keep in line" do not works.
The desktop view has been deprecated in the newest nautilus version (in favor of a new component), closing this report ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1663003 Title: The fuction "Keep in line" do not works. Status in nautilus package in Ubuntu: Invalid Bug description: The fuction "Keep in line" do not works. The icons on desktop continue to be overlapping and misalign. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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: Wed Feb 8 16:56:40 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 82G33/G31 Express Integrated Graphics Controller [1849:29c2] InstallationDate: Installed on 2017-01-30 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=d5a9640e-861d-4d51-9e8c-a7552c19a161 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree""true" EndSection dmi.bios.date: 03/17/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Phitronics G31VS2-M dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd03/17/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnPhitronicsG31VS2-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 8 15:47:44 2017 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1663003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672950] Re: nautilus launched from Unity8 opens a 'Desktop' window
the desktop view has been removed from nautilus, the usecase described here is also not currently maintained ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1672950 Title: nautilus launched from Unity8 opens a 'Desktop' window Status in Canonical System Image: New Status in nautilus package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Invalid Bug description: nautilus launched from Unity8 opens a 'Desktop' window. It needs to be run with --no-desktop to avoid that. Although this issue is confused by two other bugs: * Unity8 incorrectly chooses Xmir -> bug 1672931 ; and * When using Xmir the desktop window is transparent -> bug 1672949 These are three separate bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670683] Re: Nautilus ignores "Documents" if it is a symlink to a NFS share
Is that still an issue in newer versions? Is the folder showing if you quit/restart nautilus? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1670683 Title: Nautilus ignores "Documents" if it is a symlink to a NFS share Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus I have a NFS share where many Ubuntu desktops share the same remote folder as Documents (German "Dokumente") and Pictures (German "Bilder") folders. This works perfectly, only Nautilus refuses to show the "Dokumente" folder in its left side navigation bar. One of the computers weirdly works perfectly (folders are shown), but all others (3) don't have these entries, see screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 7 14:41:37 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1286x911+222+103'" InstallationDate: Installed on 2016-09-28 (159 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1670683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687478] Re: "properties" -> "open with" - defective statemachine
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1687478 Title: "properties" -> "open with" - defective statemachine Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is defective. To open this dialogue reightclick a file, click "properties" and select "Open With" tab. The behaviour of the button "Set as default" is correct. After clicking that button, the behaviour of the "Add" button is also correct. But clicking only the button "Add" after opening the dialogue without click "Set as default", it shows the wrong behavior. Clicking "add" does always the same like clicking "Set as Default". Clicking "Set as default" one time repairs that behavior. Why that? There are two problems. Clicking "Add" does have the behaviour like clicking "Set as default" to have one "Default Application" set, if no "Default Application" is set. That is correct. 1st problem: This dialogue starts in state believing no default application is set. But the already set default application is listed as "Default Application". That means, clicking "Add" does the same like "Set as default", when it should not. 2nd related problem: Clicking "Add" to set the "Default Application" the first time, does not set the state that the "Default Application" is set like clicking "Set as default" does. So the 1st problem is repeated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 1 23:09:06 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'253' b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1687478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
Hello Gert, or anyone else affected, Accepted mutter into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: New Status in mutter source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: New Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on cogl_texture_get_height [ Test case ] No clear reproducer is know for such issue, crashes should be monitored in e.u.c checking that this is not happening anymore for the version in proposed. [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711438] Re: nautilus crashed with SIGABRT in g_assertion_message() (filename != NULL)
There has similar problems that got fixed since you reported the issue, e.g https://gitlab.gnome.org/GNOME/nautilus/issues/640 ... do you still get the problem in the current version? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1711438 Title: nautilus crashed with SIGABRT in g_assertion_message() (filename != NULL) Status in nautilus package in Ubuntu: Incomplete Bug description: During the display of a rather large SMB share directory ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.24.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 17 20:33:10 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-04-01 (138 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-06-08 (70 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814185] [NEW] /usr/bin/nautilus:11:nautilus_path_bar_size_allocate:gtk_widget_size_allocate_with_baseline:gtk_box_size_allocate_no_center:gtk_box_allocate_contents:gtk_css_gad
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7.1, the problem page at https://errors.ubuntu.com/problem/00dc9cddf551a06041fc17b5e0d7b745973c0e56 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1814185 Title: /usr/bin/nautilus:11:nautilus_path_bar_size_allocate:gtk_widget_size_allocate_with_baseline:gtk_box_size_allocate_no_center:gtk_box_allocate_contents:gtk_css_gadget_allocate Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7.1, the problem page at https://errors.ubuntu.com/problem/00dc9cddf551a06041fc17b5e0d7b745973c0e56 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp