[Desktop-packages] [Bug 1729433]
Reopening this bug. An update to a newer version via the PPA. The Calc seems to be steady but I've appeared to still be having the issue on LibreOffice Draw even after an update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027790] [NEW] bash completion doesn't show "remove" option
Public bug reported: Flatpak package contains bash script for bash completion feature. If I say `flatpak in`, I will got `info` and `install` options. Flatpak autocomplete options doesn't work for `remove` option. If I say `flatpak rem`, I will got only `remote`, and `remove` will not be suggested. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: flatpak 1.14.4-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 13:30:21 2023 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2027790 Title: bash completion doesn't show "remove" option Status in flatpak package in Ubuntu: New Bug description: Flatpak package contains bash script for bash completion feature. If I say `flatpak in`, I will got `info` and `install` options. Flatpak autocomplete options doesn't work for `remove` option. If I say `flatpak rem`, I will got only `remote`, and `remove` will not be suggested. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: flatpak 1.14.4-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 14 13:30:21 2023 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2027790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021929] [NEW] upgrade to exiv2 0.28.0
Public bug reported: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/2021929 Title: upgrade to exiv2 0.28.0 Status in exiv2 package in Ubuntu: New Bug description: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990277] [NEW] Nautilus crashes when open a new window from the panel
Public bug reported: Nautilus can add it's favorites to the panel icon. So, the user can right-click on an icon to open any favorites folder. If a Nautilus windows is already open, opening any folder from favorites crashes nautilus. journalctl -e: сен 20 15:32:42 Compy kernel: nautilus[107750]: segfault at 0 ip sp 7ffe8815c688 error 14 in nautilus[5612a329f000+> сен 20 15:32:42 Compy kernel: Code: Unable to access opcode bytes at RIP 0xffd6. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 15:30:40 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/usr/bin/fish SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-06-08 (103 days ago) usr_lib_nautilus: file-roller3.42.0-1 nautilus-share 0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1990277 Title: Nautilus crashes when open a new window from the panel Status in nautilus package in Ubuntu: New Bug description: Nautilus can add it's favorites to the panel icon. So, the user can right-click on an icon to open any favorites folder. If a Nautilus windows is already open, opening any folder from favorites crashes nautilus. journalctl -e: сен 20 15:32:42 Compy kernel: nautilus[107750]: segfault at 0 ip sp 7ffe8815c688 error 14 in nautilus[5612a329f000+> сен 20 15:32:42 Compy kernel: Code: Unable to access opcode bytes at RIP 0xffd6. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 15:30:40 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/usr/bin/fish SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-06-08 (103 days ago) usr_lib_nautilus: file-roller3.42.0-1 nautilus-share 0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980936] [NEW] Flatpaked apps doesn't start under wayland, if called from another app
Public bug reported: I run Gnome Wayland session and I have several apps installed from flatpak - gthumb and evince are among them. If I download a file using a web-browser and try to open this file from the browser's "download" menu, the PDF or JPG files won't open. I can fix it by setting up evince or gthumb to run x11 by disabling wayland with flatseal. Web-browser is not installed by a flatpak or snap, so it can be vivaldi or yandex-browser. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 12:09:43 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-06-08 (28 days ago) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1980936 Title: Flatpaked apps doesn't start under wayland, if called from another app Status in flatpak package in Ubuntu: New Bug description: I run Gnome Wayland session and I have several apps installed from flatpak - gthumb and evince are among them. If I download a file using a web-browser and try to open this file from the browser's "download" menu, the PDF or JPG files won't open. I can fix it by setting up evince or gthumb to run x11 by disabling wayland with flatseal. Web-browser is not installed by a flatpak or snap, so it can be vivaldi or yandex-browser. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 12:09:43 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-06-08 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1980936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978707] [NEW] Dragging windows cause gnome-shell to hangs up temporarily
Public bug reported: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Запись экрана от 14.06.2022 19:58:43.webm" https://bugs.launchpad.net/bugs/1978707/+attachment/5597258/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2014.06.2022%2019%3A58%3A43.webm -- 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/1978707 Title: Dragging windows cause gnome-shell to hangs up temporarily Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
I often even mix multiple languages in the same text, for various reasons. In a multi-language context, this is quite common. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
When I wrote "can type", I meant of course with the spellchecker working in the language, assuming I have the right dictionary installed, without the spellchecker trying to tell me that **all** my _words_ are _wrong_ and _everything_ has a _red_ _underline_, which is _quite_ _annoying_. (Underline for illustration of the effect.) It would be quite a pity to do all this work in this bug, and then the spellchecker still assumes English, just because Gmail or Yahoo Mail or RoundCube or whatever web app is in English. How would RoundCube know which language I am writing the email in? I write emails (and text in webapps) in multiple languages, so this logic as stated in comment 38 would render the fix here moot in such situations and keep the spellchecker broken for all languages but one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
> element or document language ... is ... en-US ..., we'll only enable the en-US dictionary So, if Gmail or Yahoo or RoundCube document was set to "en-US", that means I can only type English emails? Doesn't that counter the purpose of this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
I just came across this in Jammy (for the first time) as well. I have
two icom ham radio transceivers that use this chipset and the first one
detected IC-7300 was not usable until brltty was removed.
USB ID: 10c4:ea60
looking at device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""
ATTR{power/async}=="disabled"
ATTR{power/control}=="auto"
ATTR{power/runtime_active_kids}=="0"
ATTR{power/runtime_active_time}=="0"
ATTR{power/runtime_enabled}=="disabled"
ATTR{power/runtime_status}=="unsupported"
ATTR{power/runtime_suspended_time}=="0"
ATTR{power/runtime_usage}=="0"
looking at parent device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="cp210x"
ATTRS{port_number}=="0"
ATTRS{power/async}=="enabled"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_kids}=="0"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_enabled}=="disabled"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{power/runtime_usage}=="0"
looking at parent device
'/devices/pci:00/:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0':
KERNELS=="3-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="cp210x"
ATTRS{authorized}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bInterfaceProtocol}=="00"
ATTRS{bInterfaceSubClass}=="00"
ATTRS{bNumEndpoints}=="02"
ATTRS{interface}=="CP2102 USB to UART Bridge Controller"
ATTRS{power/async}=="enabled"
ATTRS{power/runtime_active_kids}=="0"
ATTRS{power/runtime_enabled}=="enabled"
ATTRS{power/runtime_status}=="active"
ATTRS{power/runtime_usage}=="1"
ATTRS{supports_autosuspend}=="1"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/874181
Title:
brltty daemon prevents creation of ttyUSB0 device link
Status in brltty package in Ubuntu:
Confirmed
Status in brltty source package in Oneiric:
Fix Released
Bug description:
Impact:
This bug is somewhat hardware specific, affecting all users of the USB serial
controller, device 10c4:ea60.
Test case:
With the current version of brltty in Oneiric, brltty takes over any device
using the above mentioned USB serial controller, whether it is a Braille
display or not. This is because one of Brltty's supported displays uses this
USB serial control internally for ocmmunication. The brltty package in
oneiric-proposed has the udev rule for this controller commented out, allowing
other users of devices based on this controller to work properly.
Regression potential:
All users of the supported Seika will have to load Brltty manually, as the
udev rule for their device is commented out, to allow other USB serial
controller users to use their device as a proper serial device.
Original description follows:
After upgrading from Ubuntu 11.04 to 11.10, I no longer found a
'/dev/ttyUSB0' for my serial-to-USB converter. The device is part of
a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products,
Inc. CP210x Composite Device".
Every time I plugged in the device, dmesg showed the device coming up
and 'brltty' did *something* to it. At this point, no device was
present in '/dev'.
[ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected
[ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd
[ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0
[ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty'
sets config #1
After removing 'brltty', the '/dev/ttyUSB0' device appears again like
it used to.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: brltty (not installed)
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Fri Oct 14 14:39:29 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=
LC_TIME=C
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: brltty
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I can say, that I have this dialog only if I have a flatpak updates, not apt updates. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
As far as I can say, the dialog itself works as intended. The bug is, that the Ubuntu box is rebooting instead of turninging off. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists
Public bug reported: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session ** Attachment added: "Снимок экрана от 2022-02-01 11-25-20.png" https://bugs.launchpad.net/bugs/1962346/+attachment/5563780/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202022-02-01%2011-25-20.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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939211] [NEW] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
Public bug reported: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: Screen flickering after upgrading from 5.8 kernel to 5.11 kernel Status in xorg package in Ubuntu: New Bug description: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color P
[Desktop-packages] [Bug 1927970] Re: Maximised gnome-terminal not returning to normal size
Looks like there is a matching upstream https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359 -- 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/1927970 Title: Maximised gnome-terminal not returning to normal size Status in gnome-terminal package in Ubuntu: New Bug description: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927970] [NEW] Maximised gnome-terminal not returning to normal size
Public bug reported: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1927970 Title: Maximised gnome-terminal not returning to normal size Status in gnome-terminal package in Ubuntu: New Bug description: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924964] [NEW] screen glitches
Public bug reported: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924964 Title: screen glitches Status in xorg package in Ubuntu: New Bug description: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But
[Desktop-packages] [Bug 1919071] [NEW] Gsd media keys crashed SIGSEGV
Public bug reported: Hi there Extremely new user and a newly built pc. I’ve experienced some crashes / system locks and am hoping for some tips and thoughts to help me out. The error message I received last night is as follows: Executable gsd-media-keys Package gnome settings daemon 3.36.q Title gsd media keys crashed with SIGSEGV in tcache get() I’m on app version 2.20.11-0ubuntu27.16 On AMD with integrated graphics I wondered if it was to do with the usb wireless HP keyboard? However this morning I had Firefox crash. I am currently using WiFi via my ASUS B450 onboard WiFi which again I wondered might be the cause? Appreciate some help. I’m a little experienced with hardware and PCs albeit very, very new to Ubuntu and Linux! Appreciated ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1919071 Title: Gsd media keys crashed SIGSEGV Status in gnome-settings-daemon package in Ubuntu: New Bug description: Hi there Extremely new user and a newly built pc. I’ve experienced some crashes / system locks and am hoping for some tips and thoughts to help me out. The error message I received last night is as follows: Executable gsd-media-keys Package gnome settings daemon 3.36.q Title gsd media keys crashed with SIGSEGV in tcache get() I’m on app version 2.20.11-0ubuntu27.16 On AMD with integrated graphics I wondered if it was to do with the usb wireless HP keyboard? However this morning I had Firefox crash. I am currently using WiFi via my ASUS B450 onboard WiFi which again I wondered might be the cause? Appreciate some help. I’m a little experienced with hardware and PCs albeit very, very new to Ubuntu and Linux! Appreciated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1919071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007]
I also see a large number of ns* temporary files that Thunderbird leaves behind in `/tmp/`. This is quite annoying. I've currently got almost 1000 ns* files there: ``` /tmp/nsemail-328.eml /tmp/nsemail-622.eml /tmp/nsmail-2.pdf /tmp/nsemail-329.eml /tmp/nsemail-623.eml /tmp/nsmail-2.png /tmp/nsemail-32.eml /tmp/nsemail-624.eml /tmp/nsmail-2.tmp /tmp/nsemail-330.eml /tmp/nsemail-625.eml /tmp/nsmail-30.tmp /tmp/nsemail-331.eml /tmp/nsemail-626.eml /tmp/nsmail-31.tmp /tmp/nsemail-332.eml /tmp/nsemail-627.eml /tmp/nsmail-32.tmp /tmp/nsemail-333.eml /tmp/nsemail-628.eml /tmp/nsmail-33.tmp /tmp/nsemail-334.eml /tmp/nsemail-629.eml /tmp/nsmail-34.tmp /tmp/nsemail-335.eml /tmp/nsemail-62.eml /tmp/nsmail-3.eml /tmp/nsemail-336.eml /tmp/nsemail-630.eml /tmp/nsmail-3.jpeg /tmp/nsemail-337.eml /tmp/nsemail-631.eml /tmp/nsmail-3.pdf /tmp/nsemail-338.eml /tmp/nsemail-632.eml /tmp/nsmail-3.tmp /tmp/nsemail-339.eml /tmp/nsemail-633.eml /tmp/nsmail-4.eml /tmp/nsemail-33.eml /tmp/nsemail-634.eml /tmp/nsmail-4.jpeg /tmp/nsemail-340.eml /tmp/nsemail-635.eml /tmp/nsmail-4.pdf /tmp/nsemail-341.eml /tmp/nsemail-636.eml /tmp/nsmail-4.tmp /tmp/nsemail-342.eml /tmp/nsemail-637.eml /tmp/nsmail-5.eml /tmp/nsemail-343.eml /tmp/nsemail-638.eml /tmp/nsmail-5.jpeg /tmp/nsemail-344.eml /tmp/nsemail-639.eml /tmp/nsmail-5.pdf /tmp/nsemail-345.eml /tmp/nsemail-63.eml /tmp/nsmail-5.tmp /tmp/nsemail-346.eml /tmp/nsemail-640.eml /tmp/nsmail-6.eml /tmp/nsemail-347.eml /tmp/nsemail-641.eml /tmp/nsmail-6.jpeg /tmp/nsemail-348.eml /tmp/nsemail-642.eml /tmp/nsmail-6.pdf /tmp/nsemail-349.eml /tmp/nsemail-643.eml /tmp/nsmail-6.tmp /tmp/nsemail-34.eml /tmp/nsemail-644.eml /tmp/nsmail-7.jpeg /tmp/nsemail-350.eml /tmp/nsemail-645.eml /tmp/nsmail-7.pdf /tmp/nsemail-351.eml /tmp/nsemail-646.eml /tmp/nsmail-7.tmp /tmp/nsemail-352.eml /tmp/nsemail-647.eml /tmp/nsmail-8.pdf /tmp/nsemail-353.eml /tmp/nsemail-648.eml /tmp/nsmail-8.tmp /tmp/nsemail-354.eml /tmp/nsemail-649.eml /tmp/nsmail-9.pdf /tmp/nsemail-355.eml /tmp/nsemail-64.eml /tmp/nsmail-9.tmp /tmp/nsemail-356.eml /tmp/nsemail-650.eml /tmp/nsmail.asc /tmp/nsemail-357.eml /tmp/nsemail-651.eml /tmp/nsmail.docx /tmp/nsemail-358.eml /tmp/nsemail-652.eml /tmp/nsmail.eml /tmp/nsemail-359.eml /tmp/nsemail-653.eml /tmp/nsmail.ics /tmp/nsemail-35.eml /tmp/nsemail-654.eml /tmp/nsmail.jpeg /tmp/nsemail-360.eml /tmp/nsemail-655.eml /tmp/nsmail.odt /tmp/nsemail-361.eml /tmp/nsemail-656.eml /tmp/nsmail.pdf /tmp/nsemail-362.eml /tmp/nsemail-657.eml /tmp/nsmail.png /tmp/nsemail-363.eml /tmp/nsemail-658.eml /tmp/nsmail.tmp /tmp/nsemail-364.eml /tmp/nsemail-659.eml /tmp/nsmail.zip /tmp/nsemail-365.eml /tmp/nsemail-65.eml ``` This is just an excerpt. There are many more, total 989 files. And that although I've had already cleaned them up relatively recently already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair
[Desktop-packages] [Bug 1909037] [NEW] Weird sorting occurs on numbers sequence filenames
Public bug reported: I have a lot of files from the camera, named ACE_0001.nef, ACE_0002.nef and so on. I imported these files into darktable. Darktable places a corresponding xmp file near every nef file, resulting in ACE_0001.nef.xmp, ACE_0002.nef.xmp and so on. The problem is, for files less then 100 in numbers, xmp files are sorted before nef files, but starting ACE_0100.nef* xmp files are sorted after nef. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 Uname: Linux 5.10.0-051000rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 23:16:38 2020 InstallationDate: Installed on 2019-11-16 (402 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-02 (234 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "Снимок экрана от 2020-12-22 23-17-21.png" https://bugs.launchpad.net/bugs/1909037/+attachment/5445993/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-12-22%2023-17-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1909037 Title: Weird sorting occurs on numbers sequence filenames Status in nautilus package in Ubuntu: New Bug description: I have a lot of files from the camera, named ACE_0001.nef, ACE_0002.nef and so on. I imported these files into darktable. Darktable places a corresponding xmp file near every nef file, resulting in ACE_0001.nef.xmp, ACE_0002.nef.xmp and so on. The problem is, for files less then 100 in numbers, xmp files are sorted before nef files, but starting ACE_0100.nef* xmp files are sorted after nef. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 Uname: Linux 5.10.0-051000rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 23:16:38 2020 InstallationDate: Installed on 2019-11-16 (402 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-02 (234 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1909037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904924] [NEW] Xorg freeze
Public bug reported:
Sounds like a fairly common problem according to [this
page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
freezes, and while I'm still able to move the mouse around, I can't
successfully click or type at any windows. It takes about 30 seconds for
gnome-shell to restart, and then the clock starts running (and the
system monitor starts updating) again.
This problem has been bugging me for a few months now, but I'm not sure
when it started. It tends to happen in clumps; sometimes it will go
several days without happening, but once it starts it often happens
twice pretty quickly, and often a few times across a day. I haven't been
able to isolate what causes it, but more often than not it has something
to do with clicking on a window or tab in Chrome. (It definitely also
happens in other applications, though.)
Every time it happens, dmesg contains a stack dump for gnome-shell
("page allocation failure"). I can provide gists of these dumps if
that's helpful (and not already included in the apport data). So I'm not
sure if this is actually an xorg thing or a gnome-shell thing.
% lsb_release -rd
Description:Ubuntu 20.10
Release:20.10
% dpkg -l xorg* gnome-shell* | grep '^ii'
ii gnome-shell 3.38.1-1ubuntu1.1
amd64graphical shell for the GNOME desktop
ii gnome-shell-common 3.38.1-1ubuntu1.1
all common files for the GNOME graphical shell
ii gnome-shell-extension-appindicator 34-1
all AppIndicator/KStatusNotifierItem support for GNOME Shell
ii gnome-shell-extension-desktop-icons 20.04.0+git20200908-1
all desktop icon support for GNOME Shell
ii gnome-shell-extension-prefs 3.38.1-1ubuntu1.1
amd64tool to enable / disable GNOME Shell extensions
ii gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1
all Display system information in GNOME Shell status bar
ii gnome-shell-extension-system76-power 2.0.0~1602857239~20.10~914b531~dev
all Gnome-shell extension for System76 Power Management
ii gnome-shell-extension-ubuntu-dock68ubuntu20.10.1
all Ubuntu Dock for GNOME Shell
ii gnome-shell-extensions 3.38.1-1
all Extensions to extend functionality of GNOME Shell
ii xorg 1:7.7+19ubuntu15
amd64X.Org X Window System
ii xorg-docs-core 1:1.7.1-1.1
all Core documentation for the X.org X Window System
ii xorg-sgml-doctools 1:1.11-1
all Common tools for building X.Org SGML documentation
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic
5.8.17
Uname: Linux 5.8.0-7630-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59
UTC 2020
GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
BootLog:
CasperMD5CheckResult: skip
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 15:05:17 2020
DistUpgraded: 2020-11-16 10:15:57,099 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if
00 [VGA controller])
Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
InstallationDate: Installed on 2018-01-19 (1035 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System76, Inc. Wild Dog Performance
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7630-generic
root=UUID=e12a4ebc-6235-4471-a2da-3f9da9d48f74 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to groovy on 2020-11-16
[Desktop-packages] [Bug 1903910] Re: Mouse settings ignored when plugging in a new mouse
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 > @Ben: Can you please install the mutter packages from this PPA I can confirm that the suggested package works - I've tried with multiple mice and all keep adopt the expected settings when I unplug and plug them in again. -- 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/1903910 Title: Mouse settings ignored when plugging in a new mouse Status in gnome-control-center package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903910] Re: Primary mouse button setting reverts to default
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 I can also confirm that gsettings shows the correct value when disconnecting the mouse, but when the mouse is reconnected, the setting is reverted silently (gsettings and gnome-control-center show the wrong value). gsettings and gnome-control-center are in sync, but both wrong. Steps to reproduce: 1) Plug in two USB mice. 2) Set Primary Button: Right. 3) Confirm - both buttons work as expected on both mice, gsettings shows "left-handed true" 4) Unplug one mouse. 5) The remaining mouse works fine, gsettings and gnome-control-center both show the right setting. 6) Plug the second mouse in again. 7) gsettings and gnome-control-center still show the same setting, however the two mice have different behaviour. Summary: Mouse settings are not applied to a new mouse. ** Summary changed: - Primary mouse button setting reverts to default + Mouse settings ignored when plugging in a new mouse -- 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/1903910 Title: Mouse settings ignored when plugging in a new mouse Status in gnome-control-center package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903910] Re: Primary mouse button setting reverts to default
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 After a bit more debug, it appears the problem occurs when any external mouse is disconnected and reconnected (ruling out the USB hub and switch as a factor). -- 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/1903910 Title: Primary mouse button setting reverts to default Status in gnome-control-center package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903910] [NEW] Primary mouse button setting reverts to default
Public bug reported: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1903910 Title: Primary mouse button setting reverts to default Status in gnome-control-center package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
** Description changed: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland - applications scales fine — 200% on the primary monitor and 100% on the - secondary. + applications scales 200% on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) -- 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/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales 200% on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] [NEW] XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
Public bug reported: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales fine — 200% on the primary monitor and 100% on the secondary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "LowDPI monitor is primary" https://bugs.launchpad.net/bugs/1903383/+attachment/5432115/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-11-07%2012-26-28.png -- 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/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales fine — 200% on the primary monitor and 100% on the secondary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
** Attachment added: "HiDPI monitor is primary" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+attachment/5432118/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-11-07%2012-26-50.png -- 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/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales fine — 200% on the primary monitor and 100% on the secondary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme and scaling not honoured for cursor themes not included in gtk-common-themes
> @Ben, thanks for the replies, when you wrote that after restarting the theme is still wrong, that is when using whiteglass which we determined to be due to having it missing from the snap themes right? That's correct - the theme change and scaling occurred when I set the desktop mouse cursor to Whiteglass. When moving the cursor over Chromium, the cursor reverted changed theme (to DMZ-Black, I think) and scaled down small. > could you confirm that it works if you select e.g yaru or adwaita? I don't appear to have Adwaita mouse theme and Yaru looks identical to DMZ-Black, so I couldn't tell you if the theme changes or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: [snap] Mouse pointer theme and scaling not honoured for cursor themes not included in gtk-common-themes Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
*** This bug is a duplicate of bug 1900334 *** https://bugs.launchpad.net/bugs/1900334 Not a problem whatsoever. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
According to #1900334, the snap doesn't include all cursor themes. If I change my desktop mouse cursor theme to DMZ-Black and restart Chromium, the cursor size issue is fixed (i.e. Chromium cursor size matches the desktop size). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme not honoured
> $ snap revert chromium I've already tried revert, however I'd also tried changing to other channels (edge, etc.) beforehand, so revert didn't revert back to the original working version. I was actually hoping to be able to list and revert to an arbitrary revision, but saw no obvious way to do that. > Did you restart chromium after changing the configuration? Restarting after changing settings seems to help - it fixes the cursor size, but not the theme (ref: #1900472). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: [snap] Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme not honoured
- which desktop and ubuntu serie do you use? Ubuntu 20.04 (gnome desktop) - was it working fine before? Yes. If someone could let me know how I can roll back to older versions of the snap, I can test and report exactly which version broke, however I the version I listed above introduces the issue. - do you use the default cursor theme or a custom one? I'm currently using Whiteglass, but regardless of the cursor theme I select, it always appears to revert to DMZ-Black on Chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: [snap] Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
If I revert to 100% scaling, the mouse cursor stays the same (minuscule) size when transitioning between Chromium and other windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
** Attachment added: "Image showing Chromium cursor size (and theme)." https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+attachment/5424336/+files/mouse_cursor_desktop_theme.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
Please ignore the last image - attached in error. ** Attachment added: "Image showing Chromium cursor size (and theme)." https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+attachment/5424337/+files/mouse_cursor_chromium_theme.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue
** Attachment added: "Image showing native cursor size (and theme)." https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+attachment/5424335/+files/mouse_cursor_desktop_theme.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme not honoured
Good to hear the cause has been identified. Unfortunately, the scaling is the worst problem here - I can live with having to use a different cursor, but on a 13" 4k monitor laptop screen, the scaling issue makes the cursor practically invisible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: [snap] Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme not honoured
New ticket created: #1900472 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: [snap] Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900472] [NEW] [snap] Mouse pointer scaling issue
Public bug reported: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900472 Title: [snap] Mouse pointer scaling issue Status in chromium-browser package in Ubuntu: New Bug description: Note: Issue originally reported in ticket #1900334, however two symptoms are seen, hence creating a second ticket to track each symptom separately. Original description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif This ticket is intended to track the pointer scaling issue shown in the gif above. It's worth noting that this issue is seen on a HiDPI machine (4k monitor) with 200% desktop scaling in display settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
** Attachment added: "Incorrect theme (Chromium)" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+attachment/5424279/+files/mouse_cursor_chromium_theme.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Incomplete Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
Apologies, I'll clarify - when the mouse cursor transitions to Chromium, the theme changes _and_ the pointer becomes tiny (as in the gif I linked). It's worth noting that I'm on a HiDPI laptop (4k screen) with 200% scaling enabled. The mouse pointer theme selected on the desktop is Whiteglass, however it seems to transition to a small version of either DMZ-Black or Yaru (I can't see any difference between the two) on Chromium. The Chromium mouse theme I see looks the same as that in the gif (albeit smaller). ** Attachment added: "Expected theme (desktop)" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+attachment/5424278/+files/mouse_cursor_desktop_theme.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: Incomplete Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
In addition to the mouse pointer/cursor scaling down to tiny size, the theme also appears to revert to something other than the system setting therefore this bug may be a duplicate of, or related to: #1838008. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
Possibly related - I presume the following means the "core" and "snap- store" snaps were also updated at the same time: > snap changes chromium ID Status Spawn Ready Summary 24 Donetoday at 08:00 BST today at 08:05 BST Auto-refresh snaps "snap-store", "core", "chromium" > snap info core name: core summary: snapd runtime environment publisher: Canonical✓ store-url: https://snapcraft.io/core contact: sn...@canonical.com license: unset description: | The core runtime environment for snapd type: core snap-id: 99T7MUlRhtI3U0QFgl5mXXESAiSwt776 tracking: latest/stable refresh-date: today at 08:03 BST channels: latest/stable:16-2.472020-10-14 (10126) 102MB - latest/candidate: 16-2.47.1 2020-10-13 (10185) 102MB - latest/beta: 16-2.47.1 2020-10-08 (10185) 102MB - latest/edge: 16-2.47.1+git2428.1f1ad3fe 2020-10-18 (10243) 102MB - installed: 16-2.47 (10126) 102MB core -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
Likewise for edge (88.0.4292.2). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
Also affects the current beta version - updated with: > snap switch --beta chromium > snap refresh > snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/beta refresh-date: today at 15:46 BST channels: latest/stable:86.0.4240.75 2020-10-15 (1350) 170MB - latest/candidate: 86.0.4240.75 2020-10-15 (1350) 170MB - latest/beta: 87.0.4280.20 2020-10-16 (1357) 172MB - latest/edge: 88.0.4292.2 2020-10-16 (1358) 173MB - installed: 87.0.4280.20(1357) 172MB - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
Version info: > snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 08:05 BST channels: latest/stable:86.0.4240.75 2020-10-15 (1350) 170MB - latest/candidate: 86.0.4240.75 2020-10-15 (1350) 170MB - latest/beta: 87.0.4280.20 2020-10-16 (1357) 172MB - latest/edge: 88.0.4292.2 2020-10-16 (1358) 173MB - installed: 86.0.4240.75(1350) 170MB - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] Re: Mouse pointer theme not honoured
It's worth noting that this issue does not affect the Chrome release of the same version (86.0.4240.75), which I have installed for comparison - i.e. this appears to be specific to snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900334] [NEW] Mouse pointer theme not honoured
Public bug reported: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900334 Title: Mouse pointer theme not honoured Status in chromium-browser package in Ubuntu: New Bug description: Since updating to the latest version, the mouse pointer/cursor in Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown on the desktop (or other non-snap applications). The symptom looks identical to that shown on this ticket: https://github.com/brave/browser-laptop/issues/9772 See this gif: https://user- images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a- a1a32ff3af01.gif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Noticed that I couldn't use my headset mic on any apps in the past month, but the above reports are describing the same behavioural issues as I am seeing soI think I am hitting the same problem. Using Sennheisser HD 4.40BT headphones on a System76 Gazelle. Connects default audio through headphones with the A2DP profile as expected when connecting through BT, but the Internal Microphone stays selected for input. Trying to select the HD4.4 microphone setting does nothing, and no signal of any kind comes through the input. Switching to the HFP/HSP profile also leads to a break in audio, and after the A2DP setting is shown as unavailable until I wipe the userland pulse configs. It cuts off the audio through the headset and ends up in a bad configuration where I have to turn BT off and on again to reconnect and when it does, the configuration is stuck on HFP/HSP and in mono. No audio through the headset mic can be picked up through any pulseaudio-enabled monitors, all showing zero input with whatever configuration or set-up I can muster. Running Linux pop-os 5.4.0-7642-generic #46~1598628707~20.04~040157c- Ubuntu SMP Fri Aug 28 18:02:16 UTC x86_64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
This bug is NOT invalid. This issue has remained unaddressed for years. Worse still, workarounds that used to mitigate the problem (dconf tweaks, etc) no longer seem effective. PLEASE, do not close this bug. -- 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/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295627] Re: Wrong language (German) after fresh install
This is still an issue in Ubuntu 20.04. I changed it manually: Settings > Language and Region > Manage Installed Languages Install/remove languages choose: other (it only shows a small list at first), and check "Dutch". Afterwards, go to tab "Regional Formats". Here, you'll see "Deutsch" as a display language for numbers, dates and currencies. Now you can select "Nederlands (België)". Press "Apply system-wide". After logging it again, it should be "solved". -- 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/1295627 Title: Wrong language (German) after fresh install Status in gnome-control-center package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: Fresh install from the live-cd (Daily build Xubuntu 14.04 - 32 bit). My location was determined as Brussels (which is correct). 1. Loginscreen : date and time in german 2. After login : date and time in german Locale is set to Deutsch ??? 3. Ibus : keyboard-layout = German(?)-Belgian ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Fri Mar 21 13:07:03 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InstallationDate: Installed on 2014-03-21 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140320) SourcePackage: ubiquity 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/1295627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
Can confirm, using nvidia-driver-450 seems to resolve the issue. I installed from here: https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa -- 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/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Nicolas -- I've seen the R7000 Chinese post (https://www.cnblogs.com/mikeguan/p/13126497.html), and what it basically entails is blacklisting hid_multitouch (or disabling it in the kernel and recompiling), which according to other forums seems to have an effect on some touchpads, but has no effect on the MSFT0001:00 04F3:3140 touchpad we have. I attempted his suggestions anyways, and saw the same lack of results -- the touchpad remained dead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Touchpad MSFT0001:00 04F3:3140 is dead on 5.8 rc5 as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
** Attachment added: "gedit.png" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1857191/+attachment/5395035/+files/gedit.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888574] [NEW] Dark mode highlight is too similar to text color
Public bug reported: Hi all! This is just a wishlist bug, but the dark mode in Gedit on Ubuntu doesn't work well for me. In dark mode, the highlight color and the text color are very similar, and the lack of contrast makes it difficult to the see text. Perhaps changing the highlight color to purple or something else to enhance contrast would be much appreciated. Thanks! Ubuntu 20.04 Installed: 3.36.2-0ubuntu1 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gedit.png" https://bugs.launchpad.net/bugs/1888574/+attachment/5395032/+files/gedit.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/1888574 Title: Dark mode highlight is too similar to text color Status in gedit package in Ubuntu: New Bug description: Hi all! This is just a wishlist bug, but the dark mode in Gedit on Ubuntu doesn't work well for me. In dark mode, the highlight color and the text color are very similar, and the lack of contrast makes it difficult to the see text. Perhaps changing the highlight color to purple or something else to enhance contrast would be much appreciated. Thanks! Ubuntu 20.04 Installed: 3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1888574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
+1 to bionic backport please -- 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/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Expired Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself
Yes, I am pretty sure: $ apt-cache policy mutter mutter: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- 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/1877589 Title: Wayland windows does not redraw itself Status in mutter package in Ubuntu: New Bug description: I'm not sure, if it is not a bug of certain Wayland applications. Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I change their size, or switch to another window or overview. For example, audacity does not redraw current position marker, and I need to click with a mouse, or resize the window to see it. Firefox sometimes just freeze, until I click or until I resize its window, or I switch to overview. What kind of trace shoud I perform to obtain more information? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:27:24 2020 InstallationDate: Installed on 2019-11-16 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself
After updating to 3.36.2 problem still occurs. -- 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/1877589 Title: Wayland windows does not redraw itself Status in mutter package in Ubuntu: New Bug description: I'm not sure, if it is not a bug of certain Wayland applications. Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I change their size, or switch to another window or overview. For example, audacity does not redraw current position marker, and I need to click with a mouse, or resize the window to see it. Firefox sometimes just freeze, until I click or until I resize its window, or I switch to overview. What kind of trace shoud I perform to obtain more information? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:27:24 2020 InstallationDate: Installed on 2019-11-16 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Had issues with keyboard shortcuts for changing language, up/down volume, open terminal and so on... First I tried comment #55 and logged out and back in, it didn't help. I went to try comment #11 (sleep solution) but then I remembered that few days ago I installed Skype and it was auto starting when I logged in and maybe cause of that the "timing went off", so instead of setting the sleep I just removed Skype from the auto start and restarted... and it worked! -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Just to be clear about the comment I wrote above, the solution is not really related to Skype, its probably just the fact that something new is loading up on log in and removing it will (hopefully) solve the issue. -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself
Yes, I disabled all extensions to ensure that is is not an extension problem. -- 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/1877589 Title: Wayland windows does not redraw itself Status in mutter package in Ubuntu: New Bug description: I'm not sure, if it is not a bug of certain Wayland applications. Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I change their size, or switch to another window or overview. For example, audacity does not redraw current position marker, and I need to click with a mouse, or resize the window to see it. Firefox sometimes just freeze, until I click or until I resize its window, or I switch to overview. What kind of trace shoud I perform to obtain more information? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:27:24 2020 InstallationDate: Installed on 2019-11-16 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877589] [NEW] Wayland windows does not redraw itself
Public bug reported: I'm not sure, if it is not a bug of certain Wayland applications. Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I change their size, or switch to another window or overview. For example, audacity does not redraw current position marker, and I need to click with a mouse, or resize the window to see it. Firefox sometimes just freeze, until I click or until I resize its window, or I switch to overview. What kind of trace shoud I perform to obtain more information? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:27:24 2020 InstallationDate: Installed on 2019-11-16 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1877589 Title: Wayland windows does not redraw itself Status in gnome-session package in Ubuntu: New Bug description: I'm not sure, if it is not a bug of certain Wayland applications. Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I change their size, or switch to another window or overview. For example, audacity does not redraw current position marker, and I need to click with a mouse, or resize the window to see it. Firefox sometimes just freeze, until I click or until I resize its window, or I switch to overview. What kind of trace shoud I perform to obtain more information? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:27:24 2020 InstallationDate: Installed on 2019-11-16 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1877589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 After looking through the posted bug and comments I'm not sure that the issues are related. It seems more like, in this case, GNOME is just out of sync with pulse about what the default device is thanks to pulse changing it out during login. Changing the selected device fixes the issue (until the next login). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875729] Re: Fractional Scaling crashes gnome-control-center
Hi Sebastian and Daniel, thanks for getting back to me. Daniel, I think you are likely correct with the 2 bugs you suggested, they seem to be similar. The links are: https://errors.ubuntu.com/oops/13fe9496-8745-11ea-ac2d-fa163e983629 https://errors.ubuntu.com/oops/390d34ea-874a-11ea-a30e-fa163e6cac46 https://errors.ubuntu.com/oops/3547348e-897f-11ea-a33f-fa163e6cac46 -- 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/1875729 Title: Fractional Scaling crashes gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Overview: When applying "Fractional Scaling" of 150% or 175%, the screen goes black for a while, then after a little while it comes back unscaled and gnome-control-center has crashed. Found in: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Go into "Screen Display" in Settings. 2. Enable "Fractional Scaling". 3. Select "150%" or "175%". 4. Observe that the screen goes blank for about 5 seconds. 5. Observe that upon the screen coming back, the Settings application has crashed. Additional details: If instead of selecting "150%" or "175%" I select "125%", then the screen will scale to 200% instead, but if I select and apply "125%" again, then suddenly only just over of a quarter of the screen is recognised as display and the rest just displays my background and top bar extended. I am using a 4k display over a display port cable. I am using a GTX 1070 TI with the Nvidia 440.64 driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 19:37:27 2020 InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875729] [NEW] Fractional Scaling crashes gnome-control-center
Public bug reported: Overview: When applying "Fractional Scaling" of 150% or 175%, the screen goes black for a while, then after a little while it comes back unscaled and gnome-control-center has crashed. Found in: Description:Ubuntu 20.04 LTS Release:20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Go into "Screen Display" in Settings. 2. Enable "Fractional Scaling". 3. Select "150%" or "175%". 4. Observe that the screen goes blank for about 5 seconds. 5. Observe that upon the screen coming back, the Settings application has crashed. Additional details: If instead of selecting "150%" or "175%" I select "125%", then the screen will scale to 200% instead, but if I select and apply "125%" again, then suddenly only just over of a quarter of the screen is recognised as display and the rest just displays my background and top bar extended. I am using a 4k display over a display port cable. I am using a GTX 1070 TI with the Nvidia 440.64 driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 19:37:27 2020 InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1875729 Title: Fractional Scaling crashes gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Overview: When applying "Fractional Scaling" of 150% or 175%, the screen goes black for a while, then after a little while it comes back unscaled and gnome-control-center has crashed. Found in: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Go into "Screen Display" in Settings. 2. Enable "Fractional Scaling". 3. Select "150%" or "175%". 4. Observe that the screen goes blank for about 5 seconds. 5. Observe that upon the screen coming back, the Settings application has crashed. Additional details: If instead of selecting "150%" or "175%" I select "125%", then the screen will scale to 200% instead, but if I select and apply "125%" again, then suddenly only just over of a quarter of the screen is recognised as display and the rest just displays my background and top bar extended. I am using a 4k display over a display port cable. I am using a GTX 1070 TI with the Nvidia 440.64 driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 19:37:27 2020 InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Is it supposed to switch back on reboot though? If I select a certain device I expect it to stay that way. It's not like I'm unplugging and replugging my USB device. From a user's perspective this certainly doesn't feel like the desired behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 684982]
VERIFIED FIXED on Ubuntu 20.04 beta with Gnome 3 classic and an old X11 Window Manager. THANK YOU SO MUCH ヽ(•‿•)ノ I've seen it in the trunk builds I made, and I was so happy. Just last week I thought "Ression restore considering virtual desktops would be my biggest wish for Firefox right now". And a week later, it worked. Can you imagine how happy I was? Thank you so much! If we see each other in person, I'll buy you a meal. Consider yourself hugged virtually. THANKS SO MUCH This was really great and kind. Thank you :-) Ben -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869513] [NEW] package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1
Public bug reported: /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by /usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::hasChromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::readPixels(int, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::InputFile(char const*, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::insert(char const*, Imf_2_2::Slice const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::chromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::globalThreadCount()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::header() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::writePixels(int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Channel::Channel(Imf_2_2::PixelType, int, int, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::begin()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Slice::Slice(Imf_2_2::PixelType, char*, unsigned long, unsigned long, int, int, double, bool, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::dataWindow() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::~Header()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::OutputFile(char const*, Imf_2_2::Header const&, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::findChannel(char const*) const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::end()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::Header(int, int, float, Imath_2_2::Vec2 const&, float, Imf_2_2::LineOrder, Imf_2_2::Compression)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Chromaticities::Chromaticities(Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::~OutputFile()' collect2: error: ld returned 1 exit status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openexr 2.3.0-6build1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 27 15:58:19 2020 ErrorMessage: installed openexr package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-27 (121 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.1 SourcePackage: openexr Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago) ** Affects: openexr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1869513 Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 Status in openexr package in Ubuntu: New Bug description: /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by /usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or
[Desktop-packages] [Bug 490935]
(In reply to Johannes Reiff from comment #95) > hasn't there just been any volunteer to implement the feature? Yes > I have another use-case for this feature: Many scanners nowadays can send > emails with the scan attached. By default, though, these mails have a very > generic subject. Being able to change the subject from the mail client ... > allows finding particular scans later on. > > I have been doing this in the past using the Header Tools Lite addon. This > addon, however, is not compatible with newer versions of Thunderbird. 100% exactly my problem as well. This makes scan to email very hard to use. Everything has the same subject. Get 5 at the same time, and it's impossible to manage. Scan to email is a widely advertized feature of printers, so it's not a mainstream feature, and not marginal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/490935 Title: it is not possible to modify email subject Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Microsoft Outlook allows to modify "subject" of incoming emails. This is very very useful, especially when sender used a meaningless subject, or a simple dot. This feature should be very useful also in Thunderbird. Thanks a lot ProblemType: Bug Architecture: i386 CheckboxSubmission: c44b5fa992c605c204076ccbc3a738b7 CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 Date: Tue Dec 1 18:36:54 2009 DistroRelease: Ubuntu 9.10 Package: mozilla-thunderbird (not installed) ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.50-generic SourcePackage: thunderbird Uname: Linux 2.6.31-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/490935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"
This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and 5.3.9, nvidia drivers version 435 and 440) It only happens when using nvidia GPU. If I prime-select my intel GPU then there is no issue. It seems related to the laptop display being on some internal display port that gets disconnected when the lid is closed. If I type 'systemctl suspend' before closing my lid everything works fine when I open. I suspect this is actually a bug in nvidia drivers and not in xorg- server -- 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/1791981 Title: X Server session crash for "No space left on device" Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1322728] Re: VPN Connection Failed With 2 Factor Authentication
I just tried on 19.10 and have the same issue. Let me know any logs or anything is needed to help debug the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1322728 Title: VPN Connection Failed With 2 Factor Authentication Status in network-manager-fortisslvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Hi all, my setup is an openvpn access server with google 2 factor auth i was trying to connect to my VPN using the gnome openvpn module and get the following errors on syslog: May 23 22:23:00 laptop nm-openvpn[18049]: [OpenVPN Server] Peer Connection Initiated with [AF_INET]xx.xx.xx.xx:1194 May 23 22:23:02 laptop nm-openvpn[18049]: AUTH: Received control message: AUTH_FAILED,CRV1:R,E:d1r12r21df232+owqrf23t23t23tCn:aXRf3r2s=:Enter Google Authenticator Code May 23 22:23:02 laptop nm-openvpn[18049]: SIGTERM[soft,auth-failure] received, process exiting May 23 22:23:02 laptop NetworkManager[1043]: VPN plugin failed: 0 i looked in the documentation but didn't found anything useful. any help will be appreciated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-fortisslvpn/+bug/1322728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
I can confirm both the bug with CS:GO (and several other games that go non-responsive for a short while after starting) and that the fix works. I installed the packages from the ppa and have tested with CS:GO and a couple of others I was experiencing the problem on (Dying Light and TF2 behave similarly) and the games start correctly now and do not block the UI or crash gnome-shell, though they still display the Force Quit dialog. I can do any further testing needed but this LGTM. -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine. Using a Radeon RX 580 video card. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I also hit Fn-A, which I saw somewhere (sorry to not have the link) that would disable adaptive brightness. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Alright, here we go. I have the kernel listed above installed: Linux shadeball 5.2.0-9-generic #10~bfo110511 SMP Tue Jul 16 13:17:28 CST 2019 x86_64 x86_64 x86_64 GNU/Linux I then went into the Power settings and turned Dim Screen When Inactive to off, Blank Screen to Never and so far there have been basically no flickers. There may have been one or two, but I can't confirm that I saw them and cannot reproduce them. I have tried it both on AC power and on battery, and with success on both. Thank you so much! -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
But just to confirm, I think the patched kernel did improve the amount of flickering. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Huh, I wonder if this is a Gnome Shell issue and not a kernel issue after all. After switching to Ubuntu Mate, and uninstalling the kernel mentioned above, I have not had a flicker yet. Anecdotally, I have also heard of people installing KDE on an XPS 13 9380 and also not having this issue. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Another error message from a flicker Sep 12 20:28:01 shadeball org.gnome.Shell.desktop[5959]: [6514:6514:0912/202801.632870:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1280 times! -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I ran "journalctl --user" after the last flicker and this is the output from the time around the flicker Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.077664:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.078033:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.084532:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: [1:1:0912/201234.084847:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. I can post the full multi-day output of journalctl --user if that would be useful to you all. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I am running Ubuntu 19.04 with an XPS 13 9380 with Intel graphics. I installed the kernel mentioned above, and the problem is still occurring. I do a dmesg everytime I see it happen, but I don't see a consistent message every time it happens. I am more than willing to do any and all testing you all need, so if you think of something I could do to further investigate, let me know! -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801540]
(In reply to Takashi Iwai from comment #127)
> Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting
> based on LPIB instead of the position buffer. I thought the position buffer
> isn't available or unreliable on non-Intel chips, but it might be different
> on the recent AMD one.
Contrary to what Ernst experienced, removing AZX_DCAPS_POSFIX_LPIB
completely broke audio on my system (ASUS PRIME X470, also 1022:1457),
so I guess it's still unreliable as you mentioned.
Was looking through the pci_ids array in sound/pci/hda/hda_intel.c and
noticed that my audio controller (1022:1457) isn't listed.
The only thing I can see that would match is the following, which seems
to be intended for AMD GPUs.
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_ANY_ID),
.class = PCI_CLASS_MULTIMEDIA_HD_AUDIO << 8,
.class_mask = 0xff,
.driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_HDMI },
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838577] [NEW] Default audio device changes on reboot; audio still outputs using my previously-selected device
Public bug reported: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic disco eoan ** Description changed: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and - volume control adjusts the USB speaker volume. Despite pulse seeing the - USB device as the current output device, I still hear sound from my - line-out. + Gnome shell / Gnome settings volume control adjusts the USB speaker + volume. Despite seeing the USB device as the current output device, I + still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) 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: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs
[Desktop-packages] [Bug 1835625] Re: Shows old snap edge version of thunderbird
As I wrote on the snapcraft forums, that's a problem then as long as the snap continues to be out of date/unstable, as the snap replaces the deb version for users that don't have Thunderbird installed. I don't mind if non-stable snaps appear in the store, but they should not be default if a deb version is also available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1835625 Title: Shows old snap edge version of thunderbird Status in gnome-software package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Released Bug description: Test case: Open ubuntu-software, search thunderbird Version returned is an old edge version of thunderbird not meant to be used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 14:57:47 2019 InstallationDate: Installed on 2019-07-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801540]
(In reply to Marco from comment #100) > Yea, I'm still trying to find the energy to begin to write a parser for the > codec commands, but this will surely take quite a lot of time. This actually sounds like something I would be interested in working on. However I don't really have any experience working with low level audio like this. Are the dumps you gave for the ALC892? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
Is there a workaround? This is currently breaking my entire audio setup (using Ubuntu Studio, where jackd is crucial) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
How does one upgrade to systemd-241 in ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Unknown Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832651] [NEW] jackdbus fails to start: cannot allocate memory
Public bug reported: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in jackd2 package in Ubuntu: New Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830472] [NEW] 'mv' command without target address
Public bug reported: When I was using the mv command, I forgot to enter the target folder, but the terminal did not report an error and the source file was gone. But when I tried it again， it report the error "mv: missing destination file operand after 'filename'". Though the file is not important, I hope you can figure it out. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 25 18:12:56 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-03-07 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "the wrong command screenshot" https://bugs.launchpad.net/bugs/1830472/+attachment/5266487/+files/2019-05-25%2017-45-32%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.png -- 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/1830472 Title: 'mv' command without target address Status in gnome-terminal package in Ubuntu: New Bug description: When I was using the mv command, I forgot to enter the target folder, but the terminal did not report an error and the source file was gone. But when I tried it again， it report the error "mv: missing destination file operand after 'filename'". Though the file is not important, I hope you can figure it out. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 25 18:12:56 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-03-07 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-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/1830472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
I'm on 19.04 and I seem to be able to reproduce this at least once a day while I leave my screen locked overnight. Am willing to provide logs and core dumps if possible. Just let me know how/what you need to capture. Each morning when I log back in, the screen will sit and freeze for a minute or so while gnome shell crashes and restarts, but at least it keeps my windows and workspaces open / in place. A bit after that is when apport gives me the dialog. -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() 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/gnome-shell/+bug/1702151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file
OK well with more resources in use the behaviour I am getting is that Image Viewer boots, shows a blank window, and then exits. So that's a little bit like my comment #4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1828720 Title: eog (Ubuntu image viewer) consumes all memory when opening a tiff file Status in eog package in Ubuntu: Incomplete Bug description: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file
OK the original trigger file is OK now and uses a similar amount of memory to load. I guess it would be more appropriate to say that there's nothing to stop eog loading a file that's impracticably large, and a refinement would be to do a rough calculation of the memory requirement and ask the user to confirm they want to open it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1828720 Title: eog (Ubuntu image viewer) consumes all memory when opening a tiff file Status in eog package in Ubuntu: Incomplete Bug description: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file
This file is identical in pixel dimensions to one that caused the bug earlier. It is 1-bit with a size of 10332px x 4148px. It is LZW compressed and contains an entirely white image. *Opening this file with Image Viewer (eog) doesn't trigger the bug* with the resources available on my system now, though it takes a bit of time to appear and requires over 1GB of memory. I will load up more software and see if that affects the outcome, and I will try the one of the files that did trigger it earlier at the current system usage level (I cannot upload that as it's a private scan from a book and sharing it would violate copyright). ** Attachment added: "Sample LZW compressed 1-bit TIFF" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+attachment/5263279/+files/1bit-test-compressed.tiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1828720 Title: eog (Ubuntu image viewer) consumes all memory when opening a tiff file Status in eog package in Ubuntu: Incomplete Bug description: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828720] [NEW] eog (Ubuntu image viewer) consumes all memory when opening a tiff file
Public bug reported: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug bionic third-party-packages ** Description changed: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files - are opened. Any TIFF file can cause a loop risky even if less than 1MB - in size, so it seems that the program is encountering an internal issue + are opened. Any TIFF file can cause a loop even if less than 1MB in + size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. - OS: - Description: Ubuntu 18.04.2 LTS - Release: 18.04 - - Package: - eog: - Installed: 3.28.1-1 - Candidate: 3.28.1-1 - Version table: - *** 3.28.1-1 500 - 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog 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 eog in Ubuntu. https://bugs.launchpad.net/bugs/1828720 Title: eog (Ubuntu image viewer) consumes all memory when opening a tiff file Status in eog package in Ubuntu: Incomplete Bug description: The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format. The loop quickly consumes all free memory and locks up the machine (I do not have any swap). Steps to reproduce: * open any TIFF file using ImageViewer, the default image file handler. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 11:11:02 2019 InstallationDate: Installed on 2015-02-21 (1540 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821494] [NEW] Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping
Public bug reported:
Similar to the Steelseries Arctis headphones, these sound "cards"
present as two output devices, one intended for voice chat and one for
everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that
requires no special driver logic; instead, the "everything else" output
pretends to be 7.1, and simply applies the HRTF to the streams sent by
the host. However, the channel mappings picked up by ALSA are wrong --
the rear speakers and center/LFE are swapped.
I know, technically this is two bugs, but they have the same fix which
is impractical to separate. I'm attaching a "sennheiser-gsx.conf" based
on the Arctis 7 profile that both corrects the channel mapping and
exposes both output subdevices. A simple udev rule seals the deal:
ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e", ENV{PULSE_PROFILE_SET
}="sennheiser-gsx.conf"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: roothorick 7548 F pulseaudio
/dev/snd/controlC2: roothorick 7548 F pulseaudio
/dev/snd/controlC0: roothorick 7548 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 23:09:21 2019
InstallationDate: Installed on 2018-09-12 (193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2019-03-23T20:51:33.488207
mtime.conffile..etc.pulse.default.pa: 2019-03-23T23:03:49.029912
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: "sennheiser-gsx.conf"
https://bugs.launchpad.net/bugs/1821494/+attachment/5248935/+files/sennheiser-gsx.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821494
Title:
Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse &
incorrect channel mapping
Status in pulseaudio package in Ubuntu:
New
Bug description:
Similar to the Steelseries Arctis headphones, these sound "cards"
present as two output devices, one intended for voice chat and one for
everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that
requires no special driver logic; instead, the "everything else"
output pretends to be 7.1, and simply applies the HRTF to the streams
sent by the host. However, the channel mappings picked up by ALSA are
wrong -- the rear speakers and center/LFE are swapped.
I know, technically this is two bugs, but they have the same fix which
is impractical to separate. I'm attaching a "sennheiser-gsx.conf"
based on the Arctis 7 profile that both corrects the channel mapping
and exposes both output subdevices. A simple udev rule seals the deal:
ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e",
ENV{PULSE_PROFILE_SET}="sennheiser-gsx.conf"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: roothorick 7548 F pulseaudio
/dev/snd/controlC2: roothorick 7548 F pulseaudio
/dev/snd/controlC0: roothorick 7548 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 23:09:21 2019
InstallationDate: Installed on 2018-09-12 (193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" -
Re: [Desktop-packages] [Bug 1316673] Re: Pressing umount button leads to sticky icon as mouse pointer
> Do you still see that issue in more recent Ubuntu versions? > > ** Changed in: nautilus (Ubuntu) >Status: New => Incomplete No. Should be closed. Cheers Benjamin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1316673 Title: Pressing umount button leads to sticky icon as mouse pointer Status in nautilus package in Ubuntu: Incomplete Bug description: When pressing the umount button in nautilus (see screenshoot_1.png, #1), the mouse pointer changes to a hand - which is not recoreded by the screenshoot application - and carries around one of the fav-links. Pressing ESC solves the problem. This happens every time I press umount. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 6 17:52:28 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 'where', 'permissions', 'date_accessed']" SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1316673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 583797]
Yay, thanks so much! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/583797 Title: "Warn on closing with multiple tabs open" not honored Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy firefox firefox: Installed: 11.0+build1-0ubuntu0.11.10.1 Candidate: 11.0+build1-0ubuntu0.11.10.1 Version table: *** 11.0+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main i386 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in Firefox, with Edit -> Preferences -> Tabs -> "Warn on closing with multiple tabs open" checkbox checked, is when one click the X, File -> Quit, Ctrl+Q , or Alt+Space -> C, one get's the confirmation box: Confirm close You are about to close x tabs. Are you sure you want to continue? 4) What happens instead is one is not warned and the window closes. PARTIAL WORKAROUND: about:config -> browser.tabs.maxOpenBeforeWarn -> change from 15 to 2. This will pop up the confirmation box clicking the X and Alt+Space -> C only. WORKAROUND: Disable Ctrl+Q quiting the browser by installing keyconfig add-on: http://mozilla.dorando.at/keyconfig.xpi Then Tools -> Add-Ons -> Extensions -> keyconfig Preferences -> highlight Quit -> Disable Original Reporter Comments: I found a "workaround" that says to set "open to a blank page" somewhere else, and I set this, but it still doesn't warn me. I work from home and frequently spend an hour or so putting in data, all on one screen. If I accidentally hit the stupid little x (which is now in the left hand corner just where you don't need it, it is too easy to hit it by accident, but i can't change this, it comes with the distro), i lose all that work. Please tell me how to fix this terrible bug. Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.1 THIS BUG AFFECTS MY SECURITY (INCOME) but i guess would not be classifed as a security bug per se ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 21 14:07:40 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/583797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The UX391UA fix is not in 4.20 as it was already a release candidate. To get sound working on this model you'll need to download the 4.20 source, apply the patch to sound/pci/hda/patch_realtek.c then compile and install the kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809656] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224923/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809656] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224922/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
