[Desktop-packages] [Bug 663184] Re: cannot connect to PPTP server with iPhone
I appreciate your query & i try my best to provide you the proper solution or suggestion to resolve your issues.If you are getting issue while connecting PPTP server with iPhone then i suggest you to follow this blog: https://www.mactechnicalsupportnumbers.com/blog/itunes- error-1671/, to get your solution back. Thanks for Sharing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/663184 Title: cannot connect to PPTP server with iPhone Status in network-manager-pptp package in Ubuntu: Triaged Bug description: Binary package hint: network-manager-pptp Hi, I have a MacBook Pro with dualboot and Ubuntu 10.10 as second OS. I suspect there is something wrong with iPhone / PPTP interaction. I am not sure this is the correct place for a bug report, but you can always point me to the right direction, correct? OSX + pptp + iphone => OK OSX + pptp + wireless => OK Ubuntu 10.10 + pptp + wireless => OK Ubuntu 10.10 + pptp + iphone ≠ doesn't work In other words - the same iPhone works with PPTP VPN connection from OSX and the same VPN connection works over wireless in both OSX and Linux. But PPTP over iPhone in Ubuntu doesn't work. Connection times out. This happens both with USB and Bluetooth connection. Comparing two connection logs - failed and successful, I see that "PPTP_SET_LINK_INFO received from peer_callid 0" message is never received from PPTP server and messages file has this record Oct 19 12:43:30 poga-linux pppd[3470]: LCP: timeout sending Config-Requests Logfiles are below. Message log for failed connection attempt: Oct 19 12:42:59 poga-linux pppd[3470]: Plugin /usr/lib/pppd/2.4.5//nm-pptp-pppd-plugin.so loaded. Oct 19 12:42:59 poga-linux pppd[3470]: pppd 2.4.5 started by root, uid 0 Oct 19 12:42:59 poga-linux pppd[3470]: Using interface ppp0 Oct 19 12:42:59 poga-linux pppd[3470]: Connect: ppp0 <--> /dev/pts/1 Oct 19 12:43:30 poga-linux pppd[3470]: LCP: timeout sending Config-Requests Oct 19 12:43:30 poga-linux pppd[3470]: Connection terminated. Oct 19 12:43:30 poga-linux pppd[3470]: Modem hangup Oct 19 12:43:30 poga-linux pppd[3470]: Exit. Daemon log for succesful connection via wireless: Oct 19 12:40:12 poga-linux NetworkManager[1007]: Starting VPN service 'org.freedesktop.NetworkManager.pptp'... Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN service 'org.freedesktop.NetworkManager.pptp' started (org.freedesktop.NetworkManager.pptp), PID 3121 Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN service 'org.freedesktop.NetworkManager.pptp' appeared, activating connections Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN plugin state changed: 1 Oct 19 12:40:22 poga-linux NetworkManager[1007]: VPN plugin state changed: 3 Oct 19 12:40:22 poga-linux NetworkManager[1007]: VPN connection 'VPN' (Connect) reply received. Oct 19 12:40:22 poga-linux modem-manager: (net/ppp0): could not get port's parent device Oct 19 12:40:22 poga-linux NetworkManager[1007]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Oct 19 12:40:22 poga-linux NetworkManager[1007]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Oct 19 12:40:23 poga-linux pptp[3128]: nm-pptp-service-3121 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Oct 19 12:40:24 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 39142). Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:950]: PPTP_SET_LINK_INFO received from peer_callid 0 Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:953]: send_accm is , recv_accm is Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 warn[ctrlp_disp:pptp_ctrl.c:956]: Non-zero Async Control Character Maps are not supported! Oct 19 12:40:31 poga-linux NetworkManager[1007]: VPN connection 'VPN' (IP Config Get) reply received. Oct 19 12:40:31 poga-linux NetworkManager[1007]: VPN Gateway:
[Desktop-packages] [Bug 663184] Re: cannot connect to PPTP server with iPhone
Dear Neil, I appreciate your reply, but do you realise how old exatcly this bug is? I don't remeber anything about it, I use Ubuntu 18.x now (occasionally) and I have a completely different phone now. Thanks anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/663184 Title: cannot connect to PPTP server with iPhone Status in network-manager-pptp package in Ubuntu: Triaged Bug description: Binary package hint: network-manager-pptp Hi, I have a MacBook Pro with dualboot and Ubuntu 10.10 as second OS. I suspect there is something wrong with iPhone / PPTP interaction. I am not sure this is the correct place for a bug report, but you can always point me to the right direction, correct? OSX + pptp + iphone => OK OSX + pptp + wireless => OK Ubuntu 10.10 + pptp + wireless => OK Ubuntu 10.10 + pptp + iphone ≠ doesn't work In other words - the same iPhone works with PPTP VPN connection from OSX and the same VPN connection works over wireless in both OSX and Linux. But PPTP over iPhone in Ubuntu doesn't work. Connection times out. This happens both with USB and Bluetooth connection. Comparing two connection logs - failed and successful, I see that "PPTP_SET_LINK_INFO received from peer_callid 0" message is never received from PPTP server and messages file has this record Oct 19 12:43:30 poga-linux pppd[3470]: LCP: timeout sending Config-Requests Logfiles are below. Message log for failed connection attempt: Oct 19 12:42:59 poga-linux pppd[3470]: Plugin /usr/lib/pppd/2.4.5//nm-pptp-pppd-plugin.so loaded. Oct 19 12:42:59 poga-linux pppd[3470]: pppd 2.4.5 started by root, uid 0 Oct 19 12:42:59 poga-linux pppd[3470]: Using interface ppp0 Oct 19 12:42:59 poga-linux pppd[3470]: Connect: ppp0 <--> /dev/pts/1 Oct 19 12:43:30 poga-linux pppd[3470]: LCP: timeout sending Config-Requests Oct 19 12:43:30 poga-linux pppd[3470]: Connection terminated. Oct 19 12:43:30 poga-linux pppd[3470]: Modem hangup Oct 19 12:43:30 poga-linux pppd[3470]: Exit. Daemon log for succesful connection via wireless: Oct 19 12:40:12 poga-linux NetworkManager[1007]: Starting VPN service 'org.freedesktop.NetworkManager.pptp'... Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN service 'org.freedesktop.NetworkManager.pptp' started (org.freedesktop.NetworkManager.pptp), PID 3121 Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN service 'org.freedesktop.NetworkManager.pptp' appeared, activating connections Oct 19 12:40:12 poga-linux NetworkManager[1007]: VPN plugin state changed: 1 Oct 19 12:40:22 poga-linux NetworkManager[1007]: VPN plugin state changed: 3 Oct 19 12:40:22 poga-linux NetworkManager[1007]: VPN connection 'VPN' (Connect) reply received. Oct 19 12:40:22 poga-linux modem-manager: (net/ppp0): could not get port's parent device Oct 19 12:40:22 poga-linux NetworkManager[1007]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Oct 19 12:40:22 poga-linux NetworkManager[1007]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Oct 19 12:40:23 poga-linux pptp[3128]: nm-pptp-service-3121 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Oct 19 12:40:24 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Oct 19 12:40:25 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 39142). Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:950]: PPTP_SET_LINK_INFO received from peer_callid 0 Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 log[ctrlp_disp:pptp_ctrl.c:953]: send_accm is , recv_accm is Oct 19 12:40:27 poga-linux pptp[3135]: nm-pptp-service-3121 warn[ctrlp_disp:pptp_ctrl.c:956]: Non-zero Async Control Character Maps are not supported! Oct 19 12:40:31 poga-linux NetworkManager[1007]: VPN connection 'VPN' (IP Config Get) reply received. Oct 19 12:40:31 poga-linux NetworkManager[1007]: VPN Gateway: x.x.x.x Oct 19 12:40:31 poga-linux NetworkManager[1007]: Tunnel Device: ppp0 Oct 19 12:40:31 poga-linux Network
[Desktop-packages] [Bug 1800479] Re: 18.10 Wayland segmentation fault (11) for any qt application
Hi Daniel! Well, here's what i have atm: 1)Yes, i have crash file there, and using your instructions i can't tell you the ID of newly-created bug yet :-( In journal: Oct 30 10:39:33 pc whoopsie[1635]: [10:39:33] Parsing /var/crash/_usr_bin_Xwayland.1000.crash. Oct 30 10:39:33 pc whoopsie[1635]: [10:39:33] Uploading /var/crash/_usr_bin_Xwayland.1000.crash. In terminal: /var/crash$ ubuntu-bug _usr_bin_Xwayland.1000.crash /var/crash$ And that's all. 2)It looks like there are only mine reports. https://errors.ubuntu.com/user/6626511b8d58d5f8e77588f2617b1a2e80e5d6f1a0054b078e23c26b18f7586ad593232adaf57e66f92ebc61cd4d94e07e9b24cf45003d744ef595b6ec8338ab -- 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/1800479 Title: 18.10 Wayland segmentation fault (11) for any qt application Status in xorg-server package in Ubuntu: Incomplete Bug description: Dear all! Starting from some beta 18.10 i experience continious segv fault in Wayland session. COnfiguration is acer swift 5 with 2 additional 24" dell monitors. I choose wayland session in gdm. Everything starts smoothly and good, gnome applications runs ver good. If i will not use any qt application - everything is good. If i start any qt - graphical server crashes immediately and drops me to gdm prompt. During usual xorg session everything is OK. Here's what i have in general log: ___ Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Backtrace: Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x55f02dd6dc39] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f2c91ebbe1f] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f2c8e3b3760] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f2c8e2784b1] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f2c8e19552a] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f2c8e1955ee] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f2c8e1956c9] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f2c8e061432] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f2c8e3cd35d] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f2c8e791e89] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f2c8e78fc93] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 11: /usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55f02dc9ac69] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 12: /usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55f02dc9868b] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 13: /usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55f02dd5c61d] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 14: /usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55f02dca2bd9] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 15: /usr/bin/Xwayland (glvndGetExports+0xde5) [0x55f02dd7cf35] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 16: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55f02dd37bae] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 17: /usr/bin/Xwayland (InitFonts+0x3b6) [0x55f02dd3bb36] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f2c91ce309b] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) 19: /usr/bin/Xwayland (_start+0x2a) [0x55f02dc0d1ea] Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) Segmentation fault at address 0x68 Oct 29 16:30:50 dshuvalovpc org.gnome.Shell.desktop[2612]: (EE) O
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/357992 -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/357993 -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799262] Re: OpenVPN doesn't respect dns servers in settings
The output of systemd-resolve in attachment. > The behaviour change could be a side effect of the fix for bug #1754671 Before update to Cosmic in Bionic everything works fine ** Attachment added: "systemd-resolve.log" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1799262/+attachment/5207070/+files/systemd-resolve.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1799262 Title: OpenVPN doesn't respect dns servers in settings Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Hello! After upgrading to Ubuntu 18.10 OpenVPN doesn't respect dns servers in settings. It trying to resolve internal host with default DNS server except resolving with dns servers from connection settings. On Ubuntu 18.04 all works fine 1) 18.10 2) 1.8.6-1ubuntu1 3) OpenVPN uses DNS servers for resolving from connection settings 4) Resolving used by default DNS server ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-openvpn 1.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:46:17 2018 InstallationDate: Installed on 2018-09-24 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to cosmic on 2018-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1799262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800604] [NEW] package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in pack
Public bug reported: No user impact, just apport message received. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-common 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Oct 29 16:28:47 2018 DuplicateSignature: package:libsane-common:1.0.27-1~experimental3ubuntu2 Unpacking libsane-common (1.0.27-1~experimental3ubuntu2) over (1.0.25+git20150528-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-O8tDiq/09-libsane-common_1.0.27-1~experimental3ubuntu2_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 ErrorMessage: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 InstallationDate: Installed on 2017-12-18 (315 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, 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.6 SourcePackage: sane-backends Title: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2017-12-28T11:51:30.738804 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1800604 Title: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane- config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 Status in sane-backends package in Ubuntu: New Bug description: No user impact, just apport message received. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-common 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Oct 29 16:28:47 2018 DuplicateSignature: package:libsane-common:1.0.27-1~experimental3ubuntu2 Unpacking libsane-common (1.0.27-1~experimental3ubuntu2) over (1.0.25+git20150528-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-O8tDiq/09-libsane-common_1.0.27-1~experimental3ubuntu2_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 ErrorMessage: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 InstallationDate: Installed on 2017-12-18 (315 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, 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.6 SourcePackage: sane-backends Title: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2017-12-28T11:51:30.738804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1800604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800604] Re: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in packag
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1800604 Title: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane- config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 Status in sane-backends package in Ubuntu: New Bug description: No user impact, just apport message received. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-common 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Oct 29 16:28:47 2018 DuplicateSignature: package:libsane-common:1.0.27-1~experimental3ubuntu2 Unpacking libsane-common (1.0.27-1~experimental3ubuntu2) over (1.0.25+git20150528-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-O8tDiq/09-libsane-common_1.0.27-1~experimental3ubuntu2_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 ErrorMessage: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 InstallationDate: Installed on 2017-12-18 (315 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, 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.6 SourcePackage: sane-backends Title: package libsane-common 1.0.27-1~experimental3ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/sane-config.1.gz', which is also in package libsane-dev 1.0.25+git20150528-1ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2017-12-28T11:51:30.738804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1800604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
Hi, I confirm too on Ubuntu 18.04 NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
PSJSingh, As I wrote in the upstream report, #1 wasn't enough for app grid, you had to filter the notify::checked signal callback, but we're going with the fix proposed that just handles both. -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800634] [NEW] Mouse Movement Inverted
Public bug reported: I'm not sure this is gnome shell, as the behavior was also seen in GDM. Except in GDM, the entire screen was upside down in addition to the mouse being inverted. Upon login to gnome shell, the mouse pointer was upside down, and my movements on the mouse were inverted. Meaning when I moved my mouse up, the pointer went down (using an actual mouse, not a touchpad). I believe left and right worked properly (I can't remember clearly) But when I got the mouse over to the top-right of the screen to turn on wifi (NetworkManager was mysteriously not running -- solved by 'systemctl start NetworkManager' in a terminal), it actually opened up the gnome shell activities menu. Meaning that gnome-shell, at least from my interpretation, interpreted the click as being in the top-left of the screen instead of the top-right. I was able to finally open firefox (I had given up on mouse movement at this point and was using keyboard shortcuts) and googled the problem. I found this page: https://askubuntu.com/questions/1061403/ubuntu-18-04-1-upside-down- mouse-cursor-and-inverted-position I did an 'apt update' and 'apt full-upgrade', and then executed 'apt-get remove iio-sensor-proxy'. The reboot afterward took longer than usual it seemed, but it finally went down. Seeing that removing the iio- sensor-proxy worked, I was trying to figure out what sort of sensor would be triggering this behavior. And then I saw that I had my PS4 controller plugged in, which has the sixaxis sensor in it. Removing that package fixed the problem. My mouse/screen is no longer inverted, and my PS4 controller (which I'm assuming has the sensor) is still plugged in. 1) [joe@titan:~]$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 2) [joe@titan:~]$ apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) I expected screen and mouse behavior to be normal. 4) Screen was upside down on GDM, but correct in gnome-shell. I'm not sure if the mouse movement was correct or upside down in GDM, typically I never touch my mouse during the login process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 06:33:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport 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-10-27 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic gnome -- 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/1800634 Title: Mouse Movement Inverted Status in gnome-shell package in Ubuntu: New Bug description: I'm not sure this is gnome shell, as the behavior was also seen in GDM. Except in GDM, the entire screen was upside down in addition to the mouse being inverted. Upon login to gnome shell, the mouse pointer was upside down, and my movements on the mouse were inverted. Meaning when I moved my mouse up, the pointer went down (using an actual mouse, not a touchpad). I believe left and right worked properly (I can't remember clearly) But when I got the mouse over to the top-right of the screen to turn on wifi (NetworkManager was mysteriously not running -- solved by 'systemctl start NetworkManager' in a terminal), it actually opened up the gnome shell activities menu. Meaning that gnome-shell, at least from my interpretation, interpreted the click as being in the top-left of the screen instead of the top-right. I was able to finally open firefox (I had given up on mouse movement at this point and was using keyboard shortcuts) and googled the problem. I found this page: https://askubuntu.com/questions/1061403/ubuntu-18-04-1-upside-down- mouse-cursor-and-inverted-position I did an 'apt update' and 'apt full-upgrade', and then executed 'apt- get remove iio-sensor-proxy'. The reboot afterward took longer than usual it seemed, but it finally went down
[Desktop-packages] [Bug 1719797] Re: Firmware update seemingly not working
On Bionic, I'm running: $ apt-cache policy fwupd fwupd: Installed: 1.0.9-0ubuntu2 Candidate: 1.0.9-0ubuntu2 Version table: *** 1.0.9-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.6-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.5 Candidate: 3.28.1-0ubuntu4.18.04.5 Version table: *** 3.28.1-0ubuntu4.18.04.5 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4.18.04.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages I have a firmware update pending (handy!). Go to the firmware update tab, click Update on the fwupdate. After a second or two it tells me that it's done and the update disappears from the list. Clicking "refresh", the update stays hidden. Quitting and reloading g-s, the update stays hidden, as expected. All passed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in fwupd source package in Bionic: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software package in Fedora: Unknown Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798228] Re: Snap search results not in the same order as command line
Running gnome-software from proposed: apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.5 Candidate: 3.28.1-0ubuntu4.18.04.5 Version table: *** 3.28.1-0ubuntu4.18.04.5 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4.18.04.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Opened g-s, searched for "Sky", and Skype was the top result, as is expected. Passed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1798228 Title: Snap search results not in the same order as command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Won't Fix Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] When searching in GNOME Software, the Snap results are not returned in the same order as the command line. This is due to classic snaps being considered a lower quality than strict snaps. [Test Case] 1. Open GNOME Software 2. Search for "sky" Expected result: Snaps matching "sky" are returned, with the same order as the command line (Skype is first) Observed result: While mostly in the same order, some snaps are not (Skype is the last snap in the list, in eighth position). [Regression Potential] The fix is to set the "match value" of each Snap GsApp to be the order the results are returned in. This field is checked before the "kudo" field which is populated based on the confinement used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Changed in: mutter (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu: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/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358005 ** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358006 ** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358007 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu: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/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800640] [NEW] Plane 1 (SMP) characters are not justified properly in Writer
Public bug reported: Justifying paragraphs with Unicode Plane 1 (SMP) characters does not work as expected. See the attached screenshot of a document with one paragraph in Gothic (U+10330–U+1034F) and another one in Old Hungarian (U+10C80–U+10CFF). Both paragraphs have been justified but visually only the left edge seems aligned. If you try selecting words with the keyboard or the mouse, the font metrics are totally off. In the attached screenshot, I have selected the second word of the sentence (𐌼𐌰𐌽𐌽𐌰) but visually it looks like two characters of the following word have been selected as well. Both scripts display the same behavior although Gothic is an LTR script and Old Hungarian is RTL. Description:Ubuntu 18.04.1 LTS Release:18.04 libreoffice-writer: Installed: 1:6.0.6-0ubuntu0.18.04.1 Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 11:31:48 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot Plane 1 justification.png" https://bugs.launchpad.net/bugs/1800640/+attachment/5207144/+files/Screenshot%20Plane%201%20justification.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1800640 Title: Plane 1 (SMP) characters are not justified properly in Writer Status in libreoffice package in Ubuntu: New Bug description: Justifying paragraphs with Unicode Plane 1 (SMP) characters does not work as expected. See the attached screenshot of a document with one paragraph in Gothic (U+10330–U+1034F) and another one in Old Hungarian (U+10C80–U+10CFF). Both paragraphs have been justified but visually only the left edge seems aligned. If you try selecting words with the keyboard or the mouse, the font metrics are totally off. In the attached screenshot, I have selected the second word of the sentence (𐌼𐌰𐌽𐌽𐌰) but visually it looks like two characters of the following word have been selected as well. Both scripts display the same behavior although Gothic is an LTR script and Old Hungarian is RTL. Description: Ubuntu 18.04.1 LTS Release: 18.04 libreoffice-writer: Installed: 1:6.0.6-0ubuntu0.18.04.1 Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 11:31:48 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1800640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800640] Re: Plane 1 (SMP) characters are not justified properly in Writer
** Attachment added: "Document used to create the screenshot" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1800640/+attachment/5207147/+files/Plane%201%20justification.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1800640 Title: Plane 1 (SMP) characters are not justified properly in Writer Status in libreoffice package in Ubuntu: New Bug description: Justifying paragraphs with Unicode Plane 1 (SMP) characters does not work as expected. See the attached screenshot of a document with one paragraph in Gothic (U+10330–U+1034F) and another one in Old Hungarian (U+10C80–U+10CFF). Both paragraphs have been justified but visually only the left edge seems aligned. If you try selecting words with the keyboard or the mouse, the font metrics are totally off. In the attached screenshot, I have selected the second word of the sentence (𐌼𐌰𐌽𐌽𐌰) but visually it looks like two characters of the following word have been selected as well. Both scripts display the same behavior although Gothic is an LTR script and Old Hungarian is RTL. Description: Ubuntu 18.04.1 LTS Release: 18.04 libreoffice-writer: Installed: 1:6.0.6-0ubuntu0.18.04.1 Candidate: 1:6.0.6-0ubuntu0.18.04.1 Version table: *** 1:6.0.6-0ubuntu0.18.04.1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 11:31:48 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1800640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Description changed: + [ Impact ] + + In some early intel GPUs gdm can't start in wayland mode, and so gnome- + shell + + [ Test case ] + + - Start the pc or logout/end session + - Try to login with the "Ubuntu on Wayland" session + - Ubuntu should start + + [ Regression potential ] + + Possible false positive on wayland support check on some cards + + + --- + + https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - DisplayManager: gdm3DistroRelease: Ubuntu 17.10 + CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True ** Merge proposal unlinked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358006 ** Merge proposal unlinked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] In some early intel GPUs gdm can't start in wayland mode, and so gnome-shell [ Test case ] - Start the pc or logout/end session - Try to login with the "Ubuntu on Wayland" session - Ubuntu should start [ Regression potential ] Possible false positive on wayland support check on some cards --- https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1571237] Re: incorrect displaying of color state in inkjet by printer Brother MFC-J5720DW
Thanks for the update, Tothsoft. I believe the status should still be "New" "Confirmed" status is for tickets where another reporter has experienced the same issue. I will change the status back to "new" Thanks again for taking the time to submit the apport information. :) G ** Changed in: system-config-printer (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1571237 Title: incorrect displaying of color state in inkjet by printer Brother MFC- J5720DW Status in system-config-printer package in Ubuntu: New Bug description: Hi, It is incorrect displaying of color state of inkjet by printer Brother MFC-J5720DW, through application system-config-printer. It display all 4 color, but in not good order (application have order Black/Yellow/Cyan/Magenta; but printer have order Magenta/Cyan/Yellow/Black) it means that when black color is 0 % in printer, in system-config-printer is displayed that Magenta is 0%. It was at computers with linux mint 17.3/Ubuntu 14.04 amd64 bit --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-07-29 (92 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lpstat: device for Boomaga: boomaga:/ device for BRFAX: usb:/dev/usb/lp0 device for Brother_DCP_L2520DW_series: ipp://BRWC48E8FC5C81A.local:631/ipp/print device for MFCJ5720DW: dnssd://Brother%20MFC-J5720DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c66f7b1 device for PDF: cups-pdf:/ MachineType: Hewlett-Packard HP EliteBook 8570w NonfreeKernelModules: nvidia Package: system-config-printer 1.5.11-1ubuntu2 [origin: Ubuntu] PackageArchitecture: all Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer (w/ options) MFCJ5720DW: Brother MFC-J5720DW CUPS Brother_DCP_L2520DW_series: DCP-L2520DW series Boomaga: Boomaga printer BRFAX: Brother BRMFCFAX for CUPS ProcEnviron: LANGUAGE=sk TERM=xterm PATH=(custom, no user) LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=4f52eb9a-4d4c-46cb-98b3-3af6fa25f32f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: third-party-packages tara Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: Toto nie je oficiálny Linux balík. Prosím, odstráňte všetky balíky tretích strán a skúste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1571237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
I have the same problem as Walter (alsa reload helps). The laptop is Asus VivoBook Pro 17, audio device is "00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)". Can I help with solving this issue in any way? -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
** Description changed: + [ Impact ] + Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. - ProblemType: Bug - DistroRelease: Ubuntu 17.10 + [ Test case ] + + - Look for xterm in gnome-shell activities and add it to favourtes + - With the ubuntu-dock showing in the desktop, touch the xterm icon + - Only one instance if it should open + - Tapping the app icons grid should properly open the g-s overview + - Tapping on dock icons when in overview mode should work normally + + [ Regression potential ] + + Taps on other gnome-shell buttons could not work poperly (like some menu + items or app grid) + + + + ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: gnome-shell-extension-ubuntu-dock + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. [ Test case ] - Look for xterm in gnome-shell activities and add it to favourtes - With the ubuntu-dock showing in the desktop, touch the xterm icon - Only one instance if it should open - Tapping the app icons grid should properly open the g-s overview - Tapping on dock icons when in overview mode should work normally [ Regression potential ] Taps on other gnome-shell buttons could not work poperly (like some menu items or app grid) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/358010 -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. [ Test case ] - Look for xterm in gnome-shell activities and add it to favourtes - With the ubuntu-dock showing in the desktop, touch the xterm icon - Only one instance if it should open - Tapping the app icons grid should properly open the g-s overview - Tapping on dock icons when in overview mode should work normally [ Regression potential ] Taps on other gnome-shell buttons could not work poperly (like some menu items or app grid) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Description changed: + [Impact] Unable to type capital letters using onscreen keyboard: + [Test Case] 1. Launch a program where you can type text (gedit for example). 2. Activate on screen keyboard (by touching the screen, foe example). 3. Notice all the keys on the on screen keyboard display lowercase letters. 4. Begin typing. Lowercase characters are typed into the text area. 5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard. 6. Notice all the keys on the on screen keyboard now display capital letters. 7. Begin typing. 8. A lowercase character will be typed into the text area. This is not expected behavior. Instead, a capital letter should have been typed. (All the keys on the on screen keyboard revert to lower case. This is expected, since the on screen shift key would need to be pressed again in order to attempt to type another capital character). + [Regression Potential] + Please make sure that osk correctly revert to lower case. Also make sure + the physical keyboard correctly works after using the osk. + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: caribou 0.4.21-2 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: GNOME Date: Sun Nov 5 10:57:04 2017 InstallationDate: Installed on 2017-11-03 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark" ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1730211 Title: Unable to type capital letters using onscreen keyboard Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: [Impact] Unable to type capital letters using onscreen keyboard: [Test Case] 1. Launch a program where you can type text (gedit for example). 2. Activate on screen keyboard (by touching the screen, foe example). 3. Notice all the keys on the on screen keyboard display lowercase letters. 4. Begin typing. Lowercase characters are typed into the text area. 5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard. 6. Notice all the keys on the on screen keyboard now display capital letters. 7. Begin typing. 8. A lowercase character will be typed into the text area. This is not expected behavior. Instead, a capital letter should have been typed. (All the keys on the on screen keyboard revert to lower case. This is expected, since the on screen shift key would need to be pressed again in order to attempt to type another capital character). [Regression Potential] Please make sure that osk correctly revert to lower case. Also make sure the physical keyboard correctly works after using the osk. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: caribou 0.4.21-2 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: GNOME Date: Sun Nov 5 10:57:04 2017 InstallationDate: Installed on 2017-11-03 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04
In Xenial, /usr/share/ghostscript/9.5/iccprofiles was a directory. In Bionic, it is a symlink to /usr/share/color/icc/ghostscript. The Bionic package needs to use dpkg-maintscript-helper to ensure the transition is done properly. I will prepare a fix for this. ** Package changed: cups (Ubuntu) => ghostscript (Ubuntu) ** Also affects: ghostscript (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ghostscript (Ubuntu Bionic) Status: New => Confirmed ** Changed in: ghostscript (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: ghostscript (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800328 Title: HP Office Jet Cups reports Filter Failed. Works OK with 16.04 Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Bionic: Confirmed Bug description: After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails to print with the status "Filter Failed". On a 16.04 system printing is OK. Printer: Network HP-Officejet-Pro-8620 No changes were made other than the do-release-upgrade and 'apt dist-upgrade'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 27 23:58:29 2018 Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100 MachineType: System76 Meerkat Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago) dmi.bios.date: 11/22/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3: dmi.product.name: Meerkat dmi.product.version: meer3 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
Thank you for your bug report, that's an upstream issue and known there as https://gitlab.gnome.org/GNOME/gnome-control-center/issues/190 ** Package changed: network-manager (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in gnome-control-center package in Ubuntu: Triaged Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799262] Re: OpenVPN doesn't respect dns servers in settings
Could you give some details on your VPN config and on the DNS server you expect to be used? ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1799262 Title: OpenVPN doesn't respect dns servers in settings Status in network-manager-openvpn package in Ubuntu: New Bug description: Hello! After upgrading to Ubuntu 18.10 OpenVPN doesn't respect dns servers in settings. It trying to resolve internal host with default DNS server except resolving with dns servers from connection settings. On Ubuntu 18.04 all works fine 1) 18.10 2) 1.8.6-1ubuntu1 3) OpenVPN uses DNS servers for resolving from connection settings 4) Resolving used by default DNS server ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-openvpn 1.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:46:17 2018 InstallationDate: Installed on 2018-09-24 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to cosmic on 2018-10-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1799262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/358007 -- 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/1730211 Title: Unable to type capital letters using onscreen keyboard Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: [Impact] Unable to type capital letters using onscreen keyboard: [Test Case] 1. Launch a program where you can type text (gedit for example). 2. Activate on screen keyboard (by touching the screen, foe example). 3. Notice all the keys on the on screen keyboard display lowercase letters. 4. Begin typing. Lowercase characters are typed into the text area. 5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard. 6. Notice all the keys on the on screen keyboard now display capital letters. 7. Begin typing. 8. A lowercase character will be typed into the text area. This is not expected behavior. Instead, a capital letter should have been typed. (All the keys on the on screen keyboard revert to lower case. This is expected, since the on screen shift key would need to be pressed again in order to attempt to type another capital character). [Regression Potential] Please make sure that osk correctly revert to lower case. Also make sure the physical keyboard correctly works after using the osk. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: caribou 0.4.21-2 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: GNOME Date: Sun Nov 5 10:57:04 2017 InstallationDate: Installed on 2017-11-03 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800650] [NEW] gedit highlights indexes of multidimensional arrays as comments in Perl mode
Public bug reported: In gedit's Perl highlight mode, variables of all kinds ($var, %hash, @array etc.) are highlighted in dark green. The same usually works for the last index of an array as well ($#array) but only if the array is one-dimensional. With multidimensional arrays, the proper syntax is more complicated: $#{$array[0]} should give the last index of the first element of an array of arrays. Here gedit however interprets the number sign (#) as the mark of a comment and highlights the rest of the line in blue. The expected behavior would be to highlight $#{$array[0]} in dark green like all other variables. See the attached screenshot. Description:Ubuntu 18.04.1 LTS Release:18.04 gedit: Installed: 3.28.1-1ubuntu1 Candidate: 3.28.1-1ubuntu1 Version table: *** 3.28.1-1ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 12:27:38 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot gedit perl multi-array index.png" https://bugs.launchpad.net/bugs/1800650/+attachment/5207156/+files/Screenshot%20gedit%20perl%20multi-array%20index.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1800650 Title: gedit highlights indexes of multidimensional arrays as comments in Perl mode Status in gedit package in Ubuntu: New Bug description: In gedit's Perl highlight mode, variables of all kinds ($var, %hash, @array etc.) are highlighted in dark green. The same usually works for the last index of an array as well ($#array) but only if the array is one-dimensional. With multidimensional arrays, the proper syntax is more complicated: $#{$array[0]} should give the last index of the first element of an array of arrays. Here gedit however interprets the number sign (#) as the mark of a comment and highlights the rest of the line in blue. The expected behavior would be to highlight $#{$array[0]} in dark green like all other variables. See the attached screenshot. Description: Ubuntu 18.04.1 LTS Release: 18.04 gedit: Installed: 3.28.1-1ubuntu1 Candidate: 3.28.1-1ubuntu1 Version table: *** 3.28.1-1ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 12:27:38 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04
You're right. I can confirm that the runtime related refs are now installed without any issue, however the new code seems to have problems with downgrades. :-( Unfortunately, I am not a good in C so I cannot fix it myself and Joaquim Rocha doesn't work on GNOME Software anymore. Other possible solution to the related refs issue is to switch to the new GNOME Software 3.30.* version in Bionic instead of using an older one. This solution is recommended by GS devs because the new GS has many fixes (not only the Flatpak ones). -- 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/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) using GNOME Software on Ubuntu 18.04, the runtime extensions are not installed. They are installed if you run "flatpak update" from Terminal after the installation. This issue should be already fixed in GNOME Software upstream so I believe that this is a downstream Ubuntu issue. Please, fix this. Steps to Reproduce: 1. Use the latest, fully updated Ubuntu 18.04 image. 2. Install "flatpak" and "gnome-software-plugin-flatpak" packages. 3. Restart the system. 4. Download and add the Flathub repo file: https://dl.flathub.org/repo/flathub.flatpakrepo 5. Search and install the "GNOME Web" Flatpak package using GNOME Software. 6. Run the installed "Web" application. Actual results: GNOME Web is started with the default (Adwaita) theme (and without the correct locale if you use non-English system). Expected results: GNOME Web is started with the correct (Ubuntu) theme (and with the correct locale if you use non-English system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800272] Re: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card
Hello, Attached you will find file. I have reinstalled the drivers since reporting the message, but the sound does not come back and I need to restart it in the terminal. it only helps "alsa force-reload". ** Attachment added: "all.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+attachment/5207164/+files/all.txt -- 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/1800272 Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After update to 18.10 no sound in internal speakers and jackport. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 11:10:22 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (820 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-10-21 (6 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.00 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.3E dmi.chassis.asset.tag: CNU14045VQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.00:bd02/14/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.3E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6460b dmi.product.sku: LG643EA#AKD dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1800272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04
It would be great if some GS dev from Canonical could fix the current patches. -- 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/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) using GNOME Software on Ubuntu 18.04, the runtime extensions are not installed. They are installed if you run "flatpak update" from Terminal after the installation. This issue should be already fixed in GNOME Software upstream so I believe that this is a downstream Ubuntu issue. Please, fix this. Steps to Reproduce: 1. Use the latest, fully updated Ubuntu 18.04 image. 2. Install "flatpak" and "gnome-software-plugin-flatpak" packages. 3. Restart the system. 4. Download and add the Flathub repo file: https://dl.flathub.org/repo/flathub.flatpakrepo 5. Search and install the "GNOME Web" Flatpak package using GNOME Software. 6. Run the installed "Web" application. Actual results: GNOME Web is started with the default (Adwaita) theme (and without the correct locale if you use non-English system). Expected results: GNOME Web is started with the correct (Ubuntu) theme (and with the correct locale if you use non-English system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800587] [NEW] gnome shell crashes, dock visible in lookscreen
You have been subscribed to a public bug: gnome shell sometimes "crashes", especially when system auto locks. The user theme shell extension disappears (standard ui then) and the dock gets partly unresponsive and does not disappears. When the system is locked, the dock is still visible and one can launch programs, which are not visible but still started. Sometimes it seems like two gnome-shell guis are overlapping each other. I am using a gtk+ theme: https://github.com/nivekxyz/afflatus There is no crash file for gnome-shell in /var/crash. My whoopsi ID is: https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918 Description:Ubuntu 18.10 Release:18.10 gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1 Version table: *** 3.30.1-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status This bug might be close to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1799242 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- gnome shell crashes, dock visible in lookscreen https://bugs.launchpad.net/bugs/1800587 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800587] Re: gnome shell crashes, dock visible in lookscreen
** Package changed: apport (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800587 Title: gnome shell crashes, dock visible in lookscreen Status in gnome-shell package in Ubuntu: New Bug description: gnome shell sometimes "crashes", especially when system auto locks. The user theme shell extension disappears (standard ui then) and the dock gets partly unresponsive and does not disappears. When the system is locked, the dock is still visible and one can launch programs, which are not visible but still started. Sometimes it seems like two gnome-shell guis are overlapping each other. I am using a gtk+ theme: https://github.com/nivekxyz/afflatus There is no crash file for gnome-shell in /var/crash. My whoopsi ID is: https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918 Description: Ubuntu 18.10 Release: 18.10 gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1 Version table: *** 3.30.1-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status This bug might be close to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1799242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798470] Re: gnome-software can't handle composite CAB files
I've upgraded on a bionic machine to 3.28.1-0ubuntu4.18.04.5. xdg-open FirmwareUpdateLinux_00.00.07.cab opens a composite CAB file in gnome-software now. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04
Proper Flatpak support is really important to end-users as Flatpak is becoming a standard in cross-distro application distribution. -- 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/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) using GNOME Software on Ubuntu 18.04, the runtime extensions are not installed. They are installed if you run "flatpak update" from Terminal after the installation. This issue should be already fixed in GNOME Software upstream so I believe that this is a downstream Ubuntu issue. Please, fix this. Steps to Reproduce: 1. Use the latest, fully updated Ubuntu 18.04 image. 2. Install "flatpak" and "gnome-software-plugin-flatpak" packages. 3. Restart the system. 4. Download and add the Flathub repo file: https://dl.flathub.org/repo/flathub.flatpakrepo 5. Search and install the "GNOME Web" Flatpak package using GNOME Software. 6. Run the installed "Web" application. Actual results: GNOME Web is started with the default (Adwaita) theme (and without the correct locale if you use non-English system). Expected results: GNOME Web is started with the correct (Ubuntu) theme (and with the correct locale if you use non-English system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278387] Re: Private key generation does not work at all
I have a same problem with version 3.30 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1278387 Title: Private key generation does not work at all Status in seahorse package in Ubuntu: Confirmed Bug description: The current version of seahorse in Ubuntu 14.04 shows an option to generate a "private key". It is neither obvious what kind of key this is nor does the option work at all, leaving fields for key type empty and not offering the possibility to active the "Create" button, leaving this option completely pointless. Additionally, when setting the key size, the value is not limeted by anything other then the size of int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1278387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1571237] Re: incorrect displaying of color state in inkjet by printer Brother MFC-J5720DW
Evidence for mirror wrong setting ** Attachment added: "printer cmoparating reality and system config.png" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1571237/+attachment/5207170/+files/printer%20cmoparating%20reality%20and%20system%20config.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1571237 Title: incorrect displaying of color state in inkjet by printer Brother MFC- J5720DW Status in system-config-printer package in Ubuntu: New Bug description: Hi, It is incorrect displaying of color state of inkjet by printer Brother MFC-J5720DW, through application system-config-printer. It display all 4 color, but in not good order (application have order Black/Yellow/Cyan/Magenta; but printer have order Magenta/Cyan/Yellow/Black) it means that when black color is 0 % in printer, in system-config-printer is displayed that Magenta is 0%. It was at computers with linux mint 17.3/Ubuntu 14.04 amd64 bit --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-07-29 (92 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lpstat: device for Boomaga: boomaga:/ device for BRFAX: usb:/dev/usb/lp0 device for Brother_DCP_L2520DW_series: ipp://BRWC48E8FC5C81A.local:631/ipp/print device for MFCJ5720DW: dnssd://Brother%20MFC-J5720DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c66f7b1 device for PDF: cups-pdf:/ MachineType: Hewlett-Packard HP EliteBook 8570w NonfreeKernelModules: nvidia Package: system-config-printer 1.5.11-1ubuntu2 [origin: Ubuntu] PackageArchitecture: all Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer (w/ options) MFCJ5720DW: Brother MFC-J5720DW CUPS Brother_DCP_L2520DW_series: DCP-L2520DW series Boomaga: Boomaga printer BRFAX: Brother BRMFCFAX for CUPS ProcEnviron: LANGUAGE=sk TERM=xterm PATH=(custom, no user) LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=4f52eb9a-4d4c-46cb-98b3-3af6fa25f32f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: third-party-packages tara Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: Toto nie je oficiálny Linux balík. Prosím, odstráňte všetky balíky tretích strán a skúste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/13/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IAV Ver. F.68 dmi.board.name: 176B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 50.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.68:bd04/13/2018:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8570w dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1571237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work
** Tags removed: rls-cc-incoming -- 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/1798053 Title: [SRU] Click on the back icon in gnome-software doesn't work Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Bug description: [Test Case] 1. Open gnome-software 2. Press Ctrl+F and type "firefox" or any string that will return results 3. Click any result in the list (snap package or deb, already installed or not, it doesn't matter) 4. Observe that a new page is open showing details about the application 5. Close gnome-software 6. Open gnome-software again 7. Observe that the application is open on the last open page (details view about the application) 8. Click the back button (top-left corner) Expected result: the application goes back to the list of search results (or perhaps to the home screen) Current result: nothing happens Please note that the upstream fix reverts a new behaviour and as a result, when opening again gnome-software at step 6, the application opens on the home screen instead of resuming the last open page. This is consistent with how gnome-software behaves in bionic. So after applying the patch, steps 7 and 8 can be folded into one single step: "Observe that the application is open on the home screen". [Regression Potential] Low. This is a cherry-pick of a self-contained trivial upstream commit that is already released in gnome-software 3.30.3 (https://gitlab.gnome.org/GNOME/gnome-software/commit/ca5f8e74b6f9991ae228caa2c698131a54764774). As noted above, it does change the behaviour of re-opening the application after closing it, but it reverts it to the behaviour it had in bionic, so I don't think it should be considered a regression. Re-opening the application after closing it in a number of different situations should be thoroughly exercised to make sure that this doesn't introduce any functional regression. [Original Description] Searched for Chromium, installed Chromium (snap version), clicked Launched and used chromium. Went back to gnome-software and clicked the back button. Nothing happened. Restarted gnome-software and clicked the back button. Nothing happened. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu3 [modified: usr/share/gnome-shell/search-providers/org.gnome.Software-search-provider.ini] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 11:22:16 2018 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu3 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797604] Re: Xserver opengl problems on i5-8259U
Marking as bb-notfixing. This means the bug is not considered a release blocker, but can still be worked on and fixed. ** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1797604 Title: Xserver opengl problems on i5-8259U Status in xf86-video-intel: Unknown Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I have installed 18.04.1 server on Intel NUC NUC8i5BEH with minimal xinit and xserver-xorg-video-intel. But it has 2 major issues: 1. Huge Xorg CPU usage with intel driver...more than 110% on glxgears without vsync (with modesetting driver Xorg has zero CPU usage and very good Opengl performance) 2. on DRI3 glxgears it skip most frames and display one frame every 60-70 frames but reported FPS is doubled than on DRI2 to reproduce a problem install fresh server image of 18.04 and then install minimal xinit+xserver-xorg-video-intel. Put 20-intel.conf to enable intel driver. Run X by startx and then run glxgears. 20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" # Option "DRI" "3" EndSection P.S. Before 18.04 I tried 16.04 with HWE kernel...on stock Xserver and Intel driver it just crash. On latest HWE xserver and HWE Intel driver it works the same as 18.04 because it has the same versions. But with old 1.18 xserver and HWE intel driver it works in DRI2 mode...Xorg CPU usage just 10% instead of 110% on xserver 1.19...The only problem - poor OPENGL performance (glxgears 5400 fps vs 8000 fps on 1.19 xserver) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Oct 12 17:27:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2074] MachineType: Intel(R) Client Systems NUC8i5BEH ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b5cc483d-ce2c-11e8-9739-94c691a2ff22 ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0048.2018.0919.2013 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72692-303 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0048.2018.0919.2013:bd09/19/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i5BEH dmi.product.version: J72747-302 dmi.sys.vendor: Intel(R) Client Systems 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1797604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: evince crashes in FcConfigParseAndLoad Status in fontconfig package in Ubuntu: Incomplete Bug description: I have the following situation persistently on my system (Ubuntu 18.04.1 on Dell Latitude E6500): Evince called with any pdf file crashes immediately with a segmentation fault. From the crash dump, I see that the crash happens in fontconfig's FcConfigParseAndLoad function, i.e. when the system fonts.conf is read. I can reproduce the crash with the following minimal example: #include const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf"; FcConfig* config; int main(){ FcConfigParseAndLoad(config, filename, FcTrue); } The fonts.conf file used here is also absolutely minimal: (Get me right. It first happened with my system fonts.conf, which is not empty. In order to find out whether a specific entry lead to the crash, I deleted entry after entry, ultimately reaching the file above, and always FcConfigParseAndLoad crashes. I have no idea how to go on from here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
I tested totem 3.26.2-1ubuntu2 under Cosmic and the Create screenshot gallery... option works as advertised. Note that the Take screenshot option does not work for me (I suspect that should be a different bug report. The screenshot works as expected under totem 3.18.1-1ubuntu4 under 16.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Committed Status in totem source package in Cosmic: Fix Committed Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800135] Re: libssh-dev is missing cmake find module
Are you sure this is still incorrect in cosmic? It seems to me this is only broken in bionic. Cosmic build log has libssh-dev_0.8.1-1_amd64.deb new debian package, version 2.0. size 217956 bytes: control archive=1172 bytes. 918 bytes,21 lines control 845 bytes,12 lines md5sums Package: libssh-dev Source: libssh Version: 0.8.1-1 Architecture: amd64 Maintainer: Ubuntu Developers Original-Maintainer: Laurent Bigonville Installed-Size: 1064 Depends: libssh-4 (= 0.8.1-1), libssl-dev, zlib1g-dev Suggests: libssh-doc Conflicts: libssh-gcrypt-dev Section: libdevel Priority: optional Homepage: https://www.libssh.org/ Description: tiny C SSH library. Development files (OpenSSL flavor) The ssh library was designed to be used by programmers needing a working SSH implementation by the mean of a library. The complete control of the client is made by the programmer. With libssh, you can remotely execute programs, transfer files, use a secure and transparent tunnel for your remote programs. With its SFTP implementation, you can play with remote files easily. . This package contains development files to build the OpenSSL flavor. drwxr-xr-x root/root 0 2018-08-14 07:43 ./ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/include/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/include/libssh/ -rw-r--r-- root/root 37596 2018-08-09 09:18 ./usr/include/libssh/callbacks.h -rw-r--r-- root/root 6867 2016-03-03 19:05 ./usr/include/libssh/legacy.h -rw-r--r-- root/root 29642 2018-08-13 20:21 ./usr/include/libssh/libssh.h -rw-r--r-- root/root 20102 2018-08-10 11:23 ./usr/include/libssh/libsshpp.hpp -rw-r--r-- root/root 12393 2018-08-09 09:18 ./usr/include/libssh/server.h -rw-r--r-- root/root 31787 2018-08-10 09:06 ./usr/include/libssh/sftp.h -rw-r--r-- root/root 2735 2018-08-10 11:23 ./usr/include/libssh/ssh2.h drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/ -rw-r--r-- root/root 377 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config-version.cmake -rw-r--r-- root/root 493 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config.cmake -rw-r--r-- root/root906476 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/libssh.a lrwxrwxrwx root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/libssh.so -> libssh.so.4 drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/pkgconfig/ -rw-r--r-- root/root 121 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/pkgconfig/libssh.pc drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/doc/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/doc/libssh-dev/ lrwxrwxrwx root/root 0 2018-08-14 07:43 ./usr/share/doc/libssh-dev/changelog.Debian.gz -> ../libssh-4/changelog.Debian.gz -rw-r--r-- root/root 13682 2018-08-14 07:43 ./usr/share/doc/libssh-dev/copyright -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1800135 Title: libssh-dev is missing cmake find module Status in libssh package in Ubuntu: Confirmed Bug description: libssh-dev: 0.8.0~20170825.94fa1e38-1ubuntu0.1 There is no libssh-config.cmake packaged in libssh-dev package leading to find_package calls for LibSSH failing. The build output [1] lists a /<>/debian/tmp- gcrypt/usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config.cmake file was installed, however. [1] https://launchpadlibrarian.net/356107564/buildlog_ubuntu-bionic- amd64.libssh_0.8.0~20170825.94fa1e38-1build1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1800135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800135] Re: libssh-dev is missing cmake find module
On 30/10/2018 15:42, Harald Sitter wrote: > Are you sure this is still incorrect in cosmic? It seems to me this is > only broken in bionic. Seems .cmake are installed in both -dev packages in cosmic, with a conflicts to prevent both being installed at the same time. I would guess I was looking at the wrong build log or file list in a tab when it looked like this was not the case. ** Also affects: libssh (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libssh (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1800135 Title: libssh-dev is missing cmake find module Status in libssh package in Ubuntu: Confirmed Status in libssh source package in Bionic: Confirmed Bug description: libssh-dev: 0.8.0~20170825.94fa1e38-1ubuntu0.1 There is no libssh-config.cmake packaged in libssh-dev package leading to find_package calls for LibSSH failing. The build output [1] lists a /<>/debian/tmp- gcrypt/usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config.cmake file was installed, however. [1] https://launchpadlibrarian.net/356107564/buildlog_ubuntu-bionic- amd64.libssh_0.8.0~20170825.94fa1e38-1build1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1800135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Thanks for the update, Daniel! I am eagerly waiting. Switched of gnome- shell and would love to come back. -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 --- I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic There's similar bug that should be related to this one https://bugs.launchpad.net/ubuntu/+source/gn
[Desktop-packages] [Bug 1800135] Re: libssh-dev is missing cmake find module
** Changed in: libssh (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1800135 Title: libssh-dev is missing cmake find module Status in libssh package in Ubuntu: Fix Released Status in libssh source package in Bionic: Confirmed Bug description: libssh-dev: 0.8.0~20170825.94fa1e38-1ubuntu0.1 There is no libssh-config.cmake packaged in libssh-dev package leading to find_package calls for LibSSH failing. The build output [1] lists a /<>/debian/tmp- gcrypt/usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config.cmake file was installed, however. [1] https://launchpadlibrarian.net/356107564/buildlog_ubuntu-bionic- amd64.libssh_0.8.0~20170825.94fa1e38-1build1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1800135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800690] [NEW] Non-adjacent Displays fails with uninformative error
Public bug reported: System: Ubuntu Cosmic Package: gnome-control-center: Installed: 1:3.30.1-1ubuntu2 Candidate: 1:3.30.1-1ubuntu2 Version table: *** 1:3.30.1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status Expected: an error message about non-adjacent displays when non-adjacent displays were preventing a resolution change What happened: a generic error message about "hardware limitations". When trying to change the resolution of my displays, when multiple displays were connected, it failed with the error "Changes Cannot Be Applied: this could be due to hardware limitations." However, if I run gnome-control-center from the command line, I get the following, much more helpful output: (gnome-control-center:7405): display-cc-panel-WARNING **: 10:15:42.267: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent Indeed, moving the displays to be adjacent within the settings app fixed the problem and allowed the resolution to be changed. The GUI should inform users when non-adjacent displays are preventing a settings change, instead of failing with an uninformative message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 10:18:43 2018 InstallationDate: Installed on 2018-10-25 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1800690 Title: Non-adjacent Displays fails with uninformative error Status in gnome-control-center package in Ubuntu: New Bug description: System: Ubuntu Cosmic Package: gnome-control-center: Installed: 1:3.30.1-1ubuntu2 Candidate: 1:3.30.1-1ubuntu2 Version table: *** 1:3.30.1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status Expected: an error message about non-adjacent displays when non-adjacent displays were preventing a resolution change What happened: a generic error message about "hardware limitations". When trying to change the resolution of my displays, when multiple displays were connected, it failed with the error "Changes Cannot Be Applied: this could be due to hardware limitations." However, if I run gnome-control-center from the command line, I get the following, much more helpful output: (gnome-control-center:7405): display-cc-panel-WARNING **: 10:15:42.267: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent Indeed, moving the displays to be adjacent within the settings app fixed the problem and allowed the resolution to be changed. The GUI should inform users when non-adjacent displays are preventing a settings change, instead of failing with an uninformative message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 10:18:43 2018 InstallationDate: Installed on 2018-10-25 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1800690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: verification-needed-cosmic ** Tags added: verification-failed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Added comment to the other bug #1740894: Same issue on the Dell as we had here, the new update to 2.23-1 from -proposed breaks disabling the airplane mode on the Dell XPS 15 9575. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04
This bug was fixed in the package ghostscript - 9.25~dfsg+1-0ubuntu0.18.04.2 --- ghostscript (9.25~dfsg+1-0ubuntu0.18.04.2) bionic-security; urgency=medium * SECURITY UPDATE: Multiple security issues - debian/patches/0218*.patch: multiple cherry-picked upstream commits to fix security issues. Thanks to Jonas Smedegaard for cherry-picking these for Debian's 9.25~dfsg-3 package. - debian/libgs9.symbols: added new symbol. - CVE-2018-17961 - CVE-2018-18073 - CVE-2018-18284 * Fix LeadingEdge regression introduced in 9.22. (LP: #1800062) - debian/patches/lp1800062.patch: fix cups get/put_params LeadingEdge logic in cups/gdevcups.c. * Fix iccprofiles directory to symlink issue (LP: #1800328) - debian/libgs__VER__-common.maintscript.in: make sure directory is correctly transitioned to a symlink. -- Marc Deslauriers Tue, 30 Oct 2018 09:00:57 -0400 ** Changed in: ghostscript (Ubuntu Bionic) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-17961 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18073 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18284 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800328 Title: HP Office Jet Cups reports Filter Failed. Works OK with 16.04 Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Bionic: Fix Released Bug description: After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails to print with the status "Filter Failed". On a 16.04 system printing is OK. Printer: Network HP-Officejet-Pro-8620 No changes were made other than the do-release-upgrade and 'apt dist-upgrade'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 27 23:58:29 2018 Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100 MachineType: System76 Meerkat Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago) dmi.bios.date: 11/22/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3: dmi.product.name: Meerkat dmi.product.version: meer3 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800062] Re: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops
This bug was fixed in the package ghostscript - 9.25~dfsg+1-0ubuntu0.18.04.2 --- ghostscript (9.25~dfsg+1-0ubuntu0.18.04.2) bionic-security; urgency=medium * SECURITY UPDATE: Multiple security issues - debian/patches/0218*.patch: multiple cherry-picked upstream commits to fix security issues. Thanks to Jonas Smedegaard for cherry-picking these for Debian's 9.25~dfsg-3 package. - debian/libgs9.symbols: added new symbol. - CVE-2018-17961 - CVE-2018-18073 - CVE-2018-18284 * Fix LeadingEdge regression introduced in 9.22. (LP: #1800062) - debian/patches/lp1800062.patch: fix cups get/put_params LeadingEdge logic in cups/gdevcups.c. * Fix iccprofiles directory to symlink issue (LP: #1800328) - debian/libgs__VER__-common.maintscript.in: make sure directory is correctly transitioned to a symlink. -- Marc Deslauriers Tue, 30 Oct 2018 09:00:57 -0400 ** Changed in: ghostscript (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800062 Title: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Bug description: PDF file data fail to rendering to raster data. We were reported a bug from our printer users: I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay. But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 9.25, I print the same file with the same driver there is an error reports: "Filter Error" I figure out that all the papersize with define "LeadingEdge" can't print success after update. (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay). I view the "CUPS Error Log",there is an error reports when print job fails: "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_ Unrecoverable error: undefined in .putdeviceprops" Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem. -- ghostscript had confirm that this a bug of ghostscript 9.22(and the later version). Below information is the correspondence of ghostscript: https://bugs.ghostscript.com/show_bug.cgi?id=700023 --- Our printer driver users(also users of Ubuntu 16.04) can't do their normal print jobs. So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1800062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800062] Re: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops
This bug was fixed in the package ghostscript - 9.25~dfsg+1-0ubuntu0.14.04.2 --- ghostscript (9.25~dfsg+1-0ubuntu0.14.04.2) trusty-security; urgency=medium * SECURITY UPDATE: Multiple security issues - debian/patches/0218*.patch: multiple cherry-picked upstream commits to fix security issues. Thanks to Jonas Smedegaard for cherry-picking these for Debian's 9.25~dfsg-3 package. - debian/symbols.common: added new symbol. - CVE-2018-17961 - CVE-2018-18073 - CVE-2018-18284 * Fix LeadingEdge regression introduced in 9.22. (LP: #1800062) - debian/patches/lp1800062.patch: fix cups get/put_params LeadingEdge logic in cups/gdevcups.c. -- Marc Deslauriers Tue, 30 Oct 2018 09:05:40 -0400 ** Changed in: ghostscript (Ubuntu Trusty) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-17961 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18073 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18284 ** Changed in: ghostscript (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800062 Title: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Bug description: PDF file data fail to rendering to raster data. We were reported a bug from our printer users: I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay. But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 9.25, I print the same file with the same driver there is an error reports: "Filter Error" I figure out that all the papersize with define "LeadingEdge" can't print success after update. (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay). I view the "CUPS Error Log",there is an error reports when print job fails: "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_ Unrecoverable error: undefined in .putdeviceprops" Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem. -- ghostscript had confirm that this a bug of ghostscript 9.22(and the later version). Below information is the correspondence of ghostscript: https://bugs.ghostscript.com/show_bug.cgi?id=700023 --- Our printer driver users(also users of Ubuntu 16.04) can't do their normal print jobs. So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1800062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800062] Re: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops
This bug was fixed in the package ghostscript - 9.25~dfsg+1-0ubuntu0.16.04.2 --- ghostscript (9.25~dfsg+1-0ubuntu0.16.04.2) xenial-security; urgency=medium * SECURITY UPDATE: Multiple security issues - debian/patches/0218*.patch: multiple cherry-picked upstream commits to fix security issues. Thanks to Jonas Smedegaard for cherry-picking these for Debian's 9.25~dfsg-3 package. - debian/symbols.common: added new symbol. - CVE-2018-17961 - CVE-2018-18073 - CVE-2018-18284 * Fix LeadingEdge regression introduced in 9.22. (LP: #1800062) - debian/patches/lp1800062.patch: fix cups get/put_params LeadingEdge logic in cups/gdevcups.c. -- Marc Deslauriers Tue, 30 Oct 2018 09:04:39 -0400 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800062 Title: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Bug description: PDF file data fail to rendering to raster data. We were reported a bug from our printer users: I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay. But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 9.25, I print the same file with the same driver there is an error reports: "Filter Error" I figure out that all the papersize with define "LeadingEdge" can't print success after update. (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay). I view the "CUPS Error Log",there is an error reports when print job fails: "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_ Unrecoverable error: undefined in .putdeviceprops" Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem. -- ghostscript had confirm that this a bug of ghostscript 9.22(and the later version). Below information is the correspondence of ghostscript: https://bugs.ghostscript.com/show_bug.cgi?id=700023 --- Our printer driver users(also users of Ubuntu 16.04) can't do their normal print jobs. So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1800062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
Some feedback for Cosmic: FWIW, I can confirm that the update did NOT break the keyboard backlight key on Dell XPS 15 9575, where it had already worked flawlessly out-of- the-box with Cosmic since installation in early September (contrary to the bug description above stating that "keyboard backlight control keys don't work in cosmic") At the time also submitted the similar bug #1791372, "Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image". I can test this update on the Asus as well but cannot report result before Sunday, Oct 4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Status in upower source package in Cosmic: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800062] Re: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops
This bug was fixed in the package ghostscript - 9.25~dfsg+1-0ubuntu1.1 --- ghostscript (9.25~dfsg+1-0ubuntu1.1) cosmic-security; urgency=medium * SECURITY UPDATE: Multiple security issues - debian/patches/0218*.patch: multiple cherry-picked upstream commits to fix security issues. Thanks to Jonas Smedegaard for cherry-picking these for Debian's 9.25~dfsg-3 package. - debian/libgs9.symbols: added new symbol. - CVE-2018-17961 - CVE-2018-18073 - CVE-2018-18284 * Fix LeadingEdge regression introduced in 9.22. (LP: #1800062) - debian/patches/lp1800062.patch: fix cups get/put_params LeadingEdge logic in cups/gdevcups.c. -- Marc Deslauriers Tue, 30 Oct 2018 08:38:06 -0400 ** Changed in: ghostscript (Ubuntu Cosmic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800062 Title: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Bug description: PDF file data fail to rendering to raster data. We were reported a bug from our printer users: I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay. But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 9.25, I print the same file with the same driver there is an error reports: "Filter Error" I figure out that all the papersize with define "LeadingEdge" can't print success after update. (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay). I view the "CUPS Error Log",there is an error reports when print job fails: "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_ Unrecoverable error: undefined in .putdeviceprops" Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem. -- ghostscript had confirm that this a bug of ghostscript 9.22(and the later version). Below information is the correspondence of ghostscript: https://bugs.ghostscript.com/show_bug.cgi?id=700023 --- Our printer driver users(also users of Ubuntu 16.04) can't do their normal print jobs. So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1800062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
This ONLY happens on Ubuntu 18.10, no issue in 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
Fix verified in version 0.99.8-2ubuntu0.1 on a MacBook Air 11" running Kubuntu cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Status in upower source package in Cosmic: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799851] Re: Software Boutique window suddenly shows Welcome window and looses all the apps I queued to install
ok. Lets try this. start software boutique from the terminal and give us all the output when trying to replicate the problem. (open terminal and type ubuntu-mate-welcome --boutique) -- 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/1799851 Title: Software Boutique window suddenly shows Welcome window and looses all the apps I queued to install Status in gnome-software package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Incomplete Bug description: I was selecting apps to install in the Software Boutique, then suddenly the Boutique Window displayed the welcome window and lost all the apps I queued for installation. Ubuntu 18.04.1 LTS (just reinstalled when Ubuntu MATE 18.10 went into total meltdown). AMD 64-bit prosessor Menu->Administration->Software Boutique I had actually hoped to install the same software I had installed when I first installed 18.04. All work lost. The code quality is definitely going down hill fast. (even ubuntu-bug -w gets an error message robert@A88XM-A:~/Desktop$ ubuntu-bug -w Gtk-Message: 20:41:01.726: GtkDialog mapped without a transient parent. This is discouraged.). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3.6-minimal 3.6.6-1~18.04 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 24 20:41:06 2018 ExecutablePath: /usr/bin/python3.6 InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: python3.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800587] Re: gnome shell crashes, dock visible in lookscreen
** Description changed: gnome shell sometimes "crashes", especially when system auto locks. The user theme shell extension disappears (standard ui then) and the dock - gets partly unresponsive and does not disappears. When the system is + gets partly unresponsive and does not disappear. When the system is locked, the dock is still visible and one can launch programs, which are not visible but still started. Sometimes it seems like two gnome-shell guis are overlapping each other. I am using a gtk+ theme: https://github.com/nivekxyz/afflatus There is no crash file for gnome-shell in /var/crash. My whoopsi ID is: https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918 Description: Ubuntu 18.10 Release: 18.10 gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1 Version table: *** 3.30.1-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status This bug might be close to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1799242 -- 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/1800587 Title: gnome shell crashes, dock visible in lookscreen Status in gnome-shell package in Ubuntu: New Bug description: gnome shell sometimes "crashes", especially when system auto locks. The user theme shell extension disappears (standard ui then) and the dock gets partly unresponsive and does not disappear. When the system is locked, the dock is still visible and one can launch programs, which are not visible but still started. Sometimes it seems like two gnome-shell guis are overlapping each other. I am using a gtk+ theme: https://github.com/nivekxyz/afflatus There is no crash file for gnome-shell in /var/crash. My whoopsi ID is: https://errors.ubuntu.com/user/4912803dbfec31e449bfee329a6e5edad140c781b2d05cc329cafbde52ad0ff8692fa6b3bb3c909d322e12ecba40cd35b2fcc024a3d6c5ecf6895762b05ba918 Description: Ubuntu 18.10 Release: 18.10 gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1 Version table: *** 3.30.1-2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status This bug might be close to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1799242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796397] Re: DuckDuckGo search icon is blurry, low resolution
@osomon Since Quantum, FF has an icon in the source tree - https://hg.mozilla.org/mozilla- central/file/default/browser/components/newtab/data/content/tippytop/images /duckduckgo-...@2x.png -- 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/1796397 Title: DuckDuckGo search icon is blurry, low resolution Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 62.0+build2-0ubuntu0.18.04.5 amd64 To reproduce: - Set search engine to DDG - Go to the new tab page. The DDG search icon is very low resolution and looks like it hasn't been updated with the new logo. Expected: Use the icon built into Firefox ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0+build2-0ubuntu0.18.04.5 ProcVersionSignature: User Name 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1610 F pulseaudio /dev/snd/controlC0: ubuntu 1610 F pulseaudio BuildID: 20180913170256 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 15:46:16 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-12 (23 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.224 metric 600 MostRecentCrashID: bp-5252eef0-71dd-4e49-8315-64d660180929 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=62.0/20180913170256 (In use) Profile1 - LastVersion=62.0/20180913170346 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-5252eef0-71dd-4e49-8315-64d660180929 bp-57477e57-d8dd-4ea9-ba66-270d80180929 bp-821e4afc-cb3c-4fe2-a7ba-586440180929 bp-8b4ffe0f-54ef-4969-b8fa-7d6bd0180929 UpgradeStatus: Upgraded to bionic on 2018-09-28 (6 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
A few weeks ago I submitted the similar Bug #1791367 for airplane mode key not working on Asus ZenBook Flip UX561UD. We did some tests updating xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1 where it had worked out-of-the-box with Cosmic and xkb-data 2.23. Now tested the update to 2.23.1 from -proposed and am seeing the same issue on the Dell as in #1791367: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. I can test the Asus as well in a few days, but based on previous results I expect that it will work there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
Thanks for testing, and yes the "take screenshot" not working is another bug, can you open a new report? ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Committed Status in totem source package in Cosmic: Fix Committed Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800715] [NEW] Prompt for credential when it shouldn't
Public bug reported: * Impact Devices should be approved without password prompting for logged in admin users but they are not today because the code looks a 'wheel' as being the admin group. * Test case - log into a Ubuntu/GNOME session with an admin user - connect an USB-C device the device should be accepted without prompting (the result can be checked with the boltctl command or in the thunderbolt g-c-c section) - do the same test with a non admin user, it should be prompted for a password * Regression potentiel Check that device auth works for admin and non admin users ** Affects: bolt (Ubuntu) Importance: Low Status: Fix Released ** Changed in: bolt (Ubuntu) Importance: Undecided => Low ** Changed in: bolt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1800715 Title: Prompt for credential when it shouldn't Status in bolt package in Ubuntu: Fix Released Bug description: * Impact Devices should be approved without password prompting for logged in admin users but they are not today because the code looks a 'wheel' as being the admin group. * Test case - log into a Ubuntu/GNOME session with an admin user - connect an USB-C device the device should be accepted without prompting (the result can be checked with the boltctl command or in the thunderbolt g-c-c section) - do the same test with a non admin user, it should be prompted for a password * Regression potentiel Check that device auth works for admin and non admin users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1800715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Mario: Yeah, history seems to repeat itself. Personally I think it would help if you could file a bug specifically about the Dell issue, based on the proposed fix of xkb-data. The xkb- data fix is probably a step in the right direction, even if it triggers that regression. What do you think? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799339] Re: GeoClue times out on start
** Description changed: + * Impact + + On some configs registration to the geoclue service might fail because + the agent is started too late/after the registration timeout + + * Test case + + - log into an Ubuntu/GNOME session and check that the geolocation + feature is working (used to adjust the timezone for example) + + or from the original report + - log into xfce with redshift and check if it's working + + * Regression potential + + The change is only to increase a timeout delay + + --- + Due to an upstream bug (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue times out upon startup and certain applications (such as Redshift) do not function as intended. This has already been fixed upstream (version 2.5.0) and that version is available in Debian. Please pull the latest Debian version to fix this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1799339 Title: GeoClue times out on start Status in geoclue-2.0 package in Ubuntu: Triaged Status in geoclue-2.0 package in Debian: Unknown Bug description: * Impact On some configs registration to the geoclue service might fail because the agent is started too late/after the registration timeout * Test case - log into an Ubuntu/GNOME session and check that the geolocation feature is working (used to adjust the timezone for example) or from the original report - log into xfce with redshift and check if it's working * Regression potential The change is only to increase a timeout delay --- Due to an upstream bug (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue times out upon startup and certain applications (such as Redshift) do not function as intended. This has already been fixed upstream (version 2.5.0) and that version is available in Debian. Please pull the latest Debian version to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1799339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800727] [NEW] [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
Public bug reported: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed Status in xkeyboard-config package in Ubuntu: New Bug description: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002
[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)
** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: Confirmed => In Progress ** Changed in: evince (Ubuntu) Assignee: Jamie Strandboge (jdstrand) => Sebastien Bacher (seb128) ** Description changed: + * Impact + + Nautilus fails to generate previews for pdf files + + * Test case + + Download/copy a pdf, open the directory in nautilus, a preview image + should be displayed + + * Regression potential + + Check that there are no other apparmor denials and the thumbnailer works + + + - + While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) -- 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/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: In Progress Status in evince package in Debian: Unknown Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.1
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Hi All, any progress here ? Thanks -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 --- I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic There's similar bug that should be related to this one https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix didn't work for me. --- ApportV
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Bug description: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Gunnar: Sure, happy to sacrifice my airport key :) New bug #1800727 for the XPS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The correct command should be: sudo apt install --reinstall pcscd Use cut-and-paste to be sure to use the correct command and send back the correct results. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1700104 Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pcsc-lite package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: pcscd 1.8.10-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 AptOrdering: pcscd: Install pcscd: Configure Architecture: amd64 Date: Fri Jun 23 12:21:31 2017 DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-28 (177 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: pcsc-lite Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)
The filename changed when starting to use bubblewrap, the gnome-desktop corresponding code is https://gitlab.gnome.org/GNOME/gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-script.c#L730 -- 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/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: In Progress Status in evince package in Debian: Unknown Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800550] Re: Xorg freeze
Hi, I went through steps 1 through 3, but even after applying the workaround from 994921 (commenting out the line of code), rebooting, and replicating the bug no .crash file was generated. I was lucky enough to have the screen stay uncorrupted during the lag phase of the bug and I already had the terminal open on screen for use when the mouse stopped responding. I was able to run top and there was one process that was consistently at between 40 and 60% cpu usage: kworker/u8:4-events_unbound . I have no idea what that is but everything else on the system was at 0.3% or less, including xorg. -- 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/1800550 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Both during and after installation (meaning while running the USB iso and booting from HDD after) ubuntu will rapidly become unresponsive and eventually hang when my 4k monitor is plugged in. I have 2 monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly if I only use the 1920 monitor (this is where I am working from right now) but the moment the other monitor is plugged in I get problems. When I cold boot into the system from the small 1920x1080 monitor and then plug in the 4k monitor, the screen on my smaller monitor will glitch before returning to normal a few seconds later, while the 4k monitor never displays an image. The OS begins to bog down, the mouse begins to lag and become less responsive. If I open the display manager I can see that ubuntu has properly detected the 4k monitor and has the correct default settings (resolution, refresh rate, etc.) but attempting to make any changes will result in an immediate crash/hang upon pressing the "apply" button. If I cold boot ubuntu with only the 4k monitor plugged in, I see purple splash screen and ubuntu logo screens (at the correct resolutions) but the monitor output stops and I see only a black screen before the login screen is reached. If I cold boot with both monitors plugged in I see the splash screen and logo, there is a brief moment where the small monitor glitches, and then I see only the magenta backdrop of the login screen but there are no UI elements, and This is only seen on the small monitor; the 4k monitor has once again lost input and turned black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 17:32:16 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518] InstallationDate: Installed on 2018-10-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI 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.18.0-10-generic root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: T
[Desktop-packages] [Bug 1800550] Re: Xorg freeze
I ran perf during the bug to see if I could find out where the high CPU usage is coming from since it isn't leaving a .crash file. I sampled for 10 seconds starting immediately after plugging in the 4k monitor. By PID the report looks like: Samples: 47K of event 'cycles:ppp', Event count (approx.): 43897790507 Children Self Pid:Command + 34.78%34.78% 1763:Xorg + 30.11%30.11%0:swapper + 12.03%12.03% 139:kworker/u8:2-ev + 11.98%11.98% 202:kworker/u8:4-fl +4.91% 4.91% 415:kworker/1:2-eve 2.51% 2.51% 1943:gnome-shell 1.16% 1.16% 2183:nautilus-deskto 0.73% 0.73% 2659:Web Content So xorg and kernel calls are making up 63.7% with just 4.4% as noise and 30.11% idle. Sorting by symbol: Samples: 47K of event 'cycles:ppp', Event count (approx.): 43897790507 Children Self Symbol - 47.40%47.35% [k] ioread32 - 23.83% ret_from_fork kthread worker_thread - process_one_work + 20.26% nv50_disp_atomic_commit_work + 3.55% nvif_notify_work + 9.32% 0x5593da5de690 + 7.36% 0 + 6.72% 0x5593da5dd3b0 It looks like ioread32 is getting called a lot by nouveau. -- 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/1800550 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Both during and after installation (meaning while running the USB iso and booting from HDD after) ubuntu will rapidly become unresponsive and eventually hang when my 4k monitor is plugged in. I have 2 monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly if I only use the 1920 monitor (this is where I am working from right now) but the moment the other monitor is plugged in I get problems. When I cold boot into the system from the small 1920x1080 monitor and then plug in the 4k monitor, the screen on my smaller monitor will glitch before returning to normal a few seconds later, while the 4k monitor never displays an image. The OS begins to bog down, the mouse begins to lag and become less responsive. If I open the display manager I can see that ubuntu has properly detected the 4k monitor and has the correct default settings (resolution, refresh rate, etc.) but attempting to make any changes will result in an immediate crash/hang upon pressing the "apply" button. If I cold boot ubuntu with only the 4k monitor plugged in, I see purple splash screen and ubuntu logo screens (at the correct resolutions) but the monitor output stops and I see only a black screen before the login screen is reached. If I cold boot with both monitors plugged in I see the splash screen and logo, there is a brief moment where the small monitor glitches, and then I see only the magenta backdrop of the login screen but there are no UI elements, and This is only seen on the small monitor; the 4k monitor has once again lost input and turned black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission deni
[Desktop-packages] [Bug 1800550] Re: Xorg freeze
NVIDIA drivers installed through the "Additional Drivers" section in the Software & Updates program work fine. I can use my monitor now, although booting takes significantly longer now than before. -- 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/1800550 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Both during and after installation (meaning while running the USB iso and booting from HDD after) ubuntu will rapidly become unresponsive and eventually hang when my 4k monitor is plugged in. I have 2 monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly if I only use the 1920 monitor (this is where I am working from right now) but the moment the other monitor is plugged in I get problems. When I cold boot into the system from the small 1920x1080 monitor and then plug in the 4k monitor, the screen on my smaller monitor will glitch before returning to normal a few seconds later, while the 4k monitor never displays an image. The OS begins to bog down, the mouse begins to lag and become less responsive. If I open the display manager I can see that ubuntu has properly detected the 4k monitor and has the correct default settings (resolution, refresh rate, etc.) but attempting to make any changes will result in an immediate crash/hang upon pressing the "apply" button. If I cold boot ubuntu with only the 4k monitor plugged in, I see purple splash screen and ubuntu logo screens (at the correct resolutions) but the monitor output stops and I see only a black screen before the login screen is reached. If I cold boot with both monitors plugged in I see the splash screen and logo, there is a brief moment where the small monitor glitches, and then I see only the magenta backdrop of the login screen but there are no UI elements, and This is only seen on the small monitor; the 4k monitor has once again lost input and turned black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 17:32:16 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518] InstallationDate: Installed on 2018-10-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI 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.18.0-10-generic root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-vide
[Desktop-packages] [Bug 1800743] [NEW] /usr/bin/gnome-screensaver:11:settings_backend_path_changed:g_settings_backend_invoke_closure:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-8ubuntu3, the problem page at https://errors.ubuntu.com/problem/639d17b97c1a4674be2b62f464eeb8ff3b082d88 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-screensaver (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-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1800743 Title: /usr/bin/gnome- screensaver:11:settings_backend_path_changed:g_settings_backend_invoke_closure:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in gnome-screensaver package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-8ubuntu3, the problem page at https://errors.ubuntu.com/problem/639d17b97c1a4674be2b62f464eeb8ff3b082d88 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-screensaver/+bug/1800743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800744] [NEW] Suspend/resume stopped working after 0.8.8.1 package installed, reverting to 0.8.8 solved my problem.
Public bug reported: Suspend/resume stopped working after 0.8.8.1 package installed, Every time I closed and reopen the laptop lid the system rebooted. Reverting to package version 0.8.8 solved my problem. I have a Dell XPS 15 9550. Kernel info below. $ uname -a Linux rafxps15 4.18.13-041813-generic #201810100332 SMP Wed Oct 10 07:34:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy nvidia-prime nvidia-prime: Installed: 0.8.8 Candidate: 0.8.8.1 Version table: 0.8.8.1 500 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages *** 0.8.8 500 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status rafael@rafxps15:~$ ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Description changed: - Suspend/resume stopped working after 0.8.8.1 package installed, - reverting to 0.8.8 solved my problem. + Suspend/resume stopped working after 0.8.8.1 package installed, + Every time I closed and reopen the laptop lid the system rebooted. + + Reverting to package version 0.8.8 solved my problem. + I have a Dell XPS 15 9550. Kernel info below. $ uname -a Linux rafxps15 4.18.13-041813-generic #201810100332 SMP Wed Oct 10 07:34:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy nvidia-prime nvidia-prime: - Installed: 0.8.8 - Candidate: 0.8.8.1 - Version table: - 0.8.8.1 500 - 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - *** 0.8.8 500 - 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 0.8.8 + Candidate: 0.8.8.1 + Version table: + 0.8.8.1 500 + 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + *** 0.8.8 500 + 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages + 100 /var/lib/dpkg/status rafael@rafxps15:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800744 Title: Suspend/resume stopped working after 0.8.8.1 package installed, reverting to 0.8.8 solved my problem. Status in nvidia-prime package in Ubuntu: New Bug description: Suspend/resume stopped working after 0.8.8.1 package installed, Every time I closed and reopen the laptop lid the system rebooted. Reverting to package version 0.8.8 solved my problem. I have a Dell XPS 15 9550. Kernel info below. $ uname -a Linux rafxps15 4.18.13-041813-generic #201810100332 SMP Wed Oct 10 07:34:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy nvidia-prime nvidia-prime: Installed: 0.8.8 Candidate: 0.8.8.1 Version table: 0.8.8.1 500 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages *** 0.8.8 500 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status rafael@rafxps15:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1800744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Oh so it seems that Ubuntu 18.10 gdm and desktop defaults to Wayland, that has probably something to do with GDM and the wayland session... I defaulted GDM and Gnome to X... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable
*** This bug is a duplicate of bug 1767648 *** https://bugs.launchpad.net/bugs/1767648 Have the same problem. -- 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/1769299 Title: universal access zoom unusable Status in gnome-shell package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Filed by mark on behalf of low vision user Ken. Ken is able to read 56 point type without magnification at normal reading distance and can barely read the universal access "large text" from a distance of about 2.5 inches from a 26inch monitor at 1360x768. So he really needs magnification and a lot more than the 2x default I used here for testing. We do not live in the same town so providing additional details would be slow. Turned on zoom from the universal access button on top panel. Default settings were used including Zoom = 2.0, screen part = full Several areas are corrupted. These zoom and scroll separately from the rest of the screen and in a way that severely impairs use as portions may not ever be visible. Portions of these subwindows cannot be used because you have to move the mouse off them to be able see them so you can either see or click but not both. These areas are: - The top panel - The left panel (launcher) (intermittently) - pull down menus, particularly the universal access pull down from the top panel Also, the zoom randomly every couple seconds. jumps to a different position without the user's consent. This appeared to be because text was printed by a program running in the terminal window (long apt-get install) but continued to happen even when that window was minimized and even when that program stopped printing. These problems persisted with all the other zoom modes. One mode, however, created new bugs. With "magnifier extends outside of screen", you lose the ability to see the top and left panels at all; you can pan over where they would be but they are not drawn. Can't open the pulldown menu since there is no icon, so who knows how it would be rendered. These bugs made it very difficult to get screenshots, especially with the defective screenshot program gnome-screenshot which ships with system. Also, the bug-reporting program did not permitted attaching additional screenshots once spectacle was installed. Ubuntu 18.04, fresh install, only a few added packages (ham radio related, chrome). Not using wayland, though a wayland session runs concurrently with X11 even though no one has logged in with wayland. Another problem in making the bug report is the irresponsible practice of failing to identify the software being used. The accessability man in circle menu does not have a heading to tell you what program is run for the accessability menu or any of the functions thus invoked. Nor does the settings. And there is no tooltip, popup, or about menu item to convey this information to the user. And running a diff on ps doesn't show any new processes started when zoom is turned on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 5 00:04:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1163] InstallationDate: Installed on 2018-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 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.15.0-20-generic root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: lib
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Oh actually no I don't know...It's really strange and frustrating when this happens, because I was able to reproduce the problem on an Ubuntu 18.04 based distro using GDM as display manager... A way to make it working is to run "vulkaninfo" as sudo once, it works, then also without sudo is back to work again once you reboot... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800749] [NEW] Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game)
Public bug reported: When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are "skips" in the animation of the rotating cubes. Upon further "evaluation", I noticed the system mouse pointer "popping up" briefly at the moment of the glitch(near the crosshair) about once a second. When not in fullscreen, the animation is smooth(no visible skips/glitches) and I don't see the system mouse pointer "popping up" every second. It works fine in fullscreen mode in Ubuntu 18.04. To recreate/observe the problem: 0. Boot into Ubuntu 18.10 1. Install sauerbraten 2. Start sauerbraten 3. Set sauerbraten to fullscreen mode(sauerbraten->options..->display->fullscreen) 4. Start a game(I like sauerbraten->bot match->start match->ctf->europium) 5. Move forward with the 'w' key(steer with the mouse) to some rotating cubes. Here you should notice the glitch in rotation and the _system_ mouse pointer flickering in and out near the crosshair at a rate of about once a second. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 21:46:28 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2102] LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/Downloads/username-18.10-desktop-amd64.iso ipv6.disable=1 net.ifnames=0 quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.407 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A 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.:bvrK55A.407:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55A dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1800749 Title: Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game) Status in xorg package in Ubuntu: New Bug description: When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are "skips" in the animation of the rotating cubes. Upon further "evaluation", I noticed the system mouse pointer "popping up" briefly at the moment of the glitch(near the crosshair) about once a second. When not in fullscreen, the animation is smooth(no visible skips/glitches) and I don't see the system mouse pointer "popping up" every second. It works fine in fullscreen mode in Ubuntu 18.04. To recreate/observe the problem: 0. Boot into Ubuntu 18.10 1. Install sauerbraten 2. Start sauerbraten 3. Set sauerbraten to fullscreen mode(sauerbraten->options..->display->fullscreen) 4. Start a game(I like sauerbraten->bot match->start match->ctf->europium) 5. Move forward with the 'w' key(steer with the mouse) to some rotating cubes. Here you should notice the glitch in rotation and the _system_ mouse pointer flickering in and out near the crosshair at a rate of about once a second. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18
[Desktop-packages] [Bug 1771035] Re: Please remove gnome-vfs from Ubuntu
** No longer affects: gmotionlive (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs in Ubuntu. https://bugs.launchpad.net/bugs/1771035 Title: Please remove gnome-vfs from Ubuntu Status in gnome-raw-thumbnailer package in Ubuntu: New Status in gnome-vfs package in Ubuntu: New Bug description: gnome-vfs has been removed from Debian Testing and will not be included in the Debian 10 "Buster" release. We should do the same. If we do it now, maybe some projects will do the needed porting work away from libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04 LTS or Debian 10. Users who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few years. This bug depends on the libgnome removal LP: #1771031 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-raw-thumbnailer/+bug/1771035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable
*** This bug is a duplicate of bug 1767648 *** https://bugs.launchpad.net/bugs/1767648 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769299 Title: universal access zoom unusable Status in gnome-shell package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Filed by mark on behalf of low vision user Ken. Ken is able to read 56 point type without magnification at normal reading distance and can barely read the universal access "large text" from a distance of about 2.5 inches from a 26inch monitor at 1360x768. So he really needs magnification and a lot more than the 2x default I used here for testing. We do not live in the same town so providing additional details would be slow. Turned on zoom from the universal access button on top panel. Default settings were used including Zoom = 2.0, screen part = full Several areas are corrupted. These zoom and scroll separately from the rest of the screen and in a way that severely impairs use as portions may not ever be visible. Portions of these subwindows cannot be used because you have to move the mouse off them to be able see them so you can either see or click but not both. These areas are: - The top panel - The left panel (launcher) (intermittently) - pull down menus, particularly the universal access pull down from the top panel Also, the zoom randomly every couple seconds. jumps to a different position without the user's consent. This appeared to be because text was printed by a program running in the terminal window (long apt-get install) but continued to happen even when that window was minimized and even when that program stopped printing. These problems persisted with all the other zoom modes. One mode, however, created new bugs. With "magnifier extends outside of screen", you lose the ability to see the top and left panels at all; you can pan over where they would be but they are not drawn. Can't open the pulldown menu since there is no icon, so who knows how it would be rendered. These bugs made it very difficult to get screenshots, especially with the defective screenshot program gnome-screenshot which ships with system. Also, the bug-reporting program did not permitted attaching additional screenshots once spectacle was installed. Ubuntu 18.04, fresh install, only a few added packages (ham radio related, chrome). Not using wayland, though a wayland session runs concurrently with X11 even though no one has logged in with wayland. Another problem in making the bug report is the irresponsible practice of failing to identify the software being used. The accessability man in circle menu does not have a heading to tell you what program is run for the accessability menu or any of the functions thus invoked. Nor does the settings. And there is no tooltip, popup, or about menu item to convey this information to the user. And running a diff on ps doesn't show any new processes started when zoom is turned on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 5 00:04:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1163] InstallationDate: Installed on 2018-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 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.15.0-20-generic root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A
[Desktop-packages] [Bug 1769299] Re: universal access zoom unusable
*** This bug is a duplicate of bug 1767648 *** https://bugs.launchpad.net/bugs/1767648 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1769299 Title: universal access zoom unusable Status in gnome-shell package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Filed by mark on behalf of low vision user Ken. Ken is able to read 56 point type without magnification at normal reading distance and can barely read the universal access "large text" from a distance of about 2.5 inches from a 26inch monitor at 1360x768. So he really needs magnification and a lot more than the 2x default I used here for testing. We do not live in the same town so providing additional details would be slow. Turned on zoom from the universal access button on top panel. Default settings were used including Zoom = 2.0, screen part = full Several areas are corrupted. These zoom and scroll separately from the rest of the screen and in a way that severely impairs use as portions may not ever be visible. Portions of these subwindows cannot be used because you have to move the mouse off them to be able see them so you can either see or click but not both. These areas are: - The top panel - The left panel (launcher) (intermittently) - pull down menus, particularly the universal access pull down from the top panel Also, the zoom randomly every couple seconds. jumps to a different position without the user's consent. This appeared to be because text was printed by a program running in the terminal window (long apt-get install) but continued to happen even when that window was minimized and even when that program stopped printing. These problems persisted with all the other zoom modes. One mode, however, created new bugs. With "magnifier extends outside of screen", you lose the ability to see the top and left panels at all; you can pan over where they would be but they are not drawn. Can't open the pulldown menu since there is no icon, so who knows how it would be rendered. These bugs made it very difficult to get screenshots, especially with the defective screenshot program gnome-screenshot which ships with system. Also, the bug-reporting program did not permitted attaching additional screenshots once spectacle was installed. Ubuntu 18.04, fresh install, only a few added packages (ham radio related, chrome). Not using wayland, though a wayland session runs concurrently with X11 even though no one has logged in with wayland. Another problem in making the bug report is the irresponsible practice of failing to identify the software being used. The accessability man in circle menu does not have a heading to tell you what program is run for the accessability menu or any of the functions thus invoked. Nor does the settings. And there is no tooltip, popup, or about menu item to convey this information to the user. And running a diff on ps doesn't show any new processes started when zoom is turned on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 5 00:04:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1163] InstallationDate: Installed on 2018-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 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.15.0-20-generic root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A versio
[Desktop-packages] [Bug 1800751] [NEW] package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: idem for my ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-menus 3.13.3-11ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 31 00:12:34 2018 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-06-18 (134 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1800751 Title: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gnome-menus package in Ubuntu: New Bug description: idem for my ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-menus 3.13.3-11ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 31 00:12:34 2018 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-06-18 (134 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1800751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800751] Re: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1800751 Title: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gnome-menus package in Ubuntu: New Bug description: idem for my ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-menus 3.13.3-11ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 31 00:12:34 2018 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-06-18 (134 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1800751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1800328] Re: HP Office Jet Cups reports Filter Failed. Works OK with 16.04
On 10/30/18 5:25 AM, Marc Deslauriers wrote: > In Xenial, /usr/share/ghostscript/9.5/iccprofiles was a directory. > In Bionic, it is a symlink to /usr/share/color/icc/ghostscript. > > The Bionic package needs to use dpkg-maintscript-helper to ensure the > transition is done properly. > > I will prepare a fix for this. > $ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic $ ls -l /usr/share/ghostscript/ total 8 drwxr-xr-x 4 root root 4096 Oct 28 06:49 9.25 lrwxrwxrwx 1 root root 37 Aug 8 2017 current -> /etc/alternatives/ghostscript-current drwxr-xr-x 2 root root 4096 Oct 19 12:44 fonts $ ls -l /usr/share/ghostscript/current/ total 24 drwxr-xr-x 11 root root 4096 Oct 3 06:14 Resource lrwxrwxrwx 1 root root27 Sep 27 04:27 iccprofiles -> ../../color/icc/ghostscript drwxr-xr-x 2 root root 20480 Oct 28 06:49 lib Tom Dean -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800328 Title: HP Office Jet Cups reports Filter Failed. Works OK with 16.04 Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Bionic: Fix Released Bug description: After upgrade from 16.04 to 18.04 and doing an 'apt dist-upgrade', cups fails to print with the status "Filter Failed". On a 16.04 system printing is OK. Printer: Network HP-Officejet-Pro-8620 No changes were made other than the do-release-upgrade and 'apt dist-upgrade'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 27 23:58:29 2018 Lpstat: device for HP-HP-Officejet-Pro-8620: socket://192.168.1.193:9100 MachineType: System76 Meerkat Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-HP-Officejet-Pro-8620.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7479522-2d49-4598-a480-8ed5dee4c2c8 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-19 (8 days ago) dmi.bios.date: 11/22/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0057.2017.1122.1550 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0057.2017.1122.1550:bd11/22/2017:svnSystem76:pnMeerkat:pvrmeer3:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvnSystem76:ct3:cvrmeer3: dmi.product.name: Meerkat dmi.product.version: meer3 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
I attach the debdiff output with the ibus-xx-f19-password.patch reapplied in case anyone wants to rebuild the package or the package maintainer wants to pick it up. ** Patch added: "1-1.0-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+attachment/5207331/+files/1-1.0-1ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799851] Re: Software Boutique window suddenly shows Welcome window and looses all the apps I queued to install
APolihron, Thank you for telling me what to try and, more importantly how to do it! I admit I am a Linux newbie. I got the following: robert@A88XM-A:~/Desktop$ ubuntu-mate-welcome --boutique [Welcome] Starting in Software Boutique mode. [Welcome] Snap detected. Using __VERSION__ [Welcome] Version: 17.10.26 [Welcome] Application Ready. Since the time of the original report, I have had to reinstall Ubuntu MATE 18.04 for the third time in the last week. After re-installation, the Boutique seems to be working as expected. I even got the Software app to install and work. I think the initial crash might have been the result of trying to select too many apps for installation. But without a dump or the ability to repeat the failure, I do not see any resolution other than ask the developer to check the code for adding an app to the queue and closing this bug report. Robert Pearson -- 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/1799851 Title: Software Boutique window suddenly shows Welcome window and looses all the apps I queued to install Status in gnome-software package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Incomplete Bug description: I was selecting apps to install in the Software Boutique, then suddenly the Boutique Window displayed the welcome window and lost all the apps I queued for installation. Ubuntu 18.04.1 LTS (just reinstalled when Ubuntu MATE 18.10 went into total meltdown). AMD 64-bit prosessor Menu->Administration->Software Boutique I had actually hoped to install the same software I had installed when I first installed 18.04. All work lost. The code quality is definitely going down hill fast. (even ubuntu-bug -w gets an error message robert@A88XM-A:~/Desktop$ ubuntu-bug -w Gtk-Message: 20:41:01.726: GtkDialog mapped without a transient parent. This is discouraged.). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3.6-minimal 3.6.6-1~18.04 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 24 20:41:06 2018 ExecutablePath: /usr/bin/python3.6 InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: python3.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800763] [NEW] After installing the package with version 340.107, the system won't start
Public bug reported: On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restart, entered recovery mode, with root terminal, and removed the driver, and then the systems starts using the Nouveau drivers. The GPU is a nVidia GeForce 9500GT. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Description changed: - On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restard, entered recovery mode, with root terminal, and removed the driver, and the the systems starts using the Nouveau drivers. + On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restart, entered recovery mode, with root terminal, and removed the driver, and then the systems starts using the Nouveau drivers. The GPU is a nVidia GeForce 9500GT. ** Summary changed: - After installing the package with 340.107, the system won't start + After installing the package with version 340.107, the system won't start -- 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/1800763 Title: After installing the package with version 340.107, the system won't start Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restart, entered recovery mode, with root terminal, and removed the driver, and then the systems starts using the Nouveau drivers. The GPU is a nVidia GeForce 9500GT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1800763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789474] Re: Unable to boot without radeon.dpm=0
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1789474 Title: Unable to boot without radeon.dpm=0 Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1788471 Title: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 22:04:28 2018 InstallationDate: Installed on 2018-08-13 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789474] Re: Unable to boot without radeon.dpm=0
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1789474 Title: Unable to boot without radeon.dpm=0 Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738606] Re: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1738606 Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') Status in cups package in Ubuntu: Expired Bug description: Processing triggers for libc-bin (2.19-0ubuntu6.13) ... Errors were encountered while processing: cups-server-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-server-common 1.7.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CupsErrorLog: E [10/Dec/2017:11:53:47 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:12:19:55 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:13:15:06 +0530] Filter "rastertopwg" not found. Date: Sun Dec 17 13:31:43 2017 Dependencies: DuplicateSignature: package:cups-server-common:1.7.2-0ubuntu1.8:package cups-server-common is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2017-09-16 (92 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 3542 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: cups Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0KHNVP dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747338] Re: package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status '
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1747338 Title: package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status 'half-installed') Status in cups package in Ubuntu: Expired Bug description: Keeps coming on when i log in, just switching back to ubuntu from windows so unclear if it is because I am removing the windows partition and maybe their was data loss. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-server-common 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CupsErrorLog: E [04/Feb/2018:22:13:24 -0500] Unable to open listen socket for address /var/run/cups/cups.sock:0 - Permission denied. E [04/Feb/2018:22:14:37 -0500] Unable to open listen socket for address /var/run/cups/cups.sock:0 - Permission denied. Date: Sun Feb 4 22:21:57 2018 Dependencies: DuplicateSignature: package:cups-server-common:2.1.3-4ubuntu0.3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package cups-server-common (--configure): package cups-server-common is not ready for configuration ErrorMessage: package cups-server-common is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-02-05 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=25d0b994-bf9b-4425-849f-19dd4dee8017 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: cups Title: package cups-server-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2018-02-05 (0 days ago) dmi.bios.date: 03/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: AB350M Pro4 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.:bvrP2.10:bd03/30/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751099] Re: Different bugs from what I saw (new linux user)
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1751099 Title: Different bugs from what I saw (new linux user) Status in cups package in Ubuntu: Expired Bug description: I had some errors for 2-3 days, but it resolved after I made an update, but I wanted to check if I still had some bugs,so I runned the command "ubuntu-bug cups" and I found a long row... I would love some help if you can give it to me, I'm a new user and I don't know so much about Linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 22 19:04:27 2018 InstallationDate: Installed on 2018-01-31 (22 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude D620 Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=c5716610-bf00-4497-938c-dba51b08d432 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0FT292 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1751099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 577543] Re: Autoscroll sticks on in Firefox, and keeps scrolling
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/577543 Title: Autoscroll sticks on in Firefox, and keeps scrolling Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox When pressing the middle button on the mouse to autoscroll, autoscroll will stick on, and keep scrolling in the original direction, no matter where you move the mouse, or if you press any buttons. It usually lasts for 15 seconds or so before unsticking. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Sat May 8 19:17:06 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support N/A firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/577543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 365239] Re: Jumbled output on plaintext lines with '_' char via lpr on HP Color LaserJet CP2025dn
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/365239 Title: Jumbled output on plaintext lines with '_' char via lpr on HP Color LaserJet CP2025dn Status in HPLIP: Incomplete Status in hplip package in Ubuntu: Expired Bug description: Printer: HP Color LaserJet CP2025dn printer Driver: HP Color LaserJet CP2020 Series with Duplexer Postscript (recommended) PPD: hp-color_laserjet_cp2025dn-ps.ppd The problem: When printing from the command line via lp or lpr, if a line within a plaintext file contains an underscore character ('_'), then characters to the right of the underscore are shifted leftwards, thereby creating a jumbled overstrike effect. Lines that do not contain an underscore character seem to print just fine. This "underscore creates overstrike" bug does not occur when printing the same plain text file from firefox. Here's a copy of my test file (notice the underscores in different places on each line): 12345678901234567890123456789012345678901234567890123456789012345678901234567890 123456789_1234567890123456789012345678901234567890123456789012345678901234567890 1234567890123456789_123456789012345678901234567890123456789012345678901234567890 12345678901234567890123456789_12345678901234567890123456789012345678901234567890 123456789012345678901234567890123456789_1234567890123456789012345678901234567890 1234567890123456789012345678901234567890123456789_123456789012345678901234567890 12345678901234567890123456789012345678901234567890123456789_12345678901234567890 123456789012345678901234567890123456789012345678901234567890123456789_1234567890 1234567890123456789012345678901234567890123456789012345678901234567890123456789_ To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/365239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 395516] Re: Toner levels are available, but not reported to CUPS
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/395516 Title: Toner levels are available, but not reported to CUPS Status in hplip package in Ubuntu: Expired Bug description: Binary package hint: hplip I have a HP CP1515n printer, and the toner levels can be read using the hplip tools. I was expecting the toner info to be exported though the "normal" CUPS gui (system-config-printer -> properties -> Ink/toner levels) as well, but that property page only shows "Marker levels are not reported for this printer". Please make it so marker levels are reported through the standard CUPS gui. ProblemType: Bug Architecture: amd64 Date: Sat Jul 4 15:47:59 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Color-LaserJet-CP1515n: hp:/net/HP_Color_LaserJet_CP1515n?ip=192.168.1.103 MachineType: Dell Inc. Inspiron 530s Package: hplip 3.9.6-0ubuntu3 Papersize: a4 PpdFiles: Color-LaserJet-CP1515n: HP Color LaserJet cp1515n hpijs pcl3, 3.9.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-1-generic root=UUID=d96ea05d-89de-4719-93d3-2d4a266abe17 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-1.14-generic SourcePackage: hplip Uname: Linux 2.6.31-1-generic x86_64 dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530s dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/395516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 289173] Re: Ubuntu driver for HP D4200 fails when printing to networked printer shared on XP
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/289173 Title: Ubuntu driver for HP D4200 fails when printing to networked printer shared on XP Status in hplip package in Ubuntu: Expired Bug description: I have an HP D4200 printer shared by an XP pc. Using the default system-config-printer in Ubuntu, when I add the printer, the tool finds the shared printer on the network. Whenever I print however the printer queue hangs and the PC needs to be rebooted. Thus I am trying HPLIP. I installed HPLIP but the network connection option will not find the shared printer. If I manually put in the same URI as is in the cups tool, it still does not find it. the URI is: smb://home/hydrogen/mainfloor home is the windows workgroup hydrogen is the pc name mainfloor is the printer ID (this is a 3 floor house) There is no browse option that I could find. I have uninstalled, purged and deleted HPLIP and reinstalled. The first time I installed there was a broken package in aptitude returning an error. I fixed the package error before reinstalling but note that the dependencies did not appear to be removed. I do not know if it was necessary to remove the dependencies before reinstalling. What should I do now? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/289173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 347222] Re: toolbox.py crashed with TypeError in updateHeaderTab()
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/347222 Title: toolbox.py crashed with TypeError in updateHeaderTab() Status in hplip package in Ubuntu: Expired Bug description: Binary package hint: hplip Happend on AMD 64 System with Nvidia 750sli chipset when trying to do a fax set up with new CM 1312 nfi color laser printer. Run Kunbuntu Jaunty latest alpha 6 snapshot software ProblemType: Crash Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/hplip/toolbox.py InterpreterPath: /usr/bin/python2.6 Lpstat: device for Fax_2: hpfax:/usb/HP_Color_LaserJet_CM1312nfi_MFP?serial=00CNC88CFN0V device for HP_Color_LaserJet_CM1312nfi_MFP: hp:/usb/HP_Color_LaserJet_CM1312nfi_MFP?serial=00CNC88CFN0V MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: hplip-data 3.9.2-3ubuntu1 PackageArchitecture: all Papersize: a4 PpdFiles: Fax_2: HP Fax 2 HP_Color_LaserJet_CM1312nfi_MFP: HP Color LJ cm1312nfi MFP hpijs, hpijs 3.9.2 ProcCmdLine: root=UUID=2d352982-6d29-4902-952c-86914aeaf866 ro quiet splash pci=nomsi ProcCmdline: python /usr/bin/hp-toolbox ProcEnviron: LANG=en_ZA.UTF-8 SHELL=/bin/bash LC_CTYPE=C ProcVersionSignature: Ubuntu 2.6.28-11.36-generic PythonArgs: ['/usr/bin/hp-toolbox'] SourcePackage: hplip Title: toolbox.py crashed with TypeError in updateHeaderTab() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/347222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp