[Desktop-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset
That is a very good observation about not having to be on startup!! After I disabled both vmware.service and virtualbox.service, I cleaned-up: delete the '/root' and then make sure to mount it from the zfs dataset. Then I shutdown the system yesterday evening (2020-06-25). When I started the system this morning (2020-06-26): I saw that again the zfs dataset could not be mounted because a '/root' already exists, this time with an empty ".cache" folder in it. So it seems you were right about the vwmware or virtualbox that they use pulseaudio as root. But that is not the real issue: problem is with the ".cache" folder which is created at shutdown 'after' the zfs dataset is unmounted, just like you said. I'm not sure how to investigate what happens at shutdown, but I'll try to find out. Meanwhile it's clear this not a pulseaudio issue ==> this ticket should be closed (I'm not sure if I can do that, or you or someone else needs to do it). Daniel, thank you very much for your quick and very helpful responses: I appreciate it a lot! Filesystem details after a night of shutdown: - root@minighost:~# pwd /root root@minighost:~# ls -la total 10 drwxr-xr-x 3 root root 3 Jun 26 07:12 . drwxr-xr-x 34 root root 38 Jun 25 20:12 .. drwx-- 2 root root 2 Jun 25 20:23 .cache root@minighost:~# tree -a . └── .cache 1 directory, 0 files root@minighost:~# - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: - root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# - Extra details: - Ubuntu release: - root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 - - status of 'zfs-mount.service' is the following: - root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# - - software versions: - root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
Good, bug 1884925 is what I need to look at then. But I can't because it is private. Are you able to set bug 1884925 to public? -- 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/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
the file was in /var/crash hence where bug #1884925 's contents came from -- 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/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
Try this: Settings > Privacy > Diagnostics > Send error reports to Canonical = Automatic then reproduce the crash and hopefully errors.ubuntu.com will show it. Although I would hope that even with 'Manual' set you would find the crash file in /var/crash ..? -- 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/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800
[Desktop-packages] [Bug 1882410] Re: GNOME Shell crashed with signal 5
still nothing in https://errors.ubuntu.com/user/ID since 2017 -- 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/1882410 Title: GNOME Shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Incomplete Bug description: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868
[Desktop-packages] [Bug 1885242] Re: intel graphics
Please describe the problem you are experiencing. ** 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/1885242 Title: intel graphics Status in Ubuntu: Incomplete Bug description: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY25PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/+bug/1885242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885242] [NEW] intel graphics
Public bug reported: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY25PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 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/1885242 Title: intel graphics Status in xorg package in Ubuntu: New Bug description: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP
[Desktop-packages] [Bug 1232873] Re: "could not back up files" dialog never shown; breaks scheduled backups
--auto is how we launch the background backups. I think this bug has been fixed in recent releases by a more concerted effort to keep the progress windows on top of the rest of the interface. But if folks can still reproduce using a recent Deja Dup (40+ I’d say), please reopen and I can try to reproduce. ** Changed in: deja-dup Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1232873 Title: "could not back up files" dialog never shown; breaks scheduled backups Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Incomplete Status in deja-dup package in Arch Linux: New Bug description: On the conclusion of a backup, if any nonreadable files exist in the backup source directories, Deja Dup shows a notification at the bottom of my screen telling me that the backup completed but not all files were able to be backed up; "see dialog for details". However, this dialog never appears. As a result, the "deja-dup --backup --auto" process never terminates, as it's waiting for me to close a dialog that never appeared in the first place. This effectively breaks the automatic, "set-and-forget" backup strategy, as deja-dup-monitor will not launch another scheduled backup until the deja-dup process exits, which will never happen. This only happens when deja-dup is launched with "deja-dup --backup --auto"; launching with "deja-dup --backup" (no auto) does show the dialog at the end of the process, allowing me to close it and properly terminate the backup. ~$ lsb_release -d Description: Ubuntu Saucy Salamander (development branch) ~$ dpkg-query -W deja-dup duplicity deja-dup 27.3.1-0ubuntu1 duplicity 0.6.21-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1232873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885167] Re: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1885167 Title: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found Status in libfprint package in Ubuntu: New Bug description: After installing ubuntu and inspecting the drivers and whats working and what not I foudn that a lot of people are having problems with fingerprint on these two models, as I can see IML verzions got support recently so I hope this should be a quick fix. Fingerprint sensor is not working and it's not detected by kernel at all. Currently running on the latest version of Ubuntu. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: almir 974 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=b236fe34-8dda-44ae-ad12-6af861ad21d7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN17WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1885167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculater not open
Please watch this ** Attachment added: "Watch" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+attachment/5387274/+files/15931401782894331137486421409278.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculater not open Status in gnome-calculator package in Ubuntu: Incomplete Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1882453] Re: [nvidia] GUI blanks after long period of use
Daniel, The attached photo has memory utilization data on the Nivida GPU on typical use. I'll try to figure out how to force the problem on demand. I believe its related to an application I'm using, however the problem has not returned and I've updated the driver a few times already. Thanks Daniel, Chris Morales On 6/15/20 21:58, Daniel van Vugt wrote: > Thanks. Although system memory is perfectly healthy and there's no > obvious leak in gnome-shell, I suspect the problem here might be a leak > of GPU memory/resources (which won't show up in 'ps') > > Are you able to find some Nvidia tools to report GPU memory usage? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882453 > > Title: >[nvidia] GUI blanks after long period of use > > Status in gnome-shell package in Ubuntu: >Incomplete > > Bug description: >GUI screen goes blank with a right click on the desktop or a click on >the power button. The entire systems seems to slow too, with CPU >utilization reaching 100% at a consistent interval. This has happened >twice already after a long period of idle or when conducting many >actions with several applications. Not sure if any of it is causation >given its only happened twice and I can't replicate the problem >consistently. If you need further information reach me at >clmora...@pm.me. > >ProblemType: Bug >DistroRelease: Ubuntu 20.04 >Package: xorg 1:7.7+19ubuntu14 >ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 >Uname: Linux 5.4.0-34-generic x86_64 >NonfreeKernelModules: nvidia_modeset nvidia >.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:06: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 440.64 Fri Feb 21 > 01:17:26 UTC 2020 > GCC version: >ApportVersion: 2.20.11-0ubuntu27.3 >Architecture: amd64 >BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >CasperMD5CheckResult: skip >CompositorRunning: None >CurrentDesktop: ubuntu:GNOME >Date: Sun Jun 7 15:00:40 2020 >DistUpgraded: Fresh install >DistroCodename: focal >DistroVariant: ubuntu >ExtraDebuggingInterest: Yes >GraphicsCard: > NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] >InstallationDate: Installed on 2020-05-20 (17 days ago) >InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) >MachineType: MSI MS-7885 >ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash >ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic > root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7 >SourcePackage: xorg >Symptom: display >UpgradeStatus: No upgrade log present (probably fresh install) >dmi.bios.date: 03/20/2015 >dmi.bios.vendor: American Megatrends Inc. >dmi.bios.version: 1.80 >dmi.board.asset.tag: To be filled by O.E.M. >dmi.board.name: X99A SLI PLUS(MS-7885) >dmi.board.vendor: MSI >dmi.board.version: 1.0 >dmi.chassis.asset.tag: To Be Filled By O.E.M. >dmi.chassis.type: 3 >dmi.chassis.vendor: MSI >dmi.chassis.version: 1.0 >dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: >dmi.product.family: To be filled by O.E.M. >dmi.product.name: MS-7885 >dmi.product.sku: To be filled by O.E.M. >dmi.product.version: 1.0 >dmi.sys.vendor: MSI >version.compiz: compiz N/A >version.libdrm2: libdrm2 2.4.101-2 >version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 >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.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/gnome-shell/+bug/1882453/+subscriptions ** Attachment added: "GTX_970_stats.png" https://bugs.launchpad.net/bugs/1882453/+attachment/5387273/+files/GTX_970_stats.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu.
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- 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/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/gnome-control-center/+bug/1874567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876551] Re: Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1876551 Title: Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Upgraded from 19.10 to 20.04. Running: * NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) * Gigabyte P55A-UD4 * Intel Core i7 860 * 2x DELL U2413 1920x1200 * One connected via DVI in landscape * Detected as #2 * Positioned on the left * Configured to be screen with dock/launcher * One connected via HDMI in portrait * Detected as 1 * Positioned on the right Upon logging into my normal gnome session, the right display (detected as display 1) was no longer rotated to portrait orientation. Attempting to do this through the normal Gnome settings panel appears to disable monitor 1 which I want to rotate, and increase the virtual desktop size on monitor 2. Without rotation, both monitors are functioning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 15:52:13 2020 InstallationDate: Installed on 2016-01-21 (1563 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1876551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885235] Re: python 3.8 bugs in hplip / focal upgrade
*** This bug is a duplicate of bug 1870019 *** https://bugs.launchpad.net/bugs/1870019 ** This bug has been marked a duplicate of bug 1870019 HPLIP: SyntaxWarning, using is or is not, did you mean == or != ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1885235 Title: python 3.8 bugs in hplip / focal upgrade Status in hplip package in Ubuntu: New Bug description: /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1885235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
I also logged https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-340/+bug/1876551 about nvidia-340 drivers having the same problem (won't remember the config). My workaround is a .desktop file that calls xrandr with my desired parameters I configured with nvidia tool and then dumped out with xrandr. ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- 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/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/gnome-control-center/+bug/1874567/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1884754] Re: Fractional scaling not persisted in VMware Player
Thanks for pointing that out. That sounds relevant to bug 1885026 and this one... In the case of this bug it explains why the fractional scaling value is not persisted -- because the virtual monitor resolution has changed. Mutter considers that a different display configuration and so won't keep any old settings from it. You can see this as a separate block in your ~/.config/monitors.xml ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - Fractional scaling not persisted in VMware Player + Fractional scaling does not persist across reboots in resizable VM windows -- 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/1884754 Title: Fractional scaling does not persist across reboots in resizable VM windows Status in mutter package in Ubuntu: Triaged Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885026] Re: Fractional scaling contains 175% option twice
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/9 -- 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/1885026 Title: Fractional scaling contains 175% option twice Status in gnome-control-center package in Ubuntu: New Bug description: When opening the Settings, select Displays and then enable "Fractional Scaling". The Scale options change to 100% / 125% / 175% / 175% / 250% If you click the first 175% option it will even automatically select the second one instead. The third option should likely be 150% instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 15:21:07 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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-control-center/+bug/1885026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculater not open
Please open the 'Terminal' app and type: snap connections gnome-calculator Now what text do you see in the Terminal window? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculater not open Status in gnome-calculator package in Ubuntu: Incomplete Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885235] [NEW] python 3.8 bugs in hplip / focal upgrade
Public bug reported: /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1885235 Title: python 3.8 bugs in hplip / focal upgrade Status in hplip package in Ubuntu: New Bug description: /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1885235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Unfortunately all the duplicates of this bug have now moved to bug 1874567. I think that might be overly confusing, especially if it turns out to not be fixed. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877939] Re: Unwanted desktop panning when using two displays
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1877939 Title: Unwanted desktop panning when using two displays Status in xorg package in Ubuntu: New Bug description: I use two displays. One has a resolution of 3840x2160, and another one is to the right of that with a resolution of 1080x1920 in "Portrait Left" mode. I use "Join Displays" in Settings > Displays. When I configure this setup using Settings > Displays, my main desktop ends up being too big, extending to the secondary monitor to the right. When I move my mouse to the right edge of the secondary screen, the desktop pans. When I arrange the secondary monitor to the left of my main display, this bug does not occur. Secondary monitor on the right (bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+3840+0 right (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 708mm x 399mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) Secondary monitor on the left (no bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 4920 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+0+0 right (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+1080+0 (normal left inverted right x axis y axis) 708mm x 399mm 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) The only difference between these two situations is that I dragged the monitor from the right to the left in Settings > Displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 09:03:00 2020 DistUpgraded: 2020-05-10 23:03:38,881 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-51-generic, x86_64: installed nvidia, 435.21, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106 [GeForce RTX 2060 Rev. A] [103c:6903] InstallationDate: Installed on
[Desktop-packages] [Bug 1878371] Re: Displays overlap
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1878371 Title: Displays overlap Status in xorg package in Ubuntu: New Bug description: Displays were correct under 19.10, upgraded to 20.04. I have 2 monitors. Mon1: Right, Portrait is 1920x1080. Mon2: Left, Landscape is 3840x2160. The display to Mon2 overlaps Mon1 display by approx 90%. Moving cursor to far right causes display 2 on Mon2 to slide left. Moving cursor to far left causes display 2 to slide right over the top of display 1. Both displays in settings are correct. The problem appears as if the window for display 2 is a port on a screen approx 5000x2160. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 09:31:07 2020 DistUpgraded: 2020-05-12 14:33:26,654 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-51-generic, x86_64: installed nvidia, 390.132, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:858b] InstallationDate: Installed on 2017-03-02 (1167 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05430fcd-4b22-4784-bef0-4438e1c00dd8 ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 11/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9904 dmi.board.asset.tag: Default string dmi.board.name: X99-A II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9904:bd11/30/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-08-17T11:15:24.518740 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue May 12 21:39:37 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1876170] Re: [nvidia] Monitor setups including portrait orinted monitors cause horizontal resolution to increase
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1876170 Title: [nvidia] Monitor setups including portrait orinted monitors cause horizontal resolution to increase Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: With a multi-monitor setup that includes one portrait oriented screen, most of the time several of the monitors end up with extended horizontal resolution to the right, resulting in panning when you move the mouse, as well as overlap between the screen areas. I can occasionally make it behave after some enabling, disabling and orientation changes of the monitors, but seemingly only if I have them all in a row and don't have the portrait one furthest to the right. Attempted setup that breaks: --- |1920x1080 | |nvidia egpu|1080| --- --- ---|x | |2560x1440 |1920x1080 |1920x1080 |1920| |laptop internal|nvidia egpu|nvidia egpu|egpu| | |--- --- --- Also attached screenshot that should illustrate the issue well. I can't tell for sure if this is an xorg issue or a nvidia one, I did look at both arandr and nvidia-settings and in neither can I see anything amiss. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 20:18:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104 [GeForce RTX 2070 SUPER] [1043:8727] InstallationDate: Installed on 2020-04-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L5CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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
[Desktop-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac)
[Desktop-packages] [Bug 1876621] Re: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1876621 Title: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes Status in xorg package in Ubuntu: New Bug description: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/1876621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1881342 Title: Display settings are completely broken in 20.04 Status in xorg package in Ubuntu: New Bug description: This is after doing a fresh Ubuntu 20.04 installation, on my machine equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait mode. This used to work properly in Ubuntu 19.10, but is utterly broken in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work anymore. It'd be much easier to show what's going on with a video, so here goes: https://youtu.be/OHxKWfSxhsE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1879058 Title: Display viewport incorrect with 90° rotated displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-30 (383 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx: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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Since most of the bug reports are about this issue and not the other issue, I will unmark it right now. While I still have a clear list of most of the bug reports that should be moved back to this one. ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874914] Re: Gnome Shell panel stretches across 1.5 monitors
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1874914 Title: Gnome Shell panel stretches across 1.5 monitors Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The title bar stretches ~1/2 way onto the second screen. Also when I move the mouse to the right the whole screen scrolls the width of the overlap. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 14:00:34 2020 DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-46-generic, x86_64: installed nvidia, 440.64, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2018-05-23 (702 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67GD dmi.board.vendor: Intel Corporation dmi.board.version: AAG10206-207 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/gnome-shell/+bug/1874914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same issue here - I can't switch to HSP/HFP mode on Ubuntu 20.04 uname -r 5.4.0-39-generic pulseaudio --version pulseaudio 13.99.1 Device 38:18:4C:94:DE:B2 (public) Name: WH-1000XM3 Alias: WH-1000XM3 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d) UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351) UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7) UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba) UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b) UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15) Modalias: usb:v054Cp0CD3d0422 ManufacturerData Key: 0x012d ManufacturerData Value: 04 00 01 31 00 01 b3 ee e4 3f 00 60 d0 00 00 00 ...1.?.` 00 00 00 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885167] Re: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found
** Summary changed: - Lenovo Thinkbook 14-IIL and 15-IIL Fingerprint not found + 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1885167 Title: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found Status in libfprint package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: After installing ubuntu and inspecting the drivers and whats working and what not I foudn that a lot of people are having problems with fingerprint on these two models, as I can see IML verzions got support recently so I hope this should be a quick fix. Fingerprint sensor is not working and it's not detected by kernel at all. Currently running on the latest version of Ubuntu. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: almir 974 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=b236fe34-8dda-44ae-ad12-6af861ad21d7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN17WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1885167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized
I see a similar issue with the "Device not trusted yet" dialog when plugging in an iPhone. Is that the same bug? Please see the screenshot. ** Attachment added: "Device not trusted yet - text cut off, ellipsized" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+attachment/5387236/+files/Device%20not%20trusted%20yet%20text%20cut%20off.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Shell dialog text is truncated and ellipsized Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: Boxes wants to inhibit shortcuts You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:29:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
@3v1n0 I did some further testing with your mutter package and noticed some important issues. Even though scaling works mostly ok, I noticed a consistent side-effect on X applications that they scale in reverse to the rest of the UI. So Gnome Shell, GTK apps and QT apps will scale 125% but at the same time X apps will scale 0.75% (or lower) and they ll become super tiny. You can test this with Gimp xterm and XNethack. -- 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 1885130] Re: Please add a way to show only open-source apps
Okay, filed https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 Would be nice if ubuntu-bug sent me there directly. I'm getting tired of having to file a lot of bug reports twice. Sometimes downstream says go to upstream, sometimes upstream says go to downstream. The app displays as Ubuntu Software, but its CLI / package name is gnome- software. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1021 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps Status in gnome-software package in Ubuntu: New Bug description: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885170] Re: Feature request: make nemo the default file manager instead of nautilus
Thank you for your bug report, the bug tracker isn't the right place for a such discussion though, you should better post on https://discourse.ubuntu.com/ explaining why you think switching would be the right solution ** Changed in: nautilus (Ubuntu) Importance: Undecided => Wishlist ** Changed in: nautilus (Ubuntu) Status: New => Opinion -- 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/1885170 Title: Feature request: make nemo the default file manager instead of nautilus Status in nautilus package in Ubuntu: Opinion Bug description: I'd like to propose that you make nemo the default file manager packaged with Ubuntu in the future instead of Nautilus. My justification is centered around utility, use of space, and features. Please see the portion of my answer near the bottom titled "Why use nemo over Ubuntu's default nautilus file manager?" here: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
@3v1n0 You are indeed right. The new mutter package was not installed from the ppa for some reason. I think it should be ok now. Version is 3.36.3-0ubuntu0.20.04.1.nv1 I am happy to report that fractional scaling works now. Compositor behavior seems a bit weird(as if there is more tearing) when moving windows but that just might be my idea. Please find attached the new logs ** Attachment added: "new_mutter.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5387222/+files/new_mutter.log -- 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 1885170] [NEW] Feature request: make nemo the default file manager instead of nautilus
Public bug reported: I'd like to propose that you make nemo the default file manager packaged with Ubuntu in the future instead of Nautilus. My justification is centered around utility, use of space, and features. Please see the portion of my answer near the bottom titled "Why use nemo over Ubuntu's default nautilus file manager?" here: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the-default- file-manager-in-ubuntu-18-04/1173861#1173861. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1885170 Title: Feature request: make nemo the default file manager instead of nautilus Status in nautilus package in Ubuntu: New Bug description: I'd like to propose that you make nemo the default file manager packaged with Ubuntu in the future instead of Nautilus. My justification is centered around utility, use of space, and features. Please see the portion of my answer near the bottom titled "Why use nemo over Ubuntu's default nautilus file manager?" here: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883253] Re: no Multi-Arch support
This bug was fixed in the package gamemode - 1.5.1-0ubuntu6 --- gamemode (1.5.1-0ubuntu6) groovy; urgency=medium * debian/*.install: - use the correct paths for other architectures -- Sebastien Bacher Thu, 25 Jun 2020 17:58:01 +0200 ** Changed in: gamemode (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/1883253 Title: no Multi-Arch support Status in gamemode package in Ubuntu: Fix Released Bug description: @seb128 please rebase gamemode against the Debian version 1.5.1-4 and include Multi-Arch support. There are a lot of upstream bug reports because 32bit support is missing in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1883253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876170] Re: [nvidia] Monitor setups including portrait orinted monitors cause horizontal resolution to increase
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1876170 Title: [nvidia] Monitor setups including portrait orinted monitors cause horizontal resolution to increase Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: With a multi-monitor setup that includes one portrait oriented screen, most of the time several of the monitors end up with extended horizontal resolution to the right, resulting in panning when you move the mouse, as well as overlap between the screen areas. I can occasionally make it behave after some enabling, disabling and orientation changes of the monitors, but seemingly only if I have them all in a row and don't have the portrait one furthest to the right. Attempted setup that breaks: --- |1920x1080 | |nvidia egpu|1080| --- --- ---|x | |2560x1440 |1920x1080 |1920x1080 |1920| |laptop internal|nvidia egpu|nvidia egpu|egpu| | |--- --- --- Also attached screenshot that should illustrate the issue well. I can't tell for sure if this is an xorg issue or a nvidia one, I did look at both arandr and nvidia-settings and in neither can I see anything amiss. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 20:18:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU104 [GeForce RTX 2070 SUPER] [1043:8727] InstallationDate: Installed on 2020-04-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L5CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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
[Desktop-packages] [Bug 1874914] Re: Gnome Shell panel stretches across 1.5 monitors
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1874914 Title: Gnome Shell panel stretches across 1.5 monitors Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The title bar stretches ~1/2 way onto the second screen. Also when I move the mouse to the right the whole screen scrolls the width of the overlap. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 14:00:34 2020 DistUpgraded: 2020-04-24 13:37:27,004 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-46-generic, x86_64: installed nvidia, 440.64, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-46-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2018-05-23 (702 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=6aabc146-ac5f-4072-a83d-2cdc70d0615f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67GD dmi.board.vendor: Intel Corporation dmi.board.version: AAG10206-207 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-207:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/gnome-shell/+bug/1874914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 Marking this as duplicate of #1874567 for now, if it's not the case, unmark it. ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876621] Re: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1876621 Title: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes Status in xorg package in Ubuntu: New Bug description: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/1876621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877939] Re: Unwanted desktop panning when using two displays
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1877939 Title: Unwanted desktop panning when using two displays Status in xorg package in Ubuntu: New Bug description: I use two displays. One has a resolution of 3840x2160, and another one is to the right of that with a resolution of 1080x1920 in "Portrait Left" mode. I use "Join Displays" in Settings > Displays. When I configure this setup using Settings > Displays, my main desktop ends up being too big, extending to the secondary monitor to the right. When I move my mouse to the right edge of the secondary screen, the desktop pans. When I arrange the secondary monitor to the left of my main display, this bug does not occur. Secondary monitor on the right (bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+3840+0 right (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 708mm x 399mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) Secondary monitor on the left (no bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 4920 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+0+0 right (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+1080+0 (normal left inverted right x axis y axis) 708mm x 399mm 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) The only difference between these two situations is that I dragged the monitor from the right to the left in Settings > Displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 09:03:00 2020 DistUpgraded: 2020-05-10 23:03:38,881 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-51-generic, x86_64: installed nvidia, 435.21, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106 [GeForce RTX 2060 Rev. A] [103c:6903] InstallationDate: Installed on
[Desktop-packages] [Bug 1878371] Re: Displays overlap
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1878371 Title: Displays overlap Status in xorg package in Ubuntu: New Bug description: Displays were correct under 19.10, upgraded to 20.04. I have 2 monitors. Mon1: Right, Portrait is 1920x1080. Mon2: Left, Landscape is 3840x2160. The display to Mon2 overlaps Mon1 display by approx 90%. Moving cursor to far right causes display 2 on Mon2 to slide left. Moving cursor to far left causes display 2 to slide right over the top of display 1. Both displays in settings are correct. The problem appears as if the window for display 2 is a port on a screen approx 5000x2160. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 09:31:07 2020 DistUpgraded: 2020-05-12 14:33:26,654 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-51-generic, x86_64: installed nvidia, 390.132, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:858b] InstallationDate: Installed on 2017-03-02 (1167 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05430fcd-4b22-4784-bef0-4438e1c00dd8 ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 11/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9904 dmi.board.asset.tag: Default string dmi.board.name: X99-A II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9904:bd11/30/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-08-17T11:15:24.518740 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue May 12 21:39:37 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1879058 Title: Display viewport incorrect with 90° rotated displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-30 (383 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac)
[Desktop-packages] [Bug 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx: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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1881342 Title: Display settings are completely broken in 20.04 Status in xorg package in Ubuntu: New Bug description: This is after doing a fresh Ubuntu 20.04 installation, on my machine equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait mode. This used to work properly in Ubuntu 19.10, but is utterly broken in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work anymore. It'd be much easier to show what's going on with a video, so here goes: https://youtu.be/OHxKWfSxhsE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
@mastorak: are you sure you're using those packages? I don't see any reference in the logs. @blitmaps, most of the developers use intel or free drivers all the time, so testing in other scenarios is not always possible. Also this bug has at least three different behaviors depending on GPU hardware, for example in my Prime hardware it behaves correctly, while it doesn't in another prime hardware I recently got. -- 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 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium
For reference, this PR might fix it. https://github.com/snapcore/fc-
cache-static-builder/pull/2/files
--
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/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
rendering issue in chromium
Status in chromium-browser package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling
> Disabling fullscreen unredirection sounds like a good option. Well, I was thinking about that, but it also causes slowdown in games and D-R videos, so while resizing the UI might be not optimal it also allows better performances in such scenarios. -- 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/1871849 Title: Full screen videos suddenly change scale when using fractional scaling Status in mutter package in Ubuntu: Confirmed Bug description: firefox does not properly play full screen videos using fractional scale at 125% --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-29 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885159] [NEW] Firefox after update doesn't start - Ubuntu 16.04.6 LTS
Public bug reported: After latest FF beta update - Firefox doesn't start (also there is no crash). In system monitor Firefox process is visible, but still app doesn't appear.Starting in safe mode doesn't help. Previous version: 77.0.1+build1-0ubuntu0.16.04.1 Updated version: 78.0+build1-0ubuntu0.16.04.2 Ubuntu version: Ubuntu 16.04.6 LTS Apport bug report attached. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport.firefox.nkp4vez_.apport" https://bugs.launchpad.net/bugs/1885159/+attachment/5387177/+files/apport.firefox.nkp4vez_.apport -- 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/1885159 Title: Firefox after update doesn't start - Ubuntu 16.04.6 LTS Status in firefox package in Ubuntu: New Bug description: After latest FF beta update - Firefox doesn't start (also there is no crash). In system monitor Firefox process is visible, but still app doesn't appear.Starting in safe mode doesn't help. Previous version: 77.0.1+build1-0ubuntu0.16.04.1 Updated version: 78.0+build1-0ubuntu0.16.04.2 Ubuntu version: Ubuntu 16.04.6 LTS Apport bug report attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814238] Re: deja-dup saves passphrase in /tmp
** Changed in: deja-dup Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1814238 Title: deja-dup saves passphrase in /tmp Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Committed Bug description: I have unchecked the "save passphrase" option in deja-dup, but still I have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase in the clear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 10:59:06 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1814238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815056] Re: deja-dup is asking for the admin password
** Changed in: deja-dup Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1815056 Title: deja-dup is asking for the admin password Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Committed Bug description: This is on Ubuntu 18.04.1 LTS with deja-dup 37.1-2fakesync1ubuntu0.1. I'm using deja-dup for backup of my home directory. I don't have sudo permissions on the machine. I have only my home in backup and all files are owned by me. Still I always get this message: "Privileges are required to restore files to system locations". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 15:38:37 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1815056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885130] Re: Please add a way to show only open-source apps
Thank you for your bug report, ideally that would be sent upstream on https://gitlab.gnome.org/GNOME/gnome-software/-/issues ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps Status in gnome-software package in Ubuntu: New Bug description: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculater not open
you didn't get the ouput of the command requested in the previous comment -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculater not open Status in gnome-calculator package in Ubuntu: Incomplete Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885136] Re: Nautilus connection to SSH IPv6 address fails
Thank you for your bug report, could you report it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1885136 Title: Nautilus connection to SSH IPv6 address fails Status in nautilus package in Ubuntu: New Bug description: After reading answer https://answers.launchpad.net/ubuntu/+question/151402 I have tested that 1) on the command line """ sftp 'USER@[IPv6_ADDR%INTERFACE]' """ connects successfully , but 2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 'ssh' and 'sftp' result in "Connection failed" for the same form of address. Expectation was for this connection to succeed. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 16:52:53 2020 InstallationDate: Installed on 2018-01-10 (896 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885006] Re: Search Service broken on Ubuntu Nightly builds
** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- 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/1885006 Title: Search Service broken on Ubuntu Nightly builds Status in firefox package in Ubuntu: Fix Released Bug description: Search Service broken on Ubuntu Nightly builds.As reported in the Mozilla bug tracker, the search service has broken on the Ubuntu nightly builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1647576 It is broken due to this patch: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/view/head:/debian/patches /cleanup-old-distribution-search-engines.patch The code surrounding that has changed, however it should not be necessary now anyway, as we fixed the issues with distributions and built-in engines back in 76 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623597). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878921] Re: USB 3 NVMe SSD dongle doesn't flip
I don't recall seeing that error before. The 2 services I'm referring to are the systemd services: - usb_modeswitch@1-4.service - and usb_modeswitch@2-4.service I only realized that as I was trying to debug the error seen in the attached log.txt in my previous post -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1878921 Title: USB 3 NVMe SSD dongle doesn't flip Status in usb-modeswitch package in Ubuntu: In Progress Bug description: I have a AM8180 AMicro adapter. It is an adapter for an M.2 SSD NVMe disk to USB 3. It works fine on Windows, but on Ubuntu, when I plug it in, the drive shows for a second then disappears. If I try to do fdisk or gparted, it seems to lock something and I can't shutdown the laptop (it is stuck on the Disk Management Unmounting step. My info: 1) Release: Description: Ubuntu 20.04 LTS Release: 20.04 2) Package version: usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://th.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What I expect to happen: I expect the drive to stay mounted 4) What happened instead: The disk is mounted then immediately unmount. Before I create the partitions in Windows, nothing mounted but the disk briefly appeared in the Disk Manager. Attached is my (filtered) syslog when I plug to the USB-C (notice the message advising to tell the developers about the model. Maybe it's just vendor info missing). I have modified 2 flags in /etc/usb_modeswitch.conf: - DisableSwitching=0 changed to 1 - #SetStorageDelay=4 changed to un-commented then restarted. That didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1878921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs
this should be looked at by the Desktop Team. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860620 Title: ubuntu-desktop-minimal should not depend on mysql libs Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: After upgrading to 20.04 I decided to remove packages that I don't need or use. I was surprised to find that mysql client, server and common packages were installed, as I could not remember having installed mysql -- I don't use it or develop for it... When I removed them, ubuntu-desktop-minimal went along for the ride: c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common mysql-server-core-5.7 Reading package lists... Done Building dependency tree Reading state information... Done Package 'mysql-client-core-5.7' is not installed, so not removed Package 'mysql-server-core-5.7' is not installed, so not removed The following package was automatically installed and is no longer required: libgsound0 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* mysql-common* ubuntu-desktop-minimal* 0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded. After this operation, 28.4 MB disk space will be freed. (Reading database ... 381127 files and directories currently installed.) Removing ubuntu-desktop-minimal (1.443) ... Removing gnome-control-center (1:3.34.1-1ubuntu3) ... Removing colord (1.4.4-1ubuntu1) ... Removing libsane:amd64 (1.0.27-3.2ubuntu3) ... Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ... Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ... Removing mysql-common (5.8+1.0.5ubuntu2) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.32.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for man-db (2.9.0-2) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for udev (244-3ubuntu1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu1) ... (Reading database ... 380812 files and directories currently installed.) Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ... Purging configuration files for colord (1.4.4-1ubuntu1) ... And, reinstalling ubuntu-desktop-minimal wants to brings them back, even with recommends and suggests turned off: c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install- --no-install-recommends --no-install-suggests c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install-suggests Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common Suggested packages: colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip Recommended packages: gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker sane-utils firefox hplip The following NEW packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common ubuntu-desktop-minimal 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6,114 kB of archives. After this operation, 28.4 MB of additional disk space will be used. Do you want to continue? [Y/n] This seems really wrong... and looks like a transitive dependency, as I don't see it in apt-get showpkg ubuntu-desktop-minimal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop-minimal 1.443 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux ashmem_linux ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 19:26:53 2020 InstallationDate: Installed on 2018-08-26 (514 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I absolutly agree. This bug is a No-Go for the newest official long term support version. It should have priority high, and someone should be assigned to it! -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
@Tim Passingham: +1 Me too cannot understand that this annoying bug is classified as "Medium". It should be "High" because getting wrong data in LibreOffice Applications. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculater not open
Hello please resolve it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculater not open Status in gnome-calculator package in Ubuntu: Incomplete Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769116] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'
I have this on ubuntu 20.04, fresh install. Some further details here: https://askubuntu.com/questions/1252536/flickering-and-sudden- resolution-changes-on-20-04-and-old-radeon-hd-6570-card -- 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/1769116 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay' Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell[1938]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 4 12:52:16 2018 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818968] Re: can't select text from the start of a line on a terminator shell
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1818968 Title: can't select text from the start of a line on a terminator shell Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ever since yaru became the default theme, I'm not able to select text from the start of the line anymore, instead it'll try to resize the split terminator shell. To reproduce: - open terminator - split the window vertically - try to select text on the right side terminal - notice you can't select the first character, instead it will try to resize the split To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1818968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885136] Re: Nautilus connection to SSH IPv6 address fails
** Description changed: After reading answer https://answers.launchpad.net/ubuntu/+question/151402 I have tested that 1) on the command line """ - sftp USER@'[IPv6_ADDR%INTERFACE]' + sftp 'USER@[IPv6_ADDR%INTERFACE]' """ connects successfully , but 2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 'ssh' and 'sftp' result in "Connection failed" for the same form of address. Expectation was for this connection to succeed. - $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 16:52:53 2020 InstallationDate: Installed on 2018-01-10 (896 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago) usr_lib_nautilus: -- 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/1885136 Title: Nautilus connection to SSH IPv6 address fails Status in nautilus package in Ubuntu: New Bug description: After reading answer https://answers.launchpad.net/ubuntu/+question/151402 I have tested that 1) on the command line """ sftp 'USER@[IPv6_ADDR%INTERFACE]' """ connects successfully , but 2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 'ssh' and 'sftp' result in "Connection failed" for the same form of address. Expectation was for this connection to succeed. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 16:52:53 2020 InstallationDate: Installed on 2018-01-10 (896 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I am still really struggling to understand why this is not a major issue amongst ubuntu users. If I use the default interface I get driven crazy several times a day with mainly libreoffice various applications, copying and pasting and getting the wrong data. Can it be that there are either very few focal desktop users, or libreoffice users, or is it something else more specific to some systems?, or does no one ever copy and paste any more, or do people just not complain? It's so fundamental for me. I'm still torn between slow wayland and buggy gnome. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885136] [NEW] Nautilus connection to SSH IPv6 address fails
Public bug reported: After reading answer https://answers.launchpad.net/ubuntu/+question/151402 I have tested that 1) on the command line """ sftp USER@'[IPv6_ADDR%INTERFACE]' """ connects successfully , but 2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 'ssh' and 'sftp' result in "Connection failed" for the same form of address. Expectation was for this connection to succeed. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 16:52:53 2020 InstallationDate: Installed on 2018-01-10 (896 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1885136 Title: Nautilus connection to SSH IPv6 address fails Status in nautilus package in Ubuntu: New Bug description: After reading answer https://answers.launchpad.net/ubuntu/+question/151402 I have tested that 1) on the command line """ sftp USER@'[IPv6_ADDR%INTERFACE]' """ connects successfully , but 2) on the address field of nautilus 1:3.26.4-0~ubuntu18.04.5, both protocols 'ssh' and 'sftp' result in "Connection failed" for the same form of address. Expectation was for this connection to succeed. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 16:52:53 2020 InstallationDate: Installed on 2018-01-10 (896 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-02-12 (499 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880339] Re: package sgml-base 1.29.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sgml-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1880339 Title: package sgml-base 1.29.1 failed to install/upgrade: triggers looping, abandoned Status in sgml-base package in Ubuntu: Confirmed Bug description: During the upgrade from ubuntu 18.04 LTS to 20.04 the installation crashed because it could not install the package sgml-base. I rebooted the computer and got the bug I am reporting. I have attached the print of the error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sgml-base 1.29.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 23 17:29:08 2020 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2020-04-20 (32 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.29.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to focal on 2020-05-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1880339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885130] [NEW] Please add a way to show only open-source apps
Public bug reported: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps Status in gnome-software package in Ubuntu: New Bug description: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
Oups ``` Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium ``` when should it trigger snap installation ? -- 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/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Users trying to install chromium-browser with apt in a chroot will see the preinst script hang for 30min, and eventually fail. This use case is important as chroots are used by sysadmins to prepare installers. [Test Case] Create a focal chroot (for example using "pcreate -a amd64 -d focal focal-amd64"), enter the chroot and run "apt install chromium-browser". Expected outcome: the installation succeeds, even though the chromium snap is not being installed because snapd cannot run in the chroot. Incorrect (current) outcome: the installation hangs during 30 minutes while trying to contact the snap store, and eventually fails. [Regression Potential] As this change modifies the chromium-browser preinstallation script, it should be verified that installing the package on systems that are capable of running snapd (e.g. virtual machines or bare metal) still works as expected. [Original Description] Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
Just tried with -proposed repo, installation of chromium-browser package doesn't hang in a chroot anymore. After first reboot the package is installed in version: 83.0.4103.97-0ubuntu0.20.04.1 Please change tag from verification-needed-focal to verification-done- focal. -- 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/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Users trying to install chromium-browser with apt in a chroot will see the preinst script hang for 30min, and eventually fail. This use case is important as chroots are used by sysadmins to prepare installers. [Test Case] Create a focal chroot (for example using "pcreate -a amd64 -d focal focal-amd64"), enter the chroot and run "apt install chromium-browser". Expected outcome: the installation succeeds, even though the chromium snap is not being installed because snapd cannot run in the chroot. Incorrect (current) outcome: the installation hangs during 30 minutes while trying to contact the snap store, and eventually fails. [Regression Potential] As this change modifies the chromium-browser preinstallation script, it should be verified that installing the package on systems that are capable of running snapd (e.g. virtual machines or bare metal) still works as expected. [Original Description] Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852679] Re: CLI to copy to clipboard does not work
if I use screenshot 3.36.0 gui and click save to clipboard it works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1852679 Title: CLI to copy to clipboard does not work Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: I just upgraded today to 19.10. I have a keyboard shortcut setup to run gnome-screenshot --area -c to allow me to do quick screen grabs. I can confirm that if I use the screenshot dialog I can copy to the clipboard with that but using the CLI version of the same function does not work. It looks like it functions normal but when you go to paste the screenshot that you just took, nothing happens. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.33.90-1ubuntu1 Candidate: 3.33.90-1ubuntu1 Version table: *** 3.33.90-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852679] Re: CLI to copy to clipboard does not work
I can confirm this on 20.04 on my Tuxedo laptop. It seems that the clipboard is erasing the image. I used this feature a lot and now the only option is via the image on harddrive. Than open folder copy image and past that :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1852679 Title: CLI to copy to clipboard does not work Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: I just upgraded today to 19.10. I have a keyboard shortcut setup to run gnome-screenshot --area -c to allow me to do quick screen grabs. I can confirm that if I use the screenshot dialog I can copy to the clipboard with that but using the CLI version of the same function does not work. It looks like it functions normal but when you go to paste the screenshot that you just took, nothing happens. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.33.90-1ubuntu1 Candidate: 3.33.90-1ubuntu1 Version table: *** 3.33.90-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885127] [NEW] ethernet interfaces explicity excluded from management in globally-managed-devices.conf
Public bug reported: The file `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` included with this package (installed via apt in 19.10 environment) contains the line: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma ``` In my system (laptop with no native ethernet), this results in the inability to easily use USB/ethernet adapters. After manually modifying: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet ``` the USB/ethernet adapter is detected and configured automatically by NetworkManager ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1885127 Title: ethernet interfaces explicity excluded from management in globally- managed-devices.conf Status in network-manager package in Ubuntu: New Bug description: The file `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` included with this package (installed via apt in 19.10 environment) contains the line: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma ``` In my system (laptop with no native ethernet), this results in the inability to easily use USB/ethernet adapters. After manually modifying: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet ``` the USB/ethernet adapter is detected and configured automatically by NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-riscv - 5.4.0-27.31 --- linux-riscv (5.4.0-27.31) focal; urgency=medium * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798) * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667) - [config] riscv: disable am-1805 RTC driver * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() - mm: limit boost_watermark on small zones - ceph: demote quotarealm lookup warning to a debug message - staging: gasket: Check the return value of gasket_get_bar_index() - coredump: fix crash when umh is disabled - iocost: protect iocg->abs_vdebt with iocg->waitq.lock - batman-adv: fix batadv_nc_random_weight_tq - batman-adv: Fix refcnt leak in
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-kvm - 5.4.0-1015.15 --- linux-kvm (5.4.0-1015.15) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-kvm (5.4.0-1012.12) focal; urgency=medium * focal/linux-kvm: 5.4.0-1012.12 -proposed tracker (LP: #1878795) * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during
[Desktop-packages] [Bug 1884505] Re: Libreoffice crashes gnome session
the issue seems to be with the nvidia driver Äen 24 17:29:57 shadow /usr/lib/gdm3/gdm-x-session[2110]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to Äen 24 17:29:57 shadow /usr/lib/gdm3/gdm-x-session[2110]: (EE) NVIDIA(0): recover... Äen 24 17:29:57 shadow kernel: NVRM: GPU at PCI::02:00: GPU-6cd46921-f10b-b317-640a-62e0db607a2b ** Package changed: libreoffice (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Incomplete => New -- 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/1884505 Title: Libreoffice crashes gnome session Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: After while (1-5 min) using Libreoffice Cals/Writer the program crashes the running gnome session. And login screen pops up. After new login there are issues with audio playback so restart is required. I tested both libreoffice snap and dep packages. Problem occurs with both. My suspicion is that it is related to graphics card or driver. Notebook Dell 7559, GeForce 960M rev a2, driver 440.62, Ububtu 20.04 After each crash I found something like below in dmesg log: [14564.930179] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 [14564.930629] NVRM: Xid (PCI::02:00): 32, pid=30138, Channel ID 0018 intr 0004 full output in attachment. This bug is very annoying and makes the whole system useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:47:12 2020 InstallationDate: Installed on 2020-05-11 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice 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-440/+bug/1884505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885006] Re: Search Service broken on Ubuntu Nightly builds
This should be fixed with the 79.0~a1~hg20200625r537324 builds https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/revision/2342 ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/1885006 Title: Search Service broken on Ubuntu Nightly builds Status in firefox package in Ubuntu: Confirmed Bug description: Search Service broken on Ubuntu Nightly builds.As reported in the Mozilla bug tracker, the search service has broken on the Ubuntu nightly builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1647576 It is broken due to this patch: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.groovy/view/head:/debian/patches /cleanup-old-distribution-search-engines.patch The code surrounding that has changed, however it should not be necessary now anyway, as we fixed the issues with distributions and built-in engines back in 76 (https://bugzilla.mozilla.org/show_bug.cgi?id=1623597). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling not persisted in VMware Player
I think I just found out the real issue, and that information is not going to help you because it will contain seemingly random indicators depending on how I size my windows. VMware Player, like most virtualization software, runs windowed by default, and that window is dynamically resizeable. Now someone in all their wisdom at Ubuntu apparently decided that the available scaling options depend on the current resolution. So when I keep the settings screen open, and start resizing the window, thus dynamically resizing the "monitor", I can see the available scaling options change in real time. At 3840x2075 (that's 4k minus the VMware window borders) I see the 100/125/175/175/250 selector, at 3480x1859 I don't even get any fractional scaling options, at really low resolutions all scaling options disappear. When VMware Player boots, it snaps to the default 1024x768 size. So that's the monitor resolution when the desktop loads, it concludes scaling is not allowed at that level, and resets to 100%, no matter what it was before the reboot. The real issue appears to be: scaling settings should not be modified based on resolution during boot. -- 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/1884754 Title: Fractional scaling not persisted in VMware Player Status in mutter package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884823] Re: gnome-disks: missing "x" in windowbar to close gnome-disks
*** This bug is a duplicate of bug 1832606 *** https://bugs.launchpad.net/bugs/1832606 thanks, you have the buttons on the left which is already reported as bug #1832606 ** This bug has been marked a duplicate of bug 1832606 GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1884823 Title: gnome-disks: missing "x" in windowbar to close gnome-disks Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: There are only buttons to minimize or maximize the window of gnome- disks, but no button to close that window as usual. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 21:10:23 2020 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2020-05-23 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=de_DE.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1884823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885111] Re: 3 ports disabled
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1885111 Title: 3 ports disabled Status in cups package in Ubuntu: Incomplete Bug description: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCW1AGG dmi.product.version: C6031Z7V dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jan 3 08:58:12 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1885111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747034] Re: application startup blocks on plugin timeout
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1747034
Title:
application startup blocks on plugin timeout
Status in gnome-software package in Ubuntu:
Confirmed
Bug description:
On my test machine fwupd service timeouts (due to bug 1746485) This
causes gnome-software to wait until the timeout during startup and has
an impact of 20s on startup.
16:06:43:0338 Gs plugin no longer recently active: packagekit-history
16:07:03:0673 Gs not GsPlugin error from plugin fwupd g-io-error-quark:24:
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0673 Gs failed to call gs_plugin_refresh on fwupd: Error calling
StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0674 As run
0x55835f044d90~GsPlugin::packagekit-refresh(gs_plugin_refresh)
16:07:03:0683 Gs emitting global waiting
If the service is removed it starts faster bug then an error message
is displayed on the UI ('Something went wrong')
16:08:19:0509 As run 0x561b59f85590~GsPlugin::fwupd(gs_plugin_refresh)
16:08:19:0514 Gs not GsPlugin error from plugin fwupd FwupdError:10: The
name org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 Gs failed to call gs_plugin_refresh on fwupd: The name
org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 As run
0x561b59f85590~GsPlugin::packagekit-refresh(gs_plugin_refresh)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 2 17:09:38 2018
InstallationDate: Installed on 2013-09-03 (1612 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
InstalledPlugins:
gnome-software-plugin-flatpak 3.26.5-1ubuntu1
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.26.5-1ubuntu1
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to bionic on 2018-01-26 (7 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1747034/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium
I've just been reading through the code used to build the bin/fc-
cache-v6 and bin/fc-cache-v7 binaries in the core snap:
https://github.com/snapcore/fc-cache-static-builder
I think I understand what the problem is: while it is rebuilding copies
of xenial's and bionic's fontconfig tools that statically link to
libfontconfig, it's using the xenial version of libfreetype2 for both.
I suspect that this old freetype version does not understand all the
features of the font (e.g. the scalable colour emoji), so the generated
cache also misses them.
--
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/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
rendering issue in chromium
Status in chromium-browser package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
OK then. Just needs sanity checking. Which means I need to build a bionic machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
OK then. Just needs sanity checking. Which mean I need to build a bionic machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885111] [NEW] 3 ports disabled
Public bug reported: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCW1AGG dmi.product.version: C6031Z7V dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jan 3 08:58:12 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1885111 Title: 3 ports disabled Status in xorg package in Ubuntu: New Bug description: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias:
[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
the test got retried and is green now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
It would be good to find out how we get HiDPI displays to the testing team, because this should not have made it past test. -- 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 1747034] Re: application startup blocks on plugin timeout
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1747034
Title:
application startup blocks on plugin timeout
Status in gnome-software package in Ubuntu:
Confirmed
Bug description:
On my test machine fwupd service timeouts (due to bug 1746485) This
causes gnome-software to wait until the timeout during startup and has
an impact of 20s on startup.
16:06:43:0338 Gs plugin no longer recently active: packagekit-history
16:07:03:0673 Gs not GsPlugin error from plugin fwupd g-io-error-quark:24:
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0673 Gs failed to call gs_plugin_refresh on fwupd: Error calling
StartServiceByName for org.freedesktop.fwupd: Timeout was reached
16:07:03:0674 As run
0x55835f044d90~GsPlugin::packagekit-refresh(gs_plugin_refresh)
16:07:03:0683 Gs emitting global waiting
If the service is removed it starts faster bug then an error message
is displayed on the UI ('Something went wrong')
16:08:19:0509 As run 0x561b59f85590~GsPlugin::fwupd(gs_plugin_refresh)
16:08:19:0514 Gs not GsPlugin error from plugin fwupd FwupdError:10: The
name org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 Gs failed to call gs_plugin_refresh on fwupd: The name
org.freedesktop.fwupd was not provided by any .service files
16:08:19:0514 As run
0x561b59f85590~GsPlugin::packagekit-refresh(gs_plugin_refresh)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 2 17:09:38 2018
InstallationDate: Installed on 2013-09-03 (1612 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
InstalledPlugins:
gnome-software-plugin-flatpak 3.26.5-1ubuntu1
gnome-software-plugin-limba N/A
gnome-software-plugin-snap3.26.5-1ubuntu1
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to bionic on 2018-01-26 (7 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1747034/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Yea... I've turn it on and off using monitor switch button many times without luck... but in my case I had to PULL OUT THE POWER PLUG. I know how it sounds and how weird it is but just after that it was fixed and it didn't work before. I really don't know why, but it helped me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Hi, I tried power on and off the monitor multiple times, but nothing helped, still blank screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
