[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 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 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 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 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 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 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 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
[Desktop-packages] [Bug 1809656] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224919/+files/ProcInterrupts.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] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224921/+files/UdevDb.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] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224920/+files/ProcModules.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] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224913/+files/DpkgLog.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] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224918/+files/ProcCpuinfoMinimal.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] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224916/+files/MonitorsUser.xml.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] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224915/+files/Lsusb.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] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224917/+files/ProcCpuinfo.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] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224914/+files/Lspci.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] Re: Small windows output corrupted in XWayland clients
apport information ** Tags added: apport-collected bionic ubuntu wayland-session ** Description changed: 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 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224912/+files/CurrentDmesg.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: amdgp
[Desktop-packages] [Bug 1809656] [NEW] Small windows output corrupted in XWayland clients
Public bug reported: 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. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Снимок экрана от 2018-12-24 13-38-38.png" https://bugs.launchpad.net/bugs/1809656/+attachment/5224638/+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%202018-12-24%2013-38-38.png -- 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. 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 1786233] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1786233/+attachment/5173662/+files/GsettingsChanges.txt -- 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/1786233 Title: Can't rename a desktop file Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 InstallationDate: Installed on 2018-01-08 (213 days ago) InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219) Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 Tags: third-party-packages wayland-session bionic Uname: Linux 4.18.0-041800rc8-generic x86_64 UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. Пожалуйста, удалите все сторонние пакеты и попробуйте снова. UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago) UserGroups: adm kvm lpadmin sudo tty vboxusers video _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786233] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1786233/+attachment/5173663/+files/ProcCpuinfoMinimal.txt -- 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/1786233 Title: Can't rename a desktop file Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 InstallationDate: Installed on 2018-01-08 (213 days ago) InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219) Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 Tags: third-party-packages wayland-session bionic Uname: Linux 4.18.0-041800rc8-generic x86_64 UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. Пожалуйста, удалите все сторонние пакеты и попробуйте снова. UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago) UserGroups: adm kvm lpadmin sudo tty vboxusers video _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786233] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1786233/+attachment/5173664/+files/ProcEnviron.txt -- 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/1786233 Title: Can't rename a desktop file Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 InstallationDate: Installed on 2018-01-08 (213 days ago) InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219) Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 Tags: third-party-packages wayland-session bionic Uname: Linux 4.18.0-041800rc8-generic x86_64 UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. Пожалуйста, удалите все сторонние пакеты и попробуйте снова. UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago) UserGroups: adm kvm lpadmin sudo tty vboxusers video _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786233] Re: Can't rename a desktop file
apport information ** Tags added: apport-collected bionic third-party-packages wayland- session ** Description changed: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. - Dekstop files are different. If I try to rename firefox.desktop to - firefox.txt in order to edit this file manually, I can't do so, because - nautilus always add desktop extension. If I accidentially rename regular - file to a desktop file, I can't rename it back, because Nautilus throw - an error, that this desktop file has a wrong format (obviously because - it is not a desktop file). + Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + CurrentDesktop: pop:GNOME + DistroRelease: Pop!_OS 18.04 + InstallationDate: Installed on 2018-01-08 (213 days ago) + InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219) + Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu] + PackageArchitecture: amd64 + Tags: third-party-packages wayland-session bionic + Uname: Linux 4.18.0-041800rc8-generic x86_64 + UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. Пожалуйста, удалите все сторонние пакеты и попробуйте снова. + UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago) + UserGroups: adm kvm lpadmin sudo tty vboxusers video + _MarkForUpload: True + usr_lib_nautilus: ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1786233/+attachment/5173661/+files/Dependencies.txt -- 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/1786233 Title: Can't rename a desktop file Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.04 InstallationDate: Installed on 2018-01-08 (213 days ago) InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219) Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 Tags: third-party-packages wayland-session bionic Uname: Linux 4.18.0-041800rc8-generic x86_64 UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. Пожалуйста, удалите все сторонние пакеты и попробуйте снова. UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago) UserGroups: adm kvm lpadmin sudo tty vboxusers video _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786233] [NEW] Can't rename a desktop file
Public bug reported: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1786233 Title: Can't rename a desktop file Status in nautilus package in Ubuntu: New Bug description: Nautilus allows to rename any generic file, including the extension part. For example, I can rename "Image.jpeg" to "Image.jpg" or even "Image.png" which is not right, but still possible. Dekstop files are different. If I try to rename firefox.desktop to firefox.txt in order to edit this file manually, I can't do so, because nautilus always add desktop extension. If I accidentially rename regular file to a desktop file, I can't rename it back, because Nautilus throw an error, that this desktop file has a wrong format (obviously because it is not a desktop file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734745] [NEW] NM assumes avahi ip addres and default gw for disconnected device
Public bug reported: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "commands_output" https://bugs.launchpad.net/bugs/1734745/+attachment/5015325/+files/commands_output -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734745 Title: NM assumes avahi ip addres and default gw for disconnected device Status in network-manager package in Ubuntu: New Bug description: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445514] Re: Can't install fglrx with the new quantal Xorg stack in Trusty
*** This bug is a duplicate of bug 1424491 *** https://bugs.launchpad.net/bugs/1424491 ** This bug has been marked a duplicate of bug 1424491 apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1445514 Title: Can't install fglrx with the new quantal Xorg stack in Trusty Status in fglrx-installer package in Ubuntu: New Bug description: With the new 14.04.2 update, Xorg stack is now from Utopic, so the packages named as xserver-xorg-core-lts-utopic, xserver-xorg-input- all-lts-utopic and so on. But fglrx (and fglrx-update) drivers from the repository depends on xorg-video-abi-11 (or xorg-video-abi-12 and so on) which is somehow does not provided by xserver-xorg-core-lts-utopic, and provided only by xserver-xorg-core. So, the user can't install fglrx driver anymore. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 17 17:14:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e193] InstallationDate: Installed on 2015-04-15 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=74a97b44-c85a-476c-ae72-6a16275da268 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd02/16/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 17 14:15:21 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1445514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445514] [NEW] Can't install fglrx with the new quantal Xorg stack in Trusty
Public bug reported: With the new 14.04.2 update, Xorg stack is now from Utopic, so the packages named as xserver-xorg-core-lts-utopic, xserver-xorg-input-all- lts-utopic and so on. But fglrx (and fglrx-update) drivers from the repository depends on xorg-video-abi-11 (or xorg-video-abi-12 and so on) which is somehow does not provided by xserver-xorg-core-lts-utopic, and provided only by xserver-xorg-core. So, the user can't install fglrx driver anymore. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 17 17:14:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e193] InstallationDate: Installed on 2015-04-15 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=74a97b44-c85a-476c-ae72-6a16275da268 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd02/16/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 17 14:15:21 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1445514 Title: Can't install fglrx with the new quantal Xorg stack in Trusty Status in fglrx-installer package in Ubuntu: New Bug description: With the new 14.04.2 update, Xorg stack is now from Utopic, so the packages named as xserver-xorg-core-lts-utopic, xserver-xorg-input- all-lts-utopic and so on. But fglrx (and fglrx-update) drivers from the repository depends on xorg-video-abi-11 (or xorg-video-abi-12 and so on) which is somehow does not provided by xserver-xorg-core-lts-utopic, and provided only by xserver-xorg-core. So, the user can't install fglrx driver anymore. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 17 17:14:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limite
[Desktop-packages] [Bug 1398164] Re: Writer hangs when editing table in print layout mode, if table row is too high
Cannot reproduce with Libreoffice 4.4.2 — closing. ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- 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/1398164 Title: Writer hangs when editing table in print layout mode, if table row is too high Status in libreoffice package in Ubuntu: Fix Released Bug description: When the table configured not to wrap on the pages, and table cell content is too high for a cell, it must go out of the sheet. LO Writer hangs in this situation (both in case of doc or odt files). See attachment, try to change it to the print layout from web layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1398164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398164] [NEW] Writer hangs when editing table in print layout mode, if table row is too high
Public bug reported: When the table configured not to wrap on the pages, and table cell content is too high for a cell, it must go out of the sheet. LO Writer hangs in this situation (both in case of doc or odt files). See attachment, try to change it to the print layout from web layout. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Тестовое.odt" https://bugs.launchpad.net/bugs/1398164/+attachment/4272433/+files/%D0%A2%D0%B5%D1%81%D1%82%D0%BE%D0%B2%D0%BE%D0%B5.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1398164 Title: Writer hangs when editing table in print layout mode, if table row is too high Status in libreoffice package in Ubuntu: New Bug description: When the table configured not to wrap on the pages, and table cell content is too high for a cell, it must go out of the sheet. LO Writer hangs in this situation (both in case of doc or odt files). See attachment, try to change it to the print layout from web layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1398164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 669465] Re: Evolution's e-addressbook-factory process renders CPU usage 100%
Same problem with ZImbra's online accounts. Syncronization made by WebDAV. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/669465 Title: Evolution's e-addressbook-factory process renders CPU usage 100% Status in Evolution Data Server: New Status in “evolution-data-server” package in Ubuntu: Expired Bug description: Binary package hint: evolution-data-server I have set-up Evolution email client to access my Gmail and UbuntuOne address books. However, on some occasions e-addressbook-factory starts using 100% of CPU. It has happened to me more than ten times, but I still cannot tell what exactly causes the book to occur. It may be something with Gmail address book and UbuntuOne address book accessed at the same time. BTW, this bug seems to occur more often after Ubuntu resumes from suspend. Killing the process, apparently, helps, as it is restarted and works normal. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution-data-server 2.30.3-2ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Nov 1 16:06:27 2010 ExecutablePath: /usr/lib/evolution/e-addressbook-factory InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: evolution-data-server To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/669465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880121] Re: Gdm crashes after reboot after setting autologin option
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/880121/+attachment/2567638/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/880121 Title: Gdm crashes after reboot after setting autologin option Status in “gdm” package in Ubuntu: New Bug description: Ubuntu 11.10, GDM 3.0.4 I have one user and set up autologin using system preferences - users. Gdm didn't start after reboot, leaving just a blank screen So I used lightdm instead and now I here. Nothing in dmesg, syslog or something. The bug is reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/880121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880121] Re: Gdm crashes after reboot after setting autologin option
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/880121/+attachment/2567637/+files/dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/880121 Title: Gdm crashes after reboot after setting autologin option Status in “gdm” package in Ubuntu: New Bug description: Ubuntu 11.10, GDM 3.0.4 I have one user and set up autologin using system preferences - users. Gdm didn't start after reboot, leaving just a blank screen So I used lightdm instead and now I here. Nothing in dmesg, syslog or something. The bug is reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/880121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880121] [NEW] Gdm crashes after reboot after setting autologin option
Public bug reported: Ubuntu 11.10, GDM 3.0.4 I have one user and set up autologin using system preferences - users. Gdm didn't start after reboot, leaving just a blank screen So I used lightdm instead and now I here. Nothing in dmesg, syslog or something. The bug is reproducible. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/880121 Title: Gdm crashes after reboot after setting autologin option Status in “gdm” package in Ubuntu: New Bug description: Ubuntu 11.10, GDM 3.0.4 I have one user and set up autologin using system preferences - users. Gdm didn't start after reboot, leaving just a blank screen So I used lightdm instead and now I here. Nothing in dmesg, syslog or something. The bug is reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/880121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
