Gnome Display Manager major error?
GDM is giving me error saying "Oh No something went wrong"
I have just installed nvidia drivers from the website and am using intel for display(it wasnt working with nvidia) and bumblebee.
systemctl status gdm.service gives:
Failed to give slave programs access to the display.
Note: I am using 64 bit system
Graphics card : Nvidia GT555M with Optimus Technology
Startx is working fine
Last edited by harshsahil48 (2014-02-15 14:47:07)
Try to start gdm and then provide /var/log/Xorg.0.log. And maybe a gdm log (don't know where that is) -> /var/log/... ?
Similar Messages
-
Gnome-Shell logs in as Gnome Display Manager
Hello,
My gnome-shell decided to crap out on me after working perfectly for the past few days. It wouldn't boot into the session even with extensions off. I tried everything(removing old configuration files, setting an autostart on Gnome-shell in ~/.config/autostart. Now my Gnome-shell starts but it logs in as Gnome Display Manager. Terminals do not start up(they come up and dissapear). I can't log in to XFCE anymore as a fallback because GDM autostarts into itself. I tried switching display managers to slim but it errors starting in there also.
This behavior happened after a symlinked a file but I'm not sure which. The page I was browsing it on was on my other user.
Thanks, I am really bummed that I can't even get into my XFCE session right now and this GDM as user is nearly unuseable.
Edit: https://bbs.archlinux.org/viewtopic.php?id=118651
#3 is the post I followed, will try to remove the sym link and see what happens.
Last edited by 6msj (2011-10-26 18:55:36)Looks like removing the sym link did it, but now my previews are screwed up.
http://dl.dropbox.com/u/11400324/Screen … 0%3A09.png -
Display SXMB_MONI XML errors in Solution Manager (CEN)
Hello All,
Requirement is to display the XML error messages in SXMB_MONI in our Solution Manager (CEN)? Could you please let me know the major steps that would be involved on the same?
Please share your thoughts!
Thank You,
AntarpreetMy apologies not reading it properly....
Solution manager also usess the same concepts of the CCMS as we do it in XI, so you can setup the XI envinorment details in solution manager and try to capture the alerts....
Here are the Steps:
Prereq:
All Satellite systems connected from Solution Manager on the "Transaction SMSY" screen.
Prepare RFC connections between Solution Manager and Satellite systems for data collection ( RZ20 Data collection RFCs)
Steps:
1. Register "SAPCCMSR" and "SAPCCM4.X" on Sattilite Systems to report ABAP and Java stacks in local systems and report to Solution manager System
2. On Solution Manager System ( Acting as Central System) configure CCMS monitoring sets fromRZ20.
3. RZ21 --> configure CCMS pings alert monitoring.
all info with step by step guide avalible from Solution Manager configuration guides and http://service.sap.com/rkt
( This ref from solution manager forum)
check this link also:
http://www.scribd.com/doc/7858198/Solution-Manager-SAP-NW2004S-Monitoring-Setup-Guide-SP12 -
I installed gnome-cups-manager from TUR: [staging]
The install went fine. I can't find the cups-manager anywhere in
the menus. I then tried as su
# /opt/gnome/bin/gnome-cups-manager
/opt/gnome/bin/gnome-cups-manager: error while loading shared libraries: liblinc.so.1: cannot open shared object file: No such file or directory
iI don't know how to fix this
Thanks
dkKind of bad news now, from the looks of it, it won't work with the new gtk or the new gnome or something else that is new on my system, as it won't compile. I will look around for patches and if anyone else can figure out how to get it to work, it would be helpful.
Kritoke -
Gnome power manager upgrade - nvidia sedmentation error
I am trying to use the rolling update model properly and check the web page for issues before doing my pacman Syu.
I updated gnome-power-manager (along with the other available updates) today amd immediately noticed different behaviour.
The laptop (Dell Inspiron 1720) no longer suspended when I shut the lid. I still had the shutdown menu option but... when I used it it intermittently caused segmentation fault errors in nvidia settings and stuff like Google Earth no longer worked. My graphics card is geForce 8600M GT.
Downgrading the gnome-power-manager package restored everything to working order.
Maybe I did something daft, but I'd like to know if there is something else I should have checked or if there is a problem with this package. In the meantime I've added it to IgnorePkgi just pointing out that you can try to fix it yourself(until is fixed in our repo) by compiling gnome-power-manager using abs and add that option to the ./configure within PKGBUILD.
Last edited by wonder (2009-04-14 20:26:39) -
Gnome-power-manager no icon is being displayed
Hi.
I've recently upgraded to Gnome 2.18 from testing and noticed that gnome-power-manager does not display icon for my battery. I've chcecked options and everything seems to be fine. The process itself is also running. After couple of tests I've managed to show icon (killed process and re-run it with --no-daemon option) but after restart the icon was missing. Lshal shows my battery withouth any problem. Does anyone have similar problem??? My system is up-to-date, updated everyday.In this thread: http://bbs.archlinux.org/viewtopic.php?id=31193
JGC wrote:The gnome-power-manager thing is something that appeared after switching to the GtkStatusIcon API. This bug appears because gnome-power-manager starts before the notification area is placed on the panel.
This problem has been picked up already, so perhaps something's already being done before 2.18 goes to the extra repository. -
Qosmio F30: New nVidia display driver v156.72 VISTA fixes major errors
http://www.laptopvideo2go.com/forum/index.php?showtopic=15580
This driver fixes major errors in some of the new games Released recently
Works on F30,G30 With nVidia Geforce Go 7600
Download from
HereThanks for this notification.
This website is already known to me and I have noticed this new graphic driver version.
Its really an option to the original nVidia GPU drivers which are usually designed only for the desktop PC graphic cards.
But the drivers from the www.laptopvideo2go.com site run on the notebooks too. -
I am new to Arch. I have installed Arch, X, Mate (as the DE) and Lightdm as the display manager. Lightdm will only start in X, with the sudo lightdm command. From there, you can get into Mate.
Mate seems to work just fine. However, it would be nice to be able to boot successfully to a display manager and then into a desktop environment.
Before Lightdm, I had installed gdm with xfce. Gdm starts up properly but will not properly start either xfce or Mate. Gdm goes to a screen that is akin to the login screen but with nothing else. I just tried slim, which will not start up, either on boot up or from x.
I am not sure what to post for logs on this. In any event, my computer is an old Dell Dimension 2400, with a pentium 4 processor, intel graphics and 2 gb of memory. I am not sure what log would be helpful here but, if someone could help me with my issue, it would be appreciated.
My x-0-greeter.log reads:
** (process:290): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_shell_parse_argv: assertion `command_line != NULL' failed
** (lightdm-gtk-greeter:331): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
** (lightdm-gtk-greeter:331): WARNING **: Failed to load user image: Failed to open file '/home/allen/.face': Permission denied
** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
(lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
That seems to include some errors. The x-0.log reads:
X.Org X Server 1.14.2
Release Date: 2013-06-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.9.7-1-ARCH i686
Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
Build Date: 01 July 2013 10:52:25AM
Current version of pixman: 0.30.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) AIGLX: Suspending AIGLX clients for VT switch
setversion 1.4 failed
The lightdm.log reads:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=532
[+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using Xephyr for X servers
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Adding default seat
[+0.00s] DEBUG: Starting seat
[+0.00s] DEBUG: Starting new display for greeter
[+0.00s] DEBUG: Starting local X display
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Activating VT 7
[+0.03s] DEBUG: Logging to /var/log/lightdm/x-2.log
[+0.03s] DEBUG: Writing X server authority to /run/lightdm/root/:2
[+0.03s] DEBUG: Launching X Server
[+0.03s] DEBUG: Launching process 536: /usr/bin/Xephyr :2 -auth /run/lightdm/root/:2 -nolisten tcp vt7 -novtswitch
[+0.06s] DEBUG: Waiting for ready signal from X server :2
[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
The log from slim reads:
slim: waiting for X server to begin accepting connections.
slim: pam_authentication(): Authentication failure
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
The xorg.0.log reads:
[ 6.928]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 6.928] X Protocol Version 11, Revision 0
[ 6.928] Build Operating System: Linux 3.9.7-1-ARCH i686
[ 6.928] Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
[ 6.929] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
[ 6.929] Build Date: 01 July 2013 10:52:25AM
[ 6.929]
[ 6.929] Current version of pixman: 0.30.0
[ 6.929] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.929] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.929] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
[ 6.958] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 6.978] (==) No Layout section. Using the first Screen section.
[ 6.978] (==) No screen section available. Using defaults.
[ 6.978] (**) |-->Screen "Default Screen Section" (0)
[ 6.978] (**) | |-->Monitor "<default monitor>"
[ 6.985] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 6.985] (==) Automatically adding devices
[ 6.985] (==) Automatically enabling devices
[ 6.985] (==) Automatically adding GPU devices
[ 7.000] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 7.000] Entry deleted from font path.
[ 7.000] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 7.000] Entry deleted from font path.
[ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 7.000] Entry deleted from font path.
[ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 7.000] Entry deleted from font path.
[ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 7.000] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 7.000] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.000] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.005] (II) Loader magic: 0x8258620
[ 7.005] (II) Module ABI versions:
[ 7.005] X.Org ANSI C Emulation: 0.4
[ 7.005] X.Org Video Driver: 14.1
[ 7.005] X.Org XInput driver : 19.1
[ 7.005] X.Org Server Extension : 7.0
[ 7.006] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.007] (--) PCI:*(0:0:2:0) 8086:2562:1028:0160 rev 1, Mem @ 0xe8000000/134217728, 0xfeb80000/524288
[ 7.008] Initializing built-in extension Generic Event Extension
[ 7.008] Initializing built-in extension SHAPE
[ 7.008] Initializing built-in extension MIT-SHM
[ 7.008] Initializing built-in extension XInputExtension
[ 7.008] Initializing built-in extension XTEST
[ 7.008] Initializing built-in extension BIG-REQUESTS
[ 7.008] Initializing built-in extension SYNC
[ 7.008] Initializing built-in extension XKEYBOARD
[ 7.008] Initializing built-in extension XC-MISC
[ 7.008] Initializing built-in extension SECURITY
[ 7.008] Initializing built-in extension XINERAMA
[ 7.008] Initializing built-in extension XFIXES
[ 7.008] Initializing built-in extension RENDER
[ 7.008] Initializing built-in extension RANDR
[ 7.008] Initializing built-in extension COMPOSITE
[ 7.008] Initializing built-in extension DAMAGE
[ 7.008] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.008] Initializing built-in extension DOUBLE-BUFFER
[ 7.008] Initializing built-in extension RECORD
[ 7.008] Initializing built-in extension DPMS
[ 7.008] Initializing built-in extension X-Resource
[ 7.008] Initializing built-in extension XVideo
[ 7.008] Initializing built-in extension XVideo-MotionCompensation
[ 7.008] Initializing built-in extension XFree86-VidModeExtension
[ 7.008] Initializing built-in extension XFree86-DGA
[ 7.008] Initializing built-in extension XFree86-DRI
[ 7.008] Initializing built-in extension DRI2
[ 7.008] (II) LoadModule: "glx"
[ 7.027] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 7.042] (II) Module glx: vendor="X.Org Foundation"
[ 7.042] compiled for 1.14.2, module version = 1.0.0
[ 7.042] ABI class: X.Org Server Extension, version 7.0
[ 7.042] (==) AIGLX enabled
[ 7.042] Loading extension GLX
[ 7.042] (==) Matched intel as autoconfigured driver 0
[ 7.042] (==) Matched intel as autoconfigured driver 1
[ 7.042] (==) Matched vesa as autoconfigured driver 2
[ 7.042] (==) Matched modesetting as autoconfigured driver 3
[ 7.043] (==) Matched fbdev as autoconfigured driver 4
[ 7.043] (==) Assigned the driver to the xf86ConfigLayout
[ 7.043] (II) LoadModule: "intel"
[ 7.044] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 7.098] (II) Module intel: vendor="X.Org Foundation"
[ 7.098] compiled for 1.14.2, module version = 2.21.12
[ 7.098] Module class: X.Org Video Driver
[ 7.098] ABI class: X.Org Video Driver, version 14.1
[ 7.098] (II) LoadModule: "vesa"
[ 7.098] (WW) Warning, couldn't open module vesa
[ 7.098] (II) UnloadModule: "vesa"
[ 7.098] (II) Unloading vesa
[ 7.098] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 7.098] (II) LoadModule: "modesetting"
[ 7.099] (WW) Warning, couldn't open module modesetting
[ 7.099] (II) UnloadModule: "modesetting"
[ 7.099] (II) Unloading modesetting
[ 7.099] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 7.099] (II) LoadModule: "fbdev"
[ 7.099] (WW) Warning, couldn't open module fbdev
[ 7.099] (II) UnloadModule: "fbdev"
[ 7.099] (II) Unloading fbdev
[ 7.099] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 7.099] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
HD Graphics 4600, Iris(TM) Pro Graphics 5200,
Haswell CRW Server (GT1), Haswell CRW Server (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, ValleyView PO board
[ 7.101] (++) using VT number 7
[ 7.101] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 7.101] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 7.101] (==) intel(0): RGB weight 888
[ 7.101] (==) intel(0): Default visual is TrueColor
[ 7.101] (--) intel(0): Integrated Graphics Chipset: Intel(R) 845G
[ 7.101] (**) intel(0): Relaxed fencing disabled
[ 7.102] (**) intel(0): Wait on SwapBuffers? enabled
[ 7.102] (**) intel(0): Triple buffering? enabled
[ 7.102] (**) intel(0): Framebuffer tiled
[ 7.102] (**) intel(0): Pixmaps tiled
[ 7.102] (**) intel(0): 3D buffers tiled
[ 7.102] (**) intel(0): SwapBuffers wait enabled
[ 7.103] (==) intel(0): video overlay key set to 0x101fe
[ 7.303] (II) intel(0): Output VGA1 has no monitor section
[ 7.443] (II) intel(0): EDID for output VGA1
[ 7.443] (II) intel(0): Manufacturer: DEL Model: 3142 Serial#: 894121267
[ 7.443] (II) intel(0): Year: 1999 Week: 29
[ 7.443] (II) intel(0): EDID Version: 1.2
[ 7.443] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 7.443] (II) intel(0): Sync: Separate
[ 7.443] (II) intel(0): Max Image Size [cm]: horiz.: 32 vert.: 24
[ 7.443] (II) intel(0): Gamma: 2.27
[ 7.443] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 7.443] (II) intel(0): First detailed timing is preferred mode
[ 7.443] (II) intel(0): redX: 0.645 redY: 0.321 greenX: 0.285 greenY: 0.600
[ 7.443] (II) intel(0): blueX: 0.142 blueY: 0.057 whiteX: 0.283 whiteY: 0.298
[ 7.443] (II) intel(0): Supported established timings:
[ 7.443] (II) intel(0): 720x400@70Hz
[ 7.443] (II) intel(0): 640x480@60Hz
[ 7.443] (II) intel(0): 640x480@75Hz
[ 7.443] (II) intel(0): 800x600@60Hz
[ 7.443] (II) intel(0): 800x600@75Hz
[ 7.443] (II) intel(0): 1024x768@60Hz
[ 7.443] (II) intel(0): 1024x768@75Hz
[ 7.443] (II) intel(0): 1280x1024@75Hz
[ 7.443] (II) intel(0): Manufacturer's mask: 0
[ 7.443] (II) intel(0): Supported standard timings:
[ 7.443] (II) intel(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881
[ 7.443] (II) intel(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
[ 7.443] (II) intel(0): #2: hsize: 640 vsize 480 refresh: 85 vid: 22833
[ 7.443] (II) intel(0): Supported detailed timing:
[ 7.443] (II) intel(0): clock: 94.5 MHz Image Size: 306 x 230 mm
[ 7.444] (II) intel(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0
[ 7.444] (II) intel(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0
[ 7.444] (II) intel(0): Serial No: 5322DE5K5379
[ 7.444] (II) intel(0): Monitor name: DELL M780
[ 7.444] (II) intel(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 85 kHz,
[ 7.444] (II) intel(0): EDID (in hex):
[ 7.444] (II) intel(0): 00ffffffffffff0010ac423133354b35
[ 7.444] (II) intel(0): 1d0901020820187fea1269a552499924
[ 7.444] (II) intel(0): 0e484ca54b0061594559315901010101
[ 7.444] (II) intel(0): 010101010101ea240060410028303060
[ 7.444] (II) intel(0): 130032e61000001e000000ff00353332
[ 7.444] (II) intel(0): 324445354b353337390a000000fc0044
[ 7.444] (II) intel(0): 454c4c204d3738300a202020000000fd
[ 7.444] (II) intel(0): 0032a01e55ff000a20202020202000e3
[ 7.444] (II) intel(0): Printing probed modes for output VGA1
[ 7.444] (II) intel(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 7.444] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 7.444] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 7.444] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 7.444] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 7.444] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 7.444] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 7.444] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 7.444] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 7.444] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.444] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 7.444] (II) intel(0): Output VGA1 connected
[ 7.444] (II) intel(0): Using exact sizes for initial modes
[ 7.444] (II) intel(0): Output VGA1 using initial mode 1024x768
[ 7.444] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 7.444] (II) intel(0): Kernel page flipping support detected, enabling
[ 7.444] (==) intel(0): DPI set to (96, 96)
[ 7.444] (II) Loading sub module "fb"
[ 7.444] (II) LoadModule: "fb"
[ 7.444] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7.458] (II) Module fb: vendor="X.Org Foundation"
[ 7.458] compiled for 1.14.2, module version = 1.0.0
[ 7.458] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.458] (II) Loading sub module "dri2"
[ 7.458] (II) LoadModule: "dri2"
[ 7.458] (II) Module "dri2" already built-in
[ 7.458] (==) Depth 24 pixmap format is 32 bpp
[ 7.466] (II) intel(0): [DRI2] Setup complete
[ 7.466] (II) intel(0): [DRI2] DRI driver: i915
[ 7.466] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
[ 7.478] (II) UXA(0): Driver registered support for the following operations:
[ 7.478] (II) solid
[ 7.478] (II) copy
[ 7.478] (II) composite (RENDER acceleration)
[ 7.478] (II) put_image
[ 7.478] (II) get_image
[ 7.478] (==) intel(0): Backing store disabled
[ 7.478] (==) intel(0): Silken mouse enabled
[ 7.478] (II) intel(0): Initializing HW Cursor
[ 7.478] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 7.480] (==) intel(0): DPMS enabled
[ 7.480] (==) intel(0): Intel XvMC decoder disabled
[ 7.480] (II) intel(0): Set up overlay video
[ 7.480] (II) intel(0): direct rendering: DRI2 Enabled
[ 7.480] (==) intel(0): hotplug detection: "enabled"
[ 7.540] (--) RandR disabled
[ 7.689] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 7.689] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 7.689] (II) AIGLX: enabled GLX_ARB_create_context
[ 7.689] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 7.689] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 7.689] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 7.689] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 7.689] (II) AIGLX: Loaded and initialized i915
[ 7.689] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 7.690] (II) intel(0): Setting screen physical size to 270 x 203
[ 7.924] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 7.924] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.924] (II) LoadModule: "evdev"
[ 7.925] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 7.943] (II) Module evdev: vendor="X.Org Foundation"
[ 7.943] compiled for 1.14.2, module version = 2.8.1
[ 7.943] Module class: X.Org XInput Driver
[ 7.943] ABI class: X.Org XInput driver, version 19.1
[ 7.943] (II) Using input driver 'evdev' for 'Power Button'
[ 7.943] (**) Power Button: always reports core events
[ 7.943] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 7.943] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.943] (--) evdev: Power Button: Found keys
[ 7.943] (II) evdev: Power Button: Configuring as keyboard
[ 7.943] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 7.943] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 7.943] (**) Option "xkb_rules" "evdev"
[ 7.943] (**) Option "xkb_model" "pc104"
[ 7.943] (**) Option "xkb_layout" "us"
[ 7.980] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 7.980] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.980] (II) Using input driver 'evdev' for 'Power Button'
[ 7.980] (**) Power Button: always reports core events
[ 7.980] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 7.980] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.980] (--) evdev: Power Button: Found keys
[ 7.980] (II) evdev: Power Button: Configuring as keyboard
[ 7.981] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
[ 7.981] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 7.981] (**) Option "xkb_rules" "evdev"
[ 7.981] (**) Option "xkb_model" "pc104"
[ 7.981] (**) Option "xkb_layout" "us"
[ 7.981] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 7.982] (II) config/udev: Adding input device OM (/dev/input/event1)
[ 7.982] (**) OM: Applying InputClass "evdev pointer catchall"
[ 7.982] (II) Using input driver 'evdev' for 'OM'
[ 7.982] (**) OM: always reports core events
[ 7.982] (**) evdev: OM: Device: "/dev/input/event1"
[ 7.982] (--) evdev: OM: Vendor 0x4f3 Product 0x232
[ 7.982] (--) evdev: OM: Found 3 mouse buttons
[ 7.982] (--) evdev: OM: Found scroll wheel(s)
[ 7.982] (--) evdev: OM: Found relative axes
[ 7.982] (--) evdev: OM: Found x and y relative axes
[ 7.982] (II) evdev: OM: Configuring as mouse
[ 7.982] (II) evdev: OM: Adding scrollwheel support
[ 7.982] (**) evdev: OM: YAxisMapping: buttons 4 and 5
[ 7.982] (**) evdev: OM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 7.982] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input1/event1"
[ 7.982] (II) XINPUT: Adding extended input device "OM" (type: MOUSE, id 8)
[ 7.982] (II) evdev: OM: initialized for relative axes.
[ 7.983] (**) OM: (accel) keeping acceleration scheme 1
[ 7.983] (**) OM: (accel) acceleration profile 0
[ 7.983] (**) OM: (accel) acceleration factor: 2.000
[ 7.983] (**) OM: (accel) acceleration threshold: 4
[ 7.983] (II) config/udev: Adding input device OM (/dev/input/mouse0)
[ 7.983] (II) No input driver specified, ignoring this device.
[ 7.983] (II) This device may have been added with another device file.
[ 7.984] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 7.984] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.984] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 7.984] (**) AT Translated Set 2 keyboard: always reports core events
[ 7.984] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 7.984] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 7.984] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 7.984] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 7.984] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 7.984] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 7.984] (**) Option "xkb_rules" "evdev"
[ 7.984] (**) Option "xkb_model" "pc104"
[ 7.984] (**) Option "xkb_layout" "us"
[ 7.985] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 7.985] (II) No input driver specified, ignoring this device.
[ 7.985] (II) This device may have been added with another device file.
[ 29.826] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 53.275] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 53.426] (II) intel(0): EDID vendor "DEL", prod id 12610
[ 53.427] (II) intel(0): Using EDID range info for horizontal sync
[ 53.427] (II) intel(0): Using EDID range info for vertical refresh
[ 53.427] (II) intel(0): Printing DDC gathered Modelines:
[ 53.427] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 53.427] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 53.427] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 53.427] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 53.427] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 53.427] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 53.427] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 53.427] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 53.427] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 53.427] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 53.427] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 53.433] setversion 1.4 failed
[ 57.450] (II) intel(0): EDID vendor "DEL", prod id 12610
[ 57.450] (II) intel(0): Using hsync ranges from config file
[ 57.450] (II) intel(0): Using vrefresh ranges from config file
[ 57.450] (II) intel(0): Printing DDC gathered Modelines:
[ 57.450] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 57.450] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 57.450] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 57.450] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 57.450] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 57.450] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 57.450] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 57.450] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 57.450] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 57.450] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 57.450] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 57.590] (II) intel(0): EDID vendor "DEL", prod id 12610
[ 57.590] (II) intel(0): Using hsync ranges from config file
[ 57.590] (II) intel(0): Using vrefresh ranges from config file
[ 57.590] (II) intel(0): Printing DDC gathered Modelines:
[ 57.590] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 57.590] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 57.590] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 57.590] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 57.590] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 57.590] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 57.590] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 57.590] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 57.590] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 57.590] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 57.590] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 57.763] (II) intel(0): EDID vendor "DEL", prod id 12610
[ 57.763] (II) intel(0): Using hsync ranges from config file
[ 57.763] (II) intel(0): Using vrefresh ranges from config file
[ 57.763] (II) intel(0): Printing DDC gathered Modelines:
[ 57.763] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 57.763] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 57.763] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 57.763] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 57.763] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 57.763] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 57.763] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 57.763] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 57.763] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 57.763] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 57.763] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
[ 57.903] (II) intel(0): EDID vendor "DEL", prod id 12610
[ 57.903] (II) intel(0): Using hsync ranges from config file
[ 57.903] (II) intel(0): Using vrefresh ranges from config file
[ 57.903] (II) intel(0): Printing DDC gathered Modelines:
[ 57.903] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
[ 57.903] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 57.903] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 57.903] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 57.903] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 57.903] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 57.903] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 57.903] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 57.903] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 57.903] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
[ 57.903] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
No doubt I have missed the pertinent log.
Last edited by nef131 (2013-07-31 12:47:23)Oxyd,
The current state of things, after removing gdm, slim and reinstalling lightdm, is that nothing has changed. In any event, below is the results of pacman -Qs lightdm:
[allen@archbox ~]$ pacman -Qs lightdm
local/lightdm 1:1.6.0-5 (lightdm)
A lightweight display manager
local/lightdm-gtk3-greeter 1:1.6.0-1
GTK+ greeter for LightDM
[allen@archbox ~]$
The result of is cat /etc/lightdm/lightdm.conf:
[allen@archbox ~]$ cat /etc/lightdm/lightdm.conf
# General configuration
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# xsessions-directory = Directory to find X sessions
# remote-sessions-directory = Directory to find remote sessions
# xgreeters-directory = Directory to find X greeters
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#log-directory=/var/log/lightdm
run-directory=/run/lightdm
#cache-directory=/var/cache/lightdm
#xsessions-directory=/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#xgreeters-directory=/usr/share/xgreeters
# Seat defaults
# type = Seat type (xlocal, xremote)
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# exit-on-failure = True if the daemon should exit if this seat fails
[SeatDefaults]
#type=xlocal
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#greeter-session=example-gtk-gnome
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-guest=true
#guest-session=UNIMPLEMENTED
session-wrapper=/etc/lightdm/xsession
#display-setup-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-session=UNIMPLEMENTED
pam-service=lightdm-autologin
#exit-on-failure=false
# Seat configuration
# Each seat must start with "Seat:".
# Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
#[Seat:0]
# XDMCP Server configuration
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
# it can be a word and the first 7 characters are used as the key.
[XDMCPServer]
#enabled=false
#port=177
#key=
# VNC Server configuration
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#width=1024
#height=768
#depth=8
The result of cat /etc/lightdm/lightdm-gtk-greeter.conf is :
[allen@archbox ~]$ cat /etc/lightdm/lightdm-gtk-greeter.conf
# background = Background file to use, either an image path or a color (e.g. #772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
# font-name = Font to use
# xft-antialias = Whether to antialias Xft fonts (true or false)
# xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
# xft-hintstyle = What degree of hinting to use (none, slight, medium, or full)
# xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
# show-language-selector (true or false)
# show-indicators = semi-colon ";" separated list of allowed indicator modules (e.g. libsoundmenu.so)
# show-clock (true or false)
# clock-format = strftime-format string, e.g. %H:%M
# keyboard = command to launch on-screen keyboard
[greeter]
#background=
#theme-name=
#icon-theme-name=
#font-name=
#xft-antialias=
#xft-dpi=
#xft-hintstyle=
#xft-rgba=
#show-language-selector=
#show-indicators=
#show-clock=
#clock-format=
#keyboard=
Cfr: "Did you test X following the Beginners' Guide?"
Yes. I tested X. I believe that I followed the Beginner's Guide to the letter. Of course, I am new to Arch, so it is possible I misunderstood something. I believe what I did was to enter the following command to install X: pacman -S xorg-server xorg-server-utils xorg-xinit and then, as provided in the guide, I installed mesa.
I have, per your suggestion, removed xorg-server-xephyr. I note, however, that the guide for installing lightdm indicates that the package should be installed initially, in order to test to see if lightdm works. In any event, removing it does not alter how the system starts up.
You are correct that I am starting the computer directly to lightdm - and not starting lightdm from X - but lightdm leaves a blank page, as I noted. I can click around on the blank page and stuff pops up. On looking at Oxyd's suggested outputs, I wonder if my problem is that nearly everything in the configuration file has been commented out. -
Weblogic Managed Server Error- JavaEE agent test failed in ODI
Hi All,
Please help wit the issue below !!
Versions: ODI 11.1.1 and Weblogic 11g Release1 10.3.3.
Server : Windows 2003 server ,32-bit OS.
->Able to connect the Standalone agent succesfully .
Issue : In Weblogic ,the admin server is connecting without error . But when i start the Managed server"odi_server1" we found the major error occuring while connecting to the Master Repository . Pasted below the Error log .
Please help!!
####<Mar 23, 2011 3:58:16 PM IST> <Error> <Deployer> <admin-3fqjbc1oo> <odi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1300876096336> <BEA-149231> <Unable to set the activation state to true for the application 'oraclediagent'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
KennyHi Kenny,
This error seems to indicate the credentials you've specified for the master repo are not working. Either ensure the login works at the repo, or rerun the installer and specify a set of known good credentials there.
Regards,
Robb Salzmann -
Cannot set resolution with gnome-display-properties
Hey all!
After full system update my external display does not get detected/recognized properly by gnome-display-properties
Though before upgrade it worked just fine!
Tried to downgrade hal and xorg-server but without any success.
Any ideas how to fix?
Thanks!I have the same problem. I do, like You, own a ASUS P4S8X motherboard and a MSI (Ti4800SE-VTD8X(MS-8900))videocard.
Because it was a brand new system i installed everything from scratch, so installed the MSI drivers for the videocard. Afterwards i thought i that it would be better to download the latest nvidia drivers. Since that time i have the same problem with the property settings of the videocard, Ghost Recon (original and supplied version) does not work anymore as goes for liveupdate of msi.
There is a solution but i think it is CRAP. You have to uninstall nvidia drivers and reinstall the original msi drivers.... bla bla bla... Why is it that there are a lot of known errors with msi/nvidia drivers in conjuntion with the liveupdate, supplied games and with the settings?? I would like to see a (driver)update from msi which is for mortals. I'm not the hacking and phreaking guy, and so are more. I have spent a fortune on this card so MSI get started!!!!!! -
Gnome-network-manager problems
Hello all,
I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
However, when I reboot under those settings, I can't connect to anything, including ethernet.
Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
Thank you very much for any help.
Matt[matt@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"3KR98"
Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:76 Missed beacon:31
[matt@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
Interrupt:22 Base address:0x6800
eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:76 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific? -
Logitech F310 Gamepad only works with Display Manager [SOLVED]
So I bought a couple Logitech F310 gamepads, for, well, gaming, and I had a hell of a time trying to get my games to respond to them. I run XMonad, and boot it directly via xinit. On a whim, I tried activating gdm and logging into a gnome session, and presto, my controllers worked. I got a bare bones xmonad session file going, and eventually switched over to lxdm just for testing purposes, and the controllers would continue to work like a charm.
Now, I would prefer to not to have to use a display manager, though it's not a deal breaker (though they seem to introduce other problems -- now systemd hangs on shutdown when I'm using lxdm). Still, I'm curious as to what kind of an effect the mere activation of a display manager could have on the system which would cause it to properly recognize the gamepads. To be clear, without a display manager, the pads are detected, are correctly listed in /dev/input. and I can even run jstest and see that they respond well (though they seem oddly configured), but games will not recognize their existence, and so they're effectively useless.
Any help would be appreciated.
Last edited by alex404 (2014-04-08 21:16:07)It would appear that this is related to this post as well:
https://bbs.archlinux.org/viewtopic.php?pid=1368721
Here's a list of processes that run when I'm using LXDM, versus XMonad:
kworker/u16:8
kworker/6:2
irq/46-iwlwifi
login
xinit
irq/44-iwlwifi
kworker/2:2
kworker/2:3
lxdm-binary
lxdm-session
gnome-keyring-d
pulseaudio
rtkit-daemon
gconf-helper
gconfd-2
The modules being listed are the same. Definitely an odd problem. I'm just resorting to using LXDM for now, even though I'd rather not. -
Gnome-power-manager update causes backlight to power off frequently
After the upgrade to gnome-power-manager 2.26.1-1 today, my laptop screen backlight is being powered off constantly, after only about 1 minute. It's not the screen blanking, but the backlight going off. It comes right back up if I do anything on the keyboard.
My power management preferences haven't changed though. They're all set (as before the upgrade) to never dim the display and never put the display to sleep. So why is the backlight going off anyway?
Also, this pretty distinctly seems to have to do with Gnome and not X. If I leave the laptop for an extended period at the GDM login screen, the backlight is never powered off. The problem only develops after I have logged into Gnome.
Thanks for any help.
Last edited by cb474 (2009-04-23 07:14:55)Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
xset -dpms
This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
xset -dpms
This is working.
You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
Hope that helps.
Last edited by cb474 (2009-04-24 08:26:23) -
Solaris 10 gnome session manager crashes on login
There are two Solaris 10 servers at work that I cannot log into. At the login screen I choose Options --> Session --> Java Desktop System, Release 3
and then try to log in. I get the following error message:
"The GNOME session manager (process XXXXX) has crashed due to a fatal error. (Segmentation Fault). When you close this dialog, all applications will close and your session will exit. Please save all your files before closing this dialog."
I was able to find one post on this error using google. It said that the user solved this problem by editing the LD_LIBRARY_PATH variable by moving /usr/local/lib to the beginning of the line. This didn't fix my problem. I logged in via ssh and double checked that the LD_LIBRARY_PATH change had saved.
Other people can log into the server just fine. Just not me. I even completely wiped my home directory. Anybody know where I can find a fix for this?Just discovered that if one of the working users logs completely out, they cannot log back in. So this error affects everybody.
-
System-config-display, gnome-display-properties - inconsistent R5 U5 64bit
Hi all,
I have OEL Rel 5 U5 (64-bit) installed and running on an IBM x3200 which has Radeon integrated graphics, with a IBM ThinkVision LCD monitor (1280x1024 max)
Problem I have is eventhough system-config-display lets me select 1280x1024 I can't actually get it to switch. Upon log-off/log-in, reboot, restart, etc... it still returns to 1024x768 mode.
Running gnome-display-properties only gives me a choice of 1024x768, 800x600, or 640x480.
I've also tried xrandr and trying to force it to 1280x1024 but it tells me I only have the 3 choices given by gnome-display-properties.
My xorg.conf file is configured with 1280x1024, 1024x768, and 800x600 modes, so I'm baffled at where gnome-display-properties and xrandr are getting their mode choices...
Can anyone shed some light on this?Based on Xorg log I'm guessing the monitor driver just will not support the higher res and apparently that's where 'gnome-display-properties' gets its info regardless of what I try in Xorg.conf.
I'll see if I can manipulate the monitor settings and see where that gets me...
I see the following in the log:
(II) RADEON(0): Monitor1 EDID data ---------------------------
(II) RADEON(0): Manufacturer: IBM Model: 29a Serial#: 16843009
(II) RADEON(0): Year: 2003 Week: 16
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Digital Display Input
(II) RADEON(0): Max Image Size [cm]: horiz.: 30 vert.: 23
(II) RADEON(0): Gamma: 1.00
(II) RADEON(0): No DPMS capabilities specified
(II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEON(0): Default color space is primary color space
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
(II) RADEON(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
(II) RADEON(0): Supported VESA Video Modes:
(II) RADEON(0): 720x400@70Hz
(II) RADEON(0): 640x480@60Hz
(II) RADEON(0): 640x480@72Hz
(II) RADEON(0): 640x480@75Hz
(II) RADEON(0): 800x600@56Hz
(II) RADEON(0): 800x600@60Hz
(II) RADEON(0): 800x600@72Hz
(II) RADEON(0): 800x600@75Hz
(II) RADEON(0): 1024x768@60Hz
(II) RADEON(0): 1024x768@70Hz
(II) RADEON(0): 1024x768@75Hz
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported Future Video Modes:
(II) RADEON(0): #0: hsize: 1024 vsize 768 refresh: 60 vid: 16481
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 65.0 MHz Image Size: 300 x 225 mm
(II) RADEON(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0
(II) RADEON(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
(II) RADEON(0): Serial No: Reserved
(II) RADEON(0): Monitor name: IBM RSA2
(II) RADEON(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 70 kHz, PixClock max 110 MHz
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): DFP table revision: 3
(II) RADEON(0): Panel infos found from DDC detailed: 1024x768
(II) RADEON(0): Valid Mode from Detailed timing table: 1024x768
(II) RADEON(0): Valid Mode from standard timing table: 1024x768
(II) RADEON(0): Valid Mode from established timing table: 1024x768
(II) RADEON(0): Valid Mode from established timing table: 1024x768
(II) RADEON(0): Valid Mode from established timing table: 1024x768
(II) RADEON(0): Valid Mode from established timing table: 800x600
(II) RADEON(0): Valid Mode from established timing table: 800x600
(II) RADEON(0): Valid Mode from established timing table: 800x600
(II) RADEON(0): Valid Mode from established timing table: 800x600
(II) RADEON(0): Valid Mode from established timing table: 640x480
(II) RADEON(0): Valid Mode from established timing table: 640x480
(II) RADEON(0): Valid Mode from established timing table: 640x480
(II) RADEON(0): Total of 12 mode(s) found.
Here's video info from lspci:
0a:04.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00 [VGA controller])
Subsystem: IBM Unknown device 0325
Flags: bus master, stepping, fast Back2Back, medium devsel, latency 66, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at 6000 [size=256]
Memory at d0800000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at d0820000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Xorg.conf:
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "Monitor"
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
ModelName "LCD Panel 1280x1024"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.5 - 64.0
VertRefresh 56.0 - 65.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "radeon"
Option "AccelMethod" "UXA"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
EndSection
Maybe you are looking for
-
Hi. I need to find out how I can make a file in documents so that I can paste my C.V in there as I am signing up to a job site and as you know it says browse a file to find the cv. But I cannot see how I can create a file so then I paste the C.V the
-
Spotlight "disappearing"? New since update to 10.4.5
I'm experiencing a major Spotlight error since updating to 10.4.5 through Software Update. In my menu bar, I have a few items. From left-to-right: an e-mail monitor, a SMART status monitor, my Fast User Switching icon, the clock, then Spotlight. When
-
Are there pros and cons to assembling a graphic on a page in InDesign vs photoshop? I'm creating a 50 page book, and I often run into not knowing whether something should be done first in photoshop or indesign. There are times when I think the entire
-
Not Able to see SAP systems in List of Available SAP Systems for Crystal R
Hi All, We have installed Crystal reports 2008 and SAP integration KIt client software on my machine. I am trying to create Crystal reports based on the BI query and I could see SAP Connections in the 'Create new connections list' but not able to see
-
Why doesn't flash player work even though I've downloaded it and enabled it?
flash player was already download to my computer when i bought it. it has been working fine for about a year but it suddenly stopped working about 4 weeks ago? I've tried searching up whats happening but nearly all the websites say it would be becaus