[plasmashell] [Bug 390177] Upgrade to 5.12 activated window decoration menu button, making in-app menu bars disappear

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com
Version|5.12.2  |5.19.4

--- Comment #47 from OlafLostViking  ---
I just encountered the same problem when updating to 5.19.4 on Manjaro. Adding
and removing the menu bar button in the windows decoration did not bring the
menus back.

What worked in the end was after the removal of the burger menu to run in my
.config dir: find ./ -type f -exec sed -i
's/MenuBar=Disabled/MenuBar=Enabled/g' {}

I may be old fashioned, but on the desktop, I really want to have menu bars :-)

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

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

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

--- Comment #14 from OlafLostViking  ---
Still valid.

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

[kscreenlocker] [Bug 417743] kscreenlocker_g crashes with segmentation fault after stand by

[OlafLostViking]

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

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 375331] Black screen after resuming from hibernation

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com
Version|5.8.5   |5.18.0

--- Comment #9 from OlafLostViking  ---
@7 Absolutely. `kscreen-doctor` (on text console) shows my `eDP1` is connected
but disabled. Enabling it via `kscreen-doctor` gives no error message, but the
screen stays black and the output of another `kscreen-doctor` call shows it
still as disabled.

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

[kmail2] [Bug 384554] Message dialogs keep stacking up

[OlafLostViking]

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

--- Comment #3 from OlafLostViking  ---
Can I be of any further assistance?

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

[kontact] [Bug 327282] Google calendar/ical event gets doubled, i.e. added twice - event visible with no calendar displayed

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

Version|5.7.3   |5.9.2
 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #8 from OlafLostViking  ---
Unfortunately, I can confirm it for 5.9.3. Just duplicated a huge event and
invited half the company over our Google enterprise calender... :-(

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

[kmail2] [Bug 362575] Cannot unsubscribe IMAP folder

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
Version|5.2.1   |5.9.1
 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #6 from OlafLostViking  ---
Unfortunately, I just encountered that very problem on 5.9.1 with a Gmail
account.

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

[Falkon] [Bug 393921] New: Sort "Cookie Filtering" lists

[OlafLostViking]

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

Bug ID: 393921
   Summary: Sort "Cookie Filtering" lists
   Product: Falkon
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

The white- or blacklist of the "Cookie Filtering" dialog could be sorted, so
that it's easier to find a certain entry.

* alphabetically   (abc.com, def.com, ghi.abc.com)
* hierarchical, alpabetical (abc.com, --ghi.abc.com, def.com)

I'd prefer the second variant, where each level of domains is a new sorting
key/level.

BTW: When already touching that dialog, double clicking/pressing F2 to
rename/edit an entry would be a nice comfort feature :)

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

[Falkon] [Bug 393919] New: Support "Session Cookies"

[OlafLostViking]

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

Bug ID: 393919
   Summary: Support "Session Cookies"
   Product: Falkon
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

I wasn't able to replicate the "Session Cookie" behaviour from Konqueror.

I want to allow certain sites to store cookies permanently (just like now with
the "Cookie Filtering" whitelist) while accepting all other cookies but
throwing them away after closing the window. When I select "Delete cookies on
close", my wanted cookies (like from bugs.kde.org) also get thrown away. While
"Allow storing of cookies" without deleting them will let everything into my
cookie jar.

So a possiblity to whitelist certain sites (cookies granularity would even be
more awesome, but ... well ;-) ) and accepting but throwing away at the end
cookies from all other sites would be quite helpful.

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

[kmail2] [Bug 374546] OpenPGP signatures performed by KMail, not recognized by other email clients

[OlafLostViking]

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

--- Comment #18 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I've looked a little bit further into this problem and it seems in my case it
is at least partly an @#$&* Exchange server that is/has to be used for sending.
It's simply forwarding Thunderbird mails, but rewriting the KMail mails to a
new base64 encoded attachment (which, as written, contains the PGP message).
Other mail servers don't seem to do that. @Vishnu, did you use an Exchange
sometimes?

If this is really true, would it be possible to somehow "trick" Exchange into
not rewriting the 7-Bit MIME part (ASC armored PGP message) into a base64 MIME
part (I'm not knowledgable enough to understand why it is even doing that.
7Bit/1000chars should be fine.)? 

BTW:
> Why am I asked to click on "Decrypt Message" on every mail
> in the message list? It would probably be more convenient
> to just try to decrypt it and only when there's not fitting
> key in the agent ask for user interaction.
Found the setting! That's why I'd really enjoy using KMail again - it has so
many things I wish for :-)

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

[kmail2] [Bug 374546] OpenPGP signatures performed by KMail, not recognized by other email clients

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

Version|5.4.0   |5.8.0
   Platform|Other   |Archlinux Packages

--- Comment #17 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
KMail 5.8.0 is still not usable as a mail client when using encryption with
openpgp. Now I am not even able to force it as described before by using
unicode characters anymore (or I am missing something...).

KMail itself will only show an attachment with "Version 1" in it and another
(called msg.asc) which contains the message as I was able to verify with "gpg
--decrypt msg.asc".

Thunderbird/Enigmail just says the e-mail was broken by Exchange and isn't able
to repair/show the message.


BTW: Why am I asked to click on "Decrypt Message" on every mail in the message
list? It would probably be more convenient to just try to decrypt it and only
when there's not fitting key in the agent ask for user interaction.

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

[Akonadi] [Bug 392948] New: Akonadi fails to start on a fresh system (cannot create directory)

[OlafLostViking]

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

Bug ID: 392948
   Summary: Akonadi fails to start on a fresh system (cannot
create directory)
   Product: Akonadi
   Version: GIT (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

I just installed a fresh KDE Neon Developer Edition using the development
branches because I wanted to check for another critical (for me) bug (#374546).

The assistant when starting Kontact the first time fails without giving usable
error messages. The console reveals that the database directory is not created
automatically and akonadi fails to start. Bad for new users ;-)

olaflostviking@neon-valhalla:~$ akonadictl start  
olaflostviking@neon-valhalla:~$ Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/olaflostviking/.local/share/akonadi/mysql.conf",
"--datadir=/home/olaflostviking/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-olaflostviking.7ef5j8/mysql.socket",
"--pid-file=/tmp/akonadi-olaflostviking.7ef5j8/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "180409 23:03:19 [Note] /usr/sbin/mysqld
(mysqld 10.0.34-MariaDB-0ubuntu0.16.04.1) starting as process 1809 ...\n180409
23:03:19 [Warning] Can't create test file
/home/olaflostviking/.local/share/akonadi/db_data/neon-valhalla.lower-test\n\x07/usr/sbin/mysqld:
Can't change dir to '/home/olaflostviking/.local/share/akonadi/db_data/'
(Errcode: 2 \"No such file or directory\")\n180409 23:03:19 [ERROR]
Aborting\n\n180409 23:03:19 [Note] /usr/sbin/mysqld: Shutdown complete\n\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...

olaflostviking@neon-valhalla:~$ cd .local/share/akonadi/ 
olaflostviking@neon-valhalla:~/.local/share/akonadi$ ls -l
total 24
-rw-rw-r-- 1 olaflostviking olaflostviking  150 Apr  9 23:03
akonadi_control.error
-rw-rw-r-- 1 olaflostviking olaflostviking  150 Apr  9 23:03
akonadi_control.error.old
-rw-rw-r-- 1 olaflostviking olaflostviking0 Apr  9 23:03 akonadictl.error
-rw-rw-r-- 1 olaflostviking olaflostviking0 Apr  9 23:03
akonadictl.error.old
-rw-rw-r-- 1 olaflostviking olaflostviking  995 Apr  9 23:03
akonadiserver.error
-rw-rw-r-- 1 olaflostviking olaflostviking  995 Apr  9 23:03
akonadiserver.error.old
-rw-rw-r-- 1 olaflostviking olaflostviking 3423 Apr  9 22:58 mysql.conf
drwxrwxr-x 4 olaflostviking olaflostviking 4096 Apr  9 22:58 search_db
lrwxrwxrwx 1 olaflostviking olaflostviking   34 Apr  9 22:58
socket-neon-valhalla -> /tmp/akonadi-olaflostviking.7ef5j8
olaflostviking@neon-valhalla:~/.local/share/akonadi$ mkdir db_data
olaflostviking@neon-valhalla:~/.local/share/akonadi$ akonadictl start
olaflostviking@neon-valhalla:~/.local/share/akonadi$ Connecting to deprecated
signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
/usr/bin/mysqlcheck: Got error: 1049: Unknown database 'akonadi' when selecting
the database
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.
org.kde.pim.maildirresource: the resource is not properly configured: there is
no config file for the resource. We create a new one.
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.
"No file selected."
org.kde.pim.maildirresource: the resource is not properly configured: there is
no config file for the resource. We create a new one.
QObject::killTimer: Timers cannot be stopped from another thread

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

[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> 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 95733] KMail should always encode as base64 any non text/* and non message/* MIME part

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[konsole] [Bug 388771] New: Bookmarks could include an initial script to be run

[OlafLostViking]

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

Bug ID: 388771
   Summary: Bookmarks could include an initial script to be run
   Product: konsole
   Version: 17.12.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: bookmark
  Assignee: konsole-de...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

A bookmark could include an script to be run after open the tab to
* set the tab title (this could also be part of the bookmark, alternatively)
* set different prompts
* connect to a SSH server
* open up a monitoring tools

I'm using bookmark folders per project so that I get one or two shells in each
relevant repository root, the build directories, the special environment etc.
So f.ex. having a special tab title set automatically would be helpful.

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

[kdevelop] [Bug 388710] New: KDevelop needs to be restarted after activation of "Ninja" plugin/no build tool view in project settings

[OlafLostViking]

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

Bug ID: 388710
   Summary: KDevelop needs to be restarted after activation of
"Ninja" plugin/no build tool view in project settings
   Product: kdevelop
   Version: 5.2.1
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Build tools: Ninja
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

After enabling the "Ninja" plugin in KDevelop, I was able to set the default
build program to "Ninja" in the "CMake" plugin. But in the project settings the
configuration of the "Make" tools vanishes while at the same time no "Ninja"
settings are visible. You need to restart KDevelop so that these settings are
finally vivisble.

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

[kmail2] [Bug 374546] OpenPGP signatures performed by KMail, not recognized by other email clients

[OlafLostViking]

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

--- Comment #16 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Can I provide some mails, too, that would help to analyse the problem? What
exact combination of mails would be needed? Or is everything understood and
it's "just" a matter of fixing?

Since it seems to be working with Vishnu, could it be a combination of
KMail/kgpg/gpgme/etc.? Thanks!

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

[plasma-nm] [Bug 388516] New: Support "partially saved" password (for tokens like yubikey)

[OlafLostViking]

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

Bug ID: 388516
   Summary: Support "partially saved" password (for tokens like
yubikey)
   Product: plasma-nm
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

I use a yubikey to connect to an OpenVPN server. For now I told plasma-nm to
not save the password so I get prompted everytime. There I enter a "fixed"
password and append a one time one with the help of the yubikey (just behaves
like a keyboard). So just the normal password dialog/logic is needed.

It would be nice, if plasma-nm could save the fixed password part and just let
me enter the rest. F.ex. by having another drop-down option "Save password ...
and prompt every time." while setting the cursor right after the saved and
pre-filled out password. Like that I won't have to enter the fixed password and
can just trigger the yubikey entry after clicking on Connect.

PS: I don't think this is related to #350521 , as we don't need any special
challenge/response.

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

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

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
Version|Git (master)|5.7.0

--- Comment #9 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
After showing collegues KMail I stumbled upon this "feature" again. I am well
aware how to get around that (as kindly explained above), but this surely isn't
a well received workaround.

Since this report is closed, shall we continue discussing in here or open a new
one? Thanks.

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

[kmail2] [Bug 374546] OpenPGP signatures performed by KMail, not recognized by other email clients

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #14 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I am using KMail 5.7.0 and it cannot verify signatures sent by itself ("Message
was signed with unkown key 0x1234 The validity of the signature cannot be
verified. Status: Bad signature."). When I add Unicode characters into the
message body, the signature is verified correctly. Mails sent by Thunderbird
always verify.

Additionally, an encrypted and signed message from Thunderbird is shown in
KMail correctly "stacked" (after clicking decrypt, KMail shows the blue
"Encrypted message" frame with a valid green "Signed by ..." frame inside)
while an encrypted mail sent by KMail will simply be shown as an empty mail
with the msg.asc and AT00..1 attachments (after clicking "decrypt" one can very
shortly see the blue frame).

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

[kmail2] [Bug 388036] New: Include support for autocrypt

[OlafLostViking]

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

Bug ID: 388036
   Summary: Include support for autocrypt
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

To improve the ease of use for PGP based mail encryption, it'd be great if
KMail could join the ranks [1] of autocrypt [2] supporting mail client.s

Basically, Autocrypt just adds another mail header which includes meta
informations for further encryption, including the public key of the sender.

[1] https://autocrypt.org/en/latest/dev-status.html
[2] https://autocrypt.org/en/latest/details.html

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

[kdevelop] [Bug 343935] Consider adding support for Meson build system

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> 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 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[OlafLostViking]

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

--- Comment #18 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Just as a little remark, considering a different use case for Plasma:

All mentioned bug reports complain about the widgets been displaced after
playing a game. Another annoying thing are projectors. When attaching the
notebook to give a presentation, Plasma changes (hopefully... but that's
another topic ;-) ) the resolution to the projector's, which can be as low as
1024x768.

As I started mis-using the Plasma desktop as a post-it-widget dumpground for
topic based ToDos for now, they are resized and many even reduced to the small
yellow icon. Restoring them all takes quite a while.

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

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[Akonadi] [Bug 363928] After suspend akonadiserver use about 2 cpus

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> 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 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[plasma-pa] [Bug 385250] New: Cannot change volume per channel

[OlafLostViking]

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

Bug ID: 385250
   Summary: Cannot change volume per channel
   Product: plasma-pa
   Version: 5.10.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: olaf.the.lost.vik...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

plasma-pa cannot (or, to be fair, I cannot find it ;-) ) change the volume per
channel (like left 10% louder than right) as pavucontrol or kmix can. As
plasma-pa is meant to substitute kmix, this would be a regression, which makes
using headphones quite unpleasant for people with hearing problems. For now I
installed pavucontrol and showed the affected person how to use it. But that's
merely a workaround.

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

[kmail2] [Bug 384554] Message dialogs keep stacking up

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #2 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Created attachment 107793
  --> https://bugs.kde.org/attachment.cgi?id=107793=edit
Dialog starts stacking up seconds after starting up Kontact.

Sure thing! See attachment.

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

[kmail2] [Bug 384554] New: Message dialogs keep stacking up

[OlafLostViking]

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

Bug ID: 384554
   Summary: Message dialogs keep stacking up
   Product: kmail2
   Version: 5.6.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

When KMail/Akonadi tries to sync with a server and there is an error (like in
my case an invalid certificate) it keeps on trying and stacking up dialogs
(asking if I want to accept the certificate). When I'm not at the computer,
it's quite possible (just happened ;-) ) that I come back to around 200 stacked
dialogs.

Possible solution: As long as the user didn't react (saying it's okay or not
okay to continue or whatever answer is needed for a dialog), no new tries of
the action mentioned should be started.

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

[trojita] [Bug 321374] Multiple accounts

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> 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 356657] Notification popups not readable

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

Version|unspecified |5.5.1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #3 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I am now using KMail 5.5.2 [not selectable in the version drop down].

After deliberately setting wrong passwords for receiving mails, a popup dialog
is opened _in the background_ (behind Kontact). But at least it's telling me
what's wrong and it won't disappear without interaction.

But setting a wrong password for the SMTP server still only triggers a
notification and no dialog. And this says the server wouldn't support PLAIN
(which is plain wrong ;-) ). The size of the notification is now big enough for
me to read everything, though.

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

[kmail2] [Bug 356657] Notification popups for authentication error misleading

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

Summary|Notification popups not |Notification popups for
   |readable|authentication error
   ||misleading

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

[kdevelop] [Bug 310725] kdevelop crashes when trying to remove breakpoint

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #5 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I think I just experienced the same (wasn't found by DrKonqi), sorry for
duplicate in that case: bug #381312

Additionally, I guess the following bug reporters have the same problem:
- bug #334877
- bug #340844
- bug #347529
- bug #348945
- bug #350490
- bug #361693
- bug #363237
- bug #372937
- bug #377995

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

[kdevelop] [Bug 381312] Crash after setting a breakpoint/breakpoint moved

[OlafLostViking]

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

--- Comment #1 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Mh, this could be related to bug #310725 .

Other reports about crashes after breakpoint editing (weren't found by
DrKonqi):
- bug #334877
- bug #340844
- bug #347529
- bug #348945
- bug #350490
- bug #361693
- bug #363237
- bug #372937
- bug #377995

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

[kdevelop] [Bug 381312] New: Crash after setting a breakpoint/breakpoint moved

[OlafLostViking]

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

Bug ID: 381312
   Summary: Crash after setting a breakpoint/breakpoint moved
   Product: kdevelop
   Version: 5.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.1.1)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I returned to my code view after debugging with a breakpoint set. There I
edited some code and wanted to set a new breakpoint. After clicking into the
icon bar the breakpoint appears at a totally different place (potentially due
to inserted/deleted lines of code) and KDevelop crashed.

- How to replicate:

While I didn't manage to let KDevelop crash again, you can at least see the
breakpoint problem by setting a breakpoint, inserting some lines before it and
then setting another breakpoint/deleting it. The positions will be messed up.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcb05cea840 (LWP 3984))]

Thread 13 (Thread 0x7fca80c7a700 (LWP 15338)):
#0  0x7fcafa08ea29 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fcafa049143 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fcafa049b2b in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fcafa049d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fcb033eee9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fcb0339521a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fcb031b740a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fcb031bbcbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fcafc4b8297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fcb02ad025f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fcaaa79d700 (LWP 4669)):
#0  0x7fcafc4be39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fcaf3ea6ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fcaf3ea6b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fcafc4b8297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fcb02ad025f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fcaa9f9c700 (LWP 4129)):
#0  0x7fcafa049136 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fcafa049b2b in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fcafa049d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fcb033eee9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fcb0339521a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fcb031b740a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fcb00cdcd3f in  () at /usr/lib/libKDevPlatformLanguage.so.10
#7  0x7fcb031bbcbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fcafc4b8297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fcb02ad025f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fcaab7fe700 (LWP 4086)):
#0  0x7fcb02ac62bd in poll () at /usr/lib/libc.so.6
#1  0x7fcafa049bf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fcafa049d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fcb033eee9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fcb0339521a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fcb031b740a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fcb031bbcbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7fcafc4b8297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fcb02ad025f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fcaabfff700 (LWP 4027)):
#0  0x7fcafc4be39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fcb031bd0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fcaf764f3cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fcaf76542b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fcaf764e913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fcaf7651b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fcb031bbcbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7fcafc4b8297 in start_thread () at /usr/lib/libpthread.so.0

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[OlafLostViking]

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

--- Comment #7 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Sorry! Bug #381310

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

[kdevelop] [Bug 381310] Tool views broken/not repainted when detached

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #6 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I'd like to see this, too, because of bug # . :)

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

[kdevelop] [Bug 381310] New: Tool views broken/not repainted when detached

[OlafLostViking]

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

Bug ID: 381310
   Summary: Tool views broken/not repainted when detached
   Product: kdevelop
   Version: 5.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

I have two monitors, but both with a resolution too low to show everything
needed. So I open the "Variables tool view" in detachable state when debugging
and move it onto the other screen.

When returning to Debug mode after working in Code mode, the tool view won't be
redrawn anymore. It just "copies" the pixels underneath when opened. Since I
know where the view should be, I can move and resize it but the initially
copied "background pixels" stay there. To see the real content, I have to
redock and detach it manually again.

Perhaps this can be solved by taking bug #377934 into account?

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

[kdevelop] [Bug 381240] New: "Number of simultaneous jobs" in "Make settings" always initially disabled

[OlafLostViking]

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

Bug ID: 381240
   Summary: "Number of simultaneous jobs" in "Make settings"
always initially disabled
   Product: kdevelop
   Version: 5.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

When opening the "Make settings" in the "Configure Project" dialog, the "Number
of simultaneous jobs" input field is always grayed out, even if the "Override
number of jobs" checkbox is active. To change the number, I have first uncheck
this box and re-activate it. After that, the number input field is active
again.

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

[kopete] [Bug 378012] Crash when going online

[OlafLostViking]

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

--- Comment #2 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Dear Pali,

actually I only sent this via Dr Konqi, which said the bt would be useful. So,
since I don't have any further details and I also cannot reproduce it reliably,
the report should probably be closed.

Thanks!

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

[kopete] [Bug 378012] New: Crash when going online

[OlafLostViking]

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

Bug ID: 378012
   Summary: Crash when going online
   Product: kopete
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

Application: kopete (1.11.3)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.4-1-ARCH x86_64
Distribution: "Arch Linux"

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

On a freshly rebooted computer, I went online with Kopete. KWallet asked for
the password, Kopete went online with some accounts and then crashed.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f863da52840 (LWP 2184))]

Thread 3 (Thread 0x7f861ee7f700 (LWP 3395)):
#0  0x7f8639cf767d in poll () at /usr/lib/libc.so.6
#1  0x7f86359647a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f86359648bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f863b4c9f8e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#4  0x7f863b49843f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#5  0x7f863b4987a5 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQtCore.so.4
#6  0x7f863b386779 in QThread::exec() () at /usr/lib/libQtCore.so.4
#7  0x7f86252a32b8 in  () at /usr/lib/kde4/kopete_jabber.so
#8  0x7f863b38904a in  () at /usr/lib/libQtCore.so.4
#9  0x7f86372c62e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f8639d0154f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f861f680700 (LWP 3394)):
#0  0x7ffdb119f939 in  ()
#1  0x7ffdb119fbc5 in clock_gettime ()
#2  0x7f8639d0e826 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7f863b3e3a85 in  () at /usr/lib/libQtCore.so.4
#4  0x7f863b4cae15 in  () at /usr/lib/libQtCore.so.4
#5  0x7f863b4c963c in  () at /usr/lib/libQtCore.so.4
#6  0x7f863b4c9705 in  () at /usr/lib/libQtCore.so.4
#7  0x7f8635963c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7f86359646cb in  () at /usr/lib/libglib-2.0.so.0
#9  0x7f86359648bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x7f863b4c9f8e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#11 0x7f863b49843f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#12 0x7f863b4987a5 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQtCore.so.4
#13 0x7f8624e4d453 in QCA::SyncThread::run() () at /usr/lib/libqca.so.2
#14 0x7f863b38904a in  () at /usr/lib/libQtCore.so.4
#15 0x7f86372c62e7 in start_thread () at /usr/lib/libpthread.so.0
#16 0x7f8639d0154f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f863da52840 (LWP 2184)):
[KCrash Handler]
#6  0x7f863cbe16a0 in  () at /usr/lib/libkopete.so.4
#7  0x7f863cbe157f in  () at /usr/lib/libkopete.so.4
#8  0x7f863cbe15e9 in  () at /usr/lib/libkopete.so.4
#9  0x7f863b4b1f44 in QObjectPrivate::deleteChildren() () at
/usr/lib/libQtCore.so.4
#10 0x7f863b4b459c in QObject::~QObject() () at /usr/lib/libQtCore.so.4
#11 0x7f863bf74c09 in KNotification::~KNotification() () at
/usr/lib/libkdeui.so.5
#12 0x7f863b4b3a58 in QObject::event(QEvent*) () at /usr/lib/libQtCore.so.4
#13 0x7f863a542f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQtGui.so.4
#14 0x7f863a549e3c in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQtGui.so.4
#15 0x7f863bf4932a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkdeui.so.5
#16 0x7f863b499b6d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/libQtCore.so.4
#17 0x7f863b49d046 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQtCore.so.4
#18 0x7f863b4c9dfe in  () at /usr/lib/libQtCore.so.4
#19 0x7f86359645a7 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#20 0x7f8635964810 in  () at /usr/lib/libglib-2.0.so.0
#21 0x7f86359648bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#22 0x7f863b4c9f6e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#23 0x7f863a5ebed6 in  () at /usr/lib/libQtGui.so.4
#24 0x7f863b49843f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#25 0x7f863b4987a5 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQtCore.so.4
#26 0x7f863b49e209 in QCoreApplication::exec() () at
/usr/lib/libQtCore.so.4
#27 0x00413f65 in  ()
#28 0x7f8639c35511 in __libc_start_main () at 

[kscreenlocker] [Bug 377428] New: Indicate if Num Lock is active.

[OlafLostViking]

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

Bug ID: 377428
   Summary: Indicate if Num Lock is active.
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: breeze-theme
  Assignee: plasma-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

(my current version is 5.9.3, which isn't selectable above)

My TKL keyboard as well as my notebook keyboard map certain "normal" keys to
number keys if Num Lock is active. Indicating this on the lockscreen just like
with Caps Lock could be helpful.

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

[kdevelop] [Bug 376979] New: angle brackets in doxygen comments break syntax highlighting

[OlafLostViking]

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

Bug ID: 376979
   Summary: angle brackets in doxygen comments break syntax
highlighting
   Product: kdevelop
   Version: 5.0.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

Using angle brackets inside of doxygen comments breaks the syntax highlighting.
After the opening <, the highlighting changes and only gets back to "comment
mode" after the closing > of _another_ tag.

Example:

/**
 * Lorem  dolor  amet.
 */

It's probably related to the old bug #155100 .

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

[kdevelop] [Bug 321965] Highlighting broken by previous multibyte characters

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[neon] [Bug 371722] Let crash handler install debug packages

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 362516] Plugin Request: SMS

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 333832] KDE Connect in KTP (Kde TelePathy)

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 367999] It would be a "killer-app" with akonadi/kadressbook integration and full SMS chat support

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[OlafLostViking]

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

--- Comment #10 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I'm happy to read about your plans - thank you!

For a functionality that lets me control the phone on my desktop (the best
would be just "mirror" one Android app into a window on my desktop) another bug
report would be better, right? Or would that fit into here, too?

(Background: using Android applications like single-device Telegram with
encrypted chats on the desktop to not always switch between devices)

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

[kdeconnect] [Bug 370919] Keyboard to smartphone

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdevelop] [Bug 274430] KDevelop syntax highlighting wrong on lines containing unicode characters

[OlafLostViking]

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

--- Comment #9 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Just tried with 5.0.3 (still valid) and wanted to pose a question to the
KDevelop-developers:

Since this is a quite old bug report, initially for KDevelop 4.x, I wonder if
it's wanted by you to keep this problem in this report or open a new one with
an up-to-date version number? Not that it will be ignored when scanning through
the bug lists and deleted eventually since it's for the 4.x branch.

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

[kdevelop] [Bug 274430] KDevelop syntax highlighting wrong on lines containing unicode characters

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #8 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I just tried

std::cout << "OlafLostViking ❤ KDevelop!" << std::endl;

in KDevelop 5.0.2 and encountered the very same problem.

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

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

[OlafLostViking]

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

--- Comment #45 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
After the VM window was in fullscreen size, kscreen/plasma no longer
automatically adapts to a new (smaller or bigger) size of the VM window. It's
necessary to manually adapt to the new size just like after the very first
login.

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

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

[OlafLostViking]

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

--- Comment #44 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Sorry for the double post. But after talking about the display manager: What
about setups without display managers? Where the plasma sessions is started
directly by systemd or sth. similar?

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

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

[OlafLostViking]

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

--- Comment #43 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
(In reply to Sebastian Kügler from comment #42)
> That means that if you log into a fresh session, we don't do anything on
> login wrt screen setup. We expect the system to be set up.

Oh, I'm sorry, now I understand! As I'm currently having so many problems with
Plasma and multiscreen I totally forgot about that possibility of changing
screens ;-D.

Since I cannot remember seeing a messed up resolution with native modesetting
in SDDM (poulsbo doesn't count...), I agree with you on real hardware. Getting
things like rotated screens/orientation of tablets etc. over DDC or whatever
tablets are using is probably too much to ask for now ;-).


> With the current state, we now detect if the current resolution goes away,
> and we react to that by modesetting the new preferred resolution. So if you
> log in to a fresh vm, the login manager (or X startup) has to take care of
> that, to avoid unnecessary mode changes.

Adapting to a changing preferred resolution is basically the most important
thing. I just retried it (Neon is great for this!) and it still won't adapt
until I manually adapted the resolution in kscreen at least once (just as you
described).

To _always_ switch to the preferred resolution (as long as the setting to
always use preferred mode is active [f.ex. by some administrative or /etc/skel
file entry - you do not necessaryily have to had a session running to have
non-default settings]) could also be an alternative in the case of VMs, where
SDDM doesn't set the correct resolution for now. Just think about automatically
started fullscreen VMs at some kind of kiosk.

On the other hand I understand that this should be the display manager's job...
:-/ I'll try to play around with it a little bit. Perhaps there's another
solution.


> The move from projector problem, I'm not sure I understand.

Sorry, I didn't make myself very clear. And after typing up a looong paragraph
explaining it, I realized this would open up pandorra's box. So for now I'd say
ignore what I said at this point ;-)


> I like the idea of making the preferred mode more prominent, or logical in
> the UI, I'll give that some more consideration. Currently working on bits
> and pieces for an improved KCM, so that kind of input is well-timed. :)

Great! I'm glad you are improving kscreen more and more.

And if you're redesigning, please prevent the screen "icons" jump around as
soon as you enable them - setting up a huge mulit-monitor setup on a low
resolution notebook screen is a horror *duck and run* ;-D

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

[kopete] [Bug 372886] kopete crashes when OTR session is initiated without key

[OlafLostViking]

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

--- Comment #4 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Created attachment 102470
  --> https://bugs.kde.org/attachment.cgi?id=102470=edit
backtrace of kopete crashing when receiving an OTR message while not having a
key on our own

The crash handling dialog didn't offer any more symbols to install. But
--nofork did the trick :D

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

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

[OlafLostViking]

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

--- Comment #41 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I'm not sure if I understood you correctly. But if you suggested that, when
starting a plasmashell session, you set the initial resolution to the size of
the VM window (preferred resolution as shown by xrandr), independently of what
the last set resolution was, I agree. So, do not try to tranfer the resolution
of the last shutdown to the new startup. Always stay with the preferred mode
until the user manually switches away from it. And go back to the adapting size
if the user selects the window size again.

To improve the user experience, I'd suggest to add a checkbox "Use preferred
resolution" which is checked by default. And only when the user deactivates
that, plasma uses fixed resolutions as given in kscreen. By using this approach
it would even be possible for a user to always stay with a "strange" resolution
even when rebooting the VM (plasma always restores the last selected resolution
when the checkbox wasn't selected). This would also help people on "real"
hardware that have to carry their machine from projector to projector. Plasma
wouldn't switch between different resolutions if the user forced f.ex.
1024x768. Only after selecting "Use preferred mode" plasma/kscreen takes back
command and adapts to the resolution of the hardware/vm window.

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

[kopete] [Bug 372886] kopete crashes when OTR session is initiated without key

[OlafLostViking]

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

--- Comment #2 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I used your PPA as suggested in bug #362535 and there it happens, too. Just add
a new account without a key and initiate an OTR session from a peer.
Unfortunately, even though I installed kopete-dbg, neither on the console nor
in the KDE Crash Handler there are any details.

So I started kopete in gdb, but "bt" just said "No stack.". How can I get you a
useable backtrace from your PPA in Ubuntu? Thanks!

-- 
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]

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

--- Comment #21 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Sorry - I'm not that fast ;-)

Since I'm no Ubuntu user, I was struggling to get your repo to work. But in the
meantime I found out I have to add the "universe" repo for that. (Perhaps it
would be possible that the Neon guys just include your kopete sources into
their build system? It would be great to have one single "reference" setup for
helping to test out new builds.)

So far it looks like the problem is fixed, now! Great - I hope this will soon
be available on my Arch machine :D

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

[kdevelop] [Bug 372923] New: wrong language parser arguments aren't pointed out

[OlafLostViking]

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

Bug ID: 372923
   Summary: wrong language parser arguments aren't pointed out
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

It's great that I can change the parser arguments in "Configure Language
Support"! But when I give a wrong one, KDevelop doesn't tell me about that but
parses the code wrongly. It would be better, if KDevelop mentions problems with
the command line arguments that aren't accepted by the underlying libclang.

Example:
I wanted to use some C++17 features and since this is not selectable in the
Profile dropdown, I added -std=c++17 to the arguments. But clang only accepts
-std=c++1z for now instead, which means not even C++11/14 is parsed anymore.

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

[kdevelop] [Bug 372875] problem with semantic highlighting: operator[ std::string ]

[OlafLostViking]

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

--- Comment #2 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Thanks for having a look!

While I agree that [ is the u_map::op[str], I am wondering why the second
bracket is coloured differently (like a normal array ]) and not in the special
colour of the first bracket [.

Just to clarify what I meant (I simply don't understand the different colours)
- not to insist that I'm right or whatever ;)

-- 
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]

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

--- Comment #18 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
(In reply to Pali Rohár from comment #17)
> From which git commit?

Mh, it looks like Kopete isn't even built for neon dev unstable. Which means I
didn't test the newest version but some older one packaged by ubuntu(?). Sorry
for the noise! (And I hope I'll get this Neon VM clean again from all these
packages ;-) )

-- 
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]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
   Platform|Archlinux Packages  |Neon Packages
Version|unspecified |Git
 Resolution|FIXED   |---

--- Comment #15 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Okay, managed to get it to work (Kopete in GIT master/Neon cannot connect to
kdetalk.net anymore, so I created another account which worked).

The problem is still there (packages from today, minutes ago). Closing the
window will break all further encrytion (even when I choose to restart the OTR
session!). Only a restart of kopete and establishing a new OTR session makes
encryption work again.

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

[kopete] [Bug 372886] New: kopete crashes when OTR session is initiated without key

[OlafLostViking]

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

Bug ID: 372886
   Summary: kopete crashes when OTR session is initiated without
key
   Product: kopete
   Version: Git
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: OTR Plugin
  Assignee: kopete-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

While testing out the newest master (installed in neon dev) I encountered a
crash which was already valid in the current stable release.

When the account does not yet have a generated OTR key but the other side
starts an OTR session, the "receiving" kopete (the one without key) crashes.

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

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

[OlafLostViking]

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

--- Comment #39 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I just updated the VM again:

* The guest desktop will still only adjust to the outer window size after it
has been changed at least once manually via kscreen to the exact size of a
resized VM window.

* The modelist in kscreen is not updated when resizing (but that's not really
critical, I'd say). So you have to open it just after resizing your outer
window.

-- 
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]

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

--- Comment #14 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Thanks for debugging!

I installed kopete in my neon test vm (400 MiB stuff X-D ), but from there it
cannot connect at all... So I wasn't able to test it for now. But will your fix
just correct the GUI or will it prevent Kopete/libotr from ending the OTR
encryption just when closing a window? The latter would be preferable, of
course ;)

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

[kdevelop] [Bug 372875] New: problem with semantic highlighting: operator[ std::string ]

[OlafLostViking]

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

Bug ID: 372875
   Summary: problem with semantic highlighting: operator[
std::string ]
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

The most awesome semantic highlighting (one if the main selling points for
KDevelop ;-) ) seems to have a problem when using the operator[] with strings.
I saw it first when using libconfig++, but I built a minimal example with
unordered_map:

std::unordered_map< std::string, std::string > kde_map;
std::cout << "KDevelop is " << kde_map[ "kdevelop" ] << "!" <<
std::endl;

Here you can see that the squared brackets are coloured differently.

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

[kdevelop] [Bug 372842] New: restore file tree state after startup

[OlafLostViking]

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

Bug ID: 372842
   Summary: restore file tree state after startup
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: file tree
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

When starting KDevelop it restores the last session state ("sub"windows, open
files, etc.) which is great (and kind of mandatory for an IDE ;-) ). But the
file tree in the projects panel is always in the default state (collapsed to
the root element).

It'd be nice, if its state could also be restored upon opening a KDevelop
session so resuming work at a specific part of a (huge/deep) hierarchy is
easier.

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

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

[OlafLostViking]

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

--- Comment #35 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
I updated the Neon VM during the last days (as well as just minutes ago) but my
plasma desktop didn't adjust itself to the VM window.

But then I opened up kscreen to check if the new "strange" resolution is
finally visible in its dropdown (which it is now!) and after applying this, the
desktop adjusts (with some delay)! This is great, thank you very much!

There still seems to be some problems as I first had to adjust the screen
manually once and the kscreen dialog is not updated with available modes when
it's opened, but after this I can finally use KDE in a fullscreen VM :D


BTW: Is SDDM using kscreen, too? (since it isn't using any other resolution but
the default in contrast to GDM that adapts just fine)

-- 
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]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #9 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Sure thing:

1. start kopete and go online

2. open XML console for the jabber account used for testing

3. send unencrypted message from another account/server/VM via KTP
3a. as expected: unencrypted message in XML console

4. initiate OTR session from the other client (KTP)
4a. Kopete and KTP show that the channel is encrypted
4b. messages sent in both directions are encrypted

===> This is the important step. Closing the window triggers the problem.
5. close chat window in kopete

6. reopen it and send message
6a. Kopete still claims that the channel is encrypted
6b. KTP correctly says the received message is unencrypted
6c. the XML console confirms this as I can read the sent message in clear text


This also "works" when using Converstations on an Android phone instead of KTP
as partner.

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

[telepathy] [Bug 368339] Add support for XEP-0313 Message Archive Management on XMPP accounts to KDE Telepathy log viewer

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

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

[OlafLostViking]

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

--- Comment #30 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
(Welcome back, I hope you are refreshed enough for all these bugs ;-) )

I'm not an expert for virt-manager. But by default my own virt-manager is just
setting up a spice-channel. This channel is then used for the communication
with the host and the vm guest (via space-vdagent). I never had a qemu-ga
channel active (or qemu-guest-agent installed in the guests).

So if you just setup a "default" KVM-VM in virt-manager and install (and
autostart, obviously) spice-vdagent in the client, everything should work
(without qemu-ga).

Out of curiosity, I installed qemu-guest-agent into my Neon VM, created a GA
channel in virt-manager and rebooted. Connecting to the channel worked, but no
changes in adapting to the outer VM window. Just logs already shown by Martin
in the journal.

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

[kdevelop] [Bug 372215] New: Crash while parsing static_assert

[OlafLostViking]

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

Bug ID: 372215
   Summary: Crash while parsing static_assert
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

By putting a "static_assert( true );" into a minimal file skeleton, KDevelop
crashes with SIG11.

The crash handler shows the following backtrace:

Thread 13 (Thread 0x7f1dc53fa700 (LWP 19454)):
[KCrash Handler]
#6  0x7f1da52523de in  () at /usr/lib/libclang.so.3.9
#7  0x7f1da5235302 in  () at /usr/lib/libclang.so.3.9
#8  0x7f1da52333f0 in  () at /usr/lib/libclang.so.3.9
#9  0x7f1da52339a5 in  () at /usr/lib/libclang.so.3.9
#10 0x7f1da52395ac in  () at /usr/lib/libclang.so.3.9
#11 0x7f1da52398c0 in  () at /usr/lib/libclang.so.3.9
#12 0x7f1da5233314 in  () at /usr/lib/libclang.so.3.9
#13 0x7f1da523c154 in clang_visitChildren () at /usr/lib/libclang.so.3.9
#14 0x7f1dc4192408 in  () at /usr/lib/libKDevClangPrivate.so.25
#15 0x7f1da5233975 in  () at /usr/lib/libclang.so.3.9
#16 0x7f1da5237c76 in  () at /usr/lib/libclang.so.3.9
#17 0x7f1da52333f0 in  () at /usr/lib/libclang.so.3.9
#18 0x7f1da523c154 in clang_visitChildren () at /usr/lib/libclang.so.3.9
#19 0x7f1dc4181577 in  () at /usr/lib/libKDevClangPrivate.so.25
#20 0x7f1dc4193504 in  () at /usr/lib/libKDevClangPrivate.so.25
#21 0x7f1da5233975 in  () at /usr/lib/libclang.so.3.9
#22 0x7f1da5232ebd in  () at /usr/lib/libclang.so.3.9
#23 0x7f1da5232fe2 in  () at /usr/lib/libclang.so.3.9
#24 0x7f1da523360c in  () at /usr/lib/libclang.so.3.9
#25 0x7f1da523c154 in clang_visitChildren () at /usr/lib/libclang.so.3.9
#26 0x7f1dc4175424 in Builder::visit(CXTranslationUnitImpl*, void*,
QHash const&, bool) () at
/usr/lib/libKDevClangPrivate.so.25
#27 0x7f1dc41a3b1a in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at /usr/lib/libKDevClangPrivate.so.25
#28 0x7f1dcc0820a9 in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevclangsupport.so
#29 0x7f1e0c314586 in
ThreadWeaver::IdDecorator::run(QSharedPointer,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#30 0x7f1e0c314b88 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#31 0x7f1e0c313a9a in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#32 0x7f1e0c313140 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#33 0x7f1e17a11d78 in  () at /usr/lib/libQt5Core.so.5
#34 0x7f1e10bf5454 in start_thread () at /usr/lib/libpthread.so.0
#35 0x7f1e173277df in clone () at /usr/lib/libc.so.6

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

[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes

[OlafLostViking]

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

--- Comment #5 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Sorry for coming back ;-)

But I now have a error-free header file not included anywhere which isn't
parsed anymore after some editing (renaming of a class). Deleting the cache
won't help either. Just copy/paste the contents to a file2.hpp makes it work
again.

Is there something we users can do in such a case to gather more meaningful
information for the kdevelop developers despite just crying "Won't work!"?

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

[kdevelop] [Bug 371747] New: Parsing problems propagate up the whole include-tree.

[OlafLostViking]

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

Bug ID: 371747
   Summary: Parsing problems propagate up the whole include-tree.
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

I have a project which has to use Intel Pin. But I am sure you can find many
projects like this, so please take this just as an example.

Deep into the include-tree of Pin there is a config.h file that includes
further headers depending on DEFINES. F.ex.:

#if !defined(FUND_TC_HOSTCPU)
#   include "fund/config-hostcpu.h"
#endif

This is not a problem when building as the build system sets the correct
values, but KDevelop cannot parse the whole project (which has to include the
"top" header ) because this config-hostcpu.h file doesn't exist.

I solved this for now by just providing DEFINES (which I hope are correct...)
in the project settings. But I don't think this should be mandatory for users
to go through (sometimes huge) external projects, understand their
include/define magic and guess (probably wrong) values to manually add to the
project.

KDevelop could f.ex. accept it doesn't understand/cannot parse a certain header
(and of course showing "Problems" when opening that!) but not propagate these
errors into the parsing of my own files.

This is probably connected to bug #371741.

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

[kdevelop] [Bug 371741] KDevelop doesn't report certain errors.

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdevelop] [Bug 371747] Parsing problems propagate up the whole include-tree.

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

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

[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes

[OlafLostViking]

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

--- Comment #4 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
After a long testing session, I found the reason for the behaviour in my case
(and some other smaller problems :-/ ) which is probably not related to OP's
case. So I created a new bug report: bug #371741

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

[kdevelop] [Bug 371741] New: KDevelop doesn't report certain errors.

[OlafLostViking]

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

Bug ID: 371741
   Summary: KDevelop doesn't report certain errors.
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
  Target Milestone: ---

== Short ==

KDevelop is not reporting a not-closed namespace in a header file. (No
"expected { to match this }" in the "Problems" tab.)



== Long ==

KDevelop is not marking problems in a header file when a namepsace is not
correctly closed. In smaller projects (I tried to build a minimal example) this
is then easily seen in the main.cpp; in my case (see below) I have no idea at
all if in any file down the tree this was ever shown. But in the end I never
saw an error; only files not getting parsed/coloured.

While I do see that a preprocessor could insert that missing } in any other
file, I, personally, would probably prefer to get a warning when the braces in
a file are not matching. Isn't that default behaviour?



== My case==

It all started with the fact that some files in my project were missing the
semantic colouring and weren't parsed anymore by the clang-parser.

For my further project internal tests I used a trivial (stand-alone, only
std::lib, simple RAII flag saver) header file that didn't get parsed anymore in
my project. I found out this only happens when the file is included in another
class. Going down the tree I finally found the culprit: a totally unrelated
header file which was used in a class that used a class that... etc that
included this header (all files along this tree failed to parse/colour).

In this header file, a namespace was opened but not correctly closed. But
KDevelop did not complain about that anywhere but simply did no longer parse
the other files using this header as well as totally unrelated headers included
by them. The "bad" file itself even looked fine - all nice colours). Compiling
fails, of course, with one of the glorious C++ error messages saying that
std::string does not exist inside of a standard library. That's how I finally
started suspecting some namespace stuff.



== Minimal example ==

* Create "New from template" CMake project
* Add file test.hpp
* contents of test.hpp (+ header guards)
namespace FOO
{
class BAR {};
* #include test.hpp
* / data types are not recognised or no error at all (bigger project)
  / missing brace marked inside of the "innocent" cpp file

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

[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes

[OlafLostViking]

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

--- Comment #3 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
Created attachment 101821
  --> https://bugs.kde.org/attachment.cgi?id=101821=edit
"proof" of kdevelop vs filesystem

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

[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #2 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
As I _guess_ this could be related, I'll just add my experience to this thread.
In my "not so huge" project, the parser sometimes stops parsing at all for
certain files (as described in #371018 it's quite slow to start so that I
sometimes don't even realise it anymore when it fails). So currently I have the
situation that no matter what I change an #include directive to, KDevelop
insists it is the old, correct file that is meant. I'll add a screenshot...

This behaviour could explain many other parts where the highlighting isn't
working anymore after switching to KDevelop 5 (until now I thought it's a huge
mess in my code that the parser simply gave up or so - but here it's pretty
obvious).

Restarting KDevelop doesn't help. It starts, takes its 5 seconds or so clang
salute (see #369164) and then stays like shown in the following screenshot.
Even clearing the DUCHAIN cache by deleting the whole kdevelop .cache directory
doesn't work (which irritates me a lot ;-) ).

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

[kdevelop] [Bug 371018] CPP parser responds very slow after user action

[OlafLostViking]

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

OlafLostViking <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

-- 
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 <olaf.the.lost.vik...@gmail.com> 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 <olaf.the.lost.vik...@gmail.com> 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 <olaf.the.lost.vik...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from OlafLostViking <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> 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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
(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

[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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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 <olaf.the.lost.vik...@gmail.com> ---
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.