[pimsettingexporter] [Bug 369375] New: Using pimsettingexporter --import fails to restore settings from other version of OS

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 369375
   Summary: Using pimsettingexporter --import fails to restore
settings from other version of OS
   Product: pimsettingexporter
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: freekdekru...@kde.nl

I used pimsettingexporter to save all settings on openSUSE 42,1. To restore
these settings on the same account in openSUSE 42.2 I use:
>  pimsettingexporter -v
pimsettingexporter 5.3.0 (QtWebEngine)
The main problem I had was that this application did not use the names I gave
to the 6 IMAP servers I use. So I has problems to match folders that were
presented to me to match to folders on the new account. I just want to mimic
the situation on the older system on the new system. So finally I did hit the
Cancel button repeatedly which resulted in a crash. I started the application
on a console so I got the error message.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 4483, resource id:
46141944, major code: 40 (TranslateCoords), minor code: 0
KCrash: Application 'pimsettingexporter' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

Because I did run the application twice, I got all accounts, servers etc. twice
in the system, which became apparent after starting kontact. So probably the
default should be to overwrite all information instead of merging things in a
new run of the application.


Reproducible: Always



Expected Results:  
I would expect to run the application without many questions about how to match
folders and just have a setup that mimics the original setup it gets imported
from.

I will delete the account and start all over again.

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

[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #7 from Freek de Kruijf  ---
(In reply to David Edmundson from comment #6)
> the giant translation bundles contain translations for all KDE software -
> including stuff that you happen to not be using.
> 
> I don't understand what you think the problem is.

The problem is that plasma_applet_kdeobservatory is obsolete. So it should not
end up in the giant bundle anymore.

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

[kmail2] [Bug 337656] Choosing a custom font for the message text does not work

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED

--- Comment #3 from Freek de Kruijf  ---
Tried it with kmail5 16.08.1. I was unable to change the font and its size used
in the message and message list panels. Changing this in the folder panel works
as expected.

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

[kmail2] [Bug 292516] KMail2 IMAP accounts keep crashing and loosing email content

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Freek de Kruijf  ---
Does not happen anymore. Is no longer reproducible. Consider it fixed.

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

[kmail2] [Bug 298399] 'Customize accounts order' randomly fails if folders are sorted manually

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--- Comment #14 from Freek de Kruijf  ---
Checked it for kmail5 16.08.1 and it works as it should.

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

[Akonadi] [Bug 338215] A substring in a call to drkonqi from akonadi in kdepimlibs is not completely filled in

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Freek de Kruijf  ---
I am unable to check this for kmail5 or rather akonadi. It appeared when
connecting to a courier IMAP server with a problem. Now I am using dovecot.
Can't reproduce it.

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

[kaddressbook] [Bug 280800] kmail group contacts not working

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #8 from Freek de Kruijf  ---
Checked it in kmail5 16.08.01. Problem does not exist anymore.

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

[kontact] [Bug 369333] New: Crash when deleting message in kmail2

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 369333
   Summary: Crash when deleting message in kmail2
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: freekdekru...@kde.nl

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was going through a number of new messages, which were successively deleted.
After a few KMail crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f20a9216600 (LWP 8190))]

Thread 34 (Thread 0x7f1f58af9700 (LWP 8303)):
#0  0x7f20a0e50ea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f20a0e0b996 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f20a66efaab in QEventDispatcherGlib::processEvents (this=0x32d48b0,
flags=...) at kernel/qeventdispatcher_glib.cpp:419
#3  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f58af8c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#5  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x30e9d70) at
thread/qthread_unix.cpp:341
#6  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f1f5ba3e700 (LWP 8300)):
#0  0x7f20a66eefa0 in timerSourcePrepareHelper (timeout=0x7f1f5ba3dab4,
src=) at kernel/qeventdispatcher_glib.cpp:126
#1  timerSourcePrepare (source=, timeout=0x7f1f5ba3dab4) at
kernel/qeventdispatcher_glib.cpp:159
#2  0x7f20a0e0ad79 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f20a0e0b79b in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f20a0e0b98c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f20a66efaab in QEventDispatcherGlib::processEvents
(this=0x7f1f58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#6  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f5ba3dc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#8  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x30f1f90) at
thread/qthread_unix.cpp:341
#9  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#10 0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f1f697a6700 (LWP 8248)):
#0  0x7f20a1a6410f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20991e4d49 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f20991e5460 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f20991e5630 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f20991e223d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f1f6abed700 (LWP 8242)):
#0  0x7f20a1a6410f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20991e4d49 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f20991e5460 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f20991e5630 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f20991e223d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#6  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f1f6b3ee700 (LWP 8237)):
#0  0x7f20a0e0afe5 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f20a0e0b7e8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f20a0e0b98c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f20a66efaab in QEventDispatcherGlib::processEvents
(this=0x7f1f5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f20a66976fa in QEventLoop::exec (this=this@entry=0x7f1f6b3edc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f20a64bd3c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f20a64c22e8 in QThreadPrivate::start (arg=0x2348d30) at
thread/qthread_unix.cpp:341
#7  0x7f20a1a5e454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f20a5bb93ff in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f1f6bbef700 (LWP 8235)):
#0  0x7f20a0e0af30 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  

[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #5 from Freek de Kruijf  ---
The file plasma_applet_kdeobservatory.po is still in kde-l10n-nl-16.08.0.tar.xz
from the download site of kde.org. Should it be removed?

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

[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DOWNSTREAM  |---

--- Comment #4 from Freek de Kruijf  ---
I raised the issue downstream in openSUSE, but the answer from there is that it
is unclear how the KDE project provides the newest versions of translations to
downstream distributors. Could you enlighten me on that?

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

[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REOPENED

--- Comment #2 from Freek de Kruijf  ---
It may be a problem with the openSUSE distribution. I have the problem at least
in the Tumbleweed version. I found the missing message in
/usr/share/locale/nl/LC_MESSAGES/plasma_applet_kdeobservatory.mo, which comes
with the package kde-l10n-nl-16.08.0-1.2.noarch. I inspected the build system
where this package is build and found it comes from a tar file
kde-l10n-nl-16.08.0.tar.xz. I assume this comes from the KDE project. I
inspected that tar file and found the mentioned po file in it. So at least the
bug is that this po file should not be included anymore. The question arises
also, whether other files should be excluded there as well.

To answer your question about the missing message or rather a message with a
typo which has been fixed in the po file quite some time ago. I found that one
in /usr/share/locale-bundle/nl/LC_MESSAGES/pkupdates.mo. Which comes from the
package bundle-lang-kde-nl-13.2-30.1.noarch. I inspected the building system
which generates this package, but this one is too complicated to find why this
system is not using the more up-to-date po file. So I will first file a bug
report in openSUSE about using not-up-to-date po files to generate this
package.

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

[plasmashell] [Bug 369200] New: translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 369200
   Summary: translation file for plasma_applet_kdeobservatory.pot
is missing in svn repository
   Product: plasmashell
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: freekdekru...@kde.nl
CC: bhus...@gmail.com, plasma-b...@kde.org

Using the plasma applet to update packages I found untranslated messages.
Searching the system I found that these messages should come from
plasma_applet_kdeobservatory.mo. Searching the svn repository for a file
plasma_applet_kdeobservatory.pot I found this file is not present. So
apparently at least this file is not presented for translation.
The po file is present in kde-l10n-nl-16.08.0.tar.xz, but the last translation
is from 2010, where the pot file is from 2014.

Reproducible: Always



Expected Results:  
The system should present this file for translation. Maybe other pot files are
missing as well.

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

[kmail2] [Bug 366204] Setting Fancy headers in View is not kept in kmail 16.04

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #4 from Freek de Kruijf  ---
Thanks, the workaround works!

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

[kmail2] [Bug 366204] Setting Fancy headers in View is not kept in kmail 16.04

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #2 from Freek de Kruijf  ---
(In reply to Michal Hlavac from comment #1)
> as workaround edit ~/.config/kmail2rc and search for entry
> header-plugin-style-name.

There is no such entry in this file.

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

[lokalize] [Bug 368842] New: Behavior of navigation in lokalize is broken

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 368842
   Summary: Behavior of navigation in lokalize is broken
   Product: lokalize
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: project management
  Assignee: sha...@ukr.net
  Reporter: freekdekru...@kde.nl

Using lokalize 16.08.0 I have a project project file showing two folders,
docmessages and messages.
Expanding messages I see the list of folders for the subdivision of KDE.
Expanding one of the subdivisions, I see the .po files or sometimes the .pot
files. Selecting a .pot file an opening it for editing I select "Save as..."
from the "File" menu item in the main toolbar.

1. The first problem is that this brings dialog to save a file, which used to
have the name of the .po already present in the text box used for the new file
name. Now one has to fill this is, which is error prone.
2. The second problem occurs after saving the .po file an exiting the editor
window. This shows the project tab, but in the tab the content is completely
repainted and only the two top folders are shown. This used to be the same as
it was just before selecting the .pot file.
3. After selection of a .po file for editing and exiting that window, the
project tab used to be the same as it was before the selection. Using the Up or
Down arrow key used to go the next or previous line in the project tab. This is
no longer the case. Having expanded the messages folder it might jump back to a
.po file in a subfolder in the docmessages folder.

Please bring back the behavior in this respect like it was before.

Reproducible: Always

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

[lokalize] [Bug 367712] New: Selecting a .pot file in the project windows, in the editor window Save as... does not fill in the .po file name

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 367712
   Summary: Selecting a .pot file in the project windows, in the
editor window Save as... does not fill in the .po file
name
   Product: lokalize
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sha...@ukr.net
  Reporter: freekdekru...@kde.nl

This is lokalize 16.04.3.
Selecting a .pot file in the project window, because the .po file does not
exist, opens the editor window with the .po file name as the title of the tab.
Using File->Save as... opens a popup file window. However the text field for
the file name is empty. This used to contain the name of the .po file, which is
very convenient. Entering the file name is a nuisance and not necessary as
previous versions of lokalize showed.

Reproducible: Always




Fill in the .po file name.

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

[drkonqi] [Bug 337758] After specifying account name and password for bugs.kde.org drkonqi reports a 410 failed authentication

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

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

--- Comment #26 from Freek de Kruijf  ---
Apparently solved.

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

[kmail2] [Bug 367589] Header of message list does not show all activated items

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #2 from Freek de Kruijf  ---
Created attachment 100690
  --> https://bugs.kde.org/attachment.cgi?id=100690=edit
image 2

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

[kmail2] [Bug 367589] Header of message list does not show all activated items

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #1 from Freek de Kruijf  ---
Created attachment 100689
  --> https://bugs.kde.org/attachment.cgi?id=100689=edit
image 1

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

[kmail2] [Bug 367589] New: Header of message list does not show all activated items

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 367589
   Summary: Header of message list does not show all activated
items
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: f.de.kru...@gmail.com

Image 1 shows the header of the message list after starting kontact with kmail
as the default module. It shows 3 additional items next to the Subject
(Onderwerp) column. However 4 items are activated as can be seen in the second
image. Size (Grootte) is not present as a column in the header. In order to
make this column present one needs to deactivate Bijlage (Attachment) first and
activate Groote (Size) and Bijlage (Attachment) in that order.

Reproducible: Always




# kmail -v
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
kmail2 5.2.3
# kontact -v
kontact 5.2.3

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

[kontact] [Bug 367031] New: Deleting message in a threaded message causes a crash

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 367031
   Summary: Deleting message in a threaded message causes a crash
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: f.de.kru...@gmail.com

Application: kontact (5.3.40 pre (QtWebEngine))

Qt Version: 5.7.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20160812) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Deleting a message in a thread of messages like the description of the already
reported message.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f166fba0940 (LWP 3309))]

Thread 31 (Thread 0x7f14da3ed700 (LWP 3422)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154b242b03 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f154b57ea81 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#4  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f14dabee700 (LWP 3421)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154b242b03 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f154b57ea81 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#4  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f14db3ef700 (LWP 3420)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154b242b03 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f154b57ea81 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#4  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f14dbbf0700 (LWP 3419)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154b2419b1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f154b57ea81 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#4  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f152124a700 (LWP 3418)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154b54dd8b in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f154b54ddc9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#4  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f152959e700 (LWP 3387)):
#0  0x7f166c5b4a1d in poll () from /lib64/libc.so.6
#1  0x7f166626a056 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f166626a16c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f166d0ef1bb in QEventDispatcherGlib::processEvents
(this=0x7f151c000940, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f166d0984da in QEventLoop::exec (this=this@entry=0x7f152959dc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f166cec5b83 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f166ceca986 in QThreadPrivate::start (arg=0x153fdd0) at
thread/qthread_unix.cpp:368
#7  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#8  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f152b2ec700 (LWP 3384)):
#0  0x7f166846809f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f165f28cd89 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f165f28d3a9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f165f28d560 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f165f28a197 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f1668462474 in start_thread () from /lib64/libpthread.so.0
#6  0x7f166c5bd3ed in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f1546b00700 (LWP 3346)):
#0  0x7f16662ae0a5 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f1666269a7c in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f1666269ff4 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f166626a16c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f166d0ef1bb in QEventDispatcherGlib::processEvents
(this=0x7f153c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f166d0984da in QEventLoop::exec (this=this@entry=0x7f1546affc80,
flags=..., flags@entry=...) at 

[drkonqi] [Bug 366792] trying to report a crash, drkonqi needs to install debug packages, which takes too long, cancel causes the crash

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #2 from Freek de Kruijf  ---
After applying today's update of Tumbleweed's Unstable KDE packages (kmail
package version reported as 16.11.60git.20160816T021536~cb4e447-978.1), the
problem in kmail did not occur anymore. So drkonqi did not start. The problem
is not reproducible anymore.

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

[drkonqi] [Bug 366792] New: trying to report a crash, drkonqi needs to install debug packages, which takes too long, cancel causes the crash

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 366792
   Summary: trying to report a crash, drkonqi needs to install
debug packages, which takes too long, cancel causes
the crash
   Product: drkonqi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: f.de.kru...@gmail.com

After a crash of kontact, drkonqi needs to install debug packages. Trying to do
so takes too long. Pressing Cancel crashes drkonqi.
I did install kontact-debuginfo and libKF5KontactInterface5-debuginfo, but this
was not enough to skip the installation of debug packages.

Reproducible: Always

Steps to Reproduce:
1. Start kontact using kmail and click on a message with a text attachment.
Using Fancy headers, the header is displayed in a flickering way. Showing the
name of the attachment for a while and after that without that name after which
this is repeated. Clicking on the name of the attachment, in order to be able
to save it, causes the crash of kontact.
2. Press to load debuginfo packages and after several minutes, press Cancel.



This is the beta version of the current KF5 applications, together with
Framework and Qt5.7.

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

[kontactinterface] [Bug 366206] Left panel of Kontact does not fit properly in left space of Kontact

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #1 from Freek de Kruijf  ---
Created attachment 100351
  --> https://bugs.kde.org/attachment.cgi?id=100351=edit
Screenshot

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

[kontactinterface] [Bug 366206] New: Left panel of Kontact does not fit properly in left space of Kontact

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 366206
   Summary: Left panel of Kontact does not fit properly in left
space of Kontact
   Product: kontactinterface
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: f.de.kru...@gmail.com

See picture. The panel in which to choose between i.e. KMail or Adresses is not
properly aligned in the reserved space. There is unoccupied space on the right
and the subwindow with icons is too small.

Reproducible: Always

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

[kmail2] [Bug 366204] New: Setting Fancy headers in View is not kept in kmail 16.04

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 366204
   Summary: Setting Fancy headers in View is not kept in kmail
16.04
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: f.de.kru...@gmail.com

After setting Fancy Headers in menu View->Headers and leaving KMail/Kontact
this setting is not preserved in the next invocation of Kontact/Kmail. It
starts with the setting KMail 5.2.

Reproducible: Always

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

[lokalize] [Bug 348573] The Dutch translation for the documentation of lokalize is missing in kde-l10n-nl.x.y.x.tar.xz

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

Summary|Tar file of lokalize only   |The Dutch translation for
   |contains the English|the documentation of
   |documentation   |lokalize is missing in
   ||kde-l10n-nl.x.y.x.tar.xz

--- Comment #2 from Freek de Kruijf  ---
So this bug report should be handled by the people who do the packaging for
kde-l10n-LANG.
This bug is still present in version 16.03.90.

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

[lokalize] [Bug 363735] After opening a project file the tab Project Overview shows nothing; window does not get repainted

[Freek de Kruijf via KDE Bugzilla]

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

Freek de Kruijf  changed:

   What|Removed |Added

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

--- Comment #1 from Freek de Kruijf  ---
Problem seems to have been resolved.

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

[lokalize] [Bug 363735] New: After opening a project file the tab Project Overview shows nothing; window does not get repainted

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 363735
   Summary: After opening a project file the tab Project Overview
shows nothing; window does not get repainted
   Product: lokalize
   Version: 2.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: sha...@ukr.net
  Reporter: f.de.kru...@gmail.com

After opening a project file the tab Project Overview (PO) shows nothing.
However the status bar shows the statistics. Clicking on the tab Translation
Memory (TM) and back on Project Overview, the window shows the po folders.
Trying to open a folder by clicking on the > in front of the folder should
unfold the folder and show the po files. However nothing changes in the window.
Again clicking tab TM and back PO now shows the unfolded folder. So apparently
after a change the window is not repainted.

Reproducible: Always




The versions of, and the underlying software are:
KDE Frameworks 5.22.0
Qt 5.6.0 (built against 5.6.0)
The xcb windowing system

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

[plasmashell] [Bug 358699] New: Crash when configuring Appearance of KMail

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 358699
   Summary: Crash when configuring Appearance of KMail
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: f.de.kru...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

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

I was configuring Fonts in the Appearance of KMail during which this crash
occurred

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3ef8dfd8c0 (LWP 1815))]

Thread 22 (Thread 0x7f3ee2361700 (LWP 1816)):
#0  0x7f3ef237a24d in poll () from /lib64/libc.so.6
#1  0x7f3ef7250432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f3ef7252007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f3ee44b0e29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f3ef2a6b94f in QThreadPrivate::start (arg=0x18b5f70) at
thread/qthread_unix.cpp:331
#5  0x7f3ef1b814a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f3ef2382bdd in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f3edb3ea700 (LWP 1835)):
#0  0x7f3ef2a63d1a in testAndSetRelaxed
(currentValue=, newValue=0x1, expectedValue=0x0,
_q_value=@0x19c92d8: 0x1) at ../../src/corelib/arch/qatomic_x86.h:259
#1  testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, _q_value=@0x19c92d8:
0x1) at ../../src/corelib/thread/qgenericatomic.h:166
#2  testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=0x19c92d8, this@entry=0x29) at
../../src/corelib/thread/qbasicatomic.h:278
#3  fastTryLock (current=, this=0x19c92d8, this@entry=0x29)
at thread/qmutex.h:82
#4  QMutex::lock (this=this@entry=0x19c92d8) at thread/qmutex.cpp:212
#5  0x7f3ef2c8fdb9 in QMutexLocker (m=0x19c92d8, this=)
at ../../src/corelib/thread/qmutex.h:128
#6  canWaitLocked (this=0x19c92b0) at ../../src/corelib/thread/qthread_p.h:240
#7  postEventSourcePrepare (timeout=, s=0x7f3ed40012d0) at
kernel/qeventdispatcher_glib.cpp:254
#8  postEventSourceCheck (source=0x7f3ed40012d0) at
kernel/qeventdispatcher_glib.cpp:264
#9  0x7f3eeea6dce1 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f3eeea6e208 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f3eeea6e36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f3ef2c9052b in QEventDispatcherGlib::processEvents
(this=0x7f3ed40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#13 0x7f3ef2c3a63a in QEventLoop::exec (this=this@entry=0x7f3edb3e9cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#14 0x7f3ef2a66b1c in QThread::exec (this=this@entry=0x19c9100) at
thread/qthread.cpp:503
#15 0x7f3ef5d369a5 in QQmlThreadPrivate::run (this=0x19c9100) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#16 0x7f3ef2a6b94f in QThreadPrivate::start (arg=0x19c9100) at
thread/qthread_unix.cpp:331
#17 0x7f3ef1b814a4 in start_thread () from /lib64/libpthread.so.0
#18 0x7f3ef2382bdd in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f3ecd749700 (LWP 1846)):
#0  0x7f3ef1b8707f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3ed39900b3 in snprintf (__fmt=0x7f3ed3aa857a
"\357\377\360\070\357\377\340\070\357\377\360\070\357\377\360\070\357\377\360\070\357\377",
__n=16, __s=) at /usr/include/bits/stdio2.h:64
#2  thread_function (init_data=0x1c8f39c) at lp_rast.c:792
#3  0x7f3ed398ff37 in lp_rast_clear_color (task=0x1c8f39c, arg=...) at
lp_rast.c:145
#4  0x7f3ecd749700 in ?? ()
#5  0x0da34116a6dc97df in ?? ()
#6  0x in ?? ()

Thread 19 (Thread 0x7f3eccf48700 (LWP 1847)):
#0  0x7f3ef1b8707f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3ed39900b3 in snprintf (__fmt=0x7f3ed3aa857a
"\357\377\360\070\357\377\340\070\357\377\360\070\357\377\360\070\357\377\360\070\357\377",
__n=16, __s=) at /usr/include/bits/stdio2.h:64
#2  thread_function (init_data=0x1c8f504) at lp_rast.c:792
#3  0x7f3ed398ff37 in lp_rast_clear_color (task=0x1c8f504, arg=...) at
lp_rast.c:145
#4  0x7f3eccf48700 in ?? ()
#5  0x0da34116a6dc97df in ?? ()
#6  0x in ?? ()

Thread 18 (Thread 0x7f3ecc747700 (LWP 1848)):
#0  0x7f3ef1b8707f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3ed39900b3 in snprintf (__fmt=0x7f3ed3aa857a

[plasmashell] [Bug 358712] New: Icon of Device Notifier is too small and text remains in System Tray

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 358712
   Summary: Icon of Device Notifier is too small and text remains
in System Tray
   Product: plasmashell
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Device Notifier
  Assignee: plasma-b...@kde.org
  Reporter: f.de.kru...@gmail.com

The attached screenshot shows in the red circle the icon of the Device Notifier
which should be as large as the Icon of the Moon next to it.
I clicked left on this icon and the text "Geen apparaten beschikbaar" appeared
in the Tray, which is the text I get when hoovering over the Device Notifier
Icon. It stayed there, see Gee, the start in the blue ellips.

Reproducible: Always

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

[plasmashell] [Bug 358712] Icon of Device Notifier is too small and text remains in System Tray

[Freek de Kruijf via KDE Bugzilla]

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

--- Comment #1 from Freek de Kruijf  ---
Created attachment 96894
  --> https://bugs.kde.org/attachment.cgi?id=96894=edit
Screenshot with some extra ellipses

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