[Bug 1059263] Re: Cannot reboot or shutdown system
I have no idea if this is still an issue but this is a very old bug report. I use MATE and it works fine there. Assuming fixed. ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1059263 Title: Cannot reboot or shutdown system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1059263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767454]
*** Bug 398698 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
3.18.7 is way too old at this point. Please upgrade if you can. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793007] [NEW] gnome-disk-image-mounter creates loopback device but it is not mounted automatically
Public bug reported: First I thought nothing at all happened, but it turns out the loopback device is created, only this is not visible as Nautilus hides these by default. When I used nemo though or in Nautilus on 'other places' they are shown and are mounted if clicked on manually. syslog shows that udisksd reports the creation of the corresponding loop device. But this just happens silently and nothing is automounted. If the iso image is clicked again, it just creates anothe loopback device to the same image. It might also be a Nautilus problem I guess, depending on which part fails here. I also checked for existing issues here or in gnome-disks upstream, but couldn't find any so maybe it is something about the ubuntu package that could be improved? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 20:50:38 2018 ExecutablePath: /usr/bin/gnome-disk-image-mounter InstallationDate: Installed on 2014-07-29 (1510 days ago) InstallationMedia: It ProcEnviron: LANG=de_DE.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to bionic on 2018-09-07 (10 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1793007 Title: gnome-disk-image-mounter creates loopback device but it is not mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1793007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
1. $ sudo vim /etc/default/grub 2. removed "nomodeset" (leaving emptry string for GRUB_CMDLINE_LINUX 3. $ sudo update-grub 4. $ sudo update-initramfs -u 5. $ sudo vim /etc/gdm3/custom.conf 6. remove # in front of "#WaylandEnable=false", leaving "WaylandEnable=false" (under "[daemon]") 7. sudo reboot I made sure before as well I am using gdm3 login manager by `sudo dpkg- reconfigure gdm3` and selecting "gdm3". Unfortunately, this did not have the desired result. When the login screen pops up, the screen is frozen, and I can't login. Still the same as before. I also installed OpenSSH before to try and connect from another computer, to get some details during the freeze. However, when the computer is frozen and I try to connect to it through SSH, it takes a while and then it says: "ssh: connect to host peter-h67m-ud2h port 22: No route to host". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
Stephane, you should file a new bug using “ubuntu-bug /var/crash/_usr_bin_metacity.1000.crash” command (or whatever path to .crash file is), attaching the crash file to existing bug does not help. Also, we do not always have resources for supporting old Ubuntu versions. Please upgrade to 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on 16.04. Here is the crash dump. ** Attachment added: "_usr_bin_metacity.1000.crash" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791454] Re: system-monitor produces many apparmor permission denied warnings
If this bug is about a snap package you should probably open a report with the snap author. Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1791454 Title: system-monitor produces many apparmor permission denied warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762561] Re: No message about plugging in laptop needed for updating firmware in Ubuntu software center
*** This bug is a duplicate of bug 1694076 *** https://bugs.launchpad.net/bugs/1694076 ** This bug has been marked a duplicate of bug 1694076 No error message on firmware update fail -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1762561 Title: No message about plugging in laptop needed for updating firmware in Ubuntu software center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1694076] Re: No error message on firmware update fail
Since this was in 3-26 and now at 3-28 in bionic, closing this issue. ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1694076 Title: No error message on firmware update fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1694076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
** Tags added: nvidia ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1792843/+attachment/5189875/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
Note: for now I have worked around this by preventing my console from being locked when the display sleep kicks in. Not ideal but at least I don't have to reboot after every sleep. Also, probably not relevant, but this was happening before I switched to bionic app sources (which I needed for some php apps). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: So yesterday I got the prompt to upgrade my 16LTS system to 18. This caused a number of issues, but the most frustrating issue out of many has to be this one. After a period of inactivity, the lock screen kicks in. When I then try to log in, using the correct password, I get a spinner for about 10 seconds, the "Authentication error". After a couple of seconds "Authentication error" goes away but now it seems no keys are registering at all in the password field. I say "it seems" because I see no "*"s as I type, but I do see occasional prompts of "Authentication error" coming back, but I haven't pinpointed the circumstances - certainly not triggered by hitting ENTER, sometimes backspace? Not sure if it has anything to do with the keys. After this all I can do is log in over ssh and reboot; I'm basically locked out on the console. If I wait a while the keyboard does seem to come back but the problem is still there - my password is not accepted and then the keyboard again seems to do nothing for a while. This happens whether I have a USB keyboard connected or whether I am running Synergy and using a virtual keyboard. Mouse continues to work fine. - Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic - x86_64) + Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic x86_64) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + GsettingsChanges: + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 + Tags: third-party-packages bionic + Uname: Linux 4.15.0-34-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1792843/+attachment/5189874/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1792843/+attachment/5189876/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791433] Re: Path traversal vulnerability
https://bugs.launchpad.net/ubuntu/+source/file-roller/3.30.0-1 ** Changed in: file-roller (Ubuntu) Importance: Undecided => Low ** Changed in: file-roller (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1791433 Title: Path traversal vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1791433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
did anyone try to test mutter 3.30 to see if the issue is fixed or not I don't want to be shocked that the issue isn't fixed when 18.10 is released then I'll have to wait for another 6 months for the fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791433] Re: Path traversal vulnerability
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1791433 Title: Path traversal vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1791433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
Tested this on my system and this has solved the issue for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Same issue here. Filled up hard drive pretty quickly and I have a 512GB SSD Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #0 0x7ffe78ba8ab0 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f49884c7780 @ 273) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #1 0x7ffe78ba8b20 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f49885b5de0 @ 71) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #2 0x7ffe78ba8b20 I self-hosted:916 (0x7f49885f12b8 @ 367) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #3 0x7ffe78ba8bc0 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f49885d2230 @ 386) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #4 0x555d11c8f210 i resource:///org/gnome/shell/ui/layout.js:531 (0x7f49884042b8 @ 127) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #5 0x7ffe78ba97b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f49885b5de0 @ 71) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #6 0x7ffe78ba97b0 I self-hosted:916 (0x7f49885f12b8 @ 367) Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: == Stack trace for context 0x555d118ea330 == -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
** Changed in: zsh (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
** Changed in: wget (Ubuntu) Status: New => Triaged ** Changed in: wget (Ubuntu) Assignee: Noël Köthe (noel) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792924] Re: Passwords entered in GDM can be displayed when switching TTYs
*** This bug is a duplicate of bug 1767918 *** https://bugs.launchpad.net/bugs/1767918 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1767918, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1767918 Login password from GDM is shown in plain text on the VT1 console -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1792924 Title: Passwords entered in GDM can be displayed when switching TTYs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
This issue has been fixed upstream. It requires fixes in both gnome- software and fwupd. gnome-software fix (on the Gnome Software 3-28 branch): https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e fwupd fix (on the 1_0_X branch): https://github.com/hughsie/fwupd/commit/80f6e995f68ad7559c4a386a58e9ee43750bf6aa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792924] [NEW] Passwords entered in GDM can be displayed when switching TTYs
Public bug reported: Ubuntu 18.04.1 LTS gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 Version table: *** 3.28.2-0ubuntu1.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages When switching between TTYs or sessions via the Alt+Function keybindings, you can briefly display all entered passwords from the GDM password box. When I was switching from a TTY to my active GNOME Shell session, I accidentally pressed `Alt`+`F1`+`F2` at the same time instead of just `Alt`+`F2`, and when I did this, a black screen with text appeared for a second or so that displayed everything that had been entered into the GDM password box, regardless of which user it was. I believe this may be problematic on multi-user systems. I tried to take a picture but the quality is subpar as I had to handle the camera and press the keys at the same time to capture ( https://photos.app.goo.gl/8k5voYWcvK424xp59 ) The intentionally blurred area is where the passwords/entered text was shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.4 Uname: Linux 4.18.7-041807-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 05:12:33 2018 InstallationDate: Installed on 2018-09-15 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1792924 Title: Passwords entered in GDM can be displayed when switching TTYs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792900] Re: help
** Package changed: xorg (Ubuntu) => gstreamer0.10 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1792900 Title: help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1792900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792910] Re: Firefox doesn't use the session's theme
** Package changed: gnome-session (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1792910 Title: Firefox doesn't use the session's theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792900] [NEW] help
You have been subscribed to a public bug: root@chika:~# gst-launch-0.10 tcpclientsrc host=10.0.0.240 port=5000 ! multipartdemux ! jpegdec ! v4l2sink device=/dev/video0 Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... root@chika:~# ls -l /dev/video* ls: cannot access /dev/video*: No such file or directory root@chika:~# gnome-control-center *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): screen-cc-panel-WARNING **: Error getting brightness: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (gnome-language-selector:6364): Gtk-DEBUG: Connecting to session manager (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called expand (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called fill (gnome-control-center.real:6331): Gtk-WARNING **: GtkTable does not have a property called position (gnome-control-center.real:6331): GLib-GIO-CRITICAL **: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_get_int32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed (gnome-control-center.real:6331): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (gnome-control-center.real:6331): GLib-CRITICAL **: Source ID 8200 was not found when attempting to remove it Error getting devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Power was not provided by any .service files *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:197: Running the following duplicity (6813) command: duplicity 'collection-status' '-- gio' 'file:///root/deja-dup' '--no-encryption' '--verbosity=9' '--gpg- options=--no-use-agent' '--archive-dir=/root/.cache/deja-dup' '-- tempdir=/tmp' '--log-fd=16' ** (deja-dup:6798): DEBUG: DuplicityInstance.vala:570: duplicity (6813) exited with value 0 (gnome-control-center.real:6331): info-cc-panel-WARNING **: Failed to get fallback mode: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files root@chika:~# gstreamer-properties (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog .has-separator (gstreamer-properties:6857): Gtk-WARNING **: Unknown property: GtkDialog.has-separator gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'v4lsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosrc' gstreamer-properties-Message: Error running pipeline 'Video for Linux 2 (v4l2)': Cannot identify device '/dev/video0'. [v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src1: system error: No such file or directory] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140 Uname: Linux 4.4.0-135-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 17 11:36:31 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
[Bug 1792365] Re: On-screen keyboard doesn't work for GEdit
Could you please tell me how to change the setting you mentioned earlier? Thanks. I should have said this earlier, but this bug is pretty much the same as this bug (https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1589240). I read a comment that said a new bug should be filed, so I filed one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1792365 Title: On-screen keyboard doesn't work for GEdit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1792365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
wget builds and works with pcre2 in Debian (uploaded). I cannot change the Status to Triaged. Maybe somebody with higher privileges can change the wget status of this bug to Triaged. thx. ** Changed in: wget (Ubuntu) Assignee: (unassigned) => Noël Köthe (noel) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792910] Re: Firefox doesn't use the session's theme
** Attachment added: "Screenshot from 2018-09-17 11-24-08.png" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1792910/+attachment/5189794/+files/Screenshot%20from%202018-09-17%2011-24-08.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1792910 Title: Firefox doesn't use the session's theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1792910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792910] [NEW] Firefox doesn't use the session's theme
Public bug reported: Firefox doesn't use Adwaita's theme for it. See the screenshot. I don't use vanilla GNOME on other distributions so I'm not entirely sure what the correct behaviour is but pretty sure Firefox is not supposed to be using the Yaru(?) theme? I have the communitheme snap (0.1 (1171)) installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 17 11:17:45 2018 InstallationDate: Installed on 2017-08-03 (409 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-22 (148 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1792910 Title: Firefox doesn't use the session's theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1792910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792798] Re: gdm3 will start in a new tty after suspend
screenshot of how it looks like right after powering it on from suspend/sleep mode. (tty2) ** Attachment added: "screenshot of how it looks like right after powering it on from suspend/sleep mode. (tty2)" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792798/+attachment/5189770/+files/41779791_2162365020704740_6495823733788246016_n.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1792798 Title: gdm3 will start in a new tty after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792798/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
I'll try this first thing I get home! Can I run the "sudo update-initramfs" during nomodeset? Or should I remove "nomodeset" first and start in recovery mode? Since otherwise, I am not able to get a command line. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
Please try: 1. Remove "nomodeset" from your kernel command line and `sudo update- initramfs`; then 2. Edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false 3. Reboot Can you log in now? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792437] Re: totem video play back laggy when opened through GUI, running it from terminal is OK
well when I execute this command a window pops up saying information is being collected that may help developers to fix this problem! Then it shows a summary and request my permission to send the collected data which I press send... The first time I executed the command, it asked for permission to connect with my launchpad account which I granted. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1792437 Title: totem video play back laggy when opened through GUI, running it from terminal is OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1792437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792437] Re: totem video play back laggy when opened through GUI, running it from terminal is OK
well when execute this commands a windows pops up saying information is being collected that may help developers to fix this problem! Then it shows a summary and request my permission to send the collected data which I press send... The first time I executed the command, it asked for permission to connect with my launchpad account which I granted. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1792437 Title: totem video play back laggy when opened through GUI, running it from terminal is OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1792437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
** Description changed: Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is frozen. I tried both gdm3 and lightdm login managers, with either I don't get into the system. I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD Graphics 2000. I have an external 24" ASUS display connected with VGA (tried HDMI as well but same problem). + UPDATE: I now use "nomodeset" since that is the only way to get into the + system. However, graphics are low and there's only 1 screen resolution + available (1280x1024) which does not suit my screen at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 18:16:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-15 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/12/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H67M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1809141934.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780623] Re: Cannot Open a new Gnome Calculator Window
Still can reproduce this problem with 18.04.1. ** Changed in: gnome-calculator (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1780623 Title: Cannot Open a new Gnome Calculator Window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1780623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789962] Re: gnome-shell segfaults in Wayland when display is turned off while Kodi running
Thanks. Our next option is to try attaching a few more .crash files to this bug. Maybe one or two will be more human-readable. So I will make this bug private from now on so you can do that with some security... ** Information type changed from Public to Private ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789962 Title: gnome-shell segfaults in Wayland when display is turned off while Kodi running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1792822] Re: dual monitor not working in 18.04(.1)
Hi Daniel, I tried with uncommenting WaylandEnabled=false earlier. Then the login screen remains totally Black on both monitors. Had to restore by disabling gdm and using lightdm again. I'm happy to try other suggestions! Kind regards, Floris Op ma 17 sep. 2018 09:55 schreef Daniel van Vugt < daniel.van.v...@canonical.com>: > It sounds like this problem may be limited to Wayland sessions (which > includes the login screen). Please try this workaround next time you > install 18.04: > > Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: > #WaylandEnable=false > > Then reboot. > > ** Tags added: multi-monit radeon > > ** Tags removed: multi-monit > ** Tags added: multi-monitor > > ** Summary changed: > > - dual monitor not working in 18.04(.1) > + Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1792822 > > Title: > Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system > > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1). > This renders 18.04 useless. Till this is solved will have to stick > with 16.04. i.e. this is a pretty critical bug! > > > After a fresh install from DVD first got a freeze on login screen (live > CD will run ubuntu though!). This could be solved by switching to lightdm > display manager. (Boo! for GDM that cannot even show a login screen without > freezing the system) > > But one issue remains: the dual monitor setup will not work in 18.04. > > I can see the mouse move to the second monitor. I can drag windows > there (and lose sight of them). I can see the mouse cursor change to > click a link. But otherwise there is a completely black screen, or > dots / colored fields, but nothing even resembling a program. > > MB: Gigabyte GA-A75M-UD2H > Monitor that works fine: ASUS on Radeon HD 6550D > monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on > the gigabyte motherboard) > > Note: dual monitor setup did not work with other upgrades after 16.04. I > hoped this would be solved with the next LTS update. Not so, to great > disappointment! > Ubuntu really fails if with new major updates it makes systems fall > down. This kind of thing should work FLAWLESS out of the box! How would > anyone move to Ubuntu when this kind of thing does not work? Windows is a > drama, but at least it has the mere basics working! > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3.1 > ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 > Uname: Linux 4.4.0-135-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Sun Sep 16 23:09:31 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: >virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed >virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed >virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] > [1002:9640] (prog-if 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] > [1458:d000] >Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] > [1002:9440] (prog-if 00 [VGA controller]) > Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD > 4870] [174b:0851] > InstallationDate: Installed on 2016-10-02 (714 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H > ProcEnviron: >LANGUAGE=nl_NL >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=nl_NL.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic > root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/17/2011 > dmi.bios.vendor: Award Software International, Inc. > dmi.bios.version: F6c > dmi.board.name: GA-A75M-UD2H > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.modalias: >
[Bug 1792365] Re: On-screen keyboard doesn't work for GEdit
OK, let's use bug 1697641 for Chromium. This bug is about GEdit only now. ** Summary changed: - On-screen keyboard doesn't work outside of Ubuntu's text fields + On-screen keyboard doesn't work for GEdit ** No longer affects: chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1792365 Title: On-screen keyboard doesn't work for GEdit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1792365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792437] Re: totem video play back laggy when opened through GUI, running it from terminal is OK
That command did not seem to work. It should have added some attachments to this bug. Please try again: apport-collect 1792437 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1792437 Title: totem video play back laggy when opened through GUI, running it from terminal is OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1792437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792702] Re: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it.
Can you please run this command on the machine to send us more information? apport-collect 1792702 ** Summary changed: - gnome-shell filling /var/log/syslog + gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it. + gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792702 Title: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792878] [NEW] gvfs lockup due to max number of connections
Public bug reported: Currently, the default value of max-conns-per-host libsoup property is used, which causes dav backend lockups if two files are opened. see: https://gitlab.gnome.org/GNOME/gvfs/commit/7b991137b8a820f018ddaa970d54f91d1f411a0f I've managed to fix the problem by changig the code of Version 1.36 (current ubuntu version) an compile it. As long as the version of gvfs is not updated to a version with fixing the problem, the patch described in the link above should be backported into version 1.36. quit urgent for us 'cause our system is heavely dependend on webdav Thanks Ueli ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 17 10:02:36 2018 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792878 Title: gvfs lockup due to max number of connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792878/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792365] Re: On-screen keyboard doesn't work outside of Ubuntu's text fields
Chromium is a special case, you'll have to force-enable accessibility to get the OSK to show up. See https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697641/comments/7. For other applications (including gedit and libreoffice), the OSK should show up if you enable the OSK in the accessibility settings. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1792365 Title: On-screen keyboard doesn't work outside of Ubuntu's text fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
** Bug watch removed: Debian Bug tracker #908769 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908769 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792798] Re: gdm3 will start in a new tty after suspend
** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1792798 Title: gdm3 will start in a new tty after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1792798/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
** Summary changed: - Xorg freeze + Login screen freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782681] Re: Upgrade to 3.26.4 and SRU it
Verification done as package is installable from proposed. No further tests are needed here. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1782681 Title: Upgrade to 3.26.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792798] [NEW] gdm3 will start in a new tty after suspend
You have been subscribed to a public bug: I'm not sure if there is any related info in log files because there is no actual crash or error messages. Im using Ubuntu 18.04 and Gnome3 on Xorg. Also, I have a NVidia GT520M with nvidia-390 driver installed through ubuntu-drivers utility. Cant confirm that is a graphics driver issue because I installed it on a fresh Ubuntu. Description === Whenever I suspend my laptop (e.g. close lid) and then turn it on, a new session will be opened in tty2 causing two graphical sessions being executed at the same time (?) Workaround === I found a workaround that simply requires to Log Out from the 2nd session (tty2) and pressing Ctrl+Alt+F1 to go back to the original Xorg session. After that the Login screen will appear. The background image will get pixelized and very distorted when the 2nd Xorg session is loaded. Will try to add a screenshot as attachment. Also, this bug could lead to "bypass" the login menu. I was able to change session without being asked for user password: one is stuck at the login screen and the other is logged in already. Not sure if it is a security issue because it would require a successful authentication beforehand. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-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.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 16 14:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-08-19 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. K53SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=d07ee961-7df7-4a6a-9fc9-10d6724a7e9b ro quiet splash intel_pstate=enable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SJ.315 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SJ.315:bd09/26/2011:svnASUSTeKComputerInc.:pnK53SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK53SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.family: K dmi.product.name: K53SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- gdm3 will start in a new tty after suspend https://bugs.launchpad.net/bugs/1792798 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] [NEW] Login screen freeze
You have been subscribed to a public bug: Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is frozen. I tried both gdm3 and lightdm login managers, with either I don't get into the system. I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD Graphics 2000. I have an external 24" ASUS display connected with VGA (tried HDMI as well but same problem). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 18:16:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-15 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/12/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H67M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0+git1809141934.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- Login screen freeze https://bugs.launchpad.net/bugs/1792807 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
BTW - I'm running Kubuntu, and doing the upgrade with kubuntu-devel- release-upgrade works just fine without needing to update appstream to 0.12.2 first. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792822] Re: dual monitor not working in 18.04(.1)
It sounds like this problem may be limited to Wayland sessions (which includes the login screen). Please try this workaround next time you install 18.04: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false Then reboot. ** Tags added: multi-monit radeon ** Tags removed: multi-monit ** Tags added: multi-monitor ** Summary changed: - dual monitor not working in 18.04(.1) + Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792822 Title: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792857] Re: Mouse pointer is the wrong size after resuming from suspend
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792857 Title: Mouse pointer is the wrong size after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1792843 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792822] [NEW] Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system
You have been subscribed to a public bug: Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1). This renders 18.04 useless. Till this is solved will have to stick with 16.04. i.e. this is a pretty critical bug! After a fresh install from DVD first got a freeze on login screen (live CD will run ubuntu though!). This could be solved by switching to lightdm display manager. (Boo! for GDM that cannot even show a login screen without freezing the system) But one issue remains: the dual monitor setup will not work in 18.04. I can see the mouse move to the second monitor. I can drag windows there (and lose sight of them). I can see the mouse cursor change to click a link. But otherwise there is a completely black screen, or dots / colored fields, but nothing even resembling a program. MB: Gigabyte GA-A75M-UD2H Monitor that works fine: ASUS on Radeon HD 6550D monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the gigabyte motherboard) Note: dual monitor setup did not work with other upgrades after 16.04. I hoped this would be solved with the next LTS update. Not so, to great disappointment! Ubuntu really fails if with new major updates it makes systems fall down. This kind of thing should work FLAWLESS out of the box! How would anyone move to Ubuntu when this kind of thing does not work? Windows is a drama, but at least it has the mere basics working! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 16 23:09:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] [1002:9640] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] [174b:0851] InstallationDate: Installed on 2016-10-02 (714 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6c dmi.board.name: GA-A75M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 16 19:34:47 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 multi-monitor radeon ubuntu xenial -- Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system https://bugs.launchpad.net/bugs/1792822 You received this bug notification because you are a member of Ubuntu Desktop Bugs,
[Bug 1792857] [NEW] Mouse pointer is the wrong size after resuming from suspend
You have been subscribed to a public bug: After resuming from suspend, but mouse pointer is the wrong size when located in some parts of the screen. Specifically, when mousing over the left or top bars of the UI (not the desktop or any running programs), the pointer is too large. A workaround is to open display settings, pick any other resolution, click apply, then click revert. When the original resolution is restored, the pointer size returns to normal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 20:46:42 2018 DistUpgraded: 2018-05-28 17:09:21,096 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: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2016-04-27 (872 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20BSCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-29 (111 days ago) dmi.bios.date: 08/13/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET32W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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: Mon May 28 16:18:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1049 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Mouse pointer is the wrong size after resuming from suspend https://bugs.launchpad.net/bugs/1792857 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792365] Re: On-screen keyboard doesn't work outside of Ubuntu's text fields
** Changed in: gedit (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1792365 Title: On-screen keyboard doesn't work outside of Ubuntu's text fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Have the same issue upgrading from bionic to cosmic. Updating appstream to the version from cosmic workedaround the problem. Please backport fix to bionic so that other people will be able to upgrade using the Ubuntu normal upgrade process. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
