| Very nice!
Jan 10 2007 on content Mile-High |
This is now my desktop background. Thank you! |
|  | | Great program
Nov 22 2006 on content KTorrent |
After using Azureus which has a quite slow GUI and doesn't fit well into my KDE desktop, I switched to KTorrent and am very satisfied. So thank you very much for this great program! |
| | | *SOLVED*
Oct 30 2006 on content KVideoEncoder |
Ok, the new ebuild has successfully compiled on two different systems with Qt 3 and 4. In that case Qt 4's qmake is in /usr/bin and usually picked first. The ebuild takes care of that now. |
| | | Re: Re: Re: configur/mak
Oct 30 2006 on content KVideoEncoder |
All KDE programs currently need Qt 3 as KDE itself doesn't run with Qt 4. This will change once KDE 4 comes out.
On Gentoo you'll automatically get the Qt development files when you install Qt 3. In case you have both Qt 3 and Qt 4 installed, I guess the configure script will pick the Qt 4 qmake binary. Please try the ebuild I've sent to you if it works for you. I'm installing Qt 4.1 in the meantime so I can have a look at this, too. |
| | | Gentoo ebuild
Oct 29 2006 on content KVideoEncoder |
Thank you for this application! I have sent my Gentoo ebuild to you via email, please publish it here for download. |
| | | Great
Oct 21 2006 on content Polyester |
It's my favorite style now, thank you very much! Maybe it can be included in KDE4? |
| | | Re: More verbose errors
Apr 24 2006 on content Roaring Penguin PPPoE Kontrol |
I cannot show errors when you don't have permission to execute pppoe-*. Those are started via sudo, and sudo would prompt you for a password, but you don't see that dialog.
Wrong credentials will be logged in /var/log/messages, for example:
Apr 24 19:24:25 mosher sudo: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/pppoe-start
Apr 24 19:24:25 mosher pppd[2804]: pppd 2.4.3 started by root, uid 0
Apr 24 19:24:25 mosher pppd[2804]: Using interface ppp0
Apr 24 19:24:25 mosher pppd[2804]: Connect: ppp0 /dev/pts/4
Apr 24 19:24:25 mosher pppoe[2805]: PADS: Service-Name: ''
Apr 24 19:24:25 mosher pppoe[2805]: PPP session is 1227 (0x4cb)
Apr 24 19:24:27 mosher pppd[2804]: PAP authentication failed
Apr 24 19:24:27 mosher pppd[2804]: Connection terminated.
Apr 24 19:24:27 mosher pppoe[2805]: Session 1227 terminated -- received PADT from peer
Apr 24 19:24:27 mosher pppoe[2805]: Sent PADT
Apr 24 19:24:27 mosher pppd[2804]: Exit.
Apr 24 19:24:27 mosher pppoe-connect: PPPoE connection lost; attempting re-connection.
The interesting line is this one:
Apr 24 19:24:27 mosher pppd[2804]: PAP authentication failed
This is what a timeout looks like:
Apr 24 19:27:31 mosher sudo: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/pppoe-start
Apr 24 19:27:31 mosher pppd[3704]: pppd 2.4.3 started by root, uid 0
Apr 24 19:27:31 mosher pppd[3704]: Using interface ppp0
Apr 24 19:27:31 mosher pppd[3704]: Connect: ppp0 /dev/pts/4
Apr 24 19:28:02 mosher pppd[3704]: LCP: timeout sending Config-Requests
Apr 24 19:28:02 mosher pppd[3704]: Connection terminated.
Apr 24 19:28:02 mosher pppd[3704]: Modem hangup
Apr 24 19:28:06 mosher pppoe[3705]: Timeout waiting for PADO packets
Apr 24 19:28:06 mosher pppd[3704]: Exit.
Apr 24 19:28:06 mosher pppoe-connect: PPPoE connection lost; attempting re-connection.
Again this is the interesting one:
Apr 24 19:28:02 mosher pppd[3704]: LCP: timeout sending Config-Requests
I don't know another way to get error codes, the script pppoe-start only gives 0 or 1, meaning success or failure. The problem with /var/log/messages is, that file is not world readable, so I cannot easily extract the error information from pppoe-start. |
| |
| |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
