Hi all!
I've been using TDE 3.5.13 since mid-October, first with the night builds. With the release in November, I try to use as my main desktop, but now it seems I have to go back to "old" KDE 3.5.10, because of some problems with TDE - not so many, but still important one's.
My system is a Debian squeeze, so every day I do a "apt-get update" hopefully looking for some correction for the bugs, but every time no updates.
So, I would like to know if 3.5.13 will have some bugs correction, and when??
Or will I have to wait for the next main release in estimated 6 months time?
Thanks!
Hi all!
I've been using TDE 3.5.13 since mid-October, first with the night builds. With the release in November, I try to use as my main desktop, but now it seems I have to go back to "old" KDE 3.5.10, because of some problems with TDE - not so many, but still important one's.
My system is a Debian squeeze, so every day I do a "apt-get update" hopefully looking for some correction for the bugs, but every time no updates.
So, I would like to know if 3.5.13 will have some bugs correction, and when??
Or will I have to wait for the next main release in estimated 6 months time?
Thanks!
Most likely you will have to wait for the next release. I assume you have bug reports in for the problems you are experiencing?
Tim
On Sat, Dec 3, 2011 at 9:19 PM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Most likely you will have to wait for the next release. I assume you have bug reports in for the problems you are experiencing?
Tim
Hi Tim,
No, I haven't yet, partly for lack of time, partly because I was waiting that some upgrades could cure the issues.
On Sat, Dec 3, 2011 at 10:52 PM, David Hare davidahare@gmail.com wrote:
Please state here also, what those problems are in addition to bug reports. Others here use also TDE as main desktop and may be able to help with at least workarounds. It's also possible, you may have misconfigured something
You cannot go back to "old KDE 3.5.10" on Squeeze (at least not cleanly)
Regards, David
Hi David,
You are right, I should have asked for some help! I had experienced some aleatory crashes, mainly when logging in and out.
But, my main problems/blockers are (in order):
- Irc does not work in Kopete - my .xsession-errors file gets too long with errors from Trinity, after only two days it is more than 200Kb - see below - compiz is not working: no kde/tde window decorator that works (segfaults, maybe just a recompilation could cure the problem??), and I try to use the gtk-decorator, but that has some issues and is not a solution (I use compiz a lot)
Also, it seems there are some memory leaks, for instance with Kpdf and large pdf files, and Konqueror with some io-slaves, but that I have to dig deeper before I draw any conclusion.
- .xsession-errors (excerpt):
... kdeinit: Got EXT_EXEC 'kio_uiserver' from launcher. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing kdeinit: PID 4084 terminated. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing kdeinit: Got EXEC_NEW 'kio_thumbnail' from launcher. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4000010 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x42000e4 kdeinit: Got EXT_EXEC 'ksysguard' from launcher. Could not load library! Trying exec.... QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing kdeinit: PID 4091 terminated. kdeinit: PID 4131 terminated. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing Killed kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher. kbuildsycoca running... Reusing existing ksycoca DCOP Cleaning up dead connections. kdeinit: PID 4173 terminated. kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher. kbuildsycoca running... Reusing existing ksycoca kdeinit: PID 4185 terminated. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600003 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600009 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600015 fixme:htmlhelp:HtmlHelpW HH case HH_CLOSE_ALL not handled. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600001 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600001 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600001 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4600001 kdeinit: PID 4403 terminated. kdeinit: Got EXEC_NEW 'kio_about' from launcher. kdeinit: Got EXEC_NEW 'kio_file' from launcher. kdeinit: Got EXEC_NEW 'kio_thumbnail' from launcher. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing kdeinit: PID 4535 terminated. kdeinit: PID 2684 terminated. kdeinit: PID 4537 terminated. kdeinit: Got EXEC_NEW 'kio_thumbnail' from launcher. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing kdeinit: Got EXT_EXEC 'kwrite' from launcher. QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing QSettings::sync: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing ...
etc... and it keeps repeating...
On 03/12/11 22:36, Jorge Gonçalves wrote:
Hi all!
I've been using TDE 3.5.13 since mid-October, first with the night builds. With the release in November, I try to use as my main desktop, but now it seems I have to go back to "old" KDE 3.5.10, because of some problems with TDE - not so many, but still important one's.
Please state here also, what those problems are in addition to bug reports. Others here use also TDE as main desktop and may be able to help with at least workarounds. It's also possible, you may have misconfigured something
You cannot go back to "old KDE 3.5.10" on Squeeze (at least not cleanly)
Regards, David
On Sat, Dec 3, 2011 at 10:52 PM, David Hare davidahare@gmail.com wrote:
You cannot go back to "old KDE 3.5.10" on Squeeze (at least not cleanly)
Regards, David
Yes, I can ! ;-)
Before moving to Trinity, I did a full backup of my Lenny/Squeeze Kde 3.5.10 partition, so now is just a matter of restoring it!
(my data is on a separate partition)
On 04/12/11 12:21, Jorge Gonçalves wrote:
On Sat, Dec 3, 2011 at 10:52 PM, David Haredavidahare@gmail.com wrote:
You cannot go back to "old KDE 3.5.10" on Squeeze (at least not cleanly)
Regards, David
Yes, I can ! ;-)
Before moving to Trinity, I did a full backup of my Lenny/Squeeze Kde 3.5.10 partition, so now is just a matter of restoring it!
(my data is on a separate partition)
It is unclear what is "Lenny/Squeeze Kde 3.5.10 partition"
Kde 3.5.10 is uninstallable in Debian Squeeze and does not even exist in Squeeze repos
Do you mean Debian Lenny, mixed with some Squeeze packages? In which case, you are running a mixed system, not Squeeze proper. That is supportable by it's user only because it would be customised to it's core level!
David
Do you mean Debian Lenny, mixed with some Squeeze packages? In which case, you are running a mixed system, not Squeeze proper. That is supportable by it's user only because it would be customised to it's core level!
That's not necessarily so. You can still get the 3.5.10-2 packages for squeeze whe you use the debian snapshot mirror from 2010/05/28, 15:55:48 [1]. That was my black friday :-/ - I kept a local copy of that repository till Tim came with TDE 3.5.12 :-)
[1] http://snapshot.debian.org/archive/debian/20100528T155548Z/
On Sun, Dec 4, 2011 at 12:23 PM, David Hare davidahare@gmail.com wrote:
On 04/12/11 12:21, Jorge Gonçalves wrote:
On Sat, Dec 3, 2011 at 10:52 PM, David Haredavidahare@gmail.com wrote:
You cannot go back to "old KDE 3.5.10" on Squeeze (at least not cleanly)
Regards, David
Yes, I can ! ;-)
Before moving to Trinity, I did a full backup of my Lenny/Squeeze Kde 3.5.10 partition, so now is just a matter of restoring it!
(my data is on a separate partition)
It is unclear what is "Lenny/Squeeze Kde 3.5.10 partition"
It is the partition in the Hard-drive where I have my main working DE, a (very old) Lenny install, with Kde 3.5.10, that over the months and years has been somehow upgraded to Squeeze.
Kde 3.5.10 is uninstallable in Debian Squeeze and does not even exist in Squeeze repos
Who said I need to install Kde again? I just need to restore my HD partition, as it was prior to November 2001. A 5 minutes job... :-)
Do you mean Debian Lenny, mixed with some Squeeze packages? In which case, you are running a mixed system, not Squeeze proper. That is supportable by it's user only because it would be customised to it's core level!
David
-
David Hare -
Jorge Gonçalves -
Mag. Dr. Nikolaus Klepp -
Timothy Pearson