← Back to team overview

desktop-packages team mailing list archive

Re: [Bug 849600] Re: gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()

 

There is one way to temporary fix it.
Start gnome-screensaver in console, and you can lock the screen.
But unfortunatly, screensaver segfault after unlock the screen.
18.09.2011 22:57 пользователь "Jeffrey Tees" <849600@xxxxxxxxxxxxxxxxxx>
написал:
> No Screensaver set, Screen seems to blank anyway after about ten
> minutes, no way to switch it off in Settings. When playing a video, even
> when the player is set to inhibit screensaver during playback it blanks
> anyway. Don't know if this is related to this crash which occured after
> swiping the mouse to bring back the screen but it bugs the hell out of
> me so thought I i'd mention it anyway...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (852053).
> https://bugs.launchpad.net/bugs/849600
>
> Title:
> gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/849600/+subscriptions

-- 
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/849600

Title:
  gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  Opening a new bug because this seems to be the first Oneiric beta1
  instance of the bug. I run gnome-shell, and I was unable to log back
  in after the screen locked. Running gnome-shell --replace from a
  virtual terminal allowed me to unlock the screen. I don't believe it's
  a security issue because I still was required to enter a password to
  get back to my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.1.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Tue Sep 13 21:07:00 2011
  ExecutablePath: /usr/bin/gnome-screensaver
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe9827167a0:	mov    0x18(%rax),%rdi
   PC (0x7fe9827167a0) ok
   source "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known VMA region (needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-screensaver
  StacktraceTop:
   ?? () from /usr/lib/libgnome-desktop-3.so.2
   ?? () from /usr/lib/libgnome-desktop-3.so.2
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-screensaver crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/849600/+subscriptions


References