[Bug 1085706] Re: pam_ecryptfs: seteuid error

2017-02-12 Thread PJO
Also present in Linux Mint 18.1

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1085706

Title:
  pam_ecryptfs: seteuid error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 545397] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in exit()

2010-04-03 Thread PJO
Made some progress on this.

My initial install of 10.04 beta 1 -- the first Lucid version I tried --
wouldn't do 1920x1200 video with an ATEN CS1734B KVM switch in place.
The switch, although it supports monitor resolutions well in excess of
this, prevents the detection of some monitor parameters and the display
defaults to a lower resolution. This seems to have been the cause of
some problems, for me anyway.

Here http://ohioloco.ubuntuforums.org/showthread.php?t=1435151 there's a
reference to the driver being unable to

> identify the correct EDID info,

which reminded me of this.

First time around I ended up installing with a directly connected
monitor (hardware drivers installed ok) and then getting xorg.conf
configured to use 1920x1200 to eliminate black borders caused by the
system seeing a lower resolution display. It was because I was having
difficulty getting1920x1200 that I did a clean install with the monitor
directly attached.

Once I had the xorg.conf file figured out (or borrowed to be precise;
see blog posts) I didn't think I'd need to unplug from the switch again.
I thought I could just reuse that xorg.conf file. Wrong! And
furthermore, I couldn't install the drivers until after I'd done a
system update (not the case last time as far as I remember). Doing it
the other way around led to a crash, and this time the drivers were
installed automatically after the system update (nice).

http://wombatdiet.net/2010/03/25/first-impressions-ubuntu-10-04/
http://wombatdiet.net/2010/03/19/fedora-12-and-the-aten-cs1734b/

I haven't been able to get xorg.conf adjusted for use with Fedora 12 yet
(with a Samsung 2443NW); the Ubuntu config doesn't work.

ATEN have previously blamed my monitor (a different one) for Ubuntu not
getting the resolution right, but I now know and I've sent them xorg log
files made with and without the switch in place, that what's detected is
very different with the switch in use. Until today however, that didn't
cause any crashes.

Bottom line is, I think, not to use a KVM switch during installation,
just in case.

Message for Canonical: I would gladly give preference to Ubuntu
certified hardware.

-- 
gnome-screensaver-gl-helper crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/545397
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 545397] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in exit()

2010-04-03 Thread PJO
NOTE ERRONEOUS # OF ARGUMENTS ABOVE

and for the latest driver:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 914, in 
get_handlers
inst = obj(backend)
  File "/usr/share/jockey/handlers/fglrx.py", line 16, in __init__
raise SystemError, 'does not currently work with X.org 1.7'
SystemError: does not currently work with X.org 1.7

jockey.log attached

** Attachment added: "jockey.log"
   http://launchpadlibrarian.net/42998618/jockey.log

-- 
gnome-screensaver-gl-helper crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/545397
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 545397] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in exit()

2010-04-03 Thread PJO
Got a crash when trying to load Nvidia drivers for a Gigabyte
motherboard with 630i chipset. Worked on original 10.04 beta install but
not now on a reinstallation. Tried both drivers offered

2010-04-03 15:42:56,513 DEBUG: Instantiated Handler subclass 
__builtin__.NvidiaDriverCurrent from name NvidiaDriverCurrent
2010-04-03 15:42:56,524 DEBUG: NVIDIA accelerated graphics driver availability 
undetermined, adding to pool
2010-04-03 15:42:56,525 DEBUG: Could not instantiate Handler subclass 
__builtin__.NvidiaDriverBase from name NvidiaDriverBase
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 914, in 
get_handlers
inst = obj(backend)
TypeError: __init__() takes exactly 3 arguments (2 given)
2010-04-03 15:42:56,536 WARNING: modinfo for module nvidia_173 failed: ERROR: 
modinfo: could not find module nvidia_173

-- 
gnome-screensaver-gl-helper crashed with SIGSEGV in exit()
https://bugs.launchpad.net/bugs/545397
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs