[Bug 595555] Re: screensaver can't be interrupted once fade begins
Launchpad has imported 88 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=612620. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-07-08T15:50:49+00:00 james wrote: Description of problem: With xorg-x11-server-Xorg-1.8.2-1.fc13, it is no longer possible to interrupt fade-out-to-screensaver with either a keypress or mouse movement. Works OK under xorg-x11-server-Xorg-1.8.0-12.fc13.x86_64. Version-Release number of selected component (if applicable): gnome-screensaver-2.30.0-1.fc13.x86_64 gnome-power-manager-2.30.1-1.fc13.x86_64 [I understand this might be a X server bug, but I've filed it under g-ss for the time begin. Please reassign as appropriate.] Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/3 On 2010-07-08T21:55:53+00:00 jeff.raber wrote: I have the same package versions as mentioned in comment 1, but am unable to reproduce this issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/4 On 2010-07-09T16:16:05+00:00 james wrote: (In reply to comment #1) > I have the same package versions as mentioned in comment 1, but am unable to > reproduce this issue. Maybe it's hardware dependent. I have Intel X3100 graphics with xorg-x11 -drv-intel-2.11.0-5.fc13.x86_64. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/5 On 2010-07-09T16:38:14+00:00 jeff.raber wrote: Please add drm.debug=0x04 to the kernel command line, restart your computer, reproduce the issue, then attach to following items to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) Also, is the computer fading out to a screensaver, or to low power mode? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/6 On 2010-07-09T17:26:08+00:00 jeff.raber wrote: Created attachment 430725 yum.log showing the packages that were update/installed on 2010-07-08 Yesterday I could not reproduce this issue. Today I can. I have attached a log showing the 80 packages (minus the debuginfo packages) that were installed/updated on my machine yesterday. Prime suspects are 'libdrm' and 'kernel' and maybe 'xorg-x11-drv- vmmouse'. In my free time, I will try downgrading each to see if that resolves the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/7 On 2010-07-09T17:58:28+00:00 nphilipp wrote: (In reply to comment #2) > (In reply to comment #1) > > I have the same package versions as mentioned in comment 1, but am unable to > > reproduce this issue. > > Maybe it's hardware dependent. I have Intel X3100 graphics with > xorg-x11-drv-intel-2.11.0-5.fc13.x86_64. Sounds reasonable: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) xorg-x11-drv-intel-2.11.0-5.fc13.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/8 On 2010-07-09T18:50:12+00:00 jeff.raber wrote: Sorry, I should have mentioned mine is: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/9 On 2010-07-09T19:11:39+00:00 james wrote: Created attachment 430743 dmesg output with drm.debug=0x04 after failed attempt to stop a fadeout Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/10 On 2010-07-09T19:12:19+00:00 james wrote: Created attachment 430744 Xorg.0.log after failed attempt to stop fadeout Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/59/comments/11 On 2010-07-09T19:15:05+00:00 james wrote: (In reply to comment #3) > Please add drm.debug=0x04 to the kernel command line, restart your computer, > reproduce the issue, then attach to following items to the bug re
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: xorg-server (Fedora) Status: Unknown => Fix Released ** Changed in: xorg-server (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/59 Title: screensaver can't be interrupted once fade begins To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/59/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Also affects: xorg-server (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/59 Title: screensaver can't be interrupted once fade begins -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
In case anyone is still looking for an answer, I've found a solution: Since the screensaver is now handled by gnome, I checked the Configuration Editor. You'll find the screensaver settings in there under apps -> gnome-screensaver. I noticed that the "idle-delay" key was NOT set to the value I put in the gui settings (System->Preferences->Screensaver) which was 1 minute. It had 10 instead. Once I set it to 1 minute the screensaver actually started at 1 minute instead of just fading and coming back to the desktop. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/59 Title: screensaver can't be interrupted once fade begins -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Branch linked: lp:ubuntu/xorg-server -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: gnome-screensaver Status: Invalid => Unknown ** Changed in: gnome-screensaver Importance: Unknown => Medium -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Branch linked: lp:ubuntu/xorg-server -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
This bug was fixed in the package xorg-server - 2:1.9.0-0ubuntu1 --- xorg-server (2:1.9.0-0ubuntu1) maverick; urgency=low * Merge from (unreleased) Debian experimental. Remaining Ubuntu changes: - rules, control: + Disable SELinux, libaudit-dev is not in main yet (LP 406226). Drop libaudit-dev from build-deps. - rules: Enable xcsecurity (LP 247537). - local/xvfb-run*: Add correct docs about error codes (LP 328205) - rules: Add --with-extra-module-dir to support GL alternatives. - control: Xvfb depends on xauth, x11-xkb-utils. (LP 500102) - rules, local/64-xorg-xkb.rules: Don't use keyboard-configuration until it's available. - control: Update some versioned Breaks for Ubuntu versions. - debian/patches: + 100_rethrow_signals.patch: When aborting, re-raise signals for apport + 109_fix-swcursor-crash.patch: Avoid dereferencing null pointer while reloading cursors during resume. (LP 371405) + 111_armel-drv-fallbacks.patch: Add support for armel driver fallbacks. + 121_only_switch_vt_when_active.diff: Add a check to prevent the X server from changing the VT when killing GDM from the console. + 122_xext_fix_card32_overflow_in_xauth.patch: Fix server crash when “xauth generate” is called with large timeout. + 157_check_null_modes.patch, 162_null_crtc_in_rotation.patch, 166_nullptr_xinerama_keyrepeat.patch, 167_nullptr_xisbread.patch 169_mipointer_nullptr_checks.patch, 172_cwgetbackingpicture_nullptr_check.patch: Fix various segfaults in xserver by checking pointers for NULL values before dereferencing them. + 165_man_xorg_conf_no_device_ident.patch Correct man page + 168_glibc_trace_to_stderr.patch: Report abort traces to stderr instead of terminal + 184_virtual_devices_autodetect.patch: Use vesa for qemu device, which is not supported by cirrus + 187_edid_quirk_hp_nc8430.patch: Quirk for another LPL monitor (LP 380009) + 188_default_primary_to_first_busid.patch: Pick the first device and carry on (LP 459512) + 189_xserver_1.5.0_bg_none_root.patch: Create a root window with no background. + 190_cache-xkbcomp_output_for_fast_start_up.patch: Cache keyboard settings. + 191-Xorg-add-an-extra-module-path.patch: Add support for the alternatives module path. + 197_xvfb-randr.patch: Adds xrandr support to xvfb. (LP 516123) + 198_nohwaccess.patch: Adds a -nohwaccess argument to make X not access the hardware ports directly. + 200_randr-null.patch: Clarify a pointer initialization. + 203_gestures-extension.patch: + 202_xf86CoordinationsToWindows.patch: Add gesture extension support (LP: 616678) + debian/serverminver: Bump for gesture support * New upstream release: - Fixes crash in DamageUnregister on session close (LP: #343694) - Fixes crash with extremely large windows exposed by xpdf (Closes: #320627) * Drop 17-fix-DRI2-segfault-when-clientGone.diff: fixed upstream in more generality. * debian/patches/204_fix-neg-sync-transition.patch: - Fix edge case in SYNC extension resulting in GNOME screensaver's fade-to-screensaver being uninteruptible. (LP: #59) -- Christopher James Halse RogersTue, 24 Aug 2010 15:44:10 +1000 ** Changed in: xorg-server (Ubuntu Maverick) Status: In Progress => Fix Released -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
I think the patches on the Fedora bug are incorrect, although the analysis is helpful. ** Changed in: xorg-server (Ubuntu Maverick) Status: Confirmed => In Progress -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
The Fedora bug apparently contains patches (mentioned in the Gnome bug, not tested by myself) ** Bug watch added: Red Hat Bugzilla #612620 https://bugzilla.redhat.com/show_bug.cgi?id=612620 ** Also affects: xorg-server (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=612620 Importance: Unknown Status: Unknown -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: xorg-server (Ubuntu Maverick) Status: Triaged => Confirmed -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
Chris, is that still on your list? -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: gnome-screensaver Status: New => Invalid -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
Thank you for your bug report, the issue started with the xserver new server this cycle, Chris do you have any clue about this issue? ** Package changed: gnome-screensaver (Ubuntu Maverick) => xorg-server (Ubuntu Maverick) ** Changed in: xorg-server (Ubuntu Maverick) Assignee: Canonical Desktop Team (canonical-desktop-team) => Chris Halse Rogers (raof) -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: gnome-screensaver (Ubuntu Maverick) Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team) -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: gnome-screensaver Status: Unknown => New -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
The screensaver hasn't changed in maverick. Are you sure this isn't a xserver issue? -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
Thank you for reporting this bug upstream. This has been reported by people using "gnome-screensaver 2.30.0-1ubuntu1". I am setting this to triaged/medium as asked to by Mohamed Amine IL Idrissi in #ubuntu-bugs. ** Changed in: gnome-screensaver (Ubuntu Maverick) Importance: Undecided => Medium ** Changed in: gnome-screensaver (Ubuntu Maverick) Status: Confirmed => Triaged -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Bug watch added: GNOME Bug Tracker #625374 https://bugzilla.gnome.org/show_bug.cgi?id=625374 ** Also affects: gnome-screensaver via https://bugzilla.gnome.org/show_bug.cgi?id=625374 Importance: Unknown Status: Unknown -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Tags added: regression-potential x64 -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Also affects: gnome-screensaver (Ubuntu Maverick) Importance: Undecided Status: Confirmed -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
Yep, I also see this - to me this is a regression relative to Lucid. (seen on 2 machines). The other thing is the fade is very very slow. Dave -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
I have the same symptoms in Lucid, but using Xorg edgers PPA. There is also bug #512306 for Lucid. -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595555] Re: screensaver can't be interrupted once fade begins
Thanks for your report. I will move this to gnome-screensaver since the above information indicates that you are not using xscreensaver. ** Package changed: xscreensaver (Ubuntu) => gnome-screensaver (Ubuntu) -- screensaver can't be interrupted once fade begins https://bugs.launchpad.net/bugs/59 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
