[Desktop-packages] [Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
The issue has since been fixed and is not present in gtk3, version 3.24. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1731581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
Is this behavior a consequence of Bug #1926256 "Pasted text in the terminal is always highlighted and selected" ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: New Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
@Egmont, You mean it will always be like this going forward? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Is this the feature you are referring to?... f. New active mark and face feature: when enabled, it will highlight the text inserted by a bracketed paste (the `active region') and the text found by incremental and non-incremental history searches. This is tied to bracketed paste and can be disabled by turning off bracketed paste. ..or, is it this one?... h. Bracketed paste mode is enabled by default. If so, it looks like this "feature" can be disabled. How? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I find there is an inconsistency with this new approach: If you've just pasted text, then highlight the text, the text looks unhighlighted. This is visually confusing. Perhaps this is an unintended consequence that needs remediation? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927827] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1927827/+attachment/5497797/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in cheese package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notific
[Desktop-packages] [Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported
apport information ** Tags added: apport-collected ** Description changed: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-04-28 (17 days ago) + InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) + MachineType: HP HP Spectre x360 Convertible 15-bl1XX + NonfreeKernelModules: nvidia_modeset nvidia + Package: cheese 3.38.0-3 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 + RelatedPackageVersions: + cheese3.38.0-3 + cheese-common 3.38.0-3 + Tags: hirsute gstreamer-error + Uname: Linux 5.11.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 12/15/2020 + dmi.bios.release: 15.43 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F.43 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 827F + dmi.board.vendor: HP + dmi.board.version: 95.11 + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 95.11 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Spectre + dmi.product.name: HP Spectre x360 Convertible 15-bl1XX + dmi.product.sku: 1VW22AV + dmi.sys.vendor: HP + lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface + Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1927827/+attachment/5497795/+files/CheeseDebug.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in
[Desktop-packages] [Bug 1927827] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1927827/+attachment/5497798/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in cheese package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To
[Desktop-packages] [Bug 1927827] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1927827/+attachment/5497796/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in cheese package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notif
[Desktop-packages] [Bug 1927827] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1927827/+attachment/5497799/+files/lspci.txt ** Changed in: cheese (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in cheese package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID
[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
Affects Ubuntu 21.04. -- 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/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926862] [NEW] Unable to exit Activities Overview in Ubuntu 21.04
Public bug reported: In Ubuntu 21.04, after entering the Activities Overview by clicking on Activities, by using the hot corner, or by pressing the Super key, the user is not able to exit the Activities Overview and return to the Desktop. The user can still open or close applications, or move applications to different work spaces, but the user can not interact with open applications or return to the normal GNOME desktop. This issue occurs randomly. The only remedy is to logout, restart gnome shell with Alt-F2, R if using Xorg. This affects: Ubuntu 21.04 gnome-shell 3.38.4-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 1 21:37:12 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-28 (3 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1926862 Title: Unable to exit Activities Overview in Ubuntu 21.04 Status in gnome-shell package in Ubuntu: New Bug description: In Ubuntu 21.04, after entering the Activities Overview by clicking on Activities, by using the hot corner, or by pressing the Super key, the user is not able to exit the Activities Overview and return to the Desktop. The user can still open or close applications, or move applications to different work spaces, but the user can not interact with open applications or return to the normal GNOME desktop. This issue occurs randomly. The only remedy is to logout, restart gnome shell with Alt-F2, R if using Xorg. This affects: Ubuntu 21.04 gnome-shell 3.38.4-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 1 21:37:12 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-28 (3 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926816] Re: Computer does not shut down
I am closing this bug report, since GDM is not causing the shutdown issue. ** Changed in: gdm3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1926816 Title: Computer does not shut down Status in gdm3 package in Ubuntu: Invalid Bug description: In Ubuntu 21.04, when I shut down, my laptop never actually shuts down. I see a black screen, the laptop stays on, and the fans spin up. The computer will stay in this state all night. I then have to press and hold the power button to shut down the device. I am using the default kernel, 5.11.0-16-generic. I am also using the Nvidia driver (nvidia-driver-460, version 460.73.01-0ubuntu1) with XOrg. This was not an issue for prior releases of Ubuntu on this machine. For example, Ubuntu 20.04 does not have this problem. I see the following messages in the journalctl log (attached) for gdm.service, which I think may be contributing to this issue: gdm.service: Main process exited, code=exited, status=1/FAILURE gdm.service: Failed with result 'exit-code'. Stopped GNOME Display Manager. gdm.service: Triggering OnFailure= dependencies. Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Fri Apr 30 19:09:43 2021 InstallationDate: Installed on 2021-04-28 (2 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926816] [NEW] Computer does not shut down
Public bug reported: In Ubuntu 21.04, when I shut down, my laptop never actually shuts down. I see a black screen, the laptop stays on, and the fans spin up. The computer will stay in this state all night. I then have to press and hold the power button to shut down the device. I am using the default kernel, 5.11.0-16-generic. I am also using the Nvidia driver (nvidia-driver-460, version 460.73.01-0ubuntu1) with XOrg. This was not an issue for prior releases of Ubuntu on this machine. For example, Ubuntu 20.04 does not have this problem. I see the following messages in the journalctl log (attached) for gdm.service, which I think may be contributing to this issue: gdm.service: Main process exited, code=exited, status=1/FAILURE gdm.service: Failed with result 'exit-code'. Stopped GNOME Display Manager. gdm.service: Triggering OnFailure= dependencies. Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Fri Apr 30 19:09:43 2021 InstallationDate: Installed on 2021-04-28 (2 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Journalctl log from prior unsuccessful shutdown." https://bugs.launchpad.net/bugs/1926816/+attachment/5493993/+files/journal_ctl_2021-04-30-02.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1926816 Title: Computer does not shut down Status in gdm3 package in Ubuntu: New Bug description: In Ubuntu 21.04, when I shut down, my laptop never actually shuts down. I see a black screen, the laptop stays on, and the fans spin up. The computer will stay in this state all night. I then have to press and hold the power button to shut down the device. I am using the default kernel, 5.11.0-16-generic. I am also using the Nvidia driver (nvidia-driver-460, version 460.73.01-0ubuntu1) with XOrg. This was not an issue for prior releases of Ubuntu on this machine. For example, Ubuntu 20.04 does not have this problem. I see the following messages in the journalctl log (attached) for gdm.service, which I think may be contributing to this issue: gdm.service: Main process exited, code=exited, status=1/FAILURE gdm.service: Failed with result 'exit-code'. Stopped GNOME Display Manager. gdm.service: Triggering OnFailure= dependencies. Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Fri Apr 30 19:09:43 2021 InstallationDate: Installed on 2021-04-28 (2 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
Ubuntu 21.04 uses the following vte packages: libvte-2.91-0, version 0.62.3-1ubuntu1 libvte-2.91-common, version 0.62.3-1ubuntu1 gir1.2-vte-2.91, version 0.62.3-1ubuntu1 Ubuntu 20.04 uses the following vte packages: libvte-2.91-0, version 0.60.1-1ubuntu1 libvte-2.91-common, version 0.60.1-1ubuntu1 gir1.2-vte-2.91, version 0.60.1-1ubuntu1 In Ubuntu 21.04, when text is pasted into Gnome Terminal, the text is always highlighted. - It appears as if the text is selected, but it is only highlighted. - If you right-click on this highlighted text, the "Copy" option is actually disabled. - Clicking in the terminal or clicking on the highlighted text does not un-highlight the text. - The only way to un-highlight the pasted text is to type a key. - If you try to select the highlighted text by clicking and dragging the mouse pointer, the text color actually inverts, and the text looks like it is not selected, when it in fact is selected. enter image description here This confusing behavior is not present in Ubuntu 20.04. - In Ubuntu 20.04, when text is pasted into Gnome Terminal, the text is not highlighted. - Then, selecting the text highlights it, as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1926256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
The "Select All" shortcut, when enabled, only selects text from the end of the buffer that fits precisely within the height of the terminal. For example 1. Type `ls -l /lib/*` and press Enter. 2. Scroll the terminal to the beginning. 3. Select all using your configured shortcut (Ctrl-Shift-A in my case). 4. Notice that no text is selected. 5. Then scroll the terminal to the bottom. 6. Notice all of the text that fits within the terminal window size is selected. 7. You can expand the terminal vertically to see that text above this area is not selected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: New Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
I am using nvidia-driver-460 version 460.39-0ubuntu0.20.04.1. xserver-common version 2:1.20.9-2ubuntu1.2~20.04.1 xserver-xephyr version 2:1.20.9-2ubuntu1.2~20.04.1 xserver-xorg version 1:7.7+19ubuntu14 xserver-xorg-core version 2:1.20.9-2ubuntu1.2~20.04.1 The GDM screen would only appear after typing Ctrl+Alt+F2 followed by Ctrl+Alt+F1. The following seems to have fixed the issue for me, and the GDM screen now appears without having to resort to the above "trick". 1. Edit the file /lib/udev/rules.d/61-gdm.rules. sudo nano /lib/udev/rules.d/61-gdm.rules The original file looks like this: # disable Wayland on Hi1710 chipsets ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/lib/gdm3/gdm-disable-wayland" # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" Comment all of the lines as shown: # disable Wayland on Hi1710 chipsets # ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", RUN+="/usr/lib/gdm3/gdm-disable-wayland" # disable Wayland when using the proprietary nvidia driver # DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" Type Ctrl+X to exit, then Y, and then Enter to save the file. 2. Ensure that the Wayland is not disabled in GDM. sudo nano /etc/gdm3/custom.conf Comment the "WaylandEnable" line, if it is not already commented, as shown: # WaylandEnable=false Type Ctrl+X to exit. If you made changes, type Y, and then Enter to save the file. 3. Finally, reboot. Explanation The /lib/udev/rules.d/61-gdm.rules file is supposed to prevent GDM from displaying the Wayland session option when the NVIDIA proprietary drivers are installed, since NVIDIA does not support Wayland. However, in Ubuntu 20.04, there seems to be another redundant mechanism or rule that also prevents GDM from displaying the Wayland session option. I suspect this, because even after making the above change, the Wayland session option is still not displayed in GDM. (Setting WaylandEnable=true in /etc/gdm3/custom.conf has no effect). Therefore, I have a hunch that there are two conflicting rules, and disabling one of the rules (i.e. /lib/udev/rules.d/61-gdm.rules) seems to remove the conflict. Here is the journalctl boot log before making the above changes. You can see there is an error loading the "fb" module. /usr/lib/gdm3/gdm-x-session[964]: (II) Loading sub module "fb" /usr/lib/gdm3/gdm-x-session[964]: (II) LoadModule: "fb" /usr/lib/gdm3/gdm-x-session[964]: (II) Loading /usr/lib/xorg/modules/libfb.so /usr/lib/gdm3/gdm-x-session[964]: (II) Module fb: vendor="X.Org Foundation" /usr/lib/gdm3/gdm-x-session[964]: compiled for 1.20.9, module version = 1.0.0 /usr/lib/gdm3/gdm-x-session[964]: ABI class: X.Org ANSI C Emulation, version 0.4 /usr/lib/gdm3/gdm-x-session[964]: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. /usr/lib/gdm3/gdm-x-session[964]: (EE) /usr/lib/gdm3/gdm-x-session[964]: (EE) Backtrace: /usr/lib/gdm3/gdm-x-session[964]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55936e23a59c] /usr/lib/gdm3/gdm-x-session[964]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f70b994541f] /usr/lib/gdm3/gdm-x-session[964]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f70b978218b] /usr/lib/gdm3/gdm-x-session[964]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f70b9761859] /usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[964]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f70b976171a] /usr/lib/gdm3/gdm-x-session[964]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f70b9772f36] /usr/lib/gdm3/gdm-x-session[964]: (EE) 6: /usr/lib/xorg/Xorg (dixRegisterPrivateKey+0x239) [0x55936e0f7ac9] /usr/lib/gdm3/gdm-x-session[964]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_init+0xcf) [0x7f70b4b9735f] /usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[964]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f70b87fcc00] /usr/lib/gdm3/gdm-x-session[964]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[964]: (EE) 9: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f70b87f4dd0] /usr/lib/gdm3/gdm-x-session[964]: (EE) 10: /usr/lib/xorg/Xorg (AddGPUScreen+0xf5) [0x55936e0d92d5] /usr/lib/gdm3/gdm-x-session[964]: (EE) 11: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0xa44) [0x55936e134cf4] /usr/lib/gdm3/gdm-x-session[964]: (EE) 12: /usr/lib/xorg/Xorg (xf86PlatformDeviceCheckBusID+0x225) [0x55936e13a035] /usr/lib/gdm3/gdm-x-session[964]: (EE) 13: /usr/lib/xorg/Xorg (config_fini+0xa4a) [0x55936e1368da] /usr/lib/gdm3/gdm-x-session[964]: (EE) 14: /usr/lib/xorg/Xorg (config_fini+0x15eb) [0x55936e13810b] /
[Desktop-packages] [Bug 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
Could this be a regression of Bug #1792932 ? -- 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/1811023 Title: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 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/xorg-server/+bug/1811023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666]
I'm using 3.34.1 in Ubuntu 19.10, and I don't experience this issue anymore. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standar
James, Per comment #5 (https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1723678/comments/5) you should probably open a new bug report, and link this old bug. (Also, add a comment here with the link to the new bug report, so folks that are subscribed to this bug and are also still experiencing this issue can indicate that they are impacted). -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I am using 18.10 and I have not yet experienced this issue. For me, in 18.04, something that consistently triggered this bug was whenever I accidentally touched the touch-screen on my laptop while adjusting it. In 19.04, I am able to interact with the touch-screen using my fingers, and this issue has not appeared yet. Also, I never used workspace related extensions. So, it is possible that there are multiple issues here, that all have the same symptom. Perhaps there is a common underlying cause, such as a memory issue, as Daniel van Vugt had suggested. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded. Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Logs' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="u Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.clocks' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Characters.BackgroundService' Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Calculator.SearchProvider' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon... Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all features are available Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 (series 16; classic) ubuntu/19.04 (amd64) linux/5.0.0-13-generic. Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 systemd[1]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1745]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1217]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1]: Started Snappy daemon. Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMet Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:21 PS006 dbus-da
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
It just happened now... When this happened, I had right clicked on a misspelled work in a Firefox text area. I didn't get a popup context menu; I thought it was just Firefox acting up. So, I switched to my open Gedit window, to cut the correctly spelled word from my text document, and the context menu in Gedit wouldn't work either. It didn't work for a while. But as I started to research and copy logs in order to collect information to post here, the right click context menu magically started to work again, after some time. I'll post the journalctl out put here. The issue happened around 10:19 in the logs... -- 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/1825919 Title: Gedit right click context menu stops working Status in gedit package in Ubuntu: Incomplete Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
NON_DEFAULT EXTENSIONS -- Dash to Dock https://extensions.gnome.org/extension/307/dash-to-dock/ Note: I have removed gnome-shell-extension-ubuntu-dock Bluetooth Quick Connect https://extensions.gnome.org/extension/1401/bluetooth-quick-connect/ Caffeine [INACTIVE] https://extensions.gnome.org/extension/517/caffeine/ Clipboard Indicator https://extensions.gnome.org/extension/779/clipboard-indicator/ Coverflow Alt-Tab https://extensions.gnome.org/extension/97/coverflow-alt-tab/ Printers https://extensions.gnome.org/extension/1218/printers/ Refresh Wifi Connections https://extensions.gnome.org/extension/905/refresh-wifi-connections/ Sound Input & Output Device Chooser https://extensions.gnome.org/extension/906/sound-output-device-chooser/ TLP Switcher https://extensions.gnome.org/extension/1212/tlp-switcher/ DEFAULT EXTENSIONS -- Desktop Icons [INACTIVE] Note: Default Ubuntu extension Ubuntu appindicators Note: Default Ubuntu extension GEDIT PLUGINS - I have the following Gedit plugin packages installed: 1. gedit-plugins 2. gedit-source-code-browser-plugin The following Gedit plugins are activated: Character Map Code Comment Document Statistics File Browser Panel Find in Files Insert Date/Time Join/Split Lines Smart Spaces Sort Source Code Browser Spell Checker Word Completion Zeitgeist dataprovider REPRODUCING ISSUE - I haven't been able to find a consistent way to reproduce this issue... It occurs after using Gedit for a long time. I use Gedit heavily, open many tabs, and open local and remote text documents. I do lot of cut-and-paste, I use the right-click context menu a frequently to cut or paste text. While using Gedit, I simultaneously use Meld, and sometimes I have the same document(s) open in Gedit and in Meld. I may edit a document at the same time in Meld and in Gedit. (When I do this, I simply reload the file when Meld or Gedit warn me that a file has changed). One extension that I use heavily is Clipboard Indicator. -- 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/1825919 Title: Gedit right click context menu stops working Status in gedit package in Ubuntu: Incomplete Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Right click context menu stops working
I see this in my application logs: Unable to parse accelerator ???:ignored request to install 6 accelerators (Where ??? is a non-printing character). ** Description changed: The Gedit text area right-click context menu stops appearing. - This bug affects Ubuntu 19.10, but may be a regression of old Bug + This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. ** Summary changed: - Right click context menu stops working + Gedit right click context menu stops working -- 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/1825919 Title: Gedit right click context menu stops working Status in gedit package in Ubuntu: New Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Still present in Ubuntu 19.04, fresh install. (Although, now, clicking twice seems to bring up the authentication dialog, and you don't have to click very rapidly). -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 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: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Ubuntu version 19.04 GTK3 version 3.24.8-1ubuntu1 Gnome Shell Version 3.32.0 -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 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: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] [NEW] Right click context menu stops working
Public bug reported: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.10, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Description changed: The Gedit text area right-click context menu stops appearing. - This may be a regression of old Bug #1731581 from Ubuntu 17.10. + This bug affects Ubuntu 19.10, but may be a regression of old Bug + #1731581 from Ubuntu 17.10. - Gedit version: 3.32.0-3 - Fresh install of Ubuntu 19.04 - gkt-3 version: 3.24.8-1ubuntu1 + Gedit version: 3.32.0-3 + Fresh install of Ubuntu 19.04 + gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. -- 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/1825919 Title: Right click context menu stops working Status in gedit package in Ubuntu: New Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.10, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
For reference, here are the upstream bugs: GITLAB: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 BUGZILLA: https://bugzilla.gnome.org/show_bug.cgi?id=724935 https://bugzilla.gnome.org/show_bug.cgi?id=703046 -- 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/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
This bug is still being tracked in bugzilla. ** Bug watch added: GNOME Bug Tracker #724935 https://gitlab.gnome.org/724935 ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 => GNOME Bug Tracker #724935 ** Bug watch added: GNOME Bug Tracker #703046 https://gitlab.gnome.org/703046 -- 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/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Oops, I meant to say, "Less than *4* doesn't work, and more than 4 are not necessary." -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 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: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
I opened this issue against gnome-shell, upstream. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 I did not report this bug against gtk+3.0. Should I do that as well? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Works on 18.10 x64 for me... $ sudo apt update $ sudo apt install --reinstall libxkbcommon0 libxkbcommon-x11-0 xkb-data Thanks! -- 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 Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released 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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Interesting... I tried that, and I noticed that 4 rapid clicks (actually taps on my touchpad) consistently brings up the pkexec password box. Less than 3 doesn't work, and more than 4 are not necessary. Once you've been authenticated, you are able to make changes on the Other Software tab, as you would expect. -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 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: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Sam James Houlbrook, If you are still having this problem, after updating, you'll need to open a new bug report, since a fix was released. (I am able to type capital enters using the onscreen keyboard in 18.10, so I can't test this in 18.04). -- 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: Fix Released Status in OEM Priority Project bionic series: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released 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 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
Marco, I tried the extension level patch at https://github.com/micheleg/dash- to-dock/issues/128#issuecomment-432913072. Here are my findings... #1 It worked great for preventing two instances of am application from launching when touching an icon on the dock. #2 However, touching the App Grid Icon still does not work. (It seems like the App Grid is unresponsive, but what is really happening is that the applications overview appears briefly and suddenly disappears, as if you had tapped on the App grid Icon twice). Does the fix at https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/272 resolve item #2 above? System Info... $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic $ gnome-shell --version GNOME Shell 3.30.1 $ uname -r 4.18.0-10-generic -- 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
I'm willing to help test this, so please let me know what to do. -- 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 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
The fact that the Dash is visible on the desktop ~immediately after~ a touch event seems to be contributing to the problem. See this experiment I did... https://github.com/micheleg/dash-to- dock/issues/128#issuecomment-423012581 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have an Bangho AERO 1104 with touch screen, when I try to open the application drawer from the applications icon in the dock, it does not open. 1)- Ubuntu 17.10 Artful Aardvark 64 bit 2)- gnome-shell-extension-ubuntu-dock_0.7 3)- What should happen is that touching the applications icon in the dock, opens the application drawer. 4)- Instead, what has happened is that absolutely nothing happened To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Reading through the bug report linked by Daniel van Vugt (vanvugt) in comment #24 (https://github.com/micheleg/dash-to-dock/issues/128), I noticed that Dash-to-Dock is only affected. I had uninstalled the Ubuntu Dock... $ sudo apt autoremove --purge gnome-shell-extension-ubuntu-dock However, I was using the Dash-to-Dock extension, instead. $ sudo apt install gnome-shell-extension-dashtodock So, I disabled Dash-to-Dock. Now the problem is gone. Are all of you using either Dash-to-Dock or the Ubuntu-Dock? If so, what happens when you disable or remove it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have an Bangho AERO 1104 with touch screen, when I try to open the application drawer from the applications icon in the dock, it does not open. 1)- Ubuntu 17.10 Artful Aardvark 64 bit 2)- gnome-shell-extension-ubuntu-dock_0.7 3)- What should happen is that touching the applications icon in the dock, opens the application drawer. 4)- Instead, what has happened is that absolutely nothing happened To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
I'll go first... $ sudo dmidecode | grep -A9 "System Information" System Information Manufacturer: HP Product Name: HP Spectre x360 Convertible 15-bl1XX Version: Serial Number: 5CD74284QL UUID: 37444335-3234-3438-514C-4C3432344435 Wake-up Type: Power Switch SKU Number: 1VW22AV Family: 103C_5335KV HP Spectre $ sudo lshw -short H/W path Device Class Description = system HP Spectre x360 Convertible 15-bl1XX (1VW22AV) /0 bus827F /0/0 memory 64KiB BIOS /0/10 memory 16GiB System Memory /0/10/0memory 8GiB SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0.4 ns) /0/10/1memory 8GiB SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0.4 ns) /0/14 memory 256KiB L1 cache /0/15 memory 1MiB L2 cache /0/16 memory 8MiB L3 cache /0/17 processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/100 bridge Intel Corporation /0/100/2 displayIntel Corporation /0/100/4 genericSkylake Processor Thermal Subsystem /0/100/13 genericIntel Corporation /0/100/14 busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0usb1busxHCI Host Controller /0/100/14/0/5 multimedia HP TrueVision FHD RGB-IR /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2busxHCI Host Controller /0/100/14.2genericSunrise Point-LP Thermal subsystem /0/100/15 genericSunrise Point-LP Serial IO I2C Controller #0 /0/100/16 communication Sunrise Point-LP CSME HECI #1 /0/100/1c bridge Intel Corporation /0/100/1c/0displayNVIDIA Corporation /0/100/1c.4bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.6bridge Sunrise Point-LP PCI Express Root Port #7 /0/100/1c.6/0 wlo1networkWireless 8265 / 8275 /0/100/1c.7bridge Sunrise Point-LP PCI Express Root Port #8 /0/100/1c.7/0 genericRTS525A PCI Express Card Reader /0/100/1d bridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1d/0storageToshiba America Info Systems /0/100/1f bridge Intel Corporation /0/100/1f.2memory Memory controller /0/100/1f.3multimedia Intel Corporation /0/100/1f.4busSunrise Point-LP SMBus /1 power KB06079XL $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0115 (rev 01) $ lsmod | grep multi hid_multitouch 20480 0 hid 118784 4 hid_sensor_hub,i2c_hid,hid_multitouch,intel_ishtp_hid $ modinfo hid_multitouch | grep version srcversion: F120069FA6914E49C917A88 --
[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
This bug seems to only affect Xorg. Wayland is not affected (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1725384/comments/18). Since Xorg is not a priority, I suspect this bug is not getting attention. Unfortunately, many of us have to use Xorg (if you have Nvidia hardware, for example). Initially, I thought that perhaps Gnome is generating multiple touch events, causing the apps overview to open, and then close again (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1725384/comments/10). However, this could be an issue in Gnome Shell, Gnome Dash, Xorg, specific hardware, or something else entirely. Let's see if we can narrow it down or find some kind of pattern, or clue, to what is going wrong. Doing this may help provide the developers with enough information to spot the cause and fix this bug. It would really useful for all of us to list the hard ware we have... Please share the output of: (1) $ sudo dmidecode | grep -A9 "System Information" (2) $ sudo lshw -short (3) $ lspci (4) Is the multi-touch module loaded (most likely for all of us)... $ lsmod | grep multi (5) Multi-touch module version number... $ modinfo hid_multitouch | grep version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have an Bangho AERO 1104 with touch screen, when I try to open the application drawer from the applications icon in the dock, it does not open. 1)- Ubuntu 17.10 Artful Aardvark 64 bit 2)- gnome-shell-extension-ubuntu-dock_0.7 3)- What should happen is that touching the applications icon in the dock, opens the application drawer. 4)- Instead, what has happened is that absolutely nothing happened To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I don't use workspaces-to-dock, and I still have the issue. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I think this bug has been moved to https://gitlab.gnome.org/GNOME/gnome- shell/issues/135 How can we add a remote bug watch for that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard Status in caribou package in Ubuntu: Confirmed Bug description: Unable to type capital letters using onscreen keyboard: 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). 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/ubuntu/+source/caribou/+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 1770299] [NEW] Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'
Public bug reported: I executed gnome-shell --replace from the terminal. After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 9 22:29:33 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-05 (5 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver" 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 ** Description changed: - I executed gnome-shell --restart from the termnal. + I executed gnome-shell --replace from the termnal. - - After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... + After navigating through gnome-shell using my touch screen, I observed + the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 9 22:29:33 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-05 (5 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver" 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: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - I executed gnome-shell --replace from the termnal. + I executed gnome-shell --replace from the terminal. After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to t
[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
This is still an issue on Ubuntu 18.04 using Xorg. Interestingly, capital letters now work on the login GDM screen. But on the desktop, it does't work. Touching the virtual shift key still produces lower case letters. Also, when I select the symbols key to bring up the symbols keyboard layout, not all the keys work. The keys below the top row number of number keys actually produce numbers instead of symbols. Some of the virtual symbols keys do nothing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard Status in caribou package in Ubuntu: Confirmed Bug description: Unable to type capital letters using onscreen keyboard: 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). 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/ubuntu/+source/caribou/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual machine. Instead of corrupted graphics in the Ubiquity window, I saw a blank white area above the "Copying files..." progress bar. After a few seconds, the Ubiquity slide show appeared as usual, and I did *not* get a crash. I will also try this on actual hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' Status in cairo: Confirmed Status in OEM Priority Project: Triaged Status in cairo package in Ubuntu: In Progress Status in glib2.0 package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: In Progress Status in cairo source package in Bionic: In Progress Status in glib2.0 source package in Bionic: Invalid Status in ubiquity source package in Bionic: In Progress Bug description: The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although it was working some weeks/months ago, so this is a recent regression. --- https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77 https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15 https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7 https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524 --- WORKAROUND: 1. Boot into the live session. 2. Settings > Devices > Displays > Scale = 100% 3. Click Apply. 4. Proceed with installation: Click "Install Ubuntu 18.04 LTS". --- Crashed in a VM in the middle of installation. The host is Bionic up to date. From the journal Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000] Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation: Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last): Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 757, in Feb 23 12:52:41 ubuntu /install.py[6858]: install.run() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 135, in run Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 505, in copy_all Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + copy_progress) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: self.command(command, *args, **kw)) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 104, in command Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status) Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() with base 10: '' ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 Date: Fri Feb 23 12:52:28 2018 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: ubiquity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ubiquity crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Ubiquity also crashes inside a virtual machine (VirtualBox) running on a non-HiDPI host machine. I have observed corrupted graphics in the "main area" of Ubiquity when this bug occurs. By "main area", I am referring to the rendered rectangular area in Ubiquity below the title bar and above the "Copying files..." progress bar. The corruption looks like jagged diagonal lines or "snow". I have seen this on both actual hardware (HiDPI machine scaled at 200%) and in a virtual machine (non-HiDPI hardware scaled at 100%). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' Status in OEM Priority Project: Triaged Status in glib2.0 package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Triaged Status in glib2.0 source package in Bionic: Invalid Status in ubiquity source package in Bionic: Triaged Bug description: The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although it was working some weeks/months ago, so this is a recent regression. --- https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77 https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15 https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7 https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524 --- WORKAROUND: 1. Boot into the live session. 2. Settings > Devices > Displays > Scale = 100% 3. Click Apply. 4. Proceed with installation: Click "Install Ubuntu 18.04 LTS". --- Crashed in a VM in the middle of installation. The host is Bionic up to date. From the journal Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000] Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation: Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last): Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 757, in Feb 23 12:52:41 ubuntu /install.py[6858]: install.run() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 135, in run Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 505, in copy_all Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + copy_progress) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: self.command(command, *args, **kw)) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 104, in command Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status) Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() with base 10: '' ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 Date: Fri Feb 23 12:52:28 2018 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: ubiquity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ubiquity crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launch
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Here is the backtrace (bt f) with debug symbols. I still have gdb open, if anyone needs me to do anything else? ** Attachment added: "gdb backtrace (bt f) with debug symbols" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131712/+files/gdb_output_with_debug_symbols.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' Status in glib2.0 package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Triaged Status in glib2.0 source package in Bionic: Incomplete Status in ubiquity source package in Bionic: Triaged Bug description: The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although it was working some weeks/months ago, so this is a recent regression. --- https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77 https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15 --- WORKAROUND: 1. Boot into the live session. 2. Settings > Devices > Displays > Scale = 100% 3. Click Apply. 4. Proceed with installation: Click "Install Ubuntu 18.04 LTS". --- Crashed in a VM in the middle of installation. The host is Bionic up to date. From the journal Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000] Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation: Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last): Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 757, in Feb 23 12:52:41 ubuntu /install.py[6858]: install.run() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 135, in run Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 505, in copy_all Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + copy_progress) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: self.command(command, *args, **kw)) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 104, in command Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status) Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() with base 10: '' ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 Date: Fri Feb 23 12:52:28 2018 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: ubiquity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ubiquity crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727318] Re: I can not change Wallpaper after Ubuntu 17.10 Update
I tried to set an svg as my wallpaper by right clicking on it. Then I opened Gnome Control Center. I clicked on Backgrounds in gnome Control center, but Control Center froze. The background id get set after a delay, but I had to kill Control Center. Afterwards, I saw the error in the logs. -- 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/1727318 Title: I can not change Wallpaper after Ubuntu 17.10 Update Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After Ubuntu Update? 1- I can not change wallpaper 2- I can not change some configs 3- Strange keyboard layout (not configurable) See some errors founded: (gnome-control-center:5657): Clutter-WARNING **: Whoever translated default:LTR did so wrongly. (gnome-control-center:5657): Grilo-WARNING **: [registry] grl- registry.c:1362: Plugin 'grl-flickr' not available (gnome-control-center:5657): background-cc-panel-WARNING **: Plug-in "grl-flickr" não disponível ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 10:22:58 2017 InstallationDate: Installed on 2016-08-02 (448 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727) 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/1727318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=791427 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1731581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
Here is the Bugzilla bug... https://bugzilla.gnome.org/show_bug.cgi?id=791427 ** Bug watch added: GNOME Bug Tracker #791427 https://bugzilla.gnome.org/show_bug.cgi?id=791427 -- 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/1731581 Title: Context menus do not appear for Gtk text areas upon right-click Status in gnome-shell package in Ubuntu: New Bug description: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Same issue as LuisC on 17.10, but using xorg. Also, my keyboard stops working, so I can't press super key. However, the gnome-shell top bar and the Ubuntu Dock still accept inputs. As a result, I am able to launch programs. I can also kill programs by clicking on the window's "X" (close) in Activities (overview) mode, but the window controls (close, minimize, and maximize) do not accept any form of input. Restarting solves the problem. Loging-out and loging back in does not correct the problem. Note that I am able to use the mouse and keyboard on the GDM screen, just like I am able to interact with the topbar and Ubuntu Dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
Do we know what the desired behavior requirements are? I'm thinking something like... 1. User taps screen 2. Check if event is in an editable text area 3. If yes, display caribou in half* of the screen where tap did ~not~ occur 4. If no, do not display caribou 5. If caribou is not displayed, sliding up from the bottom of the screen should always be available in order to activate the on-screen keyboard. (* Perhaps this could actually be changed to: display caribou in the quadrant of the screen diagonal to where the tap occurred. But you have to take screen size into account, so for smaller screens, the half screen rule above may need to be used). -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721315] Re: On-screen keyboard shows up on first touch even when touch does not activate a text-field
*** This bug is a duplicate of bug 1723857 *** https://bugs.launchpad.net/bugs/1723857 Do we know what the desired behavior requirements are? I'm thinking something like... 1. User taps screen 2. Check if event is in an editable text area 3. If yes, display caribou in half* of the screen where tap did ~not~ occur 4. If no, do not display caribou 5. If caribou is not displayed, sliding up from the bottom of the screen should always be available in order to activate the on-screen keyboard. (* Perhaps this could actually be changed to: display caribou in the quadrant of the screen diagonal to where the tap occurred. But you have to take screen size into account, so for smaller screens, the half screen rule above may need to be used). -- 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/1721315 Title: On-screen keyboard shows up on first touch even when touch does not activate a text-field Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Impact == Copied from: https://bugzilla.gnome.org/show_bug.cgi?id=788188 "After using the keyboard (or bluetooth stylus), the first touch gesture I make on the touchscreen always brings up the on-screen keyboard, irrespective of whether the touch activates a text-field. This is annoying, for instance when I am using the touchscreen on the maps app (which is much more convenient than from the touchpad), or when I am using the stylus and want to use a touch-screen gesture to scroll to the next page." Test Case = Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686802] Re: Locked screen is visible for about a second on resume
Experiencing this on 17.10. It happens on every resume from suspend. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 I am using gnome-session, Xorg, and gdm3. Is this the same as Bug #1416897? -- 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/1686802 Title: Locked screen is visible for about a second on resume Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: I'm using current Ubuntu Gnome 16.04.2 but the same issue is present in Ubuntu 16.04.2. The problem occurs with or without nvidia drivers. I'm running a fresh installation. On resume, for a second, i can see my screen as it was before suspend. This means that if someone open my laptop can see my desktop and my things. Ok is only a second, but is a very hight security issue for me. I'm sure that is not an hardware problem because with Kde Neon I have not the same behaviour , with or without nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1686802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen
Experiencing this on 17.10. It happens on every resume from suspend. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 I am using gnome-session and Xorg. -- 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/1416897 Title: static image of desktop and windows displayed instead of lockscreen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: This is a follow-on from bug 1375271( https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though it may actually implicate a different underlying problem. . Expectation -- Given any one of the following actions: - (from active desktop session) choosing "lock" from the Unity Panel power menu; - (from locked session with screen turned off): using mouse movement, keystrokes, etc. to poke the screen awake; or - (from suspend) initiating a resume, ...the expected result is to display an interactive lockscreen where the active user's password can be entered to access the session. On this particular machine, which is a touch hybrid, the lockscreen also includes the Onboard soft keyboard. . Observed behavior -- Instead of the lockscreen, each of these actions triggers the machine to display an image of the desktop/window session as it had been near the time of the lock or suspend. The cursor is visible and can be moved. The Unity Panel and Launcher usually appear as normal, although sometimes they are missing. Nothing happens when the user attempts to interact with the visible session by mouse or keyboard input. Keyboard input will actually be fed to the lockscreen's password entry window, however. So blindly typing the password from the zombie GUI session image -- and then pressing "enter" -- will bring up an active, working session. TTY session logins are available by the keyboard shortcuts ctrl- alt-F[number]. After pulling up one of these login screens (without actually logging in), then returning with ctrl-alt-F7, the lockscreen appears as expected. . Regression timeframe: I believe this behavior began sometime during January 2015. . Replication: This unexpected behavior takes place almost every time one of the listed actions is taken. During one period of testing on 2015-01-31, the bug disappeared for a few rounds of lock and unlock. However, it re-appeared shortly thereafter (I believe after the next restart or suspend-resume). . Video attachment: A 1-minute video (.webm, no audio) is attached showing one form of this bug (simple lock-unlock). The main feed was taken from a smartphone, but the video also includes an inset of what SimpleScreenRecorder (SSR) "saw" during the process. On "lock", the actual screen became fully black. SSR, by contrast, recorded a black screen that included a clock in the top-right. On mouse movement, the actual screen displayed the static image of the GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen appearing. . Security tag reasoning: This bug displays a snapshot of recent screen contents from a user's GUI session even when the user has (actively or indirectly) locked the session. It also prevents a user from turning on the screen to command a user switch, go into TTY, etc. without displaying an image of her private GUI session. . Current graphics-related system info: OEM: HP Envy x360 15t (convertible hybrid notebook) CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400 OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel OpenGL Extensions version: 3.0 Mesa 10.5.0-devel OS: Ubuntu 14.10 64-bit Kernel: 3.16.0-29 generic X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1 Pixman version: 0.32.4 Compiz version: 0.9.12 Please let me know if there is further config information that would be helpful. . Upstream testing: This is a production machine. I am willing to test pre-release packages provided the testing configurations are easy to revert (such as upstream kernels). I have been burned in the past with broken package systems and protracted config repairs after testing experimental graphics and video driver software. But I would still be willing give it a shot if there is a simple and reliable process to roll back the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1416897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731587] Re: Application 'org.gnome.Shell.desktop' killed by signal 11
This is random for me as well, but I have received this error while watching Netflix in Google Chrome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1731587 Title: Application 'org.gnome.Shell.desktop' killed by signal 11 Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Gnome Session randomly crashes. Seems to happen a lot while running 'Videos' application. Here is part of syslog: Nov 10 19:01:47 msi-01 systemd[1]: Started Run anacron jobs. Nov 10 19:01:47 msi-01 anacron[6903]: Anacron 2.3 started on 2017-11-10 Nov 10 19:01:47 msi-01 anacron[6903]: Normal exit (0 jobs run) Nov 10 19:02:35 msi-01 gnome-shell[5258]: ../../../../gobject/gsignal.c:2641: instance '0x56552d09fcc0' has no handler with id '40302' Nov 10 19:02:35 msi-01 gnome-shell[5258]: ../../../../gobject/gsignal.c:2641: instance '0x56552e423d20' has no handler with id '40302' Nov 10 19:02:35 msi-01 gnome-shell[5258]: (cogl-pipeline.c:602):_cogl_pipeline_update_layers_cache: code should not be reached Nov 10 19:02:35 msi-01 kernel: [236833.394536] gnome-shell[5258]: segfault at 80 ip 7f375f2193dc sp 7ffe8b8912c8 error 4 in libmutter-cogl-1.so[7f375f1d8000+a5000] Nov 10 19:02:35 msi-01 gnome-shell[5258]: message repeated 2 times: [ (cogl-pipeline.c:602):_cogl_pipeline_update_layers_cache: code should not be reached] Nov 10 19:02:35 msi-01 update-notifier[6014]: Error reading events from display: Broken pipe Nov 10 19:02:35 msi-01 nautilus[5966]: Error reading events from display: Broken pipe Nov 10 19:02:35 msi-01 telepathy-indic[5706]: Error reading events from display: Broken pipe Nov 10 19:02:35 msi-01 caffeine[5607]: Error reading events from display: Broken pipe Nov 10 19:02:35 msi-01 org.gnome.Shell.desktop[5258]: (EE) Nov 10 19:02:35 msi-01 org.gnome.Shell.desktop[5258]: Fatal server error: Nov 10 19:02:35 msi-01 org.gnome.Shell.desktop[5258]: (EE) failed to read Wayland events: Broken pipe Nov 10 19:02:35 msi-01 org.gnome.Shell.desktop[5258]: (EE) Nov 10 19:02:35 msi-01 gnome-session[5192]: gnome-session-binary[5192]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Nov 10 19:02:35 msi-01 gnome-session-binary[5192]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Nov 10 19:02:35 msi-01 gnome-session-binary[5192]: Unrecoverable failure in required component org.gnome.Shell.desktop Nov 10 19:02:35 msi-01 thunderbird.desktop[5779]: xcb_connection_has_error() returned true Nov 10 19:02:35 msi-01 org.gnome.Shell.desktop[5258]: xcb_connection_has_error() returned true Nov 10 19:02:35 msi-01 gsd-rfkill[5430]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput' Nov 10 19:02:35 msi-01 chromium-browser.desktop[6658]: [6724:6724:1110/190235.947265:ERROR:x11_util.cc(89)] X IO error received (X server probably went away) Nov 10 19:02:35 msi-01 chromium-browser.desktop[6658]: [6658:6658:1110/190235.948751:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away) Nov 10 19:02:35 msi-01 gsd-keyboard[5469]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 gsd-media-keys[5467]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 thunderbird[5779]: thunderbird: Fatal IO error 104 (Connection reset by peer) on X server :0. Nov 10 19:02:35 msi-01 gsd-a11y-keyboa[5454]: gsd-a11y-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 gsd-color[5458]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 firefox[5855]: firefox: Fatal IO error 104 (Connection reset by peer) on X server :0. Nov 10 19:02:35 msi-01 gsd-clipboard[5459]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 nautilus-deskto[5622]: nautilus-desktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 10 19:02:35 msi-01 gsd-xsettings[5447]: gsd-xsettings: Fatal IO error 104 (Connection reset by peer) on X server :0. Nov 10 19:02:35 msi-01 org.a11y.atspi.Registry[5293]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Nov 10 19:02:35 msi-01 org.a11y.atspi.Registry[5293]: after 2069 requests (2069 known processed) with 0 events remaining. Nov 10 19:02:35 msi-01 gsd-color[2721]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Goldstar_Company_Ltd_LG_ULTRAWIDE_57706_someuser_1000 Nov 10 19:02:35 msi-01 kernel: [236833.520793] rfkill: input handler enabled Nov 10 19:02:35 msi-01 udev-acl.ck[6953]: g_slice_set_config: asse
[Desktop-packages] [Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
I just noticed a side-effect which may help in debugging this issue... The mouse cursor does not revert to a pointer after doing a right-click. NORMAL EXPECTED BEHAVIOR (a) Typically, if you are hovering over an editable text area, the mouse pointer is a vertical bar (cursor). when you move outside the text area, such as the window title-bar, the mouse pointer reverts to an arrow. (b) Also, when you right click in a text area, the mouse pointer changes to an arrow, so you can pick something in the pop-up context menu that appears. UNWANTED SIDE-EFFECT BEHAVIOR In this case, right-clicking does not change the cursor to an arrow; it stays as a vertical bar. After this, if you move the pointer outside the text area to the window title bar, the mouse pointer is still a cursor (vertical bar shape). Normal behavior should be as described in (a) above. This also happens for window resize pointers. The mouse pointer stays as a cursor every where in the window after right-clicking in the text area. -- 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/1731581 Title: Context menus do not appear for Gtk text areas upon right-click Status in gnome-shell package in Ubuntu: New Bug description: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https
[Desktop-packages] [Bug 1731581] [NEW] Context menus do not appear for Gtk text areas upon right-click
Public bug reported: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" 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 artful -- 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/1731581 Title: Context menus do not appear for Gtk text areas upon right-click Status in gnome-shell package in Ubuntu: New Bug description: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google C
[Desktop-packages] [Bug 1730281] Re: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen
*** This bug is a duplicate of bug 1725384 *** https://bugs.launchpad.net/bugs/1725384 ** This bug has been marked a duplicate of bug 1725384 On touch screens, the apps icon in the dock does not open when touched -- 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/1730281 Title: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Clicking on the application button (with a mouse) in the Ubuntu Dock causes the applications icons to be displayed. ISSUE On a Touch Screen... The issue is, if you touch the application button in the Ubuntu Dock, the applications icons appear (expand out from the button using animation) but then they suddenly disappear (contract back into the button using animation). If you touch the button and do not remove your finger, all of the icons are displayed on the screen. As soon as you remove your finger, the icons recede back into the button. EXPECTED Touching the application button (with a finger) in the Ubuntu Dock should cause the applications icons to be displayed. They should continue to be displayed until the user selects an application, presses the ESC key, or clicks an icon on the dock. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7 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: Mon Nov 6 00:24:05 2017 InstallationDate: Installed on 2017-11-03 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 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/ubuntu/+source/gnome-shell/+bug/1730281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Please see gnome bug #790104. https://bugzilla.gnome.org/show_bug.cgi?id=790104 ** Bug watch added: GNOME Bug Tracker #790104 https://bugzilla.gnome.org/show_bug.cgi?id=790104 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard Status in caribou package in Ubuntu: New Bug description: Unable to type capital letters using onscreen keyboard: 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). 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/ubuntu/+source/caribou/+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 1685035] Re: GDM login doesn't scale on Hi-DPI display
For me, the GDM screen is scaling the icons and text correctly. However, the pointer is very tiny. This tiny pointer is also briefly visible on the Plymouth screen just before GDM appears. Once I click on the user name, and hover over the password text box, the cursor scales up to the correct size. It seems as if the pointer retains its original size (from Plymouth), until it encounters a text area. Then it seems to read the gsettings value and resize itself. GDM 3.26.1 GNOME Shell 3.26.1 Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful -- 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/1685035 Title: GDM login doesn't scale on Hi-DPI display Status in GNOME Settings Daemon: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Zesty: Fix Released Bug description: Impact -- GDM's login screen was being start with no gnome-settings-daemons plugins. In particular, this broke Hi-DPI support in the login screen Test Case - - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI display (ideally one that worked well with Ubuntu GNOME 16.10). - Restart your computer. - The login screen should automatically show at the right scale. Regression Potential See the other 3.24.2 bugs but this commit is a simple typo fix. Original Bug Report --- Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login screen is too tiny to read. GDM login screen doesn't reflect changes to org.gnome.desktop.interface scaling-factor or text-scaling-factor. Eg: xhost +SI:localuser:gdm sudo su gdm -s /bin/bash gsettings set org.gnome.desktop.interface scaling-factor 2 gsettings set org.gnome.desktop.interface text-scaling-factor 2.0 no effect. Creating a gdm user under /etc/dconf and running dconf update has no effect either. Scaling-factor seems to scale the mouse cursor, but nothing else. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1685035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730229] [NEW] Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input
Public bug reported: The desktop area stops accepting inputs from the mouse, keyboard, trackpad, and touchscreen. However, gnome session is not frozen, because I can still interact with the topbar and the Ubuntu Dock using the pointer or keyboard. I can move the pointer using the trackpad, or attached mouse, but clicking or typing in windows on the desktop area has no effect. What I can not do: - I can not close windows using the window buttons. - I can not move windows. - I can not bring windows to the foreground. - I can not click on any dialog buttons. - I can not type in any test areas (such as in gedit). What I can do: - I can start the activities view by clicking on Activities in the top left corner. - I can launch programs from the dock and from the applications button. - I can also interact with the notifications area or the indicator icons at the right of the topbar. - I can type and search for applications after entering the Activities overview. Logging-out and loggin-in does not resolve the problem. - Note that GDM accepts mouse and keyboard inputs. - After logging back into the desktop, I can not interact with the desktop area, as before. Restating is the only way to regain ability to interact with the windows and desktop area. I experience this issue on my laptop running Ubuntu 17.10, but I have not had this issue on my desktop running Ubuntu 17.10. Additional Information (Laptop): 2017 HP Spectre x360 Convertible Laptop - 15t touch GeForce MX150 Using xserver-xorg 1:7.7+19ubuntu3 amd64 Using Nvidia binary driver version 384.90 $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ gnome-shell --version GNOME Shell 3.26.1 $ mutter --version mutter 3.26.1 Note: My desktop (which does not have this issue) is also running Ubuntu 17.10, has an Nvidia card, and is using the proprietary driver with xorg. I'm not sure if mutter is responsible for handling mouse/keyboard inputs separately from GDM, extensions, and the topbar, so I opened this bug against gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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 14:19:45 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" 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: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: - The desktop area stops accepting inputs from the mouse, keyboard, trackpad, and touchscreen. - I can move the pointer using the trackpad or attached mouse, but clicking or typing has no effect. - However, gnome session is not frozen, because I can still interact with the topbar and the Ubuntu Dock. + The desktop area stops accepting inputs from the mouse, keyboard, + trackpad, and touchscreen. + + However, gnome session is not frozen, because I can still interact with + the topbar and the Ubuntu Dock using the pointer or keyboard. + + I can move the pointer using the trackpad, or attached mouse, but + clicking or typing in windows on the desktop area has no effect. What I can not do: - I can not close windows using the window buttons. - I can not move windows. - I can not bring windows to the foreground. - I can not click on any dialog buttons. - I can not type in any test areas (such as in gedit). What I can do: - I can start the activities view by clicking on Activities in the top left corner. - I can launch programs from the dock and from the applications button. - I can also interact with the notifications area or the indicator icons at the right of the topbar. - I can type and search for applications after entering the Activities overview. Logging-out and loggin-in does not resolve the problem. - Note that GDM accepts mouse and keyboard inputs. - After logging back into the desktop, I can not interact with the desktop area, as before. Restating is the only way to regain ability to interact with the windows and desktop area. Addition
[Desktop-packages] [Bug 1730211] [NEW] Unable to type capital letters using onscreen keyboard
Public bug reported: Unable to type capital letters using onscreen keyboard: 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). 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) ** Affects: caribou (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard Status in caribou package in Ubuntu: New Bug description: Unable to type capital letters using onscreen keyboard: 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). 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/ubuntu/+source/caribou/+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 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
I still see significant blurriness in Wayland compared to Xorg. I currently have gnome-shell 3.26.1-0ubuntu4, and I still see the problem. However, in comment #11, this bug report says that a fix was released for 3.26.1-0ubuntu1 on 10/6/2017. I added the following settings in /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml and recompiled the schema so it will apply system wide. Hinting = 'full' Antialiasing = 'rgba' Dconf confirms that the system using these default values, as configured above. When I log into a Wayland session, the desktop fonts respect these settings, but gnome-shell fonts look terrible. The fonts from the topbar, all dropdowns from the top bar, and right-click pop-ups from the dock are extreemly fuzzy. When I log into an Xorg session, gnome-shell fonts look great, very sharp, and clear. There is a significant difference between gnome-shell on Xorg and Wayland. I've attached the following screen-shots to help illustrate the difference: - Wayland on Ubuntu 17.10.png - Screenshot of Wayland + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10 - Xorg on Ubuntu 17.10.png - Screenshot of Xorg + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10 - Wayland vs Xorg on Ubuntu 17.10.png - Screenshot, zoomed in 1500%, showing font rendering differences between Wayland and Xorg Depending on your monitor and resolution, you may not see the difference between the two attached pictutes "Wayland on Ubuntu 17.10.png" and "Xorg on Ubuntu 17.10.png". Nevertheless the third image, " Wayland vs Xorg on Ubuntu 17.10.png", should help. In this image, you can actually see the sub-pixel font rendering, and you can see that grayscale is being used in Wayland (even though I have configured 'rgba'). I will aslo assume that my system setting of 'full' hinting is being ignored as well, by Wayland. 4.13.0-16-generic No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful gnome-shell: Installed: 3.26.1-0ubuntu4 Candidate: 3.26.1-0ubuntu4 Version table: *** 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
Wayland vs Xorg on Ubuntu 17.10.png - Screenshot, zoomed in 1500%, showing font rendering differences between Wayland and Xorg ** Attachment added: "Font rendering differences between Wayland and Xorg, zoomed in 1500%" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714459/+attachment/4985545/+files/Wayland%20vs%20Xorg%20on%20Ubuntu%2017.10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
Xorg on Ubuntu 17.10.png - Screenshot of Xorg + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10 ** Attachment added: "Xorg + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714459/+attachment/4985534/+files/Xorg%20on%20Ubuntu%2017.10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
Wayland on Ubuntu 17.10.png - Screenshot of Wayland + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10 ** Attachment added: "Wayland + gnome-shell topbar, gnome-shell notifications, and Nautilus on Ubuntu 17.10" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714459/+attachment/4985533/+files/Wayland%20on%20Ubuntu%2017.10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
@Didier Roche, I am quite appreciative that you noticed this and opened this bug! QUESTION ABOUT THE FIX: Will subpixel order (=rgb) and hinting (=slight) be hard coded into Wayland, or will the user be able to override these (perhaps through a glib schema file)? -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
Same experience as in #2... Just added Google account in Online Accounts in Control Center, and Control Center crashed. Despite the crash, the Google account was added successfully and seems to be working. -- 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/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in GTK+: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 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/gtk/+bug/1720400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724011] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 Just added Google account in Online Accounts in Control Center, and Control Center crashed. Despite the crash, the Google account was added successfully and seems to be working. -- 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/1724011 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: Confirmed Bug description: added google account, then switched to new tab in settings. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 19:35:17 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f087bd3fb3b:mov0x8(%rax),%rax PC (0x7f087bd3fb3b) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
FYI, just found out the hard way that "Device" needs to be lower case!... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I forgot to add, my wi-fi adapter info is: $ lsusb | grep Wireless Bus 001 Device 002: ID 050d:825b Belkin Components F5D8055 N+ Wireless Adapter v2000 [Ralink RT3072] And I believe it is using the following driver/module: $ lsmod rt2x00usb 20480 1 rt2800usb Located at... /lib/modules/4.10.0-22-generic/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
In my logs, I see the message: "...aborting authentication ...by local choice (Reason: 3=DEAUTH_LEAVING)" (I've listed below the relevant portion of the log file, since the logs above do not include this particular error). The solution posted in comment #1 (https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1681513/comments/1) worked for me... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [Device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart I did not need to install dnsmasq-base, as suggested in comment #24 (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/comments/24). What is the purpose of installing this? - - - - - - - - - - - - - - - - - - - - SYSTEM INFO - - - - - - - - - - - - - - - - - - - - Linux RS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - LOG - - - - - - - - - - - - - - - - - - - - Jun 19 19:20:42 MY_COMPUTER NetworkManager[724]: [1497914442.1301] device (wlx00227540404a): supplicant interface state: disconnected -> scanning Jun 19 19:20:43 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: SME: Trying to authenticate with b4:75:0e:69:96:af (SSID='MY_WIFI' freq=2462 MHz) Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.130115] wlx00227540404a: authenticate with b4:75:0e:69:96:af Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.209885] wlx00227540404a: send auth to b4:75:0e:69:96:af (try 1/3) Jun 19 19:20:43 MY_COMPUTER NetworkManager[724]: [1497914443.7071] device (wlx00227540404a): supplicant interface state: scanning -> authenticating Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.231002] wlx00227540404a: authenticated Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.003601] wlx00227540404a: aborting authentication with b4:75:0e:69:96:af by local choice (Reason: 3=DEAUTH_LEAVING) Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): Activation: (wifi) association took too long, failing activation Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): state change: config -> failed (reason 'ssid-not-found') [50 120 53] Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4984] manager: NetworkManager state is now DISCONNECTED Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5053] device (wlx00227540404a): Activation: failed for connection 'MY_WIFI 1' Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5111] device (wlx00227540404a): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 19 19:20:45 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: CTRL-EVENT-DISCONNECTED bssid=b4:75:0e:69:96:af reason=3 locally_generated=1 Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.063699] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.9519] device (wlx00227540404a): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning) Jun 19 19:20:46 MY_COMPUTER kernel: [ 3003.775904] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2947] sup-iface[0x558e6b4676e0,wlx00227540404a]: connection disconnected (reason -3) Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2958] device (wlx00227540404a): supplicant interface state: authenticating -> disconnected - - - - - - - - - - - - - - - - - - - - -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is
[Desktop-packages] [Bug 1697221] [NEW] Wrapping for labels breaks words
Public bug reported: Labels for some items in Gnome Control Center are too long to fit on a single line. As a result they must continue onto a second line. ISSUE: Labels do not break at work boundaries. Instead, they break in the middle of words. (See attached screenshot). Examples: Region & Lan guage Mouse & Touch pad EXPECTED BEHAVIOR: Labels should break at work boundaries (i.e. spaces between words). Examples: Region & Language Mouse & Touchpad (If a word is too long and must break in the middle, then conventional word hyphenation rules should be applied, or an exception may be made to keep the code simple. This may occur if new items with very long names are added to the control center in the future, or for accessibility reasons where very large fonts are used). ADDITIONAL INFO: The font used in the screenshots is Liberation Sans Regular 10. (However, the word wrapping behavior should be independent of the font and size used). $ uname -a Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Gnome Control Center showing faulty line wrapping" https://bugs.launchpad.net/bugs/1697221/+attachment/4893733/+files/Screenshot%20from%202017-06-10%2018-05-53.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1697221 Title: Wrapping for labels breaks words Status in gnome-control-center package in Ubuntu: New Bug description: Labels for some items in Gnome Control Center are too long to fit on a single line. As a result they must continue onto a second line. ISSUE: Labels do not break at work boundaries. Instead, they break in the middle of words. (See attached screenshot). Examples: Region & Lan guage Mouse & Touch pad EXPECTED BEHAVIOR: Labels should break at work boundaries (i.e. spaces between words). Examples: Region & Language Mouse & Touchpad (If a word is too long and must break in the middle, then conventional word hyphenation rules should be applied, or an exception may be made to keep the code simple. This may occur if new items with very long names are added to the control center in the future, or for accessibility reasons where very large fonts are used). ADDITIONAL INFO: The font used in the screenshots is Liberation Sans Regular 10. (However, the word wrapping behavior should be independent of the font and size used). $ uname -a Linux PS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1697221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585782] [NEW] Inconsistent height on System Monitor header bar
Public bug reported: ISSUE: The height of the header bar changes depending on which button/view is selected. The "Processes" header bar is higher than the "Resources" or "File Systems" header bar. The "Processes" header bar has a gap below the buttons, but the "Resources" and "File Systems" header bars do not have a gap below the buttons. DESIRED BEHAVIOR: The height of the header bar should remain consistent, regardless of which button/view is selected. Preferably, the "Resources" or "File Systems" header bars should have the same height as the "Processes" header bar, with a gap below the buttons. ADDITIONAL INFORMATION: Please see the attached image. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-system-monitor 3.18.2-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 25 15:53:11 2016 InstallationDate: Installed on 2016-05-24 (1 days ago) InstallationMedia: Ubuntu 16.04.0 2016.05.23 amd64 "Custom Xenial Xerus" SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "System Monitor Header Bar Heights 2016-05-25-01-PS.png" https://bugs.launchpad.net/bugs/1585782/+attachment/4670384/+files/System%20Monitor%20Header%20Bar%20Heights%202016-05-25-01-PS.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1585782 Title: Inconsistent height on System Monitor header bar Status in gnome-system-monitor package in Ubuntu: New Bug description: ISSUE: The height of the header bar changes depending on which button/view is selected. The "Processes" header bar is higher than the "Resources" or "File Systems" header bar. The "Processes" header bar has a gap below the buttons, but the "Resources" and "File Systems" header bars do not have a gap below the buttons. DESIRED BEHAVIOR: The height of the header bar should remain consistent, regardless of which button/view is selected. Preferably, the "Resources" or "File Systems" header bars should have the same height as the "Processes" header bar, with a gap below the buttons. ADDITIONAL INFORMATION: Please see the attached image. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-system-monitor 3.18.2-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 25 15:53:11 2016 InstallationDate: Installed on 2016-05-24 (1 days ago) InstallationMedia: Ubuntu 16.04.0 2016.05.23 amd64 "Custom Xenial Xerus" SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1585782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
Experiencing this issue on Ubuntu 16.04 x64. To recreate... Execute: $ gsettings get org.compiz.expo:/org/compiz/profiles/unity/plugins/expo/ vp-saturation Note the value is 40.0. Create a file called /usr/share/glib-2.0/schemas/11_test.gschema.override with the following content: [org.compiz.expo:/org/compiz/profiles/unity/plugins/expo] vp-saturation = '10.0' Note that a relocatable schema was specified in the above file. Execute: $ glib-compile-schemas /usr/share/glib-2.0/schemas/ Execute: $ gsettings get org.compiz.expo:/org/compiz/profiles/unity/plugins/expo/ vp-saturation Note that the vp-saturation value is still 40, and has not been updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1281580 Title: glib-compile-schemas doesn't compile relocatable schemas Status in GLib: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: Dear Developers, I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 and, because my wife is using this system as well, I defined some settings in a gschema.override file. Everything is working right, except applying settings related to custom key-bindings. I added following lines my gschema.override file: [org.gnome.settings-daemon.plugins.media-keys] www='w' email='e' custom-keybindings = ['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0'] [org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/] name = 'Launch Gedit' command = 'gedit' binding = 'g' I put my gschema.override file in the '/usr/share/glib-2.0/schemas' directory. After I added these lines, I ran 'glib-compile-schemas /usr/share/glib2.0/schemas' and no error was reported. For testing purposes I created a new user, logged out, and logged in with the new user. In the best case, the custom key-binding were applied automatically, but this has not happened. Other defined key-bindings were applied correctly. In the gnome-control-center's key-bindings tab, the table containing custom shortcuts is empty, containing one row with empty columns. Running 'gsettings list-recursively org.gnome.settings-daemon.plugins .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins /media-keys/custom-keybindings/custom0/' shows, the name, command, and binding key pairs contain empty ('') values. If I manually run following commands, the custom key-binding is created correctly: gsettings set org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/ name "Launch Gedit" gsettings set org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/ command "gedit" gsettings set org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/ binding "g" Am I doing anything wrong when I want to add a custom key-bindings in my schema file, or is 'glib-compile-schemas' really not applying this part from the schema file? Attila ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libglib2.0-bin 2.39.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Feb 18 13:58:37 2014 InstallationDate: Installed on 2013-12-13 (67 days ago) InstallationMedia: BeLin 3.02 i386 SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1523086] Re: Ubuntu 15.10: GNOME Terminal window loses mouse cursor
** Changed in: xorg (Ubuntu) Status: Incomplete => 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/1523086 Title: Ubuntu 15.10: GNOME Terminal window loses mouse cursor Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu: Ubuntu 15.10 Package: gnome-terminal-3.16.2-1ubuntu4 Problem: Sometimes, but always when out of focus, a GNOME terminal window will lose mouse icon when it is hovered over the window. Clicking the window (and thus bringing it back in focus) restores the mouse icon. Once all that starts to happen, any URLs in the terminal stop showing pointer cursor when hovered over, but they do respond to clicks and right-clicks. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlad 1856 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a666043d-11d1-472f-8ccd-3ef13cae559a InstallationDate: Installed on 2015-11-19 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=UUID=7671ab7d-b593-4193-9a95-3f7b4389bf8f ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A770DE+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd11/26/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA770DE+: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/xorg/+bug/1523086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 459275] Re: hp-fax-cups.ppd.gz missing driver
Experienced this on a fresh install of 15.04. Used @David Girault's suggestion to work-around the issue. (Hopefully it will be resolved for 15.10). -- 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/459275 Title: hp-fax-cups.ppd.gz missing driver Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Fix Released Bug description: I have not had an issue with the Beta nor previous Alpha versions of 9.10 Kubuntu 64 bit. This issue has only occurred with a fresh install of the Release Candidate. After installing HP-gui, I have attempted to set up my HP OfficeJet 6300 Series multi-function printer on my network, running sudo hp- setup, as I always do. The HP setup finds my OfficeJet 6300, as usual, but when attempting to add the printer, the fax is not found. I receive the following error information: HP OfficeJet 6300 Series Unable to locate the HPLIP Fax PPD File hp-fax-hpcups.ppd.gz Fax setup has been disabled Again, this has not been a problem until after doing a fresh install of RC. ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xdbe78000 irq 23' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,14627309,0011' Controls : 35 Simple ctrls : 20 DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel. Date: Fri Oct 23 12:37:38 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=1fc8148f-ae59-416a-adeb-c7b5c1d024a0 HotplugNewDevices: HotplugNewMounts: MachineType: MSI MS-7309 NonfreeKernelModules: nvidia Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=/dev/mapper/lvm-root ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 09/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V9.2 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7309 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV9.2:bd09/05/2008:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7309 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/459275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
This is a Confirmed bug, but it has not been assigned, so I don't think a solution is in sight, yet. Gedit is such a critical application for me, I had to reinstall Ubuntu 14.04. As a result, I can't test if upstream GTK+3 v 4.14 solves the problem, or if this is an incorrect hunch on my part. If anyone wants to try, you can download the appropriate deb file directly from Debian and install it using dpkg -i ... AMD64 https://packages.debian.org/jessie/amd64/libgtk-3-0/download i386 https://packages.debian.org/jessie/i386/libgtk-3-0/download If you try this, remember, libgtk-3-0 v 3.14.4-1 is still in testing. Also please share your findings with us. -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
Just a quick note, launchpad automatically linked the Bugzilla bug I referenced above to a bug ~within~ Launchpad with the same number, so please don't use that automatic link. Use these links instead: https://bugzilla.gnome.org/show_bug.cgi?id=715008 https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1309785. -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
It is possible that package libgtk-3-0 (3.12.2-0ubuntu15) is the culprit... I suggest this because there is a bug where fonts become blury in text views, whenever scrollbars are displayed. See https://bugzilla.gnome.org/show_bug.cgi?id=715008 or see https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1309785. The Bugzilla bug #715008 was fixed in version 3.14 of libgtk-3-0, but Utopic (14.10) is only using version 3.12.2 of libgtk-3-0. Perhpas this current bug is also related to the way GTK+3 (libgtk-3-0) handles text views in general? ** Bug watch added: GNOME Bug Tracker #715008 https://bugzilla.gnome.org/show_bug.cgi?id=715008 -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
** Description changed: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. - Notice that the mouse pinter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. + Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
I think this is a problem that extends beyond gedit... The same issue appears in Calculator. Lainch calculator. Click in the text area. Press and hold the alt key, or type and cust some numbers. The the mouse pointer pinter is invisible while hovering over the text area. It might have something to do with the text area gtk widget. -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse pinter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking
@Jan Corazza, you are right, if I long-press Alt, the same issue occurs. However, I do not see a flickering in my gedit window, but that may be a side-effect that is visible, or not visible, depending on the user's hardware and monitor. ** Description changed: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. - Notice that the mouse cursos is invisible while hovering over the gedit window. - Notice that the gedit cursor is no longer blinking. + Notice that the mouse pinter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. - $ uname -a + $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse pinter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387219] [NEW] Mouse pointer disappears and cursor stops blinking
Public bug reported: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse cursos is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- 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/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in “gedit” package in Ubuntu: New Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press to cut the text. Notice that the mouse cursos is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
I do not have the "Google Calendar Service" option on the Online Accounts | Google screen. These are the options available to me. 1. Empathy 2. Evolution Data Server 3. Shotwell 4. Evolution Data Server 5. Photos search plugin 6. Google Drive search plugin They are all turned "On", but I only use Empathy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1323009] Re: Light DM does not show the current automatic wallpaper changer background on Login Screen
** Description changed: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). - 2. Wait about 1/2 hr an notice that the background automatically changes. + 2. Wait about 1/2 hr and notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. - 5. Now, log-out the user. + 5. Now, log-out of the user's account to show the Light DM Login screen. 6. Notice that the changed background does *not* appear on the user's - Light DM login scren. The Ligh DM screen is blank. + Light DM login scren. The Ligh DM screen is blank. (This is the issue; + the same background that was shown on the user's home screen and the + user's Lock screen should appear here). - 7. Now login to the same user. - 8. Notce there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. + 7. Now, login to the same user's account. + 8. Notice there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. (This may be a side-effect of the issue in step 6). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince 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 evince in Ubuntu. https://bugs.launchpad.net/bugs/1323009 Title: Light DM does not show the current automatic wallpaper changer background on Login Screen Status in “evince” package in Ubuntu: New Bug description: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr and notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out of the user's account to show the Light DM Login screen. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. (This is the issue; the same background that was shown on the user's home screen and the user's Lock screen should appear here). 7. Now, login to the same user's account. 8. Notice there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. (This may be a side-effect of the issue in step 6). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1323009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1323009] [NEW] Light DM does not show the current automatic wallpaper changer background on Login Screen
Public bug reported: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr an notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out the user. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. 7. Now login to the same user. 8. Notce there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1323009 Title: Light DM does not show the current automatic wallpaper changer background on Login Screen Status in “evince” package in Ubuntu: New Bug description: 1. Change background and select an automatically changing background (for example, "Ubuntu 14.04 Community Wallapers" which is defined by /usr/share/backgrounds/contest/trusty.xml). 2. Wait about 1/2 hr an notice that the background automatically changes. 3. Lock the screen and notice the changed background appears on the user's Light DM lock scren. 4. Log back in. 5. Now, log-out the user. 6. Notice that the changed background does *not* appear on the user's Light DM login scren. The Ligh DM screen is blank. 7. Now login to the same user. 8. Notce there is screen corruption / tearing for a few seconds until the user's correct dynamic background is displayed and the screen is repainted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 10:01:08 2014 InstallationDate: Installed on 2014-04-28 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1323009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311734] Re: Gedit switches to grayscale font antialiasing when the text exceeds window size
*** This bug is a duplicate of bug 1309785 *** https://bugs.launchpad.net/bugs/1309785 ** This bug has been marked a duplicate of bug 1309785 blurry font as document is longer than one page and scroll bars appear -- 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/1311734 Title: Gedit switches to grayscale font antialiasing when the text exceeds window size Status in “gedit” package in Ubuntu: New Bug description: Gedit switches to gray-scale font anti-aliasing when the text displayed does not fit within the window. To reproduce the bug: (1) Select the following font settings: Default font: Liberation Sans, 10 Document font: Liberation Sans, 10 Monospace font: Liberation Mono, 9 Window title font: Liberation Sans Bold, 10 Antialiasing: RGBA Hinting:Medium Text scaling factor:1.00 (2) Open gedit. (Optionally, make the window a little smaller so you don't have to type so much in the next step). (3) Type some text and notice that the font selections you made are being used. (Take a screen-shot for reference). (4) Continue typing more text, until the text no longer fits in the gedit window's text area. The vertical overlay scroll bar will appear at the right window edge (if you have text wrap enabled). (5) Now that the text you typed does not fit within the gedit window, notice that the text is no longer as smooth as before. (Take a screen- shot for reference). (6) Open and zoom into the screen shot from step 3, and then open and zoom into the screen shot from step 5. Notice that the colored font hinting (or anti-aliased font edges) that appearED in the screen-shot from step 3 are no longer present in the screen-shot from step 5. The fonts in the screen-shot from step 5 have gray antialiasing / hinting. I have attached a screen-shots depicting this situation. The left side of the screen shot shows gedit with good font antialiasing / hinting (from step 3). The left side of the screen shot shows gedit with bad font antialiasing / hinting (from step 5). I have also zoomed into the letter "A" in each respective scenario, and pasted that into the image to show how the font hinting / anti-aliasing changes when text does not fit into the gedit window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CurrentDesktop: Unity Date: Wed Apr 23 14:58:48 2014 ExecutablePath: /usr/bin/gedit LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1311734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311734] Re: Gedit switches to grayscale font antialiasing when the text exceeds window size
I've opened upstream bug number 729126 for this issue... https://bugzilla.gnome.org/show_bug.cgi?id=729126 ** Bug watch added: GNOME Bug Tracker #729126 https://bugzilla.gnome.org/show_bug.cgi?id=729126 -- 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/1311734 Title: Gedit switches to grayscale font antialiasing when the text exceeds window size Status in “gedit” package in Ubuntu: New Bug description: Gedit switches to gray-scale font anti-aliasing when the text displayed does not fit within the window. To reproduce the bug: (1) Select the following font settings: Default font: Liberation Sans, 10 Document font: Liberation Sans, 10 Monospace font: Liberation Mono, 9 Window title font: Liberation Sans Bold, 10 Antialiasing: RGBA Hinting:Medium Text scaling factor:1.00 (2) Open gedit. (Optionally, make the window a little smaller so you don't have to type so much in the next step). (3) Type some text and notice that the font selections you made are being used. (Take a screen-shot for reference). (4) Continue typing more text, until the text no longer fits in the gedit window's text area. The vertical overlay scroll bar will appear at the right window edge (if you have text wrap enabled). (5) Now that the text you typed does not fit within the gedit window, notice that the text is no longer as smooth as before. (Take a screen- shot for reference). (6) Open and zoom into the screen shot from step 3, and then open and zoom into the screen shot from step 5. Notice that the colored font hinting (or anti-aliased font edges) that appearED in the screen-shot from step 3 are no longer present in the screen-shot from step 5. The fonts in the screen-shot from step 5 have gray antialiasing / hinting. I have attached a screen-shots depicting this situation. The left side of the screen shot shows gedit with good font antialiasing / hinting (from step 3). The left side of the screen shot shows gedit with bad font antialiasing / hinting (from step 5). I have also zoomed into the letter "A" in each respective scenario, and pasted that into the image to show how the font hinting / anti-aliasing changes when text does not fit into the gedit window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CurrentDesktop: Unity Date: Wed Apr 23 14:58:48 2014 ExecutablePath: /usr/bin/gedit LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1311734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311734] [NEW] Gedit switches to grayscale font antialiasing when the text exceeds window size
Public bug reported: Gedit switches to gray-scale font anti-aliasing when the text displayed does not fit within the window. To reproduce the bug: (1) Select the following font settings: Default font: Liberation Sans, 10 Document font: Liberation Sans, 10 Monospace font: Liberation Mono, 9 Window title font: Liberation Sans Bold, 10 Antialiasing: RGBA Hinting:Medium Text scaling factor:1.00 (2) Open gedit. (Optionally, make the window a little smaller so you don't have to type so much in the next step). (3) Type some text and notice that the font selections you made are being used. (Take a screen-shot for reference). (4) Continue typing more text, until the text no longer fits in the gedit window's text area. The vertical overlay scroll bar will appear at the right window edge (if you have text wrap enabled). (5) Now that the text you typed does not fit within the gedit window, notice that the text is no longer as smooth as before. (Take a screen- shot for reference). (6) Open and zoom into the screen shot from step 3, and then open and zoom into the screen shot from step 5. Notice that the colored font hinting (or anti-aliased font edges) that appearED in the screen-shot from step 3 are no longer present in the screen-shot from step 5. The fonts in the screen-shot from step 5 have gray antialiasing / hinting. I have attached a screen-shots depicting this situation. The left side of the screen shot shows gedit with good font antialiasing / hinting (from step 3). The left side of the screen shot shows gedit with bad font antialiasing / hinting (from step 5). I have also zoomed into the letter "A" in each respective scenario, and pasted that into the image to show how the font hinting / anti-aliasing changes when text does not fit into the gedit window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CurrentDesktop: Unity Date: Wed Apr 23 14:58:48 2014 ExecutablePath: /usr/bin/gedit LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "Before and after screenshot showing how gedit font rendering changes when text exceeds window size." https://bugs.launchpad.net/bugs/1311734/+attachment/4094332/+files/Gedit_Good_And%20Bad_Font_Antialiasing%20%282014-04-23%29.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/1311734 Title: Gedit switches to grayscale font antialiasing when the text exceeds window size Status in “gedit” package in Ubuntu: New Bug description: Gedit switches to gray-scale font anti-aliasing when the text displayed does not fit within the window. To reproduce the bug: (1) Select the following font settings: Default font: Liberation Sans, 10 Document font: Liberation Sans, 10 Monospace font: Liberation Mono, 9 Window title font: Liberation Sans Bold, 10 Antialiasing: RGBA Hinting:Medium Text scaling factor:1.00 (2) Open gedit. (Optionally, make the window a little smaller so you don't have to type so much in the next step). (3) Type some text and notice that the font selections you made are being used. (Take a screen-shot for reference). (4) Continue typing more text, until the text no longer fits in the gedit window's text area. The vertical overlay scroll bar will appear at the right window edge (if you have text wrap enabled). (5) Now that the text you typed does not fit within the gedit window, notice that the text is no longer as smooth as before. (Take a screen- shot for reference). (6) Open and zoom into the screen shot from step 3, and then open and zoom into the screen shot from step 5. Notice that the colored font hinting (or anti-aliased font edges) that appearED in the screen-shot from step 3 are no longer present in the screen-shot from step 5. The fonts in the screen-shot from step 5 have gray antialiasing / hinting. I have attached a screen-shots depicting this situation. The left side of the screen shot shows gedit with good font antialiasing / hinting (from step 3). The left side of the screen shot shows gedit with bad font antialiasing / hinting (from step 5). I have also zoomed into the letter "A" in each respective scenario,
[Desktop-packages] [Bug 1242984] Re: Gedit context menu font is monospace
Sebastien, Please see the attached screenshot. 1. Gedit with Courier 12 as the monospaced text font. Notice the context menu uses the same monospaced font. 2. For comparison, Kate with Courier 12 as the monospaced text font. Notice the context menu uses the system's proportional font. ** Attachment added: "Gedit Context Menu with Monospaced Font" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1242984/+attachment/3893010/+files/Gedit%20context%20Menu%20compared%20with%20Kate%20context%20menu%202013-10-27-01-PS.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/1242984 Title: Gedit context menu font is monospace Status in “gedit” package in Ubuntu: Incomplete Bug description: Start Gedit in Ubuntu 13.10 Right click in the text area Notice that the context menu font is Monospaced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1242984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242984] [NEW] Gedit context menu font is monospace
Public bug reported: Start Gedit in Ubuntu 13.10 Right click in the text area Notice that the context menu font is Monospaced ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- 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/1242984 Title: Gedit context menu font is monospace Status in “gedit” package in Ubuntu: New Bug description: Start Gedit in Ubuntu 13.10 Right click in the text area Notice that the context menu font is Monospaced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1242984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1187132] Re: Fax sending broken (after upgrading to raring?)
Experiencing the same issue. Looks like a regression of Bug #153152. -- 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/1187132 Title: Fax sending broken (after upgrading to raring?) Status in “hplip” package in Ubuntu: Confirmed Bug description: (Fix/Workaround included, see below) Reproduce: Try sending a fax using the fax printer from Evince, LibreOffice, etc. Expected result: Target phone number selection dialog should appear (from hplip). Actual result: Nothing visible happens / dialog doesn't appear. OR Reproduce: Try sending a fax using the hp-sendfax utility. Cover page dialog appears, continue to the next step, add a PDF file (or anything else). Expected result: File should be listed in the file overview in hp-sendfax's dialog. Actual result: Returning from the file selection dialog does not trigger any visible action (selected file does not appear in the file list). Debugging: Saw this in the syslog: hpcupsfax[12947]: common/utils.c 253: Failed to check directory [/var/log/hp/tmp] errno[2] ... so I created /var/log/hp/tmp (parent directory already existed). Tried sending a fax again, saw this in the syslog: hpcupsfax[31352]: prnt/hpijs/hpcupsfax.cpp 685: ERROR: Unable to open Fax output file - /var/log/hp/tmp/hplipfaxLog_sPUT65 for writing Played with permissions on /var/log/hp/tmp until it worked. root:lp/775 sounds halfway sane and works for me. lp:.../755 would probably be okay as well. Suggested fix: Ensure that /var/log/hp/tmp gets pre-created with sane permissions or patch/configure hplip to use another path maybe (?). I am not entirely sure when this bug got introduced. I had sent my last fax about two months ago, so it was certainly before the upgrade to raring. I assume this bug is not printer-specific. Similar issue in Fedora Core: https://bugs.launchpad.net/hplip/+bug/1055510 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: hplip 3.13.3-1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Jun 3 22:50:14 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-06-17 (717 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: device for Officejet_6500_E709a: hp:/net/Officejet_6500_E709a?zc=HPD8265E device for Officejet_6500_E709a_fax: hpfax:/net/Officejet_6500_E709a?zc=HPD8265E MachineType: Gigabyte Technology Co., Ltd. GA-880GA-UD3H MarkForUpload: True Papersize: a4 PpdFiles: Officejet_6500_E709a: HP Officejet 6500 e709a, hpcups 3.13.3 Officejet_6500_E709a_fax: HP Fax hpcups ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-22-generic root=UUID=93f6756c-a6cb-4dde-9875-e61e6daacefa ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to raring on 2013-04-25 (39 days ago) dmi.bios.date: 11/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-880GA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1187132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1090645] Re: "Wired connection 1" deleted after creating "Wired connection 2" and Rebooting
This is still an issue in 13.04. Would someone please test this using the steps above and confirm? -- 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/1090645 Title: "Wired connection 1" deleted after creating "Wired connection 2" and Rebooting Status in “network-manager” package in Ubuntu: New Bug description: I've experienced this three times on a fresh install of Ubuntu 12.10 x64. If you create a new wired network connection, the original wired connection is deleted after a reboot. Steps to recreate Bug... Note that "Wired connection 1" is the default connection. From the Network Manager applet, select Edit Connections. Select the "Wired" tab. Click "Add". Enter Connection name: "Wired connection 2" Select the Device MAC address from the drop down list. Select the "IPv4 Settings" tab. Select "Automatic (DHCP) addresses only" from the Method dropdown. Enter DNS Servers (ex. 8.8.8.8, 8.8.4.4) Click Save. The new connection ("Wired connection 2") and the existing connection ("Wired connection 1") are visible in the Network Manager applet. Test both connections ("Wired connection 1" and "Wired connection 2") and confirm you are able to connect. Select "Wired connection 1" and let it connect. Shut down the computer. Turn on the computer. Note that "Wired connection 2" is the only connection available. "Wired connection 1" has dissapeared fro mthe Network Manager applet. Also note that "Wired connection 1" does not appear in /etc/NetworkManager/system-connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1090645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070303] Re: Lightdm don't show user wallpaper
I have not experienced this issue with fresh install of 12.10 or 13.04, so I have marked the bug as fix released. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1070303 Title: Lightdm don't show user wallpaper Status in “lightdm” package in Ubuntu: Fix Released Bug description: Ubuntu 12.10, Gnome Classic with compiz When showing login screen, it shows ubuntu default wallpaper, and not user wallpaper. My wallpaper is not in ubuntu's list, but from a different folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1070303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option
I just posted a work-around on Ask Ubuntu, until this gets resolved. (See http://askubuntu.com/questions/308385/how-to-start-empathy-hidden- in-13-04). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1179180 Title: Impossible to open Empathy contact list window if already started with '-h' option Status in “empathy” package in Ubuntu: Confirmed Bug description: If I add Empathy to 'Startup Applications' to start it with '-h' option, I'll never be able to open the contact list window. Tried: - If query with 'ps -ef | grep emapthy', I can see empathy is running. - If run 'empathy' from command line, the command exits without any output, but nothing happens after that. - If choose 'Empathy Internet Messaging' from Unity Dashboard, nothing happens. - If choose from the locked lens, I can see the icon "blinks slowly" (if you know what I mean, I'm not native speaker of English), and then it stops blinking, nothing happens after that. However, if I didn't start Empathy with '-h' option, everything seems normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 12 18:27:52 2013 InstallationDate: Installed on 2012-08-12 (273 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1179180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option
I'm able to reproduce this... 1. Make sure Empathy is not running. If it is running quit it, or kill it from the system monitor. 2. In a terminal, start empathy using the "start hidden option, as follows: $ empathy -h 3. Notice that empathy is now running in system moitor. 4. From the messaging menu indicator applet, select Empathy. 5. The Empathy Contact List window does *not* appear, as expected. 6. Now try to start Empathy from the Unity Dash. 7. Again, the Empathy Contact List window does not appear, as expected. 8. Notice that empathy is still running in the background in system moitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1179180 Title: Impossible to open Empathy contact list window if already started with '-h' option Status in “empathy” package in Ubuntu: Confirmed Bug description: If I add Empathy to 'Startup Applications' to start it with '-h' option, I'll never be able to open the contact list window. Tried: - If query with 'ps -ef | grep emapthy', I can see empathy is running. - If run 'empathy' from command line, the command exits without any output, but nothing happens after that. - If choose 'Empathy Internet Messaging' from Unity Dashboard, nothing happens. - If choose from the locked lens, I can see the icon "blinks slowly" (if you know what I mean, I'm not native speaker of English), and then it stops blinking, nothing happens after that. However, if I didn't start Empathy with '-h' option, everything seems normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 12 18:27:52 2013 InstallationDate: Installed on 2012-08-12 (273 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1179180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183489] Re: Empathy Contact List does not un-hide
*** This bug is a duplicate of bug 1179180 *** https://bugs.launchpad.net/bugs/1179180 ** This bug has been marked a duplicate of bug 1179180 Impossible to open Empathy contact list window if already started with '-h' option -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1183489 Title: Empathy Contact List does not un-hide Status in “telepathy-gabble” package in Ubuntu: New Bug description: If Empathy is started in hidden mode (using the -h option) then you can not show the Empathy contacts list window. Steps to reproduce: 1. Make sure Empathy is not running. If it is running quit it, or kill it from the system monitor. 2. In a terminal, start empathy using the "start hidden option, as follows: $ empathy -h 3. Notice that empathy is now running in system moitor. 4. From the messaging menu indicator applet, select Empathy. 5. The Empathy Contact List window does *not* appear, as expected. 6. Now try to start Empathy from the Unity Dash. 7. Again, the Empathy Contact List window does not appear, as expected. 8. Notice that empathy is still running in the background in system moitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1183489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183489] [NEW] Empathy Contact List does not un-hide
*** This bug is a duplicate of bug 1179180 *** https://bugs.launchpad.net/bugs/1179180 Public bug reported: If Empathy is started in hidden mode (using the -h option) then you can not show the Empathy contacts list window. Steps to reproduce: 1. Make sure Empathy is not running. If it is running quit it, or kill it from the system monitor. 2. In a terminal, start empathy using the "start hidden option, as follows: $ empathy -h 3. Notice that empathy is now running in system moitor. 4. From the messaging menu indicator applet, select Empathy. 5. The Empathy Contact List window does *not* appear, as expected. 6. Now try to start Empathy from the Unity Dash. 7. Again, the Empathy Contact List window does not appear, as expected. 8. Notice that empathy is still running in the background in system moitor. ** Affects: telepathy-gabble (Ubuntu) Importance: Undecided Status: New ** Tags: 13.04 empathy ubuntu x64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1183489 Title: Empathy Contact List does not un-hide Status in “telepathy-gabble” package in Ubuntu: New Bug description: If Empathy is started in hidden mode (using the -h option) then you can not show the Empathy contacts list window. Steps to reproduce: 1. Make sure Empathy is not running. If it is running quit it, or kill it from the system monitor. 2. In a terminal, start empathy using the "start hidden option, as follows: $ empathy -h 3. Notice that empathy is now running in system moitor. 4. From the messaging menu indicator applet, select Empathy. 5. The Empathy Contact List window does *not* appear, as expected. 6. Now try to start Empathy from the Unity Dash. 7. Again, the Empathy Contact List window does not appear, as expected. 8. Notice that empathy is still running in the background in system moitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1183489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070303] Re: Lightdm don't show user wallpaper
I did a reinstall of 12.10 and the problem went away. Of course, the image that I want to be displayed on the screen must still be placed directly in the user's ~/Pictures folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1070303 Title: Lightdm don't show user wallpaper Status in “lightdm” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10, Gnome Classic with compiz When showing login screen, it shows ubuntu default wallpaper, and not user wallpaper. My wallpaper is not in ubuntu's list, but from a different folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1070303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp