Thanks for the ideas and help I got home after the bar on the weekend, and asked myself "Self, *hicup* Wonder if there are any upgrades tonight..." so I ran pacman and noticed QT was upgraded..
So on a whim I removed xfree86 again and slaped in X... seeing that I was half cooked I wouldn't have minded if it didn't work and pass out peacefully.
When X was installed I started KDE, and POOF! JPEG's work! Thanks again all for the help
]]>I used KDE for two years and it's just getting buggier all the time.
3.2 series have been really messy. It's a wonderful piece of software but there is others who will catch up with them,hopefully without the bugs. A few months timeout to do some clenup would do good like you said. I checked out the Fluxbox website earlier today and those screenshots looked really nice. But all kde apps don't run standalone or?
BTW, I can't leave X
# id:3:initdefault:
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# x:5:respawn:/usr/X11R6/bin/xdm -nodaemon
x:5:once:/opt/kde/bin/kdm -nodaemon
when I do X restarts after appr 1 min. I want my Vim back.
]]>That site is really scary dp! Maybe I should move along to some other DE. If Fluxbox eventually is getting to 1.0, it's looking very nice indeed!
indeed, yes ... fluxbox is the thing i use while compiling KDE (the week when a new release comes out) - it's not so feature-rich, but is very simple and usefull
kde has a lot of features ... but in my eyes, it needs a time-period, where all the open bugs should be cleaned up (freeze for all new features for e.g. 4 months would be ok, i think)... mostly, because heavy bugs accumulate and if you make a bug by fixing another, this is not a solution (and this happened since 3.2.0 2 times on different bugs)
the thing is: if people make great new features, people are suddenly working on making more other features instead of having a code-cleaning and bug-fixing period
]]>Wow... Thanks
I thought I was going nuts lol Thanks for your help!
If it was a QT problem why did it work in xfree86 and not X?
hmm ... no idea ... maybe qt is built against xfree86 and in X they changed something (as X has some patches - the only difference to xfree86 for now)
Then again I should just shut my yap and read some more huh? LOL
no, being quiet is no solution ... but if it's kde, the bugs.kde.org have a lot of bugs you can surf to find things that maybe are already broken for some reason
at least others that come to the same trouble will find this post and maybe have other info about it and in some time this can be solved too :-)
]]>I thought I was going nuts lol Thanks for your help!
If it was a QT problem why did it work in xfree86 and not X?
Then again I should just shut my yap and read some more huh? LOL
]]>i searched a little the bugs.kde.org ... with some success:
http://bugs.kde.org/show_bug.cgi?id=55863
is very similar to your trouble
also (but older)
http://bugs.kde.org/show_bug.cgi?id=5042
it's QT that causes the trouble, as it seems
]]>If it wasn't for that damed jpeg problem in KDE I would still be with X.. I guess I could always use gnome, or some other gtk wm but I was at my wits end... kuickshow worked at displaying the jpegs, but not kview... it was so hit and miss I asked myself..
"Are you sure you are comfortable enough with Linux?" almost thought that I should hang up my towel and go back to M$...
Then I pulled my head outta my arse and went to xfree86 lol
]]>My own experience is that you don't mess with x.
It can take a week to get a mouse going.
xerxes2 wrote:Hello soffcore, welcome to Arch!
I think that the reason you have not got any answers is because most people stick with xfree.
So am I.Maybe if things change and xfree and xorg are becoming incompatible in the future, wich I don't think is gonna happen,you probably choose xorg.
Hope you get your backgrounds back though!
this cannot be said better - thanx for reading my thoughts
Thanks Thought I was being snubbed out LOL I went back to xfree86 and all is well again.. I even went as far as installing xfree86 along side to see if there were any files that were not present in the X package, and all files were present.. weird.. so I gave up for now and went back to X.
Mime-types, libs, all check out.. that is what is so frustrating about this problem.. if I missed a symlink some where I am going to gouge my eyes out with my pencil. lol
Thanks Tho!
]]>Hello soffcore, welcome to Arch!
I think that the reason you have not got any answers is because most people stick with xfree.
So am I.Maybe if things change and xfree and xorg are becoming incompatible in the future, wich I don't think is gonna happen,you probably choose xorg.
Hope you get your backgrounds back though!
this cannot be said better - thanx for reading my thoughts
]]>I think that the reason you have not got any answers is because most people stick with xfree.
So am I.
Maybe if things change and xfree and xorg are becoming incompatible in the future, wich I don't think is gonna happen,you probably choose xorg.
Hope you get your backgrounds back though!
]]>if i understand you right, you have trouble with JPEG images to set as background, but PNG works fine - is this the actual situation?
as i cannot reproduce this (can set all image types as background without problem), here the way i would search for the trouble:
- is the needed libs+kde+x/xfree86 up to date with the repos?
- how is the mime-type for JPEG set in kde? (control panel) --- is "embedding" set to "Show the file in embedded viewer" or "Use 'image' group"?
]]>