Bug 1375190 - ksmserver crashed when I switched user
Summary: ksmserver crashed when I switched user
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 12:40 UTC by pavel raur
Modified: 2017-12-12 10:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:13:52 UTC
Type: Bug


Attachments (Terms of Use)
packages on my pc (49.34 KB, text/plain)
2016-09-12 12:40 UTC, pavel raur
no flags Details
journalctl (153.96 KB, text/plain)
2016-09-12 12:40 UTC, pavel raur
no flags Details
packages on my pc (55.09 KB, text/plain)
2016-09-12 12:50 UTC, pavel raur
no flags Details

Description pavel raur 2016-09-12 12:40:06 UTC
Created attachment 1200201 [details]
packages on my pc

Description of problem:
In KDE fully updated system I switched user and logged in as another one. Then I logged out and login as the first user again. Crash notification appeared and then screen went black.
Notifications were about ksmserver, kwin, and akonadi. I tried again and result was same, but kwin didn't crashed this time.

akonadi_followupreminder_agent segmentation faul (11)
akonadi_ical_resource segmentation faul (11)
akonadi_sendlater_agent segmentation faul (11)
ksmserver segmentation faul (11)

Version-Release number of selected component (if applicable):
plasma-workspace-5.7.4-2.fc25.x86_64
kwin-5.7.4-1.fc25.x86_64
akonadi-1.13.0-102.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1.Switch user
2.login as another user
3.logout
4.login as the first user

Actual results:
some error notifications are displayed and then screen go black

Expected results:
user should normally login without any errors 

Additional info:

Comment 1 pavel raur 2016-09-12 12:40:37 UTC
Created attachment 1200202 [details]
journalctl

Comment 2 pavel raur 2016-09-12 12:50:28 UTC
Created attachment 1200203 [details]
packages on my pc

Sorry I uploaded wrong package list.

Comment 3 Rex Dieter 2016-09-13 18:16:09 UTC
If possible, please report this upstream @ bugs.kde.org

Comment 4 Fedora End Of Life 2017-11-16 19:33:52 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:13:52 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.