[Desktop-packages] [Bug 1740869] Re: is not respoding window is constantly showing when debugging a program in Eclipse
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740869 Title: is not respoding window is constantly showing when debugging a program in Eclipse Status in mutter package in Ubuntu: Confirmed Bug description: Mentioned window about no responding program is showing and stealing focus when I try to debug a Java program in Eclipse. When I click on Wait, it disappears for a moment and opens again. This renders Ubuntu 17.10 with Gnome 3 nearly useless for program debugging. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 2 14:22:56 2018 InstallationDate: Installed on 2017-12-04 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+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 1722897] Re: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg)
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg) Status in mutter package in Ubuntu: Incomplete Bug description: I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd like to chat with someone about how Ubuntu Wayland works. Specifically, when a VM is configured to have 4MB of GPU memory, we have trouble setting modes above 1024x768@32bpp even though there's technically enough GPU memory to handle the framebuffer. This does not happen with Ubuntu 17.10 Xorg desktop. From what I can see there are two things: 1. Ubuntu Wayland seems to be allocated 2-3 framebuffer sized surfaces. Is it doing triple-buffering? 2. For certain modes, e.g. 1360x768 and 800x600, the pitch coming into .create_fb is greater than mode->width * bytes-per-pixel. For instance, for 800x600@32bpp, the requested pitch is 3328 instead of 3200. These two behaviors is different from what we assumed for low memory configurations, and so is causing some issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 Uname: Linux 4.13.0-syeh-v4.13 x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 12:50:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-10-03 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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.13.0-username-v4.13 root=UUID=e5e24738-af43-4671-9595-cccd3f4c77b8 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet modprobe.blacklist=vmwgfx kgdboc=ttyS1,115200 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 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:bd05/19/2017: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 N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 11 12:38:36 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No
[Desktop-packages] [Bug 1729170] Re: gnome window manager lacks keybindings
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1729170 Title: gnome window manager lacks keybindings Status in mutter package in Ubuntu: New Bug description: Alt-Space invokes the window manager menu with the usual entries (maximize/minimize/move/resize ). Alas, I have to select the menu item using arrows and Enter - there is no "hot keys" like "m" for minimize like it was with unity. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.1-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 22:47:47 2017 SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1729170/+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 1723877] Re: bad rendering of ":" character (white rectangular block)
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1723877 Title: bad rendering of ":" character (white rectangular block) Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When selecting an Ubuntu (wayland or x) session, the ":" character in the top panel clock renders as a white rectangular block (see attached png screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 09:47:34 2017 DisplayManager: gdm3 InstallationDate: Installed on 2015-11-17 (698 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-03 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723877/+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 1725180] Re: Shell animations are not smooth
** Tags added: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1725180 Title: Shell animations are not smooth Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently using Intel HD Graphics 630 as Nvidia seems to have no support for xwayland. The window/dock/launcher animations are lagging/shaky (not smooth). __ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725180/+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 1724732] Re: Wayland login options are missing when a radeon card is installed
Thank you (me) for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1724732 Title: Wayland login options are missing when a radeon card is installed Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Wayland login options are missing when a radeon card is installed. GDM only offers Xorg sessions... 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] Subsystem: Hewlett-Packard Company Cedar GL [FirePro 2270] Kernel driver in use: radeon Kernel modules: radeon And I'm not in hybrid mode either. The integrated graphics device is not listed by lspci. Strangely I can start weston on another VT successfully. Only mutter/gdm3 is refusing to show Wayland as an option. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 11:18:11 2017 InstallationDate: Installed on 2017-05-03 (168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+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 1725836] Re: No more than 2 displays work simultaneously
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: No more than 2 displays work simultaneously Status in Mutter: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1740484] Re: video corruption with amd RX560 and 2k display
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740484 Title: video corruption with amd RX560 and 2k display Status in mutter package in Ubuntu: Incomplete Status in mutter package in Fedora: Confirmed Bug description: When using wayland, I get a lot of video corruption on my 2k display. It usually shows up as bands of the background image or gnome-shell status bar flickering across the display at different vertical positions. There is a Fedora bug with a similar problem and video: https://bugzilla.redhat.com/show_bug.cgi?id=1417778 WORKAROUND: Select 'Gnome under X.Org' from the login screen instead of wayland. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 11:06:18 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-21-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Baffin [Radeon RX 560] [1da2:e348] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=2452d0da-14e9-4f88-9660-5a86aee79ff4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/mutter/+bug/1740484/+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 1727868] Re: New windows are unfocused and go below current window
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727868 Title: New windows are unfocused and go below current window Status in mutter package in Ubuntu: Incomplete Bug description: When new applications are launched from the terminal in 17.10, the windows are unfocused and appear below the current window. This is the opposite of the behavior in (at least) 16.10 and 17.04, where new windows would appear focused and on top. This appears to be a feature in Gnome 3, which is new in 17.10. Ubuntu users upgrading from earlier versions should not be assumed to be familiar Gnome 3, nor with how to tweak Gnome settings. The Release Notes should indicate this change and document how to turn it off. Also, and more importantly, there needs to actually be a way to restore the previous behavior. If there is, I've been unable to find it in Settings, gnome-tweak-tool, or dconf-editor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 17:43:57 2017 InstallationDate: Installed on 2016-12-27 (303 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-10-20 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727868/+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 1718393] Re: Keybindings stop working from time to time
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1718393 Title: Keybindings stop working from time to time Status in mutter package in Ubuntu: Incomplete Bug description: For some reason keybindings (like L) stop working. As workaround I need to redefine them in control center, but it will work until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.0-1 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: GNOME Date: Wed Sep 20 13:43:22 2017 SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-08-30 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1718393/+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 1716434] Re: Please revert "Call cogl_xlib_renderer_set_threaded_swap_wait_enabled()" to avoid high cpu usage when constantly rendering
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716434 Title: Please revert "Call cogl_xlib_renderer_set_threaded_swap_wait_enabled()" to avoid high cpu usage when constantly rendering Status in Mutter: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: Hello! There is performance regression in Mutter: https://bugzilla.gnome.org/show_bug.cgi?id=781835 While originally it was reported that issue is reproducible with nVidia proprietary driver, unfortunately it happens on Intel hardware too: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-323600036 If possible, please revert this commit https://git.gnome.org/browse/mutter/commit/?id=383ba566bd7c2a76d0856015a66e47caedef06b6 before Ubuntu 17.10 release. This issue could be related: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1696305 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1716434/+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 1714787] Re: Launching chocolate-doom or prboom-plus crashes Wayland session
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: chocolate-doom (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: prboom-plus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714787 Title: Launching chocolate-doom or prboom-plus crashes Wayland session Status in chocolate-doom package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in prboom-plus package in Ubuntu: Incomplete Bug description: When trying to launch Doom (both chocolate-doom and prboom-plus), the Wayland session will crash. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1 Uname: Linux 4.13.0-041300rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 10:37:38 2017 InstallationDate: Installed on 2017-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Tags: artful wayland-session Uname: Linux 4.12.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chocolate-doom/+bug/1714787/+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 1722501] Re: Tiling gedit causes the gedit window to get stuck.
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1722501 Title: Tiling gedit causes the gedit window to get stuck. Status in mutter package in Ubuntu: Incomplete Bug description: Using Ubuntu Budgie Beta2, fully updated, dragging a gedit window to be tiled causes the window to be stuck where it is dropped. Related: https://github.com/budgie-desktop/budgie-desktop/issues/1185 and https://github.com/budgie-desktop/budgie-desktop/issues/1189 After the fix, mentioned here: https://bugzilla.gnome.org/show_bug.cgi?id=788666, most windows can be tiled now, except for gedit windows. Those still make the desktop hang. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Oct 10 11:35:24 2017 InstallationDate: Installed on 2017-08-29 (41 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170829) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722501/+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 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] Status in mutter package in Ubuntu: Incomplete Bug description: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): 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 Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] It should be noted that all monitors are working as expected during boot (e.g. while typing my HDD unlock password) Regrettably the segfault information changes every time and apport doesn't seem able to capture reports for it. xfce sessions from lightdm start regularly and can use external monitors regularly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 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: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+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 1716271] Re: Window resize handles outside of window
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716271 Title: Window resize handles outside of window Status in mutter package in Ubuntu: Incomplete Bug description: Window resize controls appear only when mouse is outside of window, on its shadow. If window is in the corner or edge of the screen - that makes impossible to resize window using mouse. Ubuntu 17.10 daily with mutter 3.25.91+20170902~ce515c5-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716271/+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 1720838] Re: Nvidia gnome control center scale gets overridden on reboot
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1720838 Title: Nvidia gnome control center scale gets overridden on reboot Status in Mutter: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session. If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%". To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-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 375.82 Wed Jul 19 21:16:49 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 2 11:34:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230] InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20ENCTO1WW 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.13.0-12-generic.efi.signed root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET70W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 xserver.bootTime: Mon Oct 2 11:32:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1720838/+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 1716160] Re: System goes to sleep with external monitor and lid closed after login
** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716160 Title: System goes to sleep with external monitor and lid closed after login Status in Mutter: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gdm3 source package in Artful: Invalid Status in gnome-settings-daemon source package in Artful: Fix Released Status in mutter source package in Artful: Invalid Bug description: Using a laptop with lid closed and an external monitor, you can boot. Bios will show on the external monitor, as well as gdm when boot is finished. You can then choose a user and type in your password, which is accepted. But then, system goes to sleep (as the lid is cloesd I guess). Going out of sleep with the power button shows the gnome shell. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1716160/+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 1758289] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.42
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1758289 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.42-0ubuntu1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Bionic Beaver (development branch) 18.04 2)- 3)I expected to properly install NVIDIA DRIVERS. 4)BLACK SCREEN or ONLY LOGIN SCREEN WORKS. P.S. try 3 different drivers. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Fri Mar 23 03:30:39 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.42-0ubuntu1 ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.42-0ubuntu1 InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180322) Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.42-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1758289/+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 1727035] Re: apps start maximized randomly
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727035
Title:
apps start maximized randomly
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Firefox, thunderbird, aisleriot, all start full screen randomly.
Sometimes they start at the correct size at last close.
To reproduce: open {aisleriot|firefox|thunderbird} change size to not full
screen.
Close {aisleriot|firefox|thunderbird}
Open {aisleriot|firefox|thunderbird}
Result: {aisleriot|firefox|thunderbird} is full screen
Expected result: {aisleriot|firefox|thunderbird} is same size as when closed.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mutter 3.26.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 12:24:58 2017
InstallationDate: Installed on 2017-05-23 (153 days ago)
InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64
(20170412)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: Upgraded to artful on 2017-10-22 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727035/+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 1678456] Re: gnome-session depends on xwayland
I think this is implemented starting in Ubuntu 18.10. ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1678456 Title: gnome-session depends on xwayland Status in Mutter: Confirmed Status in mutter package in Ubuntu: Fix Released Bug description: With GNOME Wayland it should be possible to run GNOME without any legacy X or xwayland support. It should be an optional dependency, not a hard dependency. If anything, it should be a gnome-session-wayland dependency, not a gnome-session dependency. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sat Apr 1 12:26:37 2017 DisplayManager: lightdm InstallationDate: Installed on 2013-12-26 (1191 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1678456/+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 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I try to get a screenshot from my video and totem shows a message saying it could not get a screenshot of the video and suggesting to open a bug. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:54:16 2017 InstallationDate: Installed on 2017-09-29 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721248/+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 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1732245 Title: [wayland] Fullscreen games offset after returning from alt-tab Status in Mutter: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+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 1726207] Re: gnome-shell crashed with SIGSEGV in meta_window_force_restore_shortcuts()
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1726207 Title: gnome-shell crashed with SIGSEGV in meta_window_force_restore_shortcuts() Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: gnome-shell crashed with SIGSEGV in meta_window_force_restore_shortcuts() ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 09:14:11 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f4122b32330 : mov(%rdi),%rax PC (0x7f4122b32330) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_force_restore_shortcuts () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_keybindings_process_event () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell crashed with SIGSEGV in meta_window_force_restore_shortcuts() 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-shell/+bug/1726207/+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 1786881] Re: Languages always shown with English names
Fixed with: https://gitlab.gnome.org/GNOME/gnome-desktop/merge_requests/15 -- 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/1786881 Title: Languages always shown with English names Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Impact] Selecting a language from Settings always shows the names in English (e.g. German) instead of the name in the native language (e.g. Deutsch). [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: A list of languages is available, using the native language for each item, e.g. "English, Deutsch, ..." Observed result: A list of languages is available, using the English translations for each item, e.g. "English, German, ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+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 1717923] Re: 17.10 GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mutter (Ubuntu Artful) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1717923 Title: 17.10 GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent Status in Mutter: Confirmed Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Artful: Incomplete Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". journal excerpt === Aug 22 21:12:31 gnome-shell[23153]: Ignoring invalid monitor configuration for LVDS1:LGD:0x02f8:0x, VGA1:???:0x:0x: Logical monitors not adjecent Aug 22 21:12:32 kernel: gnome-shell[23153]: segfault at 8 ip 7f5a7c06ebd0 sp 7ffdc85ce7c8 error 4 in libmutter-1.so.0.0.0[7f5a7c015000+13e000] Workaround == Move or remove the hidden file ~/.config/monitors.xml to be able to log in to GNOME Shell. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1717923/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
** Tags added: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Unknown Status in mpv package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1715330 Title: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/923e1f8ff89aa3ff451c6aec260ec590152cf01a --- Artful Desktop daily, wayland session Test Case: Pre-requisites: Package update that downloads a payload and download fails (ie flash plugin) 1. Wait until the update-notifier dialog informing the user about the download failure shows up 2. Click on the 'Execute' buitton 3. Enter your credentials 4. Proceed with the download Expected result The package is downloaded Actual result This crash happens when the authentication window is displayed 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 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 09:41:48 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2014-07-23 (1140 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f72063804ef:mov0x8(%rdi),%eax PC (0x7f72063804ef) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so 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 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to artful on 2017-06-13 (84 days ago) UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1715330/+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 1700085] Re: Mouse cursor is tiny on HiDPI screens
** Tags added: bionic -- 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/1700085 Title: Mouse cursor is tiny on HiDPI screens Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am on Artful and have switched to GNOME as GNOME is the default desktop now and Unity shows some instabilities. I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with 14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi CRT resolution. With some effort I have at least got a somewhat useful scaling of the GUI elements (esp. text size), mainly by getting into Unity7, getting into the Display Settings there, removing my ~1.5 scaling factor, returning to GNOME, installing the advanced settings manager (gnome- tweak-tool or so) and setting a scaling factor of ~2). Large text in accessibilty does not work for me as it makes the text huge. Now the mouse cursor does no bother on all these changes. It stays always in its 72-dpi hard-coded size which is really tiny under GNOME on my QHD screen. It gets easily totally invisible for me, especially on text fields where it gets a skinny vertical bar. Therefore there are two fixes needed: 1. Mouse cursor needs to scale with scale factor for the desktop, so that it is in a good size relation with the rest of the desktop. Please take this into account for fractional scaling efforts. 2. Even a standard-sized mouse cursor can be too small for people with vision problems, so the accessibility options need a possibility to apply a (fractional) adjustable scaling factor to the mouse cursor's standard size. Please take these changes into account ASAP, ideally on 17.10 at the latest. Please consider backporting upstream fixes for achieving this goal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700085/+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 1711439] Re: Mutter crashing when workspace count is changed
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1711439 Title: Mutter crashing when workspace count is changed Status in mutter package in Ubuntu: Incomplete Bug description: Fresh install of Artful nightly from earlier this week. Steps to reproduce: 1. Open gnome-tweak-tool 2. Browse to workspaces pane 3. Change workspaces count (for me at this time 2->3->2) 4. I am returned to gdm login. Journal logging (EDIT: shortened as attached anyway): Aug 17 19:45:31 matt-xps-13-9360 org.gnome.Shell.desktop[1501]: ** Aug 17 19:45:31 matt-xps-13-9360 org.gnome.Shell.desktop[1501]: mutter:ERROR:core/screen.c:1263:update_num_workspaces: assertion failed: (w->windows == NULL) Aug 17 19:45:31 matt-xps-13-9360 gnome-calendar[2084]: Error reading events from display: Broken pipe Aug 17 19:45:31 matt-xps-13-9360 gnome-control-c[2077]: Error reading events from display: Broken pipe Aug 17 19:45:31 matt-xps-13-9360 seahorse[2085]: Error reading events from display: Broken pipe Aug 17 19:45:31 matt-xps-13-9360 gnome-terminal-[1834]: Error reading events from display: Broken pipe Aug 17 19:45:31 matt-xps-13-9360 nautilus[2082]: Error reading events from display: Broken pipe Aug 17 19:45:31 matt-xps-13-9360 gnome-tweak-too[2182]: Error reading events from display: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.24.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 17 19:54:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1711439/+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 1786881] Re: Languages always shown with English names
The design [1] is that they should show in the native language. That is what I've seen on other systems too (e.g. Android). It makes sense to me - if I only speak Mandarin then there's no reason why I would recognise the english word for that. [1] https://wiki.gnome.org/Design/SystemSettings/RegionAndLanguage -- 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/1786881 Title: Languages always shown with English names Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Impact] Selecting a language from Settings always shows the names in English (e.g. German) instead of the name in the native language (e.g. Deutsch). [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: A list of languages is available, using the native language for each item, e.g. "English, Deutsch, ..." Observed result: A list of languages is available, using the English translations for each item, e.g. "English, German, ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+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 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Are you saying this bug was fixed somewhere in 18.04? ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1714813] Re: No headphone sound.
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1714813 Title: No headphone sound. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Reproduces on: Ubuntu Mate: 16.04.3, 17.04, 17.10 Kubuntu: 17.04, 17.10 Ubuntu Budgie: 17.10 Probably not DE related since it is happening in KDE, Mate, and Budgie. Here's the output of `aplay -l` and `lspci`, let me know what other details I can provide: $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2) 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01) 04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1714813/+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 1756198] Re: Intermittent HDMI sound, working with some videos/audios, failing with others
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1756198 Title: Intermittent HDMI sound, working with some videos/audios, failing with others Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm using Lubuntu 17.10 on an ACER REVO RL80 connected to my TV through HDMI. The sound output is configured via sound settings (pavucontrol) to HDMI ouput. The sound is OK with some apps, and KO with some others. For example in VLC, it works usually fine. But on chromium/youtube, the sound is HS. Actually, i think it's not really a per app problem, but it might depend more on the type of audio being played. I thought the audio was working fine on firefox youtube at first, but once I ran into a specific video with the audio HS (and I checked this video had sound). When the audio is HS on a video play, if I start a video that usually doesn't have the problem, this video has the audio HS too. And reversely, if the audio is OK on a video, and if I start a video that usually have the problem, this time the video has its audio OK. Knowing this, I made a small sript to "fix" the audio of a video witht he problem. I pause the video with the audio problem, I start a sound hat usually doesn't have the problem, and I change the audio output back and forth to HDMI output again. It usually fixes audio, and I jsute need to resume the video with the problem BEFORE the good audio is over, and it's OK. This is my script mpv /path/to/whitenoise_48k.wav & pacmd set-card-profile 0 output:analog-stereo pacmd set-card-profile 0 output:hdmi-stereo And it's interesting to note that the same sound in 44k doesn't work (whitenoise_44k.wav). Weird stuff... These are the outputs of some commands, can make more if you want. aplay --list-devices List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC662 rev3 Digital [ALC662 rev3 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci -v 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f7e3 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel pacmd list-cards 1 card(s) available. index: 0 name: driver: owner module: 22 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7e3 irq 30" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1e20" device.product.name = "7 Series/C216 Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: no) output:analog-stereo: Analog Stereo Output (priority 6000, available: no) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560,
Re: [Desktop-packages] [Bug 1504697] Re: Message>Move does not work first time
Yes, I am on 16.04 indeed and I am expecting the system to invite me to
upgrade to 18.04 when that is worthwhile for me to do. Am I wrong here?
I have been using Shutter and only just now noticed how to set the delay
:-(
Glad to be able to help.
Humphrey
On 13/08/18 23:46, gf wrote:
> Hi again Humphrey.
> Thanks for picture. Sorry for the extra effort you had to go through to get
> the picture to me. The picture is most helpful to visualize what is happening.
>
> I think by your apport files that you are in Ubuntu version 16.04? Are
> you thinking of upgrading to 18.04 sometime soon?
>
> By the way, I use a small screen capture program called "Screenshot." It
> allows you to set a delay, and it will wait a specified time before
> taking the snap shot, so that you can go through the steps for a bug,
> like this Alt-m-m issue.
>
> Take care
> :)
> G
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1504697
Title:
Message>Move does not work first time
Status in thunderbird package in Ubuntu:
New
Bug description:
After starting tb, the first time I want to move a message with
Message>Move nothing happens.
The drop-down menu just sits there with the "Move" entry highlighted, but no
sub-menu appears.
I tried to do a screen shot, but that didn't work.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunderbird 1:38.3.0+build1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: humphrey 1508 F pulseaudio
/dev/snd/controlC1: humphrey 1508 F pulseaudio
BuildID: 20150930122345
Channel: Unavailable
CurrentDesktop: Unity
Date: Sat Oct 10 10:20:30 2015
ExecutablePath: /usr/lib/thunderbird/thunderbird
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-09-08 (31 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
IpRoute:
default via 192.168.0.1 dev eth0 proto static
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.101 metric
1
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
Profiles: Profile0 (Default) - LastVersion=38.3.0/20150930122345 (In use)
RelatedPackageVersions:
totem-mozilla 3.10.1-1ubuntu4
rhythmbox-mozilla 3.0.2-0ubuntu2
RfKill:
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.4
dmi.board.name: 0N185P
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.4:bd04/17/2009:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 420 Series
dmi.sys.vendor: Dell Inc.
---
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: humphrey 2346 F pulseaudio
/dev/snd/controlC1: humphrey 2346 F pulseaudio
BuildID: 20180710085647
Channel: Unavailable
DistroRelease: Ubuntu 16.04
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2017-12-13 (240 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
IpRoute:
default via 192.168.1.1 dev enp4s0 proto static metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.103
metric 100
IwConfig:
enp4s0no wireless extensions.
lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Tags added: fixed-in-mutter-3.29.91 ** Tags added: cosmic ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in GNOME Shell: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/160 --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786883] Re: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. No Wayland login option.
This patch seems to fix it: https://gitlab.gnome.org/GNOME/gdm/merge_requests/32 ** No longer affects: mutter (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. No Wayland login option. Status in gdm3 package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/264 --- The cosmic login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. I can tell because from ssh user 'gdm' is running: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 and not the usual Xwayland. Also the login screen offers no choice of Xorg or Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.29.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Tue Aug 14 11:41:31 2018 InstallationDate: Installed on 2018-05-26 (79 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+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 1725312] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed() from st_scroll_view_style_changed()
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/353139 -- 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/1725312 Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed() from st_scroll_view_style_changed() Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/467 Upstream fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/190 --- I was restoring a backup when this occurred. I was not interacting with the system at the time. ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 06:58:55 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f840ef624f1 : orb $0x1,0x30(%rbx) PC (0x7f840ef624f1) ok source "$0x1" ok destination "0x30(%rbx)" (0xfbf0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed() 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-shell/+bug/1725312/+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 1783571] Re: Set Yaru as default
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/353139 -- 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/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1786881] Re: Languages always shown with English names
This appears to be due to libc using the LANGUAGE environment variable over the value set in setlocale (). -- 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/1786881 Title: Languages always shown with English names Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Impact] Selecting a language from Settings always shows the names in English (e.g. German) instead of the name in the native language (e.g. Deutsch). [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: A list of languages is available, using the native language for each item, e.g. "English, Deutsch, ..." Observed result: A list of languages is available, using the English translations for each item, e.g. "English, German, ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in linux package in Ubuntu: Confirmed Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/847001/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** No longer affects: gnome-power-manager (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in linux package in Ubuntu: Confirmed Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/847001/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Comment #46 suggests to me the delay is in writes to /sys/class/backlight/. Indeed they don't use much CPU time but take too long to return. So that would make this a kernel bug... ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in linux package in Ubuntu: Confirmed Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/847001/+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 1787064] Re: Malfunction right click touch pad
*** This bug is a duplicate of bug 1759300 *** https://bugs.launchpad.net/bugs/1759300 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1759300, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1759300 Gnome Shell: Touchpad right click (bottom right) area does not work -- 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/1787064 Title: Malfunction right click touch pad Status in Ubuntu: New Bug description: Right click of touch pad does not function after upgrade to 18.04 LTS This is the only error detected so far Laptop ASUS X450L ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 08:50:53 2018 DistUpgraded: 2018-08-14 15:46:53,780 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:13fd] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:13fd] InstallationDate: Installed on 2014-05-03 (1564 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X450LN ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=b37d80a0-d27f-45b1-9e4f-6e7bd5709af3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LN.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX450LN.208:bd05/21/2014:svnASUSTeKCOMPUTERINC.:pnX450LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 14 09:23:53 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5265 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1787064/+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 1786948] Re: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load
I don't *think* that gnome-shell promises to maintain a stable API (?). I've added some extension-specific tasks here and am closing the gnome- shell task. Please add tasks for any other extensions that were installed from the archive. ** Also affects: gnome-shell-extension-dashtodock (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905106 Importance: Unknown Status: Unknown ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Confirmed ** Summary changed: - Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load + Some shell extensions (dash to dock, hide top bar) to fail to load with gnome-shell 3.29 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Some shell extensions (dash to dock, hide top bar) to fail to load with gnome-shell 3.29 Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Debian: Unknown Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+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 1787049] Re: fgnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event()
** Summary changed: - fgnome-shell crashed with SIGSEGV in meta_window_unmaximize() + fgnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() ** Summary changed: - fgnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() + gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() ** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787049 Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c --- I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi PC (0x7f598429b278) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787049/+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 1787049] Re: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event()
Also tracking in: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c ** Description changed: + https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c + + --- + I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi - PC (0x7f598429b278) ok - source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! - destination "%esi" ok + Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi + PC (0x7f598429b278) ok + source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! + destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so + meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo ** Tags added: cosmic -- 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/1787049 Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c --- I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi PC (0x7f598429b278) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell
[Desktop-packages] [Bug 1787008] Re: Disconnecting hdmi connected monitor does not reposition windows
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: multimonitor -- 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/1787008 Title: Disconnecting hdmi connected monitor does not reposition windows Status in gnome-shell package in Ubuntu: New Bug description: At time when i disconnect my monitor the windows are occasionally not repositioned on the remaining monitor on my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Aug 14 21:01:33 2018 DistUpgraded: 2018-04-27 17:12:36,606 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053] InstallationDate: Installed on 2018-03-08 (158 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20FMS2AV00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ae4268b-5721-48e8-9702-9fcdfa60f6f6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-04-27 (109 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787008/+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 1787049] Re: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787049 Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c --- I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi PC (0x7f598429b278) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787049/+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 1786999] Re: bluetooth coupling is only possible in certain combinations
** Also affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1786999 Title: bluetooth coupling is only possible in certain combinations Status in gnome-bluetooth package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Initializing a bluetooth coupling on an Android device causes a notification to be displayed in gnome-shell which doesn't display the "confirm" or ~"ignore" buttons. When clicking on the notification (which seems the only intuitive way to make the buttons visible) the notification disappears and apparently selects to ignore the requests implicitly. The user has to guess that. Initializing the coupling from the Ubuntu side works find because the confirmation has to be performed on the device. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.15.18-041518-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 14 17:23:28 2018 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-30 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1786999/+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 1787068] Re: /usr/bin/gnome-shell:11:meta_window_unmaximize:update_move:meta_window_handle_mouse_grab_op_event:meta_display_handle_event:event_callback
*** This bug is a duplicate of bug 1787049 *** https://bugs.launchpad.net/bugs/1787049 ** This bug has been marked a duplicate of bug 1787049 gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() -- 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/1787068 Title: /usr/bin/gnome- shell:11:meta_window_unmaximize:update_move:meta_window_handle_mouse_grab_op_event:meta_display_handle_event:event_callback Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787068/+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 1787068] [NEW] /usr/bin/gnome-shell:11:meta_window_unmaximize:update_move:meta_window_handle_mouse_grab_op_event:meta_display_handle_event:event_callback
*** This bug is a duplicate of bug 1787049 *** https://bugs.launchpad.net/bugs/1787049 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic -- 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/1787068 Title: /usr/bin/gnome- shell:11:meta_window_unmaximize:update_move:meta_window_handle_mouse_grab_op_event:meta_display_handle_event:event_callback Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787068/+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 1302192] Re: capabilities not preserved on installation
This is in use in cosmic and the autopkgtests pass in bionic. I don't think any further SRU verification is necessary here. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Status in livecd-rootfs source package in Bionic: Fix Committed Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+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 1706357] Re: Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Tags added: artful ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1706357 Title: Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything Status in gnome-shell package in Ubuntu: Incomplete Status in xserver-xorg-input-synaptics package in Ubuntu: Incomplete Bug description: Selecting (or turning off) natural scrolling in settings->Mouse and Touchpad appears to do nothing, scrolling remains the same using a two finger scroll. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706357/+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 1787064] [NEW] Malfunction right click touch pad
Public bug reported: Right click of touch pad does not function after upgrade to 18.04 LTS This is the only error detected so far Laptop ASUS X450L ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 08:50:53 2018 DistUpgraded: 2018-08-14 15:46:53,780 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:13fd] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:13fd] InstallationDate: Installed on 2014-05-03 (1564 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X450LN ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=b37d80a0-d27f-45b1-9e4f-6e7bd5709af3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LN.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX450LN.208:bd05/21/2014:svnASUSTeKCOMPUTERINC.:pnX450LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 14 09:23:53 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5265 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1787064 Title: Malfunction right click touch pad Status in xorg package in Ubuntu: New Bug description: Right click of touch pad does not function after upgrade to 18.04 LTS This is the only error detected so far Laptop ASUS X450L ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 08:50:53 2018 DistUpgraded: 2018-08-14 15:46:53,780 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:13fd] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:13fd] InstallationDate: Installed on 2014-05-03 (1564 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X450LN ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=b37d80a0-d27f-45b1-9e4f-6e7bd5709af3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American
[Desktop-packages] [Bug 1787063] [NEW] package libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-ins
Public bug reported: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 15 08:44:16 2018 ErrorMessage: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-installed ) InstallationDate: Installed on 2018-08-14 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: freerdp Title: package libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-installed ) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freerdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1787063 Title: package libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-installed ) Status in freerdp package in Ubuntu: New Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 15 08:44:16 2018 ErrorMessage: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-installed ) InstallationDate: Installed on 2018-08-14 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: freerdp Title: package libfreerdp-cache1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: 现在尚不能配置软件包 libfreerdp-cache1.1:amd64 不能配置(目前状态为 half-installed ) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1787063/+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 1787061] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1787061 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Installed non-free nvidia driver for GeForce 310M. After restart received this error and was prompted for a bug report. I also did a partial upgrade before restarting after switching to the non-free driver. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Wed Aug 15 09:58:34 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-onuSgl/33-nvidia-340_340.107-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 InstallationDate: Installed on 2018-01-28 (198 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1787061/+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 1540110] Re: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available.
Please note that the upstream bug hasn't expired but is now on GitLab: https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/39 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1540110 Title: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available. Status in GNOME Disks: Expired Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: gnome-disk-utility (show as "Disks" on the desktop environment running Unity) systematically does not acknowledge that disks have SMART capabilities when connected through a USB port; SMART capabilities are grayed. However, 'sudo smartctl -a /dev/' works fine confirming that there is no problem reading SMART data through a USB link. gnome- disk-utility acknowledge SMART capabilities if the same disk is connected through a SATA port. Confirmed for Ubuntu 14.04 LTS Trusty Tahr on 2016-01-26, gnome-disk- utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon. This bug is the same as bug #1092900 which was reported against Ubuntu 10.04 LTS Lucid Lynx. Following user dino99 suggestion, I opened this new bug report to follow the same problem on Ubuntu 14.04 LTS Trusty Tahr. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 31 11:30:03 2016 InstallationDate: Installed on 2014-11-01 (456 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1540110/+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 1787061] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles
Public bug reported: Installed non-free nvidia driver for GeForce 310M. After restart received this error and was prompted for a bug report. I also did a partial upgrade before restarting after switching to the non-free driver. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Wed Aug 15 09:58:34 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-onuSgl/33-nvidia-340_340.107-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 InstallationDate: Installed on 2018-01-28 (198 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1787061 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Installed non-free nvidia driver for GeForce 310M. After restart received this error and was prompted for a bug report. I also did a partial upgrade before restarting after switching to the non-free driver. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Wed Aug 15 09:58:34 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-onuSgl/33-nvidia-340_340.107-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 InstallationDate: Installed on 2018-01-28 (198 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package libgles2:amd64 1.0.0+git20180308-4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1787061/+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 1786789] Re: Update to 2.63.90
This bug was fixed in the package libsoup2.4 - 2.63.90-1
Sponsored for Iain Lane (laney)
---
libsoup2.4 (2.63.90-1) experimental; urgency=medium
* debian/{gbp.conf,control{,.in}}: Update for experimental.
* New upstream release 2.63.90 (LP: #1786789)
- Avoid unaligned memory accesses in WebSocket implementation
- Bail out on cookie-jar calls with empty hostnames
- Fix crash under soup_socket_new()
- Fix critical warning in SoupSocket
- Fix digest authentication with encoded URIs
- Fixes to GObject-introspection
- Fixes to the simple-httpd example
- Fixes to xmlrpc-server test with PHP >= 7.2 and related
- Many Coverity-found code fixes
- Set default cookie path for NULL origins
- Use atomic-refcounting in classes that are not using GObject-refcounting
- Use base domain to decide if cookies are third-party
- Use libpsl for the SoupTLD API instead of shipping a copy of the
public-suffix list
* debian/control.in:
- Build-Depend on libpsl-dev per upstream.
- Rules-Requires-Root: no - we don't need to be root to build/test.
- Standards-Version → 4.2.0
* debian/patches: Drop, included from upstream.
-- Iain Lane Fri, 10 Aug 2018 13:29:19 +0100
** Changed in: libsoup2.4 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1786789
Title:
Update to 2.63.90
Status in libsoup2.4 package in Ubuntu:
Fix Released
Bug description:
Do it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1786789/+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 1786958] Re: Update to 3.29.91
This bug was fixed in the package evince - 3.29.91-1 --- evince (3.29.91-1) experimental; urgency=medium * New upstream development release - User interface updates including "decluttered" headerbar * Build-Depend on libgspell-1-dev & libsynctex-dev * debian/evince.install: the AppStream metadata file was renamed * debian/evince.docs: This version doesn't include a README * debian/libevview3-3.symbols: Add new symbols * Bump Standards-Version to 4.2.0 -- Jeremy Bicha Tue, 14 Aug 2018 10:21:23 -0400 ** Changed in: evince (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1786958 Title: Update to 3.29.91 Status in evince package in Ubuntu: Fix Released Bug description: The update has been done in Debian, we just need to sync it once published To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1786958/+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 1087075] Re: Duplex options ignored for printing Postscript
I can confirm that this bug still exists in Ubuntu 16.04.5: specifically, I tried printing two pages of a PostScript file from Evince with Duplex set to "Long Edge (Standard)", and instead of a single sheet with both pages, the printer printed on two sheets. I also had the following error on the terminal from which I launched Evince: "fatal internal error -100" eight times, without a newline between the repetitions. It would be good to find a solution to this problem. -- 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/1087075 Title: Duplex options ignored for printing Postscript Status in cups package in Ubuntu: Incomplete Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 1776912] Re: chromium-browser package does NOT install an AppData file
Hi Olivier, sorry for the late reply but I'm in the middle of an overseas relocation (UK > Spain) + holidays and I'm a bit off the grid these days... Thanks for your comment, and sorry for reporting it against the wrong branch. Hopefully this will help having a better chromium package for future releases, though. Let me know if you need anything else from me and I'll try to help when I get some time with my computer (will be a bit off the grid for a while still, but on September things should get back to normal). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776912 Title: chromium-browser package does NOT install an AppData file Status in chromium-browser package in Ubuntu: Confirmed Bug description: In order for Chromium Browser to integrate properly with software centers (e.g. GNOME Software), an additional XML file with metadata needs to be installed under /usr/share/metainfo, in the form of an "AppData file", containing the relevant bits according to the AppStream specification: https://www.freedesktop.org/software/appstream/docs Fortunately, upstream has included that file in the chromium repository for a while (since [1]) and, as far as I can see, Fedora is already installing that file in its place, see https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462 I have quickly looked into the .install and rules files in of the chromium-browser package for Ubuntu [2][3] and I could not find any trace of this happening, so I guess all that would remain here would be to adapt the debian packaging files to make sure that it gets installed too for Ubuntu, similar to what Fedora and other distros do already. [1] https://chromium.googlesource.com/chromium/src.git/+/d6807b9a7da70dae9191b93d4ec6157187515078%5E%21 [2] https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/chromium-browser.install [3] https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/rules https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1776912/+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 1723756] Re: gnome-control-center crashed with SIGSEGV in on_notification_dismissed()
** Tags added: cosmic -- 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/1723756 Title: gnome-control-center crashed with SIGSEGV in on_notification_dismissed() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I received this crash report while working normally on my desktop. Ubuntu 17.10 beta final. Gnome and KDE are both installed. This was a Gnome3 (ubuntu on xorg) session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 17:23:51 2017 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55f650aada44:mov0xc0(%rax),%rdi PC (0x55f650aada44) ok source "0xc0(%rax)" (0x00c0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to artful on 2017-10-10 (5 days ago) 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/1723756/+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 1787033] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1723756 *** https://bugs.launchpad.net/bugs/1723756 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 #1723756, 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/1787033/+attachment/5175381/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175383/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175386/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175387/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175388/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175389/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1787033/+attachment/5175390/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1723756 gnome-control-center crashed with SIGSEGV in on_notification_dismissed() ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1787033 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: Got this crash when trying to remove a printer from gnome-control- center. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.29.90-1~ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 14 15:41:01 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-08-14 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180814) ProcCmdline: gnome-control-center ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x565069bd7404:mov0xd0(%rax),%rdi PC (0x565069bd7404) ok source "0xd0(%rax)" (0x00d0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() 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/1787033/+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 1787020] [NEW] package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] failed to install/upgrade: libp11-kit-gnome-
Public bug reported: error during the upgrade from 16.04 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 AptOrdering: libp11-kit-gnome-keyring:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 14 23:10:39 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 [origin: unknown] libc6 2.27-3ubuntu1 [origin: unknown] libgcc1 1:8-20180414-1ubuntu2 [origin: unknown] multiarch-support 2.27-3ubuntu1 [origin: unknown] DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.1-1ubuntu1_all.deb (--unpack): libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances InstallationDate: Installed on 2013-11-28 (1720 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1787020 Title: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances Status in gnome-keyring package in Ubuntu: New Bug description: error during the upgrade from 16.04 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 AptOrdering: libp11-kit-gnome-keyring:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 14 23:10:39 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 [origin: unknown] libc6 2.27-3ubuntu1 [origin: unknown] libgcc1 1:8-20180414-1ubuntu2 [origin: unknown] multiarch-support 2.27-3ubuntu1 [origin: unknown] DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libp11-kit-gnome-keyring_3.28.0.1-1ubuntu1_all.deb (--unpack): libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances InstallationDate: Installed on 2013-11-28 (1720 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 [modified: usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so] failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.1-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed
[Desktop-packages] [Bug 1787022] [NEW] Update shotwell to 0.29.4
Public bug reported: I believe Shotwell intends to release 0.30 around the time GNOME 3.30 is released in September. https://gitlab.gnome.org/GNOME/shotwell/blob/master/NEWS We should package the new version. I am not intending to work on this now. Note that the Debian package is not maintained by the Debian GNOME team and therefore the git workflow is different. https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/shotwell ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1787022 Title: Update shotwell to 0.29.4 Status in shotwell package in Ubuntu: New Bug description: I believe Shotwell intends to release 0.30 around the time GNOME 3.30 is released in September. https://gitlab.gnome.org/GNOME/shotwell/blob/master/NEWS We should package the new version. I am not intending to work on this now. Note that the Debian package is not maintained by the Debian GNOME team and therefore the git workflow is different. https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1787022/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I have the exact same problem in Ubuntu 18.04.1 tottaly updated, including backports. Mark Smith #26 commentary works with me also. I think the gdebi-gtk when not opened from terminal, crashes when I have to type me password -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Added gnome-shell to affected packages, as the issue is independent of gnome-power-manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+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 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Adding some more information. Running the following as root in a gnome terminal: SYSFILE=/sys/class/backlight/intel_backlight/brightness OLD_VAL=$(cat $SYSFILE) NEW_VAL=$((OLD_VAL + 100)) T0=$(date +%N) time echo $NEW_VAL | tee $SYSFILE T1=$(date +%N) echo "Total time (millis): $(((T1 - T0)/1000))" Gives the following: real0m0.002s user0m0.002s sys 0m0.001s Total time (millis): 3502 In other words, the write to sysfs returns in 2ms (and indeed, brightness changes instantly), but it takes 3502ms for control to get back to the prompt. During that time, the system seems to hang, but keypresses are collected: they are all echoed to the terminal right after the command returns. So the question then is: where are the 3 seconds spent? I'm happy to experiment if someone has instructions. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+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 1681129] Re: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch
** Package changed: ubuntu => mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1681129 Title: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch Status in mesa package in Ubuntu: New Bug description: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=bc09f41a-6b3d-47f9-b01d-9ac1dce625eb ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0110N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0110N8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 23 08:37:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 34381 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1681129/+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 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: jackd2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+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 1681129] [NEW] debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch
You have been subscribed to a public bug: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=bc09f41a-6b3d-47f9-b01d-9ac1dce625eb ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0110N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0110N8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 23 08:37:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 34381 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch https://bugs.launchpad.net/bugs/1681129 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa 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 1787008] [NEW] Disconnecting hdmi connected monitor does not reposition windows
Public bug reported: At time when i disconnect my monitor the windows are occasionally not repositioned on the remaining monitor on my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Aug 14 21:01:33 2018 DistUpgraded: 2018-04-27 17:12:36,606 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053] InstallationDate: Installed on 2018-03-08 (158 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20FMS2AV00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ae4268b-5721-48e8-9702-9fcdfa60f6f6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-04-27 (109 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1787008 Title: Disconnecting hdmi connected monitor does not reposition windows Status in xorg package in Ubuntu: New Bug description: At time when i disconnect my monitor the windows are occasionally not repositioned on the remaining monitor on my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Aug 14 21:01:33 2018 DistUpgraded: 2018-04-27 17:12:36,606 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053] InstallationDate: Installed on 2018-03-08 (158 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20FMS2AV00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ae4268b-5721-48e8-9702-9fcdfa60f6f6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-04-27 (109 days ago) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Desktop-packages] [Bug 1241643] Re: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug
Hi, I do no longer possess that printer, so it is no longer a problem for me. Thank you Sven -- 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/1241643 Title: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug Status in cups package in Ubuntu: Incomplete Bug description: I tried to install a canon ip4000 printer, installation got stuck. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CupsErrorLog: Date: Fri Oct 18 15:34:53 2013 DuplicateSignature: package:cups:1.7.0~rc1-0ubuntu5:subproces installed post-installation script gaf een foutwaarde 1 terug ErrorMessage: subproces installed post-installation script gaf een foutwaarde 1 terug InstallationDate: Installed on 2013-10-10 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Sony Corporation VPCF11M1E MarkForUpload: True Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=20f1a842-8225-44fc-99e8-fb648057f991 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=20f1a842-8225-44fc-99e8-fb648057f991 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0280Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF11M1E:pvrC603VG5N:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF11M1E dmi.product.version: C603VG5N dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1241643/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I *might* have a possible clue for the gdebi gui crash in Bionic. If I right click on a .deb file and tell it to install with gdebi the gui will crash. If I open a terminal in the same directory as the file and launch gdebi-gtk *.deb the gui will install and uninstall the .deb file without crashing. I hope this offers a potential clue for a fix, I love the gdebi installer and I thank ALL of you programmers for your diligence and hard work!! Mark -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1786999] [NEW] bluetooth coupling is only possible in certain combinations
Public bug reported: Initializing a bluetooth coupling on an Android device causes a notification to be displayed in gnome-shell which doesn't display the "confirm" or ~"ignore" buttons. When clicking on the notification (which seems the only intuitive way to make the buttons visible) the notification disappears and apparently selects to ignore the requests implicitly. The user has to guess that. Initializing the coupling from the Ubuntu side works find because the confirmation has to be performed on the device. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.15.18-041518-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 14 17:23:28 2018 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-30 (106 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1786999 Title: bluetooth coupling is only possible in certain combinations Status in gnome-shell package in Ubuntu: New Bug description: Initializing a bluetooth coupling on an Android device causes a notification to be displayed in gnome-shell which doesn't display the "confirm" or ~"ignore" buttons. When clicking on the notification (which seems the only intuitive way to make the buttons visible) the notification disappears and apparently selects to ignore the requests implicitly. The user has to guess that. Initializing the coupling from the Ubuntu side works find because the confirmation has to be performed on the device. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.15.18-041518-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 14 17:23:28 2018 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-30 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786999/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
I created inside /etc/x11/xorg.conf.d/ -- 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/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 725922] Re: No audio on browsers (Firefox/chrome)
Thanks. Closing as "Invalid" as issue never confirmed by another user. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/725922 Title: No audio on browsers (Firefox/chrome) Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox No audio using Flash Player in chrome or Firefox ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Feb 27 00:45:09 2011 FirefoxPackages: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/725922/+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 1706357] Re: Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything
** Package changed: mousepad (Ubuntu) => xserver-xorg-input-synaptics (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1706357 Title: Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything Status in gnome-shell package in Ubuntu: New Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Selecting (or turning off) natural scrolling in settings->Mouse and Touchpad appears to do nothing, scrolling remains the same using a two finger scroll. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706357/+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 1785806] Re: Update gnome-disk-utility to 3.29.90
This bug was fixed in the package gnome-disk-utility - 3.29.90-1ubuntu1 --- gnome-disk-utility (3.29.90-1ubuntu1) cosmic; urgency=medium * Sync with Debian (lp: #1785806). Remaining change: - Add dont-use-libdvdread.patch: + Revert commit that depends on libdvdread since it's in universe -- Sebastien Bacher Tue, 14 Aug 2018 17:09:47 +0200 ** Changed in: gnome-disk-utility (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1785806 Title: Update gnome-disk-utility to 3.29.90 Status in gnome-disk-utility package in Ubuntu: Fix Released Bug description: Update to 3.29.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1785806/+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 1706357] [NEW] Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything
You have been subscribed to a public bug: Selecting (or turning off) natural scrolling in settings->Mouse and Touchpad appears to do nothing, scrolling remains the same using a two finger scroll. ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: Confirmed -- Natural scrolling in Gnome Shell (17.10) doesn't appear to do anything https://bugs.launchpad.net/bugs/1706357 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics 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 725922] Re: No audio on browsers (Firefox/chrome)
ubuntu deprecated, no problem to cloe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/725922 Title: No audio on browsers (Firefox/chrome) Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox No audio using Flash Player in chrome or Firefox ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Feb 27 00:45:09 2011 FirefoxPackages: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/725922/+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 1785802] Re: Update gnome-calculator to 3.29.90
This bug was fixed in the package gnome-calculator - 1:3.29.91-1ubuntu1 --- gnome-calculator (1:3.29.91-1ubuntu1) cosmic; urgency=medium * Sync with Debian (lp: #1785802). Remaining change: - Add epoch -- Sebastien Bacher Tue, 14 Aug 2018 17:03:08 +0200 ** Changed in: gnome-calculator (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1785802 Title: Update gnome-calculator to 3.29.90 Status in gnome-calculator package in Ubuntu: Fix Released Bug description: Update gnome-calcualtor to 3.29.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1785802/+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 1786881] Re: Languages always shown with English names
@Robert: Probably this is not fixed at all. But do we want language names be displayed using the native language? Does upstream do so? ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned) -- 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/1786881 Title: Languages always shown with English names Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Impact] Selecting a language from Settings always shows the names in English (e.g. German) instead of the name in the native language (e.g. Deutsch). [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: A list of languages is available, using the native language for each item, e.g. "English, Deutsch, ..." Observed result: A list of languages is available, using the English translations for each item, e.g. "English, German, ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+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 1786880] Re: Changing language doesn't show previously selected language
I committed Gunnar's branch - hopefully that fixes the issue. It'll be bundled with the next upload, unless we don't get a release for a while in which case we should upload it. ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed -- 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/1786880 Title: Changing language doesn't show previously selected language Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: [Impact] Changing language in Settings doesn't show currently selected language. [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: The list of available languages shows the current language selected. Observed result: No languages are shown as selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786880/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
At least some of my issue was triggered by a yet unfixed NIS/systemd bug. systemd-logind would hang (and watchdog kicks in) if it tried to contact the NIS service because of a new IP firewall they implemented. I don't think this was entirely all of my problems but it certainly confused the issue. See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664 -- 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/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 --- No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 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 CrashCounter: 1 Date: Mon Feb 8 17:07:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, init=, fini=, rtld_fini=, stack_end=0x7fffc9e34fc8) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 17:08:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 9847 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1786948] Re: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load
Someone will probably need to file bugs against individual extensions that don't work with GNOME Shell 3.29.90. For instance, there is this bug for Dash to Dock: https://bugs.debian.org/905106 ** Bug watch added: Debian Bug tracker #905106 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905106 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load Status in gnome-shell package in Ubuntu: Incomplete Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+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 1785806] Re: Update gnome-disk-utility to 3.29.90
** Changed in: gnome-disk-utility (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1785806 Title: Update gnome-disk-utility to 3.29.90 Status in gnome-disk-utility package in Ubuntu: Fix Committed Bug description: Update to 3.29.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1785806/+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 1785802] Re: Update gnome-calculator to 3.29.90
** Changed in: gnome-calculator (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1785802 Title: Update gnome-calculator to 3.29.90 Status in gnome-calculator package in Ubuntu: Fix Committed Bug description: Update gnome-calcualtor to 3.29.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1785802/+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 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment
Same on bionic 18.04:
$ python2 --version
Python 2.7.15rc1
$ sudo hp-doctor -i
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 340, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 332, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
# Edit: pdb.set_trace()
$ sudo hp-doctor
> /usr/share/hplip/base/g.py(333)xint()
-> return l
(Pdb) ver
'2.7.15rc1'
(Pdb) ver.split('.')
['2', '7', '15rc1']
(Pdb) [int(x) for x in ver.split('.')]
*** ValueError: invalid literal for int() with base 10: '15rc1'
(Pdb)
Code work-around:
# Convert string to int and return a list.
def xint(ver):
try:
l = [int(x) for x in ver.split('.')]
except:
l = []
for x in ver.split('.'):
try:
l.append(int(x))
except:
l.append(None)
return l
$ sudo hp-doctor
error: cupsext not present in the system. Please re-install HPLIP.
# debug info: [2, 7, None]
Solution for me is `python3 hp-doctor` instead:
$ python3 -VV
Python 3.6.5 (default, Apr 1 2018, 05:46:30)
[GCC 7.3.0]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1759278
Title:
hp-doctor: UnboundLocalError: local variable 'l' referenced before
assignment
Status in HPLIP:
New
Status in hplip package in Ubuntu:
Confirmed
Bug description:
hp-doctor is trying to parse the Python version. Probably other tools
are too.
On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an
integer.
On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an
integer.
Neither of these will work.
% hp-doctor
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
(Note that my printer will only print "Unsupported Personality: UNKNOWN".
This is probably an unrelated problem.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: hplip 3.17.10+repack0-5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 14:49:56 2018
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: System manufacturer System Product Name
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb
kernel.sysrq=1
SourcePackage: hplip
UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1759278/+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 1759278] Re: hp-doctor: UnboundLocalError: local variable 'l' referenced before assignment
My OS is:
$ lsb_release -a
Distributor ID: LinuxMint
Description:Linux Mint 19 Tara
Release:19
Codename: tara
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1759278
Title:
hp-doctor: UnboundLocalError: local variable 'l' referenced before
assignment
Status in HPLIP:
New
Status in hplip package in Ubuntu:
Confirmed
Bug description:
hp-doctor is trying to parse the Python version. Probably other tools
are too.
On Python 2, sys.version is "2.7.14+", whos parts cannot be parsed as an
integer.
On Python 3, sys.version is "3.6.5rc1", whos parts cannot be parsed as an
integer.
Neither of these will work.
% hp-doctor
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
(Note that my printer will only print "Unsupported Personality: UNKNOWN".
This is probably an unrelated problem.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: hplip 3.17.10+repack0-5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
Date: Tue Mar 27 14:49:56 2018
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: System manufacturer System Product Name
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed
root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb
kernel.sysrq=1
SourcePackage: hplip
UpgradeStatus: Upgraded to bionic on 2018-02-19 (35 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1759278/+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 1784617] Re: Update gnome-initial-setup to 3.29.1
This bug was fixed in the package gnome-initial-setup - 3.29.1-1ubuntu1 --- gnome-initial-setup (3.29.1-1ubuntu1) cosmic; urgency=medium * Merge from Debian experimental (lp: #1784617). Remaining changes: + debian/control.in: - Build-Depends on libsnapd-glib-dev, libsoup2.4-dev, libsysmetrics-dev - Enable langpack usage + Ubuntu-specific patches: - 0001-Don-t-run-welcome-tour-at-end.patch - 0001-Make-summary-page-explicitly-request-navigation-butt.patch - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch - 0001-Add-Ubuntu-mode-with-special-pages.patch - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch - 0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch * d/p/0001-Add-Ubuntu-mode-with-special-pages.patch: - Support Meson build system - Show an dialog in case of error when enabling Livepatch (lp: #1764723) - Enable online accounts page (lp: #1762192) * d/p/0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch: - Enable online accounts page (lp: #1762192) * d/p/0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch: - Show "Ubuntu Single Sign-on" first in the list in the online accounts page. * d/p/0007-goa-adjust-description-to-not-mention-email-or-conta.patch: - Adjust online account description to not mention email or contacts. -- Andrea Azzarone Tue, 14 Aug 2018 16:12:10 +0200 ** Changed in: gnome-initial-setup (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1784617 Title: Update gnome-initial-setup to 3.29.1 Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: Update gnome-initial-setup to 3.29.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1784617/+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 1762192] Re: Ubuntu Welcome could offer to set up Online Accounts
This bug was fixed in the package gnome-initial-setup - 3.29.1-1ubuntu1 --- gnome-initial-setup (3.29.1-1ubuntu1) cosmic; urgency=medium * Merge from Debian experimental (lp: #1784617). Remaining changes: + debian/control.in: - Build-Depends on libsnapd-glib-dev, libsoup2.4-dev, libsysmetrics-dev - Enable langpack usage + Ubuntu-specific patches: - 0001-Don-t-run-welcome-tour-at-end.patch - 0001-Make-summary-page-explicitly-request-navigation-butt.patch - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch - 0001-Add-Ubuntu-mode-with-special-pages.patch - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch - 0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch * d/p/0001-Add-Ubuntu-mode-with-special-pages.patch: - Support Meson build system - Show an dialog in case of error when enabling Livepatch (lp: #1764723) - Enable online accounts page (lp: #1762192) * d/p/0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch: - Enable online accounts page (lp: #1762192) * d/p/0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch: - Show "Ubuntu Single Sign-on" first in the list in the online accounts page. * d/p/0007-goa-adjust-description-to-not-mention-email-or-conta.patch: - Adjust online account description to not mention email or contacts. -- Andrea Azzarone Tue, 14 Aug 2018 16:12:10 +0200 ** Changed in: gnome-initial-setup (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762192 Title: Ubuntu Welcome could offer to set up Online Accounts Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: The GNOME version of gnome-initial-setup offers to set up Online Accounts. This seems like a really useful feature that I'd like to see in the "Welcome to Ubuntu" version too. I suggest we show the GNOME Online Accounts (goa) page before the apps page. A few issues I noticed but I don't think they are blockers: Issues == 1. There is a different design pattern in the GNOME version with a top logo. I don't think it looks bad; I'm just mentioning it. 2. "Connect your accounts to easily access your email, online calendar, contacts, documents and photos." I proposed a wording change to GNOME to make this a bit more accurate for us https://bugzilla.gnome.org/795077 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1762192/+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 1764723] Re: gnome-initial-setup says that Livepatch is "all set" even if enabling is still in progress.
This bug was fixed in the package gnome-initial-setup - 3.29.1-1ubuntu1 --- gnome-initial-setup (3.29.1-1ubuntu1) cosmic; urgency=medium * Merge from Debian experimental (lp: #1784617). Remaining changes: + debian/control.in: - Build-Depends on libsnapd-glib-dev, libsoup2.4-dev, libsysmetrics-dev - Enable langpack usage + Ubuntu-specific patches: - 0001-Don-t-run-welcome-tour-at-end.patch - 0001-Make-summary-page-explicitly-request-navigation-butt.patch - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch - 0001-Add-Ubuntu-mode-with-special-pages.patch - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch - 0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch * d/p/0001-Add-Ubuntu-mode-with-special-pages.patch: - Support Meson build system - Show an dialog in case of error when enabling Livepatch (lp: #1764723) - Enable online accounts page (lp: #1762192) * d/p/0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch: - Enable online accounts page (lp: #1762192) * d/p/0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch: - Show "Ubuntu Single Sign-on" first in the list in the online accounts page. * d/p/0007-goa-adjust-description-to-not-mention-email-or-conta.patch: - Adjust online account description to not mention email or contacts. -- Andrea Azzarone Tue, 14 Aug 2018 16:12:10 +0200 ** Changed in: gnome-initial-setup (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1764723 Title: gnome-initial-setup says that Livepatch is "all set" even if enabling is still in progress. Status in gnome-initial-setup package in Ubuntu: Fix Released Status in gnome-initial-setup source package in Bionic: In Progress Bug description: * Impact - Livepatch can fail to install and the user will never be notified about the error. * Test case - Install ubuntu 18.04 - Wait for the wizard to be displayed - Activate livepatch in the livepatch page - Disconnect the system from the internet -> After a while an error message dialog should be displayed * Regression potential Gnome-initial-setup fails to properly close (make sure that after a while the process is no longer running). * Original bug In Livepatch page we show the message "You're all set: Livepatch is now on" even if this is not true. Enabling livepatch requires several time-steps (e.g. installing the snap, getting the token, etc) that can fail at any time. We should update the message and show a notification in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1764723/+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 1786880] Re: Changing language doesn't show previously selected language
Launchpad branch: https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-control- center/+git/gnome-control-center/+ref/fix-patch I couldn't figure out how to request a merge proposal, though. -- 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/1786880 Title: Changing language doesn't show previously selected language Status in gnome-control-center package in Ubuntu: In Progress Bug description: [Impact] Changing language in Settings doesn't show currently selected language. [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: The list of available languages shows the current language selected. Observed result: No languages are shown as selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786880/+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 1783515] Re: package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
** Package changed: python-numpy (Ubuntu) => hplip (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1783515 Title: package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in hplip package in Ubuntu: New Bug description: I can not install the pitivi software and get an error message when I start the computer ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-numpy 1:1.13.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 25 10:45:51 2018 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2018-06-08 (46 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: python-numpy Title: package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1783515/+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 1786958] [NEW] Update to 3.29.91
Public bug reported: The update has been done in Debian, we just need to sync it once published ** Affects: evince (Ubuntu) Importance: Wishlist Status: Fix Committed ** Tags: upgrade-software-version ** Changed in: evince (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1786958 Title: Update to 3.29.91 Status in evince package in Ubuntu: Fix Committed Bug description: The update has been done in Debian, we just need to sync it once published To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1786958/+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 1783515] [NEW] package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
You have been subscribed to a public bug: I can not install the pitivi software and get an error message when I start the computer ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-numpy 1:1.13.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 25 10:45:51 2018 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2018-06-08 (46 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: python-numpy Title: package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package python3-numpy 1:1.13.3-2ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré https://bugs.launchpad.net/bugs/1783515 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip 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 1786944] Re: package ubuntu-software 3.20.5-0ubuntu0.16.04.11 failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status
According to the attached the problem is older than 2018-08-02. We would need logs from when the problem started happening to understand what caused it. Please try running the following command and let us know if this fixes the issue: apt-get -f install If it doesn't, please inspect /var/log/apt/term.log* and /var/log/apt/history.log* and attach the relevant ones (the ones that include the first mention of a problem when installing/upgrading packages). If in doubt, the first archive should be enough: /var/log/apt/term.log.1.gz /var/log/apt/history.log.1.gz ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- 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/1786944 Title: package ubuntu-software 3.20.5-0ubuntu0.16.04.11 failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-software package in Ubuntu: Incomplete Bug description: impossible de mettre la version untuntu 18.04 à jour. et l'ensemble des mises à jour semble ne pas pouvoir s'exécuter. impossible to update ubuntu 18.04. and all updates seem to be unable to run. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: foo-yc20: Install ubuntu-software: Configure foo-yc20: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 14 14:48:42 2018 DuplicateSignature: package:ubuntu-software:3.20.5-0ubuntu0.16.04.11 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration ErrorMessage: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-05-09 (827 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: gnome-software Title: package ubuntu-software 3.20.5-0ubuntu0.16.04.11 failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2018-08-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1786944/+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 1244369] Re: Keeps pausing for ages whilst downloading IMAP
Thanks Derek. Marking Invalid. ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1244369 Title: Keeps pausing for ages whilst downloading IMAP Status in thunderbird package in Ubuntu: Invalid Bug description: Running 24.0.1 on Windows 7 x64 Ultimate. I'm trying to download my brother's Hotmail e-mai for him, so that I can then copy it to the Local folders as an offline backup. However, it's taking ages because TB keeps pausing for ages and no apparent reason. My brother has a number of folders for his e-mail on Hotmail and for example, on the folder 2009 it stopped for several minutes at 144 out of 272. Then it get to 153 and paused again for several minutes, then it went to 269 and paused again for several minutes. It's probably taken at least 15 minutes so far just to do that one folder. When it got to 272 out of 272, it again paused for ages and then when it had finished, just didn't do anything for a while. Now it's start on the folder "2010" and has got to 14 out of 1420 and paused again. When it's paused, Task Manager shows that TB is not doing anything. Under Account Settings I have "Keep messages for this account on the computer" and have all his folders except for Deleted ticked. However, if I right-click on the Account in the main window and select Subscribe, it shows all the folders, including Deleted, ticked so obviously these settings are for different uses. If I disable "Keep messages" and then drag each IMAP folder to Local Folders to copy it, it doesn't seem to pause and although slow (no doubt a limitation of IMAP) it steadily downloads the messages and Task Manager shows around 2-3% CPU. However, if I drag multiple folders to copy instead of a single one, it does seem to start pausing quite often again, even though it's only copying one folder at a time, perhaps the others being queued triggers the problem. Actually, I just tried again only dragging one of the folders "Newsletters", which was the first one it was copying when dragging multiple folders and that's having problems, currently paused at 41 out of 151. Several of the folders I'd copied previous to this one had the same amount of e-mails and didn't pause, so it doesn't appear to be the number of e-mails in a folder that's the issue. Testing on my own system the other day, with both Hotmail and Gmail accounts, I found that when copying the mail from the IMAP folders to the Local Folders, it appeared to be downloading it all again, despite it already being stored on my PC, which doesn't seem right. It also seemed to make no difference to the size of the TB data files when disabling "Keep messages for this account on the computer" with Inbox being around 600MB and Sent around 550MB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1244369/+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
