[plasmashell] [Bug 369142] plasma crashed when i loging to system

2016-10-24 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369142

--- Comment #5 from kafei  ---
It does not happen every time. After a couple of tries, I did get the crash to
occur with the same characteristics as before (black right monitor) by starting
plasmashell manually. However, when I managed to catch the same situation
running plasmashell under valgrind it did not crash... It's possible the race
doesn't occur when running under valgrind.

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


[plasmashell] [Bug 369142] plasma crashed when i loging to system

2016-10-21 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369142

--- Comment #3 from kafei  ---
Created attachment 101696
  --> https://bugs.kde.org/attachment.cgi?id=101696&action=edit
plasmashell crash stack trace

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


[plasmashell] [Bug 369142] plasma crashed when i loging to system

2016-10-21 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369142

kafei  changed:

   What|Removed |Added

 CC||matthewisrip...@gmail.com

--- Comment #2 from kafei  ---
I can confirm this bug; after installing Linux 4.8.3 and rebooting, plasmashell
crashed 3 times in a row. My right monitor was completely black except I could
mouse over it, just like the description in Bug 370916. My stack trace is also
very similar to the one in 370916, but differs slightly from the one in this
report.

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


[KScreen] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8

2016-10-18 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371196

--- Comment #2 from kafei  ---
Created attachment 101636
  --> https://bugs.kde.org/attachment.cgi?id=101636&action=edit
After switching primary display to HDMI monitor and back to DP monitor

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


[KScreen] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8

2016-10-18 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371196

--- Comment #1 from kafei  ---
Created attachment 101635
  --> https://bugs.kde.org/attachment.cgi?id=101635&action=edit
Desktop layout after reboot

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


[KScreen] [Bug 371196] New: Panel consistently appears on wrong monitor after reboot since 5.8

2016-10-18 Thread kafei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371196

Bug ID: 371196
   Summary: Panel consistently appears on wrong monitor after
reboot since 5.8
   Product: KScreen
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kded
  Assignee: se...@kde.org
  Reporter: matthewisrip...@gmail.com

I have a multi-monitor setup consisting of my 144Hz primary monitor in front of
me on displayport, and my 60Hz secondary monitor to the right on HDMI. After I
upgraded from 5.7.5 to 5.8.1 on Archlinux, my panel consistently appears on my
non-primary monitor after rebooting, and the default wallpaper appears on my
primary monitor. After going into the system settings and setting my primary
display to my HDMI monitor, then back to my DP monitor, my panel and wallpaper
move back to my primary monitor. But my secondary monitor then has the default
wallpaper and desktop toolbox. In addition, I set the refresh rate of my 144Hz
monitor to 120Hz, and this has also been resetting to 144Hz after rebooting. I
can set those back to normal, but it's annoying to have to do on each boot.

This behaviour didn't occur on 5.7, and I've never experienced multi-monitor
issues in the year I've been using plasma 5 (unlike many others), so I consider
this a regression. Behaviour similar to this is described in the comments of a
few other bug reports (https://bugs.kde.org/show_bug.cgi?id=370180 and
https://bugs.kde.org/show_bug.cgi?id=356225, the latter is filled with noise
and now closed), but I couldn't find any bug report specifically describing
this issue.  I waited until 5.8.2 before filing a bug report to see if it would
be fixed but the bug still occurs. Also, I apologize if this should have been
filed against plasmashell instead of KScreen.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to Plasma 5.8
2. Configure DP monitor to be primary with panel
3. Reboot

Actual Results:  
Panel appears on secondary (HDMI) monitor and wallpaper of other monitor is
reset to default and the desktop toolbox appears in the top right corner.

Expected Results:  
Panel should remain on primary (DP) monitor, and both monitors should keep the
same wallpaper.

I have an NVIDIA 970 using the proprietary drivers version 370.28.

Below are the outputs of `kscreen-console bug` and `qdbus org.kde.KWin /KWin
supportInformation`. I noticed that `kscreen-console bug` said "kscreen.log"
couldn't be parsed, but after deleting `~/.local/share/kscreen/kscreen.log` and
rebooting, the problem still occurred.

matt@KaFei:~$ kscreen-console bug
START: Requesting Config
Received config. Took 13 milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x1e4
Timestamp:  56207
Subpixel:   unknown
Clones:
CRTCs:  0 1 2 3
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)
SignalFormat: VGA 
supported: VGA
ConnectorType: DVI-I 
ConnectorNumber: 0  
_ConnectorLocation: 0   
DVI-I-1 disconnected (normal left inverted right x axis y axis) 
Identifier: 0x1e5   
Timestamp:  56207   
Subpixel:   unknown 
Clones: 
CRTCs:  0 1 2 3 
Transform:  1.00 0.00 0.00  
0.00 1.00 0.00  
0.00 0.00 1.00  
   filter:  
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0  
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)   
SignalFormat: TMDS