[kmail2] [Bug 336205] kmail2 crashes after startup and all windows was opened

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED
Version|unspecified |5.3.0

--- Comment #5 from Denis Kurz  ---
Ulf, thank you for your feedback. Is it possible for you to provide a backtrace
for this crash? Since it seems to be KMail crashing, you should get a DrKonqi
notification about the crash, which contains the backtrace in the second tab (I
think it reads "Entwicklerinformationen").

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

[kleopatra] [Bug 369348] New: creating a personal OpenPGP key pair results in a general error

[Gert Rijckmans via KDE Bugzilla]

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

Bug ID: 369348
   Summary: creating a personal OpenPGP key pair results in a
general error
   Product: kleopatra
   Version: 2.2.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: gert.rijckm...@telenet.be
CC: kdepim-b...@kde.org, m...@kde.org

The certificate creation Wizard results in the message: Could not create
certificate: General error
I've tried filling out different certificate details and passphrases but to no
avail.


Reproducible: Always

Steps to Reproduce:
1. Choose File -> New Certificate... in the main menu
2. Choose Create a personal OpenPGP key pair
3. Fill out the details
4. Fill out the passphrase and re-enter it
5. Type some random characters while the key is being created ...

Actual Results:  
Key pair creation failed: 'Could not create certificate: General error' are the
error details

Expected Results:  
a personal openPGP key pair

Kleopatra version 2.2.0-gitfb4ae3(2015-11-12)
MS Windows 10 Home

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

[plasmashell] [Bug 358578] Active window taskbar entry background too bright in Breeze Dark theme

[Jens Reuterberg via KDE Bugzilla]

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

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #7 from Jens Reuterberg  ---
I can't reproduce this now as in Breeze Dark the window decorations are both
dark.

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

[kmail2] [Bug 290363] Moved folders disappear

[Rigo Wenning via KDE Bugzilla]

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

--- Comment #10 from Rigo Wenning  ---
True/Not true :) It won't install without explicit act, because this changes
vendor to obs://build.opensuse.org/KDE instead of the main repositories. I had
that already and it went wrong. So I wait until they have tested this out and
include in the main repos. And In November 42.2 will come with the new KDEPIM
in the main repositories and I will be able to try. My only point is that
closing those bugs is premature. I know that there was a lot of coding with
regard to I/O and email transfer in the meantime. But it hasn't been tested yet
by those who raised the issue

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

[kmail2] [Bug 322708] kmail should allow encrypting mails with keys of unknown/zero trust

[kolAflash via KDE Bugzilla]

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

--- Comment #6 from kolAflash  ---
For PGP/MIME I can't reproduce this anymore. (can anyone?)

But for PGP/Inline this still seems to be valid, as explained here:

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

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

[valgrind] [Bug 369359] msghdr_foreachfield can crash when handling bad iovec

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101287
  --> https://bugs.kde.org/attachment.cgi?id=101287=edit
Fix crash in msghdr_foreachfield when iov_len isn't safe to dereference.

Also stop checking when max length of bytes have been reached.

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

[korganizer] [Bug 210554] Wrong time zone in "Time and Date" configure dialog and appointments

[Allen Winter via KDE Bugzilla]

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

Allen Winter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX
 CC||win...@kde.org

--- Comment #5 from Allen Winter  ---
not applicable to modern versions

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

[kmail2] [Bug 340602] KMail puts PGP/MIME signed attachments twice into the same mail (doubling mailsize)

[Allen Winter via KDE Bugzilla]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
   Version Fixed In||5.1.3
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[korganizer] [Bug 332725] reminder shows all recurring reminders even though only one shall trigger

[Wulf via KDE Bugzilla]

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

--- Comment #8 from Wulf  ---
Hi Denis, thanks for your reply.

I have no idea too, it's your decision.

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

[krita] [Bug 369368] save operation freeze and locks the application

[via KDE Bugzilla]

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

--- Comment #1 from katearche...@yandex.ru ---
maybe it is somehow related to this bug:
https://bugs.kde.org/show_bug.cgi?id=369014

At least the description sounds very similar besides the fact in my case it
doesn't matter which format do you save to.

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

[kdepimlibs] [Bug 307144] LDAP credentials saved wrongly if password cotains a colon

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de

--- Comment #6 from Denis Kurz  ---
Marc, there hasn't been any activity on this bug for almost three years, so it
seems that not too many users have this problem. However, I will at least ask a
colleague if he's able to test it, to be extra sure.

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[via KDE Bugzilla]

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

--- Comment #1 from relativistic.police...@gmail.com ---
More information I forgot to include: This doesn't occur when I use the latest
2.9 build, nor does it occur on 3.0.1 on OS X.

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

[kmail2] [Bug 290363] Moved folders disappear

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #11 from Wolfgang Bauer  ---
(In reply to Rigo Wenning from comment #10)
> True/Not true :) It won't install without explicit act, because this changes
> vendor to obs://build.opensuse.org/KDE instead of the main repositories.

No, it doesn't.
KDEPIM 15.12.3 is part of the main repos.

But it is true that it won't be installed automatically (as I wrote), and that
won't change in Leap 42.2 either.

We still let the user decide whether they want to switch to the latest KF5
version or rather stay on 4.14.10, for certain reasons.

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

[kmail2] [Bug 310914] kmail does not detect new folders of IMAP account/mismatch between "Local Abonnements" and "Serverside Subscriptions"

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #8 from Thomas Pfeiffer  ---
I can confirm this bug with 16.08.
Only restarting Akonadi shows a new folder in KMail.

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

[kdenlive] [Bug 368908] Crash when trying to play a transition

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Jean-Baptiste Mardelle  ---
Should be fixed in latest update of frei0r from our PPA

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

[valgrind] [Bug 369360] Bad sigprocmask old or new sets can crash valgrind

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101288
  --> https://bugs.kde.org/attachment.cgi?id=101288=edit
Fix crash when old/new sigprocmask isn't safe to dereference

Since we want to use the set and oldset for bookkeeping we also want
to make sure they are addressable otherwise, like the kernel, we EFAULT.
Also use EINVAL instead of EMFILE as failure when sigset size is wrong.

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

[kdev-python] [Bug 369363] Type not inferred when iterating objects with __next__

[Nicolás Alvarez via KDE Bugzilla]

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

--- Comment #1 from Nicolás Alvarez  ---
By the way, as another example for the unit tests:

class Foo:
def __iter__(self):
return Bar()
def __next__(self):
return "blah"

class Bar:
def __next__(self):
return {}

for x in Foo():
pass

Here 'x' should be of type 'dict', not 'str'!

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

[kdev-python] [Bug 369364] New: Calling an instance method through the class deduces arg types wrong

[Nicolás Alvarez via KDE Bugzilla]

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

Bug ID: 369364
   Summary: Calling an instance method through the class deduces
arg types wrong
   Product: kdev-python
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: nicolas.alva...@gmail.com

If an instance method is called 'directly' through the class, like this:
class MyClass:
def method(self, arg1):
pass

obj = MyClass()
MyClass.method(obj, 42)

The argument type is deduced wrong. It thinks the 'obj' argument matches with
the 'arg1' parameter, but it should be matched with 'self'. This means it
deduces 'arg1' to be of type 'MyClass', when it should be 'int'.

A notable common case where this causes problems is when a constructor calls
the constructor of the base class:

class Base:
def __init__(self, foo):
self.foo = foo

class Derived(Base):
def __init__(self, foo):
Base.__init__(self, foo)
# ...more Derived-specific initialization...

Now it thinks Base.__init__'s 'foo' argument is of type 'Derived', which also
affects the type of the 'foo' attribute of the object, which cascades into
breaking types in many other places :(

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

[korganizer] [Bug 369365] New: Time bar displays invalid times when using multiple timezones

[Boian Berberov via KDE Bugzilla]

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

Bug ID: 369365
   Summary: Time bar displays invalid times when using multiple
timezones
   Product: korganizer
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: korganizer-de...@kde.org
  Reporter: bberberov+...@gmail.com

I use multiple timezones and I noticed that the time bar renders the times
incorrectly.  It does not roll over times when crossing the AM/PM divide.

Reproducible: Always

Steps to Reproduce:
1.  Add multiple timezones to the time bar with high offsets


Actual Results:  
Invalid times like 19pm appear in time bar.

Expected Results:  
Time bar displays correct times.

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

[kdev-python] [Bug 369369] New: Methods get wrong arguments marked as optional in tooltip

[Nicolás Alvarez via KDE Bugzilla]

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

Bug ID: 369369
   Summary: Methods get wrong arguments marked as optional in
tooltip
   Product: kdev-python
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Code completion
  Assignee: m...@svenbrauch.de
  Reporter: nicolas.alva...@gmail.com

If a function has optional arguments (arguments with default values), the
tooltip that appears when typing the arguments in a call shows square brackets
around the optional arguments:

def func1(arg1, arg2, arg3=None, arg4=42, arg5='default'):
pass

func1( # argument tooltip says void func1 (arg1, arg2, [arg3, arg4, arg5])

However, an instance method with optional arguments shows the square brackets
in the wrong set of arguments:

class C:
def func1(self, arg1, arg2, arg3=None, arg4=42, arg5='default'):
pass

c = C()
c.func1( # argument tooltip says void func1 (arg1, arg2, arg3, [arg4, arg5])

It appears as if arg3 was not optional, but it is.

This is probably because it's not compensating for the presence of the implicit
'self' parameter.

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

[kmail2] [Bug 336205] kmail2 crashes after startup and all windows was opened

[Ulf Bartholomäus via KDE Bugzilla]

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

--- Comment #7 from Ulf Bartholomäus  ---
Created attachment 101285
  --> https://bugs.kde.org/attachment.cgi?id=101285=edit
Screenshot from GUI error message

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

[Breeze] [Bug 369302] ktorrent has three different icons

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-framework/95f01093acc981
   ||7cd5bbc0b4bcdd09376b8b6b14

--- Comment #2 from andreas  ---
Git commit 95f01093acc9817cd5bbc0b4bcdd09376b8b6b14 by andreas kainz.
Committed on 25/09/2016 at 21:00.
Pushed by andreask into branch 'master'.

update ktorrent icon

M  +---src/desktoptheme/breeze/icons/ktorrent.svgz

http://commits.kde.org/plasma-framework/95f01093acc9817cd5bbc0b4bcdd09376b8b6b14

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

[kmail2] [Bug 304525] Auto-suggesting contacts from address book using nicknames fails for first search

[Marcus Harrison via KDE Bugzilla]

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

--- Comment #2 from Marcus Harrison  ---
I have just tested this in KMail 4.14.10 from Fedora RPM packages.
Auto-completion still appears to only search the "Name" and "E-mail" fields
recorded in KAddressBook, and not the "Nickname" field.

I'll investigate building or otherwise installing a Frameworks-based version of
KMail.

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

[kmail2] [Bug 369357] New: KMail refuses to use a technically untrusted S/MIME certificate/key (sender and receiver)

[kolAflash via KDE Bugzilla]

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

Bug ID: 369357
   Summary: KMail refuses to use a technically untrusted S/MIME
certificate/key (sender and receiver)
   Product: kmail2
   Version: 5.1.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

There's no way to use a X.509 certificate/key for S/MIME from a CA which
technically isn't trusted. Neither if it's your certificate (for sending /
signing the mail) nor if it's the receivers certificate (for encrypting the
mail.

Maybe you don't want to trust a whole CA. But you may know that a certain
certificate is trustworthy (e.g. by comparing the fingerprint or because you
created the private key and anyone else has a copy).
Sadly there's no way to technically mark a single X.509 / S/MIME certificate
trustworthy. That's only possible for CAs.
(maybe there should be such a possibility for single X.509 certificates -
something to think about for Kleopatra - but as far as I know that's not the
way X.509 works)
(yes I know, I should use PGP for that trust model, but my contacts sadly don't
share that view and I don't want to trust their whole stupid CA - nevertheless
I need to encrypt my emails to them)


If sending an email, using an technically untrusted certificate for yourself,
KMail will just say (a situation that may also occur if someone else needs you
to use a certificate from a CA you don't like): "Could not compose message: Not
trusted"
No further explanation what's not trusted.
Instead there should be a warning, that you own key isn't trusted. And there
should also be the possibility to say "send anyway". Because, as said, you know
that you can trust a single key (but you can't technically set that mark to a
single X.509 key), but you don't want to trust the whole CA.


Similar thing the other way around:
Send a message to a receiver who's key technically isn't trusted. KMail will
give you a short warning, saying:
|  One or more of the OpenPGP encryption keys or S/MIME
|  certificates for recipient "recipi...@example.com" is not
|  fully trusted for encryption.
You can click "Cancel" or "Continue" and you can also select "Do not ask
again".
But also if you choose "Continue" KMail will refuse to send the mail, telling
you: "Could not compose message: Not trusted"

Reproducible: Always

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

[kdenlive] [Bug 369295] Error exporting when use Key Spill Mop Up filter

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Jean-Baptiste Mardelle  ---
Fixed in latest update of frei0r from our PPA

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

[valgrind] [Bug 369360] New: Bad sigprocmask old or new sets can crash valgrind

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369360
   Summary: Bad sigprocmask old or new sets can crash valgrind
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/rt_sigprocmask/rt_sigprocmask02 crashes valgrind:

==29826== Syscall param rt_sigprocmask(oldset) points to unaddressable byte(s)
==29826==at 0x4F25BF9: syscall (syscall.S:38)
==29826==by 0x402712: main (rt_sigprocmask02.c:107)
==29826==  Address 0x is not stack'd, malloc'd or (recently)
free'd
==29826== 
--29826-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--29826-- si_code=1;  Faulting address: 0x;  sp: 0x80327ad40

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==29826==at 0x380534BD: do_setmask (m_signals.c:1352)
==29826==by 0x380534BD: vgPlain_do_sys_sigprocmask (m_signals.c:1375)
==29826==by 0x380AF5F1: vgSysWrap_linux_sys_rt_sigprocmask_before
(syswrap-linux.c:3414)
==29826==by 0x38092CDF: vgPlain_client_syscall (syswrap-main.c:1906)
==29826==by 0x3808F8B2: handle_syscall (scheduler.c:1118)
==29826==by 0x38090E76: vgPlain_scheduler (scheduler.c:1435)
==29826==by 0x380A027A: thread_wrapper (syswrap-linux.c:103)
==29826==by 0x380A027A: run_a_thread_NORETURN (syswrap-linux.c:156)


Reproducible: Always

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

[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate

[kolAflash via KDE Bugzilla]

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

--- Comment #3 from kolAflash  ---
Another attempt to get this fixed.
https://bugs.gnupg.org/gnupg/issue2703

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

[kmail2] [Bug 276448] moved mails disappear after some time

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED
Version|2.1.0   |5.2.3

--- Comment #12 from Denis Kurz  ---
Thanks for reporting back, reopening.

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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[via KDE Bugzilla]

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

--- Comment #54 from contremait...@gmail.com ---
This bug is still in kmail 5.1.3, KDE framework 5.24.0 :(
Any plan to fix it ?

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

[plasma-nm] [Bug 369351] New: Connection editor crashes when trying to start it

[via KDE Bugzilla]

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

Bug ID: 369351
   Summary: Connection editor crashes when trying to start it
   Product: plasma-nm
   Version: 0.9.3.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: christoph.sen...@googlemail.com
CC: jgrul...@redhat.com

Application: kde-nm-connection-editor (0.9.3.4)
KDE Platform Version: 4.14.18
Qt Version: 4.8.7
Operating System: Linux 4.4.19 x86_64

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

I cannot start the connection editor. When getting to the connection list, I
select a connection and try to edit it, then the crash manager appears.

I am using NixOS.

The crash can be reproduced every time.

-- Backtrace:
Application: Verbindungs-Editor (kde-nm-connection-editor), signal:
Segmentation fault
Using host libthread_db library
"/nix/store/gwl3ppqj4i730nhd4f50ncl5jc4n97ks-glibc-2.23/lib/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path
/nix/store/c7ipds48nb7sfzhb7vqp26rrllirxwxv-gcc-5.3.0/lib/libstdc++.so.6.0.21-gdb.py
line to your configuration file "/home/christoph/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/christoph/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[KCrash Handler]
#6  0x7f0270fcd09b in ConnectionDetailEditor::gotSecrets(QString const&,
bool, QMap > const&, QString const&) () from
/nix/store/6v7fwxzg8lb0y8wxqyzw9d2dqmqvgwkf-plasma-nm-0.9.3.4/lib/libplasmanetworkmanagement-editor.so
#7  0x7f02703b6ff0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#8  0x7f0270c33ccd in NetworkManager::Connection::gotSecrets(QString
const&, bool, QMap > const&, QString const&)
() from
/nix/store/jlsl8m1wh89idjlyvy6frscp9xfknbiz-libnm-qt-0.9.8.2/lib/libNetworkManagerQt.so.1
#9  0x7f0270c36fc6 in
NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () from
/nix/store/jlsl8m1wh89idjlyvy6frscp9xfknbiz-libnm-qt-0.9.8.2/lib/libNetworkManagerQt.so.1
#10 0x7f02703b6ff0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#11 0x7f02709b700f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtDBus.so.4
#12 0x7f02703bcae1 in QObject::event(QEvent*) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#13 0x7f026e402c7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtGui.so.4
#14 0x7f026e40974c in QApplication::notify(QObject*, QEvent*) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtGui.so.4
#15 0x7f026f1270fa in KApplication::notify(QObject*, QEvent*) () from
/nix/store/931gl9inkhpb5wnp9hd1918fi1mm52im-kdelibs-4.14.18/lib/libkdeui.so.5
#16 0x7f02703a3dcd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#17 0x7f02703a702e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#18 0x7f02703d20b3 in ?? () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#19 0x7f026bafd8b7 in g_main_context_dispatch () from
/nix/store/gc2ydi1vpigsl9x2xk8vp30l65x0j4qg-glib-2.46.2/lib/libglib-2.0.so.0
#20 0x7f026bafdae8 in g_main_context_iterate.isra () from
/nix/store/gc2ydi1vpigsl9x2xk8vp30l65x0j4qg-glib-2.46.2/lib/libglib-2.0.so.0
#21 0x7f026bafdb8c in g_main_context_iteration () from
/nix/store/gc2ydi1vpigsl9x2xk8vp30l65x0j4qg-glib-2.46.2/lib/libglib-2.0.so.0
#22 0x7f02703d2204 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#23 0x7f026e4a58e6 in ?? () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtGui.so.4
#24 0x7f02703a2791 in
QEventLoop::processEvents(QFlags) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#25 0x7f02703a2aa5 in
QEventLoop::exec(QFlags) () from
/nix/store/vy506rrvd4w7ddas1j06wnpqpq04rfps-qt-4.8.7/lib/libQtCore.so.4
#26 0x7f02703a8089 in QCoreApplication::exec() () from

[bugs.kde.org] [Bug 369339] Missing versions for kaddressbook

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[kdialog] [Bug 369216] kdialog path parsing regression

[Paul via KDE Bugzilla]

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

--- Comment #4 from Paul  ---
My best guess now is it's in KIO's KFileWidget::setSelection
- d->setLocationText(QUrl(url));
+d->setLocationText(urlFromString(url));
since the second last edit to kfilewidget.cpp made that change in another
function and it has the affect of prepending file:// to absolute paths on
Linux.

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

[ktorrent] [Bug 369352] New: ktorrent crash while close the app

[Alexander Miroshnichenko via KDE Bugzilla]

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

Bug ID: 369352
   Summary: ktorrent crash while close the app
   Product: ktorrent
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: alexmin...@gmail.com

Application: ktorrent (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.8-hardened-r1 x86_64
Distribution: "Gentoo Base System release 2.2"

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

ktorrent crash while normal close the app from menu File/Exit

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x317716a7880 (LWP 4996))]

Thread 5 (Thread 0x3176e5a8700 (LWP 5008)):
#0  0x03178094e75d in poll () from /lib64/libc.so.6
#1  0x03177a88e815 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x31760003020, timeout=-1, context=0x3176990) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x3176990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3835
#3  0x03177a88e981 in g_main_context_iteration (context=0x3176990,
may_block=1) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3901
#4  0x03178173bad4 in QEventDispatcherGlib::processEvents
(this=0x31768c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0x0317816dfd5a in QEventLoop::exec (this=this@entry=0x3176e5a7ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x0317814ff53d in QThread::exec (this=this@entry=0x31785fc12c0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7  0x031785f48565 in QDBusConnectionManager::run (this=0x31785fc12c0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8  0x031781504db2 in QThreadPrivate::start (arg=0x31785fc12c0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#9  0x03177cce660c in start_thread () from /lib64/libpthread.so.0
#10 0x03178095855d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x3176d479700 (LWP 5010)):
#0  0x031786068b61 in ?? ()
#1  0x03176d478a00 in ?? ()
#2  0x000130d63498 in ?? ()
#3  0x0001 in ?? ()
#4  0x03176d478a00 in ?? ()
#5  0x03176d478aa0 in ?? ()
#6  0x03176d4789f0 in ?? ()
#7  0x031780965d1a in clock_gettime () from /lib64/libc.so.6
Backtrace stopped: frame did not save the PC

Thread 3 (Thread 0x3174efe6700 (LWP 5030)):
#0  0x03177ccec57f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x03175799eca3 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x03175799e29a in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x03177cce660c in start_thread () from /lib64/libpthread.so.0
#4  0x03178095855d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x317318dd700 (LWP 5061)):
#0  0x03177ccec57f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x031781505573 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x8319701f0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x831ae99f8,
mutex=mutex@entry=0x831ae99f0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x03178581f25d in net::ReverseResolverThread::run (this=0x831ae99e0) at
/usr/src/debug/net-libs/libktorrent-2.0.1/libktorrent-2.0.1/src/net/reverseresolver.cpp:124
#4  0x031781504db2 in QThreadPrivate::start (arg=0x831ae99e0) at
thread/qthread_unix.cpp:341
#5  0x03177cce660c in start_thread () from /lib64/libpthread.so.0
#6  0x03178095855d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x317716a7880 (LWP 4996)):
[KCrash Handler]
#6  0x0317808973cb in raise () from /lib64/libc.so.6
#7  0x031780898a31 in abort () from /lib64/libc.so.6
#8  0x0317808da91d in __libc_message () from /lib64/libc.so.6
#9  0x0317808e0c0f in malloc_printerr () from /lib64/libc.so.6
#10 0x0317808e147e in _int_free () from /lib64/libc.so.6
#11 0x03178172fbb2 in QTypedArrayData::deallocate
(data=) at ../../src/corelib/tools/qarraydata.h:222
#12 QString::~QString (this=0x397ae3602f0, __in_chrg=) at
../../src/corelib/tools/qstring.h:1065
#13 v_clear (d=0x397ae3602f0) at
../../src/corelib/kernel/qvariant_p.h:169
#14 QVariantDestructor<(anonymous
namespace)::CoreTypesFilter>::FilteredDestructor::FilteredDestructor (this=, d=0x397ae3602f0) at
../../src/corelib/kernel/qvariant_p.h:413
#15 

[kmail2] [Bug 332167] KMail is failing to encrypt PGP/Inline for non-signed key

[kolAflash via KDE Bugzilla]

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

--- Comment #6 from kolAflash  ---
Still existing in Kontact 5.1.3 (KDE Frameworks 5.21.0 on openSUSE 42.1)

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

[kdenlive] [Bug 369296] crash rendering in .mp4 on video with "levels" colour correction effect

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Jean-Baptiste Mardelle  ---
Fixed in latest update of frei0r from our PPA

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

[valgrind] [Bug 369359] New: msghdr_foreachfield can crash when handling bad iovec

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369359
   Summary: msghdr_foreachfield can crash when handling bad iovec
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/recvmsg/recvmsg01 crashes valgrind:

==29561== Syscall param recvmsg(msg.msg_iov[134]) points to unaddressable
byte(s)
==29561==at 0x4F2C690: __recvmsg_nocancel (syscall-template.S:81)
==29561==by 0x402B0E: main (recvmsg01.c:224)
==29561==  Address 0x6b636f7364750001 is not stack'd, malloc'd or (recently)
free'd
==29561== 
--29561-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--29561-- si_code=1;  Faulting address: 0x618008;  sp: 0x80327ad40

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==29561==at 0x38093BD5: msghdr_foreachfield (syswrap-generic.c:1063)
==29561==by 0x38092CDF: vgPlain_client_syscall (syswrap-main.c:1906)
==29561==by 0x3808F8B2: handle_syscall (scheduler.c:1118)
==29561==by 0x38090E76: vgPlain_scheduler (scheduler.c:1435)
==29561==by 0x380A027A: thread_wrapper (syswrap-linux.c:103)
==29561==by 0x380A027A: run_a_thread_NORETURN (syswrap-linux.c:156)


Reproducible: Always

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

[kmail2] [Bug 339087] you cannot encrypt to an expired OpenPGP certificate

[kolAflash via KDE Bugzilla]

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

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

--- Comment #2 from kolAflash  ---
Still valid for KMail 5.1.3 (KDE Frameworks 5.21.0 on openSUSE 42.1)

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

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

[kmail2] [Bug 369358] New: you cannot encrypt to an expired S/MIME certificate

[kolAflash via KDE Bugzilla]

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

Bug ID: 369358
   Summary: you cannot encrypt to an expired S/MIME certificate
   Product: kmail2
   Version: 5.1.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: kolafl...@kolahilft.de

Same as https://bugs.kde.org/show_bug.cgi?id=339087 which is for PGP, but this
time for S/MIME.

KMail does not allow to encrypt to expired certificates. It is OK to warn about
that (and would be a failure not to do so) but not allowing to encrypt to this
key is a severe security failure because it does not make any sense and forces
the user to use a different key (if available, usually not) or to send the mail
unencrypted.

Reproducible: Always


Actual Results:  
Mail can't be sent.

Expected Results:  
Warning which can be overridden.

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

[korganizer] [Bug 294595] event recurrent move one of them to another day doesn't work

[a . glazachev via KDE Bugzilla]

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

--- Comment #5 from a.glazachev  ---
Kmail 5.1.3, KDE Frameworks 5.18.0, Qt 5.5.1, xcb.

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

[ksysguard] [Bug 369366] New: Add Nextcloud monitoring support to KSysguard

[court via KDE Bugzilla]

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

Bug ID: 369366
   Summary: Add Nextcloud monitoring support to KSysguard
   Product: ksysguard
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: courthic...@gmail.com

Nextcloud provides any API that allows you to monitor your system resources
remotely. I think since KSysguard can remotely monitor systems, it would be
really neat to see this functionality added.

Reproducible: Always

Steps to Reproduce:
1. Create a new tab in KSysguard
2. Enter URL & credentials to monitor Nextcloud server that is desired to be
monitored
3. Connect and select different parts of system to be monitored


Expected Results:  
Be able to open KSysguard and view remote Nextcloud server information

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[John O'Shaughnessy via KDE Bugzilla]

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

John O'Shaughnessy  changed:

   What|Removed |Added

 CC||johnosha...@gmail.com

--- Comment #14 from John O'Shaughnessy  ---
i'm on openSUSE Tumbleweed with KDE/Plasma 5.7.4. kernel 4.7.4-2 and still got
the same problem
with all the klauncher.slave-socket files piling up in the root directory

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

[kmail2] [Bug 332614] Can't copy/paste tables from libreoffice calc after libreoffice update

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME
 CC||kde...@posteo.de

--- Comment #17 from Denis Kurz  ---
Gunter, Yuriy: Ok, there still seems to be *some* problem here, but it's not
the original bug. Since mixing multiple up bugs in one report makes it harder
to work on the bug, I close this one. Please consider filing your suggestions
("should be attached as HTML" and the like) as a fresh, new feature request.
Thanks a lot for your feedback.

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

[konsole] [Bug 368005] konsole clears all the screen when I execute clear command even if the scrollbar is infinite.

[Egmont Koblinger via KDE Bugzilla]

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

--- Comment #2 from Egmont Koblinger  ---
See also:
https://gitlab.com/gnachman/iterm2/issues/5058
https://bugzilla.gnome.org/show_bug.cgi?id=771953

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

[korganizer] [Bug 64603] Multiple overlapping events in agenda view are layed out wrong (overlapping, too wide, different widths, etc.)

[Richard Bos via KDE Bugzilla]

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

--- Comment #13 from Richard Bos  ---
Denis you're my hero.  
Thanks for looking into the KDE bug situation and for verying this problem.

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

[bugs.kde.org] [Bug 369339] Missing versions for kaddressbook

[Christophe Giboudeaux via KDE Bugzilla]

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

--- Comment #1 from Christophe Giboudeaux  ---
I won't be adding the 'KDE Applications...' part. This is troublesome when
using the drkonqi reporting tool (help/report bug)

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

[bugs.kde.org] [Bug 369342] Duplicate versions 16.08 and 5.3.0 for Akonadi

[Christophe Giboudeaux via KDE Bugzilla]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christophe Giboudeaux  ---
now that the two bugs that prevented it were moved, this version is now deleted

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

[valgrind] [Bug 369362] New: Bad sigaction arguments crash valgrind

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369362
   Summary: Bad sigaction arguments crash valgrind
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/rt_sigaction/rt_sigaction02 crashes valgrind:

--29814-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exi
ting
--29814-- si_code=1;  Faulting address: 0xA;  sp: 0x80327ad70

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==29814==at 0x380AF328: vgSysWrap_linux_sys_rt_sigaction_before
(syswrap-lin
ux.c:3376)
==29814==by 0x38092CDF: vgPlain_client_syscall (syswrap-main.c:1906)
==29814==by 0x3808F8B2: handle_syscall (scheduler.c:1118)
==29814==by 0x38090E76: vgPlain_scheduler (scheduler.c:1435)
==29814==by 0x380A027A: thread_wrapper (syswrap-linux.c:103)
==29814==by 0x380A027A: run_a_thread_NORETURN (syswrap-linux.c:156)


Reproducible: Always

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

[kdev-python] [Bug 309817] Wrong scope in the list of superclasses

[Nicolás Alvarez via KDE Bugzilla]

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

--- Comment #5 from Nicolás Alvarez  ---
(In reply to Sven Brauch from comment #4)
> Note: This corner-case is still broken (discivered by Nicolas):
> [...]
> To be fixed for 1.5.

I confirm this is still broken in 5.0.1...

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

[krfb] [Bug 356782] krfb stops sending updates after the first frame

[Michael Palimaka via KDE Bugzilla]

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

Michael Palimaka  changed:

   What|Removed |Added

 CC||kensing...@gentoo.org

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

[kleopatra] [Bug 369348] creating a personal OpenPGP key pair results in a general error

[Andre Heinecke via KDE Bugzilla]

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

--- Comment #1 from Andre Heinecke  ---
Mh, this is of course part of our general testing pattern. So it works,
usually.

Is there anything special about your username and E-Mail address (like special
characters). Did you change anything in the Advanced Options subdialog?

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

[Akonadi] [Bug 281797] kmail2/akonadi handels maildir incorrect

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||mikael.sal...@gmail.com

--- Comment #14 from Denis Kurz  ---
*** Bug 303913 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 303913] maildir 'new' directories aren't empty

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de
 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Denis Kurz  ---
Thomas, thanks for pointing this out. I think you are right

*** This bug has been marked as a duplicate of bug 281797 ***

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

[ksmserver] [Bug 369350] New: Some applications (choqok) fail to autostart in 5.8 beta

[Antonio Rojas via KDE Bugzilla]

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

Bug ID: 369350
   Summary: Some applications (choqok) fail to autostart in 5.8
beta
   Product: ksmserver
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: aro...@archlinux.org

After upgrading to Plasma 5.8 beta, some applications fail to autostart: in my
case it's choqok. Other applications seem to autostart fine. Downgrading to 5.7
(while keeping the same version of all other packages) makes it work again, so
this is definitely caused by the Plasma upgrade.

Related logs:

> journalctl -b /usr/bin/ksmserver
-- Logs begin at mar 2016-07-19 11:16:49 CEST, end at dom 2016-09-25 21:32:46
CEST. --
sep 25 21:27:47 arl-portatil ksmserver[704]: Qt: Session management error:
networkIdsList argument is NULL
sep 25 21:27:47 arl-portatil ksmserver[704]: Configuring Lock Action
sep 25 21:27:47 arl-portatil ksmserver[704]: XSync seems available and ready
sep 25 21:27:47 arl-portatil ksmserver[704]: XSync Inited
sep 25 21:27:47 arl-portatil ksmserver[704]: Supported, init completed
sep 25 21:27:47 arl-portatil ksmserver[704]: Created alarm 20971521
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver:
"/run/user/1000/KSMserver"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: KSMServer:
SetAProc_loc: conn  0 , prot= local , file= @/tmp/.ICE-unix/704
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: KSMServer:
SetAProc_loc: conn  1 , prot= unix , file= /tmp/.ICE-unix/704
sep 25 21:27:47 arl-portatil ksmserver[704]: QDBusConnection: name
'org.kde.kglobalaccel' had owner '' but we thought it was ':1.14'
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/baloo_file.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/kdeconnectd.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/krunner.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/pam_kwallet_init.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/plasmashell.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/xembedsniproxy.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Autostart 0 done
sep 25 21:27:47 arl-portatil ksmserver[704]: kcminit not running? If we are
running with mobile profile or in another platform other than X11 this is norm
sep 25 21:27:47 arl-portatil ksmserver[704]: detected kglobalaccel restarting,
re-registering all shortcut keys
sep 25 21:27:47 arl-portatil ksmserver[704]: Session path:
"/org/freedesktop/login1/session/c2"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Kcminit phase 1 done
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: autostart service
"/usr/lib/pam_kwallet_init" finished with exit code  0
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/pulseaudio.desktop"
sep 25 21:27:47 arl-portatil ksmserver[704]: ksmserver: Autostart 1 done
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting notification
thread
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/home/antonio/.config/autostart/choqok.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/home/antonio/.config/autostart/dropbox.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/home/antonio/.config/autostart/ownCloud.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/home/antonio/.config/autostart/yakuake.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/org.kde.korgac.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/powerdevil.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Starting autostart
service  "/etc/xdg/autostart/kup-daemon.desktop"
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Autostart 2 done
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: Kcminit phase 2 done
sep 25 21:27:48 arl-portatil ksmserver[704]: ksmserver: autostart service
"start-pulseaudio-x11" finished with exit code  0
sep 25 21:27:49 arl-portatil ksmserver[704]: ksmserver: autostart service
"choqok" finished with exit code  254
sep 25 21:27:49 arl-portatil ksmserver[704]: 

[korganizer] [Bug 158921] recurring entries on Feb 29. missing in non leap years

[Richard Bos via KDE Bugzilla]

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

--- Comment #5 from Richard Bos  ---
Denis you're my hero.  
Thanks for looking into the KDE bug situation and for verying this problem.

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

[valgrind] [Bug 369356] New: pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369356
   Summary: pre_mem_read_sockaddr syscall wrapper can crash with
bad sockaddr
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/bind/bind01 crashes valgrind:

==19407==at 0x4F2C427: bind (syscall-template.S:81)
==19407==by 0x402803: main (bind01.c:120)
==19407==  Address 0x is not stack'd, malloc'd or (recently)
free'd
==19407== 
--19407-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--19407-- si_code=1;  Faulting address: 0x;  sp: 0x802ea9d70

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==19407==at 0x38094231: pre_mem_read_sockaddr.part.12
(syswrap-generic.c:1131)
==19407==by 0x38092CDF: vgPlain_client_syscall (syswrap-main.c:1906)
==19407==by 0x3808F8B2: handle_syscall (scheduler.c:1118)
==19407==by 0x38090E76: vgPlain_scheduler (scheduler.c:1435)
==19407==by 0x380A027A: thread_wrapper (syswrap-linux.c:103)
==19407==by 0x380A027A: run_a_thread_NORETURN (syswrap-linux.c:156)


Reproducible: Always

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

[kaddressbook] [Bug 223236] kmail cannot connect to LDAP over SSL

[Jose Arthur Benetasso Villanova via KDE Bugzilla]

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

--- Comment #11 from Jose Arthur Benetasso Villanova  ---
I dont use kmail anymore, but I remember that I could solve this problem with a
dot file.
 I think that it was .ldaprc with "TLS_REQCERT never" inside it.

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

[korganizer] [Bug 369365] Time bar displays invalid times when using multiple timezones

[Boian Berberov via KDE Bugzilla]

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

--- Comment #1 from Boian Berberov  ---
Created attachment 101291
  --> https://bugs.kde.org/attachment.cgi?id=101291=edit
Screenshot of issue

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #46 from Leslie Zhai  ---
Git commit cbe652000292dc5a6c9e36de0d1000ca0d84f75d by Leslie Zhai.
Committed on 26/09/2016 at 02:08.
Pushed by lesliezhai into branch 'multisession'.

Update multisession implementation as Thomas suggested

Summary:
- Fix getNextWritableAdress issue with counterpart for the bdr_plus_pow
case
- Remove duplicated nextSessionStart

M  +0-2libk3b/projects/datacd/k3bdatajob.cpp
M  +0-32   libk3b/projects/datacd/k3bdatamultisessionparameterjob.cpp
M  +4-1libk3bdevice/k3bdevice.cpp

http://commits.kde.org/k3b/cbe652000292dc5a6c9e36de0d1000ca0d84f75d

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

[kdev-python] [Bug 369367] Caught exceptions get wrong scope (py3 change)

[Nicolás Alvarez via KDE Bugzilla]

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

Nicolás Alvarez  changed:

   What|Removed |Added

   Priority|NOR |LO

--- Comment #1 from Nicolás Alvarez  ---
Ugh, this is trickier than I thought because it's not really a "scope". Python
pretty much runs 'del exc' after the except block.

exc = "hello world"
try:
a=1/0
except Exception as exc:
print(exc)
print(exc)

The second print statement will raise a NameError, it will neither print the
exception nor "hello world". So it's not a matter of using a different setup of
DUContexts to create a scope; you would need support for deleting individual
variables.

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

[Akonadi] [Bug 339910] Akonadi refuses to start after upgrade to 1.12.1-r1 because table akonadi.parttable could not be created

[Beetle B . via KDE Bugzilla]

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

--- Comment #5 from Beetle B.  ---
akonadi version:

akonadi-server-1.13.1_pre20160203-r1

KDE PIM version:

4.14.11_pre20160211

I cannot get it to start:



beetle_b ~/lang/python/emailfilter $ akonadictl start  
   
 :-) 8:27PM [1129]
Starting Akonadi Server... 
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
   done. 
beetle_b ~/lang/python/emailfilter $ search paths:  ("/home/mueen/path",
"/home/mueen/path/bin", "/home/mueen/.local/bin", "/home/mueen/path",
"/home/mueen/path/bin", "/usr/local/bin", "/usr/bin", "/bin", "/opt/bin",
"/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4", "/opt/nvidia-cg-toolkit/bin",
"/usr/games/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec",
"/usr/libexec", "/usr/share/mysql/scripts", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") 
Found mysql_install_db:  "/usr/share/mysql/scripts/mysql_install_db" 
Found mysqlcheck:  "/usr/bin/mysqlcheck" 
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/mueen/.local/share/akonadi/mysql.conf",
"--datadir=/home/mueen/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-mueen.aD6Erw/mysql.socket")
stdout: ""
stderr: "160925 20:31:03 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB)
starting as process 2018 ...
"
exit code: 1
process error: "Process operation timed out"
"[
0: akonadiserver(_Z11akBacktracev+0x4a) [0x4634da]
1: akonadiserver() [0x463754]
2: /lib64/libc.so.6(+0x33030) [0x7f8b480ff030]
3: /lib64/libc.so.6(gsignal+0x37) [0x7f8b480fefb7]
4: /lib64/libc.so.6(abort+0x16a) [0x7f8b4810031a]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64)
[0x7f8b498e2ee4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xad) [0x46555d]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0)
[0x7f8b4997bbf0]
8: /usr/lib64/qt4/libQtCore.so.4(+0x11926d) [0x7f8b4998b26d]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f8b49993e51]
10: akonadiserver(_ZN6QDebugD1Ev+0x49) [0x45e6c9]
11:
akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1ecf)
[0x4d1dff]
12:
akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xff)
[0x46615f]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xb8) [0x468848]
14: akonadiserver() [0x530cf9]
15: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e)
[0x7f8b49a05ace]
16:
/usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d)
[0x7f8b499ed9cd]
17:
/usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed)
[0x7f8b499f0aed]
18: /usr/lib64/qt4/libQtCore.so.4(+0x1a8e4e) [0x7f8b49a1ae4e]
19: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f8b477a7974]
20: /usr/lib64/libglib-2.0.so.0(+0x48bc8) [0x7f8b477a7bc8]
21: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f8b477a7c6c]
22:
/usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e)
[0x7f8b49a1a60e]
23:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)
[0x7f8b499ec58f]
24:
/usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175)
[0x7f8b499ec885]
25: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89)
[0x7f8b499f1b29]
26: akonadiserver(main+0x1ed) [0x45db8d]
27: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8b480ec6a5]
28: akonadiserver(_start+0x29) [0x45e439]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)
search paths:  ("/home/mueen/path", "/home/mueen/path/bin",
"/home/mueen/.local/bin", "/home/mueen/path", "/home/mueen/path/bin",
"/usr/local/bin", "/usr/bin", "/bin", "/opt/bin",
"/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4", "/opt/nvidia-cg-toolkit/bin",
"/usr/games/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec",
"/usr/libexec", "/usr/share/mysql/scripts", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") 
Found mysql_install_db:  "/usr/share/mysql/scripts/mysql_install_db" 
Found mysqlcheck:  "/usr/bin/mysqlcheck" 
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld"
arguments: ("--defaults-file=/home/mueen/.local/share/akonadi/mysql.conf",
"--datadir=/home/mueen/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-mueen.aD6Erw/mysql.socket")
stdout: ""
stderr: "160925 20:31:04 [Note] /usr/sbin/mysqld (mysqld 10.0.25-MariaDB)
starting as process 2035 ...
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x4a) [0x4634da]
1: akonadiserver() [0x463754]
2: /lib64/libc.so.6(+0x33030) [0x7f5e7937d030]
3: 

[konsole] [Bug 369328] Settings -> Edit current profile. Does neither apply the settings to the current shell session nor inform about this

[Achim Bohnet via KDE Bugzilla]

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

--- Comment #4 from Achim Bohnet  ---
Mhmm, it worked now here too, until I've 

* closed all konsole windows
* rm $HOME/.config/konsolerc
* start konsole again

* open edit current profile
* hide scrollbar and scrollback e.g. 3000.  Press okay
-> BUG: nothing happens
* open edit current profile again
->  BUG scrollbar: right and scrollback: 1000

When I close and open konsole again,   scrollbar is hidden and scollback is
3000

>From now on edit current profile works as expected.

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

[kmail2] [Bug 303913] maildir 'new' directories aren't empty

[Thomas Zell via KDE Bugzilla]

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

--- Comment #3 from Thomas Zell  ---
I think this can be closed as a duplicate of Bug 281797

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

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

[Ivo Raisr via KDE Bugzilla]

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

Ivo Raisr  changed:

   What|Removed |Added

  Latest Commit||15985

--- Comment #22 from Ivo Raisr  ---
Follow up fix SVN r15985.

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

[kmail2] [Bug 336205] kmail2 crashes after startup and all windows was opened

[Ulf Bartholomäus via KDE Bugzilla]

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

--- Comment #6 from Ulf Bartholomäus  ---
In the moment there is no second tab. Is there an easy way to install with
zypper all needed developer packages?

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

[korganizer] [Bug 332725] reminder shows all recurring reminders even though only one shall trigger

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de

--- Comment #7 from Denis Kurz  ---
Wulf, thanks for reporting back. There's a whole bunch of reports for broken
reminders, and I should probably try to clean those separately. As of now, I
have no idea whether this bug should remain open... I leave it as is for now,
unless you'd suggest otherwise.

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

[plasmashell] [Bug 369353] New: Swedish layout doesn't make Alt Gr a 3rd level modifier by default

[ywecur via KDE Bugzilla]

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

Bug ID: 369353
   Summary: Swedish layout doesn't make Alt Gr a 3rd level
modifier by default
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: emilio.alvare...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

The Swedish keyboard layout necessitates that the key Alt Gr (Right Alt on
US-keyboards) is used as a 3rd level modifier for several important keys such
as @ and $. Having this not be the default is very confusing for new users and
makes it hard to interact with the OS. 

It is currently possible to change Alt Gr to function as a 3rd level modifier
by modifying Right Alt in the advanced section of Keyboard Hardware and Layout
(Which in itself is confusing since there is no right alt on Swedish keyboards)
so it is probably possible to inplement a solution where this is done by
default quite fast.

Reproducible: Always

Steps to Reproduce:
1. Change the keyboard layout to Swedish
2. Try to use Alt Gr (e.g. try to type @)

Actual Results:  
Alt Gr is recognized as Alt

Expected Results:  
Alt Gr is recognized correctly and as a 3rd level modifier

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

[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101286
  --> https://bugs.kde.org/attachment.cgi?id=101286=edit
Fix pre_mem_read_sockaddr crash on invalid syscall arguments

Don't do any more checks if it isn't safe to inspect the address family.
Likewise, don't check sun_path if the string address isn't safe.

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

[kdev-python] [Bug 369363] New: Type not inferred when iterating objects with __next__

[Nicolás Alvarez via KDE Bugzilla]

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

Bug ID: 369363
   Summary: Type not inferred when iterating objects with __next__
   Product: kdev-python
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: nicolas.alva...@gmail.com

If I have a generator implemented as a function, iterating over it with a for
loop (or list comprehension) correctly deduces the type of the item variable:

def gen1():
yield "blah"

for item1 in gen1():
print(item1)

Here, KDevelop knows item1 is a str, because that is what gen1 yields.

However, if I do the same with a class that has a custom __next__ method, the
type is not deduced:

class Gen2:
def __iter__(self):
return self
def __next__(self):
return "blah"

gen2 = Gen2()
for item2 in gen2:
print(item2)

The tooltip shows item2 as 'mixed', its attributes are not highlighted or
completed, etc.

This affects a few built-in types, such as I/O classes that yield strings
(lines) when iterated. (In many cases the definitions in documentation_files
don't have a __next__ and they should, but the point of this bug is that adding
the missing __next__ makes no difference)

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

[kontact] [Bug 94168] focus-stealing error msg windows can effectively lock up kontact/kmail

[Volker Blum via KDE Bugzilla]

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

--- Comment #8 from Volker Blum  ---
Thank you for following up on this. This was a long time ago. Unfortunately I
no longer have a current version to be able to test this.

Good luck! & Best wishes,
Volker

On Sep 24, 2016, at 3:30 PM, Denis Kurz via KDE Bugzilla
 wrote:

> https://bugs.kde.org/show_bug.cgi?id=94168
> 
> Denis Kurz  changed:
> 
>   What|Removed |Added
> 
> Status|CONFIRMED   |NEEDSINFO
> Resolution|--- |WAITINGFORINFO
> 
> --- Comment #7 from Denis Kurz  ---
> This bug has only been reported for versions before 4.14, which have been
> unsupported for at least two years now. Can anyone tell if this bug still
> present?
> 
> If noone confirms this bug for a Framework-based version of kontact (version
> 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in
> about three months.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 369368] New: save operation freeze and locks the application

[via KDE Bugzilla]

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

Bug ID: 369368
   Summary: save operation freeze and locks the application
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: katearche...@yandex.ru

After switching from 3.0 to 3.0.1 an attempt to save the file results in an
endless waiting for the "save window" to complete an operation(I have alot of
space and 3.0 saved the very same file fine) and if I hit close on that window
I can open various menus and dialogs(including right-button mouse docker with
brushes and colors selector and ability to pan and zoom the picture) but
brushes won't draw at all and the cursor is in a "waiting' state. But worst of
all any click on any save option(save, save as, export) wont do a thing. 

If I try to close Krita after that it crashes and delete an autosave with it. 

I'm using win7 if it is important.

It is really irritating and deal-breaking behaviour so I have to switch back to
3.0 since loosing hours or so of work isn't fun at all.

Reproducible: Sometimes

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

[kmail2] [Bug 312074] kmail can not detect mailing lists in imap folders

[Denis Kurz via KDE Bugzilla]

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

Denis Kurz  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED
Version|unspecified |5.3.1

--- Comment #16 from Denis Kurz  ---
Great, thanks a lot. Reopening

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

[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor

[nmset via KDE Bugzilla]

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

nmset  changed:

   What|Removed |Added

 CC||nm...@netcourrier.com

--- Comment #5 from nmset  ---
Same here :
Version 5.3.0 (QtWebEngine)
KDE Frameworks 5.26.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system
ArchLinux

kmail got unusable.

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

[krita] [Bug 369349] New: Low framerate when drawing with the stabilizer

[via KDE Bugzilla]

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

Bug ID: 369349
   Summary: Low framerate when drawing with the stabilizer
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: relativistic.police...@gmail.com

When drawing with the stabilizer enabled, the actual rendering of the brush
location and the new image seems to be working at a noticeably slower framerate
(maybe 20 FPS).

I'd attach a performance log but I can't find where it's being stored, it's not
in %TEMP%.

Reproducible: Always

Steps to Reproduce:
1. Create a new image 
2. Pick a brush and enable the stabilizer
3. Start drawing

Actual Results:  
The framerate is as smooth as drawing with the stabilizer off.

Expected Results:  
The drawing appears to occur at 20-ish frames a second.

System configuration: i5-4460 CPU, Radeon R9 390, 16 GB RAM. Krita's CPU usage
doesn't go noticeably higher than when it does when I draw with the stabilizer
off, and the memory usage seems reasonable.

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

[systemsettings] [Bug 369355] New: Touchpad configuration applet crashes

[Misandrist via KDE Bugzilla]

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

Bug ID: 369355
   Summary: Touchpad configuration applet crashes
   Product: systemsettings
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: e...@theunixman.com

Application: systemsettings5 (5.8.90)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.0-38-lowlatency x86_64
Distribution: KDE neon User Edition 5.7

-- Information about the crash:
>From the System Settings input devices applet, or from the command line.
Running from Neon development repository on top of Kubuntu Xenial.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbb7947a8c0 (LWP 4832))]

Thread 4 (Thread 0x7fbb64910700 (LWP 4960)):
#0  0x7fbb7fa13ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbb7f9cf391 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbb7f9cf722 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbb64bf9916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fbb7f9f5bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbb818766fa in start_thread (arg=0x7fbb64910700) at
pthread_create.c:333
#6  0x7fbb8466bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fbb66c26700 (LWP 4959)):
#0  0x7fbb8465fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbb7f9cf39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbb7f9cf4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbb7f9cf4e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbb7f9f5bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbb818766fa in start_thread (arg=0x7fbb66c26700) at
pthread_create.c:333
#6  0x7fbb8466bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fbb74f3e700 (LWP 4833)):
#0  0x7fbb8465fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbb7f9cf39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbb7f9cf4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbb84f8a23b in QEventDispatcherGlib::processEvents
(this=0x7fbb78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fbb84f34cea in QEventLoop::exec (this=this@entry=0x7fbb74f3dcd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fbb84d59fb4 in QThread::exec (this=this@entry=0x7fbb880e6d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7fbb880727a5 in QDBusConnectionManager::run (this=0x7fbb880e6d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#7  0x7fbb84d5eb98 in QThreadPrivate::start (arg=0x7fbb880e6d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#8  0x7fbb818766fa in start_thread (arg=0x7fbb74f3e700) at
pthread_create.c:333
#9  0x7fbb8466bb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fbb7947a8c0 (LWP 4832)):
[KCrash Handler]
#6  0x7fbb4726828b in TouchpadConfig::TouchpadConfig (this=0x1d763d0,
parent=, args=...) at
/workspace/build/kcms/touchpad/src/kcm/touchpadconfig.cpp:185
#7  0x7fbb472653bb in KPluginFactory::createInstance (parentWidget=, parent=, args=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:477
#8  0x7fbb851cafdf in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#9  0x7fbb87ac4216 in KCModuleLoader::loadModule(KCModuleInfo const&,
KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#10 0x7fbb87acb6ef in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#11 0x7fbb87acc2e5 in KCModuleProxy::realModule() const () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#12 0x7fbb87acc833 in KCModuleProxy::showEvent(QShowEvent*) () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#13 0x7fbb86462398 in QWidget::event (this=0x220d9b0, event=0x7ffe3a1fab70)
at kernel/qwidget.cpp:9144
#14 0x7fbb8641b89c in QApplicationPrivate::notify_helper (this=, receiver=0x220d9b0, e=0x7ffe3a1fab70) at kernel/qapplication.cpp:3799
#15 0x7fbb86423296 in QApplication::notify (this=0x7ffe3a1fc340,
receiver=0x220d9b0, e=0x7ffe3a1fab70) at 

[digikam] [Bug 369354] New: Wrong translation for german when you search for faces

[Eugen Albiker via KDE Bugzilla]

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

Bug ID: 369354
   Summary: Wrong translation for german when you search for faces
   Product: digikam
   Version: 5.2.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: eu...@eugenalbiker.de

Wrong translations for german


Reproducible: Always

Steps to Reproduce:
1. start digikam 5.2
2. click on left panel "persons"
3. click on "Sammlung nach Gesichter durchsuchen" (engl I think "find faces")

Actual Results:  
A new window pops up with 3 Buttons
- Gesichter erkennen (engl I think: "Find faces")
- Gesichter finden und erkennen (engl. I think "find and recognize faces)
- Gesichter erkennen (engl. I think "recognize faces")

Expected Results:  
The correct translation is:
- Gesichter finden  (new)
- Gesichter finden und erkennen (ok)
- Gesichter erkennen  (ok)

additional: The popup for the first entry it translated to german.
The second and third entry is not translated to german.

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

[valgrind] [Bug 369361] New: vmsplice syscall wrapper crashes on bad iovec

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369361
   Summary: vmsplice syscall wrapper crashes on bad iovec
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/vmsplice/vmsplice02 crashes valgrind:
==32085== Syscall param vmsplice(iov) points to unaddressable byte(s)
==32085==at 0x4F2C173: __vmsplice_nocancel (syscall-template.S:81)
==32085==by 0x4028BC: vmsplice_verify (vmsplice02.c:119)
==32085==by 0x4028BC: main (vmsplice02.c:83)
==32085==  Address 0x615000 is not stack'd, malloc'd or (recently) free'd
==32085== 
==32085== Syscall param vmsplice(iov[...]) points to unaddressable byte(s)
==32085==at 0x4F2C173: __vmsplice_nocancel (syscall-template.S:81)
==32085==by 0x4028BC: vmsplice_verify (vmsplice02.c:119)
==32085==by 0x4028BC: main (vmsplice02.c:83)
==32085==  Address 0x80007 is not stack'd, malloc'd or (recently) free'd
==32085== 
--32085-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--32085-- si_code=1;  Faulting address: 0x615000;  sp: 0x80327ad70

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==32085==at 0x380B71DC: vgSysWrap_linux_sys_vmsplice_before
(syswrap-linux.c:5301)
==32085==by 0x38092CDF: vgPlain_client_syscall (syswrap-main.c:1906)
==32085==by 0x3808F8B2: handle_syscall (scheduler.c:1118)
==32085==by 0x38090E76: vgPlain_scheduler (scheduler.c:1435)
==32085==by 0x380A027A: thread_wrapper (syswrap-linux.c:103)
==32085==by 0x380A027A: run_a_thread_NORETURN (syswrap-linux.c:156)



Reproducible: Always

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

[valgrind] [Bug 369361] vmsplice syscall wrapper crashes on bad iovec

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101289
  --> https://bugs.kde.org/attachment.cgi?id=101289=edit
Fix crash in vmsplice linux kernel wrapper when iovec is bad

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

Diese Altersvorsorge lohnt sich 6,1 % - Focus-Money hat getestet!

[Kathrin SchereSabrina Voigt]

Sehr geehrte Damen und Herren,

Sie wollen für Ihren Lebensabend finanziell vorsorgen? Dann sollten
Sie einen gelungenen Kompromiss zwischen  Rendite und Sicherheit
vergleichen.

Ihre zeitgemäße Kapitalanlage in unsicheren Zeiten - jetzt Infos
erhalten!

http://news.kapitalanlage-vergleich.org/track/?id=A409D3D824=86FFFB1FF5=0A438BDAE7

Ihnen ist eine flexible Anlage wichtig? Gleichzeitig wollen Sie eine
hohe Rendite mit genügend Sicherheit?

Hier die Fakten im Überblick für Sie:

- 4,2 % bis 6,1 %  Rendite garantiert
- kurze Laufzeiten
- geringe Mindesteinlage
- ohne Gebühren und Agio!

Freundliche Grüße


Sabrina Voigt
Focus-Money / Anlageberaterin

Neuigkeiten abbstellen:
http://news.kapitalanlage-vergleich.org/unsubscribe/?id=A409D3D824=0A438BDAE7=6047327159=lfhdGCrKBPiBBb-JepbzdpX4ijX1cn-pZhylGU-YtasAvENlK7HSo5xQ00fOrkUE

[krita] [Bug 369306] Unfocusing the window then drawing at the canvas yields no pressure detection or smoothing at the initial stroke.

[Phoenix Enero via KDE Bugzilla]

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

--- Comment #2 from Phoenix Enero  ---
@wolthera

I said nothing about window unfocusing mid-stroke.

My workflow involves Krita occupying one-half (or more) of my screen, with the
rest containing a browser showing my reference photos, I move a lot between the
programs so it's slightly annoying that after focusing on the browser then
drawing on the (Krita) canvas it yields a non-pressure detected stroke.

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

[kleopatra] [Bug 369348] creating a personal OpenPGP key pair results in a general error

[Gert Rijckmans via KDE Bugzilla]

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

--- Comment #2 from Gert Rijckmans  ---
Hi, no special characters in email adress and I didn't change anything in the
Advanced Options subdialog.

I used the gpg4win-2.3.3.exe installer package from https://www.gpg4win.org/

I installed the package as Adminstrator and run Kleopatra as Administrator.

Is there any way to check a log file ?

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

[korgac] [Bug 329730] reminder does not pop up at login if digital clock widget runs

[Franky via KDE Bugzilla]

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

--- Comment #11 from Franky  ---
Forgotten: My solution with the script provided in comment 7 also doesn't work
anymore.

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

[kate] [Bug 134781] API to modify some aspects of an active highlighting definition

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #5 from Dominik Haumann  ---
Thomas, is this still an issue for you? We are currently working on a new git
repository called syntax-highlighting. What are you use cases exactly? I'm not
sure modifying keyword lists is really a good idea, since to be sure, you'd
need to rehighlighting everything then (since there could be other context
switches then).

MovingRanges are imho indeed what you want. What you are missing is a proper
parser then, but I'm not convinved Kate's syntax highlighting files should act
as parser for you :-)

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

[kcalc] [Bug 321912] kcalc: radix point not available in any other than base 10

[Bob Wya via KDE Bugzilla]

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

Bob Wya  changed:

   What|Removed |Added

 CC||bob.mt@gmail.com

--- Comment #3 from Bob Wya  ---
Still not available in kcalc version 16.08.1... One can live in hope... :-(

I'd like to be able to use binary radix points - in Numerical System mode -  as
well! 

Why? Well it's useful for calculating the reciprocal of a decimal number, in
binary, to do bit-shift unsigned division. See:
http://www.hackersdelight.org/divcMore.pdf

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

[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro

[via KDE Bugzilla]

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

paul.yeom...@gmail.com changed:

   What|Removed |Added

 CC||paul.yeom...@gmail.com

--- Comment #46 from paul.yeom...@gmail.com ---
Sorry to add just a 'ME2' comment (Win 10, Krita 3.0.1, Huion H610 with
12.2.16.160527 Driver), Also to say that Downshift7's tip above to map the key
combination and set the stylus button to the same shortcut works for me.

If it helps, track down the setting in Krita via:
Settings > Configure Krita > Canvas Input Settings > Show Popup Palette

NOT the 'Keyboard Shortcuts' panel of the config dialog!

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

[valgrind] [Bug 369362] Bad sigaction arguments crash valgrind

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101290
  --> https://bugs.kde.org/attachment.cgi?id=101290=edit
Fix crash in linux [rt_]sigaction wrapper with bad old/new sigaction handler.

Since we try to modify the old/new sigaction handler before passing it
to the kernel we must make sure that (if they aren't NULL) it is safe
to use. If not we should bail out early with EFAULT.

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

[kdev-python] [Bug 369367] New: Caught exceptions get wrong scope (py3 change)

[Nicolás Alvarez via KDE Bugzilla]

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

Bug ID: 369367
   Summary: Caught exceptions get wrong scope (py3 change)
   Product: kdev-python
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: nicolas.alva...@gmail.com

Python3 has changed the scoping for exceptions caught in an 'except..as'
statement. The Python3 documentation says: "When an exception has been assigned
using "as target", it is cleared at the end of the except clause. This means
the exception must be assigned to a different name to be able to refer to it
after the except clause."

Sample code:

try:
a=1/0
except Exception as exc:
print("1", exc)

print("2", exc)

If I run this on Python2, it prints "division by zero" twice. If I run it on
Python3, it prints "division by zero" in print #1, and then raises a NameError
in #2 because 'exc' is not defined.

KDevelop still follows the Python2 scoping in this case, and 'exc' is still
highlighted as a use of the variable in the second 'print' call.

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

[i18n] [Bug 369354] Wrong translation for german when you search for faces

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

  Component|Faces-Management|de
 Status|UNCONFIRMED |CONFIRMED
Version|5.2.0   |unspecified
 Ever confirmed|0   |1
Product|digikam |i18n
   Assignee|digikam-de...@kde.org   |kde-i18n...@kde.org
 CC||lu...@hube-lueck.de

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

[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time

[via KDE Bugzilla]

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

--- Comment #7 from qualimerjud...@gmail.com ---
(In reply to nikolaos from comment #6)
> I have a problem setting the start and times as well. 
> 
> Whenever I hit "Apply" or "OK", the times are both reset to 12:00PM. I had
> the time format set to Greece and changing it to United States doesn't fix
> the problem. The event then usually does not display in the Agenda view as
> it has zero duration, but it show in the Month view. 
> 
> Some other times, however, it shows in the Agenda view spanning all day
> long, eg if I had set the event to be on the 3rd of July, then it will span
> from 00:00AM to 12:00 PM. I can then resize the event with the graphical
> handles and set its starting and ending times correctly. If I then try to
> re-edit this event and save, it will break again.

This sounds like a slightly different problem to the bug... Looking at the list
of time formats, I am unable to find Greece. Are you sure you changed the time
format, and not the time zone? I can see Athens in the list of time zones, but
there is no Greece in the time formats.

But just to check, if you open up your Korganizer and click the 'New Event'
button, are you able to select AM and PM times for the start/end configuration?
Try setting a start time of 9:00 AM and an end time of 10:00 PM. If this is the
same bug, then after setting both, the start time would be instead 9:00 PM.

For further reference, switching the time format (on Plasma 5) goes as follows:
System settings -> Regional settings -> Formats -> Detailed settings -> Time =
United States - American English (en_US)

Logging out or rebooting should set the time format.

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

[konsole] [Bug 369370] CJK character is rendered with its lower half cutted

[ntsp via KDE Bugzilla]

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

--- Comment #4 from ntsp  ---
I don't know enough to pinpoint the problem, but I can say that various fonts
exhibit the issue to varying degrees (some appear to have more "room"
separating each line).

I have changed the Kate font to "Noto Sans Mono CJK JP" which solves the
problem for my own use case within Kate. The font isn't available through the
KDE fonts menu for the "Fixed width" selection so Konsole still looks wrong for
me.

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

[kmenuedit] [Bug 369371] New: "Run in terminal" is now broken

[PhillB via KDE Bugzilla]

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

Bug ID: 369371
   Summary: "Run in terminal" is now broken
   Product: kmenuedit
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: phi...@webwombat.com.au

Any terminal app can no longer be run from the menu. "Run in terminal" doesn't
work anymore.

Reproducible: Always

Steps to Reproduce:
1. Open menu editor.
2. Create new entry.
3. Add stuff to run "ssh localhost" with "Run in terminal" 

Actual Results:  
Terminal seems to flash then immediately disappears. All entries that used to
work no longer work.

Expected Results:  
Application run in a terminal as usual.

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

[konsole] [Bug 369370] CJK character is rendered with its lower half cutted

[ntsp via KDE Bugzilla]

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

ntsp  changed:

   What|Removed |Added

 CC||ntsp...@gmail.com

--- Comment #3 from ntsp  ---
Created attachment 101293
  --> https://bugs.kde.org/attachment.cgi?id=101293=edit
Japanese text is cut off

I have the same problem. It's not restricted to Konsole since it happens in
Kate/Kwrite as well. See the screenshot.

I'm on KDE Neon.
KDE Plasma Version: 5.7.5
KDE Frameworks Version: 5.26.0
Qt Version: 5.7.0

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

[kdepim] [Bug 258214] Choosing Completion Order from the context menu of the recipient field crashed kontact

[Christian Trippe via KDE Bugzilla]

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

Christian Trippe  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #11 from Christian Trippe  ---
The crash is still reproducible with the steps in comment 2 with kmail from KDE
Applications 16.04.3.

Updated backtrace
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6d655b17c0 (LWP 15476))]

Thread 24 (Thread 0x7f6ca79a1700 (LWP 16366)):
#0  0x7ffdae4fdb41 in clock_gettime ()
#1  0x7f6d62277c7d in clock_gettime () from /lib64/libc.so.6
#2  0x7f6d62c1d8f1 in qt_clock_gettime (ts=0x7f6ca79a0ba0, clock=1) at
tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f6d62d7d609 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f6cc8014b40) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f6d62d7db85 in QTimerInfoList::timerWait (this=0x7f6cc8014b40,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f6d62d7ed4e in timerSourcePrepareHelper (timeout=0x7f6ca79a0c54,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7f6ca79a0c54) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7f6d598b04ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f6d598b0d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cc8003ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6ca79a0e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#14 0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#15 0x7f6d62b79899 in QThreadPrivate::start (arg=0x6aba900) at
thread/qthread_unix.cpp:344
#16 0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#17 0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7f6cad571700 (LWP 15566)):
#0  0x7f6d62262bfd in poll () from /lib64/libc.so.6
#1  0x7f6d598b0e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cbc003350, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6cad570e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f6d62b79899 in QThreadPrivate::start (arg=0x265ded0) at
thread/qthread_unix.cpp:344
#7  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7f6cadd72700 (LWP 15563)):
#0  0x7f6d598f2cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6d598b0d55 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cb8003ed0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6cadd71e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f6d62b79899 in QThreadPrivate::start (arg=0x383cf00) at
thread/qthread_unix.cpp:344
#7  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f6caedc2700 (LWP 15532)):
#0  0x7f6d598f2cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6d598b078e in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cb0003260, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6caedc1e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f6d62b79899 in QThreadPrivate::start (arg=0x2a26f00) at
thread/qthread_unix.cpp:344
#8  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f6caf5c3700 (LWP 15531)):
#0  

[konsole] [Bug 369370] CJK character is rendered with its lower half cutted

[CDnX via KDE Bugzilla]

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

--- Comment #2 from CDnX  ---
[Update] maybe this is because of the fallback font (right expression?)

i changed the font to D2Coding, the free fixed-width font that includes korean
glyph, and this problem solved. so i think, if setted font has no corresponding
glyph, konsole find it on fallback font, and using two font occurs this error.

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

[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time

[via KDE Bugzilla]

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

--- Comment #8 from qualimerjud...@gmail.com ---
(In reply to qualimerjudith from comment #7)
> (In reply to nikolaos from comment #6)
> > I have a problem setting the start and times as well. 
> > 
> > Whenever I hit "Apply" or "OK", the times are both reset to 12:00PM. I had
> > the time format set to Greece and changing it to United States doesn't fix
> > the problem. The event then usually does not display in the Agenda view as
> > it has zero duration, but it show in the Month view. 
> > 
> > Some other times, however, it shows in the Agenda view spanning all day
> > long, eg if I had set the event to be on the 3rd of July, then it will span
> > from 00:00AM to 12:00 PM. I can then resize the event with the graphical
> > handles and set its starting and ending times correctly. If I then try to
> > re-edit this event and save, it will break again.
> 
> This sounds like a slightly different problem to the bug... Looking at the
> list of time formats, I am unable to find Greece. Are you sure you changed
> the time format, and not the time zone? I can see Athens in the list of time
> zones, but there is no Greece in the time formats.
> 
> But just to check, if you open up your Korganizer and click the 'New Event'
> button, are you able to select AM and PM times for the start/end
> configuration? Try setting a start time of 9:00 AM and an end time of 10:00
> PM. If this is the same bug, then after setting both, the start time would
> be instead 9:00 PM.
> 
> For further reference, switching the time format (on Plasma 5) goes as
> follows:
> System settings -> Regional settings -> Formats -> Detailed settings -> Time
> = United States - American English (en_US)
> 
> Logging out or rebooting should set the time format.

Ah, apologies - Greece is indeed there, but not in English, so it was difficult
to find.

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

[kdenlive] [Bug 369023] I want to downgrade to 16.04.3 because 16.08.1 is essentially unusable for me

[YEK via KDE Bugzilla]

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

--- Comment #12 from YEK  ---
Thank you. I appreciate you taking the time to do that.

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

[kmail2] [Bug 282132] mail replies are shown in the message list without sender (aka from:) information

[Michi via KDE Bugzilla]

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

--- Comment #3 from Michi  ---
I still have this problem, but only with one particular mail account. All my
other accounts do not exhibit this behavior.

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

[krita] [Bug 369305] New: Color picking alternate invocation gets stuck when un-focusing the Krita window

[Phoenix Enero via KDE Bugzilla]

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

Bug ID: 369305
   Summary: Color picking alternate invocation gets stuck when
un-focusing the Krita window
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: phoenix.en...@gmail.com

Activating any of the color picking alternate invocation (such as when holding
the Control Key) then placing the Krita window out of focus keeps the activated
invocation stuck.

Reproducible: Always

Steps to Reproduce:
Set Canvas Input Settings → Alternative Invocation to default. Keep the Krita
program windowed (for convenience as you'll see later.)

1. Open any document or create a new one.
2. Place your cursor in the Krita canvas area.
3. Hold the control key. You should see a Foreground Color PIck.
4. While holding the control key, un-focus the Krita window by clicking
anywhere that isn't the Krita window.
5. Release the control key.
6. Move the cursor back to the Krita canvas.

Actual Results:  
The Foreground Color PIck mode is still activated. Clicking the canvas will
pick the color instead of placing a brush stroke.

Expected Results:  
The Foreground Color Pick mode is not activated. Clicking the canvas would
place a brush stroke instead of picking the color.

Similar behavior is shown with the other Color Pick alternate invocations:
Foreground Color Pick from Current Layer, Background Color Pick from Current
Layer, Background Color Pick from Merged Layers.

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

[kontact] [Bug 330041] kontact crashes when closing app while IMAP operation is still ongoing

[Michi via KDE Bugzilla]

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

--- Comment #2 from Michi  ---
seems to be fixed

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

[korganizer] [Bug 339828] Changing an appointment twice in quick succession results in conflict resolution dialog

[Sander van Grieken via KDE Bugzilla]

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

Sander van Grieken  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Sander van Grieken  ---
Cannot reproduce anymore in korganizer5

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

[kmail2] [Bug 186524] reply selects wrong identity for folder

[Peter Lewis via KDE Bugzilla]

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

Peter Lewis  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Peter Lewis  ---
Using KDE 4.14 this bug is no longer present.

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