[Desktop-packages] [Bug 1707691] Re: [xenial] xserver-xorg-dev should depend on libxfont1-dev
** No longer affects: libxfont (Ubuntu Xenial) ** No longer affects: libxfont (Ubuntu) -- 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/1707691 Title: [xenial] xserver-xorg-dev should depend on libxfont1-dev Status in xorg-server package in Ubuntu: Invalid Status in xorg-server source package in Xenial: Fix Committed Bug description: [Impact] /usr/include/xorg/dixfont.h includes X11/fonts/fontutil.h. fontutil.h is contained in libxfont1-dev package not libxfont-dev package (version 2.0.1). I am trying to build xorgxrdp and it fails because fontutil.h is missing. In Ubuntu, libxfont1-dev package is required however libxfont1-dev and libxfont-dev cannot be installed together. This is the problem. Package info: Ubuntu 16.04 $ dpkg -la | grep -e xserver-xorg-dev -e libxfont-dev ii libxfont-dev 1:2.0.1-3~ubuntu16.04.1 amd64X11 font rasterisation library (development headers) ii xserver-xorg-dev 2:1.18.4-0ubuntu0.3 amd64Xorg X server - development files [Test case] xserver-xorg-dev needs to change the dependency on libxfont-dev to libxfont1-dev. [Regression potential] none, this is just to reflect the current state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1707691/+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 1687981] Re: Backport packages for 16.04.3 HWE stack
** Changed in: xorg-server (Ubuntu Xenial) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1716084] Re: gnome-shell crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1714330 *** https://bugs.launchpad.net/bugs/1714330 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1714330, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1716084/+attachment/4946755/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946757/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946760/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946761/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946762/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946763/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716084/+attachment/4946764/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714330 gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1716084 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() Status in gnome-shell package in Ubuntu: New Bug description: At system logon time. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Sep 9 10:52:02 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-24 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f54c4c5e836:mov0x1a0(%rax),%rax PC (0x7f54c4c5e836) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716084/+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 1676573] Re: gnome-shell restarts every 20 minutes because of SEGFAULT
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1676573 Title: gnome-shell restarts every 20 minutes because of SEGFAULT Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, I'm using the latest Ubuntu Gnome 17.04 development version and I've noticed that every 20 minutes, not matter what I do, my gnome-shell restarts because of segfault. In the Logs app I have found something like that: 21:16:35 kernel: gnome-shell[21368]: segfault at 58000321 ip 58000321 sp 7ffc334e8108 error 14 in gnome-shell[55ead3143000+4000] 20:56:33 kernel: gnome-shell[20932]: segfault at 320008 ip 7f55ad542632 sp 7ffc7abbce40 error 4 in libmozjs-38.so.0.0.0[7f55ad169000+6c7000] 20:36:32 kernel: gnome-shell[18956]: segfault at 7ffc0008 ip 7ff49fe01632 sp 7ffcfb95b670 error 4 in libmozjs-38.so.0.0.0[7ff49fa28000+6c7000] 20:16:31 kernel: gnome-shell[18265]: segfault at 58000321 ip 58000321 sp 7ffe24bc5a18 error 14 in gnome-shell[56478bbb+4000] I'll be happy to provide any more information, just write me what is needed. Well... I just realized the problem concerns my Backslide extension, that switches my desktop wallpaper every 20 minutes. I'll investigate the problem and probably talk with author of the extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1676573/+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 1703377] Re: Gnome online account login prevents paste or autotype
[Expired for gnome-online-accounts (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Expired Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C
Could this be why I sometimes get no keyboard input at all in my user sessions in Artul...? (Can type password in GDM, but then all keyboard input is lost until reboot.) -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1710637/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
#82 Helped me as well. And I'm 17.04... It'd be nice to see this fixed... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1716078] [NEW] problem regarding detecting intel graphic card and changing my resolution
Public bug reported: ubuntu 14.04 cannot detect my graphic card, which is intel HD graphics 630, and I cannot change my resolution. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 8 18:11:33 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:108e] InstallationDate: Installed on 2017-09-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire TC-780 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic.efi.signed root=UUID=957edbfd-0d99-4b8f-8c66-a16283cc26ed ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R02-A2 dmi.board.name: Aspire TC-780(KBL) dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR02-A2:bd02/21/2017:svnAcer:pnAspireTC-780:pvr:rvnAcer:rnAspireTC-780(KBL):rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire TC-780 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 8 18:03:21 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1716078 Title: problem regarding detecting intel graphic card and changing my resolution Status in xorg package in Ubuntu: New Bug description: ubuntu 14.04 cannot detect my graphic card, which is intel HD graphics 630, and I cannot change my resolution. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 8 18:11:33 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:108e] InstallationDate: Installed on 2017-09-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire TC-780 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic.efi.signed root=UUID=957edbfd-0d99-4b8f-8c66-a16283cc26ed ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R02-A2 dmi.board.name: Aspire TC-780(KBL) dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR02-A2:bd02/21/2017:svnAcer:pnAspireTC-780:pvr:rvnAcer:rnAspireTC-780(KBL):rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire TC-780 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Desktop-packages] [Bug 1716077] [NEW] Settings app draws window controls incorrectly
Public bug reported: When changing window controls to the left side. Gnome control center will not draw them correctly. the controls are drawn on the middle of the window instead of the left. I have made this change by setting /org/gnome/desktop/wm/preferences/button-layout to 'close,minimize,maximize:appmenu' in dconf-editor. this issue is not present if the window controls remain on the right hand side. System info: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 Package info: gnome-control-center: Installed: 1:3.25.92.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 11:03:40 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful gnome-17.10 ** Attachment added: "Example of issue" https://bugs.launchpad.net/bugs/1716077/+attachment/4946717/+files/Screenshot%20from%202017-09-09%2011-07-51.png -- 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/1716077 Title: Settings app draws window controls incorrectly Status in gnome-control-center package in Ubuntu: New Bug description: When changing window controls to the left side. Gnome control center will not draw them correctly. the controls are drawn on the middle of the window instead of the left. I have made this change by setting /org/gnome/desktop/wm/preferences/button-layout to 'close,minimize,maximize:appmenu' in dconf-editor. this issue is not present if the window controls remain on the right hand side. System info: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Package info: gnome-control-center: Installed: 1:3.25.92.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 11:03:40 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716077/+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 290639] Re: NetworkManager cannot handle both eth0 and ppp0 at the same time
** Changed in: network-manager Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/290639 Title: NetworkManager cannot handle both eth0 and ppp0 at the same time Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Triaged Bug description: Binary package hint: network-manager Okay, so I have a pppoe-connection to my internet-provider which I connect to via a WLAN-AP that's connected with my home-network. In network-manager I can set up my Ethernet (eth0) connection to connect to the local network and my ppp0e (ppp0) connection to the internet. When I click on network-manager, I only have radio-buttons to select the desired "wired connection" which only allows me to EITHER start eth0 OR ppp0. When I'm connected to the internet, I can't access the LAN and vice-versa. The ony solution for me right now is to use pppoeconf and configure the eth0-connection via config file, which of course breaks network- manager. What I am asking for is simple: Allow the use of more than just one "wired connection" in network-manager (ditch the radio buttons and make them "multiple choice"?) here's my etc/network/interfaces: (comments were made by me for better readability here, they're not in the file itself) ##BEGIN interfaces auto lo iface lo inet loopback auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf provider dsl-provider auto eth0 iface eth0 inet static address 192.168.0.3 netmask 255.255.255.0 gateway 192.168.0.1 ##END interfaces System is 8.10 with all the latest updates, network-manager is: network-manager: Installiert: 0.7~~svn20081018t105859-0ubuntu1 Kandidat: 0.7~~svn20081018t105859-0ubuntu1 Versions-Tabelle: *** 0.7~~svn20081018t105859-0ubuntu1 0 500 http://at.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/290639/+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 1716068] [NEW] Gnome Shell crashes randomly
Public bug reported: When using Ubuntu Gnome 16.04, it is common for gnome-shell to crash unexpectedly, especially when performing intensive tasks. I've found that I was able to replicate the error by following these steps: Download and install a copy of Ubuntu Gnome 16.04.2 in VirtualBox. Open a screen displaying App icons in a menu, such as the app grid in the Gnome Shell overlay or the Arc Menu Gnome Shell extension (https://extensions.gnome.org/extension/1228/arc-menu/). Install all the latest software updates from the Software Updater or Synaptic. Upgrading all the packages between 16.04.2 to 16.04.3 seems to over-load Gnome Shell and cause the crash in the middle of the installation process. This crash always seems to occur after opening a screen with app icons and I'm not sure why. I've attached my .crash file updated with a symbolic stack trace.I hope this info and my attachment proves helpful in fixing the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 8 19:24:22 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['arc-m...@linxgem33.com']" b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 'org.gnome.Nautilus.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-09-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/bugs/1716068/+attachment/4946700/+files/_usr_bin_gnome-shell.1000.crash -- 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/1716068 Title: Gnome Shell crashes randomly Status in gnome-shell package in Ubuntu: New Bug description: When using Ubuntu Gnome 16.04, it is common for gnome-shell to crash unexpectedly, especially when performing intensive tasks. I've found that I was able to replicate the error by following these steps: Download and install a copy of Ubuntu Gnome 16.04.2 in VirtualBox. Open a screen displaying App icons in a menu, such as the app grid in the Gnome Shell overlay or the Arc Menu Gnome Shell extension (https://extensions.gnome.org/extension/1228/arc-menu/). Install all the latest software updates from the Software Updater or Synaptic. Upgrading all the packages between 16.04.2 to 16.04.3 seems to over-load Gnome Shell and cause the crash in the middle of the installation process. This crash always seems to occur after opening a screen with app icons and I'm not sure why. I've attached my .crash file updated with a symbolic stack trace.I hope this info and my attachment proves helpful in fixing the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 8 19:24:22 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['arc-m...@linxgem33.com']" b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 'org.gnome.Nautilus.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-09-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/ubuntu/+source/gnome-shell/+bug/1716068/+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 1715883] Re: Can not drag and drop from network shares to most apps
** Changed in: thunar Status: Unknown => Confirmed ** Changed in: thunar Importance: Unknown => Medium -- 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/1715883 Title: Can not drag and drop from network shares to most apps Status in Nautilus: New Status in thunar: Confirmed Status in nautilus package in Ubuntu: New Bug description: Dropping a file from a network share into most applications (Claws Mail, Chromium, Thunderbird, ...) fails silently. This is because the URIs sent by Nautilus are GFVS URIs with various schemes (smb://, davs://, ...) and most applications doing POSIX I/O can't do anything with them. This is easy to check by dropping a file from a network share into the Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1715883/+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 1715722] Re: Allow safe override of GDM3 theme
The build finished, and I installed Ubuntu, Pop, and GNOME sessions side-by-side. All three worked, and the GDM theme changed based on the alternative selected. I believe the second patch version works as expected. -- 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/1715722 Title: Allow safe override of GDM3 theme Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1715722/+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 1716022] Re: Mouse cursor jaggy movements
Played around with magnification. Pressing Super-Alt-8 somehow creates this situation. Increasing the magnification to 200%, pressing Super-Alt-8 and reverting to 100% remedies the effect. Thus: An issue that I cannot explain. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1716022 Title: Mouse cursor jaggy movements Status in xorg package in Ubuntu: Invalid Bug description: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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/xorg/+bug/1716022/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
Moving this bug under cups package. ** Package changed: cups-filters (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1715722] Re: Allow safe override of GDM3 theme
The attachment "ubuntu_gdm_alternatives.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715722 Title: Allow safe override of GDM3 theme Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1715722/+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 1716042] [NEW] [Precision 5520, Realtek ALC3266, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: Ubuntu 16.04 LTS Crackling sound comes from only the left speaker! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesco 2538 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 8 15:24:37 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-02-25 (195 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Precision 5520, Realtek ALC3266, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716042 Title: [Precision 5520, Realtek ALC3266, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 16.04 LTS Crackling sound comes from only the left speaker! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesco 2538 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 8 15:24:37 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-02-25 (195 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Precision 5520, Realtek ALC3266, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716042/+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 1565975] Re: scanning sometimes impossible with LIDE 210
Nils Kassube, I am closing this report because as per https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1565975/comments/13 the bug has been fixed in the latest development version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: sane-backends (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1565975 Title: scanning sometimes impossible with LIDE 210 Status in sane-backends package in Ubuntu: Fix Released Bug description: If I try to scan with xsane or skanlite there is often an error message like "Error during device I/O". If that error message appears, I have to replug the scanner to make it working again. There are several symptom which are not always the same: Sometimes only preview doesn't work, sometimes scanning doesn't work. Sometimes scanning with 75 dpi / color results in a corrupted image with vertical coloured lines while scanning the same text printout with 600 dpi results in a normal output. Often the scanner is very noisy compared to the sound I am used to from scanning with the trusty release. Using the amd64 version on the same machine works, but the scanner is quite noisy compared to the sound I am used to from the trusty release. WORKAROUND: Use the trusty packages of xsane, libsane and other dependencies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 CurrentDesktop: KDE Date: Mon Apr 4 21:43:22 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160404) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1565975/+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 1716034] [NEW] Network manager stops managing Ethernet links after upgrade
Public bug reported: After upgrading Ubuntu, it stopped configuring the word connection on my headless computer (super annoying to deal with). In any case, it was an issue with NM config change that caused my wired device to become unmanaged. There are several people discussing this here: https://askubuntu.com/questions/882806/ethernet-device-not-managed ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1716034 Title: Network manager stops managing Ethernet links after upgrade Status in network-manager package in Ubuntu: New Bug description: After upgrading Ubuntu, it stopped configuring the word connection on my headless computer (super annoying to deal with). In any case, it was an issue with NM config change that caused my wired device to become unmanaged. There are several people discussing this here: https://askubuntu.com/questions/882806/ethernet-device-not-managed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716034/+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 1565975] Re: scanning sometimes impossible with LIDE 210
Today I have tested the latest update for the i386 version of Artful Ardvark. With this version (1.0.27-1~experimental2) the scanner works without excessive noise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1565975 Title: scanning sometimes impossible with LIDE 210 Status in sane-backends package in Ubuntu: Triaged Bug description: If I try to scan with xsane or skanlite there is often an error message like "Error during device I/O". If that error message appears, I have to replug the scanner to make it working again. There are several symptom which are not always the same: Sometimes only preview doesn't work, sometimes scanning doesn't work. Sometimes scanning with 75 dpi / color results in a corrupted image with vertical coloured lines while scanning the same text printout with 600 dpi results in a normal output. Often the scanner is very noisy compared to the sound I am used to from scanning with the trusty release. Using the amd64 version on the same machine works, but the scanner is quite noisy compared to the sound I am used to from the trusty release. WORKAROUND: Use the trusty packages of xsane, libsane and other dependencies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 CurrentDesktop: KDE Date: Mon Apr 4 21:43:22 2016 InstallationDate: Installed on 2016-04-04 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160404) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1565975/+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 1715722] Re: Allow safe override of GDM3 theme
Linking to an upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=787454 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=787454 Importance: Unknown Status: Unknown -- 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/1715722 Title: Allow safe override of GDM3 theme Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1715722/+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 1715722] Re: Allow safe override of GDM3 theme
11:01 Laney goodnight! 11:01 jackpot51 Ok, good night Laney 11:12 didrocksjackpot51: mind toning a little bit done please? 11:12 didrocksjackpot51: you are quite offensive in that bug report 11:13 didrocksand proposing a patch that you even didn't test it doesn't really pledge your saying 11:14 jackpot51 I know I screwed up, and I am sorry. But I don't want to have our amount of maintenance increased significantly because of a hardcoded GDM theme. For the short term, I can override the gnome-shell package, but it is not good for release 11:14 didrocksjackpot51: does it justify this tone? 11:14 jackpot51 Building on gnome-shell on a new Artful installation is breaking, so I have to wait for the launchpad build to test changes. 11:15 jackpot51 No, it does not. I apologize for being offensive 11:15 didrocksok, better ground (not really fancy having this kind of discussion on Friday at 7:15PM) 11:15 didrocksso, if I have the certainty you will work on a longer term solution, alternatives is ok 11:16 didrocks(as the other solution I gave) 11:16 didrocksI just don't want that we keep this for the LTS 11:17 didrocksdoes it make sense? If so, please test the patch (especially lock screen-wise, that's the part I'm unsure if you install 2 sessions with different lock screen theme, which one will be picked) 11:17 didrocksand if you tell me it's good, I can sponsor it on Monday 11:17 didrocks(after a final round of testing ofc) 11:18 jackpot51 What happened was that user-theme stopped working the day of feature freeze for us, leading to a cascade of theming changes we had to do. This culminated in theming GDM by replacing the ubuntu.css file, which broke my ability to use ubuntu-session. I like to see all three sessions (Ubuntu, Pop, and GNOME) for testing, so I only wanted a way to keep them all installed while having the GDM theme we had designed. That is all. We are in a scramble to get things fixed in a sane way, allowing us to release an ISO with our own theming. I am very sorry for out of line, I have misinterpreted messages from others and gone overboard. 11:18 didrocksbut again, I don't want to carry the patch post-17.10. I think there is a very good opportunity for cooperating inside GNOME to have those easily themeable (Shell, GDM) 11:18 didrocksjackpot51: maybe your company could have talk or even help us within ubuntu itself to get things prepared 11:19 didrocksand we could have cooperated, things were discussed :) 11:20 jackpot51 I agree. I am here, always, with an IRC bouncer. I have been following the ubuntu-devel mailing list, which is where I first saw the gnome-shell changes. Other members of our community are present here. 11:21 didrockscome participate and ask during our meeting on #ubuntu-desktop, and work within ubuntu rather than a derivative, that will help your case being taken into account :) 11:21 jackpot51 I also want to have a good way for all GDM instances on all distributions to have the GDM look and feel configured 11:22 didrocksjackpot51: so, on that one, do we agree with the timeline? You test the patch (especially lock-screen wise), if all +1 (tell it on the bug report), I will sponsor this on Monday, and then, we work together inside GNOME to get the proper fix before the LTS 11:22 jackpot51 I, however, feel there is a systemic issue in the Ubuntu community of not working with people like myself, who are outsiders trying to make their way into the community 11:23 didrocksI'm unsure about the "trying to make their way", I've never seen you participate on our desktop meetings for instance 11:23 didrockswhere we have external contributors like jbicha and others 11:23 jackpot51 I have written patches for ubiquity, wpa, gnome initial setup, gnome control center, and others. Some have been merged, most have been ignored 11:23 didrocksjackpot51: same in any projects unfortunately, I have multiple patches ignored and staying in GNOME bug tracker for years… 11:24 didrocksjackpot51: but you are on IRC, so you can comment and ping on relevant channels, this is your added value :) 11:24 jackpot51 For example, here is a (fully tested) patch for Encrypted Home, something that I was actually present in the Ubuntu Desktop meeting discussing a desire for it: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216 ··· Bug #1699216 “Encrypted home support” : Bugs : accountsservice package : Ubuntu In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. 11:24 didrocks(and #ubuntu-desktop is a good one for those kind of topics) 11:24 ubottu Launchpad bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted home support"
[Desktop-packages] [Bug 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()
** Description changed: - sijui maelezo zaidi + Test Case: + 1. Open the 'Users' panel in gnome-control-center + 2. Select a user then click on 'Unlock' (top right button in the title bar) + + Expected result + The panel is unlocked + + Actual Result + This crash. + ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 16 10:09:12 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-06-26 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: gnome-control-center --overview SegvAnalysis: - Segfault happened at: 0x7ff4ea6fe6e9:cmpq $0x0,0x58(%rax) - PC (0x7ff4ea6fe6e9) ok - source "$0x0" ok - destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7ff4ea6fe6e9:cmpq $0x0,0x58(%rax) + PC (0x7ff4ea6fe6e9) ok + source "$0x0" ok + destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 - ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 + ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1704618 Title: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Test Case: 1. Open the 'Users' panel in gnome-control-center 2. Select a user then click on 'Unlock' (top right button in the title bar) Expected result The panel is unlocked Actual Result This crash. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 16 10:09:12 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-06-26 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7ff4ea6fe6e9:cmpq $0x0,0x58(%rax) PC (0x7ff4ea6fe6e9) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() 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/gnome-control-center/+bug/1704618/+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 1716022] [NEW] Mouse cursor jaggy movements
Public bug reported: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful performance regression single-occurrence 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/1716022 Title: Mouse cursor jaggy movements Status in xorg package in Ubuntu: New Bug description: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version:
[Desktop-packages] [Bug 1715722] Re: Allow safe override of GDM3 theme
Jeremy, you seem quite not listening to the advice we are giving to you, which is a maintainable solution to us. We told you multiple times we were happy to integrate what we think is a good solution from our perspective but you are not listening to those and seem like forcing your patch on us. This isn't how cooperation works. In addition, your unwillingness to even start discussing/thinking about an upstream solution which isn't much more work than the override makes me fear that we'll keep that specific patch for one derative forever. Also, you will understand that proposing a patch obviously broken, and such without testing it first doesn't really give confidence you will follow on a better solution rather that quick hack. Alternatives aren't something which is good to take at that time of the release. I wanted a second option and Laney seemed to agree with me as we discussed on IRC. As solutions: * Laney suggested that if that's really a temporary solution (as you might agree to work on a more long term solution), dpkg-divert is a better idea. I'm happy to ease that for you so that people can still select the ubuntu session by symlink gdm3.css to ubuntu.css in our gnome-shell package. You can then dpkg-divert it and install your own gdm3.css from your theme package (is your package in ubuntu itself btw?). How does that sound? That way, you will get in the same state than the one before we changed gnome-shell.css by gdm3.css. * The other solution, which is the more long term approach is to change for a gsettings key to select the theme. -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1715805] Re: system crash
*** This bug is a duplicate of bug 1715804 *** https://bugs.launchpad.net/bugs/1715804 ** This bug has been marked a duplicate of bug 1715804 system crash -- 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/1715805 Title: system crash Status in xorg package in Ubuntu: New Bug description: I dont know why but in between my os crashes and some orange line comes on my screen then i have to restart my pc it is hard when i am doing my projects i have to do it all again please help and i am new tu ubuntu linux ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Fri Sep 8 10:43:01 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] [1458:d000] InstallationDate: Installed on 2017-09-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 13ee:0001 MosArt Optical Mouse Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. M68MT-D3 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=40de3290-6e3a-40dc-b4a2-40c6893c2d94 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: M68MT-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd06/14/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M68MT-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Fri Sep 8 10:38:46 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715805/+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 1715931] Re: Update to exiv2 version 0.26
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: New Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1715722] Re: Allow safe override of GDM3 theme
10:57 Laney hmm, I guess actually we could use this in Ubuntu to let people use the default gdm theme 11:00 Laney maybe not, that's the built in one isn't it? 11:00 Laney jackpot51: please attach it, I think it's worth considering -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1715722] Re: Allow safe override of GDM3 theme
What is even worse, is that most of these changes that hard-code Ubuntu's theme happened on the edge of the Feature Freeze period, meaning any attempts to revert them or improve them are impaired by bureaucracy. Please try to see why this is a problem, and learn from this in the future. -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1715722] Re: Allow safe override of GDM3 theme
didrocks, I will also work on an upstreamable solution, but I am not very satisfied with your unwillingness to see things from my perspective. You have essentially broken GDM3 for all Ubuntu derivatives, forcing your theme upon them, and then having no desire to work on any solution to remove this hard-coded theming -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1715722] Re: Allow safe override of GDM3 theme
Here is a new patch fixing the alternatives path. I am waiting on a launchpad build to test this fully: https://launchpad.net/~system76/+archive/ubuntu/pop- staging/+build/13352379 ** Patch added: "ubuntu_gdm_alternatives.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+attachment/4946612/+files/ubuntu_gdm_alternatives.debdiff -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1716018] [NEW] nm-applet often disappears from panel at startup
Public bug reported: i am with ubuntu 16.04 desktop (64-bit) network-manager.service often doesn't start and nm-applet disappears from panel at startup ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Summary changed: - nm-applet offten disappears from panel at startup + nm-applet often disappears from panel at startup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716018 Title: nm-applet often disappears from panel at startup Status in alsa-driver package in Ubuntu: New Bug description: i am with ubuntu 16.04 desktop (64-bit) network-manager.service often doesn't start and nm-applet disappears from panel at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716018/+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 1714315] Re: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1704618 *** https://bugs.launchpad.net/bugs/1704618 ** Description changed: - I installed all update and upgrades for ubuntu 17.10 with gnome-shell - running, after I logged out and switched to tty2. After a reboot the - system logged out, just by itself. I rebooted, installed 'Hide Dash X', - because of a bug with 'Dash to Dock' which did not hide the standard - dash. After that, what I first wanted to do, I switched to gnome- - control-center to reenable automatic login for my account, because I - thought somehow there's the reason why the system logged out by itself. - After I unlocked the settings, the window was grayed out and crashed. - The bug report appeared. On the second try I could reenable it. It was - disabled. I reinstalled all x11, nvidia and noiveau packages via - synaptic that where shown as installed due the search option. I think it - is fixed now. + I switched to gnome-control-center to reenable automatic login for my + account, because I thought somehow there's the reason why the system + logged out by itself. After I unlocked the settings, the window was + grayed out and crashed. The bug report appeared. On the second try I + could reenable it. It was disabled. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 31 19:11:54 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-18 (43 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fe95ef49499:cmpq $0x0,0x58(%rax) - PC (0x7fe95ef49499) ok - source "$0x0" ok - destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7fe95ef49499:cmpq $0x0,0x58(%rax) + PC (0x7fe95ef49499) ok + source "$0x0" ok + destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 - ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 + ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to artful on 2017-08-13 (18 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1714315 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() Status in gnome-control-center package in Ubuntu: New Bug description: I switched to gnome-control-center to reenable automatic login for my account, because I thought somehow there's the reason why the system logged out by itself. After I unlocked the settings, the window was grayed out and crashed. The bug report appeared. On the second try I could reenable it. It was disabled. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 31 19:11:54 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-18 (43 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe95ef49499:cmpq $0x0,0x58(%rax) PC (0x7fe95ef49499) ok source "$0x0" ok destination "0x58(%rax)"
[Desktop-packages] [Bug 1715722] Re: Allow safe override of GDM3 theme
** Patch removed: "ubuntu_gdm_alternatives.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+attachment/4946604/+files/ubuntu_gdm_alternatives.debdiff -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25
See https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716011 for what actually turned out to be my issue. -- 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/1713323 Title: HiDPI support partially broken after upgrade to Gnome 3.25 Status in gnome-shell package in Ubuntu: Confirmed Bug description: After an upgrade this morning that took in the new version of this package, and a suite of gnome-session/gnome-settings packages, which may also be implicated, support for scaling on HiDPI screens seems to have partially failed. Partially. BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but when I got to the launchpad page it had pre-filled "gnome-session". One presumes there's a reason for that so I've left it, especially as this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a settings migrations utility in ubuntu-session which I wonder if it might be implicated. (TBH looking at it it's not obvious why, though it does reset scaling - that's not the problem, the problem is that it can't be set back to a combination that works.) Reminder all the stuff I'm reporting below as being wrongly-scaled was scaled correctly before the update that just took place. Enpass got a little help from having some QT env variables set, but that's it. Logging in under session "Ubuntu" (Wayland - on a different machine as this one being nvidia doesn't support it) or session "Ubuntu on Xorg" - also affects GNOME sessions: * The fonts in the top bar, and the menus and indicators accessible from there, are unscaled. The indicator icons *are* scaled correctly. * The fonts in the applications view are unscaled, but the icons and layout *are* scaled correctly. * Menu titlebar *text* is unscaled. close/minimize/maximize widgets *are* scaled correctly, as is the titlebar's size itself. * The mouse pointer is unscaled. * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud- client, hexchat, sublime text 3) are unscaled, or in some cases are a bit confused, with some elements correctly scaled, but again fonts are not. * Also on a personal note, Java 9 JavaFX apps are no longer scaled. (In Java 8 it was already broken; I was targeting Java 9 with my development partly *because* its HiDPI support was working in Linux.) FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2. ## What is working: * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus, Gedit etc. etc.) are all fine. Although note those that use a "normal" titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus) show small titlebar text as mentioned above * Google Chrome, Thunderbird, Firefox are fine (although the latter two aren't being updated for Artful yet, just sayin' ;-) ## What happens if I try to fix it: gsettings org.gnome.desktop.interface scaling-factor appears to no longer be operational. Changing its value from 0 (default), 1 and 2 appears to have no effect on anything any more. It used to be setting it to 2 fixed the few things that weren't right by having it set to 0... Correction, that *does* fix it for Java 9 JavaFX, it must be reading that setting directly. But nothing else reported as broken above is affected by changing this setting. Nor in fact does setting it to 1 cause gnome apps to be unscaled. gsettings org.gnome.desktop.interface cursor-size is working. I can set it to 48, double its normal size, to get back normal-sized cursors when the pointer is over newly-launched applications. But that's obviously a workaround. gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0, also exposed in Gnome Tweaks, unsurprisingly makes text twice as large. That "fixes" it for the applications that are reported as being unscaled above, but it also doubles the size of text in gnome apps as well, so those are now far too large for the windows they're in. Google Chrome is unaffected by this, as is Java 9 JavaFX, but Thunderbird *is* affected. I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but it seems to have a nonsense-value "@a{si} {}". I have no idea if this is anything in use or if it was an intended Unity 8 thing. I didn't try anything with it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.25.90-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 27 13:03:53 2017 InstallationDate: Installed on 2017-07-30 (27 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-session UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1716009] Re: problem with the sound since the latest update
** Package changed: firefox-3.0 (Ubuntu) => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716009 Title: problem with the sound since the latest update Status in alsa-driver package in Ubuntu: New Bug description: i am with an old intel chipset motherboard having an integrated realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the latest update there has had no effect when adjusting sound volume from the sound menu on the menu bar and sound settings, and no sound in counter strike 1.6 linux version, also, there has appeared an effect of a sound interruption/break (for less than a second) when switching between applications, however, i can still adjust the sound volume from gnome alsa mixer the latest update includes: snapd-login-service:amd64 libsnapd-glib1:amd64 linux-firmware:amd64 libgd3:amd64 the previous ——: libpackagekit-glib2-16:amd64 gir1.2-packagekitglib-1.0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716009/+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 1715722] Re: Allow safe override of GDM3 theme
As told on IRC, I doubt this patch was tested. There is no reference of ubuntu.css in the postinst, and so, the alternatives is basically referencing itself. In general, I'm really not a fan of that approach as told many times and would prefer an upstreamable solution. However, if anyone else wants to sponsor it, (after testing it) feel free. -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1716015] [NEW] Can't install software via Universe repository
Public bug reported: Even though I have Universe repository enabled, I get prompted to do so in Gnome Software and then get an error message when I choose to enable and put in root password. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 11:28:13 2017 InstallationDate: Installed on 2017-08-23 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2017-09-08 11-27-58.png" https://bugs.launchpad.net/bugs/1716015/+attachment/4946608/+files/Screenshot%20from%202017-09-08%2011-27-58.png -- 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/1716015 Title: Can't install software via Universe repository Status in gnome-software package in Ubuntu: New Bug description: Even though I have Universe repository enabled, I get prompted to do so in Gnome Software and then get an error message when I choose to enable and put in root password. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 11:28:13 2017 InstallationDate: Installed on 2017-08-23 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1716015/+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 1715722] Re: Allow safe override of GDM3 theme
didrocks, here is a debdiff for implementing the alternatives method. It did not require much code. Please let me know what you think! ** Patch added: "ubuntu_gdm_alternatives.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+attachment/4946604/+files/ubuntu_gdm_alternatives.debdiff -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1716009] [NEW] problem with the sound since the latest update
You have been subscribed to a public bug: i am with an old intel chipset motherboard having an integrated realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the latest update there has had no effect when adjusting sound volume from the sound menu on the menu bar and sound settings, and no sound in counter strike 1.6 linux version, also, there has appeared an effect of a sound interruption/break (for less than a second) when switching between applications, however, i can still adjust the sound volume from gnome alsa mixer the latest update includes: snapd-login-service:amd64 libsnapd-glib1:amd64 linux-firmware:amd64 libgd3:amd64 the previous ——: libpackagekit-glib2-16:amd64 gir1.2-packagekitglib-1.0:amd64 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- problem with the sound since the latest update https://bugs.launchpad.net/bugs/1716009 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- 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
Re: [Desktop-packages] [Bug 1715993] Re: At start-up, non dock icons are under the dock
*** This bug is a duplicate of bug 1696621 *** https://bugs.launchpad.net/bugs/1696621 Oups sorry Jeremy Gérard VAQUANT 2017-09-08 17:13 GMT+02:00 Jeremy Bicha: > *** This bug is a duplicate of bug 1696621 *** > https://bugs.launchpad.net/bugs/1696621 > > ** This bug has been marked a duplicate of bug 1696621 >Desktop icons slip under the top bar and dock > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1715993 > > Title: > At start-up, non dock icons are under the dock > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+ > bug/1715993/+subscriptions > -- 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/1715993 Title: At start-up, non dock icons are under the dock Status in gnome-shell package in Ubuntu: New Bug description: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715993/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Bug exists in 17.10 too. So it's time to switch to Ubuntu with MATE Desktop Environment. ** Tags added: artful zesty -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+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 1715722] Re: Allow safe override of GDM3 theme
Quoting from #ubuntu-devel on IRC: jackpot51 | didrocks: I am going to work on https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722 with the method I described first, having alternatives for a gdm.css file that is the stylesheet of GDM jackpot51 | It is critical to our Beta release that we have a reliable method of overriding the GDM theme, so the alternatives method seems to be the best way to go. We can talk about further improvement and upstreaming after 17.10 jackpot51: I think it will need a FFe though jackpot51 | In my mind, it isn't a feature jackpot51 | It is a bug fix for a bug affecting flavors of Ubuntu using GNOME didrocks | jackpot51: you meant "deratives" rather than flavors? I don't know of any existing 17.10 flavors using gdm? jackpot51 | Yes, that is what I mean - derivatives jackpot51 | If this becomes too complicated, we would have to fork the gnome-shell package to accomplish what we need to in Pop before 17.10 jackpot51 | So I would like to do this as simply and smartly as possible didrocks | jackpot51: I guess you just need to talk to the release team telling us you want to do a temporary override until we get a better upstreamable solution and see if they consider it's a FF breakage or not Laney | where does this pop.css come from? jackpot51 | Ok, that sounds good to me Laney | I think it'd be easier for you to dpkg-divert the ubuntu one away if this is a temporary solution for one derivative only -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1173648] Re: F3 side pane is gone in Nautilus 3.6+
** Tags added: artful -- 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/1173648 Title: F3 side pane is gone in Nautilus 3.6+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: the double pane functionality that exists in older Nautilus versions is gone in the 3.6 version. that is a huge usability issue. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1173648/+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 885592] Re: No "parent folder" button in Nautilus
** Tags added: artful 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/885592 Title: No "parent folder" button in Nautilus Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: After update to oneiric, I don't see any easy way (read: toolbar button) to navigate to the parent folder. There is a menu entry, and there are keyboard shortcuts, but neither gives an easy way to quickly navigate up in the directory tree with the mouse (in particular if you want to go up two or three levels). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Nov 3 09:49:25 2011 SourcePackage: nautilus UpgradeStatus: Upgraded to oneiric on 2011-10-17 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/885592/+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 1448511] Re: Unable to set gnome-terminal title from menu in 15.04, 15.10, 16.04 LTS, 16.10, 17.04, 17.10
** Summary changed: - Unable to set gnome-terminal title from menu in 15.04, 15.10, 16.04 LTS, 16.10 + Unable to set gnome-terminal title from menu in 15.04, 15.10, 16.04 LTS, 16.10, 17.04, 17.10 ** Tags added: artful zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1448511 Title: Unable to set gnome-terminal title from menu in 15.04, 15.10, 16.04 LTS, 16.10, 17.04, 17.10 Status in GNOME Terminal: Invalid Status in gnome-terminal package in Ubuntu: Won't Fix Bug description: In Ubuntu Precise Pangolin 12.04 was an option "Terminal -> Set Title" for setting terminal title. In Ubuntu Vivid Vervet 15.04 it is missed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Apr 25 21:04:46 2015 InstallationDate: Installed on 2015-04-25 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1448511/+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 1715722] Re: Allow safe override of GDM3 theme
It is critical to our Beta release that we have a reliable method of overriding the GDM theme, so the alternatives method seems to be the best way to go. We can talk about further improvement and upstreaming after 17.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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1715722] Re: Allow safe override of GDM3 theme
didrocks, I am going to do what I described above as it is a clean and quick method to having both of our systems ready for a 17.10 Beta release. Is that ok? ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Jeremy Soller (jackpot51) -- 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/1715722 Title: Allow safe override of GDM3 theme Status in gnome-shell package in Ubuntu: New Bug description: Currently, in artful, GDM3's theme is hardcoded to be /usr/share /gnome-shell/theme/ubuntu.css In the Ubuntu default session, this is the same CSS file as the gnome- shell mode in /usr/share/gnome-shell/modes/ubuntu.json However, in other flavors, it makes sense to install another mode json and theme css file with a clear name. Take, for instance, pop-session, that installs /usr/share/gnome-shell/theme/pop.css and /usr/share /gnome-shell/modes/pop.json In order to supply a custom GDM3 theme, which is currently hardcoded, the ubuntu.css file must be replaced with this pop.css file. This breaks ubuntu-session, causing it to have a different shell theme than expected. What would be desirable is for the GDM3 CSS file to be hardcoded to gdm.css, which would be a symlink to the correct stylesheet for the flavor. This would allow multiple GNOME Shell sessions to be installed at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+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 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)
Does this bug related to this? bug #1697882 Because I disabled 95_hide_x11_sessions_with_nvidia_kms.patch and everything started working well. On non-nvidia machine, non-hybrid machine, when I try live iso, a) Ubuntu logs into wayland b) Ubuntu-on-xorg logs into xorg as expected. I don't like the check that patch implements. It manually checks for modules in "/proc/modules" is_module_loaded (const char *module) { . . const char*modules_file = "/proc/modules"; file = fopen (modules_file, "r"); if (!file) { g_debug ("Failed to parse %s\n", modules_file); return status; } And my guess is for some reason it fails to detect intel for hybrid machine at /* Let's leave hybrid graphics alone */ if (is_module_loaded ("i915")) { g_debug ("is_nvidia_kms_available: Intel detected, doing nothing.\n"); goto end; } But then it could be just me. Does disabling the above patch solve the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1705157 Title: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg) Status in gnome-session: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Test case: Do a fresh install of current image (july 19 here Boot up, check selected session at the greeter - it will say "ubuntu" Log in, ck. env., it will actually be ubuntu-wayland Ex. $ env | grep -i wayland DESKTOP_SESSION=ubuntu-wayland WAYLAND_DISPLAY=wayland-0 XDG_SESSION_TYPE=wayland XDG_SESSION_DESKTOP=ubuntu-wayland GDMSESSION=ubuntu-wayland Test 2: From above log out, switch session in greeter to wayland on ubuntu,, switch back to ubuntu, login. Now you'll be in an ubuntu session Test 3: log out from above ubuntu session, log into ubuntu-wayland session, reboot. At greeter notice it says "ubuntu" selected. Login, ck. session. You'll actually be in an ubuntu-wayland session ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 21:48:10 2017 InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1705157/+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 1715993] Re: At start-up, non dock icons are under the dock
*** This bug is a duplicate of bug 1696621 *** https://bugs.launchpad.net/bugs/1696621 ** This bug has been marked a duplicate of bug 1696621 Desktop icons slip under the top bar and dock -- 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/1715993 Title: At start-up, non dock icons are under the dock Status in gnome-shell package in Ubuntu: New Bug description: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715993/+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 1715993] [NEW] At start-up, non dock icons are under the dock
*** This bug is a duplicate of bug 1696621 *** https://bugs.launchpad.net/bugs/1696621 Public bug reported: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Package changed: usb-creator (Ubuntu) => gnome-shell (Ubuntu) -- 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/1715993 Title: At start-up, non dock icons are under the dock Status in gnome-shell package in Ubuntu: New Bug description: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715993/+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 1673984] Re: Can not add google account any more (Zesty)
Having this same issue with 16.04 xenial. signon-ui is at version 0.17+16.04.20151125-0ubuntu1 but apt-get tells me I'm as up to date as I can be for this LTS. Does this fix need pushing to 16.04 also? (unity-control-center:5967): account-plugin-CRITICAL **: Couldn't store identity: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.InternalServer: Server internal error occurred.Could not access Signon Database. (unity-control-center:5967): credentials-cc-panel-CRITICAL **: cc- credentials-authorization-page.vala:182: Error completing auth session process: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.InternalServer: Server internal error occurred.Could not access Signon Database -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) Status in Canonical System Image: New Status in signon-ui package in Ubuntu: Fix Released Bug description: After updating Unity-Control-Center to 15.04.0+17.04.20170314-0ubuntu2 and liboxidecore to 1.20.4-0ubuntu1 on Zesty I could not able to add to add Google account. ### How to reproduce: 1. Go online account try adding google account. 2. Infobar will appear for a moment and the it will disappear. Screenshot: https://i.imgur.com/evDPZSv.png 3. The login page doesn't load at all. Running online-accounts-preferences from terminal gives: -- (unity-control-center:7866): credentials-cc-panel-CRITICAL **: cc-credentials-authorization-page.vala:182: Error completing auth session process: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 2 -- Installed Packages (Ubuntu 17.04 32 bit): account-plugin-google: 0.13+17.04.20161206-0ubuntu1 signon-ui-x11: 0.17+17.04.20161109-0ubuntu1 unity-control-center: 15.04.0+17.04.20170314-0ubuntu2 unity-control-center-signon: 0.1.9+16.10.20160825-0ubuntu1 All other packages are up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673984/+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 1715948] Re: Cannot add new user in new Gnome Settings
The old "shell" for gnome-control-center is still installed for now. So as a workaround, you can run gnome-control-center-alt Only one gnome-control-center can run at a time so make sure you close one before trying to run the other. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1715948 Title: Cannot add new user in new Gnome Settings Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Got the update for the new Gnome Settings, and I am not able to add new users. Details -> Users shows the current users on the system, click on Unlock prompts for administrator/root password, once password is entered successfully Gnome Settings disappears. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 09:49:53 2017 InstallationDate: Installed on 2017-08-23 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715948/+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 1715993] Re: At start-up, non dock icons are under the dock
*** This bug is a duplicate of bug 1696621 *** https://bugs.launchpad.net/bugs/1696621 ** Attachment added: "as it shoud be from start" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715993/+attachment/4946594/+files/1.png -- 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/1715993 Title: At start-up, non dock icons are under the dock Status in gnome-shell package in Ubuntu: New Bug description: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715993/+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 1715989] Re: right click on dock screen shot icon is not working properly
** Attachment added: "left click the 3 choices work" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1715989/+attachment/4946587/+files/2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1715989 Title: right click on dock screen shot icon is not working properly Status in gnome-screenshot package in Ubuntu: New Bug description: Right click (see attachment 1) is fine for 1st and 2nd choice, but not for the 3rd one: Take a screenshot of a selected area Actually the shape of the mouse pointer is still the same instead of changing into a cross to select the desired area. It works when we click on the icon and then select 3rd choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1715989/+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 1715993] [NEW] At start-up, non dock icons are under the dock
You have been subscribed to a public bug: One way to get the icons not under the dock is to click on any icon of the dock. They switch automatically from under the dock to next to the dock, as it should be without doing any action. Just like on attachment 1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- At start-up, non dock icons are under the dock https://bugs.launchpad.net/bugs/1715993 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1715989] [NEW] right click on dock screen shot icon is not working properly
Public bug reported: Right click (see attachment 1) is fine for 1st and 2nd choice, but not for the 3rd one: Take a screenshot of a selected area Actually the shape of the mouse pointer is still the same instead of changing into a cross to select the desired area. It works when we click on the icon and then select 3rd choice ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Attachment added: "right click on the icon" https://bugs.launchpad.net/bugs/1715989/+attachment/4946586/+files/1.png ** Package changed: usb-creator (Ubuntu) => gnome-screenshot (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1715989 Title: right click on dock screen shot icon is not working properly Status in gnome-screenshot package in Ubuntu: New Bug description: Right click (see attachment 1) is fine for 1st and 2nd choice, but not for the 3rd one: Take a screenshot of a selected area Actually the shape of the mouse pointer is still the same instead of changing into a cross to select the desired area. It works when we click on the icon and then select 3rd choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1715989/+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 1715989] [NEW] right click on dock screen shot icon is not working properly
You have been subscribed to a public bug: Right click (see attachment 1) is fine for 1st and 2nd choice, but not for the 3rd one: Take a screenshot of a selected area Actually the shape of the mouse pointer is still the same instead of changing into a cross to select the desired area. It works when we click on the icon and then select 3rd choice ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- right click on dock screen shot icon is not working properly https://bugs.launchpad.net/bugs/1715989 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. -- 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 1715948] [NEW] Cannot add new user in new Gnome Settings
Public bug reported: Got the update for the new Gnome Settings, and I am not able to add new users. Details -> Users shows the current users on the system, click on Unlock prompts for administrator/root password, once password is entered successfully Gnome Settings disappears. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 09:49:53 2017 InstallationDate: Installed on 2017-08-23 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1715948 Title: Cannot add new user in new Gnome Settings Status in gnome-control-center package in Ubuntu: New Bug description: Got the update for the new Gnome Settings, and I am not able to add new users. Details -> Users shows the current users on the system, click on Unlock prompts for administrator/root password, once password is entered successfully Gnome Settings disappears. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 09:49:53 2017 InstallationDate: Installed on 2017-08-23 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715948/+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 1715931] Re: Update to eviv2 version 0.26
** Summary changed: - Update to evi2 version 0.26 + Update to eviv2 version 0.26 ** Summary changed: - Update to eviv2 version 0.26 + Update to exiv2 version 0.26 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: New Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1715940] [NEW] Libre Office: central clic not working
Public bug reported: Unlike Firefox, gedit, terminal, ... LibreOffice does not react on central clic for copy and paste ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Package changed: usb-creator (Ubuntu) => libreoffice (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1715940 Title: Libre Office: central clic not working Status in libreoffice package in Ubuntu: New Bug description: Unlike Firefox, gedit, terminal, ... LibreOffice does not react on central clic for copy and paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1715940/+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 1715940] [NEW] Libre Office: central clic not working
You have been subscribed to a public bug: Unlike Firefox, gedit, terminal, ... LibreOffice does not react on central clic for copy and paste ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- Libre Office: central clic not working https://bugs.launchpad.net/bugs/1715940 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. -- 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 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()
** Information type changed from Private to Public ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => High -- 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/1704618 Title: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: sijui maelezo zaidi ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 16 10:09:12 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-06-26 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7ff4ea6fe6e9:cmpq $0x0,0x58(%rax) PC (0x7ff4ea6fe6e9) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() 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/gnome-control-center/+bug/1704618/+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 1715931] [NEW] Update to evi2 version 0.26
Public bug reported: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to evi2 version 0.26 Status in exiv2 package in Ubuntu: New Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1715891] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1704618 *** https://bugs.launchpad.net/bugs/1704618 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1704618, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1715891/+attachment/4946557/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946559/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946562/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946563/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946564/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946565/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1715891/+attachment/4946566/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1704618 ** Tags removed: need-amd64-retrace -- 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/1715891 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Crashed when I unlocked the users panel. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:49:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1465 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f77b3239499:cmpq $0x0,0x58(%rax) PC (0x7f77b3239499) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715891/+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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
> The problem persists if you upgrade from 16.04.3 directly to 17.04 ( as described https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1658921/comments/23 ) I can confirm this. My upgrade path was xenial -> zesty -> artful and I had to run "touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf" so network-manager could handle my enp2s0 device. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Status in network-manager source package in Yakkety: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed before rebooting you should have a network connection after you reboot. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install netplan, configure to set up static network on an ethernet device using netplan. 4) Upgrade to yakkety 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1715891] [NEW] gnome-control-center crashed with SIGSEGV
Public bug reported: Crashed when I unlocked the users panel. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:49:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1465 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f77b3239499: cmpq $0x0,0x58(%rax) PC (0x7f77b3239499) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace ** Information type changed from Private to Public -- 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/1715891 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Crashed when I unlocked the users panel. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:49:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-09-03 (1465 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f77b3239499:cmpq $0x0,0x58(%rax) PC (0x7f77b3239499) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715891/+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 1715883] Re: Can not drag and drop from network shares to most apps
Nautilus migrated to gitlab.gnome.org. The patch for this bug is at https://gitlab.gnome.org/GNOME/nautilus/merge_requests/2 ** Bug watch added: Xfce Bugzilla #13845 https://bugzilla.xfce.org/show_bug.cgi?id=13845 ** Also affects: thunar via https://bugzilla.xfce.org/show_bug.cgi?id=13845 Importance: Unknown Status: Unknown -- 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/1715883 Title: Can not drag and drop from network shares to most apps Status in Nautilus: New Status in thunar: Unknown Status in nautilus package in Ubuntu: New Bug description: Dropping a file from a network share into most applications (Claws Mail, Chromium, Thunderbird, ...) fails silently. This is because the URIs sent by Nautilus are GFVS URIs with various schemes (smb://, davs://, ...) and most applications doing POSIX I/O can't do anything with them. This is easy to check by dropping a file from a network share into the Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1715883/+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 1715883] Re: Can not drag and drop from network shares to most apps
Thunar suffers from the same bug. -- 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/1715883 Title: Can not drag and drop from network shares to most apps Status in Nautilus: New Status in thunar: Unknown Status in nautilus package in Ubuntu: New Bug description: Dropping a file from a network share into most applications (Claws Mail, Chromium, Thunderbird, ...) fails silently. This is because the URIs sent by Nautilus are GFVS URIs with various schemes (smb://, davs://, ...) and most applications doing POSIX I/O can't do anything with them. This is easy to check by dropping a file from a network share into the Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1715883/+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 1715883] [NEW] Can not drag and drop from network shares to most apps
Public bug reported: Dropping a file from a network share into most applications (Claws Mail, Chromium, Thunderbird, ...) fails silently. This is because the URIs sent by Nautilus are GFVS URIs with various schemes (smb://, davs://, ...) and most applications doing POSIX I/O can't do anything with them. This is easy to check by dropping a file from a network share into the Terminal. ** Affects: nautilus Importance: Undecided Status: New ** Affects: thunar Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus Importance: Undecided Status: 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/1715883 Title: Can not drag and drop from network shares to most apps Status in Nautilus: New Status in thunar: Unknown Status in nautilus package in Ubuntu: New Bug description: Dropping a file from a network share into most applications (Claws Mail, Chromium, Thunderbird, ...) fails silently. This is because the URIs sent by Nautilus are GFVS URIs with various schemes (smb://, davs://, ...) and most applications doing POSIX I/O can't do anything with them. This is easy to check by dropping a file from a network share into the Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1715883/+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 1711178] Re: Gnome Software consumes way too much CPU resources at times
I've hit this a few times and was never ever to find anything useful. However, this time I think I know what triggered the load. I manually installed d-feet with apt, and within a couple minutes removed it with apt. My laptop load spiked and stayed that way until I killed the process over 2 hours later. While debugging it, the only thing that stood out was this log message: Sep 7 15:02:22 mucho gnome-software[5113]: failed to rescan: Failed to parse /usr/share/applications/d-feet.desktop file: cannot process file of type application/x-desktop I heard the fan spin up less than a minute after I removed d-feet. Maybe something was queued to scan that desktop file and it was gone by the time it was ready to scan it? I briefly used strace on the process and it just looked like a bunch of waits, nothing that looked interesting. I left it in this state for over 2 hours to see if it would ever recover, but it didn't and I ultimately killed the gnome- software process. -- 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/1711178 Title: Gnome Software consumes way too much CPU resources at times Status in gnome-software package in Ubuntu: Confirmed Bug description: I've noticed my Kaby Lake i7 laptop with 16GB RAM become extremely slow at time even when not performing any CPU intensive tasks. I've tried to find out the culprit process and it turned out to be Gnome Software. It was consuming 99% of CPU. I remember having clicking "update all" in Gnome Software some time ago and also "check for updates" in control center's details section some time after that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1711178/+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 1715869] [NEW] It should say 'Position on screen' not 'Screen position'
Public bug reported: In the new Dock panel, there is an option that says 'Screen position'. The wording is not intuitive; it should say 'Position on screen'. See the attached screenshot from Didier Roche. Screen position: the position of the screen itself (is it really?!) Position on screen: the dock position on the screen (left, bottom, etc.) gnome-control-center 1:3.25.92.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dock_settings_finale.png" https://bugs.launchpad.net/bugs/1715869/+attachment/4946538/+files/dock_settings_finale.png -- 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/1715869 Title: It should say 'Position on screen' not 'Screen position' Status in gnome-control-center package in Ubuntu: New Bug description: In the new Dock panel, there is an option that says 'Screen position'. The wording is not intuitive; it should say 'Position on screen'. See the attached screenshot from Didier Roche. Screen position: the position of the screen itself (is it really?!) Position on screen: the dock position on the screen (left, bottom, etc.) gnome-control-center 1:3.25.92.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715869/+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 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04
Same issue happens on my Thinkpad x1 carbon 5th laptop. I just installed Ubuntu 16.04.3 alongside with Windows 10. fwupd randomly consumes 100% of the CPU but I didn't find any special err in my syslog. It just happened randomly without a signal (usually a short after booting), and I don't know how to reproduce it. This problem can draining my laptop battery, therefore I have to disable fwupd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1707110 Title: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04 Status in appstream-glib package in Ubuntu: Confirmed Bug description: Even though this bug is reported [https://bugs.launchpad.net/ubuntu/+source/appstream- glib/+bug/1591868] and marked as fixed, I am having the same issue on a up to date Ubuntu 16.04 system (as you can see in the attachment). Rebooting doesn't fix the problem. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+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 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players
Because have 2 ways for listing keys: 1) native (as VLC). Application get keycodes self. It always work fine. 2) over dbus observer from gnome/unity/etc-settings-daemon. unity/gnome-settings-daemon have been rewritten. Now they listen only first XF86AudioPlay key. Bluetooth key not work if keyboard (or other early connected device) have this key. mate-settings-daemon have legacy code from gnome2, but work fine too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Bluetooth headset play/pause key not fully effective in various media players Status in GNOME Shell: New Status in Unity: Invalid Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: UPDATE: Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal "AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its XF86AudioPlay). Can be reproduce: run in one terminal 'dbus-monitor "path=/org/gnome/Shell"' and in other run 'xdotool key NUMBER' where NUMBER - keycodes. Can be check 172, 172, 209, bugged 208 and 215 and other. - I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings-daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run "evtest /dev/input/event9", then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run "xev" and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1397142/+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 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players
For my case, with Bose QC35 bluetooth headphones, skip forward and backward worked with no configuration, but play/pause didn't at all. The workaround I found was to use xbindkeys with the help of xbindkeys- config to set the following: "xdotool key XF86AudioPlay" c:208 in my ~/.xbindkeysrc. This is strange, as pretty much everything else sees the button as XF86AudioPlay, but it wasn't being seen as a media key by the player. But it works now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Bluetooth headset play/pause key not fully effective in various media players Status in GNOME Shell: New Status in Unity: Invalid Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: UPDATE: Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal "AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its XF86AudioPlay). Can be reproduce: run in one terminal 'dbus-monitor "path=/org/gnome/Shell"' and in other run 'xdotool key NUMBER' where NUMBER - keycodes. Can be check 172, 172, 209, bugged 208 and 215 and other. - I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings-daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run "evtest /dev/input/event9", then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run "xev" and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1397142/+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 1715857] Re: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1715857 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127 Status in pygobject-2 package in Ubuntu: New Bug description: package python-gobject-2 2.28.6-12build1 failed to install ProblemType: Package DistroRelease: Ubuntu 15.10 Package: python-gobject-2 2.28.6-12build1 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Sep 8 19:38:39 2017 DuplicateSignature: package:python-gobject-2:2.28.6-12build1:子进程 已安装 post-installation 脚本 返回错误状态 127 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 127 InstallationDate: Installed on 2016-11-17 (295 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1715857/+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 1715662] Re: Network Connectivity Checking does not turn gray when toggle is set to Off
I know why this happens, and I posted it as a review on the upstream bug (#737362) @@ +1300,3 @@ +{ + nm_client_connectivity_check_set_enabled (client, state); + return TRUE; You should return FALSE here, so the default signal handler runs. This is the cause of https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1715662 -- 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/1715662 Title: Network Connectivity Checking does not turn gray when toggle is set to Off Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The background Network Connectivity Checking does not turn gray when the toggle is set to Off. Still has orange background. See attached image. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 09:42:59 2017 InstallationDate: Installed on 2017-08-23 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715662/+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 1715857] [NEW] package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127
Public bug reported: package python-gobject-2 2.28.6-12build1 failed to install ProblemType: Package DistroRelease: Ubuntu 15.10 Package: python-gobject-2 2.28.6-12build1 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Sep 8 19:38:39 2017 DuplicateSignature: package:python-gobject-2:2.28.6-12build1:子进程 已安装 post-installation 脚本 返回错误状态 127 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 127 InstallationDate: Installed on 2016-11-17 (295 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject-2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1715857 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127 Status in pygobject-2 package in Ubuntu: New Bug description: package python-gobject-2 2.28.6-12build1 failed to install ProblemType: Package DistroRelease: Ubuntu 15.10 Package: python-gobject-2 2.28.6-12build1 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Sep 8 19:38:39 2017 DuplicateSignature: package:python-gobject-2:2.28.6-12build1:子进程 已安装 post-installation 脚本 返回错误状态 127 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 127 InstallationDate: Installed on 2016-11-17 (295 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1715857/+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 1693291] Re: Tweak tool When Power Button Pressed interact option missing
This is fixed in Ubuntu 17.10 Beta now. https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1693291 Title: Tweak tool When Power Button Pressed interact option missing Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-tweak-tool package in Ubuntu: Invalid Bug description: Tweak tool Power proposes: When Power Button is Pressed: Hibernate-Nothing-Suspend ... but Interactive option is missing When Laptop Lid is Closed: ... Hibernate-Interactive-Logout-Nothing ... How can I Interact When Laptop Lid is Closed? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-tweak-tool 3.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 18:15:17 2017 ExecutablePath: /usr/bin/gnome-tweak-tool InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all SourcePackage: gnome-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1693291/+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 1681523] Re: [Launcher] missing right click options
@sbierman & @md-5 I'm not sure of the relationship between the two files, but in addition to `/usr/share/applications/gnome-terminal.desktop` you may also need to change `/usr/share/applications/org.gnome.Terminal.desktop` similarly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1681523 Title: [Launcher] missing right click options Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running : Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Not sure where to postthis but... Just noticed that "Right Click" options for the "Terminal" App are missing when it's locked to the 'Launcher' side-bar. You used to get the option to open "Open a New Window" or "Open a New Tab" when you right clicked on the launcher icon. Now the only options are "Terminal", "Unlock from Launcher" and "Quit". ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity 7.5.0+17.04.20170407.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 378.13 Tue Feb 7 20:10:06 PST 2017 GCC version: gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 10 18:44:46 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] [19da:7326] InstallationDate: Installed on 2017-03-04 (36 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Mon Apr 10 18:43:48 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1715854] [NEW] Adding local mail server not possible
Public bug reported: In Settings / Online Accounts trying to connect a local SMTP/IMAP account fails. Trying to add the IMAP works (one has to ignore the warning about self signed certificate). SMTP does not get added (gnome-control-center-alt:6192): GoaBackend-WARNING **: g_socket_client_connect_to_host() failed: Could not connect to smtp.rsb.intern: Connection refused (g-io-error-quark, 39) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 12:57:37 2017 InstallationDate: Installed on 2017-09-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1715854 Title: Adding local mail server not possible Status in gnome-control-center package in Ubuntu: New Bug description: In Settings / Online Accounts trying to connect a local SMTP/IMAP account fails. Trying to add the IMAP works (one has to ignore the warning about self signed certificate). SMTP does not get added (gnome-control-center-alt:6192): GoaBackend-WARNING **: g_socket_client_connect_to_host() failed: Could not connect to smtp.rsb.intern: Connection refused (g-io-error-quark, 39) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 12:57:37 2017 InstallationDate: Installed on 2017-09-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715854/+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 1711792] Re: Replace the word 'Launcher' with 'Dock' in Dock settings
And see the final screenshot at https://didrocks.fr/2017/09/08/ubuntu-gnome-shell-in-artful-day-10/ -- 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/1711792 Title: Replace the word 'Launcher' with 'Dock' in Dock settings Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I suggest to replace the word 'Launcher' with 'Dock' in the Dock settings section. Launcher was for Unity7. Dock is for GNOME Shell. See the screenshot from Didier Roche. 1:3.24.3-0ubuntu4 in Artful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1711792/+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 1711792] Re: Replace the word 'Launcher' with 'Dock' in Dock settings
Fixed now: https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 See also Matthew's comments at https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1711791/comments/3 ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- 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/1711792 Title: Replace the word 'Launcher' with 'Dock' in Dock settings Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I suggest to replace the word 'Launcher' with 'Dock' in the Dock settings section. Launcher was for Unity7. Dock is for GNOME Shell. See the screenshot from Didier Roche. 1:3.24.3-0ubuntu4 in Artful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1711792/+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 1709667] Re: Missing desktop scaling slider in system settings
Please check whether this is fixed for you with the latest gnome- control-center in Ubuntu 17.10 Beta. It has a different layout than previous versions. https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- 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/1709667 Title: Missing desktop scaling slider in system settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager) ... there is no longer the ability to configure the HiDPI scaling within the window manager. This may be an intentional regression or simply something that got passed by. But I find this configuration option to be very useful when working on a Lenovo P70 w/ 17" 4k monitor (which neds 2x DPI scaling) and also when switching back to my multiple-monitor configuration (which doesn't need any scaling). This is a piece of functionality I use on a regular basis that is now lost. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Aug 9 09:24:28 2017 DistUpgraded: 2017-08-07 09:44:27,630 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (1 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 7 08:59:11 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1709667/+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 1711791] Re: Remove the word 'Ubuntu' from 'Ubuntu Dock settings'
Fixed now: https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 Updated screenshot is the final screenshot at https://didrocks.fr/2017/09/08/ubuntu-gnome-shell-in-artful-day-10/ ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- 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/1711791 Title: Remove the word 'Ubuntu' from 'Ubuntu Dock settings' Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I suggest removing the word 'Ubuntu' from 'Ubuntu Dock settings'. Just say 'Dock Settings'. It is meaningful enough. See the screenshot from Didier Roche. 1:3.24.3-0ubuntu4 in Artful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1711791/+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 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
I believe this is fixed in Ubuntu 17.10 Beta now. Please install all updates. https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Since last night's updates, I can no longer change screen resolution or monitor alignment in gnome-control-center anymore (in gnome-shell running under Wayland). gnome-control-center fails silently in the GUI but reports this from the command line: (gnome-control-center:5887): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig All the available display modes are listed in gnome-control-center (you just can't select them). On the initial login, xrandr only showed two screen resolutions, one for screen XWAYLAND0 of 3840x2160 and another for XWAYLAND1 of 1920x1080, but after unplugging the external monitor and re-plugging it, now xrandr shows eDP-1 with all available modes and HDMI-1 with all available modes (you just can't select them from g-c-c). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 Uname: Linux 4.13.0-041300rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 11:47:50 2017 InstallationDate: Installed on 2017-08-16 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-08-17 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+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 841046] Re: Unity & GNOME3 misses an option to change the mouse pointer size & color
Fixed in Ubuntu 17.10 Beta now https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/841046 Title: Unity & GNOME3 misses an option to change the mouse pointer size & color Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in Baltix: Triaged Bug description: In the previous Ubuntu versions, it was possible to choose a mouse pointer to use with a theme. It also allowed you to set the mouse pointer size. I can no longer find this option in Ubuntu 11.10 (development branch). Version of gnome-control-center: 1:3.1.90-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/841046/+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 1715117] Re: Cannot launch wifi settings from wifi indicator "Settings panel for desktop file gnome-wifi-panel.desktop could not be loaded!"
Fixed in Ubuntu 17.10 Beta now https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.25.92.1-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1715117 Title: Cannot launch wifi settings from wifi indicator "Settings panel for desktop file gnome-wifi-panel.desktop could not be loaded!" Status in gnome-control-center package in Ubuntu: Fix Released Bug description: On latest artful desktop the wifi settings panel cannot be launched and the following error is logged in the journal Settings panel for desktop file gnome-wifi-panel.desktop could not be loaded! This panel is available in a newer version of gnome-control-center https://git.gnome.org/browse/gnome-control-center/commit/?id=016efdfac8e06a6c223e8dd8ede990bb2d49b8bd ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 12:06:41 2017 InstallationDate: Installed on 2013-09-03 (1462 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715117/+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 1715844] gvfsd-smb-browse crashed with signal 7
StacktraceTop: ?? () ?? () ?? () ?? () ?? () -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1715844] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1715844/+attachment/4946448/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1715844] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1715844/+attachment/4946449/+files/ThreadStacktrace.txt ** Changed in: gvfs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1715844] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for debianutils no debug symbol package found for perl-base no debug symbol package found for debianutils no debug symbol package found for perl-base Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1715844/+attachment/4946437/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1715844] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1715844/+attachment/4946447/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1715844] [NEW] gvfsd-smb-browse crashed with signal 7
Public bug reported: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: gvfs (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1715844 Title: gvfsd-smb-browse crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: It crashed while I was downloading a *.iso file from epiphany-browser. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 8 12:17:33 2017 Disassembly: => 0x7f287e0fafb6: Cannot access memory at address 0x7f287e0fafb6 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2017-06-21 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/3 Signal: 7 SourcePackage: gvfs StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gvfsd-smb-browse crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1715844/+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 1328692] Re: Cannot Change Password for Active Directory Users
Seems to work only on local accounts; http://bazaar.launchpad.net /~unity-control-center-team/unity-control-center/trunk/view/head:/panels /user-accounts/um-user-panel.c#L684 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1328692 Title: Cannot Change Password for Active Directory Users Status in unity-control-center package in Ubuntu: Confirmed Bug description: It seems that Active Directory users cannot change their password from the User Accounts module in the control center. When you look at their account, the 5 dots next to Password are greyed out, and you cannot click on them. For local users, the dots are black and you can change the password normally by clicking them. From a terminal, using passwd does work fine for Active Directory users. I am using Ubuntu 14.04, and sssd (1.11.5-1ubuntu3) Is this a bug, or is there maybe some sort of config that hides this option for remotely authenticated users? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1328692/+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 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)
PS1='${debian_chroot:+($debian_chroot)}\[\033[38;5;208;48m\]\u@\h\[\033[38;5;7;48m\]:\[\033[38;5;129;48m\]\w\[\033[38;5;202;48m\]\$\[\033[00m\] ' -- 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/1690966 Title: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights) Status in gnome-shell package in Ubuntu: Fix Released Bug description: In artful, Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690966/+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 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)
I propose to themed PS1 on Gnome Terminal (see attachment) ** Attachment added: "Capture du 2017-09-08 11-02-24.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690966/+attachment/4946400/+files/Capture%20du%202017-09-08%2011-02-24.png -- 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/1690966 Title: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights) Status in gnome-shell package in Ubuntu: Fix Released Bug description: In artful, Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690966/+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 1021375] Re: Nautilus says the USB stick is read only when it is not
Still present in 17.10 -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Bug description: First time I use an USB drive since I updated to 12.04 and I found a really annoying bug on Nautilus. Nautilus claims that the destination drive is read-only when in fact it is not. How to reproduce: 1. Connect a USB stick drive to your competer. 2. The USB will appear in the desktop. 3. Open two Nautilus windows one in your home folder, other in the USB stick drive. 4. Select any file from your home folder (small enough to fit the free space in the USB drive) 5. Drag the file and drop it in the USB drive window. -- Nautilus will say that it cannot copy the file because the destination is read ony -- If you try the copy the same file with the terminal you will see that the file is copied without problem, other programs like gedit or LibreOffice can write in the usb stick drive just fine. It is not a problem with the USB stick, as shown here: [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd [ 6232.426378] scsi8 : usb-storage 2-1:1.0 [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP PQ: 0 ANSI: 0 CCS [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.210138] sdb: sdb1 [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk The permisions on the removable drive are set correctly: sergio@shana:/media$ ls -lah total 12K drwxr-xr-x 3 root root 4,0K jul 5 10:20 . drwxr-xr-x 23 root root 4,0K jul 3 11:01 .. drwx-- 5 sergio sergio 4,0K dic 31 1969 DESIGNPLUS There is enough free space in the drive: sergio@shana:/media/DESIGNPLUS$ df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 50G 5,5G 42G 12% / udev 1,5G 4,0K 1,5G 1% /dev tmpfs579M 872K 579M 1% /run none 5,0M 0 5,0M 0% /run/lock none 1,5G 1,1M 1,5G 1% /run/shm /dev/sda1497M 113M 360M 24% /boot /dev/sda5245G 111G 122G 48% /home /dev/sdb11,9G 681M 1,2G 36% /media/DESIGNPLUS A file can be copied to the USB stick using the cp command for example. sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS sergio@shana:~/Trash$ cd /media/DESIGNPLUS sergio@shana:/media/DESIGNPLUS$ ls -lah total 204K drwx-- 5 sergio sergio 4,0K jul 5 10:38 . drwxr-xr-x 3 root root 4,0K jul 5 10:20 .. -rw-r--r-- 1 sergio sergio 117K jul 5 10:14 ._Screen Shot 2012-06-30 at 8.50.37 AM.png -rw-r--r-- 1 sergio sergio 55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 AM.png drwx-- 4 sergio sergio 4,0K jul 5 10:05 .Spotlight-V100 drwx-- 2 sergio sergio 4,0K jul 5 10:05 .Trashes -rw-r--r-- 1 sergio sergio 4,0K jul 5 10:05 ._.Trashes -rw-r--r-- 1 sergio sergio 73 jul 5 10:38 wireless.txt But nautilus just dennies to copy the file claming that the destination is read only, when it is not. I tested it with two different USB sticks in two different computers running Ubuntu 12.04 and the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1328692] Re: Cannot Change Password for Active Directory Users
This problem still exists in Xenial. The password cann't be altered though the GUI as the passwordbox with dots stays greyed out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1328692 Title: Cannot Change Password for Active Directory Users Status in unity-control-center package in Ubuntu: Confirmed Bug description: It seems that Active Directory users cannot change their password from the User Accounts module in the control center. When you look at their account, the 5 dots next to Password are greyed out, and you cannot click on them. For local users, the dots are black and you can change the password normally by clicking them. From a terminal, using passwd does work fine for Active Directory users. I am using Ubuntu 14.04, and sssd (1.11.5-1ubuntu3) Is this a bug, or is there maybe some sort of config that hides this option for remotely authenticated users? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1328692/+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 1713981] Re: Xwayland segfaults when using kvm (since 2:1.19.3-1ubuntu4)
This bug was fixed in the package xorg-server - 2:1.19.3-1ubuntu6 --- xorg-server (2:1.19.3-1ubuntu6) artful; urgency=medium * xwayland-add-grab-protocol-support.diff: Dropped, causes issues with kvm. (LP: #1713981) -- Timo AaltonenWed, 30 Aug 2017 14:42:05 +0300 ** Changed in: xorg-server (Ubuntu) Status: Fix Committed => Fix Released -- 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/1713981 Title: Xwayland segfaults when using kvm (since 2:1.19.3-1ubuntu4) Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: Using GNOME/wayland in artful, I get that Xwayland/shell segfault when using kvm Thread 1 "Xwayland" received signal SIGSEGV, Segmentation fault. 0x0092f4790b6e in zwp_pointer_constraints_v1_lock_pointer (lifetime=2, region=0x0, pointer=, surface=, zwp_pointer_constraints_v1=0x92f72d8060) at ./pointer-constraints-unstable-v1-client-protocol.h:347 347 ./pointer-constraints-unstable-v1-client-protocol.h: Aucun fichier ou dossier de ce type. #0 0x0092f4790b6e in zwp_pointer_constraints_v1_lock_pointer (lifetime=2, region=0x0, pointer=, surface=, zwp_pointer_constraints_v1=0x92f72d8060) at ./pointer-constraints-unstable-v1-client-protocol.h:347 #1 xwl_pointer_warp_emulator_lock (warp_emulator=0x92f7951ab0) at ../../../../../hw/xwayland/xwayland-input.c:2590 #2 0x0092f47930f8 in xwl_seat_maybe_lock_on_hidden_cursor (xwl_seat=xwl_seat@entry=0x92f72d7dd0) at ../../../../../hw/xwayland/xwayland-input.c:2762 #3 0x0092f4794660 in xwl_seat_maybe_lock_on_hidden_cursor (xwl_seat=0x92f72d7dd0) at ../../../../../hw/xwayland/xwayland-input.c:2823 #4 xwl_seat_confine_pointer (xwl_seat=0x92f72d7dd0, xwl_window=0x92f7464630) at ../../../../../hw/xwayland/xwayland-input.c:2814 #5 0x0092f48d60cf in ActivatePointerGrab (mouse=0x92f724e890, grab=0x92f797b910, time=..., autoGrab=) at ../../../../dix/events.c:1531 #6 0x0092f48d0db4 in GrabDevice (client=client@entry=0x92f769b470, dev=dev@entry=0x92f724e890, pointer_mode=1, keyboard_mode=1, grabWindow=, ownerEvents=, ctime=0, mask=0x7ffcba605420, grabtype=1, curs=0, confineToWin=31457299, status=0x7ffcba60541f "") at ../../../../dix/events.c:5120 #7 0x0092f48d3a1a in ProcGrabPointer (client=0x92f769b470) at ../../../../dix/events.c:4908 #8 0x0092f48c5e58 in Dispatch () at ../../../../dix/dispatch.c:479 #9 0x0092f48c9e80 in dix_main (argc=10, argv=0x7ffcba605628, envp=) at ../../../../dix/main.c:287 #10 0x7f6be880b421 in __libc_start_main (main=0x92f478ec50 , argc=10, argv=0x7ffcba605628, init=, fini=, rtld_fini=, stack_end=0x7ffcba605618) at ../csu/libc-start.c:291 #11 0x0092f478ec8a in _start () To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1713981/+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