| Author |
Message |
|
jonny bravo
|
Post subject: problems starting desktopbsd-tools Posted: Tue Nov 07, 2006 8:11 pm |
|
 |
| Newcomer |
|
|
Joined: Tue Nov 07, 2006 7:49 pm Posts: 3
|
I've just installed desktopbsd-tools from ports on freebsd 6.1. I seem to be having problems starting dbsd-pkgmgr, I get the screen for root login then nothing else.If I try to start it in konsole this is what I get Code: local# dbsd-pkgmgr --nofork Xlib: connection to ":0.0" refused by server Xlib: No protocol specified
kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified
kded: cannot connect to X server :0 DCOP aborting call from 'anonymous-12208' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. Xlib: connection to ":0.0" refused by server Xlib: No protocol specified
dbsd-pkgmgr: cannot connect to X server :0
Any help would greatly be appreciated Thanks.
|
|
 |
|
 |
|
kenji
|
Post subject: Posted: Tue Nov 07, 2006 9:07 pm |
|
 |
| Valued Contributor |
 |
|
|
Joined: Wed Jun 14, 2006 2:15 am Posts: 390 Location: Nevada, USA
|
|
Graphical programs cannot be started from the command line. Access it from the menu or run box (alt+F2)
_________________ Addicted to ports
DesktopBSD WIKI - FreeBSD Handbook
|
|
 |
|
 |
|
ezombie
|
Post subject: Posted: Tue Nov 07, 2006 10:27 pm |
|
 |
| Regular Visitor |
|
|
Joined: Fri Nov 03, 2006 8:11 pm Posts: 35
|
kenji wrote: Graphical programs cannot be started from the command line. Access it from the menu or run box (alt+F2)
They can too... but by default you can't run X programs from the console as root.
It should work fine from the console as a standard user by just typing dbsd-pkgmgr. KDE will add the --nofork and prompt for the root password.
I am also running FreeBSD 6.1-RELEASE with the desktopbsd-tools port. I am using the 1.1 version of the package.
|
|
 |
|
 |
|
jonny bravo
|
Post subject: Posted: Wed Nov 08, 2006 8:07 pm |
|
 |
| Newcomer |
|
|
Joined: Tue Nov 07, 2006 7:49 pm Posts: 3
|
|
I played with it a bit more last night. I think the problem is with the new default partition layout with /tmp. I reinstalled again with a diferent layout and now it's working. Thanks.
|
|
 |
|
 |
|
EvanC
|
Post subject: Posted: Mon Dec 11, 2006 1:04 am |
|
 |
| Regular Visitor |
|
|
Joined: Thu Dec 29, 2005 2:52 am Posts: 64 Location: Australia
|
Hi jonny bravo,
Could you throw more detail as to what you did to resolve this please
I have a similar issue, and believe that the /tmp partition is the issue. Did you move /tp to /var/tmp???
When you have a moment......
Cheers
Evanc
|
|
 |
|
 |
|
jonny bravo
|
Post subject: Posted: Mon Dec 11, 2006 6:23 pm |
|
 |
| Newcomer |
|
|
Joined: Tue Nov 07, 2006 7:49 pm Posts: 3
|
HI. EvanC,
I ended up reinstalling, but used the following layout. Quote: / /swap /var /usr /home This only temporarily fixed the problem. I think that there are still a few bugs with DesktopBSD-tools 1.1, and kde 3.5.4. I've noticed that after installing a few more ports the same problem came back. Im thinking its something to do with dcop or kdeinit. I get the login screen which is kdesu and then nothing, but if I logout and just run x I can start dbsd-pkgmgr
in extern and it works. Hopefully its something that will get resolved soon.
|
|
 |
|
 |
|
Oliver Herold
|
Post subject: Posted: Mon Dec 11, 2006 6:50 pm |
|
 |
| root |
 |
|
|
Joined: Mon May 08, 2006 12:27 pm Posts: 1663
|
Quote: I reinstalled again with a diferent layout and now it's working.
Maybe you have a bad sector on the harddrive and a different layout temporarily stopped the problem? I've seen similar things before.
I installed DesktopBSD on several machines without any problem and foremost with a tmp partition. Of course KDE is always good for some nasty problems. But why there aren't many more people suffering the same problem? People in PC-BSD or plain FreeBSD with KDE are using DesktopBSD tools too, with many more different partition layouts.
_________________ ... my alma mater: UNIX
DesktopBSD Developer Blog
DesktopBSD wiki
|
|
 |
|
 |
|
EvanC
|
Post subject: Posted: Tue Dec 12, 2006 6:50 am |
|
 |
| Regular Visitor |
|
|
Joined: Thu Dec 29, 2005 2:52 am Posts: 64 Location: Australia
|
Hi there,
Thanks for the info jonny,
I am running FreeBSD6 current with the DBSD tools installed. KDESU worked flawlessly until I installed the DBSD-tools, and now I can not do several things which is a little frustrating. My symptoms are
1) Can not log on as root graphically. After editing kdmrc to allow root access, KDM seems to pass the info on, but I then get booted back to the KDM log on screen. Previously, you would edit only this file, but it appears there are further config files that are in play now. 2) KDEsu freezes after I enter the root password into the prompt and hit the button. I know this has something to do with access to the X server, but the commands below do not work. 3) The only way to get any graphical window with root permissions is the trusted sudo command, and this get a little tiresome to do each time as there is no tab completion when issuing the commands. 4) An external USB Seagate HD (300G) will not mount using the DBSD tools. It complains of an unknown filetype - but it is UFS. Even after ensuring that the devfs permissions are correct, and running fsck, it still will not allow me to mount as it does not recognise the filetype. I can mount this manually with the "-t ufs" flag. 5) I can only use KDE!! KDM will not allow me to jump into fluxbox, but throws me bag to the logon screen. Grrrr
Code: $ xhost +localhost $ su - enter password # DISPLAY=:0.0 # export DISPLAY
I once fixed a similar KDEsu issue by reinstalling two base components of KDE. KDElibs must be installed before KDEbase, but this error is not consistent with a faulty install, but more an overriding of permissions - which are refreshed at startup.
I was hoping that some of this was due to my /tmp partition, but alas I think there are deeper issues here. I will let you know if I find the resolution to this.
|
|
 |
|
 |
|
Hilti
|
Post subject: shut down Posted: Thu Mar 15, 2007 10:04 pm |
|
 |
| Newcomer |
|
|
Joined: Wed Mar 14, 2007 12:57 pm Posts: 1
|
I have a slightly different problem. The other day I wanted to play onlinepoker while using the program and suddenly my entire pc shut down. do you think that could have something to do with the prog?
Thx,
Hilti
|
|
 |
|
 |
|
masterofmind1969
|
Post subject: Posted: Fri Mar 23, 2007 11:42 pm |
|
 |
| Regular Visitor |
 |
|
|
Joined: Thu Jan 25, 2007 5:41 pm Posts: 33 Location: Toronto, Canada
|
|
wow I have the same problem after I installed desktopbsd tools. I thought I installed freebsd 6.2. My first time installing freebsd from scratch. Any ideas how to fix this error?
I do agree pcbsd users can use desktopbsd tools, but then i remember i started having problems after installing desktopbsd tools, geesh and I thought it pcbsd screwing up.
|
|
 |
|
 |
|
ramrod
|
Post subject: Posted: Sat Apr 14, 2007 9:30 pm |
|
 |
| Newcomer |
 |
|
|
Joined: Wed Feb 28, 2007 1:53 am Posts: 15 Location: USA
|
EvanC wrote: 4) An external USB Seagate HD (300G) will not mount using the DBSD tools. It complains of an unknown filetype - but it is UFS. Even after ensuring that the devfs permissions are correct, and running fsck, it still will not allow me to mount as it does not recognise the filetype. I can mount this manually with the "-t ufs" flag.
I believe you're wrong to blame Desktop Tools for that. I've done a bunch of upgrades and I remember reading one release note regarding one of the main KDE components(either kdelibs or kdebase) which mentioned something about the kioslave needing root privileges for mounting now, therefore it rendered the tray mounter applet useless. I always get errors now when trying to use it one way or another. It doesn't bother me all that much since I want my drives mounted under my designated mount points instead of /media, but I'd like to still be able to use it for quick mounting of CD/DVD. I also added my hard drives to /etc/fstab so I don't have to re-mount them at every boot. So in conclusion the blame gets spread between KDE "improvements" and the archaic nature of FreeBSD whose mount utility does not allow the 'user' option to be set, unlike in Linux.
|
|
 |
|
 |
|