By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2552 - Long-standing TDE (KDE3 too) bug: KDesktop bug at startup on slower PCs
Summary: Long-standing TDE (KDE3 too) bug: KDesktop bug at startup on slower PCs
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.1.x [Trinity]
Hardware: Other Linux
: P3 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2015-12-03 12:32 CST by Alex Couture
Modified: 2018-08-30 02:52 CDT (History)
6 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Couture 2015-12-03 12:32:48 CST 
Ever since the KDE 3.5.10 era, when launching TDE on slower computers (such as P4, or a Raspberry Pi), whenever the TDE startup time is slightly longer than usual, I get to following message after the splash disappear:


Error - KDesktop

The process for the file protocol died unexpectedly.


and I'm stuck with no icons on the desktop, but the rest of TDE works as usual.


I am almost sure that it is just a timeout who generates the alarm too soon, but it might also be a ''real'' bug.

But, what could be interesting could be to do as in KDE 4 or Plasma 5; to relaunch automatically the crashed component.



Have a great day!

-Alexandre
Comment 1 linux 2016-09-27 01:24:57 CDT 
Got the same bug after upgrading from 3.5.13 to 14.0.3. I need to kill kdesktop and run it again to get icons on the desktop.
Comment 2 Q4OS Team 2016-09-27 01:42:14 CDT 
Yes, I can confirm exactly the same issue on every TDE version used.
Comment 3 Michele Calgaro 2018-08-04 05:45:43 CDT 
Is any of you able to add any more info the next time this happens?
Also can you verify if it still applies to R14.0.5 as well?
Comment 4 Q4OS Team 2018-08-04 12:32:24 CDT 
Yes, I notice this issue time by time even with the recent TDE R14.0.5 versions. It can happen in Virtualbox, mostly when the host machine is loaded by another task, or if the guest is lower in memory, for ex. 350 MB or less. It is also presented quite often on Raspberry Pi 1 or other legacy ARM boards.
Comment 5 Alex Couture 2018-08-04 15:31:37 CDT 
Hi,

I don't want to sound rude here, and I also understand TDE has a very small team of devs, but if someone took time to make a bug report, and a few years later the bug has not been solved, it is still more than likely a bug. Nobody will want to report bug if they are closed just because they have not been solved for x number of time. This does not make sense to me.

Michele, as Q4OS Team said, if you have a first-gen Pi, an older PC or a not too fast Virtual Machine (maybe Qemu or even Bochs?), you will see it quite often during TDE startup.

Thank you!
-Alexandre
Comment 6 Michele Calgaro 2018-08-05 01:51:49 CDT 
Thanks Q4OS and Alex.
Nobody is doubting the fact that this is a bug. I have just asked for additional info so that we can try to replicate this bug when/if we ever find the time to look into it :-)
Looks like running TDE on a low performance/low memory VM should bring this bug up, so the question was not invane.