https://bugs.kde.org/show_bug.cgi?id=362051
--- Comment #5 from Daniel Lichtenberger ---
I use the radeon driver. I stopped seeing this issue about a month ago as well.
My current versions are:
- Frameworks 5.25.0
- Qt 5.6.1
- Plasma 5.7.4
- Kernel 4.7.3
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=354400
Daniel Lichtenberger changed:
What|Removed |Added
CC||daniel.lichtenber...@gmx.ne
https://bugs.kde.org/show_bug.cgi?id=363935
--- Comment #3 from Daniel Lichtenberger ---
Created attachment 99378
--> https://bugs.kde.org/attachment.cgi?id=99378&action=edit
Patch: use QScreen::virtualGeometry in PanelView::updateStruts
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=363935
Daniel Lichtenberger changed:
What|Removed |Added
CC||plasma-b...@kde.org
Component|P
https://bugs.kde.org/show_bug.cgi?id=363935
--- Comment #1 from Daniel Lichtenberger ---
Created attachment 99364
--> https://bugs.kde.org/attachment.cgi?id=99364&action=edit
Screenshot showing the issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363935
Bug ID: 363935
Summary: Vertical panel covers maximized windows with new Qt
multiscreen support
Product: plasmashell
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=362051
--- Comment #3 from Daniel Lichtenberger ---
I'm having the same issue and I also suspect it's some kind of race condition.
For me the panel is stored on the wrong (left) screen about 50% of boots.
Killing and restarting plasmashell does not trigger the
https://bugs.kde.org/show_bug.cgi?id=362128
--- Comment #2 from Daniel Lichtenberger ---
I still have this issue, but I noticed that the commit I mentioned was not part
of 5.6.2 and does not seem to be related to my problem.
--
You are receiving this mail because:
You are watching all bug chang
https://bugs.kde.org/show_bug.cgi?id=362128
Bug ID: 362128
Summary: Task manager restored to wrong screen
Product: plasmashell
Version: 5.6.2
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=314943
Daniel Lichtenberger changed:
What|Removed |Added
CC||daniel.lichtenber...@gmx.ne
https://bugs.kde.org/show_bug.cgi?id=295567
Daniel Lichtenberger changed:
What|Removed |Added
CC||daniel.lichtenber...@gmx.ne
https://bugs.kde.org/show_bug.cgi?id=359888
--- Comment #3 from Daniel Lichtenberger ---
Created attachment 97591
--> https://bugs.kde.org/attachment.cgi?id=97591&action=edit
tags file that triggered the infinite loop
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359888
--- Comment #2 from Daniel Lichtenberger ---
Created attachment 97590
--> https://bugs.kde.org/attachment.cgi?id=97590&action=edit
backtrace of crash
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359888
--- Comment #1 from Daniel Lichtenberger ---
Created attachment 97589
--> https://bugs.kde.org/attachment.cgi?id=97589&action=edit
strace output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359888
Bug ID: 359888
Summary: Infinite loop in baloo_file_extractor caused by tags
file
Product: Baloo
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
15 matches
Mail list logo