[Bug 1855938] Re: [nvidia] Screen freezes and only mouse moves
@vanvugt: I haven't described a crash in Chromium. But I have switched away from Chromium, the frequency of Gnome Shell freezes it induces being one of the reasons. Attached is a journal from a freeze that happened today, with Firefox and VirtualBox open (and some filebrowser/terminal windows). ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+attachment/5351978/+files/prevboot.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/1855938 Title: [nvidia] Screen freezes and only mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855938] Re: Screen freezes and only mouse moves
Experiencing the same maybe once every two weeks for about two years now. When tabbing in or out of Chromium, the GUI freezes. The mouse cursor moves, but clicking does apparently nothing. The keyboard works: space bar to pause/resume music if a player was focused, as well as switching to a virtual terminal. I can log in there and kill X / restart gdm3, but the GUI session is lost. $ cat /etc/issue Ubuntu 18.04.3 LTS $ prime-select query intel Here's a heavily snipped journal (removed media key/spacenavd/network mount warnings and excess repeats) from around the crash: [SNIP] Jan 23 16:13:08 talas kernel: traps: compiz[17816] trap divide error ip:7fd0af9c4046 sp:7ffe928d2d20 error:0 in libstaticswitcher.so[7fd0af9b6000+1f000] [SNIP] Jan 23 16:13:35 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got pause for 13:86 [SNIP] Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got resume for 13:74 Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got resume for 226:0 Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) AIGLX: Resuming AIGLX clients after VT switch Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none Jan 23 16:13:36 talas kernel: drm: not enough stolen space for compressed buffer (need 36864000 more bytes), disabling. Hint: you may be able to increase stolen memory size in the BIOS to avoid this. [SNIP] Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed Jan 23 16:13:37 talas gnome-shell[1737]: Screen lock is locked down, not locking [SNIP] Jan 23 16:13:52 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) AIGLX: Suspending AIGLX clients for VT switch Jan 23 16:13:52 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got pause for 13:68 [SNIP] Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got resume for 13:65 Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got resume for 226:0 Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) AIGLX: Resuming AIGLX clients after VT switch Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) intel(0): switch to mode 1920x1200@60.0 on DP3-1 using pipe 0, position (1200, 0), rotation left, reflection none Jan 23 16:13:54 talas kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jan 23 16:13:54 talas kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Jan 23 16:13:54 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) intel(0): switch to mode 1920x1200@60.0 on DP3-2 using pipe 1, position (0, 0), rotation left, reflection none Jan 23 16:13:54 talas kernel: GpuWatchdog[22352]: segfault at 0 ip 5586b96ff28d sp 7f16fce386f0 error 6 in chromium-browser[5586b47ca000+8e97000] [SNIP] -- 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/1855938 Title: Screen freezes and only mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695742] Re: Fn keys recognised but not handled after 17.04 upgrade
Update: the Unity session as well as the sessions from the packages ubuntu-mate-desktop and cinnamon-desktop correctly handle all Fn keys. I'm stuck with Cinnamon for now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1695742 Title: Fn keys recognised but not handled after 17.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1695742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695742] [NEW] Fn keys recognised but not handled after 17.04 upgrade
Public bug reported: Ubuntu 17.04 amd64 upgraded from 16.10 on a Thinkpad T460p, gnome- flashback Compiz session. The Fn keys (media keys, brightness, XF86Search, etc.) have stopped working: all except XF86WLAN, which manages to toggle the wireless state, do nothing. They are visible in xev: KeyPress event, serial 62, synthetic NO, window 0x4e1, root 0xf8, subw 0x4e2, time 34775899, (50,45), root:(51,102), state 0x2010, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False and others like XF86AudioMute, XF86MonBrightnessUp, etc. neither affect the hardware nor show a notification. I can change the brightness through /sys/class/backlight/intel_backlight/brightness or with the System Settings -> Power -> Screen Brightness slider, and changing audio with the applet works too, so the drivers/modules appear to function well, but the events are not handled presumably by g-s-d (?). In System Settings -> Keyboard the shortcut for e.g. Volume Down is set to "Audio lower volume", and resetting to default as well as setting it via the keyboard doesn't change the situation. dmesg and journalctl -f are coming up empty (except for the correctly working XF86WLAN). I'd rather have this work properly instead of keybinding to amixer (with manually sent osd) or brightness file writing... Any suggestions? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-settings-daemon 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Jun 4 15:09:04 2017 InstallationDate: Installed on 2016-10-25 (221 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to zesty on 2017-05-31 (3 days ago) mtime.conffile..etc.xdg.autostart.gnome-settings-daemon.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.A11yKeyboard.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.A11ySettings.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Clipboard.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Color.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Datetime.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Housekeeping.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Keyboard.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.MediaKeys.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Mouse.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Orientation.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Power.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.PrintNotifications.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Rfkill.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.ScreensaverProxy.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Sharing.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Smartcard.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Sound.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.Wacom.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.XRANDR.desktop: 2017-05-31T23:37:45.416621 mtime.conffile..etc.xdg.autostart.org.gnome.SettingsDaemon.XSettings.desktop: 2017-05-31T23:37:45.416621 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1695742 Title: Fn keys recognised but not handled after 17.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1695742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
Not sure if this is equivalent, as I run unity-settings-daemon instead of gnome-settings-daemon (with the Compiz Unity-plugin turned off and gnome-panel instead), but it seems similar enough. Just upgraded from 14.04 to 16.04.1. I drop my laptop on a dock with two vertically oriented (rotated to portrait) monitors. This was working fine before, now it lights them up without the rotation. Rotating them manually via System Settings -> Displays, undocking and docking again reverts to the wrong (landscape) orientation. The ~/.config/monitors.xml looks fine but seems to be ignored. Reloading the settings with killall unity-settings-daemon gives me the correct orientation, which is read from the monitor.xml (editing the file by hand and killing u-s-d accepts whatever changes I make), it just doesn't get triggered on docking changes. That's the workaround for now: kill u-s-d every time I dock to that workplace, which may help with g-s-d too. It would be nice for patchlvl 1 LTS upgrades to not break such basic stuff. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245315] Re: alacarte fails to write a proper Categories=; line to .desktop files
Same with Ubuntu 13.10 64bit upgraded from 13.04. Editing the menus in gnome-panel or alternative application launchers/applets doesn't work as well as it should. There is no easy and obvious way (e.g. just dragdrop) to move the unnecessarily spammy new categories (Sundry, System Settings separate from System Tools, lots of items in Other) into one consolidated menu directory. But I guess that's another bug report. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1245315 Title: alacarte fails to write a proper Categories=; line to .desktop files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 306673] Re: autofs timeout
The bug still persists as of 12.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1088188] [NEW] Nautilus type-ahead plus mouse
Public bug reported:
OS: Ubuntu 12.04 amd64, Ubuntu 12.10 amd64, up-to-date Nautilus on each.
Reproduce:
Open directory with lots of subdirs (e.g. 'A...', ... , ''TRD001', 'TRD002',
'TRD003', ...), type first letter of target (e.g. 'T') to jump in that region,
then select it ('TRD003') with the mouse (single-click open) because that's
faster than typing it out or using the unintuitive up/down arrows (left/right
are reserved in this context), especially if you have either a trackpoint or
one hand on the mouse already.
Expected:
Nautilus should do the same af is it was typed out, then the Enter key was hit:
enter the directory and dismiss the search box.
Observed:
The search box in the bottom right corner stays with the letter 'T' typed, even
though we changed into the new subdirectory, making a follow-up type-ahead
awkward.
This has been handled correctly in the previous LTS release: using type-ahead,
then clicking anywhere inside the current directory (both _empty space between
icons_ and another dir/file) made the search box disappear.
The current behaviour is slowing down productivity with Nautilus, and since
most of the botched up Nautilus type-ahead behaviour in recent releases has
been corrected by now, I hope this one will get it's fix too.
Another application doing this correctly and intuitively is Firefox with
find-as-you-type turned on.
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
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/1088188
Title:
Nautilus type-ahead plus mouse
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1088188/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1051417] [NEW] sleep-display for battery vs AC in GUI
Public bug reported: OS: Ubuntu 12.04 Hardware: ThinkPad X230 Rationale: Being able to set different screen-inactive-times (-blank and lock) when on battery vs. AC is quite useful, for example 3-5 min vs. 20 min. Earlier versions of the power manager settings allowed this distinction, the current one (System Settings - Brightness and Lock) doesn't anymore (only for lid/critical actions in System Settings - Power). Observed behaviour: The corresponding dconf keys are org.gnome.settings-daemon.plugins.power.sleep-display-ac org.gnome.settings-daemon.plugins.power.sleep-display-battery Editing these seems to work after rudimentary testing, but also changes the Turn screen off when inactive for in Brightness and Lock to Never, regardless of which values are set. Changing the latter in turn sets both keys to the same value, which destroys the customisation. Expected behaviour: The Brightness and Lock should partially have a column for AC and battery each, like the Power settings do. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1051417 Title: sleep-display for battery vs AC in GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1051417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 371289] Re: fail to delete directory over sshfs with nautilus
This bug is still present in 12.04 with Nautilus 3.4.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/371289 Title: fail to delete directory over sshfs with nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/371289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 788415] Re: Can't disable suspend button
@Peter Silva: Instead of editing the default rules, one should create local ones, as shown here for hibernate and suspend: http://askubuntu.com/questions/94754/how-to-enable-hibernation-in-12-04/ I do agree that it's poorly documented though... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/788415 Title: Can't disable suspend button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/788415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 676072] Re: large image not correctly displayed in full screen
*** This bug is a duplicate of bug 653920 *** https://bugs.launchpad.net/bugs/653920 ** This bug has been marked a duplicate of bug 653920 resize bug (zoom in/resize window/scroll) * You can subscribe to bug 653920 by following this link: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/653920/+subscribe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. https://bugs.launchpad.net/bugs/676072 Title: large image not correctly displayed in full screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665384] Re: Rubbish on bottom of the image
*** This bug is a duplicate of bug 653920 *** https://bugs.launchpad.net/bugs/653920 ** This bug has been marked a duplicate of bug 653920 resize bug (zoom in/resize window/scroll) * You can subscribe to bug 653920 by following this link: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/653920/+subscribe -- Rubbish on bottom of the image https://bugs.launchpad.net/bugs/665384 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 653920] Re: resize bug (zoom in/resize window/scroll)
Reproducible on Ubuntu 10.10 64bit (upgraded from 10.04), nvidia driver, Compiz on. -- resize bug (zoom in/resize window/scroll) https://bugs.launchpad.net/bugs/653920 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 467284] Re: gconf: gnome-power-manager hibernate flag
Yes, the bug still persists. Moreover, the key now has a This key has no schema exclamation mark. I'd be content with having another option to disable the hibernate button in the shutdown menu, but I haven't found any corresponding settings yet. -- gconf: gnome-power-manager hibernate flag https://bugs.launchpad.net/bugs/467284 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
