Bug 328012 - Default Activities gives a broken activity
Summary: Default Activities gives a broken activity
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: activities (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-24 15:03 UTC by Jonathan Riddell
Modified: 2018-06-08 19:05 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Riddell 2013-11-24 15:03:53 UTC
On a new user there is an activity which is shows in the activity plasmoid but which can not be selected.


Reproducible: Always

Steps to Reproduce:
1. make a new user
2. log in as new user
3. look at Activities plasmoid, there is Desktop and New Activity
Comment 1 Harald Sitter 2013-11-24 19:35:53 UTC
FWIW startkde logging suggests that the activity has the uuid 00000000000000000000000000000000

also after the first login it has no visible name in the activity switching plasmoid, on subsequent logins it will be called 'new activity'
Comment 2 Hrvoje Senjan 2013-11-24 19:37:35 UTC
Looks like dupe of bug 321781
Comment 3 Ivan Čukić 2013-11-24 19:39:28 UTC
The 'null' activity appears when the activity manager daemon is not running.

What happens if you do a 'qdbus org.kde.ActivityManager /ActivityManager/Activities ListActivities'?
Comment 4 Nate Graham 2018-06-08 19:05:03 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham