[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
Same problem on Ubuntu 21.04. started gnome-font-viewer from terminal the window opens but is unresponsive. closing it I have the crash and a message: corrado@corrado-n8-hh-0101:~$ gnome-font-viewer (gnome-font-viewer:4532): Gdk-ERROR **: 08:22:36.317: The program 'gnome-font-viewer' received an X Window System error. This probably reflects a bug in the program. The error was 'BadIDChoice (invalid resource ID chosen for this connection)'. (Details: serial 1502 error_code 14 request_code 130 (MIT-SHM) minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) corrado@corrado-n8-hh-0101:~$ corrado@corrado-n8-hh-0101:~$ apt policy gnome-font-viewer gnome-font-viewer: Installed: 3.34.0-2 Candidate: 3.34.0-2 Version table: *** 3.34.0-2 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n8-hh-0101:~$ inxi -SCGx System:Host: corrado-n8-hh-0101 Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: GNOME 3.38.2 Distro: Ubuntu 21.04 (Hirsute Hippo) CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 L2 cache: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 813 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 813 2: 998 3: 989 4: 997 5: 966 6: 980 7: 954 8: 974 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:3 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.2.6 direct render: Yes corrado@corrado-n8-hh-0101:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1845362 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: Confirmed Status in gnome-font-viewer package in Debian: New Bug description: Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of application during ISO testing of a live-session. Application will crash if there is an attempt to close it or scroll through fonts. On one occasion my laptop was rendered unusable when Firefox was launched while trying to report the crash to Launchpad. After the bug report has been sent gnome-font-viewer will freeze when automatically restarted. No fonts are displayed. Work around --- gnome-font-viewer appears to start correctly when started from the command line of my Ubuntu 20.04 installation. Then subsequent attempts to start the program succeed when started from the dock or the Application Overview. I have found that this work around wasn't necessary when using Xubuntu 20.04. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.416 CurrentDesktop: XFCE Date: Wed Sep 25 17:34:17 2019 ExecutablePath: /usr/bin/gnome-font-viewer LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) ProcCmdline: gnome-font-viewer ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 425423] Re: xdg-open does not interact with /etc/alternatives
Management of alternatives requires root privileges and, as you mentioned, affects every user of computer. Because of this, I think such a feature will not be implemented in xdg-utils. These programs are intended primarily for interacting with DE, not core system mechanisms. ** Changed in: xdg-utils (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/425423 Title: xdg-open does not interact with /etc/alternatives Status in xdg-utils package in Ubuntu: Opinion Bug description: Binary package hint: xdg-utils xdg-open has its own private configuration of "preferred applications" which duplicates, and is inconsistent with, /etc/alternatives. As a long-time Debian user I supposed that I could change my web browser by simply changing the target of x-www-browser, but this did not work. I also needed to open the GNOME control panel and change my favorite web browser under the Preferred Applications applet. The best solution seems to be for the applet to somehow interact with /etc/alternatives, but I don't see how this would be possible since /etc/alternatives is for all users. A partial workaround would be for the default browser to be "x-www-browser" instead of Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/425423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
** Also affects: udisks (Ubuntu) Importance: Undecided Status: New ** Package changed: udisks (Ubuntu) => udisks2 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 783914] Re: xdg-open ignores $BROWSER
** Changed in: xdg-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/783914 Title: xdg-open ignores $BROWSER Status in xdg-utils package in Ubuntu: Confirmed Bug description: Binary package hint: xdg-utils This is on Ubuntu 11.04. xdg-open seems to be ignoring the BROWSER enviroment variable. If i'm not wrong, is using gnome-open, and i cannot configure gnome-open to use w3m, which is the browser i want to use. Wouldn't be best to honor the BROWSER variable? xdg-open should have a consistent behaviour and not change between desktops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/783914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910598] [NEW] Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
You have been subscribed to a public bug: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) ** Affects: caja (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. https://bugs.launchpad.net/bugs/1910598 You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
** Tags added: bionic ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: Triaged Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
** Tags added: oem-priority originate-from-1910660 timbuktu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: New Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pepperflashplugin-nonfree (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: New Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
Hi, I aware the adobe is not longer support since this year. but the postinst[1] is still trying to get something from remote server. as ``` upstream=$(HOME=/root wget -q -O- "https://get.adobe.com/flashplayer/webservices/json/?platform_type=Linux_arch=$arch_dist=Chrome;...) ``` and it will take 4 hours to wait for the response. --- 16:17:01 Setting up pepperflashplugin-nonfree (1.8.3+nmu1ubuntu1) ... 20:11:51 ERROR: failed to determine upstream version 20:11:51 More information might be available at: 20:11:51 http://wiki.debian.org/PepperFlashPlayer --- As comment#7, please consider to backport to bionic as well. [1] ``` update-pepperflashplugin-nonfree --install --fast || true ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in OEM Priority Project: New Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: Confirmed Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903376] Re: VGA monitor stuck at 1024x768, no EDID available
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1903376 Title: VGA monitor stuck at 1024x768, no EDID available Status in xorg-server package in Ubuntu: Expired Bug description: i recently installed XDM (xtreme download manager) after my display changed to 1024x768 before it was good with 1336x768. i have also uninstalled it but still the problem persists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:56:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2020-08-30 (69 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=5dbd6c89-5b4e-4ab5-bc60-f67c18802fcd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0020.2011.0218.1538 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0020.2011.0218.1538:bd02/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-204:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1903376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902907] Re: Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902907 Title: Developer Options shows 'groovy-proposed' instead of 'hirsute- proposed' (software-properties-gtk on 21.04 Hirsute Hippo) Status in software-properties package in Ubuntu: Expired Bug description: When testing Hirsute Hippo (21.04), I found that software-properties- gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a live session in VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Nov 4 16:16:14 2020 LiveMediaBuild: Ubuntu Unity 21.04 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867147] Re: Failed to add UUID: Busy (0x0a)
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1867147 Title: Failed to add UUID: Busy (0x0a) Status in bluez package in Ubuntu: Expired Bug description: dmesg Bluetooth: hci0: command 0x0c24 tx timeout rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no bluetoothctl Failed to start discovery: org.bluez.Error.InProgress lsusb Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) lshw *-usb descrição: USB controller produto: Cannon Lake PCH USB 3.1 xHCI Host Controller fabricante: Intel Corporation ID físico: 14 informações do barramento: pci@:00:14.0 versão: 10 largura: 64 bits clock: 33MHz capacidades: pm msi xhci bus_master cap_list configuração: driver=xhci_hcd latency=0 recursos: irq:124 memória:eb22-eb22 *-usbhost:0 produto: xHCI Host Controller fabricante: Linux 5.3.0-40-generic xhci-hcd ID físico: 0 informações do barramento: usb@1 nome lógico: usb1 versão: 5.03 capacidades: usb-2.00 configuração: driver=hub slots=16 speed=480Mbit/s *-usb:0 descrição: Interface sem fio bluetooth produto: JL AC69 A10 fabricante: Cambridge Silicon Radio, Ltd ID físico: 1 informações do barramento: usb@1:1 versão: 25.20 capacidades: bluetooth usb-2.00 configuração: driver=btusb maxpower=100mA speed=12Mbit/s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:18:43 2020 InstallationDate: Installed on 2019-06-19 (266 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteDesk 800 G4 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=885446d9-2945-4958-a7f0-1eadecf23697 ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q01 Ver. 02.06.03 dmi.board.name: 83E1 dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ01Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4SFF:pvr:rvnHP:rn83E1:rvrKBCVersion07.D2.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 SFF dmi.product.sku: 5ZA60LP#AC4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1867147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902825] Re: High CPU usage?
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1902825 Title: High CPU usage? Status in gnome-shell package in Ubuntu: Expired Bug description: high cpu usage just moving the mouse removed appindicator extension .. the cpu load is very high. running strace -c -p while moving mouse % time seconds usecs/call callserrors syscall -- --- --- - - 36.740.103852 103 1000 8 futex 31.300.088469 8 10366 8750 recvmsg 15.530.043901 11 3925 poll 10.100.028550 10 2776 write 4.330.012232 7 1537 writev 1.600.004533 4 932 read 0.390.001092 3 337 getpid 0.000.01 0 2 getrusage 0.000.01 1 1 restart_syscall 0.000.00 0 4 mprotect -- --- --- - - 100.000.282631 20880 8758 total ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Nov 4 10:49:20 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903308] Re: gnome-shell freezes and restarts itself after login
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1903308 Title: gnome-shell freezes and restarts itself after login Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-455 package in Ubuntu: Expired Bug description: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903308] Re: gnome-shell freezes and restarts itself after login
[Expired for nvidia-graphics-drivers-455 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: Incomplete => Expired -- 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/1903308 Title: gnome-shell freezes and restarts itself after login Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-455 package in Ubuntu: Expired Bug description: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903446] Re: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1903446 Title: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason Status in gnome-shell package in Ubuntu: Expired Bug description: it take also 1 Gbyte of memory I expect not using these resoruces from my cpu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 23:13:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-04 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905648] Re: [nvidia] fractional display scale cannot work properly
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1870736, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- 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/1905648 Title: [nvidia] fractional display scale cannot work properly Status in mutter package in Ubuntu: New Bug description: When I switch on fractional scaling, and choose 125%/150%/175%, everything gets very large. The screen can only display part of the whole desktop. It is even larger than the 200%-scale. P.S. As I remember, the fractional scaling works well in May. But after a update in May (forgot the exact date), fractional scaling cannot work properly anymore. After that update, I can just use 200% scale setting. I'm so sorry to report this bug so late. Also, I tested both with only the builtin screen and with an external monitor in 'Join Display' mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 09:54:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 (Whiskey Lake) [19e5:3e0c] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX250] [19e5:3e0c] InstallationDate: Installed on 2020-05-02 (207 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56db IMC Networks ov9734_azurewave_camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI HBL-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=b1d9a025-3f1d-4fad-844f-c4e836944847 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1910537] Re: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI
> Their guess is that the linux notebook is not setting EDID > configuration correctly and thus not recognized by the ATEM, > while the cheap LCD screen propably does not care about EDID > and just plays everything, therefore a wrong EDID information > would not matter. EDIDs work the other way round. An EDID is not "set" by Linux. It is hard-coded in the monitor and only read by the computer. However it is sadly common for monitor manufacturers (probably not Blackmagic) to ship monitors that advertise faulty EDID data. That's probably what an "EDID manager" is to fix, but I don't know of and have no experience with any on Linux. I would like to analyse the EDID being advertised by your ATEM, but Xrandr.txt seems to show it was not plugged into HDMI when you logged this bug. Please plug it in and then run: xrandr --verbose > xrandr2.txt and attach the resulting file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910537 Title: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI Status in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
[Desktop-packages] [Bug 1910538] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 ** This bug is no longer a duplicate of bug 1910539 [nvidia] Cannot set scale of screen ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910539] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1870736, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: nvidia xrandr-scaling ** Summary changed: - Cannot set scale of screen + [nvidia] Cannot set scale of screen ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: [nvidia] Cannot set scale of screen Status in mutter package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.
The closed status is implicit. There are a few different Status values that Launchpad treats as "closed" so I will set one... ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Invalid Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910613] [NEW] Crash of gnome shell potentially from "JS ERROR: too much recursion" from app indicators
Public bug reported: What Happened: 1) Have gnome-shell-extensions-appindicator enabled 2) The only running app using the indicator was charmtimetracker ( https://github.com/KDAB/Charm ) 3) At some point usually within 1-2 days of office usage gnome shell crashes 4) Notice "JS ERROR: too much recursion" and then a stacktrace coming from appindicator extension in journalctl What I expected to happen: For gnome-shell not to crash :-) Full logs: - Recursion warnings - https://pastebin.ubuntu.com/p/hfKMmH4Dpx/ - Stack trace - https://pastebin.ubuntu.com/p/2TC6WFVcsG/ Short Summary of Logs: === First sign of incoming crash === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: too much recursion set active@resource:///org/gnome/shell/ui/popupMenu.js:199:29 _init@resource:///org/gnome/shell/ui/popupMenu.js:104:18 _init@resource:///org/gnome/shell/ui/popupMenu.js:273:15 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:498:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === This continues many times, last instance is like this === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: Exception in callback for signal: child-added: too much recursion PopupSubMenu@resource:///org/gnome/shell/ui/popupMenu.js:1017:9 _init@resource:///org/gnome/shell/ui/popupMenu.js:1201:21 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:494:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === Then there is a stacktrace (shortened repeats) === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: The offending signal was notify on StLabel 0x5615bd3eee80. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: == Stack trace for context 0x56159bbee930 == Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #0 7ffca7535bb0 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:620 (1c7e392cc2e0 @ 100) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #1 7ffca7535c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:510 (1c7e392cae98 @ 357) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #2 5615a5c69340 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:771 (1c7e392cc880 @ 41) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #3 7ffca7536b70 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #4 7ffca7536c60 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #5 7ffca7536d70 b resource:///org/gnome/gjs/modules/core/_signals.js:133 (1c7e392a84c0 @ 427) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #6 5615a5c69290 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:134 (1c7e392c5c40 @ 74) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #7 7ffca7537c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:365 (1c7e392ca718 @ 837) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #8 5615a5c690d0 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:326 (1c7e392ca6a0 @ 423) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #9 7ffca7538970 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #10 5615a5c69018 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2784371926a0 @ 312) Versions: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 $ apt policy gnome-shell mutter gnome-shell-extension-appindicator gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages mutter: Installed:
[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore
While it won't address your UX annoyances, I have filed an issue upstream proposing an approach to make live search faster for big files: https://gitlab.gnome.org/GNOME/gedit/-/issues/398 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore Status in gedit: Unknown Status in gedit package in Ubuntu: Invalid Bug description: i use gedit a lot, and i find it comfortable in general. the new small search window is extremely impractical. FOCUS PROBLEM: CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find and now, typing ESC brings one back to the former place! when trying to use CTRL-F again, the search string is replaced by new text. if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text. this is an extremely annoying feature/behavior. i simply would like to have the old search window + its behavior back. i am working very quickly and mostly using shortcuts. gedit now completely interrupts my way of working. additionally, where are the other search functions such as case- sensitive search? additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-etc-fashion is not good for quick workers with serious amounts of data. best wishes, vollmanr To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sssd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore
** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #398 https://gitlab.gnome.org/GNOME/gedit/-/issues/398 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/-/issues/398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore Status in gedit: Unknown Status in gedit package in Ubuntu: Invalid Bug description: i use gedit a lot, and i find it comfortable in general. the new small search window is extremely impractical. FOCUS PROBLEM: CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find and now, typing ESC brings one back to the former place! when trying to use CTRL-F again, the search string is replaced by new text. if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text. this is an extremely annoying feature/behavior. i simply would like to have the old search window + its behavior back. i am working very quickly and mostly using shortcuts. gedit now completely interrupts my way of working. additionally, where are the other search functions such as case- sensitive search? additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-etc-fashion is not good for quick workers with serious amounts of data. best wishes, vollmanr To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Used Software App -> Additional Drivers -> Using NVIDIA binary driver - version 340.108 from nvidia-340 (proprietary, tested), Apply Changes. Error message: pk-client-error-quark: Error while installing package: installed nvidia-340 package post-installation script subprocess returned error exit status 10(313) uname -r 5.8.0-34-generic lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
It affects me after yesterday upgrade to 5.8. Is the release for kernel 5.8 excepted? uname -r 5.8.0-34-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
It affects me after yesterday upgrade to 5.8. Is the release for kernel 5.8 excepted? uname -r 5.8.0-34-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)
Same problem here. It also affects: 5.8.0-34-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ uname -a Linux vanhalen 5.8.0-34-generic #37~20.04.2-Ubuntu SMP Thu Dec 17 14:53:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Also, this is valid: https://askubuntu.com/questions/969352 /uninstalling-and-then-reinstalling-nvidia-384-kills-colord In other words the shell bug is still there, however, fixing manually does not fix the problem, as some header problem stops the creation of the module. Any alternative? nouveau is heating up my system. Thanks in advance, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1885344 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel) Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description: Ubuntu 20.04 LTS Release: 20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910587] Re: Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed.
** Package changed: firefox (Ubuntu) => update-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1910587 Title: Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed. Status in update-manager package in Ubuntu: New Bug description: Note: Using terminal apt-get update and apt-get upgrade still seem to work. Software Updater will show the available upgrades, and allow me to click 'install now', but after clicking that button, I get a blank window with no updates. I've noticed this since the beginning of 2021, approximately. 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) Software Updater (update-manager) 1:20.04.10.2 3) I expected the listed upgrades to go through an install process, eventually being notified all upgrades had been installed and either it was complete or it required a restart. (This is all through the GUI of the Software Updater process.) 4) I was shown a blank window from Software Updater and no upgrades are processed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2220 F pulseaudio /dev/snd/pcmC0D0p: jason 2220 F...m pulseaudio BuildID: 20201221152838 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:09:44 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-07-04 (1283 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enx00249b28f1e5 proto dhcp metric 100 default via 10.0.0.1 dev wlp2s0 proto dhcp metric 600 10.0.0.0/24 dev enx00249b28f1e5 proto kernel scope link src 10.0.0.15 metric 100 10.0.0.0/24 dev wlp2s0 proto kernel scope link src 10.0.0.46 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=84.0.1/20201221152838 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-09-20 (108 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1910587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910587] Re: Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed.
** Package changed: ubuntu => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1910587 Title: Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed. Status in firefox package in Ubuntu: New Bug description: Note: Using terminal apt-get update and apt-get upgrade still seem to work. Software Updater will show the available upgrades, and allow me to click 'install now', but after clicking that button, I get a blank window with no updates. I've noticed this since the beginning of 2021, approximately. 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) Software Updater (update-manager) 1:20.04.10.2 3) I expected the listed upgrades to go through an install process, eventually being notified all upgrades had been installed and either it was complete or it required a restart. (This is all through the GUI of the Software Updater process.) 4) I was shown a blank window from Software Updater and no upgrades are processed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2220 F pulseaudio /dev/snd/pcmC0D0p: jason 2220 F...m pulseaudio BuildID: 20201221152838 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:09:44 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-07-04 (1283 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enx00249b28f1e5 proto dhcp metric 100 default via 10.0.0.1 dev wlp2s0 proto dhcp metric 600 10.0.0.0/24 dev enx00249b28f1e5 proto kernel scope link src 10.0.0.15 metric 100 10.0.0.0/24 dev wlp2s0 proto kernel scope link src 10.0.0.46 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=84.0.1/20201221152838 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-09-20 (108 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1910587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
** Package changed: ubuntu => nautilus (Ubuntu) -- 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/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: New Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910587] [NEW] Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed.
You have been subscribed to a public bug: Note: Using terminal apt-get update and apt-get upgrade still seem to work. Software Updater will show the available upgrades, and allow me to click 'install now', but after clicking that button, I get a blank window with no updates. I've noticed this since the beginning of 2021, approximately. 1) Description: Ubuntu 20.04.1 LTS Release:20.04 2) Software Updater (update-manager) 1:20.04.10.2 3) I expected the listed upgrades to go through an install process, eventually being notified all upgrades had been installed and either it was complete or it required a restart. (This is all through the GUI of the Software Updater process.) 4) I was shown a blank window from Software Updater and no upgrades are processed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2220 F pulseaudio /dev/snd/pcmC0D0p: jason 2220 F...m pulseaudio BuildID: 20201221152838 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:09:44 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-07-04 (1283 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enx00249b28f1e5 proto dhcp metric 100 default via 10.0.0.1 dev wlp2s0 proto dhcp metric 600 10.0.0.0/24 dev enx00249b28f1e5 proto kernel scope link src 10.0.0.15 metric 100 10.0.0.0/24 dev wlp2s0 proto kernel scope link src 10.0.0.46 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=84.0.1/20201221152838 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-09-20 (108 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- Software Updater reports possible updates, but shows a blank window afterwards. No updates are performed. https://bugs.launchpad.net/bugs/1910587 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] [NEW] Thunar and Nautilus USB drive ejecting takes long time
You have been subscribed to a public bug: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Thunar and Nautilus USB drive ejecting takes long time https://bugs.launchpad.net/bugs/1910455 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)
After updating the nvidia drivers, the login screen stopped showing. It helped to switch to the console ctrl + alt + f(1-9). Completely removed everything related to nvidia drivers. Reinstalled all drivers on a clean one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1885344 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel) Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description: Ubuntu 20.04 LTS Release: 20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909789] Re: YouTube flickers when in full screen (RADEON)
Probably chromium-bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1140606 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1909789 Title: YouTube flickers when in full screen (RADEON) Status in chromium-browser package in Ubuntu: New Bug description: How to repeat issue: 1) open Chromium Browser 2) got to YouTube 3) play video 4) press 'f' to enter to full screen The screen will flicker continuous between video and background. Flickering will stop when exit full screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-197.229-generic 4.4.241 Uname: Linux 4.4.0-197-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.28 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: On modes: enabled: disabled status: disconnected Date: Fri Jan 1 02:34:47 2021 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2010-05-13 (3885 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) Load-Avg-1min: 0.98 Load-Processes-Running-Percent: 0.5% MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-197-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: chromium-browser UpgradeStatus: Upgraded to xenial on 2019-03-20 (652 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1909789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910559] [NEW] GDM3: Black screen with blinking cursor
Public bug reported: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor Status in gdm3 package in Ubuntu: New Bug description: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.
Damn doesn't seem to be a close or delete option. Daniel could you please do the honours? -- 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/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Incomplete Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909946] Re: Gnome Wayland session starts, then quits.
Daniel I was pretty sure that the problem existed in my home directory. So, rather than go through all the gnome gnome settings one by one, with subsequent reboots, I cleaned out my home directory of all gnome specific settings at once this am, and rebooted and problem is gone - I'm now in XWayland. This would have taken a long time to troubleshoot, so I took the quick route it was a Fool's errand to try to figure out which setting was creating the problem, because I have backed up my home directory for over 10 years continuously, and I had a lot of cruft in there, so it was time to clean it out.I'm going to close this bug now, thanks for all your help Daniel I didn't want to waste any more of your time. Cheers. -- 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/1909946 Title: Gnome Wayland session starts, then quits. Status in gnome-shell package in Ubuntu: Incomplete Bug description: So, this started about a week ago after an update from Ubuntu. I can initially login with XWayland, but something loading after the desktop appears, causes the session to exit. The only thing I can find relevant in the logs at the timestamp this occurred are the following: -gkr-pam: unable to locate daemon control file -Failed to start Process error reports when automatic reporting is enabled. -A start job for unit UNIT has failed I hope this helps track down the issue. Thanks for reading. BTW I have to submit this as a bug on something else, launchpad keeps telling me that XWayland doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 Uname: Linux 5.9.16-xanmod1 x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 3 19:33:28 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [148c:2356] InstallationDate: Installed on 2020-04-25 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.1+git2012290142.009e2aa5460~g~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909012] Re: my display are disappeared with I used libreoffice or other software
As you can see from the attached photo, the central screen suddenly blackens when I hover while I was working on a word processor. The problem could be a conflict between opening shotwell program in the background, as could very well happen with other programs that still require cpu resources. I ask to have some answers and to be able to know if doing the upgrade of the ubuntu version, always in LTS, can solve some bugs. I ask for an answer to updates as well and also to the fact that I have to keep restarting my computer to fix these bugs. Thanks ** Attachment added: "IMG_20201222_123937.jpg" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909012/+attachment/5450285/+files/IMG_20201222_123937.jpg -- 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/1909012 Title: my display are disappeared with I used libreoffice or other software Status in libreoffice package in Ubuntu: New Bug description: I was using libreoffice writer while, pasting an image and printing it, the screen went black while I was moving the mouse, the menu of favorite programs remains clearly visible on the sides of the screen and at the top the bar with the clock in the center and on the right side the internet connection, audio volume and shutdown lights. This is not the first time this has happened, not only with libreoffice suite but also with other programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910538] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1910539 *** https://bugs.launchpad.net/bugs/1910539 ** This bug has been marked a duplicate of bug 1910539 Cannot set scale of screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909012] Re: my display are disappeared with I used libreoffice or other software
casa@casa-System-Product-Name:~$ sudo journalctl -f [sudo] password di casa: -- Logs begin at Fri 2020-06-05 13:14:15 CEST. -- gen 07 15:27:40 casa-System-Product-Name systemd[1]: mnt-9B78\x2dB5E9.mount: Job mnt-9B78\x2dB5E9.mount/start failed with result 'dependency'. gen 07 15:27:40 casa-System-Product-Name systemd[1]: dev-disk-by\x2duuid-9B78\x2dB5E9.device: Job dev-disk-by\x2duuid-9B78\x2dB5E9.device/start failed with result 'timeout'. gen 07 15:31:23 casa-System-Product-Name rtkit-daemon[1437]: Supervising 4 threads of 2 processes of 1 users. gen 07 15:31:23 casa-System-Product-Name rtkit-daemon[1437]: Supervising 4 threads of 2 processes of 1 users. gen 07 15:34:03 casa-System-Product-Name dbus-daemon[1175]: [session uid=1000 pid=1175] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.102' (uid=1000 pid=3326 comm="/usr/bin/gnome-terminal.real " label="unconfined") gen 07 15:34:03 casa-System-Product-Name systemd[1025]: Starting GNOME Terminal Server... gen 07 15:34:03 casa-System-Product-Name dbus-daemon[1175]: [session uid=1000 pid=1175] Successfully activated service 'org.gnome.Terminal' gen 07 15:34:03 casa-System-Product-Name systemd[1025]: Started GNOME Terminal Server. gen 07 15:34:16 casa-System-Product-Name sudo[3349]: casa : TTY=pts/0 ; PWD=/home/casa ; USER=root ; COMMAND=/bin/journalctl -f gen 07 15:34:16 casa-System-Product-Name sudo[3349]: pam_unix(sudo:session): session opened for user root by (uid=0) -- 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/1909012 Title: my display are disappeared with I used libreoffice or other software Status in libreoffice package in Ubuntu: New Bug description: I was using libreoffice writer while, pasting an image and printing it, the screen went black while I was moving the mouse, the menu of favorite programs remains clearly visible on the sides of the screen and at the top the bar with the clock in the center and on the right side the internet connection, audio volume and shutdown lights. This is not the first time this has happened, not only with libreoffice suite but also with other programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910539] Re: Cannot set scale of screen
This is screenshot after clicking apply (to access print screen had to click keep changes button too) ** Attachment added: "After click on apply" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+attachment/5450246/+files/Screenshot%20from%202021-01-07%2020-52-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910537] [NEW] incorrect audio-EDID on HDMI, blocking audio transmission over HDMI
Public bug reported: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug
[Desktop-packages] [Bug 1910538] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910538/+attachment/5450200/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1910539] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910539/+attachment/5450223/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) Status in debconf package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Status in debconf source package in Focal: Confirmed Status in gtk+3.0 source package in Focal: New Bug description: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
@Mark, my understanding from the previous messages is that it's in "proposed" at present. Once it's gone through the processes explained above, it is released to 20.04 main. I.e. we all get the update normally. "N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days." - https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1899206/comments/50 -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [ Impact ] Mutter 3.36.2 breaks custom input settings [ Test case ] - Set custom settings using gnome-control-center (set custom Delay and Speed in Settings > Accessibility > Repeat Keys) or gnome-tweaks (under Additional Layout options) - Unplug / replug the input device or suspend / resume - Input device settings should be preserved [ Regression potential ] Devices added or removed may be not noticed by gnome-shell. --- I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717113] Re: thunderbird FTBFS on 390x in Artful and later
This was fixed a while ago. Note that no real testing is done on s390x as it's not a supported desktop platform, but at least the package builds there. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1717113 Title: thunderbird FTBFS on 390x in Artful and later Status in thunderbird package in Ubuntu: Fix Released Bug description: Thunderbird 1:52.2.1+build1-0ubuntu1 fails to build in Artful. https://launchpad.net/ubuntu/+source/thunderbird/1:52.2.1+build1-0ubuntu1/+build/12854586 : ... ^~~~ In file included from /<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/nsExceptionHandler.cpp:62:0, from /<>/thunderbird-52.2.1+build1/obj-arm-linux-gnueabihf/toolkit/crashreporter/Unified_cpp_crashreporter0.cpp:2: /<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:21: error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’ struct ucontext context; ^~~ /<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:12: note: forward declaration of ‘struct google_breakpad::ucontext’ struct ucontext context; ^~~~ /<>/thunderbird-52.2.1+build1/mozilla/config/rules.mk:951: recipe for target 'Unified_cpp_crashreporter0.o' failed make[5]: *** [Unified_cpp_crashreporter0.o] Error 1 ... The new upstream release (52.3.0) may fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1717113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
This bug was fixed in the package signon - 8.59+17.10.20170606-0ubuntu2.20.04.1 --- signon (8.59+17.10.20170606-0ubuntu2.20.04.1) focal; urgency=medium * Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd break compatibility with QProcess (LP: #1901609) * Build depend on quilt and integrate into debian/rules. Since this this source uses the legacy v1 format we need to manually wire up patching instead of having dpkg-source handle it -- Harald Sitter Mon, 23 Nov 2020 13:24:59 +0100 ** Changed in: signon (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
** Changed in: signon (Ubuntu Focal) Status: Incomplete => Opinion ** Changed in: signon (Ubuntu Focal) Status: Opinion => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
Will this be available in 20.04? Or is the recommendation for everyone to upgrade mutter manually? -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [ Impact ] Mutter 3.36.2 breaks custom input settings [ Test case ] - Set custom settings using gnome-control-center (set custom Delay and Speed in Settings > Accessibility > Repeat Keys) or gnome-tweaks (under Additional Layout options) - Unplug / replug the input device or suspend / resume - Input device settings should be preserved [ Regression potential ] Devices added or removed may be not noticed by gnome-shell. --- I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910521] [NEW] libappindicator breaks left-mouse actions for most applications
Public bug reported: Hello, because GTK will drop tray icon support in version 4, many projects switch to libappindicator instead. Some are network-manager-applet, blueman-tray and electron (affecting all electron apps). The latter 2 automatically use libappindicator if it's available in the system. For most applications, with libappindicator the tray icon behavior is broken (at least on archlinux with xfce4 and libappindicator-gtk3): * left mouse button triggers the context menu rather than the left-mouse-button action * the context menu is located beneath the mouse button, so when the mouse is released, the action is performed (in most cases "exit application"). Since the web is full of issue reports about this, I'm, pretty sure it's an issue in libappindicator itself than in every single application that uses it. IMO this is a critical issue, especially for a library that provides tray support to applications. Kind regards, Michael. ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libappindicator in Ubuntu. https://bugs.launchpad.net/bugs/1910521 Title: libappindicator breaks left-mouse actions for most applications Status in libappindicator package in Ubuntu: New Bug description: Hello, because GTK will drop tray icon support in version 4, many projects switch to libappindicator instead. Some are network-manager-applet, blueman-tray and electron (affecting all electron apps). The latter 2 automatically use libappindicator if it's available in the system. For most applications, with libappindicator the tray icon behavior is broken (at least on archlinux with xfce4 and libappindicator-gtk3): * left mouse button triggers the context menu rather than the left-mouse-button action * the context menu is located beneath the mouse button, so when the mouse is released, the action is performed (in most cases "exit application"). Since the web is full of issue reports about this, I'm, pretty sure it's an issue in libappindicator itself than in every single application that uses it. IMO this is a critical issue, especially for a library that provides tray support to applications. Kind regards, Michael. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1910521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
On 2021-01-05 09:13, Gunnar Hjalmarsson wrote: > In case of the former, the idea with replacing the packages with > dummies soon appears to be even more desirable than I first thought. Chris Coulson has just done that for adobe-flashplugin. So now we provide dummies in hirsute, all the supported releases, and also trusty and precise. Also flashplugin-installer is now a dummie in focal, bionic and xenial. Please consider to do the same for at least pepperflashplugin-nonfree instead of just dropping it from hirsute. ** Changed in: adobe-flashplugin (Ubuntu) Status: New => Fix Released ** Changed in: adobe-flashplugin (Ubuntu) Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) => Chris Coulson (chrisccoulson) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in adobe-flashplugin package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: New Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox
content of make.log : DKMS make.log for virtualbox-guest-6.1.10 for kernel 5.8.0-34-generic (x86_64) jeu. 07 janv. 2021 09:20:12 CET make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic' CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/VBoxGuest.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/VBoxGuest-linux.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/common/string/strformatrt.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-agnostic.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.o In file included from /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.c:30: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtR0MemAllocExecVmArea’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:171:15: error: implicit declaration of function ‘__get_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration] 171 | pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END); | ^ | get_vm_area /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:171:13: warning: assignment to ‘struct vm_struct *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 171 | pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END); | ^ /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:204:14: error: implicit declaration of function ‘map_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration] 204 | if (!map_vm_area(pVmArea, PAGE_KERNEL_EXEC, | ^~~ | get_vm_area In file included from /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.c:33: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeFree’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:596:43: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 596 | down_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:611:41: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 611 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1079:31: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1079 | down_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1165:33: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1165 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1192:29: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1192 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1607:36: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1607 | down_write(>mm->mmap_sem); |^~~~ |mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1724:34: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1724 | up_write(>mm->mmap_sem); | ^~~~ | mmap_base cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:288: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [scripts/Makefile.build:519:
[Desktop-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox
Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-guest-dkms.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/virtualbox-guest/6.1.10/build/make.log for more information. dpkg: error processing package virtualbox-guest-dkms (--configure): installed virtualbox-guest-dkms package post-installation script subprocess returned error exit status 1 0 Setting up virtualbox-guest-utils (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Setting up xmount (0.7.6-2) ... Setting up virtualbox-guest-x11 (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.3) ... Errors were encountered while processing: virtualbox-guest-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910503] [NEW] latest kernel breaks display full sizing in virtualbox
Public bug reported: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in xorg package in Ubuntu: New Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub,