[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

2016-09-24 Thread J . O . Aho via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369099

J.O. Aho  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |BACKTRACE

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

2016-09-21 Thread J . O . Aho via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369099

--- Comment #5 from J.O. Aho  ---
Created attachment 101216
  --> https://bugs.kde.org/attachment.cgi?id=101216&action=edit
The result of "thread apply all bt"

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

2016-09-21 Thread J . O . Aho via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369099

--- Comment #4 from J.O. Aho  ---
Created attachment 101215
  --> https://bugs.kde.org/attachment.cgi?id=101215&action=edit
The output generated while running plasma in gdb

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

2016-09-20 Thread J . O . Aho via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369099

--- Comment #3 from J.O. Aho  ---
With  "session has crashed" I mean I'm back at the desktop manager and required
to login again.

When only plasmashell has crashed, I can still use yakuake and from there
restart plasmashell, which usually will last a shorter time than the previous
plasmashell and may lead to that the whole session dies (back out at the
desktop manager) in the end.

When the plasmashell has crashed, I do have the bug reporter started, and it
just says there ain't enough information when I select to send in the report
(so really not sure if it does send or not). I do always klick in the option
that I know what I was doing, but I never get an option to fill in what I was
doing (which should be idling).

I can't start a plasmashell session and run it in the environment I use, I know
it does crash there too.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369099] New: When running multiple sessions at the same time, :1+ crashes after some hours

2016-09-19 Thread J . O . Aho via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369099

Bug ID: 369099
   Summary: When running multiple sessions at the same time, :1+
crashes after some hours
   Product: plasmashell
   Version: 5.7.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: tr...@iname.com

Running multiple xorg tear (:0 and :1), both running plasmashell.
:0 keeps on running stably
:1 crashes either the whole session or just the plasmashell within 24h

The difference between the two sessions is that :0 is the one which is most
used and is in focus while :1 crashes.

Graphics driver: nVidia  370.28
kde-plasma/plasma-workspace-5.7.4:5::gentoo  USE="calendar geolocation handbook
qalculate"

Reproducible: Always

Steps to Reproduce:
1. Setup desktop manager to start up two or more tears, say :0 and :1
2. Login with user A or B in :0
3. Login with the other user on :1
4. switch between users with ctrl-alt f7/f8
5. switch to user on :0 and leave the machine running over night
6. switch to user on :1 in the morning

Actual Results:  
either session or plasmashell has crashed

Expected Results:  
The session should be in the same state as it was when you switched to :0

Only plasma widget is the desktop files.

Do not find any information in ~/.xsession-error that seems to be related to
plasmashell, no core file.

-- 
You are receiving this mail because:
You are watching all bug changes.