View previous topic :: View next topic |
Author |
Message |
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Fri Jan 03, 2003 9:19 pm Post subject: logging in with KDM restarts X |
|
|
I upgraded to Gentoo 1.4_rc1 from 1.2 this weekend, and now whenever I log in (any user, any WM) from kdm X restarts. What could be causing this? |
|
Back to top |
|
|
Lin_Matt Guru
Joined: 23 Jun 2002 Posts: 581 Location: TechWasteland (Mississippi)
|
Posted: Fri Jan 03, 2003 10:59 pm Post subject: |
|
|
Did you re-emerge your kde packages? You might wanna check your free hard drive space also. Last but not least, you can try logging in and immediately after X restarts check that user's ~/.xsession-errors file. /var/log/XFree86.0.log may also have some useful output...
HTH |
|
Back to top |
|
|
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Fri Jan 03, 2003 11:11 pm Post subject: |
|
|
I should have mentioned that I've compiled KDE (3.1_rc5) several times since then...
I have lots of free space on all my drives; .xsession_errors for one user has this:
Code: | No parent pixmap for child widget QLabel
No parent pixmap for child widget QLabel
DCOPServer up and running.
kcontrol: Initializing [various things]
Mutex destroy failure: Device or resource busy
Mutex destroy failure: Device or resource busy
mcop warning: user defined signal handler found for SIG_PIPE, overriding
KSMServer: SetAProc_loc: conn 0, prot=local, file=/tmp/.ICE-unix/19155
KSMServer::restoreSession
QFont::setPointSize: Point size <= 0 (-3)
kdesktop: Saver Engine disabled
mcop warning: user defined signal handler found for SIG_PIPE, overriding
No parent pixmap for child widget QViewportWidget
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (49,-4) are not possible
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (49,-4) are not possible
Got panel toplevel Panel
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42
Got panel toplevel ZoomButton
kdesktop: slotCompleted() m_hasExistingPos: 1
WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 14
Got panel toplevel QAlphaWidget
kcontrol: Found basegroup = Settings/
kcontrol: activate: Settings/System/kdm.desktop
kcontrol: Preview for desktop 0 done
kcontrol: activate: Settings/System/printmgr.desktop
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3/lib/libkdecore.so.4: undefined symbol: init_kcm_printmgr
kdecore (KLibLoader): WARNING: KLibrary: The library kcm_printmgr does not offer an init_kcm_printmgr function
kcontrol: Unable to load module using ComponentFactory! Falling back to old loader.
ASSERT: "!name.isEmpty()" in kinstance.cpp (55)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
is this the problem?
QToolBar::QToolBar main window cannot be 0.
sh: ypcat: command not found
Got panel toplevel ZoomButton
Got panel toplevel QAlphaWidget
No parent pixmap for child widget QRadioButton
No parent pixmap for child widget QRadioButton
No parent pixmap for child widget QRadioButton
No parent pixmap for child widget QLabel
completeShutdown: client kwin
completeShutdown: client kdesktop
completeShutdown: client kicker
SystemTrayApplet::~SystemTrayApplet
completeShutdown: client klipper
completeShutdown: client kalarmd
We killed all clients. We have now clients.count()=5
KSMServer::completeKilling clients.count()=5
KSMServer::completeKilling clients.count()=4
KSMServer::completeKilling clients.count()=3
KSMServer::completeKilling clients.count()=2
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 25 (X_SendEvent)
Resource id in failed request: 0x120005a
Serial number of failed request: 5454
Current serial number in output stream: 5850
KSMServer::completeKilling clients.count()=1
KSMServer::completeKilling clients.count()=0
Calling qApp->quit()
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
KLauncher: Exiting on signal 1
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
|
|
|
Back to top |
|
|
Lin_Matt Guru
Joined: 23 Jun 2002 Posts: 581 Location: TechWasteland (Mississippi)
|
Posted: Fri Jan 03, 2003 11:50 pm Post subject: |
|
|
Quote: |
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3/lib/libkdecore.so.4: undefined symbol: init_kcm_printmgr
kdecore (KLibLoader): WARNING: KLibrary: The library kcm_printmgr does not offer an init_kcm_printmgr function
|
This certainly does look like a fatal error to me... Also, if you have emerged kde 3.1*, it should be loading libs from /usr/kde/3.1/lib not /usr/kde/3/lib. Might wanna check your PATH.... |
|
Back to top |
|
|
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Sat Jan 04, 2003 12:13 am Post subject: |
|
|
I don't know what path the xdm init script would use, but nothing in /etc/env.d has /usr/kde/3. I'll try re-emerging kdebase, since I cleaned out some old versions from /usr/kde recently. |
|
Back to top |
|
|
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Sat Jan 04, 2003 6:19 am Post subject: |
|
|
emerging kdebase didn't help, and I'm not sure how old that .xsession-errors was - I can't get anything to make output like that now. /var/log/kdm.log doesn't show anything interesting when the problem happens; where else can I find information about this? |
|
Back to top |
|
|
Lin_Matt Guru
Joined: 23 Jun 2002 Posts: 581 Location: TechWasteland (Mississippi)
|
Posted: Sat Jan 04, 2003 6:37 pm Post subject: |
|
|
hmmmmmm.... Have you tried using GDM instead? Or better yet, Ctrl-Alt-F1 to a terminal, run "/etc/init.d/xdm stop" and then run startx from the command line. I'm guessing you setup kde as your default, so kde should start from there.
You can also try stopping xdm and clearing out your /tmp directory, but I have my doubts that it will do anything for ya.
BTW, what CFLAGS are you using? |
|
Back to top |
|
|
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Sat Jan 04, 2003 7:30 pm Post subject: |
|
|
I'm using startkde right now; I tried XDM but when I log in nothing happens.
CFLAGS="-march=athlon-tbird -m3dnow -O3 -pipe -fomit-frame-pointer" |
|
Back to top |
|
|
Lin_Matt Guru
Joined: 23 Jun 2002 Posts: 581 Location: TechWasteland (Mississippi)
|
Posted: Sun Jan 05, 2003 6:11 pm Post subject: |
|
|
What version of X are you running? I know there's been some problems in the past with X and some compiler flags, but newer ebuilds filter em out for ya automagically...
I'm not sure what else to check here... |
|
Back to top |
|
|
krogoth n00b
Joined: 15 Aug 2002 Posts: 38
|
Posted: Sun Jan 05, 2003 6:18 pm Post subject: |
|
|
4.2.1-r2... I'll try KDE 3.1 rc6. |
|
Back to top |
|
|
|