[Bug 354894] [NEW] kdm fails to start properly / nvidia 180 / intrepid / kde 4.2.1 and .2
James
james.ellis at gmail.com
Sat Apr 4 01:39:35 UTC 2009
Public bug reported:
Binary package hint: kdm
KDM is failing to start properly (I think) since KDE was updated to
4.2.1
On startup, the X cursor appears for about 5 seconds but then the screen
reverts to low resolution on the main notebook flat panel, with a blue
garbled artifact at the top and what looks to be a GTK style dialogue
advertising that 'Ubuntu' could not detect graphic settings and is
working in low graphics mode.
Hitting OK in this dialogue proceeds to another screen with a few
choices, I choose the first one "Run Ubuntu in low graphics mode for
just this session" and then I get a message which states "Your display
will restart in a minute, please wait" and an OK button. I wait, nothing
happens, I wait again and nothing happens. Clicking the OK button then
gets me to shell prompt.
I can log in at the shell and get a bash prompt. Sometimes after
entering my username (no password), the display restarts and both
screens appear with a KDM greeter. At other times I have to restart KDM
in order to get the greeter screen.
This has occured on every startup since installation of KDE 4.2.1 (4.2.0
worked fine). Nvidia drivers 173, 177 and 180 (beta) all show the same
problem.
System:
* Dual screens via twinview
* dell xps 1330
* kubuntu 8.10
* kde 4.2.2 installed
/var/log/kdm.log.1:
-------------------------
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-24-xen i686 Ubuntu
Current Operating System: Linux riba 2.6.27-13-generic #1 SMP Thu Feb 26 07:26:43 UTC 2009 i686
Build Date: 26 March 2009 03:47:28PM
xorg-server 2:1.5.2-2ubuntu3.1+ppa2 (buildd at rothera.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Sat Apr 4 11:49:25 2009
(==) Using config file: "/etc/X11/xorg.conf"
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-24-xen i686 Ubuntu
Current Operating System: Linux riba 2.6.27-13-generic #1 SMP Thu Feb 26 07:26:43 UTC 2009 i686
Build Date: 26 March 2009 03:47:28PM
xorg-server 2:1.5.2-2ubuntu3.1+ppa2 (buildd at rothera.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Sat Apr 4 11:50:52 2009
(==) Using config file: "/etc/X11/xorg.conf"
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
/etc/gdm/failsafeXServer: line 124: /var/log/gdm/failsafe.log: No such file or directory
Warning: Cannot write to /var/log/gdm/failsafe.log
xinit /etc/gdm/failsafeXinit /etc/X11/xorg.conf.failsafe -- /usr/bin/X -br -once -config /etc/X11/xorg.conf.failsafe -logfile /var/log/Xorg.failsafe.log
X: warning; process set to priority -1 instead of requested priority 0
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-24-xen i686 Ubuntu
Current Operating System: Linux riba 2.6.27-13-generic #1 SMP Thu Feb 26 07:26:43 UTC 2009 i686
Build Date: 26 March 2009 03:47:28PM
xorg-server 2:1.5.2-2ubuntu3.1+ppa2 (buildd at rothera.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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.failsafe.log", Time: Sat Apr 4 11:51:12 2009
(++) Using config file: "/etc/X11/xorg.conf.failsafe"
error setting MTRR (base = 0xfb000000, size = 0x00e00000, type = 1) Invalid argument (22)
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
/etc/gdm/failsafeXServer: line 124: /var/log/gdm/failsafe.log: No such file or directory
Warning: Cannot write to /var/log/gdm/failsafe.log
xinit /etc/gdm/failsafeXinit /etc/X11/xorg.conf.failsafe -- /usr/bin/X -br -once -config /etc/X11/xorg.conf.failsafe -logfile /var/log/Xorg.failsafe.log
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
xinit: Server error.
/etc/gdm/failsafeXinit: line 209: /etc/init.d/gdm: No such file or directory
waiting for X server to shut down error setting MTRR (base = 0xfb000000,
size = 0x00e00000, type = 1) Invalid argument (22)
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-24-xen i686 Ubuntu
Current Operating System: Linux riba 2.6.27-13-generic #1 SMP Thu Feb 26 07:26:43 UTC 2009 i686
Build Date: 26 March 2009 03:47:28PM
xorg-server 2:1.5.2-2ubuntu3.1+ppa2 (buildd at rothera.buildd)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Sat Apr 4 11:51:39 2009
(==) Using config file: "/etc/X11/xorg.conf"
---------------------------
nvidia card:
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1)
Subsystem: Dell Device 0209
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
Region 5: I/O ports at ef00 [size=128]
[virtual] Expansion ROM at fc000000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information <?>
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nvidia
** Affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
--
kdm fails to start properly / nvidia 180 / intrepid / kde 4.2.1 and .2
https://bugs.launchpad.net/bugs/354894
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
More information about the kubuntu-bugs
mailing list