[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855938 Title: [nvidia] Screen freezes and only mouse moves Status in gnome-shell package in Ubuntu: Incomplete Bug description: The screen freezes but the mouse can be moved. SSH access works. This is on Legion Y545, Ubuntu 19.10 Nvidia Geforce 1660Ti Intel 9750h Symptoms: This only happens when: Nvidia-Prime is selected as "on-demand" And maybe most likely after the laptop comes out of sleep. xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1 If I choose prime-select "nvidia", this never happens. Makes me believe this has to do with intel video drivers. Error trace: GpuWatchdog[22171]: segfault at 0 ip 56163556379d sp 7fdeb6dd8480 error 6 in chrome[561631628000+717] Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 01 80 7d 8f 00 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 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' Date: Tue Dec 10 15:01:38 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc] InstallationDate: Installed on 2019-10-23 (48 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81Q6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545: dmi.product.family: Legion Y545 dmi.product.name: 81Q6 dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545 dmi.product.version: Legion Y545 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855938 Title: Screen freezes and only mouse moves Status in gnome-shell package in Ubuntu: Incomplete Bug description: The screen freezes but the mouse can be moved. SSH access works. This is on Legion Y545, Ubuntu 19.10 Nvidia Geforce 1660Ti Intel 9750h Symptoms: This only happens when: Nvidia-Prime is selected as "on-demand" And maybe most likely after the laptop comes out of sleep. xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1 If I choose prime-select "nvidia", this never happens. Makes me believe this has to do with intel video drivers. Error trace: GpuWatchdog[22171]: segfault at 0 ip 56163556379d sp 7fdeb6dd8480 error 6 in chrome[561631628000+717] Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 01 80 7d 8f 00 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Upgraded 17.10 -> 18.04, Thinkpad X460p with GeForce 940MX. No issues before (even both prime AND bumblebee worked). Exhaustively tried combinations of blacklisting modules, nvidia.modeset kernel lines and reinstalls of both default and ppa 390/396 drivers. The system will not boot past the filesystem check with nvidia drivers (and prime/bumblebee can't load them either), which renders the GPU unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, 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 Status in gnome-settings-daemon package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1695742/+subscriptions -- Mailing list:
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-settings-daemon package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 1578243] Re: Screen configuration is not preserved when logging out and logging back in
Just upgraded from 14.04 to 16.04.1 and found this (and the workaround) via googling. 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 the workplace. 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 Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1578243 Title: Screen configuration is not preserved when logging out and logging back in Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I have two identical monitors, with the dock on the left-hand side of the left monitor and the stickiness of the middle edge between the two monitors disabled. When I log out and immediately log back in, my monitor configuration changes and now both monitors are mirroring the same content. I have to hit Command-P to get them to switch back to the non-mirrored configuration they were displaying immediately before I logged out. This happens consistently, every time I log out and log back in. The monitor configuration should be preserved when I log out and log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Wed May 4 10:27:26 2016 DistUpgraded: 2016-04-28 15:18:23,890 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller [1558:7410] MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-28 (5 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. upstart.unity7.log: JavaScript error: , line 0: uncaught exception: 2147746065 version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 10:20:25 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [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 Desktop Packages, 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 Status in elementary OS: Fix Released Status in gnome-settings-daemon: Unknown Status in gnome-shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 955355] Re: Compiz does not allow focusing on the desktop with click-to-focus disabled
Confirming on 14.04 with current updates. Unable to rename files on desktop with click to focus turned off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/955355 Title: Compiz does not allow focusing on the desktop with click-to-focus disabled Status in Compiz: Confirmed Status in Compiz Core: Confirmed Status in compiz package in Ubuntu: Confirmed Bug description: With click-to-focus disabled (follow focus), compiz does not allow focusing on the desktop with any non-minimized windows present. If click-to-focus is enabled, then compiz behaves as expected. Steps to reproduce: - disable click-to-focus in compiz - open at least one application - try to rename a file on the desktop At this point the desktop will not receive focus, and typing will go into the last focused window, not the desktop (for file rename). lsb_release info: Ubuntu precise (development branch) 12.04 compiz version: 1:0.9.7.0+bzr3035-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/955355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363624] Re: Compiz mouse interact with the focused window only
Same problem here, Ubuntu 14.04, Compiz 0.9.11.2+14.04.20140714-0ubuntu1, current updates. Tried to use focus follows mouse (aka turning off click to focus), but this is too buggy in the current version of Compiz (e.g. can't rename files on desktop). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1363624 Title: Compiz mouse interact with the focused window only Status in Compiz: New Status in compiz package in Ubuntu: Confirmed Bug description: Ubuntu 14.04.1 LTS - xfce version: 1:0.9.11.2+14.04.20140714-0ubuntu1 I use enhanced zoom desktop a lot and since I upgrade to ubuntu 14.04 I can't zoom if the mouse cursor isn't on the focused windows. Not on the menu of the focused windows, not on the windows in the background, not on the ubuntu menu and toolbar etc. It severely restricts the possibilities of this great tool. Are you aware and do you know what cause this new behaviour in 14.04? Could you do somethong about it? Or is there a workaround? To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1363624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1245315 Title: alacarte fails to write a proper Categories=; line to .desktop files Status in “alacarte” package in Ubuntu: Confirmed Bug description: When creating a new menu entry in the Applications Menu of Xubuntu using the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not enable the writing of a Categories=; attribute in the new .desktop file created in /home//local/share/applications/. Without a recognized and meaningful Categories=; attribute, the new menu entry is relegated by default to the non-specific Other menu category in the Applications Menu of Xubuntu. Moving the newly-created menu entry in question to a more meaningful Applications Menu category (such as, eg, Applications, Office, Systems, etc) by dragging and dropping then fails in alacarte due to the very absence of any Categories=; attribute in the .desktop file. Instead, First, when creating a new menu entry in, for example, Applications, then alacarte should write a corresponding Categories=; attribute line in the newly-made .desktop file. Second, when dragging and dropping the newly-created menu entry in alacarte from, for example, Applications to, for instance, System, then alacarte should amend the Categories=; attribute line in the .desktop file accordingly. Note 1: If alacarte cannot do these things automatically, then it should at least allow the user to choose the Application Menu category, say, from a drop-down list, when creating or editing a menu entry, and write this choice to the corresponding .desktop file in the form of a suitable Categories=; attribute line. Note 2: Resolving this issue by manually editing .desktop files, of course, wholly defeats the very raison d'être of Menu Editor programs such as alacarte. -- System: xubuntu 13.10 32-bit fully up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 306673] Re: autofs timeout
The bug still persists as of 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout Status in Nautilus: Incomplete Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus OS: Ubuntu 8.10 Intrepid, upgraded from Hardy Software: SSHFS, AutoFS, no changes concerning Nautilus I'm using SSHFS with AutoFS to mount remote shares, which I must have unmounted after some time because of security concerns. This has had me set a timeout on the AutoFS mounts. The problem is that when opening a remote folder in Nautilus, the timeout countdown starts as soon as I stop clicking on folders/files. When it's down, I get a password prompt. This is buggy behaviour to me, because if I set the timeout to 10 seconds, there is a password prompt every 10 seconds if I just have a remote folder open in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's still quite annoying. I think that it should either: 1. Start the timeout as soon as I don't browse around or poll the file system manually in any other way. Then ask for a password only if user interaction occurs. 2. Don't time out as long as I have an open remote folder (after closing the last remote directory, let AutoFS time out and unmount). This is how KDE's Konqueror and gnome-terminal behave. There is already a bug filed at the GNOME bugzilla about this. But it originates from 2002 and the last comment is from 2006... which is about the issue still not being resolved. That's why I'm reporting here. If anyone has a better idea who to harass into fixing this, speak up ;) Here's the GNOME bug: http://bugzilla.gnome.org/show_bug.cgi?id=101673 I've also started a thread at the ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=1003656 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1088188
Title:
Nautilus type-ahead plus mouse
Status in “nautilus” package in Ubuntu:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1088188/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
Same bug here, booting from an OCZ Vertex 3 SSD, 10 out of 10 starts drop me to a irresponsive prompt + mouse cursor (restart lightdm from another virtual console works). The dirty workaround via sleep (1 second for me) gives a lightdm login prompt 10/10 times, so far. But apart from increasing OS boot time by roughly 50% ( ;) ), this just doesn't feel like the proper way to do it... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 Status in “lightdm” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10 doesn't load correctly because lightdm shows only a mouse pointer and a blinking command-line cursor. I don't know if this is only Ubuntu 12.10 specific bug, because a similar error appeared on my friend's computer back in 2011 on Ubuntu 11.10. However, switching to a command line and restarting lightdm solves the problem per instance. Also rebooting the device solves it, but also only for the specific boot. Another reboot ends with the same black screen with a working mouse pointer and a blinking cursor. I am using Asus Zenbook ux32vd (Intel HD Graphics 4000 + not used Nvidia GT620M - Optimus technology). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042069] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
@Andy: Thanks for the very useful conf file! It seems that sometime in 2010/2011 the default directory has switched from /etc/X11/xorg.conf.d/ to /usr/share/X11/xorg.conf.d/ ... so we should use that instead. There is already a 50-synaptics.conf file there. Currently I've pasted your config in a new 52-synaptics-x230.conf and it works well*. But for a proper fix the responsible Ubuntu maintainers should put it into the already present 51-synaptics-quirks.conf (which is obviously meant for such an occasion) with the correct MatchTag. I'd provide the MatchTag myself if I knew how to get it properly, but 'udevadm info --export-db' doesn't seem to offer anything directly useful and 'xinput -list' gives the fairly generic 'SynPS/2 Synaptics TouchPad'. * As an aside, I'm not sure if your config is 100% tuned, because my touchpad still jumps (just a few pixels) when moving slow-ish over the screen, but much less than before and I'm generally using the trackpoint anyway, so it's no big deal for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1042069 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: Really annoying bug! Trackpoint moves the mouse cursor smootly, when using the touchpad i have a jumpy cursor. (vertically it moves fine, horizontally it moves always 4 pixels at once). Please see the following demonstration video: http://www.youtube.com/watch?v=XUVRKFUsAmc ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 08:08:27 2012 InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120824) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1042069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042069] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
So far, Google doesn't bother returning a JumpyCursorThreshold with connection to the X230, so someone ;) will have to test it out... but we need a working MatchTag anyway for it to be of use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1042069 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: Really annoying bug! Trackpoint moves the mouse cursor smootly, when using the touchpad i have a jumpy cursor. (vertically it moves fine, horizontally it moves always 4 pixels at once). Please see the following demonstration video: http://www.youtube.com/watch?v=XUVRKFUsAmc ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 08:08:27 2012 InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120824) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1042069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1051417 Title: sleep-display for battery vs AC in GUI Status in “gnome-power-manager” package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1051417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/371289 Title: fail to delete directory over sshfs with nautilus Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: fail to delete non-empty directory over sshfs from nautilus by pressing the delete key. with Error removing file: Operation not permitted works if you empty the folder first. dir is chmod -R 0777 folder mount command was sshfs me@myServer:/ /media/myServer server: 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009 i686 GNU/Linux updated (not dist-update) Sun May 3 11:42:32 EDT 2009 client: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux updated Sun May 3 11:42:32 EDT 2009 it's like nautilus is asking for a rm -f file when it should be asking for a rm -fr file To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/371289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/788415 Title: Can't disable suspend button Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: gnome-power-manager does not allow you to set the suspend button to Do Nothing or Ask Me.It does have these options for the power button which is generally harder to hit by accident. This is a bug, not a feature request as argued in #712650.System is behaving in a non-consensual manner which can endanger the integrity of the system. Suspend button on Dynex DX-WKBD is located on corner of keyboard and very easy to bump.It was possible to disable this key in previous ubuntu/debian releases; indeed since a parrot used to share the workstation, it was necessary to disable all particularly destructive keys like suspend and window close. Also related to expired bug #492030. See also bug 736606, the equivalent problem for closing the lid. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CheckboxSubmission: 1e1a99f31ec2933306456e1f141c45d8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Wed May 25 20:20:13 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=02f53b93-8fd3-44ee-911b-a2d656e2d4d2 ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Crosshair IV Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1902:bd02/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/788415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
