[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
Started seeing this behaviour on 16.04 (fully updated), since 26-Feb. -- 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/1689356 Title: UI scale being reset to 1 everytime when display sleeps for a while Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. *-* This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. *-* ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Tu
[Desktop-packages] [Bug 332646] Re: sftp does not set timestamps
Related, and possible NOT worth raising as its own bug.
Renaming a zero-length (semaphore) file in Nautilus does NOT change its
time/date stamp.
Tested/verified today with fully updated Ubuntu 16.04 LTS, and
'Nautilus' ('Files' v3.14.3).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/332646
Title:
sftp does not set timestamps
Status in gvfs:
Confirmed
Status in gvfs package in Ubuntu:
Confirmed
Bug description:
Binary package hint: gvfs
when copying or moving files to a directory mounted over sftp, the
time stamps are not preserved.
this affects both hardy and intrepid (in hardy, it was tested with a
patched version of nautilus hence that version used to forget
timestamps on copy anyway). in both cases, i tested it locally and
everything was preserved as it should be.
moreover, when moving, nautilus first displays the correct time stamp
and only on refreshing shows the wrong updated one.
as timestamps can be considered considered important information, i
suggest this bug be treated as "losing data without notice".
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/332646/+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 1292041] Re: Lockscreen doesn't turn off the screen
Please see Bug #1292695 (which is NOT a duplicate of this NOW CLOSED bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 288762] Re: totem: can't skip chapters in matroska files
This issue is still present in Ubuntu 14.04 LTS, fully updated. An .mkv file with OR without chapters is treated the same by Totem. Most of my files played on VLC (or other player) have chpater information and you can navigate to next/previous chapter. What is the root cause? Why did this fix (xine-lib v1.1.17, per comment #11) never reach/affect Trusty (14.04)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/288762 Title: totem: can't skip chapters in matroska files Status in gstreamer0.10 package in Ubuntu: Confirmed Status in xine-lib package in Ubuntu: Fix Released Bug description: Binary package hint: totem-xine Totem is unable to access the chapters of Matroska files. The Next/Previous chapter menu options are disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/288762/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
Compiz works for me: (Force full screen redraws (buffer swap) on repaint [x]) Ubuntu 14.04 fully updated Quadro K420/PCIe/SSE2 Needed to switch from Nouveau (to edgers Nvidia 340.58) to resolved DisplayPort not handling screen saver / blanking, and poor performance (or X server crash) with DVI (Dual Link). I have just upgraded to a Samsung 27" with 2560 x 1440 resolution. The K420 video card was also required, as earlier cards (NSA 310, NVS 315) could not keep up with higher resolution. Tearing and remnants on full screen video or larger scaling of some applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in xorg package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x" NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notif
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
I am running Ubuntu 14.04 LTS (64-bit), fully updated. Unity version is: 7.2.3+14.04.20140826-0ubuntu1 I just changed monitors, and also from DVI to DisplayPort (due to higher resolution). The screen does not 'turn off', after screen locked (or timeout). Screen is black (with white mouse cursor), but still fully backlit. This does not change after many hours. This may not be the SAME bug (as original post), but has identical symptoms. NEW BUG ? Any advice / suggestions ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1251983] Re: Ubuntu 13.10 disconnects randomly
Looks more like a PPTP issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1251983 Title: Ubuntu 13.10 disconnects randomly Status in “network-manager” package in Ubuntu: New Bug description: My VPN connection fails every several minutes. Due to the fact, I cannot check properly whether the bug has been already reported. System Log (see attachment) shows likely problems with network-manager (0.9.8.0-0ubuntu22). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1251983/+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 1171578] Re: Unable to Play DVD's in Ubuntu 13.04
Verified in 13.04 (64-bit) fully updated as of 12th July. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1171578 Title: Unable to Play DVD's in Ubuntu 13.04 Status in “gstreamer0.10” package in Ubuntu: Fix Released Bug description: Many DVD's which played fine in 12.10 will not play in 13.04. An error windoe comes up saying the stream is in the wrong format. Medibuntu and libdvdcss2 are installed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 22 14:42:15 2013 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2013-04-09 (13 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1171578/+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 332646] Re: sftp does not set timestamps
Able to resolve, using 'scp -rp' at command line. Unable to resolve from any GUI app, that (in theory) uses SCP or SFTP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/332646 Title: sftp does not set timestamps Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs when copying or moving files to a directory mounted over sftp, the time stamps are not preserved. this affects both hardy and intrepid (in hardy, it was tested with a patched version of nautilus hence that version used to forget timestamps on copy anyway). in both cases, i tested it locally and everything was preserved as it should be. moreover, when moving, nautilus first displays the correct time stamp and only on refreshing shows the wrong updated one. as timestamps can be considered considered important information, i suggest this bug be treated as "losing data without notice". To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/332646/+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 332646] Re: sftp does not set timestamps
Repeated testing using Nautilus, and SFTP to server. Does NOT honour timestamp, for files or directories. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/332646 Title: sftp does not set timestamps Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs when copying or moving files to a directory mounted over sftp, the time stamps are not preserved. this affects both hardy and intrepid (in hardy, it was tested with a patched version of nautilus hence that version used to forget timestamps on copy anyway). in both cases, i tested it locally and everything was preserved as it should be. moreover, when moving, nautilus first displays the correct time stamp and only on refreshing shows the wrong updated one. as timestamps can be considered considered important information, i suggest this bug be treated as "losing data without notice". To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/332646/+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 332646] Re: sftp does not set timestamps
This was partially fixed in Ubuntu 12.04 LTS (desktop). Puch / Puill: If you copy from a remote Ubuntu platform, then the timestamp is preserved. But if you copy too, then only some platforms honour the timestamp (otherwise it is set to 'now' by the receiving platform). Tested today with full patched Ubuntu 12.04.2 LTS desktop, server, and Ubuntu 13.04 desktop (all 64-bit): - Copying from 13.04 desktop to 12.04 desktop ( Ok ) - Copying from 13.04 desktop to 12.04 server ( timestamp replaced, with 'now' ) - Copying from 12.04 desktop to 13.04 desktop ( Ok ) - Copying from 12.04 desktop to 12.04 server ( Ok, but new directories have timestamp of 'now' ) This should be fixed, and be consistent. Either as default behaviour, or from SFTP config. file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/332646 Title: sftp does not set timestamps Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs when copying or moving files to a directory mounted over sftp, the time stamps are not preserved. this affects both hardy and intrepid (in hardy, it was tested with a patched version of nautilus hence that version used to forget timestamps on copy anyway). in both cases, i tested it locally and everything was preserved as it should be. moreover, when moving, nautilus first displays the correct time stamp and only on refreshing shows the wrong updated one. as timestamps can be considered considered important information, i suggest this bug be treated as "losing data without notice". To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/332646/+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 1179553] Re: fglrx 2:9.000-0ubuntu3: fglrx kernel module failed to build
*** This bug is a duplicate of bug 859101 *** https://bugs.launchpad.net/bugs/859101 This affect Ubunut 12.04 (precise), 12.10, and 13.04 (raring). It is unliley to be a duplicate of Bug 859101 (which was on 11.10 back in Sep 2011). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1179553 Title: fglrx 2:9.000-0ubuntu3: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: Incomplete Bug description: I know I'm ahead with the kernel, but this kernel supports ssd caching and I don't want to wait 6 month. Anyway in my opinion this should not happen. Still looking for a "LINUX" Graphics-card. Graphics have always been a problem since I started with linux ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:9.000-0ubuntu3 Uname: Linux 3.9.0-030900rc8-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin DKMSBuildLog: DKMS make.log for fglrx-9.000 for kernel 3.9.0-030900rc8-generic (x86_64) Mo 13. Mai 17:33:13 CEST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.9.0-030900rc8-generic/build/include not found or incomplete file: /lib/modules/3.9.0-030900rc8-generic/build/include/linux/version.h DKMSKernelVersion: 3.9.0-030900rc8-generic Date: Mon May 13 17:33:16 2013 DistUpgraded: 2012-09-18 08:26:30,008 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: kubuntu DkmsStatus: fglrx, 9.000, 3.5.0-17-generic, x86_64: installed fglrx, 9.000, 3.5.0-28-generic, x86_64: installed DuplicateSignature: DKMS make.log for fglrx-9.000 for kernel 3.9.0-030900rc8-generic (x86_64) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.9.0-030900rc8-generic/build/include not found or incomplete file: /lib/modules/3.9.0-030900rc8-generic/build/include/linux/version.h GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2111] InstallationDate: Installed on 2012-06-26 (321 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: MSI MS-7798 MarkForUpload: True PackageVersion: 2:9.000-0ubuntu3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-030900rc8-generic root=UUID=f4b1a9c2-3b75-419a-b2b5-8f7ae9401e30 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx 2:9.000-0ubuntu3: fglrx kernel module failed to build UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 UpgradeStatus: Upgraded to quantal on 2012-09-18 (237 days ago) dmi.bios.date: 07/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75MA-P45 (MS-7798) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd07/30/2012:svnMSI:pnMS-7798:pvr1.0:rvnMSI:rnB75MA-P45(MS-7798):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7798 dmi.product.version: 1.0 dmi.sys.vendor: MSI make.log: DKMS make.log for fglrx-9.000 for kernel 3.9.0-030900rc8-generic (x86_64) Mo 13. Mai 17:33:13 CEST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.9.0-030900rc8-generic/build/include not found or incomplete file: /lib/modules/3.9.0-030900rc8-generic/build/include/linux/version.h version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Desktop-packages] [Bug 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Andres, please update 'bug affects you'. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
WORK AROUND (remove the package) ~: [b] sudo apt-get remove gnome-screensaver[/] ~: [b]sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra[/b] After installing, go to ‘Control –> Startup Applications’ Then click ‘Add’ and type the entry below: Name: Xscreensaver Command: xscreensaver –nosplash Finally click ‘Add’ When finish, open ‘Dash’ and search for xscreensaver. Open it and customize it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 756374] Re: the screensaver locks after I try to get out of it by moving the mouse or typing the keys
Similar to Bug #882893, which is for Ubuntu 11.10 (Oneiric). Some (older) graphic cards do not like Screen-Off (used by Gnome Screensaver), and CRASH .. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/756374 Title: the screensaver locks after I try to get out of it by moving the mouse or typing the keys Status in “gnome-screensaver” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-screensaver I am using the Floating Ubuntu on Natty and for two times now, the screensaver seems to freeze when I try to exit from it back to my desktop by actually using the computer I should (as it used to) redraw the desktop... I had to Ctrl+Alt+Bkpspc (kill gdm+X) to recover from it ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-screensaver 2.30.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.41-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Sun Apr 10 05:32:39 2011 EcryptfsInUse: Yes GconfGnomeSession: idle_delay = 25 /desktop/gnome/session/required_components: windowmanager = gnome-wm GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=pt_BR:en LANG=en_US.UTF-8 LC_MESSAGES=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to natty on 2011-04-10 (0 days ago) WindowManager: gnome-wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/756374/+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 842801] Re: gnome-screensaver crashed with signal 5 in _XError()
May be related to: Bug #882893 Some graphic cards do not like Screen-Off (used by screensaver), and CRASH .. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/842801 Title: gnome-screensaver crashed with signal 5 in _XError() Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: I was doing nothing special when this bug occured... ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.1.5-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 Architecture: i386 Date: Tue Sep 6 16:59:43 2011 ExecutablePath: /usr/bin/gnome-screensaver InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon ProcEnviron: SHELL=/bin/bash LC_MESSAGES=fr_FR.UTF-8 PATH=(custom, no user) LANGUAGE=fr:en LANG=fr_FR.UTF-8 Signal: 5 SourcePackage: gnome-screensaver StacktraceTop: ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 _XError () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: gnome-screensaver crashed with signal 5 in _XError() UpgradeStatus: Upgraded to oneiric on 2011-09-06 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/842801/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Previously noted, for Ubuntu 9.10 (Karmic) http://ubuntuforums.org/showpost.php?p=10279527 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Discussed elsewhere: http://earlruby.org/2011/10/work-around-for-a-locked-up-gnome-3-screen- saver-in-ubuntu-11-10/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
This could be an issue with the Intel 82865G integrated graphics driver. I have tried the older Intel 2.4 Driver. RevertingIntelDriverTo2.4 https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4 ( Does NOT work, missing details and valid PPA sources .. ) Instead I used: Downgraded versions of X.org drivers, libraries, etc. for Ubuntu. https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-retro Click on: 'View package details' Click on: 'xserver-xorg-video-intel-2.4 - 2:2.4.1-1ubuntu11~ppa1' (near bottom) Download: https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-retro/+files/xserver-xorg-video-intel-2.4_2.4.1-1ubuntu11%7Eppa1_i386.deb Then installed using: Ctrl-Alt-F1, for text login cd Downloads/ (location of .deb file) sudo dpkg -i xserver-xorg-video-intel-2.4_2.4.1-1ubuntu11~ppa1_i386.deb (enter password) sudo apt-get -f install (re-start PC) THIS DID NOT APPEAR TO FIX PROBLEM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
This may or may not be related to: Bug #727594 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
This can be defeated once, by pressing 'shift' key to wakeup. This works once (after boot time), and does NOT work a second time (after subsequent timeout). When PC is in lockout state, only power-off is possible. I have loaded SSH server, and machine is also non-responsive to connect attempt (over SSH). ** Tags added: 11.10 screensaver ui unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 778953] Re: gnome-screensaver 2.30.2-0ubuntu2 failed to exit
Created Bug #882893 instead. This identifies that this is for Ubuntu 11.10 (Oneiric) and Unity-2D. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/778953 Title: gnome-screensaver 2.30.2-0ubuntu2 failed to exit Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-screensaver If the screensaver start after 10 minutes and I want to use my PC again, it doesn't exit. I see the mouse and the screensaver stops moving but my computer freezes. Then I have to restart it by holding the turn-off button 5 seconds. This don't happens always, somethimes there is no problem. I use Ubuntu 11.04 with the Unity Interface and the Floating Ubuntu screensaver. The version of gnome-screensaver is 2.30.2-0ubuntu2. I've updated from Ubuntu 10.10 and there I never had a problem. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-screensaver 2.30.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Sat May 7 11:51:34 2011 GconfGnomeSession: idle_delay = 10 /desktop/gnome/session/required_components: windowmanager = gnome-wm panel = gnome-panel GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to natty on 2011-04-29 (8 days ago) WindowManager: gnome-wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/778953/+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 882893] [NEW] gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Public bug reported: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
This may be similar to, or a recurrence of, Bug #778953 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit Status in “gnome-screensaver” package in Ubuntu: New Bug description: On older PC (Intel P4 2.8GHz, 1GB RAM), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Occurs when I wait for timeout, and screen blanks. Does NOT occur when select screen-lock (from GUI, or keyboard) I have now two separate PCs, with identical results. Note: login screen (lightdm) is not susceptible to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+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 778953] Re: gnome-screensaver 2.30.2-0ubuntu2 failed to exit
I'm still seeing this behavior in Ubuntu 11.10 That is, for package: gnome-screensaver 3.2.0-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/778953 Title: gnome-screensaver 2.30.2-0ubuntu2 failed to exit Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-screensaver If the screensaver start after 10 minutes and I want to use my PC again, it doesn't exit. I see the mouse and the screensaver stops moving but my computer freezes. Then I have to restart it by holding the turn-off button 5 seconds. This don't happens always, somethimes there is no problem. I use Ubuntu 11.04 with the Unity Interface and the Floating Ubuntu screensaver. The version of gnome-screensaver is 2.30.2-0ubuntu2. I've updated from Ubuntu 10.10 and there I never had a problem. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-screensaver 2.30.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Sat May 7 11:51:34 2011 GconfGnomeSession: idle_delay = 10 /desktop/gnome/session/required_components: windowmanager = gnome-wm panel = gnome-panel GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to natty on 2011-04-29 (8 days ago) WindowManager: gnome-wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/778953/+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 778953] Re: gnome-screensaver 2.30.2-0ubuntu2 failed to exit
On older PC (Intel P4 2.8GHz, 1GB ram), I am seeing this lockup with default settings. Ubuntu 11.10, Unity-2D, latest patch/updates loaded. Note: login screen (lightdm) is not susceptible to this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/778953 Title: gnome-screensaver 2.30.2-0ubuntu2 failed to exit Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-screensaver If the screensaver start after 10 minutes and I want to use my PC again, it doesn't exit. I see the mouse and the screensaver stops moving but my computer freezes. Then I have to restart it by holding the turn-off button 5 seconds. This don't happens always, somethimes there is no problem. I use Ubuntu 11.04 with the Unity Interface and the Floating Ubuntu screensaver. The version of gnome-screensaver is 2.30.2-0ubuntu2. I've updated from Ubuntu 10.10 and there I never had a problem. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-screensaver 2.30.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Sat May 7 11:51:34 2011 GconfGnomeSession: idle_delay = 10 /desktop/gnome/session/required_components: windowmanager = gnome-wm panel = gnome-panel GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=nl_NL:en LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to natty on 2011-04-29 (8 days ago) WindowManager: gnome-wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/778953/+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 796076] Re: When run as root [gksudo gedit ] gedit tries to open a 2nd 'untitled document 1'
see also: Bug #838404 (more or less) a duplicate of this bug. Bug #805682 Underlying issues with Nautilus and gksudu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/796076 Title: When run as root [gksudo gedit ] gedit tries to open a 2nd 'untitled document 1' Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Triaged Bug description: Binary package hint: gedit Ex. gksudo gedit /etc/fstab will open fstab successfully but will also try to open "Untitled Document 1" at the same time If just running gksudo gedit than you'll get "Untitled Document 1" that never does fully open (become writable == Regression details == Discovered in version: 3.0.4-0ubuntu2 Last known good version: 2.30.4-2ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.0.4-0ubuntu2 [modified: usr/share/applications/gedit.desktop] ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7 Uname: Linux 2.6.38-9-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jun 11 19:11:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/796076/+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 838404] Re: opening existing file with gksu gedit creates untitled document
Does this mean (based on Bug #805682) we should: (a.) henceforth use sudo gedit systemfile (with some security issues) OR, (b.) agitate for this to be fixed, and soon. ?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/838404 Title: opening existing file with gksu gedit creates untitled document Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Triaged Bug description: When opening a text file as super user, using gksu gedit , the requested file opens, along with a second, untitled document. This is slightly annoying, since gedit will ask if the untitled document should be saved once the desired file has been edited and gedit is closed. Opening a file as a regular user does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 Date: Wed Aug 31 14:12:52 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: gedit UpgradeStatus: Upgraded to oneiric on 2011-08-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/838404/+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
