[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371417

OlafLostViking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=359542

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=371417

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371417

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
Created attachment 101684
  --> https://bugs.kde.org/attachment.cgi?id=101684=edit
kscreen.log while the described problem happened

The failure should be around 20.10.2016 08:07.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #30 from OlafLostViking  ---
Hi Sebas,

first thank you very much for the work. I really don't want you to get this
wrong and I fully understand that you are scanning through a lot of bug reports
and it takes time to understand each of them. (Especially considering my bad
English from time to time ;-) )

But I (personally) think that closing the bug because of too many details is
not the best solution. If I would have written "Yes, doesn't work with 5.8.2."
and that's it, would that have been better? So I tried around a long time to
find a way to provoke this bug and attached the logfile. To make it easier for
you to see what was happening in the log that lead to the crash I described
what I did. If you are not interested in that, wouldn't it work to just ignore
it and jump to the marked "2nd pause", where the crash happened - as written at
the beginning?

There are no problems with specific apps, as the broken images happen on
multiple ones and only after kscreen "did things" ;-). So this wasn't a "Please
fix the app." but a "Look, Kscreen(??) does something that leads to problems at
many other places." The same goes with Plasma which takes the information vom
libkscreen, I guess. Of course, nobody wants you to take care of that! It was
just mentioned so that you could guess what kscreen is doing wrong at that
point in time.

So in the end I do not know what else I could write in a new bug report but
"Crashes when (un-)docking." and attaching the very same log as above (there
was no kscreen.log at the beginning which is why I started with kscreen-console
and xrandr logs).

I tried it on bug #371417 - I hope it helps.

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

[KScreen] [Bug 371417] New: screens not (re-)actived after (un-)docking cycles of a notebook

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371417

Bug ID: 371417
   Summary: screens not (re-)actived after (un-)docking cycles of
a notebook
   Product: KScreen
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

As asked for in bug #359542 here a shorter summary of the problem mentioned
there.

KScreen fails to (re-)enable displays after docking/sleep cycles.

Reproducible: Sometimes

Steps to Reproduce:
1. Put Notebook to sleep.
2. Undock from docking station A (internal screen + one external screen).
3. Dock into docking station B (two external screens).
4. Wake-up.

Actual Results:  
Internal display goes on, gets deactivated, external displays do not get even
powered on. Undocking does not reactive the internal display. Open
data/application states get lost.

Expected Results:  
Internal display should go off but the two external displays should also get
activated.

DELL E6430 with a mobile nvidia chip.

Docking Station A has an horizontal Full-HD display on the DVI port. The
internal 1600x900 display LVDS is used.

Docking Station B has an horizontal 2560x1440 display on the DP port and a
vertical 2048x1152. The internal display cannot be used.

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

[KScreen] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #28 from OlafLostViking  ---
Did you install and run the mentioned spice-vdagent? This is mandatory for
virt-manager based VMs to communicate with the host.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

Version|5.5.4   |5.8.2

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #27 from OlafLostViking  ---
Created attachment 101655
  --> https://bugs.kde.org/attachment.cgi?id=101655=edit
screen photo showing the broken weather applet

Actually... I just saw the picture is quite bad. Basically, the white are looks
just like the qupzilla and profile pics background. It is the weather applet
from http://kde-apps.org/content/show.php/Weather+Widget?content=169572

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #26 from OlafLostViking  ---
Created attachment 101654
  --> https://bugs.kde.org/attachment.cgi?id=101654=edit
screen photo showing the broken qupzilla workspace

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #25 from OlafLostViking  ---
Created attachment 101653
  --> https://bugs.kde.org/attachment.cgi?id=101653=edit
screen photo showing the broken profile pics

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #24 from OlafLostViking  ---
Created attachment 101652
  --> https://bugs.kde.org/attachment.cgi?id=101652=edit
the automatically created kscreen.log

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #23 from OlafLostViking  ---
(Very) long story short: yes. I updated to 5.8.2 and I already saw many
improvements! Thank you! But the problem is still there.

BTW (I don't know if we need [another] bug report for that): when playing
around with multiple screen in the kscreen GUI, they something jump around
(when getting activated) and ruin any sorting work done up unto this point.

So, tighten your seatbelts, here it comes...  I will now give some kind of
diary (with terrible unprecise times as I just counted in my head) of what I
did and append the kscreen.log file that was created during that time. Please
do at least scan over the whole text, as the problems with the
panels/wallpapers and the window's movements _could_ perhaps give you an idea
(at least I hope so). I will change the docking stations later in the text and
the black-out happens after the second "pause".

* updated to Plasma 5.8.2
* "fixed" my desktop settings
* logged out
* deleted .local/share/kscreen/* on the console
* rebooted _in_ docking station WORK
  - WORK has a primary screen on Displayport DP-2 and a vertically rotated
secondary on DVI DP-1
  - the internal LVDS-0 screen has to be shut off because DELL was creative
when wiring the CPU internal and the mobile GeForce to the ports
  - SDDM shows login screen on LVDS-0 and the secondary screen DP-1 (not
rotated, understandably)
* logged in
  - keeps the screen configuration of SDDM
  - panel and wallpaper are shown correctly on the primary screen (still
LVDS-0)
  - on the secondary screen (DP-1) the default wallpaper is shown
* use kscreen to switch LVDS-0 off, set DP-2 as active primary and DP-1 as
active secondary (rotated by 90 deg)
  - the switching works almost immediately (of course no atomic modesetting
yet)
* set my own wallpaper on the secondary screen (DP-1)
* undock from docking station WORK
  - LVDS-0 get activated quite fast, all seems okay
* redock into WORK
  - setting up the screens takes a very short time (no atomic) but everything
seems to work
* undock again
  - the screen setup looks fine
  - my active browser gets moved out of the screen (I cannot see it anymore
despite on the panel)
* redock into WORK
  - screen setup is fine
  - panel is okay, but the wallpaper on the secondary screen is now the default
wallpaper
* undock
  - the browser window, which was moved out of the view earlier, is now
centered on screen (here I may add that I did not touch the GUI while doing
this docking-undocking cycles)
* redock into WORK
  - now it takes several seconds (my guess was 10-12) for the new setup to
start  <
  - screen setup is fine
  - the panel is now very narrow and on the secondary screen (DP-1)
  - there is NO wallpaper or anything else (like cashew/hamburger) on this
secondary screen; I also cannot right click on the black area (the panel is
responsive) <
* undock
  - screen setup is fine
  - panel is fine again
  - now, the afore mentioned browser window is half-way shifted (to the right
side) out of the visible desktop
* redock into WORK
  - primary screen is fine
  - secondary is showing the default wallpaper
* set the wallpaper to my own
* put notebook into sleep mode while still docked
* wake it up while still docked in WORK
  - lockscreen shows up correctly (new in 5.8.2! :-) ) on primary and secondary
(incl. rotation) screen
* put it into sleep
* wake it up
  - now the profile pics in the lockscreen are messed up (white area with a few
coloured sprinkles - I will add a photo if I don't forget later when attaching
files)
  - rest seems to be fine
* put it into sleep in docking station WORK
* undock!
* wake it up outside of docking station
  - profile pics are still messed up, rest seems fine
* redock into WORK
  - screen setup is fine
  - wallpapers are fine
  - but the panel is now on the wrong/secondary screen
* undock from WORK
  - the screen stays "half-black" for a surprisingly long time, but plasma
fills the missing part up, eventually
  - panel also takes several seconds to appear
* put notebook to sleep (still not docked)
* wake it up after docking it into WORK
  - SDDM appears on internal screen (LVDS-0) with broken profile pics (as
described above)
  - LVDS-0 shuts off
  - Secondary screen (DP-1) shows screenlocker with _working_ profile pics
  - Primary screen (DP-2) is black (no screenlocker!) while still showing the
mouse cursor
* login
  - screen setup is fine
  - my weather widget in the plasma panel as well as the website view of the
Qupzilla browser now show the same "coloured-sprinkels-on-white-ground"
background as the profile pics
  - qupzilla can be fixed by resizing, the weather applet works again after
some time (I guess after an update)
  - wallpaper is back to the default
* setting the wallpaper to mine again

== I really needed to go back to my work here ;-). So there is a pause of
"strange" things in the kscreen.log

* put notebook 

[KScreen] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #23 from OlafLostViking  ---
I just setup a Neon Developer Unstable VM. So I can help trying out stuff in
there! (As of today, it doesn't work.)

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #22 from OlafLostViking  ---
Sometimes. (I know, very helpfui. It happened once or twice this week, if I
remember correctly.)

Just now after docking the internal screen was shut off (which took two or
three seconds), the secondary external monitor was showing the lockscreen, the
primary was not (albeit it was powered on). After logging in, both were active.
Undocking worked, redocking it (taking again a few seconds) messed Plasma up
(panel on the wrong screen, far too small, wallpaper replaced by default
wallpaper, windows all on different screens with random sizes). Doing the cycle
again led to the panel being on the correct screen, the wallpaper on the
secondary screen is still the default wallpaper. After changing the wallpaper
on the secondary screen, I retried: The third try took over six or seven
seconds to shut off the LVDS (I first thought it hangs). The wallpapers of both
external screens are fine, the windows messed up and the panel again shifted
(and shrinked) to the secondary screen. To not make it an endless loop: The
fourth and last try reset the wallpaper again, but the panel was fine.

I will now delete the kscreen files again and re-start with a clean config as I
am now using 5.8.1.

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

[kopete] [Bug 362535] Kopete 1.9.0 somtimes won't encrypt even though the GUI says otherwise

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362535

--- Comment #7 from OlafLostViking  ---
1.10.1 is still dangerous for important data.

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

[kmail2] [Bug 370275] KMail crashes when pressing SPACE while displaying a message

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370275

--- Comment #3 from OlafLostViking  ---
Reported https://bugs.archlinux.org/task/51304

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

[kmail2] [Bug 370275] New: KMail crashes when pressing SPACE while displaying a message

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370275

Bug ID: 370275
   Summary: KMail crashes when pressing SPACE while displaying a
message
   Product: kmail2
   Version: 5.3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

After selecting a message from the message list, pressing space leads to an
immediate crash.

Reproducible: Always

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

[kdevelop] [Bug 369164] New: 5.0.1 "pauses" on startup

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369164

Bug ID: 369164
   Summary: 5.0.1 "pauses" on startup
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

KDevelop 5.0.1 (not selectable in the dropdown above) shows a strange startup
behaviour. After starting it, the IDE window is created and correctly filled
with content of the last session.

But then it hangs for two or three seconds without updating the screen.
Resizing it via KWin breaks the window content until the next redraw. After
that it behaves snappy as expected.

It looks like the GUI thread runs, after initializing everything, some parser
job or so instead of sending it to the background. But that is speculation...

Anything I can do to give better feedback?

Reproducible: Always

Steps to Reproduce:
1. Start KDevelop.
2. See IDE drawing.
3. Wait some seconds until GUI becomes responsive.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #20 from OlafLostViking  ---
I have no idea why kscreen is forgetting the correct settings as they are
available in the config files (deleting the config files makes it work with a
standard setup - see below - again).

BTW: This behaviour is reproducible since the update that lead to this
situation. So whenever I come to the docking station at work, my screens turn
black. I found out undocking the laptop activates the internal display again.
But deleting the kscreen configs in this running system and then re-docking the
laptop leads to a complete lockup (the internal screen freezes, the other
screens are not changed, hard reboot needed).

After a reboot SDDM is using the (X11?) standard config (as always) with the
first external screen and the internal screen active (this machine only
supports two active screens) which is also used by the desktop then. Plasma
fails to recognize the correct setup and only uses one screen (sometimes even
with a default wallpaper instead of my personal one...?), but a restart of
plasma fixes that. :-/

In the end this means I have to reboot my laptop whenever sitting down at my
desk (annoying as I have a fully enrcrypted harddisk with two-factor
authentication ;-) ).

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #18 from OlafLostViking  ---
The problem described in comment #15 just happened again. This time, I switched
to a console after  hard rebooting and dumped a simple "xrandr" and
"kscreen-console" output. Perhaps it's helpful.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #17 from OlafLostViking  ---
Created attachment 100346
  --> https://bugs.kde.org/attachment.cgi?id=100346=edit
kscreen-console.log

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #16 from OlafLostViking  ---
Created attachment 100345
  --> https://bugs.kde.org/attachment.cgi?id=100345=edit
xrandr.log

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

[kopete] [Bug 362535] Kopete 1.9.0 somtimes won't encrypt even though the GUI says otherwise

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362535

--- Comment #5 from OlafLostViking  ---
It didn't change in 1.9.3.

Since the dropdown in the bug report form isn't up to date either (latest is
1.7.2), I wonder if Kopete is still being maintained or if it's dead: Are there
any developers left or would it be better to abandon it and switch to GTK based
programs?

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #15 from OlafLostViking  ---
Okay, let's try it ;-)

At home, the laptop was running inside a docking station with the internal LVDS
and an external screen active. I put it to sleep and woke it up again at work
inside another docking station with two external screen connected (due to the
machine's architecture only two displays can be used at the same time; the LVDS
has to stay inactive at work).

Here the laptop shortly showed the kscreenlocker before shutting off the
internal display but not activating the external ones. Even switching to a
kernel console wasn't possible anymore.

Each following reboot SDDM was showing on the internal screen as well as the
"first" external one (which, btw., is rotated - SDDM doesn't know that, of
course). After logging in, all screens turned and stayed black. Switching to a
kernel console WAS possible at that point in time (on the LVDS).

Rebooting outside of the docking station, the desktop came up normaly. Deleting
the .local/share/kscreen folder made it possible again to put the laptop into
the docking station without it turning off the screens.

Having a look at the kscreen GUI now revealed that kscreen thinks the secondary
external screen has NO resolution... Simply clicking on Unify Outputs two times
made it recognize the correct resolutions again. (Perhaps kscreen should NOT
change anything when it is unsure about the system's state so that the user
isn't left with no screen active at all.)

Switching to the wanted setup with the primary external display active and
rotated, the secondary active and the internal inactive now worked. Even though
Plasma couldn't handle the primary screen and had to be restarted to get my
wallpaper (but that's nothing new and for another bug report one day).

Before putting the laptop to sleep, I let xev run:

$ xev | tee xev.log
# suspend
# steps described above
$ grep RR xev.log 
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputPropertyChangeNotifyEvent
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Disconnected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Connected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Connected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 174, synthetic NO, window 0xa1,
$ 

The whole xev.log is available for one year at https://paste.kde.org/pn9e0snkc

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #14 from OlafLostViking  ---
"Unfortunately" I have to say, the error no longer appears all the time (newest
packages from kf, apps, plasma) but only from time to time (or kwin just
crashes and reloads - so no data loss in that specific case. However, the main
culprit in messing up the screens became Plasma.).

I'll still try to remember checking xev and will report back, if I find
something - I just wanted to ACK so that the report doesn't get closed because
of a missing answer.

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

[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362958

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #17 from OlafLostViking  ---
You did check the setting in the menu mentioned in comment #14?

I just tried all the GPUs available in KVM/virt-manager in Neon:
* QXL: see above
* Virtio: won't work with Neon, but in other distributions it behaves like QXL
* Cirrus: does not report the true window resolution "to xrandr"
* VGA: offers 800x600 as the only resolution available, no matter the host
window size
* VMVGA: lots of funny effects/flickering, locks up(!) after ksplash
* Xen: doesn't come up at all

To summarize: I'd say that for now QXL and in the long run Virtio are the two
relevant GPUs for a Linux/KDE desktop in a KVM VM. The others are probably not
that important for KWin (just my personal opinion!)?

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #14 from OlafLostViking  ---
Oh, and it seems you have to select `View -> Scale Display -> Auto resize VM
with window` in the virt-manager window.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #13 from OlafLostViking  ---
Are you using spice in the virt-manager and ran spice-vdagent inside of the VM?
The spice protocol is the one responsible for the integration of host and
guest. In Neon it is in universe/x11.

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

[kmail2] [Bug 356283] Any message contents that shows in the message preview bottom pane shows <<< Grantlee theme "" is not valid >>> prefixed to the actual msg body

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356283

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #6 from OlafLostViking  ---
Using KMail 5.2.2 within Kontact.

Switching from an additionally installed theme to a default one is not saved by
KMail. The formerly selected one is preferred on every start. After
uninstalling this additional theme, the error message of the OP is shown and
even now persistently selecting a default theme is not possible.

But it seems that switching the theme in a stand-alone KMail, the settings are
saved and after that even the embedded KMail within Kontact seems to use the
correct theme.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #10 from OlafLostViking  ---
> Could you run xrandr before and after resizing the VM window and diff the 
> change?

Sure thing (using Neon):

# after booting in a VM window with 1280x720, internal resolution 1280x720
after login
$ xrandr > xrandr.before
$ qdbus org.kde.KWin /KWin supportInformation > qdbus.before
# increasing VM window size, no touching internal settings
$ xrandr > xrandr.bigger
$ qdbus org.kde.KWin /KWin supportInformation > qdbus.bigger
# decreasing VM window size, no touching internal settings
$ xrandr > xrandr.smaller
$ qdbus org.kde.KWin /KWin supportInformation > qdbus.smaller
$ diff xrandr.before xrandr.bigger 
3c3
<1280x720  59.86*+
---
>1512x893  59.84 +
13a14
>1280x720  59.86* 
$ diff xrandr.before xrandr.smaller
3c3
<1280x720  59.86*+
---
>1064x664  59.86 +
13a14
>1280x720  59.86* 
$ diff qdbus.before qdbus.bigger 
$ diff qdbus.before qdbus.smaller

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #8 from OlafLostViking  ---
=== Setup ===

The following steps have been tried on these installations within a libvirt/KVM
VM:
- Neon (user): Qt 5.7.0, KWin/Plasma 5.7.0, kf5 5.24, QXL (Virtio doesn't even
reach X11/SDDM)
- Archlinux (kf5-only): Qt 5.7.0, KWin/Plasma 5.7.0, kf5 5.23, QXL as well as
Virtio
- Manjaro (KDE): Qt 5.7.0, KWin/Plasma 5.6.5, kf5 5.23, QXL
- openSUSE (Tumbleweed): Qt 5.6.1, KWin/Plasma 5.6.4, kf5 5.23, QXL as well as
Virtio

All were updated to use the repository packages of today (2016-07-11) and
rebooted while having 1280x720 set as desktop resolution.


=== Booting ===

They boot into a default sized (1024x768) SDDM, which doesn't react on VM
window changes (unlike f.ex. GDM that I tested before in another VM, see
comment #2). After logging in, Plasma/KSplash adjusts to the resolution of the
last session. (At least most of the times... I finally gave up for now finding
a pattern - I guess using xrandr vs kscreen makes a difference... But that's
probably for another bug report one day ;-) )


=== QDbus ===

Output of the qdbus command after login:

```[olaflostviking@valhalla ~]$ qdbus org.kde.KWin /KWin supportInformation |
grep -A7 Screens
```Screens
```===
```Multi-Head: no
```Active screen follows mouse:  yes
```Number of Screens: 1
```
```Screen 0:
```-
```Name: Virtual-1   ### index depends on distribution
```Geometry: 0,0,1280x720
```Refresh Rate: 60 ### exact frequency differs on distributions

Changing the size of the outer VM window does _not_ alter the output of the
qdbus query (`diff`ed the whole output). Using kscreen to change the resolution
works as mentioned before. The output of the qdbus query changes at the
"Geometry" entry only.


=== xrandr ===

With `xrandr --output Virtual-1 --mode 1280x720` I can switch to the desired
resolution, too. This is correctly shown by a following `xrandr` (including *
and +) as well as in the `qbus...` query on KWin (just to make it clear: the
outer window size of the VM is correctly reflected by `xrandr` only but not the
`qdbus` output).


Thanks for having a look!

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

[kmail2] [Bug 362710] Message list view does not show any text (invisible sender, subject, date etc)

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362710

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[kmail2] [Bug 362608] Default colours unusable on dark theme

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362608

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[kscreenlocker] [Bug 329089] automatically unlock screen at home

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=329089

--- Comment #5 from OlafLostViking  ---
Martin marked "my" bug as duplicate; thank you - I don't understand how I could
miss this one when searching. Sorry!

But just as an additional comment (and to make sure Martin is even more
frightened by the complexity ;-p ): this bug report here talks about unlocking
after a suspend/resume cycle, which I like as an idea, too. In my bug report I
talked about inhibiting locking the screen (after X minutes) when in a specific
WiFi network (but still keep it locked when it was locked beforehand or
manually). Just semantics, I guess.

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

[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=283020

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[kscreenlocker] [Bug 362763] New: DIsable lockscreen when specific WiFi is visible

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362763

Bug ID: 362763
   Summary: DIsable lockscreen when specific WiFi is visible
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org

It would be a nice feature if KScreenLocker could be configured to not lock the
computer when it is logged into a specific Wifi. This could be tied to the
hardware address of the access point and/or to the SSID.

This could be a security risk, as a motivated attacker could fake such an AP.
So the user should be warned about that/the setting should only be made
available in advanced settings or so. Preventing switching WiFi networks while
locked could help a little bit on this front, but I guess this could become
complicated very fast... ;-)



Reproducible: Always

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

[kwin] [Bug 362754] New: Crash after wakeup from suspend with changed screen configuration

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362754

Bug ID: 362754
   Summary: Crash after wakeup from suspend with changed screen
configuration
   Product: kwin
   Version: 5.6.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

Application: kwin_x11 (5.6.3)

Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.5.1-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

* Suspend notebook while in dock with external monitors connected.
* Wake the machine up while on the road (so nothing externally connected).
* Move a window to the edge of the screen to maximize it.
* KWin crashes.

- Additional details:

* Using nvidia proprietary drivers :-(

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9eb26d3840 (LWP 6708))]

Thread 5 (Thread 0x7f9e98aa8700 (LWP 6717)):
#0  0x7f9eb1f10903 in select () from /usr/lib/libc.so.6
#1  0x7f9eafebc57f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/libQt5Core.so.5
#2  0x7f9eafebdf87 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/libQt5Core.so.5
#3  0x7f9eafebe472 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f9eafe696fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f9eafc92fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f9ea949da55 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f9eafc97de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f9eb21d8424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f9eb1f17cbd in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f9e92458700 (LWP 6719)):
#0  0x7f9eb1f10903 in select () from /usr/lib/libc.so.6
#1  0x7f9eafebc57f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/libQt5Core.so.5
#2  0x7f9eafebdf87 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/libQt5Core.so.5
#3  0x7f9eafebe472 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f9eafe696fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f9eafc92fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f9eaa52d915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f9eafc97de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f9eb21d8424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f9eb1f17cbd in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f9e7a37d700 (LWP 6722)):
#0  0x7f9eb21de03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9eaebf3134 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f9eaebf3179 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f9eb21d8424 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f9eb1f17cbd in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f9e85abd700 (LWP 8307)):
[KCrash Handler]
#5  0x7f9eafe9bab7 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () from /usr/lib/libQt5Core.so.5
#6  0x7f9eb03ee815 in QOpenGLContext::setScreen(QScreen*) () from
/usr/lib/libQt5Gui.so.5
#7  0x7f9eafe98659 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#8  0x7f9eb0b8f68c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#9  0x7f9eb0b948f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#10 0x7f9eafe6b518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#11 0x7f9eafe6d3da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#12 0x7f9eafebe352 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#13 0x7f9eaabfb34b in ?? () from /usr/lib/libQt5Quick.so.5
#14 0x7f9eafc97de8 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7f9eb21d8424 in start_thread () from /usr/lib/libpthread.so.0
#16 0x7f9eb1f17cbd in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f9eb26d3840 (LWP 6708)):
#0  0x7f9eb21de03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9eafc98c8b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f9eaabf7e94 in ?? () from /usr/lib/libQt5Quick.so.5
#3  0x7f9eaabf87ea in ?? () from /usr/lib/libQt5Quick.so.5
#4  0x7f9eaac2dc63 in 

[kopete] [Bug 362663] New: Plasma notifications about new messages persistent

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362663

Bug ID: 362663
   Summary: Plasma notifications about new messages persistent
   Product: kopete
   Version: Git
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: kopete-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

Kopete 1.9.0's (not selectable in dropdown) notifications about new messages,
displayed on a plasma 5.6.3 desktop using frameworks 5.21 do not disappear when
the message has been seen and stack up until one explicitly deletes them from
the generic Notifications Applet in plasma.

Reproducible: Always

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

[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360963

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
Simple user here.

I am using multiple "account+project@domain" addresses. For some folders I have
"use default identity" selected as sender in the folder properties, for others
a project specific one.

But the setting mentioned before is only relevant when writing a new message.
When I am answering an e-mail to "account+project123@domain" KMail
automatically selects the identity associated with that e-mail address
including From, BCC and Organization headers. Only when there is no identity
configured for that specific address it selects the default one. (This really
great support for multiple accounts and identities is one of the many reasons I
still use KMail despite akonadi ;-D. )

So perhaps I am overlooking something or my version (KMail 5.2.0) got something
fixed which wasn't yet fixed in your version?

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

[kopete] [Bug 362535] Kopete 1.9.0 somtimes won't encrypt even though the GUI says otherwise

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362535

--- Comment #1 from OlafLostViking  ---
Looks like Kopete is internally killing the _encryption_ on the sending side as
soon as I close the chat window/tab without informing the other side of that.
It can still _decrypt_ messages from the other client. I saw it first with a
Pidgin contact and verified it now with a Conversations client.

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

[Phonon] [Bug 362285] New: Audio volume settings in KCM: drop down disabled when one device is muted

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362285

Bug ID: 362285
   Summary: Audio volume settings in KCM: drop down disabled when
one device is muted
   Product: Phonon
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: settings
  Assignee: sit...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
CC: myr...@kde.org

I hope this is the correct product... I am using Phonon GStreamer 4.9.0 in a
Plasma 5.6.3 desktop with Framworks 5.21.0 and Applications 16.04.0. In the
Audio Volume KCM (as the PA Plasma widget cannot switch devices (I guess..)) I
cannot change the default output device when the currently selected device is
muted.

Reproducible: Always

Steps to Reproduce:
1. Mute audio while speakers are your default output device.
2. Open KCM Audio Volume settings because you want to switch to headphones.
3. Fail, as the drop down with the devices is inactive as long as the currently
selected device is muted.

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

[kmail2] [Bug 362280] New: KMail replaces addresses in the header by "Me"

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362280

Bug ID: 362280
   Summary: KMail replaces addresses in the header by "Me"
   Product: kmail2
   Version: Git (master)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

KMail 5.2.0 (currently not selectable in the "Version" drop-down) replaces my
e-mail address in the To: or From: etc. header by a "Me" in the message view.
To see the correct address and name I have to reach for the mouse and hover
over it with the pointer.

That's very inconvenient and useless (for me!). I know my own addresses... but
as I am using KMail with a lot of accounts including "+"-suffices (the good
support for this use case is one of the main reasons for me to use KMail) it's
an unnecessary extra step to get all information.

I couldn't find a way to deactivate that new behaviour. If you really want to
keep it (it's quite possible that just _I_ don't see the use case for that ;-)
), please make it optional so that the user can opt for the "real" header.

Reproducible: Always

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350731

--- Comment #20 from OlafLostViking  ---
Still valid for Akregator from Applications 16.04.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

OlafLostViking  changed:

   What|Removed |Added

Version|5.6.0   |master
   Platform|Archlinux Packages  |Neon Packages

--- Comment #6 from OlafLostViking  ---
Now that KDE is offering the "official" NEON packages I thought I should give
them a try to rule out distribution/packaging problems.

So I installed the NEON git stable image of today via ubiquity, updated it with
an "apt-get update"/"apt-get upgrade" and added "spice-vdagent" to it:

* neon-desktop (4+p16.04+git20160415.1334)
* kwin (4:5.6.2+p16.04+git20160415.0003-0)
* plasma-framework (5.21.0+p16.04+git20160416.0014-0)
* sddm (0.13.0-1ubuntu5)

This bug report is also valid for this installation.

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

[Akonadi] [Bug 289097] error "Unable to fetch item from backend" when entering IMAP folder

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=289097

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #84 from OlafLostViking  ---
Just hit this with kmail 5.1.3 from 15.12.3. "akonadictl fsck" and "akonadictl
vacuum" seemed to solve it for one of my two IMAP accounts - as soon as I
switch to the other account, it's going down for both of them again ;-). So
it's somehow account related.

I have to manually stop akonadi, sometimes the mysqld, too, before another
"akonadictl vacuum" command works again, btw... (hanging at "optimizing table
PimItemTable..." forever if not restarting everything beforehand).

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

OlafLostViking  changed:

   What|Removed |Added

Version|5.6.0   |5.6.1

--- Comment #4 from OlafLostViking  ---
Still valid for 5.6.1.

(Do you even want updates on this bug report when I check out a new version? Or
would it be better to keep the noise level low? :) )

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

[kscreenlocker] [Bug 361007] Changing Audio volume in Lock Screen not possible anymore

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361007

--- Comment #5 from OlafLostViking  ---
Qt 5.6.0, Archlinux AMD64

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

[kscreenlocker] [Bug 361007] Changing Audio volume in Lock Screen not possible anymore

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361007

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
This is still valid for the final version of 5.6.0 (report was for 5.5.95).

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

OlafLostViking  changed:

   What|Removed |Added

Version|5.5.4   |5.6.0

--- Comment #3 from OlafLostViking  ---
Still valid for 5.6.0.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

OlafLostViking  changed:

   What|Removed |Added

Version|5.5.1   |5.6.0

--- Comment #4 from OlafLostViking  ---
Still valid for 5.6.0

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97285|0   |1
is obsolete||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #12 from OlafLostViking  ---
Created attachment 97328
  --> https://bugs.kde.org/attachment.cgi?id=97328=edit
output of "loginctl session-status"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #11 from OlafLostViking  ---
Created attachment 97327
  --> https://bugs.kde.org/attachment.cgi?id=97327=edit
output of "kscreen-console bug"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97288|output of "kscreen outputs" |output of "kscreen-console"
description||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97326|output of "kscreen config"  |output of "kscreen-console
description||config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97287|output of "kscreen json"|output of "kscreen-console
description||json"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97285|output of "kscreen" |output of "kscreen-console"
description||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #10 from OlafLostViking  ---
Created attachment 97326
  --> https://bugs.kde.org/attachment.cgi?id=97326=edit
output of "kscreen config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #6 from OlafLostViking  ---
Created attachment 97288
  --> https://bugs.kde.org/attachment.cgi?id=97288=edit
output of "kscreen outputs"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #5 from OlafLostViking  ---
Created attachment 97287
  --> https://bugs.kde.org/attachment.cgi?id=97287=edit
output of "kscreen json"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #4 from OlafLostViking  ---
Created attachment 97286
  --> https://bugs.kde.org/attachment.cgi?id=97286=edit
output of "kscreen config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #3 from OlafLostViking  ---
Created attachment 97285
  --> https://bugs.kde.org/attachment.cgi?id=97285=edit
output of "kscreen"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #2 from OlafLostViking  ---
Created attachment 97284
  --> https://bugs.kde.org/attachment.cgi?id=97284=edit
output of "kscreen bug"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

--- Comment #1 from OlafLostViking  ---
Created attachment 97283
  --> https://bugs.kde.org/attachment.cgi?id=97283=edit
output of kscreen

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

[KScreen] [Bug 359542] New: Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359542

Bug ID: 359542
   Summary: Waking up notebook from sleep after undocking leaves
display turned off
   Product: KScreen
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

After putting my notebook to sleep with external monitors attached to the
docking station it's currently connected to and waking it up on the road
(obviously without anything attached) the display stays off.

I can switch with CTRL+ALT+F2 to a text console, but I didn't manage to
reactivate the display from there. There I called kscreen-console; I will
attach the output to the following comments.

The severity was set to "grave" as this is equivalent to a crash with data loss
(at least until I know how to reactivate the screen from a text console ;-) )
when all applications are force-shutdown when rebooting the machine.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

--- Comment #3 from OlafLostViking  ---
Can I provide any more details of should I try out other things?

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

--- Comment #2 from OlafLostViking  ---
Can I provide any more details or try out something different?

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

[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355928

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #11 from OlafLostViking  ---
Archlinux, Plasma 5.5.4, nvidia driver

kscreen: Primary output changed from KScreen::Output(Id: 653 , Name: "DP-2" ) (
"DP-2" ) to KScreen::Output(Id: 653 , Name: "DP-2" ) ( "DP-2" )
kscreen: Primary output changed from KScreen::Output(Id: 653 , Name: "DP-2" ) (
"DP-2" ) to KScreen::Output(Id: 653 , Name: "DP-2" ) ( "DP-2" )

Appears always in pairs, but without any systematics (at lost none that are
easily recognizeable for me).

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

[dolphin] [Bug 358567] Dolphin allows to place slash ('/') symbol in folder and file names under cinnamon

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358567

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
Are you sure it is adding a "/" (slash) and not a "⁄" (fraction)?

I just tried it out within a plasma workspace and it is trying to create
fractions. When my filename ends with a number, it puts it "on top" of a
fraction...

(Not saying this is a good idea - but a slash symbol in the filename shouldn't
even be possible.)

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

--- Comment #1 from OlafLostViking  ---
I may add that with xrandr the resolution change is visible:

* before resizing the window
[olaflostviking@kessel ~]$ xrandr 
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192
Virtual-0 connected primary 1280x720+0+0 0mm x 0mm
   1280x720  59.86*+
   1920x1200 59.88  
   1920x1080 59.96  
   1600x1200 59.87  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
[olaflostviking@kessel ~]$


* after resizing the window
[olaflostviking@kessel ~]$ xrandr 
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192
Virtual-0 connected primary 1280x720+0+0 0mm x 0mm
   1768x963  60.00 +
   1920x1200 59.88  
   1920x1080 59.96  
   1600x1200 59.87  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1280x720  59.86* 
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
[olaflostviking@kessel ~]$

Here you can see you X correctly "thinks" the preferred resolution is 1768x963.

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

OlafLostViking  changed:

   What|Removed |Added

Version|5.5.1   |5.5.4

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

[plasmashell] [Bug 355932] plasmashell segfaults after wakeup from suspend with one display less connected

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355932

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 355885] crashed while removing an Desktop Icon

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355885

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 352653] Dropdowns in widget properties don't follow system color settings. [regression]

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352653

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 356937] Xembed icons have black background

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356937

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

OlafLostViking  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #2 from OlafLostViking  ---
Yes, it does. In the example down below I manually set the resolution in
kscreen to 1280x720) and resized the window - the new resolution seems to be
always the value appearing first in the list. In "virt-manager" the check box
"View->Scale Display->Auto resize VM with window" is active.

When I open the kscreen config now, 1024x768 is preselected in the dropdown and
the "strange" resolution of my VM window is not selectable/shown in the list.

Just to be very sure it's not a driver problem in my KDE VM, I just installed
the "plasma" package group in my dedicated (working) GNOME VM (so everything is
up-to-date [SDDM 0.13.0, Plasma 5.5.1, Frameworks 5.17.0 and Apps 15.12.0]
without any old KDE libs/config etc.) and tried logging into Plasma via GDM as
well as SDDM. The results are the same:

* GDM adapts, Plasma starts in the "correct" resolution set by GDM but doesn't
adapt anymore.
* When booting with SDDM as display manager, it's already starting in a wrong
resolution. A started GNOME session corrects the resolution and adapts, a
Plasma session stays "wrong" and won't adapt either.


[olaflostviking@kessel ~]$ xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192
Virtual-0 connected primary 1280x720+0+0 0mm x 0mm
   1216x591  59.72 +
   1920x1200 59.88  
   1920x1080 59.96  
   1600x1200 59.87  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1280x720  59.86* 
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
[olaflostviking@kessel ~]$

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

[krunner] [Bug 354546] krunner window appears outside of visible area after reconnecting a screen

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354546

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #2 from OlafLostViking  ---
Confirm for Archlinux Plasma 5.5.1, KRunner 5.17.0.

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

[krunner] [Bug 344328] krunner is not visible when using multiple monitors

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344328

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[plasmashell] [Bug 356864] New: Plasma cannot adapt to VM host window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356864

Bug ID: 356864
   Summary: Plasma cannot adapt to VM host window
   Product: plasmashell
   Version: 5.5.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: olaf.the.lost.vik...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

When running plasmashell in a KVM/QXL/Spice VM, it fails to resize to the
client window. spice-vdagent is running. While the GDM window still correctly
follows the size/resolution changes of the outer window, plasma sticks to a
fixed one that must be switched to manually.

Reproducible: Always

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

[KScreen] [Bug 356871] New: KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356871

Bug ID: 356871
   Summary: KScreen does not adapt to window size of
QEMU/QXL/Spice VM window
   Product: KScreen
   Version: 5.5.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: dvra...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

In my Archlinux guest with xf86-video-qxl and spice-vdagentd, GDM as login
manager adapts dynamically to the size of the sourrounding host window
including taking up the native resolution of my screen when I select "Full
screen" in virt-manager's viewer. As soon as I login into a plasmashell, this
capability is lost and only the manually set fixed resolution in kscreen is
used. Resizing the window won't change the guest's resolution anymore.

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

[plasmashell] [Bug 356668] Plasma crashes when resuming from suspend with different screen

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356668

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353203

--- Comment #44 from OlafLostViking  ---
I can not confirm that completely. While it seems to be true that the login is
faster (but no guarantees for now ;-) ), a lot of autostarted programs (be it
by explicit autostart or by session restoration) now take this time to finally
start up. The desktop/plasmashell is (partly?) there and seems to be useable,
but a lot of the programs are just starting much later (and in case of programs
showing dialogs, pop up all together - like a restored kontact with open mails
or the CopyAgent from copy.com).

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

[kmail2] [Bug 355198] Feature: Navigation through Mails using Arrow Keys

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355198

--- Comment #5 from OlafLostViking  ---
@Sebastian So for you left/right works?

I am using the aforementioned versions and left/right are _not_ working for me.
It only opens/closes message trees of grouped threads but is not switching
between messages.

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

[kmail2] [Bug 356805] New: welcome screen "modal" after first setup

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356805

Bug ID: 356805
   Summary: welcome screen "modal" after first setup
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

[This applies to KMail 5.0.3 which isn't selectable in the version drop down
above.]

After creating the first mail account from the setup assisstant of KMail (local
.* folders deleted - so basically a new user), the "Welcome to KMail 5.0.3"
screen is displayed and stays there even if the user clicks into the folder
list.

After a restart of KMail clicking the folder list shows the correct message
list instead of the welcome screen.

Reproducible: Always

Steps to Reproduce:
1. new user
2. create new IMAP account with assisstant
3. let it download the mails in the background


Actual Results:  
4. don't be able to access the message list (welcome screen is constantly
displayed)

Expected Results:  
4. access message list by clicking in the folder list

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

[kmail2] [Bug 355198] Feature: Navigation through Mails using Arrow Keys

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355198

--- Comment #7 from OlafLostViking  ---
I just rechecked - this bug is still valid for a "pure" KF5 installation as
well as one on a computer just recently updated from KDE4.

The shortcuts in the menu for Next and Previous message are set to "none". So I
am a little bit confused why it works on your setups but not mine.

@Laurent: Shall I open another report or can you change the status here?

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

[kmail2] [Bug 355198] Feature: Navigation through Mails using Arrow Keys

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355198

--- Comment #3 from OlafLostViking  ---
In my case: The Archlinux package version is 15.08.3-2 (amd64). The About
dialog says 5.0.3, using frameworks 5.17.0 and Qt 5.5.1.

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

[Baloo] [Bug 356769] New: Baloo crashes when database locks are held

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356769

Bug ID: 356769
   Summary: Baloo crashes when database locks are held
   Product: Baloo
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: olaf.the.lost.vik...@gmail.com
CC: pinak.ah...@gmail.com

[This report applies to ballo 5.17.0 which isn't selectable in the Version drop
down above.]

After my obligatory "akonadictl restart" after suspend, starting the
baloo_indexer lead to crashes since the baloo-database for emails was still
locked. The culprit as a baloo indexer process from yesterday that wasn't
stopped by akonadictl (another bug?). After killing that process manually the
new could start.

A dialog telling the user why it has problems starting seems more graceful than
just crashing ;-)

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

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346181

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[kscreenlocker] [Bug 353973] screenlocker password input mixing up characters?

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353973

--- Comment #2 from OlafLostViking  ---
Sure. I'll install whatever you have ;-)

(e-mail in German would be fine if you want to send sth)

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

[kmail2] [Bug 355198] Feature: Navigation through Mails using Arrow Keys

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355198

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
This is actually a regression from earlier KMail versions (pressing left/right
changed the messages, pressing up/down scrolled in the message view). Can you
change the priority from "wishlist" to actual "bug"?

When pressing SHIFT when "navigating" with the arrow keys, it's even a
combination of the old and the new behaviour ;-)

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

[kmail2] [Bug 356657] Notification popups not readable

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356657

--- Comment #1 from OlafLostViking  ---
Just to show how this can be a problem: the reason for me not being able to
send an email was that the new KMail uses kwallet5 which didn't provide the
correct password. But as KMail's popup told me my problem is the authtication
*method* (PLAIN not supported...) and, as written above, the message from the
server itself was not readable, I didn't expect any problems with my
credentials. After changing the password manually sending emails works again.

Oh, and the popup is shown "anywhere" but not near or even in the notification
area of Plasma. But that could also be a KWin or Plasma problem (as they both
are struggeling a lot with multiple screens). I'm just mentioning it as this
could lead to more people not even ever realising there was a message
displayed. As this is an error message a modal dialog seems more appropriate.
But that's another story ;-)

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

[kmail2] [Bug 356657] New: Notification popups not readable

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356657

Bug ID: 356657
   Summary: Notification popups not readable
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

[This is for KMail 5.0.3, which is not selectable in the Version drop down.]

After updating to *5, KMail can no longer send out mails. I guess another
configuration setting wasn't ported correctly. But the notification popup,
which shows the server response on error, is a) too small to show the whole
message (only the text telling me that the following - not visible - message
was sent by the server is readable), b) disappears too fast/cannot be pinned to
the foreground or reread in the notification area of plasma and c) cannot be
logged to a file (I tried to log the notification of KMail and the SendLater
agent into a logfile to be able to read the message, but no file is created at
the given path).

Reproducible: Always

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

[plasmashell] [Bug 348608] notifications pop up on wrong monitor

[OlafLostViking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348608

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #3 from OlafLostViking  ---
Perhaps see #356461

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