Hello
I've changed from KDE4 to Trinity, because KDE4 is so buggy. Now I'm trying to set up everything, but Trinity appears to be very buggy too. Everything worked fine when I was using KDE 3.5, but now it's a mess. I'm wondering it Trinity and KDE4 get in each other's way.
- I can't set the screen's resolution, refresh rate, or gamma value. It used to be configurable via the control center, but the controls disappeared from there. You can use System/KRandRTray to set the resolution and refresh rate, but it won't remember the setting.
- Amarok crashes since a few days. A few seconds after you start a song, it generates a segmentation fault. I've tired it in KDE4, but it's the same. I've removed and installed the amarok package, but it's still the same. I've removed all amarok related configuration files (those with "amarok" in the name) from ~/.trinity and from ~/.kde, but it stays the same.
Of course the crash manager crashes, when you try to report the bug. :->
- KMail crashed ("aborted") immediately after starting it. When you started it in the terminal, you even got some information about the cause:
kmail(5507)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: !!!!!!! ERROR !!!!!!! - KHTML default stylesheet version mismatch. Aborting. Check your installation. File used was: /opt/trinity/share/apps/khtml/css/html4.css. Expected STYLE_VERSION 1
Then I've tried it in KDE4, and - bingo - it works again, even after going back to Trinity.
- When logging out of Trinity, there sometimes appears an error message that some policy is faulty (I have to write the message down). When logging into KDE4, and into and out of Trinity again, the message disappears.
- The font sizes have a life of their own. Sometimes when I log in, they are huge, and mess up the layout (amarok, for instance). Sometimes they are tiny. When I start amarok, and I get huge fonts, it fixes itself when I quit and start amarok again.
I can configure the fonts in the respective program's settings, but only part of the fonts can be configured there, and changes take effect only sometimes, or only for some font settings. I know that there are some fonts, to be configured in the control center. But that works only sometimes.
There are a lot of places where the fonts are almost unreadaby small (the menus, for instance). I've tried to configure them, but it doesn't work, or it works and goes back again.
This isn't a bug report. I have to take a closer look, first.
I wonder if I'm the only one with all of these problems. If not, how can you live with it? But from what I've seen on the net, Trinity should be quite stable and useable. So what's going on here??
As I have seen it, KDE4 and Trinity are not the best friends, at least on Debian. I'd suggest you get rid of KDE4 first, then start again with trinity.
Am Montag, 4. April 2011 schrieb Volker Wysk:
Hello
I've changed from KDE4 to Trinity, because KDE4 is so buggy. Now I'm trying to set up everything, but Trinity appears to be very buggy too. Everything worked fine when I was using KDE 3.5, but now it's a mess. I'm wondering it Trinity and KDE4 get in each other's way.
- I can't set the screen's resolution, refresh rate, or gamma value. It
used to be configurable via the control center, but the controls disappeared from there. You can use System/KRandRTray to set the resolution and refresh rate, but it won't remember the setting.
- Amarok crashes since a few days. A few seconds after you start a song, it
generates a segmentation fault. I've tired it in KDE4, but it's the same. I've removed and installed the amarok package, but it's still the same. I've removed all amarok related configuration files (those with "amarok" in the name) from ~/.trinity and from ~/.kde, but it stays the same.
Of course the crash manager crashes, when you try to report the bug. :->
- KMail crashed ("aborted") immediately after starting it. When you started
it in the terminal, you even got some information about the cause:
kmail(5507)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: !!!!!!! ERROR !!!!!!! - KHTML default stylesheet version mismatch. Aborting. Check your installation. File used was: /opt/trinity/share/apps/khtml/css/html4.css. Expected STYLE_VERSION 1Then I've tried it in KDE4, and - bingo - it works again, even after going back to Trinity.
- When logging out of Trinity, there sometimes appears an error message
that some policy is faulty (I have to write the message down). When logging into KDE4, and into and out of Trinity again, the message disappears.
- The font sizes have a life of their own. Sometimes when I log in, they
are huge, and mess up the layout (amarok, for instance). Sometimes they are tiny. When I start amarok, and I get huge fonts, it fixes itself when I quit and start amarok again.
I can configure the fonts in the respective program's settings, but only part of the fonts can be configured there, and changes take effect only sometimes, or only for some font settings. I know that there are some fonts, to be configured in the control center. But that works only sometimes.
There are a lot of places where the fonts are almost unreadaby small (the menus, for instance). I've tried to configure them, but it doesn't work, or it works and goes back again.
This isn't a bug report. I have to take a closer look, first.
I wonder if I'm the only one with all of these problems. If not, how can you live with it? But from what I've seen on the net, Trinity should be quite stable and useable. So what's going on here??
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Am Montag 04 April 2011, 12:58:39 schrieb Mag. Dr. Nikolaus Klepp:
As I have seen it, KDE4 and Trinity are not the best friends, at least on Debian. I'd suggest you get rid of KDE4 first, then start again with trinity.
I wasn't aware that there are separate KDE4 and Trinity versions of the KDE applications. I've installed Amarok-Trinity now, and it works perfectly, just as it used to before I had to reinstall my Debian system, when I was still using KDE 3.5.10.
(It's a pity that Amarok-KDE4 won't run with Trinity, because it's amazing! For instance, it will automagically download the lyrics of the song you're listening, and display it... This works about half the time, even for my non- mainstream taste in music...)
KMail-KDE4 almost works. It crashes when it is restarted by the session manager, but otherwise... Guess I should play it safe, and go to KMail- Trinity.
The mess with all the bugs I've encountered, seems to come from the KDE4 applications which are run under Trinity.
The neat inclusion of the KDE4 apps in Trinitiy's menus gives the impression that the integration is meant to work fine; at least that's the impression it gave to me.
Perhaps the KDE4 applications should be placed in a separate menu hierarchy, or some warning message should tell the user that it's unsafe, when using KDE4 apps in Trinity.
I've still got to sort out the font size mess...
Bye, Volker
On Wednesday 06 April 2011 21:13:05 Volker Wysk wrote:
Am Montag 04 April 2011, 12:58:39 schrieb Mag. Dr. Nikolaus Klepp:
As I have seen it, KDE4 and Trinity are not the best friends, at least on Debian. I'd suggest you get rid of KDE4 first, then start again with trinity.
I wasn't aware that there are separate KDE4 and Trinity versions of the KDE applications. I've installed Amarok-Trinity now, and it works perfectly, just as it used to before I had to reinstall my Debian system, when I was still using KDE 3.5.10.
They are very different!!! How would they _not_ have separate applications?
(It's a pity that Amarok-KDE4 won't run with Trinity, because it's amazing! For instance, it will automagically download the lyrics of the song you're listening, and display it... This works about half the time, even for my non- mainstream taste in music...)
Amarok 1.4.10, running on KDE 3.5.10, does this. I haven't tried the Trinity one yet, but I would expect it to be the same.
KMail-KDE4 almost works. It crashes when it is restarted by the session manager, but otherwise... Guess I should play it safe, and go to KMail- Trinity.
The mess with all the bugs I've encountered, seems to come from the KDE4 applications which are run under Trinity.
That has certainly been other people's experience, judging by this list.
The neat inclusion of the KDE4 apps in Trinitiy's menus gives the impression that the integration is meant to work fine; at least that's the impression it gave to me.
Do a little reading before installing?
Perhaps the KDE4 applications should be placed in a separate menu hierarchy, or some warning message should tell the user that it's unsafe, when using KDE4 apps in Trinity.
There have been a lot of warnings on this list.
Lisi
Am Donnerstag 07 April 2011, 00:03:30 schrieb Lisi:
I wasn't aware that there are separate KDE4 and Trinity versions of the KDE applications. I've installed Amarok-Trinity now, and it works perfectly, just as it used to before I had to reinstall my Debian system, when I was still using KDE 3.5.10.
They are very different!!! How would they _not_ have separate applications?
When is comes to Trinit/KDE4, I thought of the desktop, not the applications. I wasn't aware that the KDE3 applications still are around. I had the impression that the Trinity desktop is KDE3 whereas the Trinity applications are KDE4, which are more advanced and better than the KDE3 ones.
(It's a pity that Amarok-KDE4 won't run with Trinity, because it's amazing! For instance, it will automagically download the lyrics of the song you're listening, and display it... This works about half the time, even for my non- mainstream taste in music...)
Amarok 1.4.10, running on KDE 3.5.10, does this. I haven't tried the Trinity one yet, but I would expect it to be the same.
Huh? Are you sure you haven't mistaken the version? I'm running 1.4.10 (on Trinity), and there is definitely no feature like that.
The mess with all the bugs I've encountered, seems to come from the KDE4 applications which are run under Trinity.
That has certainly been other people's experience, judging by this list.
I haven't read the archives.
The neat inclusion of the KDE4 apps in Trinitiy's menus gives the impression that the integration is meant to work fine; at least that's the impression it gave to me.
Do a little reading before installing?
What should I have read?
Perhaps the KDE4 applications should be placed in a separate menu hierarchy, or some warning message should tell the user that it's unsafe, when using KDE4 apps in Trinity.
There have been a lot of warnings on this list.
So Trinity users should be prepared for trouble, and not expect a stable system?
Those KDE4-menu entries introduce an element of bugginess, in an otherwise perfectly stable system. That's how it seems to me.
Happy bug hunting, Volker
(It's a pity that Amarok-KDE4 won't run with Trinity, because it's amazing! For instance, it will automagically download the lyrics of the song you're listening, and display it... This works about half the time, even for my non- mainstream taste in music...)
KMail-KDE4 almost works. It crashes when it is restarted by the session manager, but otherwise... Guess I should play it safe, and go to KMail- Trinity.
The mess with all the bugs I've encountered, seems to come from the KDE4 applications which are run under Trinity.
<snip>
Do these same applications crash when run under KDE4? Or, for that matter, Gnome or XFCE? Remember the Trinity project was started, in part, due to the seemingly inherent bugginess of KDE4 and its associated applications...
Tim
Am Donnerstag 07 April 2011, 00:04:31 schrieb Timothy Pearson:
Do these same applications crash when run under KDE4? Or, for that matter, Gnome or XFCE?
I tried Amarok under KDE4 and Gnome. It crashes in both cases.
Remember the Trinity project was started, in part, due to the seemingly inherent bugginess of KDE4 and its associated applications...
They have (sometimes) good crash handling und bug reporting provisions. It must get stable some day in the (far) future... :->
Bye, Volker
On Wednesday 06 April 2011 02:48:25 pm Volker Wysk wrote:
Am Donnerstag 07 April 2011, 00:04:31 schrieb Timothy Pearson:
Do these same applications crash when run under KDE4? Or, for that matter, Gnome or XFCE?
I tried Amarok under KDE4 and Gnome. It crashes in both cases.
Remember the Trinity project was started, in part, due to the seemingly inherent bugginess of KDE4 and its associated applications...
They have (sometimes) good crash handling und bug reporting provisions. It must get stable some day in the (far) future... :->
AFAIK, KDE-Trinity is also for those who don't want to upgrade/use KDE4, this is the case with me . I don't know how well supported running both versions in parallel is, it may depend on which distro you use. Trinity is rock solid on Debian Squeeze, as long as I run the Trinity DE. Trinity apps can have issues when running under a different DE or WM, in my experience, Windowmaker.
On Debian squeeze I use Okular from KDE4, Debians dependency matrix pulls in a 'ton' of KDE4 stuff, aka libs and such, just to run one app. I have lots of hardware resources so I don't mind... as long as nothing affects my Trinity install. Don't use amarok so no experience there.
<snip>
- I can't set the screen's resolution, refresh rate, or gamma value. It
used to be configurable via the control center, but the controls disappeared from there. You can use System/KRandRTray to set the resolution and refresh rate, but it won't remember the setting.
</snip>
Just a quick comment here; the module you describe was never part of the upstream KDE sources. Instead, it was provided by Ubuntu as part of a failed attempt at a monitor/Xorg configuration utility. The biggest problem with it is that it was written solely in Python, was therefore somewhat slow, and additionally we have no Python devs here to fix it/keep it up to date.
I would strongly suggest the addition of similar functionality to libkrandr (should be somewhat simple), and then the addition of a simple, persistent randr settings manager to kcontrol. I may even do this in the future provided I have enough time. :)
Tim
Am Montag 04 April 2011, 16:10:03 schrieb Timothy Pearson:
Just a quick comment here; the module you describe was never part of the upstream KDE sources. Instead, it was provided by Ubuntu as part of a failed attempt at a monitor/Xorg configuration utility.
Why failed? It worked perfectly fine for me, before it disappeared from the control center.
[...]
I may even do this in the future provided I have enough time. :)
Transcribing the Python source to C or C++ might actually be the fastest and safest way to do it (or parts of it). The Python sources are debuged already. I don't know Python, but I guess it's probably readable, even if you don't know how to program in it.
So how do I get that Ubuntu-Python screen control back? Should I reinstall something? I don't know what I've done before it disappeared. It just wasn't there any longer.
Bye, Volker
Hello
Does anybody have an idea how to get that screen control center module back? It disappeared silently from my installation.
On Tuesday 05 April 2011 06:33:26 Volker Wysk wrote:
So how do I get that Ubuntu-Python screen control back? Should I reinstall something? I don't know what I've done before it disappeared. It just wasn't there any longer.
Bye
Hello Volker,
Does anybody have an idea how to get that screen control center module back? It disappeared silently from my installation.
In my old Ubuntu 9.10-based system the package is called kde-guidance-kde3. I believe that's the one you're referring to. It comes with a screen and display config tool, among others.
Sanne
-
Greg Madden -
Lisi -
Mag. Dr. Nikolaus Klepp -
Sanne -
Timothy Pearson -
Volker Wysk