[drkonqi] [Bug 360981] Cannot select duplicated bug

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #1 from sedrubal  ---
Same here: fedora:24, drkonqi 5.7.5

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

[drkonqi] [Bug 354292] Crash Reporting Assistant login button is always disabled

[sedrubal via KDE Bugzilla]

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

--- Comment #8 from sedrubal  ---
Did you fix this? It didn't happen to me on fedora:24. If so: Thanks <3

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

[krunner] [Bug 353995] krunner crashes after searching for an application

[sedrubal via KDE Bugzilla]

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

--- Comment #4 from sedrubal  ---
Yes, it might be a dup...

>  What's the output of: $ balooctl checkDb

$ balooctl checkDb
DocumentTermsDB check ..
PostingDB check ..
4602362400342062 is missing term 5
5064243183353902 is missing term log
Checking file paths .. 
Total Document IDs: 199366
Invalid Entries: 0 (0%)

(after running at 100% on one cpu core for quite a long time.)

> and does the crash stop if you move the baloo db

It's hard to say as krunner is not always crashing. But why should this matter
when we disabled baloo?

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[sedrubal via KDE Bugzilla]

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

--- Comment #56 from sedrubal  ---
I didn't realized it on plasma 5.6.5 if this helps...

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

[krfb] [Bug 365018] New: Can't send invitations

[sedrubal via KDE Bugzilla]

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

Bug ID: 365018
   Summary: Can't send invitations
   Product: krfb
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: grundleb...@googlemail.com
  Reporter: k...@sedrubal.de

After I started the program I found no way to start a connection to another
device. After reading the manual I searched for creating a new invitation but I
found nothing...

Reproducible: Always

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

[kmail2] [Bug 364996] Attachment reminder works only in english by default

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

   Severity|minor   |wishlist
 CC||k...@sedrubal.de

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

[kmail2] [Bug 364996] New: Attachment reminder works only in english by default

[sedrubal via KDE Bugzilla]

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

Bug ID: 364996
   Summary: Attachment reminder works only in english by default
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

Could you please add more keywords for the attachment reminder? By default
there is only "attachment" and "attached". But it'd be nice if this works also
for other languages (e.g. German: "Anhang", "angehängt"). Maybe one can add
language specific keywords when selecting the dictionary for identities?

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

[kmail2] [Bug 287263] KMail shows no mails at all, just the loading animation

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #2 from sedrubal  ---
The same here:

Akonadi 5.1.51:
Driver=QSQLITE3

kmail2 5.1.3

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #17 from sedrubal  ---
Oh I'm sorry, I forgot this. But unfortunately it is still not fixed. Now I'm
running fedora 24 with Plasma 5.6 (plasmashell 5.6.4) and Amarok Diagnostics
says:

General Information:
   Amarok Version: 2.8.90
   KDE Version: 4.14.20
   Qt Version: 4.8.7
   Phonon Version: 4.9.0
   Phonon Backend: GStreamer (4.9.0)
   PulseAudio: Yes

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

[kontact] [Bug 364219] New: Crash after long loading

[sedrubal via KDE Bugzilla]

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

Bug ID: 364219
   Summary: Crash after long loading
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

Application: kontact (5.1.3)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I pressen Ctrl+Q to quit kmail because it loaded for quite a long time single
emails.
- Unusual behavior I noticed:
Kmail took a long time to load mails

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f24ba422940 (LWP 309))]

Thread 18 (Thread 0x7f241507c700 (LWP 5863)):
#0  0x7f24cbe15b49 in g_mutex_lock (mutex=mutex@entry=0x7f24040024d0) at
gthread-posix.c:1335
#1  0x7f24cbdd0f89 in g_main_context_prepare
(context=context@entry=0x7f24040024d0, priority=priority@entry=0x7f241507bb40)
at gmain.c:3444
#2  0x7f24cbdd196b in g_main_context_iterate
(context=context@entry=0x7f24040024d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3820
#3  0x7f24cbdd1b5c in g_main_context_iteration (context=0x7f24040024d0,
may_block=1) at gmain.c:3901
#4  0x7f24d384369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f24d37ea8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f24d36103f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f24d361543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f24ccffd5ba in start_thread (arg=0x7f241507c700) at
pthread_create.c:333
#9  0x7f24d2a007cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f24167fc700 (LWP 557)):
#0  g_mutex_unlock (mutex=0x7f240990) at gthread-posix.c:1347
#1  0x7f24cbdd0f70 in g_main_context_prepare
(context=context@entry=0x7f240990, priority=priority@entry=0x7f24167fbb40)
at gmain.c:3440
#2  0x7f24cbdd196b in g_main_context_iterate
(context=context@entry=0x7f240990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3820
#3  0x7f24cbdd1b5c in g_main_context_iteration (context=0x7f240990,
may_block=1) at gmain.c:3901
#4  0x7f24d384369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f24d37ea8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f24d36103f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f24d361543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f24ccffd5ba in start_thread (arg=0x7f24167fc700) at
pthread_create.c:333
#9  0x7f24d2a007cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f2416ffd700 (LWP 549)):
#0  0x7f24cbe15b49 in g_mutex_lock (mutex=mutex@entry=0x7f240c000990) at
gthread-posix.c:1335
#1  0x7f24cbdd0960 in g_main_context_acquire (context=0x7f240c000990) at
gmain.c:3214
#2  0x7f24cbdd18f5 in g_main_context_iterate
(context=context@entry=0x7f240c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3790
#3  0x7f24cbdd1b5c in g_main_context_iteration (context=0x7f240c000990,
may_block=1) at gmain.c:3901
#4  0x7f24d384369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f24d37ea8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f24d36103f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f24d361543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f24ccffd5ba in start_thread (arg=0x7f2416ffd700) at
pthread_create.c:333
#9  0x7f24d2a007cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f24177fe700 (LWP 437)):
#0  0x7f24d360cfd9 in QMutex::lock() () from /lib64/libQt5Core.so.5
#1  0x7f24d3842d2f in postEventSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#2  0x7f24cbdd0f7d in g_main_context_prepare
(context=context@entry=0x7f2408000990, priority=priority@entry=0x7f24177fdb40)
at gmain.c:3442
#3  0x7f24cbdd196b in g_main_context_iterate
(context=context@entry=0x7f2408000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3820
#4  0x7f24cbdd1b5c in g_main_context_iteration (context=0x7f2408000990,
may_block=1) at gmain.c:3901
#5  0x7f24d384369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f24d37ea8ca in
QEventLoop::exec(QFlags) () from

[kmail2] [Bug 363531] TLS negotiation was unsuccessful

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #2 from sedrubal  ---
Yes, it is checked, because the server supports TLS and I want to use TLS ;) it
is working with Thunderbird, K9-mail, evince and many other MUAs...

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

[kmail2] [Bug 363585] New: Wrong message "Some parts of this message will not be signed"

[sedrubal via KDE Bugzilla]

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

Bug ID: 363585
   Summary: Wrong message "Some parts of this message will not be
signed"
   Product: kmail2
   Version: 5.1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

I want to send a PGP signed email with attachments. Every attachments in
attachments list has the tick "sign". However I get the message:

> Some parts of this message will not be signed.
> Sending only partially signed messages might violate site policy.
> Sign all parts instead?

I think this message is wrong as I selected to sign every attachments. When I
select "Send as it is" it seems to sign everything anyway.

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

[kmail2] [Bug 363569] New: automatic PGP Key selection not working with + separated postfix in address

[sedrubal via KDE Bugzilla]

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

Bug ID: 363569
   Summary: automatic PGP Key selection not working with +
separated postfix in address
   Product: kmail2
   Version: 5.1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

Many SMTPs allow to send emails to adresses with a '+'-separated addition: e.g.
if I have the account: f...@example.com people can also send me mails to
foo+...@example.com.

Unfortunately the automatic key selector does not (always?) find a key to
foo+...@example.com even if there is one for f...@example.com

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

[kwalletmanager] [Bug 363532] "Allow Always" does not work

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #2 from sedrubal  ---
Yes, of course: kwallet-manager itself, kmail, owncloud-desktop kded5, kontact,
akonadi_resources

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

[kwalletmanager] [Bug 363533] New: Kwallet-manager blocks itself on closing

[sedrubal via KDE Bugzilla]

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

Bug ID: 363533
   Summary: Kwallet-manager blocks itself on closing
   Product: kwalletmanager
   Version: 2.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: k...@sedrubal.de

When kwallet-manager is connected to an open wallet and when clicking on close
I get always prompted that there are still connected applications and if I want
to force to close the wallet. But only kwallet-manager is connected or listed
in the connected applications list.

Reproducible: Always

Steps to Reproduce:
1. Open kwallet-manager
2. Don't let connect an other application to the wallet
3. close the wallet

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

[kwalletmanager] [Bug 363532] New: "Allow Always" does not work

[sedrubal via KDE Bugzilla]

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

Bug ID: 363532
   Summary: "Allow Always" does not work
   Product: kwalletmanager
   Version: 2.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: k...@sedrubal.de

I enabled that kwallet prompts me if an application wants to open a wallet.
Even if I've clicked "Allow Always" for some applications, I get always
prompted for the same applications again and the section "these applications
are authorized to access this wallet" keeps ampty

Reproducible: Always

Steps to Reproduce:
1. Configure to prompt for authorization
2. (Re-) login to KDE session so that applications want to access kwallet
3. Click "Allow Always"
4. Re-login to KDE and you'll get prompted again for the same applications

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

[kmail2] [Bug 363531] New: TLS negotiation was unsuccessful

[sedrubal via KDE Bugzilla]

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

Bug ID: 363531
   Summary: TLS negotiation was unsuccessful
   Product: kmail2
   Version: 5.1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

I want to send a mail using SMTP with STARTTLS. With other programs
(thunderbird, k9mail) there is not problem but kmail complains about a
unsuccessful TLS negotiation.

First warning dialogue:

> The server failed the authenticity check (mail.rommel.stw.uni-erlangen.de).
> 
> The certificate authority's certificate is invalid
> The certificate cannot be verified for internal reasons

Clicking on "Continue" works, clicking on "Details" displays the expected TLS
certificate (I thinkt everything is correct). Clicking on "Cancel" displays:

> Your SMTP server claims to support TLS, but negotiation was unsuccessful.
> You can disable TLS in the SMTP account settings dialog.

Is there a way to debug such issues (displaying the conversation between kmail
and the SMTP Server)?

The server is exim4.

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

[kmail2] [Bug 363301] Configuration dialog for additional accounts

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #2 from sedrubal  ---
Ouh sorry... I think kmail has so many features, that it is hard to find them
;)

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

[kmail2] [Bug 363301] New: Configuration dialog for additional accounts

[sedrubal via KDE Bugzilla]

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

Bug ID: 363301
   Summary: Configuration dialog for additional accounts
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: config dialog
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

On first run of kmail there appeared a configuration dialog (wizard) which is
very nice and very usable. But if you want to configure more than one (imap)
account, there is no way to start the wizard again or I didn't find a way. So
one has to configure it manually (-> an identity, an incoming account and an
outgoing account).

Is there already a way to rerun the wizard? Is it possible to add this feature
(especially for non powerusers...)?

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

[amarok] [Bug 354863] Amarok's volume is not linked with the system volume

[sedrubal via KDE Bugzilla]

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

--- Comment #5 from sedrubal  ---
Ok, thanks ;)

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

[kmail2] [Bug 362880] Customize accounts order should not be a extra window

[sedrubal via KDE Bugzilla]

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

--- Comment #7 from sedrubal  ---
Sorry for spamming... But I didn't completely understand, what this order is
good for and why pop3 can't be reordered...

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

[kmail2] [Bug 362880] Customize accounts order should not be a extra window

[sedrubal via KDE Bugzilla]

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

--- Comment #6 from sedrubal  ---
Mh :)

But directly dragging and dropping would be, I think...

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

[kmail2] [Bug 362880] Customize accounts order should not be a extra window

[sedrubal via KDE Bugzilla]

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

--- Comment #4 from sedrubal  ---
If one can't move pop3 resources, one can list them in a fixed list below the
imap list. Or one can display them at the end of the list and disable drag and
drop and the move buttons if a pop3 resource is selected.

I think the extra window is quite redundant and not intuitive...

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

[kmail2] [Bug 362880] Customize accounts order should not be a extra window

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #2 from sedrubal  ---
Oh, I thought, this order is only for UX? Why can't you move pop3 resources?

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

[kmail2] [Bug 362880] New: Customize accounts order should not be a extra window

[sedrubal via KDE Bugzilla]

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

Bug ID: 362880
   Summary: Customize accounts order should not be a extra window
   Product: kmail2
   Version: 4.14.10
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de

I think it'd be better to integrate the window "Customize accounts order" into
the "Accounts" config window instead of having a button and a extra window. One
could add the move up and move down button to the right of the "receiving"
accounts list and enable drag and drop for the accounts order.

Reproducible: Always

Steps to Reproduce:
1. Configure Kmail
2. Accounts
3. Customize accounts order

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

[plasmashell] [Bug 358245] plasmashell unresponsive/freezes after resuming from suspend to RAM

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #9 from sedrubal  ---
Do you think, this ist related? In my case, plasmashell/kscreenlocker crashed
after resume from suspending. After some time kscreenlock worked again but
plasmashell crashed.
Additionally I have often the problem, that all GTK applications have rendering
failures and drop some letters after resuming...

Application: plasmashell (5.5.5)

Qt Version: 5.6.0
Operating System: Linux 4.4.7-300.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f9dcf687940 (LWP 31324))]

Thread 16 (Thread 0x7f9dc5fa0700 (LWP 31358)):
#0  0x7f9dddf25fdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9de3098272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f9de3099ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f9dc81f3349 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f9ddeb37e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f9ddd26560a in start_thread (arg=0x7f9dc5fa0700) at
pthread_create.c:334
#6  0x7f9dddf31a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f9dc49aa700 (LWP 31359)):
#0  0x7f9dd99f6ac4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#1  0x7f9dd99f7110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9dd99f727c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9dded60d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9dded096ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9ddeb33004 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9ddf4f84b5 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f9ddeb37e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9ddd26560a in start_thread (arg=0x7f9dc49aa700) at
pthread_create.c:334
#9  0x7f9dddf31a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f9dbefbf700 (LWP 31360)):
#0  0x7f9dddf25fdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9dd99f716c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9dd99f727c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9dded60d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9dded096ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9ddeb33004 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9de1f281b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f9ddeb37e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9ddd26560a in start_thread (arg=0x7f9dbefbf700) at
pthread_create.c:334
#9  0x7f9dddf31a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f9db2fe6700 (LWP 31361)):
#0  0x7f9dddf25fdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9dd99f716c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9dd99f727c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9dded60d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9dded096ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9ddeb33004 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9de1f281b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f9ddeb37e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9ddd26560a in start_thread (arg=0x7f9db2fe6700) at
pthread_create.c:334
#9  0x7f9dddf31a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f9db1631700 (LWP 31362)):
#0  0x7f9dddf21bcd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9dd9a3a390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f9dd99f6c64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f9dd99f7110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f9dd99f727c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f9dded60d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f9dded096ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f9ddeb33004 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f9de1f281b5 

[amarok] [Bug 354863] Amarok's volume is not linked with the system volume

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #3 from sedrubal  ---
I can confirm this. Can you reopen it?

It's because sometimes the volume buttons change another channel than amarok
plays to (for me Amarok plays on "Built-in Audio Analog Stereo" <-
standard/fallback, changing the volume with volume buttons sometimes changes
"Simultaneous output to Built-in Audio Analog Stereo"). This sound to be a fail
in the linux audio system? (Don't know much about it).

The bug made by amarok is, that sometimes amarok is completely muted or
sometimes it is normal and suddenly when track changes the volume is 100%. This
also happens often after starting amarok (it starts with 100% even if it was
normal before).

Phonon Backend: VLC 0.8.2 (but I think it also happened with GStreamer 4.8.2)
Changes: Mh... I don't think there are important changes causing this problem.
I switched the phonon backend, changed volumes using pavucontrol, ...

KDE 5 (plasma5) (e.g. dolphin 15.12.3)

$> amarok --version
Qt: 4.8.7
KDE Development Platform: 4.14.18
Amarok: 2.8.0

Distro: Fedora 23

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

[Akonadi] [Bug 360880] New: IMAP Resource crashed on authentication problems

[sedrubal via KDE Bugzilla]

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

Bug ID: 360880
   Summary: IMAP Resource crashed on authentication problems
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: sebastian.end...@online.de
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.18
Qt Version: 4.8.7
Operating System: Linux 4.4.4-301.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Kmail tried to sync one of my IMAP resources but there is a (server side)
authentication failure. I get prompted that there ('Could Not Authenticate...')
is an error and I hit retry. Then it crashed

The crash can be reproduced sometimes.

-- Backtrace:
Application: FAU Mail of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f843a42c900 (LWP 4733))]

Thread 10 (Thread 0x7f841bb55700 (LWP 14572)):
#0  0x7f843522dfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f84345dc16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f84345dc27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f8439d50e7e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f840c004530, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f8439d1f131 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f841bb54cd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8439d1f4a5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f841bb54cd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f8439c0ea99 in QThread::exec() (this=) at
thread/qthread.cpp:538
#7  0x7f8439c1138c in QThreadPrivate::start(void*) (arg=0x5562d1167360) at
thread/qthread_unix.cpp:352
#8  0x7f843996f60a in start_thread (arg=0x7f841bb55700) at
pthread_create.c:334
#9  0x7f8435239a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f841933c700 (LWP 15005)):
#0  0x7f8434620730 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f84345dc161 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f84345dc27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f8439d50e7e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f840402c500, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f8439d1f131 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f841933bcd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8439d1f4a5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f841933bcd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f8439c0ea99 in QThread::exec() (this=) at
thread/qthread.cpp:538
#7  0x7f8439c1138c in QThreadPrivate::start(void*) (arg=0x5562d1117030) at
thread/qthread_unix.cpp:352
#8  0x7f843996f60a in start_thread (arg=0x7f841933c700) at
pthread_create.c:334
#9  0x7f8435239a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f8419d4e700 (LWP 26787)):
#0  0x7f8439977b4d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f843461f390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f84345dbc64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f84345dc110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f84345dc27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f8439d50e7e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f841001e2a0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f8439d1f131 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f8419d4dcd0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f8439d1f4a5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f8419d4dcd0, flags=...) at kernel/qeventloop.cpp:204
#8  0x7f8439c0ea99 in QThread::exec() (this=) at
thread/qthread.cpp:538
#9  0x7f8439c1138c in QThreadPrivate::start(void*) (arg=0x5562d1052e70) at
thread/qthread_unix.cpp:352
#10 0x7f843996f60a in start_thread (arg=0x7f8419d4e700) at
pthread_create.c:334
#11 0x7f8435239a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f841c356700 (LWP 31194)):
#0  0x7f843522dfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f84345dc16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f84345dc27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f8439d50e7e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f84142f5580, 

[kmail2] [Bug 360791] New: Add subscribe/unsubscribe button for mailing lists

[sedrubal via KDE Bugzilla]

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

Bug ID: 360791
   Summary: Add subscribe/unsubscribe button for mailing lists
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: sebastian.end...@online.de

Mails from mailing lists often have the headers:

List-Unsubscribe: , 
 
List-Help: 
List-Subscribe: , 
 

And there are webmailers (squirrel mail) which display buttons for quick
(un)subscribe.

It'd be nice if kmail does the same ;)

Reproducible: Always

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

[gwenview] [Bug 359736] Crash when reloading SVG image

[sedrubal via KDE Bugzilla]

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

--- Comment #1 from sedrubal  ---
Created attachment 97930
  --> https://bugs.kde.org/attachment.cgi?id=97930=edit
New crash information added by DrKonqi

gwenview (4.14.0 pre) on KDE Platform 4.14.17 using Qt 4.8.7

- What I was doing when the application crashed:

I changed the displayed svg and moved my cursor over gwenview.

-- Backtrace (Reduced):
#6  0x7f577ee77267 in QSvgTinyDocument::draw(QPainter*, QRectF const&) ()
at /lib64/libQtSvg.so.4
#7  0x7f577ee7a03e in QGraphicsSvgItem::paint(QPainter*,
QStyleOptionGraphicsItem const*, QWidget*) () at /lib64/libQtSvg.so.4
#10 0x7f577f8c38a6 in QGraphicsScenePrivate::drawItemHelper(QGraphicsItem*,
QPainter*, QStyleOptionGraphicsItem const*, QWidget*, bool) () at
/lib64/libQtGui.so.4
#11 0x7f577f8c459c in QGraphicsScenePrivate::draw(QGraphicsItem*,
QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double,
QTransform const*, bool, bool) () at /lib64/libQtGui.so.4
#12 0x7f577f8c5121 in
QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*,
QTransform const*, QRegion*, QWidget*, double, QTransform const*) () at
/lib64/libQtGui.so.4

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

[gwenview] [Bug 359736] Crash when reloading SVG image

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

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

[kmail2] [Bug 358233] Reply-To is missing in compose message window

[sedrubal via KDE Bugzilla]

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

--- Comment #5 from sedrubal  ---
Ah I see. Then the items would have to be removed from the drop down, after
they are set (that's ugly)

But as I can read it in (german) wikipedia [1] there can be several comma
separated reply-to addresses (in english wikipedia this information is
missing). So this might only be logical for reply to...

[1] https://de.wikipedia.org/wiki/Header_%28E-Mail%29#Reply-To:_Antwortadresse

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

[kmail2] [Bug 358233] Reply-To is missing in compose message window

[sedrubal via KDE Bugzilla]

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

--- Comment #3 from sedrubal  ---
Wow I've never opened this menu O.o

But I think the most users will expect 'From' and 'Reply To' in the dropdown
where you can select 'To', 'CC' and 'BCC'.

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

[kmail2] [Bug 358233] Reply-To is missing in compose message window

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

--- Comment #1 from sedrubal  ---
:+1: (I think this will not be much work to implement, but many users will be
happy ;) )

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

--- Comment #12 from sedrubal  ---
Is there a reliable way to find out the version?

konsole and kate --version says:
Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.1

kded5 --version
kded5 5.18.0

kded4 --version
Qt: 4.8.7
KDE Development Platform: 4.14.16
KDE Daemon: 4.14.16

amarok --version
Qt: 4.8.7
KDE Development Platform: 4.14.16
Amarok: 2.8.0

(For me it looks like that amarok has some problems when changing the track and
refreshing all infos: On almost every track change, my HDD starts rotating
which needs some time and the GUI of amarok is not running smoothly... or maybe
there are problems with dbus/mpris?)

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

--- Comment #10 from sedrubal  ---
Ok it seems to appear with vlc and gstreamer phonon backend. But only when I
start KDE; when I start i3wm and then amarok it doesn't happen...

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

--- Comment #9 from sedrubal  ---
Ok I installed phonon-backend-vlc and I will trie. Until now it didn't happen
again, but that may be also caused, because I currently use i3 instead of KDE
as Desktop (without plasmashell ;) ) I'll switch back soon and report...

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

--- Comment #7 from sedrubal  ---
Mh all my tracks are converted to ogg and there very few mp3s but this happens
too often, I don't think it happen because of that).

I haven't all gstreamer1 plugins installed but I can play MP3 (and I think aac)
(I installed codecs from rpmfusion :( ) and of course Ogg, WAV and FLAC.

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

[drkonqi] [Bug 359405] Crash after pressing "Reload"

[sedrubal via KDE Bugzilla]

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

sedrubal  changed:

   What|Removed |Added

 CC||sebastian.end...@online.de

--- Comment #1 from sedrubal  ---
Maybe bug 249418 is a dup, but it is very old and there is a commit linked to
fix this... and the backtrace looks different to me... So I opened a new one.

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

[amarok] [Bug 359357] Amarok skips tracks

[sedrubal via KDE Bugzilla]

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

--- Comment #4 from sedrubal  ---
Created attachment 97210
  --> https://bugs.kde.org/attachment.cgi?id=97210=edit
Debug output while amarok skips a track

 - I listened "Vance Joy" - "Ministry of Sound: Sunset Soul" - "Riptide
(FlicFlac edit)"
 - after that amarok skips "Robert.B" - "33. Shaggy - Boombastic"
 - and amarok keeps playing "Calvin Harris feat Haim" - "Pray To God" - "Mike
Pickering vs Calvin Harris Hacienda Remix"

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

[drkonqi] [Bug 359405] New: Crash after pressing "Reload"

[sedrubal via KDE Bugzilla]

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

Bug ID: 359405
   Summary: Crash after pressing "Reload"
   Product: drkonqi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sebastian.end...@online.de

Dr.Konqi crashed after I pressed "Reload" to reload the generated backtrace for
the crashed plasmashell. Then another dr. konqi appeard with less buttons and
functions as normally saying:

"""
We are sorry, drkonqi closed unexpectedly.
We cannot report this error, because drkonqi does not provide a bug reporting
address.
"""
// Can you please provide a bug reporting address for drkonqi?

"""
Details:
Executeable: drkonqi  Signal: Segmentation fault (11) 
"""

And in the tab "Developer information" there is this backtrace:

"""
Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0f6a36d8c0 (LWP 17094))]

Thread 2 (Thread 0x7f0f50ce0700 (LWP 17095)):
#0  0x7f0f65509fdd in poll () at /lib64/libc.so.6
#1  0x7f0f5ff06272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f0f5ff07ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f0f536b2da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f0f661123de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f0f63cc560a in start_thread () at /lib64/libpthread.so.0
#6  0x7f0f65515a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0f6a36d8c0 (LWP 17094)):
[KCrash Handler]
#5  0x558aae3d92d1 in GdbHighlighter::highlightBlock(QString const&) ()
#6  0x7f0f669803b2 in QSyntaxHighlighterPrivate::reformatBlock(QTextBlock
const&) () at /lib64/libQt5Gui.so.5
#7  0x7f0f66980696 in QSyntaxHighlighterPrivate::reformatBlocks(int, int,
int) () at /lib64/libQt5Gui.so.5
#8  0x7f0f6632229a in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#9  0x7f0f66bb035a in QTextDocument::contentsChange(int, int, int) () at
/lib64/libQt5Gui.so.5
#10 0x7f0f6693becd in QTextDocumentPrivate::finishEdit() () at
/lib64/libQt5Gui.so.5
#11 0x7f0f671ac4ee in QWidgetTextControlPrivate::append(QString const&,
Qt::TextFormat) () at /lib64/libQt5Widgets.so.5
#12 0x7f0f67189b89 in QTextEdit::append(QString const&) () at
/lib64/libQt5Widgets.so.5
#13 0x558aae3c79ad in BacktraceWidget::backtraceNewLine(QString const&) ()
#14 0x7f0f66322127 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#15 0x558aae415035 in BacktraceGenerator::newLine(QString const&) ()
#16 0x558aae3cc2a9 in BacktraceGenerator::slotReadInput() ()
#17 0x7f0f66322127 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#18 0x7f0f662291f2 in
QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) () at
/lib64/libQt5Core.so.5
#19 0x7f0f66229670 in QProcess::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libQt5Core.so.5
#20 0x7f0f6632229a in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#21 0x7f0f663a1eae in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () at /lib64/libQt5Core.so.5
#22 0x7f0f6632e74b in QSocketNotifier::event(QEvent*) () at
/lib64/libQt5Core.so.5
#23 0x7f0f66fd841c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#24 0x7f0f66fdd8e6 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#25 0x7f0f662f373b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#26 0x7f0f6634a37d in socketNotifierSourceDispatch(_GSource*, int
(*)(void*), void*) () at /lib64/libQt5Core.so.5
#27 0x7f0f63294e3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#28 0x7f0f632951d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#29 0x7f0f6329527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#30 0x7f0f66349eaf in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#31 0x7f0f662f0eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#32 0x7f0f662f8fac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#33 0x558aae3bf4f0 in main ()
"""

If you can't find a bug here, you can close this. I think, I can't give more
information... (I even don't know the version of drkonqi...)

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