KDM-BIN Problems - PC-BSD Forums

THE JEW (RaVeN) · #1 07-15-2010, 02:52 AM

PROBLEM

KDM doesn't launch as expected and KDE specific apps seem "wonky."

Not quite sure what is going on here, but I thought I'd throw out a post. KDM doesn't launch any more.

The console tells me that:

Code:

kdm-bin[2411]: X server startup timeout, terminating
kdm-bin[2411]: X server for display :0 cannot be started, session disabled.

I noticed that I could

Code:

startx

and get a GUI. The console was complaining about kdm-bin, but

Code:

top

showed it running. I thought I'd kill it and start it again. However, when I

Code:

killall kdm-bin

up pops the kdm login.

This wouldn't be a real problem, but KDE apps seem particularly "finicky" after that. I can only launch Firefox but the Start Menu, not Konqueror. Konqueror produces the following error when tried from the command line:

Code:

konqueror: cannot connect to X server :0.0

Uninstalling and reinstalling via ports didn't fix the problem.

Currently running PC-BSD 8.1 BETA1

Any input greatly appreciated. The KDE bug report people, basically, said that they don't have a clue as PC-BSD seems to use a custom KDE implementation.

Fatmice · #2 07-15-2010, 02:59 AM

Is this an upgrade or a clean install?

THE JEW (RaVeN) · #3 07-15-2010, 03:27 AM

Clean install. Only upgrade done was a:

Code:

 portsnap update.

System Settings tells me that:

Quote:

Platform Version 4.4.4 (KDE 4.4.4)

Cheers.

Fatmice · #4 07-15-2010, 03:32 AM

head -50 /etc/ttys please.

THE JEW (RaVeN) · #5 07-16-2010, 10:54 PM

I was unaware of the mainframe history of ttys. Reference links at the bottom.

Code:

# head -50 /etc/ttys
#
# $FreeBSD: src/etc/etc.i386/ttys,v 1.10 2003/10/24 15:44:08 simokawa Exp $
#       @(#)ttys        5.1 (Berkeley) 4/17/89
#
# This file specifies various information about terminals on the system.
# It is used by several different programs.  Common entries for the
# various columns include:
#
# name  The name of the terminal device.
#
# getty The program to start running on the terminal.  Typically a
#       getty program, as the name implies.  Other common entries
#       include none, when no getty is needed, and xdm, to start the
#       X Window System.
#
# type The initial terminal type for this port.  For hardwired
#      terminal lines, this will contain the type of terminal used.
#      For virtual consoles, the correct type is typically cons25, but
#      vt220 will work better if you need interoperability with other
#      systems like Solaris or GNU/Linux.
#      Other common values include network for network connections on
#      pseudo-terminals, dialup for incoming modem ports, and unknown
#      when the terminal type cannot be predetermined.
#
# status Must be on or off.  If on, init will run the getty program on
#        the specified port.  If the word "secure" appears, this tty
#        allows root login.
#
# name  getty                           type    status          comments
#
# If console is marked "insecure", then init will ask for the root password
# when going to single-user mode.
console none                            unknown off secure
#
ttyv0   "/usr/libexec/getty Pc"         cons25  on  secure
# Virtual terminals
ttyv1   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv2   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv3   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv4   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv5   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv6   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv7   "/usr/libexec/getty Pc"         cons25  on  secure
ttyv8   "/usr/PCBSD/bin/pdm"                xterm   on  secure
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyd0   "/usr/libexec/getty std.9600"   dialup  off secure
ttyd1   "/usr/libexec/getty std.9600"   dialup  off secure
ttyd2   "/usr/libexec/getty std.9600"   dialup  off secure
ttyd3   "/usr/libexec/getty std.9600"   dialup  off secure

References

Man ttys
http://www.freebsd.org/cgi/man.cgi?q...SE&format=html

Handbook ttys
http://www.freebsd.org/doc/en/books/handbook/term.html

FreeBSD Forum example
http://forums.freebsd.org/showthread.php?t=15650

Wikipedia Overview
http://en.wikipedia.org/wiki/Computer_terminal
http://en.wikipedia.org/wiki/Serial_port

Fatmice · #6 07-16-2010, 11:42 PM

Okay, so this is telling me that kde is called when machine is boot up. You should already be in a KDE session after the machine is fully booted. Are you not?

THE JEW (RaVeN) · #7 07-18-2010, 12:30 AM

Fatmice, unless I type in something to start/kill KDE, the machine simply sits at the prompt.

QUESTIONS:

1. PC-BSD uses pf for its firewall configuration, correct?

For the

Code:

System Settings -> Network & Connectivity -> Firewall

that's just a GUI for pf, yes? If so, where is the config file?

My main problem with KDE4 being "flaky" is that I'd like to open some ports so I can setup port forwarding with my router.

EDIT:

Bah, does anyone have any links to threads in the networking section on pf? "pf" is shorter than the 3 letter minimum.

2. Any idea why KDE3.5 dependencies would interfere with KDE4? See below as to why I think that's happening.

INVESTIGATION ABOUT KDE

I did a bit more investigating.

Booting Sequence:

1. Begins to load code
2. Standard PC-BSD boot menu (PC-BSD auto chosen)
3. "PC-BSD loading system" graphic screen pops up. I push "any" key to see code
4. I notice the following:

Code:

starting dbus
.kde4/share/config/kdeblobals: No such file or directory
starting hald

I find this odd. I'll check this out later (see # 9)

5. Code finishes loading and logon at ttyv0 is shown. This is where KDE usually begins to do its thing
6. Error message:

Code:

kdm-bin[2411]: X server startup timeout, terminating
kdm-bin[2411]: X server for display :0 cannot be started, session disabled.

7. I can do two things here.

A. Launch kdm

Code:

kdm

This brings me to a KDE3.5 login manager. Logging in gives me a KDE3.5 desktop

B. Kill what KDE is running and get the standard PC-BSD login menu

Code:

killall kdm-bin

Logging into this gives me the standard KDE4 PC-BSD desktop

9. Going back to the error message of not being able to find the kde4 file, I look for it.

Code:

cd .kde4/share/config/
ee kdeglobals

I notice this line at the top:

Code:

[$Version]
update_info=socks.upd:kde3.0/r1,kded.upd:kde3.0,kaccel.upd:kde3.3/r1,kwin.upd:kde3.2Xinerama,mouse_cursor_theme.upd:kde3.4.99

I remember that I installed this desktopbsd tool pack earlier:

http://www.freshports.org/sysutils/desktopbsd-tools/

Further research shows that DesktopBSD last used KDE3.5.

http://distrowatch.com/table.php?dis...ion=desktopbsd

Quote:

kdebase 3.5.10

for 1.7

Since PC-BSD uses kde4, I think there's a conflict somewhere.

Fatmice · #8 07-18-2010, 03:51 AM

Originally Posted by THE JEW (RaVeN)

that's just a GUI for pf, yes? If so, where is the config file?

Bah, does anyone have any links to threads in the networking section on pf? "pf" is shorter than the 3 letter minimum.

/etc/pf.conf

Originally Posted by THE JEW (RaVeN)

starting dbus
.kde4/share/config/kdeblobals: No such file or directory
starting hald

This is odd. Now is that real typo or your typo?

KDE should be on ttyv8 which is Alt+F9. The fact that it is not there means it dies while parsing start-up files.

I doubt the DesktopBSD tool is the problem.

THE JEW (RaVeN) · #9 07-18-2010, 12:08 PM

Originally Posted by Fatmice

/etc/pf.conf

Thanks!

Quote:

This is odd. Now is that real typo or your typo?

KDE should be on ttyv8 which is Alt+F9. The fact that it is not there means it dies while parsing start-up files.

I doubt the DesktopBSD tool is the problem.

Bah, my cursed fingers betray me.

kdeblobals = kdeglobals

The "PCBSD loading system" splash screen is on Alt+F9. However, that splash screen sits there forever unless I hit the the any key to get to the prompt. Usually I just Alt+F5, log in, killall kdm-bin, log into the kde4 kdm, and then start using kde4.

I didn't think installing DesktopBSD Tools would be a problem either. However, I seem to remember this KDE "fun" starting after installing them from ports. If the firewall GUI worked, I'd just consider it another form of login security lol.

I'll try editing the pf config so that it suits my needs. Thanks for your help, Fatmice. If you, or anyone else, has any ideas I'm open to entertaining them.

List of "wonky" KDE bits so far:
-Firewall GUI
-Konqueror doesn't launch from menu
-kde4 kdm login manager

Fatmice · #10 07-18-2010, 08:36 PM

Well, you can test.

1/All newly created profile will have default configurations which ought to work. You can make a backup of your files, delete your user and create a new one. See if that helps.

2/Didn't help? Remove the DesktopBSD tool. Since you got it from ports, go back to the port directory and do make deinstall. It will balk that it is required some some other things.