Re: KDE login causing processes stuck in zfs wchan
2013/3/22 Daniel O'Connor > Hi, > I recently updated to KDE 4.9.5 and I've found that unless I disable > vfs.usermount (which stops gvfs from mounting) everything gets stuck in > [zfs] eventually. > > If you could produce ps axw & mount Maybe I could guess where's problem(s) lies. > This is running on.. > FreeBSD midget.dons.net.au 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #10 > r241435M: Thu Oct 11 15:03:22 CST 2012 > dar...@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET > amd64 > > Does anyone have a similar experience? > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Regards, Alexander Yerenkow ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
KDE login causing processes stuck in zfs wchan
Hi, I recently updated to KDE 4.9.5 and I've found that unless I disable vfs.usermount (which stops gvfs from mounting) everything gets stuck in [zfs] eventually. This is running on.. FreeBSD midget.dons.net.au 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #10 r241435M: Thu Oct 11 15:03:22 CST 2012 dar...@midget.dons.net.au:/usr/obj/usr/src/sys/MIDGET amd64 Does anyone have a similar experience? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Functional KDE desktop
On 18/03/2013, at 3:02, Eric S Pulley wrote: > I have it working fine here. I originally was using it on 9.0 then I > upgraded everything but that didn't work well for the KDE 4.8->4.9 > update in ports. Too many ports were split and moved around so I ended > up removing all ports and remaking them all. One big gotcha is make > sure you force a reconfigure on everything. > > My small nightmare was kdepim,kdepim-runtime and kdepimlibs > there are now two deferment types of PIM you can built the old "4.8 > style" and the new. Make sure you are consistent as these packages are > deps for many others. For a while I was still picking up settings for > the old style and it was breaking all over the place. Ugh I see. Any idea what these options are called? > If you want I can send you a list of all the stuff I have installed off > list and you can see if you're somehow missing important bits... I ended up nuking all of KDE/Qt and will try again. I also have had troubles with Python updates and a few things. I really like ports when installing but they are terrible when upgrading :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Functional KDE desktop
On Sun, 17 Mar 2013 22:35:02 +1030 "Daniel O'Connor" wrote: > Hi, > I am in the process of upgrading all the ports on a 9.1-PRERELEASE > system and I am having a lot of trouble building or running KDE 4.9.5. > > I couldn't build it due to x11/xsd not building (didn't make a > necessary header), or if I worked around that libkonq was not found > by cmake. If I manage to work around that I get an error dialogue > when logging in. > > In the end I gave up and installed packages (version 4.8.4) however > that does work as startkde gives.. [midget 22:10] ~ >env > PATH=$PATH:/usr/local/kde4/bin /usr/local/kde4/bin/startkde xset: > bad font path element (#12), possible causes are: Directory does not > exist or has wrong permissions Directory missing fonts.dir > Incorrect font server address or syntax > startkde: Starting up... > /usr/local/lib/libkdeui.so.7: Undefined symbol > "_ZN6Attica15ProviderManagerC1ERK6QFlagsINS0_12ProviderFlagEE" > startkde: Could not start kdeinit4. Check your installation. > > c++filt says this symbol is.. > Attica::ProviderManager::ProviderManager(QFlags > const&) > > Also, the startkde script does not set the pass so it never finds > kcheckrunning. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > I have it working fine here. I originally was using it on 9.0 then I upgraded everything but that didn't work well for the KDE 4.8->4.9 update in ports. Too many ports were split and moved around so I ended up removing all ports and remaking them all. One big gotcha is make sure you force a reconfigure on everything. My small nightmare was kdepim,kdepim-runtime and kdepimlibs there are now two deferment types of PIM you can built the old "4.8 style" and the new. Make sure you are consistent as these packages are deps for many others. For a while I was still picking up settings for the old style and it was breaking all over the place. If you want I can send you a list of all the stuff I have installed off list and you can see if you're somehow missing important bits... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Functional KDE desktop
Hi, I am in the process of upgrading all the ports on a 9.1-PRERELEASE system and I am having a lot of trouble building or running KDE 4.9.5. I couldn't build it due to x11/xsd not building (didn't make a necessary header), or if I worked around that libkonq was not found by cmake. If I manage to work around that I get an error dialogue when logging in. In the end I gave up and installed packages (version 4.8.4) however that does work as startkde gives.. [midget 22:10] ~ >env PATH=$PATH:/usr/local/kde4/bin /usr/local/kde4/bin/startkde xset: bad font path element (#12), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... /usr/local/lib/libkdeui.so.7: Undefined symbol "_ZN6Attica15ProviderManagerC1ERK6QFlagsINS0_12ProviderFlagEE" startkde: Could not start kdeinit4. Check your installation. c++filt says this symbol is.. Attica::ProviderManager::ProviderManager(QFlags const&) Also, the startkde script does not set the pass so it never finds kcheckrunning. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 8.2-RELEASE amd64 Gnome and KDE Slowness
I have installed FreeBSD 8.2-RELEASE amd64 on an Intel DG965WH mainboard with 6 GB RAM , 500GB Seagate HDD . When GNOME or KDE is used , their start times are very long as spanning many minutes , and opening of menus in applications such as Firefox , Dolphin , and their other programs are taking many minutes to just open the menu . Clicking any item , is also waiting many minutes to be activated . In that structure , it is not possible to use those desktop environments . After that , I have installed FreeBSD 8.2-RELEASE i386 on the same computer . The same actions are performed instantly . After that , I have installed PC-BSD 8.2-RELEASE amd64 . It is just like FreeBSD 8.2-RELEASE amd64 : Extremely slow . On FreeBSD 8.2-RELEASE amd64 , I have installed FluxBox . Its menus and their items are executed very fast . When a Gnome or KDE ( Dolphin , Ark , K3B ) program is executed from FluxBox , their menus are again very slow , whereas Firefox , Midnight Commander executions are very fast . This case is just related to FreeBSD 8.2-RELEASE amd64 . The other 64-bit operating systems are working very well . I have tested memory chips : There is no any error . I have used another 500 GB Seagate HDD : Effects are the same . I could neither be able to understand why this is happening , nor find a cure to this problem . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: various kde programs spin in a poll/read loop against their respective config files
Le Sat, 26 Sep 2009 15:25:17 +0200,
Christof Schulze a écrit :
> Hello everyone,
Hi,
> the discussion in -current and the behavior of my hard disk caused me
> to investigate. Whenever kde programs are run on this system, the
> hard disk will not spin down (even when excessive timeouts for syncs
> are in effect) So I ran truss against kwallet and plasma-desktop to
> find out they do the same thing:
>
> stat("/home/erika/.kde4/share/apps/kwallet",{ mode=drwx--
> ,inode=56314,size=3,blksize=4096 }) = 0 (0x0)
> Shouldn't this be handled by fam/gamin in order to avoid this
> overhead? While it does not produce notable load it prevents my
> processor from saving power as well as spinning down the disks.
KDE with fam is broken, according to
http://wiki.freebsd.org/KDE4
A work-around is to change the PollInterval in kdedrc
baby-jane:~$ less .kde4/share/config/kdedrc
[$Version]
update_info=kded.upd:kde3.0
[DirWatch]
PollInterval=60000
(IMHO, for KDE issues you should ask on the kde-free...@kde.org mailing
list).
See also this thread :
http://mail.kde.org/pipermail/kde-freebsd/2009-September/006447.html
Regards.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
various kde programs spin in a poll/read loop against their respective config files
Hello everyone,
the discussion in -current and the behavior of my hard disk caused me to
investigate. Whenever kde programs are run on this system, the hard disk
will not spin down (even when excessive timeouts for syncs are in effect)
So I ran truss against kwallet and plasma-desktop to find out they do the
same thing:
stat("/home/erika/.kde4/share/apps/kwallet",{ mode=drwx--
,inode=56314,size=3,blksize=4096 }) = 0 (0x0)
clock_gettime(4,{10454.430272035 }) = 0 (0x0)
clock_gettime(4,{10454.430363671 }) = 0 (0x0)
clock_gettime(4,{10454.430432397 }) = 0 (0x0)
clock_gettime(4,{10454.430516490 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
poll({3/POLLIN 9/POLLIN 8/POLLIN 5/POLLIN},4,0) = 0 (0x0)
clock_gettime(4,{10454.430734403 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
clock_gettime(4,{10454.430882473 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
poll({3/POLLIN 9/POLLIN 8/POLLIN 5/POLLIN},4,499) = 0 (0x0)
clock_gettime(4,{10454.939752100 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
clock_gettime(4,{10454.939905198 }) = 0 (0x0)
stat("/home/erika/.kde4/share/apps/kwallet",{ mode=drwx--
,inode=56314,size=3,blksize=4096 }) = 0 (0x0)
clock_gettime(4,{10454.940151049 }) = 0 (0x0)
clock_gettime(4,{10454.940242126 }) = 0 (0x0)
clock_gettime(4,{10454.940309456 }) = 0 (0x0)
clock_gettime(4,{10454.940392710 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
poll({3/POLLIN 9/POLLIN 8/POLLIN 5/POLLIN},4,0) = 0 (0x0)
clock_gettime(4,{10454.940612580 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
clock_gettime(4,{10454.940760929 }) = 0 (0x0)
read(8,0x808f9102c,4096) ERR#35 'Resource temporarily
unavailable'
Shouldn't this be handled by fam/gamin in order to avoid this overhead?
While it does not produce notable load it prevents my processor from
saving power as well as spinning down the disks. I will gladly provide
more information on this if necessary.
This is a FreeBSD 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Jul 7 04:56:00
CEST 2009
r...@ccschu935:/usr/obj/usr/src/sys/GENERIC amd64
system
Regards
Christof
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Linux/KDE and NFS locking on 7-stable
Hi all, I upgraded a FreeBSD fileserver last week from 7.0-stable to 7.2-stable and experience some weird problems now with Linux NFS clients. The Linux Clients mount their home directories via nfs. I usually use "nolock" on the client side, because file locking was always troublesome in the past. On the Clients the users run kde 3.5 or 4.2. After the update of the server kde 3.5 quit starting up (after logging in with kdm) on the spalsh screen and comes up with some kind of I/O error when writing to the home dir. At the same time the server complains about kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 Any other window manager (xfce, icewm, mwm, twm) seems to work fine. Playing around with locking, udp/tcp, rebooting some times then somehow magically made it work with kde 3.5 again (although I am using the same mount options in the and as I used before): mclane:/tank/home/gco /tank/home/ghf nfs nfsvers=3,rw,nolock,nordirplus 0 0 Turning locking on definitely does not work (tried it three times). rcp.lockd and rpc.statd are running on the server side, no further tuning done there. KDE 4.2 seems to have better, I have been able to get it working with locking turned on (but it refused to work without locking with the same errors as described above for kde 3.5). I find the whole situation a bit unattractive. Can anybody here give me a hint which combination of mount options should work for a FreeBSD Server running 7.2-stable and Linux clients running 2.6.29 and KDE3/4? I am not that much into performance here, I want a stable working solution. And why, after all, is KDE so picky about locking and nfs homedirs anyway? All other environments appear not to show these problems. cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem with KDM not passing to Xorg/KDE after login
Michael Nottebrock wrote: > On Tuesday, 17. July 2007, Kim Attree wrote: > >> Michael Nottebrock wrote: >> >>> On Monday, 16. July 2007, Kim Attree wrote: >>> >>>>> Mike, >>>>> >>>>> I had an 'exec bash' in my $HOME/.profile and removing this allowed me >>>>> to run ./Xsession default and push me into KDE ! >>>>> >>>> KDM though - still refuses to pass to KDE >>>> >>> I'm reluctant to give up on the shell angle already - can you try setting >>> your user's shell to /bin/csh or /bin/sh just for kicks and check if KDM >>> still doesn't work? >>> >> Mike, >> >> I set the user shell to /bin/sh in passwd using vipw, ran clone_root to >> propogate the change to the diskless root, rebooted the client and that >> did'nt work. >> >> It's really strange - I'm starting to think maybe its a PAM thing, since >> after I put in the user/pass in KDM, it sits for about 45-60 seconds >> before going back to the KDM login screen again. >> >> Any Thoughts ? >> > > Right now, I have run out of ideas - I have never run a diskless > configuration > myself and cannot easily make one here either, so I am probably missing a > good deal of possible failure modes here. You could try using some other > display manager for logging in instead, like xdm or gdm. > > Strange as it seems, XDM works fine.Although my users all prefer the look/feel of KDMBack to the drawing board. Thanks Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
On Tuesday, 17. July 2007, Kim Attree wrote: > Michael Nottebrock wrote: > > On Monday, 16. July 2007, Kim Attree wrote: > >>> Mike, > >>> > >>> I had an 'exec bash' in my $HOME/.profile and removing this allowed me > >>> to run ./Xsession default and push me into KDE ! > >> > >> KDM though - still refuses to pass to KDE > > > > I'm reluctant to give up on the shell angle already - can you try setting > > your user's shell to /bin/csh or /bin/sh just for kicks and check if KDM > > still doesn't work? > > Mike, > > I set the user shell to /bin/sh in passwd using vipw, ran clone_root to > propogate the change to the diskless root, rebooted the client and that > did'nt work. > > It's really strange - I'm starting to think maybe its a PAM thing, since > after I put in the user/pass in KDM, it sits for about 45-60 seconds > before going back to the KDM login screen again. > > Any Thoughts ? Right now, I have run out of ideas - I have never run a diskless configuration myself and cannot easily make one here either, so I am probably missing a good deal of possible failure modes here. You could try using some other display manager for logging in instead, like xdm or gdm. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
Michael Nottebrock wrote: > On Monday, 16. July 2007, Kim Attree wrote: > >>> Mike, >>> >>> I had an 'exec bash' in my $HOME/.profile and removing this allowed me >>> to run ./Xsession default and push me into KDE ! >>> >> KDM though - still refuses to pass to KDE >> > > I'm reluctant to give up on the shell angle already - can you try setting > your > user's shell to /bin/csh or /bin/sh just for kicks and check if KDM still > doesn't work? > > Mike, I set the user shell to /bin/sh in passwd using vipw, ran clone_root to propogate the change to the diskless root, rebooted the client and that did'nt work. It's really strange - I'm starting to think maybe its a PAM thing, since after I put in the user/pass in KDM, it sits for about 45-60 seconds before going back to the KDM login screen again. Any Thoughts ? Thanks Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 16. July 2007, Kim Attree wrote: > > Mike, > > > > I had an 'exec bash' in my $HOME/.profile and removing this allowed me > > to run ./Xsession default and push me into KDE ! > > > KDM though - still refuses to pass to KDE I'm reluctant to give up on the shell angle already - can you try setting your user's shell to /bin/csh or /bin/sh just for kicks and check if KDM still doesn't work? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
Kim Attree wrote: > Michael Nottebrock wrote: > >> On Monday, 16. July 2007, Kim Attree wrote: >> >> >>> Michael Nottebrock wrote: >>> >>> >>>> On Thursday, 12. July 2007, Kim Attree wrote: >>>> >>>> >>>>> Michael Nottebrock wrote: >>>>> >>>>> >>>>>> On Monday, 9. July 2007, Kim Attree wrote: >>>>>> >>>>>> >>>>>>> I made Root's $HOME point to /var/db (touched to make sure it's >>>>>>> writable on the diskless workstation - it is) and the KDM still >>>>>>> refuses to pass to Xorg/KDE. >>>>>>> >>>>>>> Any Other Ideas ??? >>>>>>> >>>>>>> >>>>>> Make sure you have a hostname set (in rc.conf or via dhcp) and >>>>>> "localhost" is resolvable. >>>>>> >>>>>> >>>>> Mike, >>>>> >>>>> I've checked rc.conf and the hostname is defined and a 'hostname' >>>>> command on the workstation confirms this. I've added a /etc/hosts file >>>>> on the workstation (through the /conf/default directory on diskless >>>>> server) with the following: >>>>> >>>>> 127.0.0.1 localhost >>>>> 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) >>>>> 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) >>>>> >>>>> confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM >>>>> still refuses to pass to Xorg. >>>>> >>>>> >>>> Just to make sure - you cannot launch any session type from kdm, not even >>>> failsafe? >>>> >>>> What happens if you try to run Xsession manually, i.e.: >>>> >>>> $ X & >>>> [switch back to VTY] >>>> $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default >>>> [switch back to X11] >>>> >>>> Does KDE start? If not, try running Xsession as above but with shell >>>> tracing enabled like >>>> >>>> $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default >>>> >>>> to see where it hangs/exits. >>>> >>>> >>>> Cheers, >>>> >>>> >>> Mike, >>> >>> Did what you asked: >>> >>> 1. Started background process of X as root >>> 2. Switched VTY's and ran the Xsession >>> >>> Result: KDE Ran as expected >>> >>> >>> Then as a normal user, left the Xorg process running in background as >>> root. Changed VTY, logged in as a normal user, ran the command, and also >>> with shell tracing. >>> >>> Both times just drops back to command prompt with no the following: >>> >>> >>> csc01$ sh -x /usr/local/share/config/kdm/Xsession default >>> + session=kde/Xsession >>> + [ -z ] >>> + exec /usr/local/bin/bash /usr/local/share/config/kdm/Xsession default >>> csc01$ >>> >>> >>> >> So as root Xsession works but as your user it does not, right? I suspect it >> might have something to do with your user's shell - for root, it's probably >> csh, whereas for your normal user it seems to be set to bash. >> >> You can try unsetting the SHELL environment variable or setting it to >> /bin/csh >> or /bin/sh before running Xsession as your normal user (or just temporarily >> change your shell altogether) and see if that fares any better. To debug >> Xsession with bash, try editing the Xsession script: >> >> Change the line >> >> [ -z "$BASH" ] && exec $SHELL $0 "$@" >> >> to >> >> [ -z "$BASH" ] && exec $SHELL -x $0 "$@" >> >> This should get you more debug output. >> >> Cheers, >> >> > Mike, > > I had an 'exec bash' in my $HOME/.profile and removing this allowed me > to run ./Xsession default and push me into KDE ! > > Thanks > > Kim Attree > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > KDM though - still refuses to pass to KDE :( Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
Michael Nottebrock wrote: > On Monday, 16. July 2007, Kim Attree wrote: > >> Michael Nottebrock wrote: >> >>> On Thursday, 12. July 2007, Kim Attree wrote: >>> >>>> Michael Nottebrock wrote: >>>> >>>>> On Monday, 9. July 2007, Kim Attree wrote: >>>>> >>>>>> I made Root's $HOME point to /var/db (touched to make sure it's >>>>>> writable on the diskless workstation - it is) and the KDM still >>>>>> refuses to pass to Xorg/KDE. >>>>>> >>>>>> Any Other Ideas ??? >>>>>> >>>>> Make sure you have a hostname set (in rc.conf or via dhcp) and >>>>> "localhost" is resolvable. >>>>> >>>> Mike, >>>> >>>> I've checked rc.conf and the hostname is defined and a 'hostname' >>>> command on the workstation confirms this. I've added a /etc/hosts file >>>> on the workstation (through the /conf/default directory on diskless >>>> server) with the following: >>>> >>>> 127.0.0.1 localhost >>>> 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) >>>> 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) >>>> >>>> confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM >>>> still refuses to pass to Xorg. >>>> >>> Just to make sure - you cannot launch any session type from kdm, not even >>> failsafe? >>> >>> What happens if you try to run Xsession manually, i.e.: >>> >>> $ X & >>> [switch back to VTY] >>> $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default >>> [switch back to X11] >>> >>> Does KDE start? If not, try running Xsession as above but with shell >>> tracing enabled like >>> >>> $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default >>> >>> to see where it hangs/exits. >>> >>> >>> Cheers, >>> >> Mike, >> >> Did what you asked: >> >> 1. Started background process of X as root >> 2. Switched VTY's and ran the Xsession >> >> Result: KDE Ran as expected >> >> >> Then as a normal user, left the Xorg process running in background as >> root. Changed VTY, logged in as a normal user, ran the command, and also >> with shell tracing. >> >> Both times just drops back to command prompt with no the following: >> >> >> csc01$ sh -x /usr/local/share/config/kdm/Xsession default >> + session=kde/Xsession >> + [ -z ] >> + exec /usr/local/bin/bash /usr/local/share/config/kdm/Xsession default >> csc01$ >> >> > > So as root Xsession works but as your user it does not, right? I suspect it > might have something to do with your user's shell - for root, it's probably > csh, whereas for your normal user it seems to be set to bash. > > You can try unsetting the SHELL environment variable or setting it to > /bin/csh > or /bin/sh before running Xsession as your normal user (or just temporarily > change your shell altogether) and see if that fares any better. To debug > Xsession with bash, try editing the Xsession script: > > Change the line > > [ -z "$BASH" ] && exec $SHELL $0 "$@" > > to > > [ -z "$BASH" ] && exec $SHELL -x $0 "$@" > > This should get you more debug output. > > Cheers, > Mike, I had an 'exec bash' in my $HOME/.profile and removing this allowed me to run ./Xsession default and push me into KDE ! Thanks Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 16. July 2007, Kim Attree wrote: > Michael Nottebrock wrote: > > On Thursday, 12. July 2007, Kim Attree wrote: > >> Michael Nottebrock wrote: > >>> On Monday, 9. July 2007, Kim Attree wrote: > >>>> I made Root's $HOME point to /var/db (touched to make sure it's > >>>> writable on the diskless workstation - it is) and the KDM still > >>>> refuses to pass to Xorg/KDE. > >>>> > >>>> Any Other Ideas ??? > >>> > >>> Make sure you have a hostname set (in rc.conf or via dhcp) and > >>> "localhost" is resolvable. > >> > >> Mike, > >> > >> I've checked rc.conf and the hostname is defined and a 'hostname' > >> command on the workstation confirms this. I've added a /etc/hosts file > >> on the workstation (through the /conf/default directory on diskless > >> server) with the following: > >> > >> 127.0.0.1 localhost > >> 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) > >> 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) > >> > >> confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM > >> still refuses to pass to Xorg. > > > > Just to make sure - you cannot launch any session type from kdm, not even > > failsafe? > > > > What happens if you try to run Xsession manually, i.e.: > > > > $ X & > > [switch back to VTY] > > $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default > > [switch back to X11] > > > > Does KDE start? If not, try running Xsession as above but with shell > > tracing enabled like > > > > $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default > > > > to see where it hangs/exits. > > > > > > Cheers, > > Mike, > > Did what you asked: > > 1. Started background process of X as root > 2. Switched VTY's and ran the Xsession > > Result: KDE Ran as expected > > > Then as a normal user, left the Xorg process running in background as > root. Changed VTY, logged in as a normal user, ran the command, and also > with shell tracing. > > Both times just drops back to command prompt with no the following: > > > csc01$ sh -x /usr/local/share/config/kdm/Xsession default > + session=kde/Xsession > + [ -z ] > + exec /usr/local/bin/bash /usr/local/share/config/kdm/Xsession default > csc01$ > So as root Xsession works but as your user it does not, right? I suspect it might have something to do with your user's shell - for root, it's probably csh, whereas for your normal user it seems to be set to bash. You can try unsetting the SHELL environment variable or setting it to /bin/csh or /bin/sh before running Xsession as your normal user (or just temporarily change your shell altogether) and see if that fares any better. To debug Xsession with bash, try editing the Xsession script: Change the line [ -z "$BASH" ] && exec $SHELL $0 "$@" to [ -z "$BASH" ] && exec $SHELL -x $0 "$@" This should get you more debug output. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
Michael Nottebrock wrote: > On Thursday, 12. July 2007, Kim Attree wrote: > >> Michael Nottebrock wrote: >> >>> On Monday, 9. July 2007, Kim Attree wrote: >>> >>>> I made Root's $HOME point to /var/db (touched to make sure it's writable >>>> on the diskless workstation - it is) and the KDM still refuses to pass >>>> to Xorg/KDE. >>>> >>>> Any Other Ideas ??? >>>> >>> Make sure you have a hostname set (in rc.conf or via dhcp) and >>> "localhost" is resolvable. >>> >> Mike, >> >> I've checked rc.conf and the hostname is defined and a 'hostname' >> command on the workstation confirms this. I've added a /etc/hosts file >> on the workstation (through the /conf/default directory on diskless >> server) with the following: >> >> 127.0.0.1 localhost >> 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) >> 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) >> >> confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM >> still refuses to pass to Xorg. >> > > Just to make sure - you cannot launch any session type from kdm, not even > failsafe? > > What happens if you try to run Xsession manually, i.e.: > > $ X & > [switch back to VTY] > $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default > [switch back to X11] > > Does KDE start? If not, try running Xsession as above but with shell tracing > enabled like > > $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default > > to see where it hangs/exits. > > > Cheers, > Mike, Did what you asked: 1. Started background process of X as root 2. Switched VTY's and ran the Xsession Result: KDE Ran as expected Then as a normal user, left the Xorg process running in background as root. Changed VTY, logged in as a normal user, ran the command, and also with shell tracing. Both times just drops back to command prompt with no the following: csc01$ sh -x /usr/local/share/config/kdm/Xsession default + session=kde/Xsession + [ -z ] + exec /usr/local/bin/bash /usr/local/share/config/kdm/Xsession default csc01$ Thanks Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
On Thursday, 12. July 2007, Kim Attree wrote: > Michael Nottebrock wrote: > > On Monday, 9. July 2007, Kim Attree wrote: > >> I made Root's $HOME point to /var/db (touched to make sure it's writable > >> on the diskless workstation - it is) and the KDM still refuses to pass > >> to Xorg/KDE. > >> > >> Any Other Ideas ??? > > > > Make sure you have a hostname set (in rc.conf or via dhcp) and > > "localhost" is resolvable. > > Mike, > > I've checked rc.conf and the hostname is defined and a 'hostname' > command on the workstation confirms this. I've added a /etc/hosts file > on the workstation (through the /conf/default directory on diskless > server) with the following: > > 127.0.0.1 localhost > 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) > 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) > > confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM > still refuses to pass to Xorg. Just to make sure - you cannot launch any session type from kdm, not even failsafe? What happens if you try to run Xsession manually, i.e.: $ X & [switch back to VTY] $ env DISPLAY=:0 /usr/local/share/config/kdm/Xsession default [switch back to X11] Does KDE start? If not, try running Xsession as above but with shell tracing enabled like $ env DISPLAY=:0 sh -x /usr/local/share/config/kdm/Xsession default to see where it hangs/exits. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
Michael Nottebrock wrote: > On Monday, 9. July 2007, Kim Attree wrote: > >> I made Root's $HOME point to /var/db (touched to make sure it's writable >> on the diskless workstation - it is) and the KDM still refuses to pass >> to Xorg/KDE. >> >> Any Other Ideas ??? >> > > Make sure you have a hostname set (in rc.conf or via dhcp) and "localhost" is > resolvable. > > Mike, I've checked rc.conf and the hostname is defined and a 'hostname' command on the workstation confirms this. I've added a /etc/hosts file on the workstation (through the /conf/default directory on diskless server) with the following: 127.0.0.1 localhost 196.31.157.162 diskless02.csc.jnb6.za.uu.net (server) 196.31.157.130 csc01.csc.jnb6.za.uu.net (workstation) confirmed that localhost resolves to 127.0.0.1 on the workstation. KDM still refuses to pass to Xorg. Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
On Monday, 9. July 2007, Kim Attree wrote: > I made Root's $HOME point to /var/db (touched to make sure it's writable > on the diskless workstation - it is) and the KDM still refuses to pass > to Xorg/KDE. > > Any Other Ideas ??? Make sure you have a hostname set (in rc.conf or via dhcp) and "localhost" is resolvable. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: This is a digitally signed message part.
Re: Problem with KDM not passing to Xorg/KDE after login
I made Root's $HOME point to /var/db (touched to make sure it's writable on the diskless workstation - it is) and the KDM still refuses to pass to Xorg/KDE. Any Other Ideas ??? Thanks Kim Attree Kim Attree wrote: > Danny, > > thought of that already, /root/.kde is symbolically linked to /var/.kde, > which has the contents of /root/.kde and is populated at boot. That > /var/.kde is root writable too... > > Thanks > > Kim Attree > > Danny Braniss wrote: > >> don't know if this is the problem, but usualy, in a diskless env. / is >> mountted read-only, and so ~(root) is /root which could be read-only, >> and so manythings break when trying to write,eg ~/.kde >> >> my 5c >> danny >> >> >> > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
Danny, thought of that already, /root/.kde is symbolically linked to /var/.kde, which has the contents of /root/.kde and is populated at boot. That /var/.kde is root writable too... Thanks Kim Attree Danny Braniss wrote: > don't know if this is the problem, but usualy, in a diskless env. / is > mountted read-only, and so ~(root) is /root which could be read-only, > and so manythings break when trying to write,eg ~/.kde > > my 5c > danny > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with KDM not passing to Xorg/KDE after login
Ait, I use a normal user to login into KDM, it's just run as root, well because you can't run KDM as a normal userI've disabled the ability to login as root on KDM as well Thanks Kim ait wrote: > I'm not an expert but it seems to me that KDM system won't let you > login as root ;) It's a security measure. Have you tried to login as > ordinary user? > > > > 2007/7/5, Kim Attree <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>>: > > Hey Guys, hoping you can help. > > I Have a FREEBSD 6.2-STABLE recently supped and compiled, which is a > diskless environment. The workstation I'm testing on is working fine, > Xorg 7.2 is running perfectly as is KDE (I start it up with startx > from > a user login). > > However, when I run KDM as root, and try to login as the same > user, KDM > sits for about a minute, and then just returns to the KDM login > screen. > I've gotten rid of the critical error messages I've found in > kdm-bin.log, and Xorg.log.0, but still KDM will not pass to KDE/X. > > Here are the excerpts from the logs (These log entries are only during > the login procedure, from when I press enter with a correct user/pass > until it returns to KDM). > > > (II) I810(0): [drm] removed 1 reserved context for kernel > (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xc43e7000 at > 0x28584000 > (WW) I810(0): Successfully set original devices > (WW) I810(0): Setting the original video mode instead of restoring >the saved state > (WW) I810(0): Extended BIOS function 0x5f05 failed. > (II) I810(0): BIOS call 0x5f05 not supported, setting refresh with > VBE 3 > method. > (II) I810(0): xf86UnbindGARTMemory: unbind key 18 > (II) I810(0): xf86UnbindGARTMemory: unbind key 10 > (II) I810(0): xf86UnbindGARTMemory: unbind key 11 > (II) I810(0): xf86UnbindGARTMemory: unbind key 13 > (II) I810(0): xf86UnbindGARTMemory: unbind key 12 > (II) I810(0): xf86UnbindGARTMemory: unbind key 14 > (II) I810(0): xf86UnbindGARTMemory: unbind key 15 > (II) I810(0): xf86UnbindGARTMemory: unbind key 16 > (II) I810(0): xf86UnbindGARTMemory: unbind key 17 > (WW) I810(0): Successfully set original devices (2) > FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, > should > be 1; fixing. > > > > X Window System Version 7.2.0 > Release Date: 22 January 2007 > X Protocol Version 11, Revision 0, Release 7.2 > Build Operating System: FreeBSD 6.2-STABLE i386 > Current Operating System: FreeBSD csc01.csc.jnb6.za.uu.net > <http://csc01.csc.jnb6.za.uu.net> 6.2-STABLE > FreeBSD 6.2-STABLE #8: Tue Apr 3 14:39:35 SAST 2007 > [EMAIL PROTECTED] > .csc.jnb6.za.uu.net:/usr/obj/usr/src/sys/GENERIC i386 > Build Date: 11 June 2007 >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: Wed Jul 4 15:14:21 2007 > (==) Using config file: "/etc/X11/xorg.conf" > /usr/local/share/config/kdm/Xservers: No such file or directory > FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, > should > be 1; fixing. > > > And the directory/FS Structure: > > / = NFS Mount to /diskless_root > /usr = NFS Mount to /usr > /home = NFS Read/Write mount to /home > /var = Memory filesystem populated at boot > /etc = Memory filesystem populated at boot > /tmp = NFS Read/Write mount to /netswap > > Thanks in advance, > > Kim Attree > UNIX Sysadmin > ___ > freebsd-stable@freebsd.org <mailto:freebsd-stable@freebsd.org> > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to " > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with KDM not passing to Xorg/KDE after login
Hey Guys, hoping you can help. I Have a FREEBSD 6.2-STABLE recently supped and compiled, which is a diskless environment. The workstation I'm testing on is working fine, Xorg 7.2 is running perfectly as is KDE (I start it up with startx from a user login). However, when I run KDM as root, and try to login as the same user, KDM sits for about a minute, and then just returns to the KDM login screen. I've gotten rid of the critical error messages I've found in kdm-bin.log, and Xorg.log.0, but still KDM will not pass to KDE/X. Here are the excerpts from the logs (These log entries are only during the login procedure, from when I press enter with a correct user/pass until it returns to KDM). (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xc43e7000 at 0x28584000 (WW) I810(0): Successfully set original devices (WW) I810(0): Setting the original video mode instead of restoring the saved state (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method. (II) I810(0): xf86UnbindGARTMemory: unbind key 18 (II) I810(0): xf86UnbindGARTMemory: unbind key 10 (II) I810(0): xf86UnbindGARTMemory: unbind key 11 (II) I810(0): xf86UnbindGARTMemory: unbind key 13 (II) I810(0): xf86UnbindGARTMemory: unbind key 12 (II) I810(0): xf86UnbindGARTMemory: unbind key 14 (II) I810(0): xf86UnbindGARTMemory: unbind key 15 (II) I810(0): xf86UnbindGARTMemory: unbind key 16 (II) I810(0): xf86UnbindGARTMemory: unbind key 17 (WW) I810(0): Successfully set original devices (2) FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD csc01.csc.jnb6.za.uu.net 6.2-STABLE FreeBSD 6.2-STABLE #8: Tue Apr 3 14:39:35 SAST 2007 [EMAIL PROTECTED] .csc.jnb6.za.uu.net:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 11 June 2007 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: Wed Jul 4 15:14:21 2007 (==) Using config file: "/etc/X11/xorg.conf" /usr/local/share/config/kdm/Xservers: No such file or directory FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. And the directory/FS Structure: / = NFS Mount to /diskless_root /usr = NFS Mount to /usr /home = NFS Read/Write mount to /home /var = Memory filesystem populated at boot /etc = Memory filesystem populated at boot /tmp = NFS Read/Write mount to /netswap Thanks in advance, Kim Attree UNIX Sysadmin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Mon, Apr 30, 2007 at 07:50:45PM +0200, Thomas Quinot wrote: > * Oliver Peter, 2007-04-26 : > > > > My problem is the same as Beni's. Splash screen appears and hangs. > > > I have to press power button to turn off and on my laptop. > > > Didn't try ctrl+alt+del though. > > > > I have the same problem with my 7.0-CURRENT (yesterday). > > If I can assist you testing or debugging drivers please drop me an > > e-mail. > > > > FreeBSD 7.0-CURRENT i386 with k3b-1.0_1 / hal-0.5.8.20070403_1 Thank you for your message, Thomas. > This looks similar to kern/112119, which is fixed by rev. 1.52 of > sys/dev/ata/atapi-cam.c, committed today on HEAD. Sorry for my late reply. Of course this works great for me, too. -- Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174 "Worker bees can leave. Even drones can fly away. The Queen is their slave." pgp7Pk5DgV9pa.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
* Oliver Peter, 2007-04-26 : > > My problem is the same as Beni's. Splash screen appears and hangs. > > I have to press power button to turn off and on my laptop. > > Didn't try ctrl+alt+del though. > > I have the same problem with my 7.0-CURRENT (yesterday). > If I can assist you testing or debugging drivers please drop me an > e-mail. > > FreeBSD 7.0-CURRENT i386 with k3b-1.0_1 / hal-0.5.8.20070403_1 This looks similar to kern/112119, which is fixed by rev. 1.52 of sys/dev/ata/atapi-cam.c, committed today on HEAD. Thomas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Hey, On Fri, Apr 20, 2007 at 09:43:01AM +0800, Ganbold wrote: > Michael Nottebrock wrote: > >On Wednesday, 18. April 2007, Beni wrote: > > > >>Hi List, > >> > >>I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my > >>whole system freezes when starting up k3b. I get the splash screen and > >>then > >>it all stops and a ctrl-alt-del is the only way out. > >> > > My problem is the same as Beni's. Splash screen appears and hangs. > I have to press power button to turn off and on my laptop. > Didn't try ctrl+alt+del though. I have the same problem with my 7.0-CURRENT (yesterday). If I can assist you testing or debugging drivers please drop me an e-mail. FreeBSD 7.0-CURRENT i386 with k3b-1.0_1 / hal-0.5.8.20070403_1 Bye Ollie -- Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174 "Worker bees can leave. Even drones can fly away. The Queen is their slave." pgpVcp2ChvVRV.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
Zoran Kolic said the following on 26.04.2007 17:24: >> Along with update all my system and kernel to 6.2-STABLE on Fri, Apr 6, >> I have this error message in dmesg output: >> acd0: DVDR at ata1-master UDMA33 >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 >> 0x01 >> And writing by k3b freeze ALL system, not only k3b. > > Beni confirmed that he could use command line and write a cd. That > post to mean that the problem is in k3b itself. Or not? > As for me, this is a atapi-cam problem, not k3b. (kern/112119) -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Mark Linimon said the following on 26.04.2007 10:56: -- > I believe that this problem is now in kern/112119, which I am trying to > attract developer attention to. Yes, thanks, Mark. -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
> Along with update all my system and kernel to 6.2-STABLE on Fri, Apr 6, > I have this error message in dmesg output: > acd0: DVDR at ata1-master UDMA33 > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 > 0x01 > And writing by k3b freeze ALL system, not only k3b. Beni confirmed that he could use command line and write a cd. That post to mean that the problem is in k3b itself. Or not? Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
I believe that this problem is now in kern/112119, which I am trying to attract developer attention to. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Beni said the following on 25.04.2007 22:22: > On Tuesday 24 April 2007 16:49:28 Zoran Kolic wrote: >>> This problem appear in my system after updating system and ports on >>> April, 06. >>> K3b hangs either after loading splash screen or after eject wrote media >>> from device. >> Aside that new atapi-cam.c is proven to work, I'd like to know if command >> line works or not? K3b needs cdrtools in background. What if you make iso >> file using mkisofs and burn it with cdrecord? Along with update all my system and kernel to 6.2-STABLE on Fri, Apr 6, I have this error message in dmesg output: acd0: DVDR at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 And writing by k3b freeze ALL system, not only k3b. Old kernel with atapi-cam.c 1.42.2.2 revision (beginning of March) works fine without any error messages or freezes. K3B, cdrecord, hal and others works without any visible problems. -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Tuesday 24 April 2007 16:49:28 Zoran Kolic wrote: > > This problem appear in my system after updating system and ports on > > April, 06. > > K3b hangs either after loading splash screen or after eject wrote media > > from device. > > Aside that new atapi-cam.c is proven to work, I'd like to know if command > line works or not? K3b needs cdrtools in background. What if you make iso > file using mkisofs and burn it with cdrecord? > > Zoran > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" I didn't try to make an iso, but blanking a cd-rw media with "cdrecord dev=5,0,0 blank=fast" an then writing to it with a "cdrecord -v dev=5,0,0 ubuntu-7.04-desktop-i386.iso" works without any problem. No system freeze at all. So I guess that leaves k3b having a problem... :-( Beni. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
As a data point, I was seeing the same problems, but reverting to atapi-cam.c rev 1.42.2.2 works here too. Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
> This problem appear in my system after updating system and ports on > April, 06. > K3b hangs either after loading splash screen or after eject wrote media > from device. Aside that new atapi-cam.c is proven to work, I'd like to know if command line works or not? K3b needs cdrtools in background. What if you make iso file using mkisofs and burn it with cdrecord? Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Re: [kde-freebsd] problem hal - k3b ?
> -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Ganbold said the following on 23.04.2007 05:39: > > Beni wrote: > >> On Friday 20 April 2007 03:55:56 Ganbold wrote: > >> > >>> Michael Nottebrock wrote: > >>> > >>>> I forwarded my mail to gnome@ (the HAL > maintainers) after sending it > >>>> and > >>>> Joe Marcus Clarke from gnome@ had this to say on > the issue: > >>>> > >>>> --- snip > >>>> > >>>> This should have been fixed a while ago by > jylefort when he set the > >>>> default device for ATAPI access to be the > ATAPICAM device (as > >>>> opposed to > >>>> the ATA device). Assuming you have not undone > that change, and are > >>>> running the latest version of HAL, these panics > should not be > >>>> occurring. > >>>> > >>>> Even still, you're right that these are not HAL > bugs, but rather an > >>>> issue in the kernel. I use nautilus-cd-burner > to burn CDs in GNOME, > >>>> and > >>>> I have never had such a panic on 6-STABLE. > n-c-b uses cdrecord, cdrao, > >>>> and dvd-utils under the covers to do the actual > device work. Not sure > >>>> what k3b is using, but maybe it diddles > something it shouldn't. > >>>> > >>>> Joe > >>>> > >>>> --- snip > >>>> > >>>> Beni, Robert, Ganbold, are you all in fact > running the latest > >>>> version of > >>>> the hal port and do you all have atapicam > enabled in your kernel? If > >>>> not, > >>>> making sure of both might help avoiding the > problem. > >>>> > >>> I see. I know I have updated my system last > Saturday (14th April > >>> 2007) and > >>> I think I updated both hal and kdelibs ports. I > have atapicam enabled in > >>> kernel. > >>> Let me double check it this weekend and I will > let you know. > >>> > >>> thanks, > >>> > >>> Ganbold > >>> > >>> > >>>> > -------- > > >>>> > >>>> > >>>> Subject: > >>>> Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? > >>>> From: > >>>> Joe Marcus Clarke <[EMAIL PROTECTED]> > >>>> Date: > >>>> Thu, 19 Apr 2007 12:49:26 -0400 > >>>> To: > >>>> Michael Nottebrock <[EMAIL PROTECTED]> > >>>> > >>>> To: > >>>> Michael Nottebrock <[EMAIL PROTECTED]> > >>>> CC: > >>>> [EMAIL PROTECTED] > >>>> > >>>> Michael Nottebrock wrote: > >>>> > >>>>> I forgot to cc gnome@ on my reply. I don't > think this is a HAL bug, > >>>>> but > >>>>> just FYI. > >>>>> > >>>>> > >>>>> > >>>>> > > > >>>>> > >>>>> > >>>>> Subject: > >>>>> Re: [kde-freebsd] problem hal - k3b ? > >>>>> From: > >>>>> Michael Nottebrock <[EMAIL PROTECTED]> > >>>>> Date: > >>>>> Thu, 19 Apr 2007 18:12:46 +0200 > >>>>> To: > >>>>> [EMAIL PROTECTED] > >>>>> > >>>>> To: > >>>>> [EMAIL PROTECTED] > >>>>> CC: > >>>>> Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED], > >>>>> [EMAIL PROTECTED] > >>>>> > >>>>> On Wednesday, 18. April 2007, Beni wrote: > >>>>> > >>>>>> Hi List, > >>>>>> > >>>>>> I think I have a problem with hal(d) and k3b > (version 1.0 from > >>>>>> ports) : > >>>>>> my whole system freezes when starting up k3b. > I get the splash screen > >>>>>> and then it all stops and a ctrl-alt-del is > the only way out. > >>>>>> > >>>>> Other people have reported kernel panics. It > looks to me like k3b&#
Re: [kde-freebsd] problem hal - k3b ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ganbold said the following on 23.04.2007 05:39: > Beni wrote: >> On Friday 20 April 2007 03:55:56 Ganbold wrote: >> >>> Michael Nottebrock wrote: >>> >>>> I forwarded my mail to gnome@ (the HAL maintainers) after sending it >>>> and >>>> Joe Marcus Clarke from gnome@ had this to say on the issue: >>>> >>>> --- snip >>>> >>>> This should have been fixed a while ago by jylefort when he set the >>>> default device for ATAPI access to be the ATAPICAM device (as >>>> opposed to >>>> the ATA device). Assuming you have not undone that change, and are >>>> running the latest version of HAL, these panics should not be >>>> occurring. >>>> >>>> Even still, you're right that these are not HAL bugs, but rather an >>>> issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, >>>> and >>>> I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, >>>> and dvd-utils under the covers to do the actual device work. Not sure >>>> what k3b is using, but maybe it diddles something it shouldn't. >>>> >>>> Joe >>>> >>>> --- snip >>>> >>>> Beni, Robert, Ganbold, are you all in fact running the latest >>>> version of >>>> the hal port and do you all have atapicam enabled in your kernel? If >>>> not, >>>> making sure of both might help avoiding the problem. >>>> >>> I see. I know I have updated my system last Saturday (14th April >>> 2007) and >>> I think I updated both hal and kdelibs ports. I have atapicam enabled in >>> kernel. >>> Let me double check it this weekend and I will let you know. >>> >>> thanks, >>> >>> Ganbold >>> >>> >>>> >>>> >>>> >>>> Subject: >>>> Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? >>>> From: >>>> Joe Marcus Clarke <[EMAIL PROTECTED]> >>>> Date: >>>> Thu, 19 Apr 2007 12:49:26 -0400 >>>> To: >>>> Michael Nottebrock <[EMAIL PROTECTED]> >>>> >>>> To: >>>> Michael Nottebrock <[EMAIL PROTECTED]> >>>> CC: >>>> [EMAIL PROTECTED] >>>> >>>> Michael Nottebrock wrote: >>>> >>>>> I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, >>>>> but >>>>> just FYI. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Subject: >>>>> Re: [kde-freebsd] problem hal - k3b ? >>>>> From: >>>>> Michael Nottebrock <[EMAIL PROTECTED]> >>>>> Date: >>>>> Thu, 19 Apr 2007 18:12:46 +0200 >>>>> To: >>>>> [EMAIL PROTECTED] >>>>> >>>>> To: >>>>> [EMAIL PROTECTED] >>>>> CC: >>>>> Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], >>>>> [EMAIL PROTECTED] >>>>> >>>>> On Wednesday, 18. April 2007, Beni wrote: >>>>> >>>>>> Hi List, >>>>>> >>>>>> I think I have a problem with hal(d) and k3b (version 1.0 from >>>>>> ports) : >>>>>> my whole system freezes when starting up k3b. I get the splash screen >>>>>> and then it all stops and a ctrl-alt-del is the only way out. >>>>>> >>>>> Other people have reported kernel panics. It looks to me like k3b's >>>>> device probing and hald's device probing at the same time manages to >>>>> tickle a bug in ata(4). >>>>> >>>>> Ref: >>>>> http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.htm >>>>> >>>>> l >>>>> http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html >>>>> >>>>> >>>>> I'm afraid a true kernel hacker will have to inconvenince themselves >>>>> with running k3b and hal in order to have this one fixed. FWIW, I >>>
Re: [kde-freebsd] problem hal - k3b ?
Beni wrote: On Friday 20 April 2007 03:55:56 Ganbold wrote: Michael Nottebrock wrote: I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. I see. I know I have updated my system last Saturday (14th April 2007) and I think I updated both hal and kdelibs ports. I have atapicam enabled in kernel. Let me double check it this weekend and I will let you know. thanks, Ganbold Subject: Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? From: Joe Marcus Clarke <[EMAIL PROTECTED]> Date: Thu, 19 Apr 2007 12:49:26 -0400 To: Michael Nottebrock <[EMAIL PROTECTED]> To: Michael Nottebrock <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. -------- Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock <[EMAIL PROTECTED]> Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.htm l http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe Could it all be related to this : http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034553.html and the "solution" from Shane Bell in http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034602.html : "I believe the culprit is somewhere in a recent MFC to atapi-cam.c (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system hangs and "INQUIRY ILLEGAL REQUEST" errors here." Most probably. I updated everything, including source and ports on April 22nd and the problem still exists. k3b hangs after loading splash screen and I had to use power button on my laptop to power down and up the system. I will try to revert rev 1.42.2.2 and see what will happen. Ganbold Beni. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Friday 20 April 2007 01:05:17 Michael Nottebrock wrote: > I forwarded my mail to gnome@ (the HAL maintainers) after sending it and > Joe Marcus Clarke from gnome@ had this to say on the issue: > > --- snip > > This should have been fixed a while ago by jylefort when he set the > default device for ATAPI access to be the ATAPICAM device (as opposed to > the ATA device). Assuming you have not undone that change, and are > running the latest version of HAL, these panics should not be occurring. > > Even still, you're right that these are not HAL bugs, but rather an > issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and > I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, > and dvd-utils under the covers to do the actual device work. Not sure > what k3b is using, but maybe it diddles something it shouldn't. > > Joe > > --- snip > > Beni, Robert, Ganbold, are you all in fact running the latest version of > the hal port and do you all have atapicam enabled in your kernel? If not, > making sure of both might help avoiding the problem. I'm having both # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering and # scsi-emulatie voor atatpi-cd device atapicam in my kernel. My version of hal : [EMAIL PROTECTED] ~]$ hald --version HAL package version: 0.5.8 [EMAIL PROTECTED] ~]$ Thanks Adriaan for looking into this ! Beni. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Friday 20 April 2007 03:55:56 Ganbold wrote: > Michael Nottebrock wrote: > > I forwarded my mail to gnome@ (the HAL maintainers) after sending it and > > Joe Marcus Clarke from gnome@ had this to say on the issue: > > > > --- snip > > > > This should have been fixed a while ago by jylefort when he set the > > default device for ATAPI access to be the ATAPICAM device (as opposed to > > the ATA device). Assuming you have not undone that change, and are > > running the latest version of HAL, these panics should not be occurring. > > > > Even still, you're right that these are not HAL bugs, but rather an > > issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and > > I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, > > and dvd-utils under the covers to do the actual device work. Not sure > > what k3b is using, but maybe it diddles something it shouldn't. > > > > Joe > > > > --- snip > > > > Beni, Robert, Ganbold, are you all in fact running the latest version of > > the hal port and do you all have atapicam enabled in your kernel? If not, > > making sure of both might help avoiding the problem. > > I see. I know I have updated my system last Saturday (14th April 2007) and > I think I updated both hal and kdelibs ports. I have atapicam enabled in > kernel. > Let me double check it this weekend and I will let you know. > > thanks, > > Ganbold > > > > > > > Subject: > > Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? > > From: > > Joe Marcus Clarke <[EMAIL PROTECTED]> > > Date: > > Thu, 19 Apr 2007 12:49:26 -0400 > > To: > > Michael Nottebrock <[EMAIL PROTECTED]> > > > > To: > > Michael Nottebrock <[EMAIL PROTECTED]> > > CC: > > [EMAIL PROTECTED] > > > > Michael Nottebrock wrote: > >> I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but > >> just FYI. > >> > >> > >> > >> > >> > >> Subject: > >> Re: [kde-freebsd] problem hal - k3b ? > >> From: > >> Michael Nottebrock <[EMAIL PROTECTED]> > >> Date: > >> Thu, 19 Apr 2007 18:12:46 +0200 > >> To: > >> [EMAIL PROTECTED] > >> > >> To: > >> [EMAIL PROTECTED] > >> CC: > >> Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], > >> [EMAIL PROTECTED] > >> > >> On Wednesday, 18. April 2007, Beni wrote: > >>> Hi List, > >>> > >>> I think I have a problem with hal(d) and k3b (version 1.0 from ports) : > >>> my whole system freezes when starting up k3b. I get the splash screen > >>> and then it all stops and a ctrl-alt-del is the only way out. > >> > >> Other people have reported kernel panics. It looks to me like k3b's > >> device probing and hald's device probing at the same time manages to > >> tickle a bug in ata(4). > >> > >> Ref: > >> http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.htm > >>l > >> http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > >> > >> I'm afraid a true kernel hacker will have to inconvenince themselves > >> with running k3b and hal in order to have this one fixed. FWIW, I > >> haven't seen in happening on 5.5. > > > > This should have been fixed a while ago by jylefort when he set the > > default device for ATAPI access to be the ATAPICAM device (as opposed to > > the ATA device). Assuming you have not undone that change, and are > > running the latest version of HAL, these panics should not be occurring. > > > > Even still, you're right that these are not HAL bugs, but rather an > > issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and > > I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, > > and dvd-utils under the covers to do the actual device work. Not sure > > what k3b is using, but maybe it diddles something it shouldn't. > > > > Joe Could it all be related to this : http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034553.html and the "solution" from Shane Bell in http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034602.html : "I believe the culprit is somewhere in a recent MFC to atapi-cam.c (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system hangs and "INQUIRY ILLEGAL REQUEST" errors here." Beni. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Michael Nottebrock wrote: I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. I see. I know I have updated my system last Saturday (14th April 2007) and I think I updated both hal and kdelibs ports. I have atapicam enabled in kernel. Let me double check it this weekend and I will let you know. thanks, Ganbold Subject: Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? From: Joe Marcus Clarke <[EMAIL PROTECTED]> Date: Thu, 19 Apr 2007 12:49:26 -0400 To: Michael Nottebrock <[EMAIL PROTECTED]> To: Michael Nottebrock <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. -------- Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock <[EMAIL PROTECTED]> Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Michael Nottebrock wrote: On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. My problem is the same as Beni's. Splash screen appears and hangs. I have to press power button to turn off and on my laptop. Didn't try ctrl+alt+del though. Ganbold Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --- Begin Message --- Michael Nottebrock wrote: > I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just > FYI. > > > > ---- > > Subject: > Re: [kde-freebsd] problem hal - k3b ? > From: > Michael Nottebrock <[EMAIL PROTECTED]> > Date: > Thu, 19 Apr 2007 18:12:46 +0200 > To: > [EMAIL PROTECTED] > > To: > [EMAIL PROTECTED] > CC: > Beni <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED] > > > On Wednesday, 18. April 2007, Beni wrote: >> Hi List, >> >> I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my >> whole system freezes when starting up k3b. I get the splash screen and then >> it all stops and a ctrl-alt-del is the only way out. > > Other people have reported kernel panics. It looks to me like k3b's device > probing and hald's device probing at the same time manages to tickle a bug in > ata(4). > > Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html > http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > > I'm afraid a true kernel hacker will have to inconvenince themselves with > running k3b and hal in order to have this one fixed. FWIW, I haven't seen in > happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --- End Message --- pgpMnseiiYv2q.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007 22:47:08 Richard Kuhns wrote: > On Thursday 19 April 2007 12:12, Michael Nottebrock wrote: > > On Wednesday, 18. April 2007, Beni wrote: > > > Hi List, > > > > > > I think I have a problem with hal(d) and k3b (version 1.0 from ports) : > > > my whole system freezes when starting up k3b. I get the splash screen > > > and then it all stops and a ctrl-alt-del is the only way out. > > > > Other people have reported kernel panics. It looks to me like k3b's > > device probing and hald's device probing at the same time manages to > > tickle a bug in ata(4). > > > > Ref: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html > > http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > > > > I'm afraid a true kernel hacker will have to inconvenince themselves with > > running k3b and hal in order to have this one fixed. FWIW, I haven't seen > > in happening on 5.5. > > > > > > Cheers, > > FWIW: I've been running with a kernel from Jan 22 with no problem. I built > and installed a new kernel/world today and can't run k3b as described > above. I've since reverted to my old kernel and everything's fine again. > - Rich I haven't used k3b for a while but I do have problems with kscd, kaudiocreator, and amarok CD playing. I'm running -stable from Feb 26 and latest kde and CD contents are only properly seen if you first insert the cd, then wait, and then choose the app from the "hal" menu (which takes several seconds to pop up). But even then ripping seems to deadlock, it just hangs and does nothing after you queue and start, and kscd/amarok don't play anything. Amarok merely shows the titles briefly. Both with self-made CDs and official audio CDs. It's possible that my DVD player/recorder is just dying but I'm afraid we're having a more general regression here. Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007 12:12, Michael Nottebrock wrote: > On Wednesday, 18. April 2007, Beni wrote: > > Hi List, > > > > I think I have a problem with hal(d) and k3b (version 1.0 from ports) : > > my whole system freezes when starting up k3b. I get the splash screen and > > then it all stops and a ctrl-alt-del is the only way out. > > Other people have reported kernel panics. It looks to me like k3b's device > probing and hald's device probing at the same time manages to tickle a bug > in ata(4). > > Ref: > http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html > http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > > I'm afraid a true kernel hacker will have to inconvenince themselves with > running k3b and hal in order to have this one fixed. FWIW, I haven't seen > in happening on 5.5. > > > Cheers, FWIW: I've been running with a kernel from Jan 22 with no problem. I built and installed a new kernel/world today and can't run k3b as described above. I've since reverted to my old kernel and everything's fine again. - Rich -- Richard Kuhns Wintek Corporation E-mail: [EMAIL PROTECTED] 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0646 United States of America ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
On Wednesday, 18. April 2007, Beni wrote: > Hi List, > > I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my > whole system freezes when starting up k3b. I get the splash screen and then > it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpxWXd0rPazw.pgp Description: PGP signature
Re: [kde-freebsd] problem hal - k3b ?
On Thursday 19 April 2007, Michael Nottebrock wrote: > On Wednesday, 18. April 2007, Beni wrote: > Ref: > http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.html > http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > > I'm afraid a true kernel hacker will have to inconvenince themselves with > running k3b and hal in order to have this one fixed. FWIW, I haven't seen > in happening on 5.5. I won't pretend to be a true kernel hacker, but I've got a passing acquaintance with ata(4) from hacking in it (and a weirdly patched -STABLE because of that) and k3b experience. I'll see what -- assuming I can trigger this -- I can do. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot signature.asc Description: This is a digitally signed message part.
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sun, 18 Feb 2007, Kris Kennaway wrote: http://www.freebsd.org/cgi/query-pr.cgi?pr=109277 The problem looks like a lack of proper locking during the operations with clist (specifically, this causes multiple entry to cblock_alloc()). I'm ready to provide further debugging information on this issue. Unfortunately, I'm not familiar enough with the locking concepts in modern FreeBSD kernels (and in tty subsystem particularly) in order to make the fix myself. ...and that's the problem :) You could do this additional work, but you'd be wasting your time. I don't believe that nobody _knows_ how to serialize clist-related work within ppp(4) properly. I would rather believe that nobody (at least, among the src-commiters) _cares_ about it. Well, given the presence of working alternatives to ppp(4), this situation seems to be quite explainable. OTOH I still think that my PR could be useful in two aspects: 1) it clearly documents ppp(4) as broken in it's current state so wise people won't use it in production environment; 2) it can be useful for some hypothetical courageous person who will try to fix the problem. Kris Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
Hello! On Thu, 8 Feb 2007, Kris Kennaway wrote: Not that it contradicts anything you said, but it's worth re-emphasizing that there is apparently no-one in the community interested in maintaining pppd on FreeBSD, which is how it got to the current sorry state. I agree that the absence of ppp(4) maintainer makes it harder to fix problems with this code. OTOH, I haven't found a single more-or-less informative PR regarding ppp(4)-related crashes in recent FreeBSD branches in the GNATS database. Maybe it's due to the poor repeatability of the problem due to its race-like nature. I've decided to fill up this gap, see http://www.freebsd.org/cgi/query-pr.cgi?pr=109277 The problem looks like a lack of proper locking during the operations with clist (specifically, this causes multiple entry to cblock_alloc()). I'm ready to provide further debugging information on this issue. Unfortunately, I'm not familiar enough with the locking concepts in modern FreeBSD kernels (and in tty subsystem particularly) in order to make the fix myself. Kris Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sun, Feb 18, 2007 at 09:31:47PM +0200, Dmitry Pryanishnikov wrote: > > Hello! > > On Thu, 8 Feb 2007, Kris Kennaway wrote: > >Not that it contradicts anything you said, but it's worth > >re-emphasizing that there is apparently no-one in the community > >interested in maintaining pppd on FreeBSD, which is how it got to the > >current sorry state. > > I agree that the absence of ppp(4) maintainer makes it harder to fix > problems with this code. OTOH, I haven't found a single more-or-less > informative PR regarding ppp(4)-related crashes in recent FreeBSD branches > in the GNATS database. Maybe it's due to the poor repeatability of the > problem due to its race-like nature. I've decided to fill up this gap, > see > > http://www.freebsd.org/cgi/query-pr.cgi?pr=109277 > > The problem looks like a lack of proper locking during the operations with > clist (specifically, this causes multiple entry to cblock_alloc()). > I'm ready to provide further debugging information on this issue. > Unfortunately, I'm not familiar enough with the locking concepts > in modern FreeBSD kernels (and in tty subsystem particularly) > in order to make the fix myself. ...and that's the problem :) You could do this additional work, but you'd be wasting your time. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sun, 11 Feb 2007, Bruce M. Simpson wrote: > There's information around PPP that's not been communicated or > documented well. The 'performance' way to do PPP on FreeBSD is to go off > and run MPD, because it has the right compromise between doing low-level > packet shunting in the kernel, whilst using Netgraph hooks to tap the > PPP control traffic handling off into userland. On your first point, I'd not looked into MPD before because I'd assumed it was _only_ about multilink PPP, thinking multi meant 'two or more', a misconception not immediately dispelled by the descriptions in ports and on sourceforge, until finding a bundle defined as 'one or more' links. > MPD is wicked cool, and is a well architected way to do things, but the > ultimate utility depends on how useful it is to everyone who might use it. Just now installed mpd4 for a browse over the manuals and example confs and scripts, and am completely gobsmacked by its clarity and scope. To call the scripting language 'chat' is indeed heavy-duty understatement, and the examples alone seem to cover most of what I'll need to know. I'd been mulling over ppp, ng and pppoed docs prior to doing PPPoE here (currently hiding behind an ADSL router) but now know where to start. Thanks! Ian (not at all helpful re the KPPP / pppd issue though, sorry Michael) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd
On Sat, 2007-02-10 at 03:06 +0100, Michael Nottebrock wrote: [ snip ] > All that your "bug report" accomplishes is broadcasting your bad and > uninformed attitude to an even bigger audience. It is in your own and the > FreeBSD community's best interest to backtrack before anyone gets to form a > negative opinion on both. I just took a look at the list of bugs in pppd. Aside from being unmaintained it looks as though the functionality is still okay. This is borne out my experience using pppd with my wireless modem. Just last night on a trip from JFK in fact. Opinion is getting more important with the market arrival of affordable EVDO coverage and cards. EVDO is a wireless technology for connecting to the net. The connection speeds are between 700 ~ 3000 kb/s I nearly passed on the opportunity to get one card due to reports that FreeBSD 6.1 and 6.2 had rendered kernel ppp unusable. In the current generation these cards are very fast serial modems that connect to the USB bus. They configure exactly like a serial connected modem and ppp stack. They are primarily configured for windows but configurations for kernel pppd primarily for Linux and Mac OSX are readily available on the Internet. The argument for EVDO cards also holds for bluetooth enabled phones. With Verizon and Sprint allowing you to use the bluetooth stack in your phone to connect to the Internet at EVDO speeds for a nominal fee, we should expect more people and try to use FreeBSD in this manner. When they do they will com from Linux with a kernel pppd configuration. -- Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Sunday, 11. February 2007 02:43, Bruce M. Simpson wrote: > So far so good. The problem is that the BSD magicians and the KDE GUI > magicians are not sharing their spell-books, and thus, their models of > how the code operates; the communities have to intersect somehow. That > could be you, y'know. Human bridges are just as, if not more, important > as ISO/OSI Layer 2 devices. :^) Quite true. However, this particular human bridge between developer communities is running at capacity already. We need some trunking here. Redundant links, y'know. When I said "someone", I *do* mean someone who isn't me (and whose idea of communication isn't yelling at developers in bugzilla). :) -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpLeeG7cwMsu.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
Michael Nottebrock wrote: And yes, if pppd is broken and won't be fixed, it should disappear. And when that happens, so will kppp (it won't build once the if_ppp.h header is gone). Which of course would solve the problem in a way. In any case: I dragged this issue onto -stable precisely to attract attention to the problem and hopefully motivate someone to get down and write some code, whether for pppd or kppp, I really don't care much. Necessity is the mother of invention - either that, or a big bag of cash for everyone. There's information around PPP that's not been communicated or documented well. The 'performance' way to do PPP on FreeBSD is to go off and run MPD, because it has the right compromise between doing low-level packet shunting in the kernel, whilst using Netgraph hooks to tap the PPP control traffic handling off into userland. MPD is wicked cool, and is a well architected way to do things, but the ultimate utility depends on how useful it is to everyone who might use it. So far so good. The problem is that the BSD magicians and the KDE GUI magicians are not sharing their spell-books, and thus, their models of how the code operates; the communities have to intersect somehow. That could be you, y'know. Human bridges are just as, if not more, important as ISO/OSI Layer 2 devices. :^) The way to converge on solution is communication. This has been my experience in recent successful collaboration with the Avahi developers. Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Saturday, 10. February 2007 07:34, Ian Smith wrote: > Since once trying (and failing) to debug or even comprehend a spaghetti > of scripts and configs behind a dialout-only linux pppd setup some years > ago, compared to the much more straightforward ppp with mgetty setup for > both dialout and some dialin modem lines I'd built pretty much from the > FreeBSD Handbook even at 2.2.6 with nary a problem, regressing for sake > of 'compatibility' with a linux-based sub-application seems silly. Well, kppp makes configuring dialout easy. Or attempts to, at least. :) > I agree with you about this not being a KPPP bug (though searching KDE > bugs for 'kppp' provides no shortage of hits!) and appreciate that KDE > people have no interest in catering for user ppp, since it's not linux, > despite or perhaps because of its obvious superiority to FreeBSD people. > > Maybe at least the KPPP 'documentation', such as it is, could at least > mention that it doesn't support FreeBSD's ppp over tun devices, to avoid > the expectation that it should work that gave rise to this thread. It kinda does. It says right in the about dialog and in the very first line of its online help: "A dialer and front end for pppd". > And yes, if pppd is broken and won't be fixed, it should disappear. And when that happens, so will kppp (it won't build once the if_ppp.h header is gone). Which of course would solve the problem in a way. In any case: I dragged this issue onto -stable precisely to attract attention to the problem and hopefully motivate someone to get down and write some code, whether for pppd or kppp, I really don't care much. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpyYiQbYxsIy.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
Hi, > On Fri, 09 Feb 2007 17:24:11 +0100 > Eric Masson <[EMAIL PROTECTED]> said: emss> Right, and an up to date pppd in base would be imho really nice to have. emss> Kernel pppoe as in Net/Open would be an alternative to net/mpd. emss> (No, I'm not volunteering to port NetBSD's kernel ppp to FreeBSD as my emss> C & kernel programming skills are way under required level) In my experience, this is not an issue that just porting pppd from NetBSD or OpenBSD, or importing latest pppd solves the problem. It seems locking problem to me, and setting debug.mpsafenet to 0 should be a workaround. Of course, it's great someone upgrading our pppd to recent one. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org http://www.imasy.org/~ume/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Thu, 8 Feb 2007, Michael Nottebrock wrote: > On Thursday, 8. February 2007 08:38, Ian Smith wrote: > > On Wed, 7 Feb 2007, Michael Nottebrock wrote: > > > On Wednesday, 7. February 2007 18:45, Joe Vender wrote: > > > > On Wednesday 07 February 2007 01:59, Michael Nottebrock wrote: > > > > ... > > > > > > > > > There is https://bugs.kde.org/show_bug.cgi?id=55785 on record, your > > > > > description sounds more like you're getting a kernel panic in the > > > > > background though (KPPP is a frontend for pppd and the in-kernel ppp > > > > > driver). > > > > > > > > If I want to use KPPP in FreeBSD, do I need to first manually edit any > > > > config files for pppd, and if so, please elaborate, or does creating > > > > the settings in the "Configure" sections of KPPP take care of > > > > everything needed? > > > > > > > > I found this bug report which sounds just like the problem I'm having > > > > with FreeBSD and KPPP. > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/98154 > > > > > > I agree, that sounds similar. I've changed the CC to stable@, since that > > > is a better place for pppd/kernel ppp related issues. > > > > > > > Is there any intention to address it? > > > > > > I call on the community (especially those with modems) to take it on. To > > > that end, I've left your motivational speech below intact for everyone's > > > benefit. > > > > Perhaps we should rather be calling upon the KDE developer community to > > provide such a frontend interface to configure and invoke FreeBSD's ppp, > > for those who find a little manual configuration, as you describe below, > > beyond them? > > You mean the FreeBSD-using KDE developer community, which is neither very > big > nor very prolific. I am convinced that remaining compatible with common > Linux > solutions will always be the better strategy as far as the desktop is > concerned. Well perhaps there's a pppd hacker who shares your conviction out there somewhere? As Kris emphasised, pppd's fallen into disrepair because nobody cares for it, whereas I've watched ongoing quality work on and support of ppp over the last 9 years by very cluey FreeBSD developers. I made my own choice back then, and have long omitted ppp from kernels as a waste of space, and have very rarely even seen pppd mentioned. KPPP doesn't fail here, but finding no ppp interface, has nothing to do. Since once trying (and failing) to debug or even comprehend a spaghetti of scripts and configs behind a dialout-only linux pppd setup some years ago, compared to the much more straightforward ppp with mgetty setup for both dialout and some dialin modem lines I'd built pretty much from the FreeBSD Handbook even at 2.2.6 with nary a problem, regressing for sake of 'compatibility' with a linux-based sub-application seems silly. I agree with you about this not being a KPPP bug (though searching KDE bugs for 'kppp' provides no shortage of hits!) and appreciate that KDE people have no interest in catering for user ppp, since it's not linux, despite or perhaps because of its obvious superiority to FreeBSD people. Maybe at least the KPPP 'documentation', such as it is, could at least mention that it doesn't support FreeBSD's ppp over tun devices, to avoid the expectation that it should work that gave rise to this thread. And yes, if pppd is broken and won't be fixed, it should disappear. Over and out, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd
On Friday, 9. February 2007 22:48, John Walthall wrote: > Because of known problems with > PPPD, KPPP should provide at least the option of using user land PPP. > You may of course differ from this view. However, unless a large outcry > arises, I will not close the bug. I think that it is, in-fact a bug. > Bugs are sometimes a bit subjective. The KPPP Developers can always > ignore me. No, bugs are not 'a bit subjective'. With just a little actual analysis and straight thinking it is very easy to determine what is a bug and where the bug is. The fact that KPPP does not support ppp(8) is not a bug, it is a missing feature. If you want to request a feature, you open a wish, not a bug, you word it nicely and preferably attach some code that implements that feature, because this is how community-driven open source development works. Did it ever cross your mind that the KPPP developer(s) might not even use FreeBSD? The fact that machines panic or freeze when KPPP is used is not a bug in KPPP either, because KPPP is nothing but a front-end to the software that causes the problem. By principle, a kernel panic or freeze is never an application's fault, because the kernel should never panic and never freeze, no matter what an application does. Therefore, the bug report needs to go into FreeBSD's bugtracker (someone else already filed one, see my previous mails for the URL), not KDE's. All that your "bug report" accomplishes is broadcasting your bad and uninformed attitude to an even bigger audience. It is in your own and the FreeBSD community's best interest to backtrack before anyone gets to form a negative opinion on both. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp7bVJV0CANM.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
Peter Jeremy wrote: On 2007-Feb-08 17:16:23 -0500, John Walthall <[EMAIL PROTECTED]> wrote: functionally obsolete. User PPP provides better service, and several tangible design benefits. User PPP is very easy to use, Kernel PPP is not. Actually, kernel PPP has one significant (at least theoretical) advantage over user ppp: Network data is not pushed through the kernel/userland interface an additional two times. This is irrelevant for low-speed modem interfaces but could be significant for PPPoE on high-speed broadband. Keep in mind that a firewall host is likely to be a slow box - either a pensioned-off desktop or a mini-ITX style system. FreeBSD is NOT Linux, and SHOULD NOT attempt to model it. FreeBSD is BSD UNIX! Isn't that the WHOLE POINT (pardon my shouting) for our existence? I'm not sure I see where Linux comes into this. Looking back into history, it seems that both ppp(4) and ppp(8) arrived fairly close together. It appears that ppp(4) was a port of the portable ppp-2.2 code - the same code as used in SunOS AFAIR. Yes, indeed. I admit I had not thought of that. I was writing from MY personal perspective, With my nice modern machine and my privileged state of not having broadband access (wink, wink). This is a rant, er editorial; I am writing as it seems to *me*. Conceded: this is not true for *everyone*. As to where Linux comes in. It appears to me that PPP is the more normal way on FreeBSD, whereas, in my own experience Linux, (or at least, the distributions I formerly used) prefer PPPD. Therefore when KDE wrote KPPP, (and they originally wrote it more-or-less for Linux.) They used PPPD. There is nothing theoretically invalid about PPPD. It's just not quite how we do things *most of the time*. Over time FreeBSD and Linux drifted apart on this design issue, and it became something of a characteristic of BSD, perhaps that is why Kernel PPP became less well maintained I should *not* have said "Did a clumsy job". I probably should have said, "Did a less than perfect job". I guess it's kind of like trying to make a bread recipe with rice flour instead of wheat flour. I retract this phrase. Regarding the various comments by Michael Nottebrock, Firstly: The bug you mentioned I have not experienced. I never had problems when killing the X-server. I cannot comment on that. I do not often kill my X-Server; perhaps I just didn't do it frequently enough. If you believe that this speech is a rant, you are somewhat correct. I am rather cross and it does show. However I differ with your estimation that it is undignified. Oh, Please! With all due respect you take things entirely too seriously. I am obviously being over-the-sarcastic. If you feel that you "should not dignify this rant by replying to it, but," then don't! No buts! If you really think it is a rant. Ignore it! That's the mature thing to do! As for your opinion that I should close the bug. I will not. An unwise design decision has caused this problem. Because of known problems with PPPD, KPPP should provide at least the option of using user land PPP. You may of course differ from this view. However, unless a large outcry arises, I will not close the bug. I think that it is, in-fact a bug. Bugs are sometimes a bit subjective. The KPPP Developers can always ignore me. -- Unless instructed to do otherwise, Please address mail to [EMAIL PROTECTED] and not to this address. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd
Peter Jeremy <[EMAIL PROTECTED]> writes: Hi, > Actually, kernel PPP has one significant (at least theoretical) > advantage over user ppp: Network data is not pushed through the > kernel/userland interface an additional two times. This is irrelevant > for low-speed modem interfaces but could be significant for PPPoE on > high-speed broadband. Right, and an up to date pppd in base would be imho really nice to have. Kernel pppoe as in Net/Open would be an alternative to net/mpd. (No, I'm not volunteering to port NetBSD's kernel ppp to FreeBSD as my C & kernel programming skills are way under required level) > Keep in mind that a firewall host is likely to be a slow box - either > a pensioned-off desktop or a mini-ITX style system. That sometimes run other apps... -- Et manque de bol, ça accélère énormément cette nouvelle version (à croire que l'ancienne était codée en 68k et utilisait ApplScript). -+- SC in Guide du Macounet Pervers : Jobs, stakhanoviste ? Nooon ! -+- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd
On 2007-Feb-08 17:16:23 -0500, John Walthall <[EMAIL PROTECTED]> wrote: >functionally obsolete. User PPP provides better service, and several >tangible design benefits. User PPP is very easy to use, Kernel PPP is not. Actually, kernel PPP has one significant (at least theoretical) advantage over user ppp: Network data is not pushed through the kernel/userland interface an additional two times. This is irrelevant for low-speed modem interfaces but could be significant for PPPoE on high-speed broadband. Keep in mind that a firewall host is likely to be a slow box - either a pensioned-off desktop or a mini-ITX style system. >FreeBSD is NOT Linux, and SHOULD NOT attempt to model it. FreeBSD is BSD >UNIX! Isn't that the WHOLE POINT (pardon my shouting) for our existence? I'm not sure I see where Linux comes into this. Looking back into history, it seems that both ppp(4) and ppp(8) arrived fairly close together. It appears that ppp(4) was a port of the portable ppp-2.2 code - the same code as used in SunOS AFAIR. -- Peter Jeremy pgpOiEn9LMnNN.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
On Thursday, 8. February 2007 23:16, John Walthall wrote: > Ok, now an editorial: I should not really dignify this rant by replying to it, but: > We have a fundamental design difference from Linux here. We chose this > difference because we believed that it was better. Why would we go back > now because the developers of a third-party interface to our systems did > a clumsy job? KPPP is not an interface to 'our' systems. It's an interface to *pppd*, which happens to be available for a wide range of Unices and Unix-like systems. > We should adjure them to implement the > new and better system. This is not actually an appropriate place for > this discussion. It should be directed to [EMAIL PROTECTED] and/or > http://bugs.kde.org. Because it is a KDE problem and *not* a FreeBSD > Problem. (I have already submitted it to the KDE Bugzilla) A kernel panic/freeze triggered by a badly maintained driver is most certainly not any application's problem. You should probably close that bug yourself. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpC06TnsA434.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd
Ok, now an editorial: Kernel PPP is certified crap and should be phased out. In my personal opinion the reason that it is unmaintained and slowly dissolving into a nonfunctional pool of electrolytes, is that it is functionally obsolete. User PPP provides better service, and several tangible design benefits. User PPP is very easy to use, Kernel PPP is not. I have had nothing but serious problems with Kernel PPP, In my experience whenever Kernel PPP crashes, which it does pretty much at random, and always when the network drops (a common happening for those of us blighted by Dial up.) It causes the whole system to lock up. *Forcing*me*to*physically*unplug*the*computer*to*continue*. FreeBSD is NOT Linux, and SHOULD NOT attempt to model it. FreeBSD is BSD UNIX! Isn't that the WHOLE POINT (pardon my shouting) for our existence? Isn't this why you and me bear with minor points such as this one. BECAUSE WE ARE DIFFERENT AND PROUD OF IT! If you just start modeling Linux, we are invalidating our own existence and vindicating Linux's innumerable disparities, nay flaws. We have a fundamental design difference from Linux here. We chose this difference because we believed that it was better. Why would we go back now because the developers of a third-party interface to our systems did a clumsy job? Rather than weep in anguish at their implementation of a known faulty and legacy system. We should adjure them to implement the new and better system. This is not actually an appropriate place for this discussion. It should be directed to [EMAIL PROTECTED] and/or http://bugs.kde.org. Because it is a KDE problem and *not* a FreeBSD Problem. (I have already submitted it to the KDE Bugzilla) These are of course my own opinions. -- Unless instructed to do otherwise| Support public access UNIX address mail to [EMAIL PROTECTED] | http://sdf.lonestar.org and not to [EMAIL PROTECTED]| ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Thursday, 8. February 2007 08:38, Ian Smith wrote: > On Wed, 7 Feb 2007, Michael Nottebrock wrote: > > On Wednesday, 7. February 2007 18:45, Joe Vender wrote: > > > On Wednesday 07 February 2007 01:59, Michael Nottebrock wrote: > > > ... > > > > > > > There is https://bugs.kde.org/show_bug.cgi?id=55785 on record, your > > > > description sounds more like you're getting a kernel panic in the > > > > background though (KPPP is a frontend for pppd and the in-kernel ppp > > > > driver). > > > > > > If I want to use KPPP in FreeBSD, do I need to first manually edit any > > > config files for pppd, and if so, please elaborate, or does creating > > > the settings in the "Configure" sections of KPPP take care of > > > everything needed? > > > > > > I found this bug report which sounds just like the problem I'm having > > > with FreeBSD and KPPP. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/98154 > > > > I agree, that sounds similar. I've changed the CC to stable@, since that > > is a better place for pppd/kernel ppp related issues. > > > > > Is there any intention to address it? > > > > I call on the community (especially those with modems) to take it on. To > > that end, I've left your motivational speech below intact for everyone's > > benefit. > > Perhaps we should rather be calling upon the KDE developer community to > provide such a frontend interface to configure and invoke FreeBSD's ppp, > for those who find a little manual configuration, as you describe below, > beyond them? You mean the FreeBSD-using KDE developer community, which is neither very big nor very prolific. I am convinced that remaining compatible with common Linux solutions will always be the better strategy as far as the desktop is concerned. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpDZGOjFYMZq.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Thu, Feb 08, 2007 at 06:38:08PM +1100, Ian Smith wrote: > Not to suggest that any pppd/kernel interaction problems ought not to be > addressed by those wishing to maintain pppd for linux compatibility or > other reasons, but the reality is that most FreeBSD users have long > preferred user ppp for dialup, and more recently for ADSL via PPPoE. Not that it contradicts anything you said, but it's worth re-emphasizing that there is apparently no-one in the community interested in maintaining pppd on FreeBSD, which is how it got to the current sorry state. Kris pgpXqteOiNEIs.pgp Description: PGP signature
Re: pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Wed, 7 Feb 2007, Michael Nottebrock wrote: > On Wednesday, 7. February 2007 18:45, Joe Vender wrote: > > On Wednesday 07 February 2007 01:59, Michael Nottebrock wrote: > > ... > > > > > There is https://bugs.kde.org/show_bug.cgi?id=55785 on record, your > > > description sounds more like you're getting a kernel panic in the > > > background though (KPPP is a frontend for pppd and the in-kernel ppp > > > driver). > > > > If I want to use KPPP in FreeBSD, do I need to first manually edit any > > config files for pppd, and if so, please elaborate, or does creating the > > settings in the "Configure" sections of KPPP take care of everything > > needed? > > > > I found this bug report which sounds just like the problem I'm having with > > FreeBSD and KPPP. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/98154 > > I agree, that sounds similar. I've changed the CC to stable@, since that is > a > better place for pppd/kernel ppp related issues. > > > Is there any intention to address it? > > I call on the community (especially those with modems) to take it on. To > that > end, I've left your motivational speech below intact for everyone's benefit. Perhaps we should rather be calling upon the KDE developer community to provide such a frontend interface to configure and invoke FreeBSD's ppp, for those who find a little manual configuration, as you describe below, beyond them? > > IMHO, setting up a dialup connection in FreeBSD via ppp seems like jumping > > through hoops, even compared to linux. > > Personally, I think it's pretty easy - for modem users it usually means just > editing four lines in /etc/ppp/ppp.conf (device, phone number, user, > password) then typing ppp in a shell, then typing dial and > they're online. That's pretty much the same amount of data input and > interaction that kppp requires. Indeed. And connecting small scripts to go online, and to hangup when desired (eg by kill `cat /var/run/ppp0.pid`) to a pretty desktop button or two for the one-clicker's convenience would be a useful KDE addition, assuming that the Linux bias that makes some other functions of KDE less than useful on a FreeBSD system (despite the excellent work by porters), could likewise be ameliorated? Not to suggest that any pppd/kernel interaction problems ought not to be addressed by those wishing to maintain pppd for linux compatibility or other reasons, but the reality is that most FreeBSD users have long preferred user ppp for dialup, and more recently for ADSL via PPPoE. Respectfully, Ian (using KDE despite ongoing bloat and linux-centricism) > > I was told on the freebsd-questions > > mailing list that KPPP uses pppd, and that pppd is known to be very buggy > > and essentially unmaintained in FreeBSD. If this is true, then a very > > easy-to-use feature of KDE, namely KPPP for setting up a dialup connection, > > is not going to be usable. A lot of users are going to be put off FreeBSD > > if they can't use KPPP with a serial modem on dialup. FreeBSD needs a > > usable KPPP, and therefore a working and maintained pppd, if it has any > > plans to be considered a user-friendly desktop alternative to linux, not to > > mention an alternative to Windows. > > > Cheers, > -- >,_, | Michael Nottebrock | [EMAIL PROTECTED] > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org >\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pppd crashes, was: kde-freebsd] Question about KPPP on FreeBSD
On Wednesday, 7. February 2007 18:45, Joe Vender wrote: > On Wednesday 07 February 2007 01:59, Michael Nottebrock wrote: > ... > > > There is https://bugs.kde.org/show_bug.cgi?id=55785 on record, your > > description sounds more like you're getting a kernel panic in the > > background though (KPPP is a frontend for pppd and the in-kernel ppp > > driver). > > If I want to use KPPP in FreeBSD, do I need to first manually edit any > config files for pppd, and if so, please elaborate, or does creating the > settings in the "Configure" sections of KPPP take care of everything > needed? > > I found this bug report which sounds just like the problem I'm having with > FreeBSD and KPPP. http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/98154 I agree, that sounds similar. I've changed the CC to stable@, since that is a better place for pppd/kernel ppp related issues. > Is there any intention to address it? I call on the community (especially those with modems) to take it on. To that end, I've left your motivational speech below intact for everyone's benefit. > IMHO, setting up a dialup connection in FreeBSD via ppp seems like jumping > through hoops, even compared to linux. Personally, I think it's pretty easy - for modem users it usually means just editing four lines in /etc/ppp/ppp.conf (device, phone number, user, password) then typing ppp in a shell, then typing dial and they're online. That's pretty much the same amount of data input and interaction that kppp requires. > I was told on the freebsd-questions > mailing list that KPPP uses pppd, and that pppd is known to be very buggy > and essentially unmaintained in FreeBSD. If this is true, then a very > easy-to-use feature of KDE, namely KPPP for setting up a dialup connection, > is not going to be usable. A lot of users are going to be put off FreeBSD > if they can't use KPPP with a serial modem on dialup. FreeBSD needs a > usable KPPP, and therefore a working and maintained pppd, if it has any > plans to be considered a user-friendly desktop alternative to linux, not to > mention an alternative to Windows. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgplqe9AQmLl9.pgp Description: PGP signature
Re: kde
Steinberg, Michael wrote: im compiling kde from the ports for about the hundreth time and something always goes wrong this time its more simple than most but i can't seem to find what im looking for. It attempted to fetch a library called tiff.4 in several places and found nothing. It asked me to find it and ive been looking all over google and got nothing. Does anybody know where i can find this library? Thanx, Max ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Maybe you just got to get more down and dirty. If its really getting tough and there seems no end in sight try a "portupgrade -kfa" which I have always assumed stands for (along with the old doom cheat codes) "Kick F**ken Ass" :) Also try with the -p switch to create packages which might save some time on mass package nukes and retrys, or even a -O to ignore dependencies. Also if you get stuck on something small like tiff try just installing it as a package over the internet. pkg_add -r tiff to install a binary package of it, you could also do a -f on that to force it, which is something that should be considered to at the top of your list. I almost always have a good look through my /var/db/pkg before and after even the most ruthless portupgrade I usually find it remarkably clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kde
On Saturday 11 March 2006 21:40, Steinberg, Michael wrote: > im compiling kde from the ports for about the hundreth time and something > always goes wrong this time its more simple than most but i can't seem to > find what im looking for. It attempted to fetch a library called tiff.4 in > several places and found nothing. It asked me to find it and ive been > looking all over google and got nothing. Does anybody know where i can find > this library? > Thanx, > Max The FreeBSD KDE ports have their own mailing list. Try mailing kde-freebsd@freebsd.kde.org, you are more likely to get help over there. Frederic -- PGP key: http://frederic.cgarchive.com/PGP/frederic.asc pgpfFlHwir7Gv.pgp Description: PGP signature
Re: kde
On Sat, Mar 11, 2006 at 03:40:57PM -0500, Steinberg, Michael wrote: > im compiling kde from the ports for about the hundreth time and something > always goes wrong this time its more simple than most but i can't seem to > find what im looking for. It attempted to fetch a library called tiff.4 in > several places and found nothing. It asked me to find it and ive been > looking all over google and got nothing. Does anybody know where i can find > this library? In the tiff port (graphics/tiff), oddly enough :-) It should be installed automatically if all is going well though, so I suspect something else is wrong. If this doesn't fix things for you, you'll need to follow up with the actual errors you're seeing. In future, problems with ports should be discussed on the freebsd-ports mailing list. Kris pgp9cbj67n7Pq.pgp Description: PGP signature
kde
im compiling kde from the ports for about the hundreth time and something always goes wrong this time its more simple than most but i can't seem to find what im looking for. It attempted to fetch a library called tiff.4 in several places and found nothing. It asked me to find it and ive been looking all over google and got nothing. Does anybody know where i can find this library? Thanx, Max ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE 3.5
Kris Kennaway schrieb: > Unfortunately, now we are back to square 1, since you just committed > KDE 3.5.1 :-) 'S okay - patience is a virtue and package users are the most virtuous bunch of them all. And as for square one, expat2 got bumped. :O Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: KDE 3.5
On Wed, Feb 01, 2006 at 02:52:56PM +0100, Michael Nottebrock wrote: > Roger Grosswiler schrieb: > > Hey, > > > > where can i get it from with pkg_add ?? > > http://www.freebsd.org/doc/en/books/handbook/packages-using.html Unfortunately we're still playing catch-up with the official packages, though by now we had just about got kde 3.5.0 built and uploaded everywhere. The extensive testing we had to do for recent bsd.port.mk commits monopolized the build cluster for the past few weeks to the exclusion of other package builds, and then there were qt and other port build problems that have hopefully now been resolved. Unfortunately, now we are back to square 1, since you just committed KDE 3.5.1 :-) Kris pgp2q4V7mwbKN.pgp Description: PGP signature
Re: KDE 3.5
Roger Grosswiler schrieb: > Hey, > > where can i get it from with pkg_add ?? http://www.freebsd.org/doc/en/books/handbook/packages-using.html Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: KDE 3.5
Follow the instructions at http://freebsd.kde.org/ On 2/1/06, Roger Grosswiler <[EMAIL PROTECTED]> wrote: > > Hey, > > where can i get it from with pkg_add ?? > > thx, > roger > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- // Irvin P. Piraman // http://netgarage.thefluxproject.com // Key ID: 0x92CA572B ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
KDE 3.5
Hey, where can i get it from with pkg_add ?? thx, roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE 3.5.0 seems much chubbier than 3.4.2
On Tuesday 31 January 2006 08:25, Kris Kennaway wrote: > > I did have a kernel from before the new malloc and it still seemed quite > > sluggish. I remember being stuck because a commit to the AGP driver on > > 20/12/05 prevented the nvidia driver building. > > new malloc = userland, not kernel. Yeah but I don't install world without first doing install kernel :) > P.S. You're posting to the wrong list ;) Doh! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpsrCoNDasoI.pgp Description: PGP signature
Re: KDE 3.5.0 seems much chubbier than 3.4.2
On Tue, Jan 31, 2006 at 08:09:16AM +1030, Daniel O'Connor wrote: > On Tuesday 31 January 2006 01:16, Michael Nottebrock wrote: > > > I did recently update to the latest -current (ie new malloc > > > implementation) but the the sluggish behaviour was still present prior to > > > that (although maybe not as bad) > > > > Not to suggest you're imagining things, but someone else just posted on > > freebsd-current@ that other applications show greatly increased memory > > usage as well, so it probably is a -current specific problem after all. > > I did have a kernel from before the new malloc and it still seemed quite > sluggish. I remember being stuck because a commit to the AGP driver on > 20/12/05 prevented the nvidia driver building. new malloc = userland, not kernel. Kris P.S. You're posting to the wrong list ;) pgplLgbhJo9eb.pgp Description: PGP signature
Re: KDE 3.5.0 seems much chubbier than 3.4.2
On Tuesday 31 January 2006 01:16, Michael Nottebrock wrote: > > I did recently update to the latest -current (ie new malloc > > implementation) but the the sluggish behaviour was still present prior to > > that (although maybe not as bad) > > Not to suggest you're imagining things, but someone else just posted on > freebsd-current@ that other applications show greatly increased memory > usage as well, so it probably is a -current specific problem after all. I did have a kernel from before the new malloc and it still seemed quite sluggish. I remember being stuck because a commit to the AGP driver on 20/12/05 prevented the nvidia driver building. Only yesterday did I revert those changes and built a new kernel & installed it. Unfortunately I don't have any logs or top/ps output from before the new kernel :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpzxsjUGYe02.pgp Description: PGP signature
Re: KDE 3.5.0 seems much chubbier than 3.4.2
Daniel O'Connor schrieb: > I just updated to KDE 3.5.0 and it seems considerably more memory hungry that > 3.4.2, for example.. > > PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND > 1126 darius 5 200 213M 50816K kserel 13:09 0.73% amarokapp > 1119 darius 3 200 260M 67180K kserel 40:04 0.00% kdeinit > 1153 darius 3 200 137M 51080K kserel 17:08 0.00% kmail > 1118 darius 3 200 119M 7324K kserel 6:03 0.00% kopete > 1050 darius 1 960 77228K 10140K select 3:37 0.00% kdeinit > 1090 darius 1 960 98476K 12680K select 1:20 0.00% kdeinit > 1110 darius 1 960 73292K 5136K select 1:14 0.00% kdeinit > 1089 darius 1 960 91168K 6084K select 0:47 0.00% kdeinit > 1082 darius 1 960 122M 7268K select 0:40 0.00% kdeinit > > No wonder my system is thrashing :) > > Does anyone know why 3.5.0 seems to be using so much more memory? > > I did recently update to the latest -current (ie new malloc implementation) > but the the sluggish behaviour was still present prior to that (although > maybe not as bad) Not to suggest you're imagining things, but someone else just posted on freebsd-current@ that other applications show greatly increased memory usage as well, so it probably is a -current specific problem after all. Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
KDE 3.5.0 seems much chubbier than 3.4.2
I just updated to KDE 3.5.0 and it seems considerably more memory hungry that 3.4.2, for example.. PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 1126 darius 5 200 213M 50816K kserel 13:09 0.73% amarokapp 1119 darius 3 200 260M 67180K kserel 40:04 0.00% kdeinit 1153 darius 3 200 137M 51080K kserel 17:08 0.00% kmail 1118 darius 3 200 119M 7324K kserel 6:03 0.00% kopete 1050 darius 1 960 77228K 10140K select 3:37 0.00% kdeinit 1090 darius 1 960 98476K 12680K select 1:20 0.00% kdeinit 1110 darius 1 960 73292K 5136K select 1:14 0.00% kdeinit 1089 darius 1 960 91168K 6084K select 0:47 0.00% kdeinit 1082 darius 1 960 122M 7268K select 0:40 0.00% kdeinit No wonder my system is thrashing :) Does anyone know why 3.5.0 seems to be using so much more memory? I did recently update to the latest -current (ie new malloc implementation) but the the sluggish behaviour was still present prior to that (although maybe not as bad) I have.. lrwxrwxrwx 1 root wheel 2 Oct 8 22:01 /etc/malloc.conf -> aj -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpLX41AgpmRB.pgp Description: PGP signature
Re: KDE refuses new processes when network goes away
Par Leijonhufvud wrote: > When I start it up with network up everything is fine, but if the > network dies (we have a slightly dodgy ADSL, which periodically plays > yo-yo) it will refuse to open new processes or windows. > > Is it (likely to be) a KDE, xopen or freebsd problem? Is your /etc/hosts correct? I've seen this happen when the local hostname (i.e., the output of `hostname`) cannot be resolved. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
KDE refuses new processes when network goes away
This is on a labtop (IBM Thinkpad R50e) running 5.3-RELEASE. When I start it up with network up everything is fine, but if the network dies (we have a slightly dodgy ADSL, which periodically plays yo-yo) it will refuse to open new processes or windows. Is it (likely to be) a KDE, xopen or freebsd problem? /Par -- Par Leijonhufvud [EMAIL PROTECTED] This is not a book to be set aside lightly. It should be thrown with great force! -- Dorothy Sayers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.10 and KDE 3.3.1 == broken :(
On Tue, 7 Dec 2004 15:48, Daniel O'Connor wrote: > > Needless to say that is quite untested/unsupported by us, and if you've > > been using any packages there's a good chance things aren't fitting > > together so well. I do hope Xorg 6.8.1 won't break KDE on 4.x once it's > > in ports, but I can't discount the possibility. > > I built Xorg from source using patches Eric Anholt supplied. Works in 5.x > ;) > > I guess I'll try XFree86 on this box and see if it has an effect. Well, going back to XFree86 works.. How annoying :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpbpxF0ikf3D.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Tue, 7 Dec 2004 15:45, Michael Nottebrock wrote: > Okay. Looking at your list of installed packages I see that you > > 1.) run Xorg > > and > > 2.) run Xorg 6.8.1 > > Needless to say that is quite untested/unsupported by us, and if you've > been using any packages there's a good chance things aren't fitting > together so well. I do hope Xorg 6.8.1 won't break KDE on 4.x once it's in > ports, but I can't discount the possibility. I built Xorg from source using patches Eric Anholt supplied. Works in 5.x ;) I guess I'll try XFree86 on this box and see if it has an effect. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpMhVfnpFVmU.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Tuesday, 7. December 2004 00:41, Daniel O'Connor wrote: > On Tue, 7 Dec 2004 00:55, Michael Nottebrock wrote: > > On Monday, 6. December 2004 15:03, Daniel O'Connor wrote: > > > That didn't work :( > > > > What about the icons. Do you have by chance downloaded an icontheme from > > kde-look.org via the icon-theme controlpanel and are using that now? > > No, I haven't done that. > > I did try moving my .kde and .kderc out of the way and rerunning it, but it > made no difference. Okay. Looking at your list of installed packages I see that you 1.) run Xorg and 2.) run Xorg 6.8.1 Needless to say that is quite untested/unsupported by us, and if you've been using any packages there's a good chance things aren't fitting together so well. I do hope Xorg 6.8.1 won't break KDE on 4.x once it's in ports, but I can't discount the possibility. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpQ1LzKIl3jm.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Tue, 7 Dec 2004 00:55, Michael Nottebrock wrote: > On Monday, 6. December 2004 15:03, Daniel O'Connor wrote: > > That didn't work :( > > What about the icons. Do you have by chance downloaded an icontheme from > kde-look.org via the icon-theme controlpanel and are using that now? No, I haven't done that. I did try moving my .kde and .kderc out of the way and rerunning it, but it made no difference. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpAzf51eV8US.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Monday, 6. December 2004 15:03, Daniel O'Connor wrote: > That didn't work :( What about the icons. Do you have by chance downloaded an icontheme from kde-look.org via the icon-theme controlpanel and are using that now? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp1LcuGaUKxt.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Mon, 6 Dec 2004 11:59, Daniel O'Connor wrote: > Hmm, it's pretty big :) > I just built a list of ports KDE depends on and I'm upgrading them all (big > hammer approach) That didn't work :( Here's the list.. Hermes-1.3.2 ImageMagick-6.0.6.2 ORBit-0.5.17 ORBit2-2.12.0 OpenEXR-1.2.1 WebMagick-2.03p3_4,1 WordNet-2.0 Xaw3d-1.5 a2ps-a4-4.13b_2 aalib-1.4.r5_1 acroread-5.09 adns-1.0_1 afm-1.0 ap-utils-1.3 apache+mod_ssl-1.3.33+2.8.22 apsfilter-7.2.5_1 arc-5.21e.8_1 arts-1.3.1,1 artswrapper-1.2.1_1 aspell-0.60.1.1 atk-1.8.0 audacity-1.2.1 autoconf-2.53_3 autoconf-2.59_2 autoconf213-2.13.000227_4 automake-1.5_2,1 automake-1.9.3 automake14-1.4.5_9 bash-2.05b.004 bind-8.2.3 bind9-9.2.1 bing-1.0.4 bison-1.28 bitstream-vera-1.10 bogofilter-0.15.13.2 bonobo-1.0.22_1 bzip2-1.0.1 cclient-2001,1 cdparanoia-3.9.8_7 cdrtools-2.0.3_4 compat3x-i386-4.4.20020925 cpuburn-1.4 cups-base-1.1.22.0 cups-lpr-1.1.19.0 cvsup-16.1h cyrus-imapd-2.2.10 cyrus-sasl-2.1.20 cyrus-sasl-saslauthd-2.1.20 db3-3.3.11,1 db4-4.0.14_1,1 db41-4.1.25_1 dctc-0.84.1 ddclient-3.6.3 desktop-file-utils-0.7_1 dict-1.4.9 dircproxy-1.0.5 djbfft-0.76_1 docbook-1.2 docbook-241 docbook-3.0 docbook-3.1 docbook-4.0 docbook-4.1 docbook-sk-4.1.2 docbook-xml-4.2 docbook-xsl-1.59.1 dri-5.0.2,1 dvips-5.76 edonkey-gui-gtk-0.5.0 eel2-2.4.0 epic4-1.0.1 esound-0.2.29 etcmerge-0.3_2 ethereal-0.10.6 expat-1.95.8 faces-1.6.1 fam-2.6.9_6 ffmpeg-0.4.8 flac-1.1.0_3 fontconfig-2.2.3,1 freetype-1.3.1_2 freetype2-2.1.7_3 fribidi-0.10.4_1 fxtv-1.03 gail-1.4.0 gal2-1.99.9 galeon2-1.3.17_1 gcc-3.1.1_20020726 gcc-3.3.5_20040901 gconf-1.0.9_5 gconf2-2.8.1 gd-2.0.33,1 gdbm-1.8.3 gdk-pixbuf-0.22.0_2 gengetopt-2.11 gettext-0.13.1_1 ghostscript-afpl-8.00_1 gimp-1.2.3_2,1 glib-1.2.10_11 glib-2.4.8 glimpse-4.12.6 gmake-3.80_2 gnet-1.1.4 gnocatan-0.8.1.16 gnome-icon-theme-1.0.9 gnomecanvas-0.22.0 gnomedb-0.2.96_1 gnomedesktop-2.4.0 gnomehier-1.0_20 gnomekeyring-0.2.1_1 gnomelibs-1.4.2_1 gnomemimedata-2.4.2 gnomepanel-2.4.0 gnomepilot2-2.0.10 gnomeprint-0.37 gnomespell-1.0.5 gnomevfs2-2.8.3_1 gnupg-1.2.6 gob2-2.0.6 gocr-0.39 gqmpeg-gnome-0.19.0 graphviz-1.16 gsfonts-8.11_2 gsl-1.4 gtar-1.13.25 gtk-1.2.10_12 gtk-2.4.14 gtk-engines2-2.2.0 gtkhtml3-3.0.8 gtypist-2.6.2 guile-1.6.4_2 gv-3.5.8 hdf-4.1r3 healthd-0.7.9 help2man-1.29 hicolor-icon-theme-0.5 hpijs-1.3.1 html2ps-A4-1.0 iconv-2.0_1 id3lib-3.8.3_1 imake-6.8.1 imap-uw-4.5 imlib-1.9.15_1 intltool-0.25 isc-dhcp3-server-3.0.1.r14_3 iso8879-1986 ispell-3.1.20 ja-jcode.pl-2.10 ja-p5-jcode.pl-2.10 jade-1.2.1_1 jasper-1.701.0 javavmwrapper-1.4 jdk-1.3.1p6_2 jdk-doc-1.1.8 jpeg-6b_3 kde-3.3.1 kdeaccessibility-3.3.1 kdeaddons-3.3.1 kdeaddons-atlantikdesigner-3.3.1 kdeaddons-kaddressbook-plugins-3.3.1 kdeaddons-kate-plugins-3.3.1 kdeaddons-kfile-plugins-3.3.1 kdeaddons-kicker-applets-3.3.1 kdeaddons-knewsticker-scripts-3.3.1 kdeaddons-konq-plugins-3.3.1 kdeaddons-ksig-3.3.1 kdeaddons-noatun-plugins-3.3.1 kdeaddons-renamedlg-plugins-3.3.1 kdeaddons-vimpart-3.3.1 kdeadmin-3.3.1 kdeartwork-3.3.1 kdebase-3.3.1 kdebase-konqueror-nsplugins-3.3.1 kdeedu-3.3.1 kdegames-3.3.1 kdegraphics-3.3.1 kdegraphics-kamera-3.3.1 kdegraphics-kooka-3.3.1 kdegraphics-kuickshow-3.3.1 kdelibs-3.3.1 kdemultimedia-3.3.1 kdemultimedia-mpeglib_artsplug-3.3.1 kdemultimedia-xine_artsplugin-3.3.1 kdenetwork-3.3.1_1 kdepim-3.3.1_2 kdesdk-3.3.1 kdetoys-3.3.1 kdeutils-3.3.1 kdeutils-klaptopdaemon-3.3.1 kdevelop-3.1.1 kdewebdev-3.3.1,2 koffice-1.3.4,1 lame-3.96.1 lcms-1.13_1,1 lftp-3.0.9 lha-1.14i_6 libIDL-0.8.4 libXft-2.1.6 liba52-0.7.4_1 libao-0.8.3_1 libart_lgpl2-2.3.16 libaudiofile-0.2.6 libbonobo-2.8.0_1 libbonoboui-2.4.0 libdvdcss-1.2.8_1 libdvdread-0.9.4_1 libevent-0.7.a libexif-0.6.10 libfpx-1.2.0.4_1 libgda-0.2.96_1 libglade-0.17_2 libglade2-2.4.0 libglut-6.0.1 libgnome-2.6.1.2 libgnomecanvas-2.6.1.1 libgnomeprint-2.3.1 libgnomeprintui-2.3.1 libgnomeui-2.6.1.1 libgnugetopt-1.2 libgphoto2-2.1.4_4 libgsf-1.10.1 libiconv-1.9.2_1 libicq-0.33 libidn-0.5.12 libijs-0.34 libltdl-1.5 libmad-0.15.1b_1 libmal-0.40 libmcrypt-2.5.7_1 libmikmod-3.1.7 libmng-1.0.8 libmpeg2-0.3.1_1 libmusicbrainz-2.1.1 libnet-1.0.2a libogg-1.1.2,3 libpaper-1.1.14 libproplist-0.10.1 librsvg2-2.4.0 libsoup-1.99.23 libtool-1.3.5_2 libtool-1.5.6_1 libtunepimp-0.3.0_1 libungif-4.1.3 libunicode-0.4_2 libusb-0.1.7_1 libvorbis-1.1.0,3 libwmf-0.2.5_1 libwnck-2.4.0.1 libwww-5.3.1 libxine-1.0.r5_3 libxml-1.8.17_3 libxml2-2.6.16 libxslt-1.1.12 licq-base-1.1.0-20020312 licq-console-1.2.7 licq-qt-gui-1.1.0-20020312 lilypond-1.6.0 linc-1.0.3_2 linux-edonkey-core-0.50.1,1 linux-expat-1.95.5_1 linux-fontconfig-2.1_1 linux-gtk-1.2_2 linux-realplayer-8.cs2 linux_base-7.1_7 linuxdoc-1.1 lsof-4.73.1 lynx-ssl-2.8.5 m4-1.4.1 mad-0.14.2b_2 mailman-2.1.5_1 metamail-2.7_2 mgetty-1.1.28.01.10 mhash-0.8.9 mhonarc-2.3.3 mikmod-3.1.6 mimedefang-2.44 mkcatalog-1.1 mm-1.3.0 mod_perl-1.24 mozilla-1.7.3_3,2 mp3info-gtk-0.8.4 mpeg2codec-1.2 mpg123-0.59r_15 mpg321-0.2.10_2 mplayer-fonts-0.50 mplayer-gtk-0
Re: 4.10 and KDE 3.3.1 == broken :(
On Sun, 5 Dec 2004 22:36, Michael Nottebrock wrote: > > konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown > > action : searchProvider konqueror: ERROR: Error in > > BrowserExtension::actionSlotMap(), unknown action : searchProvider > > Those can be ignored (just fyi). OK, wasn't sure if there was some thread related change recently or so :) > > Anyone seen this problem and know a fix? :) > > I *think* I came across this, but it's too long ago, I can't remember what > caused it (but I'm quite sure it was no bug in KDE). Can you provide the > list of installed packages on that machine? Hmm, it's pretty big :) I just built a list of ports KDE depends on and I'm upgrading them all (big hammer approach) Thanks for your help. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpKjfK1k6YtB.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Sunday, 5. December 2004 13:06, Michael Nottebrock wrote: > On Sunday, 5. December 2004 12:07, Daniel O'Connor wrote: > > Hi, > > I upgraded a machine here to KDE 3.3.1 (as well as Qt and Arts) but now > > Konqueror is dying :( > > > > I initially used packages, but after it didn't work I rebuilt everything > > from the port, but it still behaves the same. > > > > If I run konq from a terminal it starts, but if I type anything it blows > > up.. > > konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown > > action : searchProvider konqueror: ERROR: Error in > > BrowserExtension::actionSlotMap(), unknown action : searchProvider > > Those can be ignored (just fyi). > > > Anyone seen this problem and know a fix? :) > > I *think* I came across this, but it's too long ago, I can't remember what > caused it (but I'm quite sure it was no bug in KDE). Can you provide the > list of installed packages on that machine? I just remembered where I saw this before: With KDE 3.3.1 and some custom iconset (IIRC gorilla-svg). Are you using any custom icons? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpime3SQDBxy.pgp Description: PGP signature
Re: 4.10 and KDE 3.3.1 == broken :(
On Sunday, 5. December 2004 12:07, Daniel O'Connor wrote: > Hi, > I upgraded a machine here to KDE 3.3.1 (as well as Qt and Arts) but now > Konqueror is dying :( > > I initially used packages, but after it didn't work I rebuilt everything > from the port, but it still behaves the same. > > If I run konq from a terminal it starts, but if I type anything it blows > up.. > konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown > action : searchProvider konqueror: ERROR: Error in > BrowserExtension::actionSlotMap(), unknown action : searchProvider Those can be ignored (just fyi). > Anyone seen this problem and know a fix? :) I *think* I came across this, but it's too long ago, I can't remember what caused it (but I'm quite sure it was no bug in KDE). Can you provide the list of installed packages on that machine? -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpf7hrenf1hh.pgp Description: PGP signature
4.10 and KDE 3.3.1 == broken :(
Hi, I upgraded a machine here to KDE 3.3.1 (as well as Qt and Arts) but now Konqueror is dying :( I initially used packages, but after it didn't work I rebuilt everything from the port, but it still behaves the same. If I run konq from a terminal it starts, but if I type anything it blows up.. konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown action : searchProvider konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown action : searchProvider KCrash: Application 'konqueror' crashing... QThread: internal error: zero data for running thread. The backtrace shows nothing useful.. This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtrace s, or the stack frame was seriously corrupted in the crash. (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...0xbfbfffa8 in ?? () #0 0xbfbfffa8 in ?? () #1 0x29203c82 in pthread_cond_timedwait () from /usr/lib/libc_r.so.4 #2 0x291eb395 in _thread_gc () from /usr/lib/libc_r.so.4 #3 0x291c5240 in _thread_start () from /usr/lib/libc_r.so.4 #4 0x0 in ?? () I can rebuild with debugging symbols but.. so slow to compile :( Anyone seen this problem and know a fix? :) Thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpQPhUgo5OQG.pgp Description: PGP signature
Re: 5.3-RELEASE kde 3.3 and pf
On Wed, 2004-Nov-10 09:22:39 -0500, Michael Butler wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >> Maybe you should allow everything on lo0, in and out. > >127/8 should always be allowed on the loopback interface, >127/8 should always be dropped from all other interfaces. > >I am "uncomfortable" saying that everything should be allowed .. I agree with the latter but the former is unnecessarily restrictive. By default, FreeBSD generates a static route to `hostname` via lo0. The default ipfw rules are: 100 pass all from any to any via lo0 200 deny all from any to 127.0.0.0/8 300 deny ip from 127.0.0.0/8 to any -- Peter Jeremy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE kde 3.3 and pf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Maybe you should allow everything on lo0, in and out. 127/8 should always be allowed on the loopback interface, 127/8 should always be dropped from all other interfaces. I am "uncomfortable" saying that everything should be allowed .. Michael Butler CISSP Security Consultant Savvis Communications www.savvis.net PGP Key ID: 0x5E873CC5 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBkiQviJykeV6HPMURAuGvAKCxPvD2JBnymAZi6DSGv+h39whQoQCfSp+x TmQ7x0bqDw49rGjemk8WQUg= =Y6/E -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE kde 3.3 and pf
* Gunnar Flygt <[EMAIL PROTECTED]> (20041110 14:48): > What is it that makes KDE so slow when using pf with these simple rules. > Have I missed something? Maybe you should allow everything on lo0, in and out. -- olive ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE kde 3.3 and pf
I reply to my own question. Since I found out it was pf causing this I
started to use tcpdump on pflog0 and found that traffic from 127.0.0.1
to 127.0.0.1 was blocked. So I added as in the examples for ipf :
# allow localhost
pass in quick on lo0
pass out quick on lo0
after the antispoof rule in pf.conf, and now KDE is loading quick as
without pf. Is this something that should perhaps be in the example file
for pf? Or are there any security reasons for not having it?
On Wed, Nov 10, 2004 at 02:48:54PM +0100, Gunnar Flygt wrote:
> I've had problems with DKE 3.3 since I upgraded to 5.3-RELEASE.
> I compared the same machine (Dell Latitude D600) with a different HD
> where Gentoo Linux (Sorry for that:) resides. Om the Gentto box KDE 3.3
> starts promply from kdm, no extra delays, but with FreeBSD 5.3 it takes
> about 2 minutes to get a running KDE environment.
>
> Got the "briliant" idea to stop pf before starting kdm AND alas KDE
> starts as fast as on the Gentoo system. (Actually it is even faster than
> login on the gentoo system:)
>
> Here is my /etc/pf.conf:
>
> # $FreeBSD: src/etc/pf.conf,v 1.1.2.1 2004/09/17 18:27:14 mlaier Exp $
> # $OpenBSD: pf.conf,v 1.21 2003/09/02 20:38:44 david Exp $
> #
> # See pf.conf(5) and /usr/share/examples/pf for syntax and examples.
> # Required order: options, normalization, queueing, translation, filtering.
> # Macros and tables may be defined and used anywhere.
> # Note that translation rules are first match while filter rules are last
> match.
>
> # Macros: define common values, so they can be referenced and changed easily.
> ext_if="bge0" # replace with actual external interface name i.e., dc0
>
> # Normalization: reassemble fragments and resolve or reduce traffic
> ambiguities.
> scrub in all
>
> # block all incoming packets but allow ssh, pass all outgoing tcp and udp
> # connections and keep state, logging blocked packets.
> block in log all
> antispoof for { lo, $ext_if }
> pass in on $ext_if proto tcp from any to $ext_if port 22 keep state
> pass out on $ext_if proto { tcp, udp } all keep state
> pass out quick proto icmp from any to any keep state
> pass in quick proto icmp from any to any
>
> # drop without log
> block in proto { tcp, udp } from any to any port 134 >< 140
> block in proto tcp from any to any port = 515
> block in from any to 255.255.255.255
> # my local network Class B
> block in from any to yyy.xx.255.255
> block in from any to 224.0.0.0/4
>
> What is it that makes KDE so slow when using pf with these simple rules.
> Have I missed something?
>
> --
> Gunnar Flygt
> SR Datadrift
> Sveriges Radio
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Gunnar Flygt
SR Datadrift
Sveriges Radio
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3-RELEASE kde 3.3 and pf
I've had problems with DKE 3.3 since I upgraded to 5.3-RELEASE.
I compared the same machine (Dell Latitude D600) with a different HD
where Gentoo Linux (Sorry for that:) resides. Om the Gentto box KDE 3.3
starts promply from kdm, no extra delays, but with FreeBSD 5.3 it takes
about 2 minutes to get a running KDE environment.
Got the "briliant" idea to stop pf before starting kdm AND alas KDE
starts as fast as on the Gentoo system. (Actually it is even faster than
login on the gentoo system:)
Here is my /etc/pf.conf:
# $FreeBSD: src/etc/pf.conf,v 1.1.2.1 2004/09/17 18:27:14 mlaier Exp $
# $OpenBSD: pf.conf,v 1.21 2003/09/02 20:38:44 david Exp $
#
# See pf.conf(5) and /usr/share/examples/pf for syntax and examples.
# Required order: options, normalization, queueing, translation, filtering.
# Macros and tables may be defined and used anywhere.
# Note that translation rules are first match while filter rules are last match.
# Macros: define common values, so they can be referenced and changed easily.
ext_if="bge0" # replace with actual external interface name i.e., dc0
# Normalization: reassemble fragments and resolve or reduce traffic ambiguities.
scrub in all
# block all incoming packets but allow ssh, pass all outgoing tcp and udp
# connections and keep state, logging blocked packets.
block in log all
antispoof for { lo, $ext_if }
pass in on $ext_if proto tcp from any to $ext_if port 22 keep state
pass out on $ext_if proto { tcp, udp } all keep state
pass out quick proto icmp from any to any keep state
pass in quick proto icmp from any to any
# drop without log
block in proto { tcp, udp } from any to any port 134 >< 140
block in proto tcp from any to any port = 515
block in from any to 255.255.255.255
# my local network Class B
block in from any to yyy.xx.255.255
block in from any to 224.0.0.0/4
What is it that makes KDE so slow when using pf with these simple rules.
Have I missed something?
--
Gunnar Flygt
SR Datadrift
Sveriges Radio
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kde KUser - expires accounts
On Tue, Jul 01, 2003 at 11:50:44AM -0500, Rick Flosi wrote: > I used KUser to add a user to my system and after saving the changes I > made KUser expired all user accounts except the newly created one. > Does anyone know if there is a patch for KUser to fix this problem. I > found some discussion about this but it was from Feb. 2003 and I was > unable to find a patch. I'm just curious what the "problem" is? If you tell KUser to expire all accounts, surely, that's what it should do... personally, I would advise that the maintainers of KUser take the option away. I can't think of a practical application where you would need to expire all users. -- Paul Robinson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE apps crashing
On Sat, 29 Mar 2003 05:20, Antoine Jacoutot wrote: > On Friday 28 March 2003 12:56, Roland Jesse wrote: > > Are you saying, you cannot use Qt's OpenGL widgets with NVidia's > > binary drivers? > > I really don't know, my knowledge is very basic about it, but this is the > way the crashes stopped for me. > One other thing you could do is use the XFree "nv" driver and not the > NVidia one. I am running the nVidia drivers and using KDE with no problems. [guppy 14:54] ~ >uname -a FreeBSD guppy.dons.net.au 5.0-CURRENT FreeBSD 5.0-CURRENT #6: Wed Mar 5 22:43:49 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GUPPY i386 [guppy 14:54] ~ >ll -d /var/db/pkg/kde* /var/db/pkg/qt* drwxr-xr-x 2 root wheel 512 Mar 6 21:59 /var/db/pkg/kde-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 22:21 /var/db/pkg/kdeaddons-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 22:21 /var/db/pkg/kdebase-3.1_1 drwxr-xr-x 2 root wheel 512 Mar 6 20:58 /var/db/pkg/kdegames-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 20:58 /var/db/pkg/kdegraphics-3.1 drwxr-xr-x 2 root wheel 512 Mar 29 13:50 /var/db/pkg/kdelibs-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 22:21 /var/db/pkg/kdemultimedia-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 20:58 /var/db/pkg/kdenetwork-3.1 drwxr-xr-x 2 root wheel 512 Mar 6 20:58 /var/db/pkg/kdeutils-3.1 drwxr-xr-x 2 root wheel 512 Mar 29 13:50 /var/db/pkg/qt-3.1.1_4 [guppy 14:54] ~ >X -version XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Build Date: 06 March 2003 >From XFree86.log -> (II) LoadModule: "nvidia" (II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.3203 Module class: XFree86 Video Driver I have a GeForce 4 Ti4200. My wife's PC has a TNT2 M64 (with AGP disabled or the PC hangs). It runs KDE 3.0, 4.7-STABLE, X 4.2.1. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
