[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
If you can still ssh in while the screen is frozen then please do so and run: dmesg > frozendmesg.txt and send us the file 'frozendmesg.txt' ** Summary changed: - Screen frozen after switch to other tty and do login & logout + [nvidia] Screen frozen after switch to other tty and do login & logout ** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia ** Tags added: bionic cosmic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Status: New => Incomplete -- 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/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821262] Re: gnome-shell crashes when closing evolution
Firstly, please try uninstalling your extensions to see if that makes the problem go away: b'org.gnome.shell' b'enabled-extensions' b"['audio-input- switcher@anduchs', 'audio-output-switcher@anduchs', 'caffe...@patapon.info', 'native-window-placement@gnome-shell- extensions.gcampax.github.com', 'audio-selec...@bjarosze.gmail.com', 'audio-switcher@AndresCidoncha', 'output-audio-devices@muflone']" Secondly... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/1821262 Title: gnome-shell crashes when closing evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] Re: Desktop freezes refuses input
If you have added any gnome-shell extensions, please try uninstalling them, reboot and see if the problem goes away. -- 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/1821160 Title: Desktop freezes refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] Re: Desktop freezes refuses input
> Mouse only moves. Does not click on any open app window, left or top panels, > any area on desktop. In short does not click anywhere. If everything including the panels doesn't respond to clicking, but the cursor moves, then that means the gnome-shell process has frozen but Xorg is still working (Xorg moves the cursor). -- 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/1821160 Title: Desktop freezes refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items (if extensions are installed that add menu buttons)
** Tags added: fixed-upstream -- 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/1820775 Title: gnome-shell's user menu/item is not aligned like other menu items (if extensions are installed that add menu buttons) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
Yes, sorry it is easy to break your package configuration :( Maybe some safer instructions would be something like (not tested): 1. Software & Updates > Developer Options > Pre-released updates = ON 2. sudo apt update 3. sudo apt install gnome-shell 4. Software & Updates > Developer Options > Pre-released updates = OFF -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821264] [NEW] gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults
Public bug reported: installing Dell Oem. Running update/upgrade sudo -s sudo apt-get update && sudo apt-get upgrade -y Then running gnome-software results in the GUI loading but after 10 seconds it crashes and you see a segfault. I tried information in +Bug/1798236 but U16 does not have a later version of gnome-software. I also saw a bug similar that mentioned we need packagekit 1.12 but U16 doesn't bundle that only U19 does. I tried download a package for testing purposes but it does not resolve the issue. I saw another case within our Dell database that suggests appstream might cause the crash so I removed appstream and did and update/upgrade again. It stopped the crash initially but not on reboot. I also added the gnome3 repository in hopes I could get the updates that way and that did not help either. It is unclear what is needed to resolve this issue. Please let me know what logs you need me to provide to look into this further. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 21 19:11:27 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-rebase-20170712-0 InstallationDate: Installed on 2019-03-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170712-02:34 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1821264 Title: gnome-software from xps 13 9365 with Dell-oem running Ubuntu 16.04 segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1821264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821262] [NEW] gnome-shell crashes when closing evolution
Public bug reported: Had this happen a few times now, where closing the main evolution window results in a gnome-shell crash: Mar 21 16:55:18 taplop gnome-shell[2552]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 221715 error_code 3 request_code 18 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Mar 21 16:55:18 taplop kernel: traps: gnome-shell[2552] trap int3 ip:7fde271ce955 sp:7ffcbe8660a0 error:0 in libglib-2.0.so.0.6000.0[7fde27195000+8] Mar 21 16:55:18 taplop update-notifier[4833]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop seahorse[3088]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop evolution-alarm[2863]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gnome-calendar[3082]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gsd-wacom[2744]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gnome-session[2524]: gnome-session-binary[2524]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Mar 21 16:55:18 taplop gnome-session-binary[2524]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Mar 21 16:55:18 taplop org.gnome.Shell.desktop[2552]: (EE) failed to read Wayland events: Broken pipe Mar 21 16:55:18 taplop polkitd(authority=local)[1283]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.266, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF- Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.Wacom.desktop[20239]: Unable to init server: Could not connect: Connection refused Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.Wacom.desktop[20239]: Cannot open display: Mar 21 16:55:18 taplop gnome-session-binary[2524]: Unrecoverable failure in required component org.gnome.Shell.desktop Mar 21 16:55:18 taplop gnome-session[2524]: gnome-session-binary[2524]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Mar 21 16:55:18 taplop gnome-session-binary[2524]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Mar 21 16:55:18 taplop pulseaudio[2648]: ICE default IO error handler doing an exit(), pid = 2648, errno = 11 Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.MediaKeys.desktop[2734]: xcb_connection_has_error() returned true Mar 21 16:55:18 taplop kernel: rfkill: input handler enabled Mar 21 16:55:18 taplop gsd-clipboard[2742]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-power[2723]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop keepass.desktop[2848]: cli: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-color[2750]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-keyboard[2721]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop at-spi-bus-launcher[2596]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Mar 21 16:55:18 taplop at-spi-bus-launcher[2596]: after 76743 requests (76743 known processed) with 0 events remaining. Mar 21 16:55:18 taplop gsd-xsettings[2754]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-media-keys[2734]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop bluetoothd[1541]: Endpoint unregistered: sender=:1.420 path=/MediaEndpoint/A2DPSource Mar 21 16:55:18 taplop bluetoothd[1541]: Endpoint unregistered: sender=:1.420 path=/MediaEndpoint/A2DPSink Mar 21 16:55:18 taplop gdm-password][2472]: pam_unix(gdm-password:session): session closed for user jbarnett Mar 21 16:55:18 taplop systemd[2491]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Mar 21 16:55:18 taplop systemd[2491]: pulseaudio.service: Failed with result 'exit-code'. Mar 21 16:55:18 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Mar 21 16:55:18 taplop kernel: [drm] UVD
[Bug 1794283] Re: nautilus throws error during copying file
This is output when I was mounting samba resources and trying to copy a file: trash: Added new job source 0x5649ab5f8090 (GVfsBackendTrash) trash: Queued new job 0x5649ab5f9020 (GVfsJobMount) trash: send_reply(0x5649ab5f9020), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:CreateFileMonitor (pid=6115) trash: Queued new job 0x5649ab5f9380 (GVfsJobCreateMonitor) trash: send_reply(0x5649ab5f9380), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:CreateFileMonitor (pid=6115) trash: Queued new job 0x5649ab5f9380 (GVfsJobCreateMonitor) trash: send_reply(0x5649ab5f9380), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4370 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4370), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4410 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4410), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4550 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4550), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e45f0 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e45f0), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4550 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4550), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4370 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4370), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e42d0 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e42d0), failed=0 () trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=6115) trash: Queued new job 0x5649ab5e4230 (GVfsJobQueryInfo) trash: send_reply(0x5649ab5e4230), failed=0 () -- 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/1794283 Title: nautilus throws error during copying file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794283/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1020373] Re: Brightness control not working on Ubuntu 12.04(mac)
I am using Ubuntu 18.04 and this problem has still not been fixed nor has anybody looked at it, I would like it fixed because I don't want to go back to Mac OS X, but I might have to because this is just ridiculously bright... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1020373 Title: Brightness control not working on Ubuntu 12.04(mac) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1020373/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I installed the fix on Bionic by enabling proposed updates in settings and running Software Updater then. Everything looks fine and the problem is solved. But before when I tried to install via terminal gnome-shell/bionic- proposed and gnome-shell-common/bionic-proposed, it broke Gnome. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821014] Re: budgie-wm crashes sometimes
Sorry - cannot reproduce this - but you are right this is somewhere in clutter/mutter . Can you tell me a bit more about your setup. Is this a virtual machine - if so what virtualisation solution are you using - how have you configured your VM. Is this a real machine - if so, what graphics card and graphics driver are you using - nvidia? have you got animations switched on/off in budgie-desktop-settings (it should be off). Can you reproduce this if you boot into a live session of 19.04 Ubuntu Budgie (download the latest daily image)? -- 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/1821014 Title: budgie-wm crashes sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1821014/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821194] [NEW] Screen frozen after switch to other tty and do login & logout
Public bug reported: To simplify reproduce steps, one only has to: 1. install (tested so far) Ubuntu Bionic 2. switch to other tty by pressing Ctrl+Alt+Fn 3. login and logout Then it should try to switch back to GDM (no matter you have logged in GUI or not), triggers vt-switch bug and lock up. Some more findings: 1. So far we know all other newer Ubuntu versions are immune, e.g. Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5). 2. login _and_ logout from another virtual console is required. Switching between text console and GUI back and forth before logging out doesn't trigger this bug. So this might(?) also involves systemd-logind as well; 3. while gdm locked up, kernel and the rest of the system are actually still alive. Networking is still available, and even the input devices are still functioning well. Only gdm fails to grab the device inputs. 4. when gdm locks up due to either resume from suspend or vt-switch, restart gdm (from remote ssh) will bring the system back. ### Disco | |4.15|4.18|4.19|5.0 |---||||--- |nouveau| | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410|Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 240-6ubuntu1 * gdm3: * 3.31.4+git20190225-1ubuntu1 Hardware * 201811-26623 Summary: in Ubuntu Disco, nouveau driver is immune from this issue in all kernel versions tested. In contrary, nVIDIA driver fails every case. ### Cosmic | |4.15|4.18|4.19|5.0 |-||||--- |nouveau | | | | |nvidia-390 bionic|Affected|Affected|Affected|Affected |nvidia-390 cosmic|Affected|Affected|Affected|Affected |nvidia-410 |Affected|Affected|Affected|Affected Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * 5.0.0-7-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 239-7ubuntu10 * gdm3: * 3.30.1-1ubuntu5 Hardware * 201811-26623 Summary: in Ubuntu Cosmic, same with Disco. # Bionic | |4.15|4.18 |4.19 |-||| |nouveau|Affected[1]| |Affected[1] |hwe xorg|Affected[1]| |Affected[1] |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1] |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1] |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1] |nvidia-410 |Affected[2]|Affected[1]|Affected[3] [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm (but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a remote shell. ## Packages: * kernel: * 4.15.0-46-generic * 4.18.0-16-generic * 4.19.0-13-generic * nvidia-driver: * 390.116-0ubuntu0.18.04.1 * 390.116-0ubuntu0.18.10.1 * 410.104-0ubuntu1 * systemd: * 237-3ubuntu10.12 * gdm3: * 3.28.3-0ubuntu18.04.3 ## Hardware * 201811-26623 Summary: only 4.18 kernel with nouveau driver is immune from this issue, which follows some changes in user land should be necessary to stabilize all the (nouveau) cases. But even with that, from previous results of Cosmic/Disco, there should still some works to be done in the nvidia driver. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1821194 Title: Screen frozen after switch to other tty and do login & logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items (if extensions are installed that add menu buttons)
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1820775 Title: gnome-shell's user menu/item is not aligned like other menu items (if extensions are installed that add menu buttons) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]
** Changed in: gst-plugins-good Status: Unknown => New -- 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/1820883 Title: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"] To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/1820883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Kernel 4.15.0-47 which includes the fix is in proposed pocket. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] Re: Desktop freezes refuses input
I see some notes on bluetooth in the logs. I fully disabled the bluetooth deamon at the moment. I do not use bluetooth on this machine. Will see if it makes any difference. -- 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/1821160 Title: Desktop freezes refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] Re: Desktop freezes refuses input
Mouse only moves. Does not click on any open app window, left or top panels, any area on desktop. In short does not click anywhere. -- 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/1821160 Title: Desktop freezes refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
In which bionic kernel is the fix for this present? Did the kernel portion go out already? Timing-wise it seems like that's the case, since there's a new kernel cycle starting right now. Can someone confirm that and switch the linux task to Fix Released if that's the case? I'll release all of those then. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821014] Re: budgie-wm crashes sometimes
It crashed again, attaching a newer backtrace (this time an all thread one). ** Attachment added: "backtrace_20190321.txt" https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1821014/+attachment/5248200/+files/backtrace_20190321.txt -- 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/1821014 Title: budgie-wm crashes sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1821014/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Forgot to add: Ubuntu 18.04.2 -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
I confirm the bug exists and workarounds work, both with lightdm and ExecStartPre line. Also, adding xinit to ExecStartPre messes up suspend functionality. That is a pity... Laptop: Thinkpad P1 with nvidia graphics -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] Re: Desktop freezes refuses input
> I release the mouse with rigt Ctrl, that shows to pointer and I can move it. But click does not work. Does clicking not work on just app windows, or on the gnome shell panels too? ** Tags added: noclick ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** 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/1821160 Title: Desktop freezes refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821160] [NEW] Desktop freezes refuses input
You have been subscribed to a public bug: At random intervals desktop freezes. mouse does not function. Sometimes Alt+Tab works. I use virtualbox. Sometimes it captures the mouse and dont release it, and it take a few seconds to recognise that. I release the mouse with rigt Ctrl, that shows to pointer and I can move it. But click does not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 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: Thu Mar 21 12:34:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] [1002:954f] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RV710 [Radeon HD 4350/4550] [1043:0274] InstallationDate: Installed on 2019-03-16 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=3b8dc91d-1d7d-412f-ba84-ebeb03723557 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX 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.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic freeze noclick ubuntu -- Desktop freezes refuses input https://bugs.launchpad.net/bugs/1821160 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 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
> disruptiveness I'm talking about in terms of handling updates to the package, making it more cumbersome to handle and taking up the time/energy of reviewers, when a fast-moving experimental unfinished feature would be better maintained without that friction - allowing its developers to make any improvements they want with complete freedom. > That doesn't have the same "easy to try" nor PR potential, it also can't be described as part of the release... You'll have to give instructions for how to enable it anyway, and in that case telling people how to enable a PPA is not much of an extra leap. I would think that the main PR value is "look at this cool feature that Ubuntu's engineers have done, and you can watch it getting better with each update", which you can get with a PPA. Feel free to get a second opinion if you aren't inclined to accept this one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
** Changed in: mutter Status: Unknown => New -- 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/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #509 https://gitlab.gnome.org/GNOME/mutter/issues/509 ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/mutter/issues #506 => gitlab.gnome.org/GNOME/mutter/issues #509 ** Description changed: - https://gitlab.gnome.org/GNOME/mutter/issues/506 + https://gitlab.gnome.org/GNOME/mutter/issues/509 https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971 --- In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of package updates has stopped Apport from letting me report it until now, but the problem persists. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 11:22:20 2019 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1120 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd mock plugdev sambashare sbuild sudo wireshark separator: -- 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/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+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
Since this bug was marked as Fix Released some time ago, please continue discussion in the new bug 1803993 only. ** No longer affects: gdm3 (Ubuntu) ** No longer affects: gdm3 (Ubuntu 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/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/plymouth/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817225] Re: 18.04.2 breaks xrdp
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
Confirmed by https://askubuntu.com/q/1127408/66509 -- 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/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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
Confirmed by https://askubuntu.com/q/1127408/66509 . ** Changed in: gdm3 (Ubuntu) Status: Invalid => Confirmed ** Changed in: gdm3 (Ubuntu Bionic) Status: Invalid => Confirmed -- 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 1817225] Re: 18.04.2 breaks xrdp
** Also affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg-hwe-18.04 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
