[marble] [Bug 378156] GeoDataPlacemarks are not repainted properly after setStyle()

[Olle Lundin]

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

Olle Lundin  changed:

   What|Removed |Added

 CC||olle.lun...@titv.se

--- Comment #1 from Olle Lundin  ---
Seems to be the same problem as I reported in
https://bugs.kde.org/show_bug.cgi?id=378188

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

[partitionmanager] [Bug 378607] New: virtio devices not found (vda)

[Jerrod Frost]

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

Bug ID: 378607
   Summary: virtio devices not found (vda)
   Product: partitionmanager
   Version: 3.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: piroisl...@gmail.com
  Target Milestone: ---

(KVM/QEMU) Virtio devices are not recognized. I tried to partition a virtual
machine and noticed calamares and partitionmanager could not see/recognize vda.
virtio disks have advantages for virtual machines that emulating sata does not.
This is a must.

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

[plasmashell] [Bug 378606] New: Please replace those childish avatar images

[bugzilla_noreply]

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

Bug ID: 378606
   Summary: Please replace those childish avatar images
   Product: plasmashell
   Version: 5.9.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Hi all,

what kind of first impression of a new plasma version is this???
An avatar image coming from a childrens coloring book?

What kind of first impression do you want to give your users? Is this the kind
of professionalism you want to convey?
This is similiar if not worse than microsoft giving you a hint to name your
computer similar to 'ingrids kitchen computer' or 'gaming machine'...

So, please start being serious,
use proper - if you want to, gender neutral - avatars and stop playing like
that!!!

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

[plasmashell] [Bug 378605] New: Crash when start search in main menu

[Aleksey]

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

Bug ID: 378605
   Summary: Crash when start search in main menu
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aleo...@nazarianin.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-1-ck-k10 x86_64
Distribution (Platform): Archlinux Packages

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

Start search app in  main menu. Plasma crush when I write 2-3 text symbols in
string search Plasma.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1bd2c0a800 (LWP 4657))]

Thread 26 (Thread 0x7edaad79f700 (LWP 31905)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 25 (Thread 0x7edaae1ec700 (LWP 24978)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7edaaebed700 (LWP 24966)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7edaa700 (LWP 24523)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7edaaf7fe700 (LWP 17067)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f1ab6af9700 (LWP 8097)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1bd0744665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f1bd0744f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f1bcc9ec6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1bcb8a12e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1bcc2ff54f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f1ab7fff700 (LWP 7880)):
#0  0x7f1bcb8a7756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1bcc9ed58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1b0c9331d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f1b0c9379d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f1b0c932263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f1b0c935249 in ThreadWeaver::Thread::run() 

[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'

[Jens]

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

Jens  changed:

   What|Removed |Added

 CC||jens.wolf@rauschenberg-mfr.
   ||eu

--- Comment #3 from Jens  ---
Same Issue with Kmail 5.2.3

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

[user-manager] [Bug 378604] user-manager doesn't see/recognize users.

[Jerrod Frost]

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

Jerrod Frost  changed:

   What|Removed |Added

 CC||piroisl...@gmail.com

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

[user-manager] [Bug 378604] user-manager doesn't see/recognize users.

[Jerrod Frost]

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

--- Comment #1 from Jerrod Frost  ---
Wasn't sure whether to label normal or major. considering this application's
main purpose is to control user accounts and it cannot do that I figured to set
it to major?

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

[user-manager] [Bug 378604] user-manager doesn't see/recognize users.

[Jerrod Frost]

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

Jerrod Frost  changed:

   What|Removed |Added

   Severity|normal  |major

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

[user-manager] [Bug 378604] New: user-manager doesn't see/recognize users.

[Jerrod Frost]

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

Bug ID: 378604
   Summary: user-manager doesn't see/recognize users.
   Product: user-manager
   Version: 5.9.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: piroisl...@gmail.com
  Target Milestone: ---

user-manager doesn't see my current user!

So I created a new temp user with it. Logged into new temp user. deleted old
user. added user back. Now its visible. log out. delete temp user. decided I
want to change my avatar. change avatar, asks for root password, enter it, then
the user disappeared and I'm back to square one with no users seen by
user-manager.

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

[okular] [Bug 347738] Okular would be amazing if it could also scan to pdf !

[Jerrod Frost]

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

Jerrod Frost  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Jerrod Frost  ---


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

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

[Skanlite] [Bug 299517] Skanlite should support scan to pdf.

[Jerrod Frost]

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

--- Comment #13 from Jerrod Frost  ---
*** Bug 347738 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 378603] Kate freezes when manipulating large text blocks

[Marcell Fulop]

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

--- Comment #3 from Marcell Fulop  ---
System information:

HP EliteDesk, i7 core 6700, 24 GiB RAM

$ uname -a
Linux marekful-HP 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

[kate] [Bug 378603] Kate freezes when manipulating large text blocks

[Marcell Fulop]

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

--- Comment #2 from Marcell Fulop  ---
A seemingly similar problem is reported in the old bug which claims to have
been fixed in KDE version 4.3

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

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

[kate] [Bug 378603] Kate freezes when manipulating large text blocks

[Marcell Fulop]

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

--- Comment #1 from Marcell Fulop  ---
I could not attache a file due to attachment size restrictions but it should
produce the same behaviour with any text file of the specified size.

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

[kate] [Bug 378603] Kate freezes when manipulating large text blocks

[Marcell Fulop]

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

Marcell Fulop  changed:

   What|Removed |Added

 CC||marek...@sziget.hu

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

[kate] [Bug 378603] New: Kate freezes when manipulating large text blocks

[Marcell Fulop]

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

Bug ID: 378603
   Summary: Kate freezes when manipulating large text blocks
   Product: kate
   Version: 16.04.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: marek...@sziget.hu
  Target Milestone: ---

When large text files are opened in Kate, it stops responding on the following
operations:
- Select all - Tools -> Uppercase / Lowercase
- Select 14 lines - File -> New, Edit -> Paste

The system reports the process to be continuously running and using about 100%
CPU and varying amounts of memory but it never completes the operation.

Obviously, I did not wait _forever_ so "never" is not an accurate description
but in previous versions of KDE the exact same or very similar operations
completed within a manner of seconds whereas in this version I had to kill the
process after 10 minutes or so. This happened several times.

Steps to reproduce:
1) Open any text file of size 9 MiB or larger.
2) Select all text.
3) Select the Tools menu and the Lowercase command.

OR

1) Open any text file of size 9 MiB or larger.
2) Select the first 14 lines.
3) Open a new, empty document.
4) In the new document, paste the clipboard content.

Other notes:
The files I am experiencing this behaviour with (have not tried with other
files) do not have long lines. They actually have fixed column width of 32 and
several hundreds of thousand lines.

Attached is one file I could reproduce this bug.

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

[kate] [Bug 193271] kwrite and kate freezes replacing text on big files

[Marcell Fulop]

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

Marcell Fulop  changed:

   What|Removed |Added

 CC||marek...@sziget.hu

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

[plasma-nm] [Bug 378542] Sorting connections

[bugzilla_noreply]

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

fuermetz+...@mailbox.org changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

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

[plasma-nm] [Bug 378542] Sorting connections

[bugzilla_noreply]

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

fuermetz+...@mailbox.org changed:

   What|Removed |Added

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

--- Comment #1 from fuermetz+...@mailbox.org ---
I think this feature request is useless, as I realized now that VPN-connections
are only available, if you are connected to a network!

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

[frameworks-plasma] [Bug 377272] Multiple monitors with different resoltuion UI auto scaling

[bugzilla_noreply]

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

jlj.babydra...@gmail.com changed:

   What|Removed |Added

 CC||jlj.babydra...@gmail.com

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

[plasmashell] [Bug 378318] Cannot activate Global Menu.

[R . T . Sun]

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

--- Comment #8 from R.T. Sun  ---
Hi, sir

I can actually provide a account which reproduce this issue for you to do
remote login.
If you need me to setup remote login tools like teamviewer or anything, please
do not hesitate to contact me.

I really wish I can do something more to help resolve this issue.

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

[LabPlot2] [Bug 378588] Can't build labplot 2.4.0-kf5 on Chakra with Qt 5.8.0 and GCC 5.2.0

[Jeff Huang]

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

--- Comment #2 from Jeff Huang  ---
(In reply to Alexander Semke from comment #1)
> Hi Jeff,
> 
> thanks for reporting this. I cannot reproduce this problem with GCC 5.3.
> This must be a compiler setting and/or how Qt was build. I'll check this.
> 
> As a quick solution, does it help for you if you replace
> updatedKeyword.comment.toLatin1() by
> updatedKeyword.comment.toLatin1().data() in line 1271 and replace
> constData() by data() in line 1339 in FITSFilter.cpp?

It is fixed now! build works fine :D

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

[kmymoney4] [Bug 377368] KMyMoney 4.8 failed to import discover card ofx

[bugzilla_noreply]

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

geo...@wildturkeyranch.net changed:

   What|Removed |Added

 CC||geo...@wildturkeyranch.net

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

[ark] [Bug 378602] New: Ark crashes opening .doc file from inside zip

[bugzilla_noreply]

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

Bug ID: 378602
   Summary: Ark crashes opening .doc file from inside zip
   Product: ark
   Version: 16.12.0
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: ibu...@gmail.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Application: ark (16.12.0)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.13-desktop-2.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
Opened a zip file I downloaded from Gmail with three .doc attachments. When I
try to open one of the files by double-clicking, it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f366f948800 (LWP 21947))]

Thread 3 (Thread 0x7f3662de7700 (LWP 21949)):
#0  0x7f367a6f2f9d in poll () at /lib64/libc.so.6
#1  0x7f3676d2fa54 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3676d2fb5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f367affb95b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f367afa6f9a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f367ade03bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3678dc8615 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f367ade4ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f367746966d in start_thread () at /lib64/libpthread.so.0
#9  0x7f367a6feded in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f366ac3c700 (LWP 21948)):
#0  0x7f367a6f2f9d in poll () at /lib64/libc.so.6
#1  0x7f36747ef902 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f36747f1657 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f366d90eba9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f367ade4ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f367746966d in start_thread () at /lib64/libpthread.so.0
#6  0x7f367a6feded in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f366f948800 (LWP 21947)):
[KCrash Handler]
#6  0x7f365a204e60 in KoPart::document() const () at /lib64/libkomain.so.15
#7  0x7f365a72c204 in OkularOdtGenerator::loadDocument(QString const&,
QVector&) () at /lib64/libkookularGenerator_odt.so.15
#8  0x7f365bd98926 in Okular::Generator::loadDocumentWithPassword(QString
const&, QVector&, QString const&) () at
/lib64/libOkular5Core.so.7
#9  0x7f365bd87c6e in
Okular::DocumentPrivate::openDocumentInternal(KPluginMetaData const&, bool,
QString const&, QByteArray const&, QString const&) () at
/lib64/libOkular5Core.so.7
#10 0x7f365bd880e9 in Okular::Document::openDocument(QString const&, QUrl
const&, QMimeType const&, QString const&) () at /lib64/libOkular5Core.so.7
#11 0x7f36602bc63e in Okular::Part::doOpenFile(QMimeType const&, QString
const&, bool*) () at /usr/lib64/qt5/plugins/okularpart.so
#12 0x7f36602bdb56 in Okular::Part::openFile() () at
/usr/lib64/qt5/plugins/okularpart.so
#13 0x7f367d6a32cd in KParts::ReadOnlyPartPrivate::openLocalFile() () at
/lib64/libKF5Parts.so.5
#14 0x7f367d6a3ff4 in KParts::ReadOnlyPart::openUrl(QUrl const&) () at
/lib64/libKF5Parts.so.5
#15 0x7f36602aff99 in Okular::Part::openUrl(QUrl const&) () at
/usr/lib64/qt5/plugins/okularpart.so
#16 0x7f36619665b0 in ArkViewer::viewInInternalViewer(QString const&,
QMimeType const&) () at /usr/lib64/qt5/plugins/arkpart.so
#17 0x7f3661968357 in ArkViewer::view(QString const&) () at
/usr/lib64/qt5/plugins/arkpart.so
#18 0x7f36619548ae in Ark::Part::slotPreviewExtractedEntry(KJob*) () at
/usr/lib64/qt5/plugins/arkpart.so
#19 0x7f367afd442c in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#20 0x7f367be00732 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#21 0x7f367be01ee1 in KJob::finishJob(bool) () at
/lib64/libKF5CoreAddons.so.5
#22 0x7f367db28082 in Kerfuffle::Job::onFinished(bool) () at
/lib64/libkerfuffle.so.16
#23 0x7f367afd442c in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#24 0x7f367db5f542 in Kerfuffle::ReadOnlyArchiveInterface::finished(bool)
() at /lib64/libkerfuffle.so.16
#25 0x7f367db4d4af in Kerfuffle::CliInterface::extractProcessFinished(int,
QProcess::ExitStatus) () at /lib64/libkerfuffle.so.16
#26 0x7f367afd442c in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#27 0x7f367aee384f in 

[krecipes] [Bug 378600] New Mysql Database missing table

[John Lloyd-Jones]

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

--- Comment #1 from John Lloyd-Jones  ---
Worth mentioning that when I created the recipes tables from the create
statement in the code, I got: Error Code: 1067. Invalid default value for
'mtime'. Needed to add DEFAULT CURRENT_TIMESTAMP for ctime, mtime and atime to
get it to work.

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

[digikam] [Bug 378601] New: Window opens in full screen

[Reginald E . Dudley]

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

Bug ID: 378601
   Summary: Window opens in full screen
   Product: digikam
   Version: 5.5.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: reg77...@comcast.net
  Target Milestone: ---

Digikam opens in full screen and there are no window borders.  Clicking off
full screen and still no window borders, the window occupies the full screen
blocking access to the desktop panel.

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

[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line

[Randall Leeds]

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

Randall Leeds  changed:

   What|Removed |Added

 CC||randall.le...@gmail.com

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

[konsole] [Bug 378124] Character width for HIGH VOLTAGE SIGN possibly wrong

[Randall Leeds]

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

Randall Leeds  changed:

   What|Removed |Added

 CC||randall.le...@gmail.com

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

[konsole] [Bug 272443] *wide* chars in fixed fonts with utf-8

[Randall Leeds]

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

Randall Leeds  changed:

   What|Removed |Added

 CC||randall.le...@gmail.com

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

[konsole] [Bug 361547] Unicode text changes size and moves around when moving cursor

[Randall Leeds]

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

Randall Leeds  changed:

   What|Removed |Added

 CC||randall.le...@gmail.com

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

[krecipes] [Bug 378600] New: New Mysql Database missing table

[John Lloyd-Jones]

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

Bug ID: 378600
   Summary: New Mysql Database missing table
   Product: krecipes
   Version: 2.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krecipes-de...@kde.org
  Reporter: john.lloydjo...@gmail.com
  Target Milestone: ---

When I installed Krecipes for the first time and chose Mysql database, the
table recipes was not created. I had to create this table myself for the
application to work.

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

[krita] [Bug 378599] New: Krita crashes when attempting to duplicate a selection mask

[chuc]

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

Bug ID: 378599
   Summary: Krita crashes when attempting to duplicate a selection
mask
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: sochimi...@gmail.com
  Target Milestone: ---

Krita crashes when attempting to duplicate a selection mask by r clicking on
the mask and selecting duplicate or by clicking on the duplicate layer icon.
Behavior: Window's "program has to close" dialogue appears and the only thing
to do is close the program. 

Windows Event Info
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: krita.exe
  Application Version:  0.0.0.0
  Application Timestamp:
  Fault Module Name:libkritaui.dll
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp:   
  Exception Code:   c005
  Exception Offset: 00049e90
  OS Version:   6.3.9600.2.0.0.256.48
  Locale ID:1033
  Additional Information 1: 975a
  Additional Information 2: 975a1a83755619f414ca1bb237ffea9f
  Additional Information 3: 1a5f
  Additional Information 4: 1a5fb386d0206f4560ec4e5f01a75c37


System 
Manufacturer:  ORIGIN pc  laptop
Processor:  Intel(R) i7-67DOCPU @ 340GHz 340GHz 
Installed memoy (RAM): 16.0 GB 
System type:  Windows 8.1 Pro
64- bit Operating System, x64- based processor 
64- bit Operating System, x64- based processor 
Pen and Touch:  Pen Support 
WACOM tablet Intuos Pro PTH 651/k
 Graphics Card NVIDIA GeForce GTX 970M

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

[tellico] [Bug 375996] Add PEGI ratings for videogames

[Robby Stephenson]

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

Robby Stephenson  changed:

   What|Removed |Added

   Version Fixed In||3.0.3
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/tel
   ||lico/111c0b36b8997c7a1668a1
   ||f8b479f14cc83f4b31

--- Comment #1 from Robby Stephenson  ---
Git commit 111c0b36b8997c7a1668a1f8b479f14cc83f4b31 by Robby Stephenson.
Committed on 09/04/2017 at 22:03.
Pushed by rstephenson into branch 'master'.

Add PEGI rating to GiantBomb results

Rather than adding a new default field for PEGI, I'm choosing to add it
as an optional field for the video game data sources that support it.
Amazon UK does not appear to include PEGI ratings, at the moment, for
example, so it's a bit hit or miss.
FIXED-IN: 3.0.3

M  +4-0ChangeLog
M  +1-0src/fetch/giantbombfetcher.cpp
M  +1-0src/tests/giantbombfetchertest.cpp
M  +1-1src/tests/tellicotest.config
M  +30   -6xslt/giantbomb2tellico.xsl

https://commits.kde.org/tellico/111c0b36b8997c7a1668a1f8b479f14cc83f4b31

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

[kde] [Bug 378598] New: Scaling display affects all monitors

[bugzilla_noreply]

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

Bug ID: 378598
   Summary: Scaling display affects all monitors
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dani_k...@yahoo.com.br
  Target Milestone: ---

I have a 4k 15.6' laptop and an external monitor FHD 22 inches. The problem is
that the laptop screen I need to scale to improve readability due to the
extremely high density of each pixel. Unfortunately the external monitor is
scaled with the same ratio once I do so. Each monitor instead should have a
separate scaling factor to be entered through the Displays application.

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

[frameworks-baloo] [Bug 378597] New: New files are not indexed

[Matthieu Gallien]

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

Bug ID: 378597
   Summary: New files are not indexed
   Product: frameworks-baloo
   Version: 5.28.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: matthieu_gall...@yahoo.fr
  Target Milestone: ---

Sometime, when adding a directory with audio files in a directory included in
the list of directories indexed by Baloo, they are not indexed.
Executing balooctl check fix that.
Using balooctl status show the files inside the directory in the "scheduled"
state.

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Kevin Funk  ---
I'm on it:
  https://phabricator.kde.org/D5379

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

[konversation] [Bug 378596] New: Right click on channel applies to highlighted/focused entry rather than position

[bugzilla_noreply]

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

Bug ID: 378596
   Summary: Right click on channel applies to highlighted/focused
entry rather than position
   Product: konversation
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: jey.and@gmail.com
  Target Milestone: ---

Right click on server applies to highlighted/focused entry rather than
position, while channels that are connecting for example with slack api will
become focused/highlighted.

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

[digikam] [Bug 378591] Selecting Database Configuration Type on first startup crashed application

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #3 from caulier.gil...@gmail.com ---
digiKam as nothing to do with Wayland. It don't know and don't need to know
what's screen manager run in background, especially when you setup database.

In fact we use Qt5 as frontend. This mask the screen manager. This permit to
run under OSX or Windows without any problem.

I suspect a Qt5 compilation problem from the distro. that all. In the
backtrace, only system internal library can be visible. There is nothing from
digiKam side.

Gilles Caulier

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

[krita] [Bug 378595] New: Custom patterns on pattern overlay layer style are lost when saving/reloading

[bugzilla_noreply]

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

Bug ID: 378595
   Summary: Custom patterns on pattern overlay layer style are
lost when saving/reloading
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: layer styles
  Assignee: krita-bugs-n...@kde.org
  Reporter: switchbr...@gmail.com
  Target Milestone: ---

When a file is created with a layer having a pattern overlay using a custom
pattern, on saving and reloading that file the pattern overlay will now be
using an all-black pattern

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

[QtCurve] [Bug 376164] GTK3 Engine

[mva]

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

Vadim A. Misbakh-Soloviov (mva)  changed:

   What|Removed |Added

 CC||k...@mva.name

--- Comment #2 from Vadim A. Misbakh-Soloviov (mva)  ---
(In reply to Yichao Yu from comment #1)
> QtCurve will have a GTK3 port before Oxygen does (and Oxygen-GTK3 doesn't
> work anymore for some GTK versions already AFAICT).

And it is nothing no take from breeze?

It seems, they did some black magic to work with gtk3 (although, I'm not sure
if they already fixed colouring issues, or it still requires re-generation of
gtk3-variant).

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

[digikam] [Bug 378587] Geolocation hangs when opened twice

[Simon]

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

--- Comment #2 from Simon  ---
Actually I did something else that resulted in a freeze as well so I assumed it
is the same: I opened a gpx file, then closed the dialog, and tried to open a
gpx file again. However I can't reproduce the problem with drag 'n dropping
images to the map as you described.

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

[digikam] [Bug 378587] Geolocation hangs when opened twice

[Simon]

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #1 from Simon  ---
Created attachment 104931
  --> https://bugs.kde.org/attachment.cgi?id=104931=edit
Backtrace of geolocation freeze

I can reproduce this with a locally compiled digiKam but not with the Appimage.
The attached backtrace suggest a problem somewhere in libqgtk3/libgdk/libglib
or its configuration. That is at least for my system very sound argument, as
gtk2/3 handling is a bit messy/outdated on xfce.

What system do you use and where do you install digiKam from?

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

[digikam] [Bug 378591] Selecting Database Configuration Type on first startup crashed application

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #2 from Antonio Rojas  ---
This is crashing on Wayland, the fact that it works on X11 is completely
irrelevant. If digikam doesn't support Wayland, just close it as wontfix, and
please announce it on the release notes so that distros are aware of it. If it
does support Wayland, then this shouldn't be dismissed just because it works on
X11

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

[krita] [Bug 378594] The shortcut "V" crashes Krita.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Boudewijn Rempt  ---
That was fixed in 3.1.3 beta 1.

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

[krita] [Bug 378594] New: The shortcut "V" crashes Krita.

[Bouss]

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

Bug ID: 378594
   Summary: The shortcut "V" crashes Krita.
   Product: krita
   Version: 3.1.3-alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sylv1boussi...@gmail.com
  Target Milestone: ---

The shortcut "V" to draw straight lines, crashes Krita immediately with or
without openGL.

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

[krusader] [Bug 378593] New: Problems copying the names of files with apostrophes

[Toni Asensi Esteve]

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

Bug ID: 378593
   Summary: Problems copying the names of files with apostrophes
   Product: krusader
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: toni.ase...@kdemail.net
  Target Milestone: ---

Hi!

If you are using an embedded terminal, and in the active panel you press
Ctrl+Enter when you have a file with an apostrophe, for example:
d'a.pdf
then in the embedded terminal you get copied
"d'a.pdf'
but it isn't right, it should be
"d'a.pdf"
as Krusader 2.4.0-beta3 does.

Thanks for Krusader!

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

[umbrello] [Bug 349622] Display "documentation" in Umbrello's class diagrams

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

Summary|Display "documentation" in  |Display "documentation" in
   |Umbrello's diagrams |Umbrello's class diagrams

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

[umbrello] [Bug 374845] Add support for importing sequence diagram entries from file or clipboard

[Ralf Habacker]

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

--- Comment #3 from Ralf Habacker  ---
Git commit 89e79b8db35dd019c6399440b36df73838911826 by Ralf Habacker.
Committed on 09/04/2017 at 17:56.
Pushed by habacker into branch 'Applications/17.04'.

Fix crash on importing empty lines.

M  +3-2umbrello/diagram_utils.cpp

https://commits.kde.org/umbrello/89e79b8db35dd019c6399440b36df73838911826

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

[umbrello] [Bug 374845] Add support for importing sequence diagram entries from file or clipboard

[Ralf Habacker]

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

--- Comment #2 from Ralf Habacker  ---
Git commit 3674ad28b6cee16088cfdcc0a188accb1c6cd074 by Ralf Habacker.
Committed on 09/04/2017 at 17:56.
Pushed by habacker into branch 'Applications/17.04'.

Fix crash on importing empty lines.

M  +3-2umbrello/diagram_utils.cpp

https://commits.kde.org/umbrello/3674ad28b6cee16088cfdcc0a188accb1c6cd074

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

[kmail2] [Bug 377678] KMail header not showing attachment

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||17.04
  Latest Commit||https://commits.kde.org/mes
   ||sagelib/37b992574c9c36e65fa
   ||38d241459b856900fe413
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from David Faure  ---
Git commit 37b992574c9c36e65fa38d241459b856900fe413 by David Faure.
Committed on 09/04/2017 at 17:46.
Pushed by dfaure into branch 'Applications/17.04'.

Rework timing of script injection for showing attachments in message viewer.

It was sometimes executed too early, before the script that defines qt.jQuery.
FIXED-IN: 17.04

M  +11   -8messageviewer/src/viewer/viewer_p.cpp
M  +17   -10   messageviewer/src/viewer/webengine/mailwebenginescript.cpp
M  +0-9messageviewer/src/viewer/webengine/mailwebengineview.cpp
M  +0-1messageviewer/src/viewer/webengine/mailwebengineview.h
M  +2-2   
messageviewer/src/viewer/webengine/tests/testjquerysupportmailwebengine.js
M  +1-1webengineviewer/src/webenginepage.cpp
M  +1-3webengineviewer/src/webengineview.cpp

https://commits.kde.org/messagelib/37b992574c9c36e65fa38d241459b856900fe413

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

[kmail2] [Bug 377499] Find Messages not working unless Last Search folder deleted

[John White]

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

--- Comment #7 from John White  ---
Thank you!

Do you have any clue when Debian is going to upload the kde fix?

John

On 04/08/2017 03:19 PM, Sandro Knauß wrote:
> https://bugs.kde.org/show_bug.cgi?id=377499
>
> --- Comment #6 from Sandro Knauß  ---
> As this bug report is closed and and also the duplicate is now have been 
> solved
> it is part of Debian to backport the patch.
>

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

[plasmashell] [Bug 373705] Allow different panel configuration for activities

[Nicolas Werner]

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

Nicolas Werner  changed:

   What|Removed |Added

 CC||nicolas.wer...@ymail.com

--- Comment #3 from Nicolas Werner  ---
(In reply to David Edmundson from comment #1)
> Thanks for the comment
> 
> > or the favorite programs on application menu can be quite different for 
> > workflows, which is not possible at the moment.
> 
> This now exists in 5.9, integrated into the launcher itself.
> If you have any other specific ideas of activity specific configurations
> within an applet, we can look into that on a case-by-case basis.
> 
> Having completely different panel configurations I think would just be too
> complicated to show in the UI, and involve the user doing a lot of duplicate
> reconfiguring for global actions that exist above activities.

I agree, that configuration would be harder, so there is a case to be made,
that by default panels are synced between activities.
Still, there are cases, where you want completely different layouts of your
panels between activities. If you have a separate activity for drawing, you may
want to have a unity like task switcher on the side of your desktop. This would
require a bigger panel on a different edge of the screen. While programming
this may be wasted space, so you'd switch to a standard windows-like layout.
Maybe you'd even want to set the task switcher to autohide, which would be
annoying to activate with a graphics tablet, but with a mouse it is much
easier.
This can't be done with an automatic transition based on input devices present
like with a virtual keyboard as I don't usually disconnect my graphics tablet
when I'm not using it. The panel layout I need simply depends on the activity
I'm doing.
There are also other possible use cases. You may not want to see notifications
as well as the current time when you are studying. You may want a different
application launcher when you are playing games and you may want to have your
panels on different screens while editing a video.

Configuring your activities like that may be some work, but at the same time
activities would provide much more value as you could tailor each activity to
exactly one workflow instead of having to compromise.

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

[plasma-nm] [Bug 378592] New: SoftEther VPN Support

[Isaac]

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

Bug ID: 378592
   Summary: SoftEther VPN Support
   Product: plasma-nm
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: isaacalich8...@gmail.com
  Target Milestone: ---

Can we have SoftEther VPN support? I know it's a bit redundant since it's a
multi-protocol server, but having something that can easily get through a
firewall would be really nice. The website for it is here:
http://softether.org/

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

[kdenlive] [Bug 378469] 17.04 - Crash on Exit

[Jean-Baptiste Mardelle]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Thanks for your report. This was fixed in a recent MLT commit:
https://github.com/mltframework/mlt/commit/a3188e301b5a9a1f25dbb98a510e366363348e64

Using MLT from git or the next MLT version to be released will solve the crash

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

[digikam] [Bug 378591] Selecting Database Configuration Type on first startup crashed application

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |setup

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

[digikam] [Bug 378591] Selecting Database Configuration Type on first startup crashed application

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Look like it crash in wayland plugin from Qt5 :

Thread 1 (Thread 0x7f044cefddc0 (LWP 30898)):
[KCrash Handler]
#6  0x7f040fd54df7 in  () at /usr/lib/libwayland-client.so.0

There is nothing wrong from digiKam side here. All work fine here with a fresh 
X11 installation of digiKam in these conditions.

Sound like an Arch packaging problem. Please report it to your distro team...

Gilles Caulier

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

[digikam] [Bug 378591] New: Selecting Database Configuration Type on first startup crashed application

[Espen Fossen]

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

Bug ID: 378591
   Summary: Selecting Database Configuration Type on first startup
crashed application
   Product: digikam
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: espe...@junta.no
  Target Milestone: ---

Application: digikam (5.5.0)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-1-macbook x86_64
Distribution (Platform): Archlinux Packages

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

First start of digiKam and on the Database Configuration screen I try to click
the Type dialog, where SQlite is select, and the application just crashes. Last
log was:

digikam.general: Testing  "mysql_install_db" ...
digikam.general: Found  "mysql_install_db"
digikam.general: Testing  "mysqld" ...
digikam.general: Found  "mysqld"
sock_file=/run/user/1000/kdeinit5__1
[1]   Segmentation fault  (core dumped) digikam

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f044cefddc0 (LWP 30898))]

Thread 2 (Thread 0x7f040abd4700 (LWP 30899)):
#0  0x7f044839967d in poll () at /usr/lib/libc.so.6
#1  0x7f043c65b7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f043c65b8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f04492d706b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f044928089a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f04490a2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f0443221125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f04490a76d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f0442ff42e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f04483a354f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f044cefddc0 (LWP 30898)):
[KCrash Handler]
#6  0x7f040fd54df7 in  () at /usr/lib/libwayland-client.so.0
#7  0x7f040fd553c8 in  () at /usr/lib/libwayland-client.so.0
#8  0x7f040fd532cd in wl_proxy_marshal () at
/usr/lib/libwayland-client.so.0
#9  0x7f0449f97f06 in QWidgetPrivate::raise_sys() () at
/usr/lib/libQt5Widgets.so.5
#10 0x7f0449fa1c38 in QWidget::raise() () at /usr/lib/libQt5Widgets.so.5
#11 0x7f0449fa8a80 in QWidgetPrivate::show_helper() () at
/usr/lib/libQt5Widgets.so.5
#12 0x7f0449fab6d5 in QWidget::setVisible(bool) () at
/usr/lib/libQt5Widgets.so.5
#13 0x7f044a06aef8 in QComboBox::showPopup() () at
/usr/lib/libQt5Widgets.so.5
#14 0x7f044a06b555 in  () at /usr/lib/libQt5Widgets.so.5
#15 0x7f0449fac64f in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#16 0x7f044a067676 in QComboBox::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#17 0x7f0449f6434c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#18 0x7f0449f6c8c5 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#19 0x7f0449282440 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#20 0x7f0449f6b0cd in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib/libQt5Widgets.so.5
#21 0x7f0449fc63e6 in  () at /usr/lib/libQt5Widgets.so.5
#22 0x7f0449fc8e03 in  () at /usr/lib/libQt5Widgets.so.5
#23 0x7f0449f6434c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#24 0x7f0449f6bb61 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#25 0x7f0449282440 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#26 0x7f04497cfd53 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib/libQt5Gui.so.5
#27 0x7f04497d18c5 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib/libQt5Gui.so.5
#28 0x7f04497ad44b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#29 0x7f040ffe7d00 in  () at /usr/lib/libQt5WaylandClient.so.5
#30 0x7f043c65b5a7 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#31 0x7f043c65b810 in  () at /usr/lib/libglib-2.0.so.0
#32 0x7f043c65b8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#33 0x7f04492d704f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#34 0x7f044928089a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#35 0x7f044a152917 in QDialog::exec() () at 

[LabPlot2] [Bug 378588] Can't build labplot 2.4.0-kf5 on Chakra with Qt 5.8.0 and GCC 5.2.0

[Alexander Semke]

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

--- Comment #1 from Alexander Semke  ---
Hi Jeff,

thanks for reporting this. I cannot reproduce this problem with GCC 5.3. This
must be a compiler setting and/or how Qt was build. I'll check this.

As a quick solution, does it help for you if you replace
updatedKeyword.comment.toLatin1() by updatedKeyword.comment.toLatin1().data()
in line 1271 and replace constData() by data() in line 1339 in FITSFilter.cpp?

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

[kdevelop] [Bug 378312] Can't change the "Page size" to custom in "Print Preview"

[Friedrich W . H . Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||kosse...@kde.org
 Resolution|--- |UPSTREAM

--- Comment #1 from Friedrich W. H. Kossebau  ---
Can confirm the issue. The print preview dialog though is from the Qt5
libraries, and this bug can be seen with other instances, e.g. in Qt Assistant
(Qt 5.7.1 here).

Please check and report this with Qt at https://bugreports.qt.io (could not
find a related bug report on a quick check).

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

[kwin] [Bug 375000] Meta-to-open-menu stops working quickly after reboot on specific keyboard model

[Bartek]

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

Bartek  changed:

   What|Removed |Added

 CC||bp1...@gmail.com

--- Comment #11 from Bartek  ---
I have a similar issue, Meta key stops working some time after booting, but I
have a different keyboard (CM Storm QuickFire Ultimate), and I don't use
Alt-Tab. Could this be related?

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

[ark] [Bug 378507] [unar] ark doesn't prompt for password when trying to open a password protected entry

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||17.04.0
  Latest Commit||https://commits.kde.org/ark
   ||/b80d2e5cd2d0c12a9221720834
   ||10e8b4bcd6130a
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Elvis Angelaccio  ---
Git commit b80d2e5cd2d0c12a922172083410e8b4bcd6130a by Elvis Angelaccio.
Committed on 09/04/2017 at 15:37.
Pushed by elvisangelaccio into branch 'Applications/17.04'.

Fix extraction of encrypted entries with the unar plugin

The `passwordSwitch` property is a QStringList and not a QString.
Thus converting from QVariant to QString breaks as soon as the list
contains more than one string, which is the case with the unar plugin.
FIXED-IN: 17.04.0

Differential Revision: D5336

M  +1-1kerfuffle/cliinterface.cpp

https://commits.kde.org/ark/b80d2e5cd2d0c12a922172083410e8b4bcd6130a

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

[Plasma Workspace Wallpapers] [Bug 378590] plasmashell crash by wallpaper?

[rооt]

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

rооt  changed:

   What|Removed |Added

Product|kde |Plasma Workspace Wallpapers
   Platform|unspecified |Ubuntu Packages
 CC||cerebel...@ukr.net
  Component|general |general

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

[kde] [Bug 378590] New: plasmashell crash by wallpaper?

[rооt]

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

Bug ID: 378590
   Summary: plasmashell crash by wallpaper?
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: cerebel...@ukr.net
  Target Milestone: ---

Application: plasmashell (5.9.90)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.10.0-19-generic x86_64
Distribution: Ubuntu Zesty Zapus (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Configure Desktop -> Wallpaper -> Wallpaper Type -> Picture of the Day ->
Providers -> Bingʼs Picture of the Day --> plasmashell crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5d023b8440 (LWP 1613))]

Thread 9 (Thread 0x7f5c4d0a4700 (LWP 1622)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5cd7156b23 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f5cd7156987 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f5cfb51a6da in start_thread (arg=0x7f5c4d0a4700) at
pthread_create.c:456
#4  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f5cd4dbc700 (LWP 1621)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5cd7156b23 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f5cd7156987 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f5cfb51a6da in start_thread (arg=0x7f5cd4dbc700) at
pthread_create.c:456
#4  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f5cd55bd700 (LWP 1620)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5cd7156b23 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f5cd7156987 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f5cfb51a6da in start_thread (arg=0x7f5cd55bd700) at
pthread_create.c:456
#4  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f5cd5dbe700 (LWP 1619)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5cd7156b23 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f5cd7156987 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f5cfb51a6da in start_thread (arg=0x7f5cd5dbe700) at
pthread_create.c:456
#4  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f5cd7fff700 (LWP 1618)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5d01d252c4 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f5d01e0ef20 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f5d01d25309 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f5cfb51a6da in start_thread (arg=0x7f5cd7fff700) at
pthread_create.c:456
#4  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f5cde38d700 (LWP 1617)):
#0  0x7f5cfbf7818d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5cf6bbe576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5cf6bbe68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5cfc89bf2b in QEventDispatcherGlib::processEvents
(this=0x7f5cd8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5cfc84588a in QEventLoop::exec (this=this@entry=0x7f5cde38cca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5cfc672fe3 in QThread::exec (this=this@entry=0x557cee2cadb0) at
thread/qthread.cpp:507
#6  0x7f5cff539df5 in QQmlThreadPrivate::run (this=0x557cee2cadb0) at
qml/ftw/qqmlthread.cpp:147
#7  0x7f5cfc677c98 in QThreadPrivate::start (arg=0x557cee2cadb0) at
thread/qthread_unix.cpp:368
#8  0x7f5cfb51a6da in start_thread (arg=0x7f5cde38d700) at
pthread_create.c:456
#9  0x7f5cfbf8417f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f5cd700 (LWP 1616)):
#0  0x7f5cfbf7818d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5cf6bbe576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5cf6bbe68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  

[konsole] [Bug 378523] Bold fonts not displaying when proper settings checked

[Mike Lui]

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

Mike Lui  changed:

   What|Removed |Added

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

--- Comment #2 from Mike Lui  ---
This ended up being an issue with settings in .config/kdeglobalsrc.

I deleted all the font settings there and this fixed the issue.

See:

https://forum.qt.io/topic/78036/bold-fonts-not-working-for-many-fixed-width-fonts-in-linux

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

[kexi] [Bug 378559] changing between design and view creates a crash

[Albrecht Will]

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

--- Comment #2 from Albrecht Will  ---
the db contains pictures and has 100 MB. I send Jaroslaw a download-link

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

[systemsettings] [Bug 378589] New: System settings crashes in Display and Monitor

[Joe Roets]

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

Bug ID: 378589
   Summary: System settings crashes in Display and Monitor
   Product: systemsettings
   Version: 5.7.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: j...@createtank.com
  Target Milestone: ---

Application: systemsettings5 (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-46-generic x86_64
Distribution: Ubuntu 16.10

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

When opening Display and Monitor dialog application crashes after ~2 seconds.

I had just turned on the NVIDIA driver.
Fairly new system and driver dialog was displayed to turn it on.
No reboot was requested/required.

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7febe7b72700 (LWP 18291)):
#0  0x7fec0eb0a029 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fec0eac48d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fec0eac4aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fec127154ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fec126bd0fa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fec124e2d43 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fec10e3ec65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fec124e7c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fec0efe86ca in start_thread (arg=0x7febe7b72700) at
pthread_create.c:333
#9  0x7fec11df30af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7febf99e4700 (LWP 18279)):
#0  0x7fec11de70bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fec0eac49d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fec0eac4aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fec127154ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fec126bd0fa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fec124e2d43 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fec15898575 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fec124e7c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fec0efe86ca in start_thread (arg=0x7febf99e4700) at
pthread_create.c:333
#9  0x7fec11df30af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fec02199700 (LWP 18278)):
#0  0x7fec11de70bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fec0f85fc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fec0f8618d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fec04d23299 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fec124e7c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fec0efe86ca in start_thread (arg=0x7fec02199700) at
pthread_create.c:333
#6  0x7fec11df30af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fec157438c0 (LWP 18276)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7fec11d223ea in __GI_abort () at abort.c:89
#8  0x7fec124cecc1 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fec110d9a13 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7fec110e1b82 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7fec110e1f63 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fec13618f65 in QWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7fec5a13 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7fec13bf58ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fec13bfad4f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fec126bf3b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fec1360e29d in

[LabPlot2] [Bug 378588] New: Can't build labplot 2.4.0-kf5 on Chakra with Qt 5.8.0 and GCC 5.2.0

[Jeff Huang]

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

Bug ID: 378588
   Summary: Can't build labplot 2.4.0-kf5 on Chakra with Qt 5.8.0
and GCC 5.2.0
   Product: LabPlot2
   Version: Frameworks
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.se...@web.de
  Reporter: s8321...@gmail.com
  Target Milestone: ---

Created attachment 104930
  --> https://bugs.kde.org/attachment.cgi?id=104930=edit
build failed log

I got error message in build.log when I'm building labplot-kf5 2.4.0 on Chakra.

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

[plasmashell] [Bug 377055] some icons cannot be pinned to panel on wayland

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

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

[kmail2] [Bug 344099] KMail composer changes HTML format when replying to HTML mail

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #1 from David Faure  ---
"why are there so many line brakes in the text/plain version of the email"
should finally be fixed with https://codereview.qt-project.org/191229

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Rick Graves]

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

--- Comment #6 from Rick Graves  ---
How does one activate highlighting? 

I am mostly using the default configuration.  For kate, I set the line length
limit to zero and I use spaces not tabs.

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

[digikam] [Bug 378587] Geolocation hangs when opened twice

[Sander]

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

Sander  changed:

   What|Removed |Added

 CC||b...@sanderdekievit.nl

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

[digikam] [Bug 378587] New: Geolocation hangs when opened twice

[Sander]

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

Bug ID: 378587
   Summary: Geolocation hangs when opened twice
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation-Editor
  Assignee: digikam-de...@kde.org
  Reporter: b...@sanderdekievit.nl
  Target Milestone: ---

Steps to reproduce:
1. Open Geolocation. Geotag (drag 'n drop) one image on the map.
2. Click Apply and close geolocation screen
3. Open Geolocation again.
4. Drag a picture to the map -> mouse cursor changes to 'forbidden to change'
and digikam becomes unresponsive

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Rick Graves]

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

--- Comment #5 from Rick Graves  ---
The Thinkpad T500 uses the ATI Mobility Radeon HD 3650  display adapter
(http://www.thinkwiki.org/wiki/Category:T500).  I have the same problem with
kate and kwrite on my home desktop, which has a dual core Athlon II CPU and 16
GB of memory, on which kinfocenter says the display adapter is NVIDIA GT218
[GeForce 210].

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

[krita] [Bug 378586] New: Zooming with Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

Bug ID: 378586
   Summary: Zooming with Two-finger-scrolling is too sensitive
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Version: 3.1.2
When I zoom in and out of an image using Two-finger-scrolling on the touchpad,
this goes way too fast/much too sensitive, so it is almost impossible to get to
a desired magnification.

Please have a look at https://bugs.kde.org/show_bug.cgi?id=377128 as this one
seems to be almost the same problem.

(I reported a similar problem for gwenview:
https://bugs.kde.org/show_bug.cgi?id=378584)

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Rick Graves]

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

--- Comment #4 from Rick Graves  ---
Created attachment 104929
  --> https://bugs.kde.org/attachment.cgi?id=104929=edit
Thinkpad T500 with kubuntu drives for 14.04 & 16.04

One laptop, two hard drives, 1) kubuntu 14.04 & 2) kubuntu 16.04.

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

[plasmashell] [Bug 378585] Old icons appear when toggling compositing on/off

[Artur O .]

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

--- Comment #1 from Artur O.  ---
Doing; 
kquitapp5 plasmashell
plasmashell &>/dev/null &

will fix this temporary only to be triggered later on.

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #1 from Thomas Mitterfellner  ---
I forgot: this is for version 16.08.2, KDE Frameworks 5.32.0, Qt 5.8.0 (built
against 5.8.0), the xcb windowing system

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

[plasmashell] [Bug 378585] New: Old icons appear when toggling compositing on/off

[Artur O .]

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

Bug ID: 378585
   Summary: Old icons appear when toggling compositing on/off
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: commander.alch...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

When toggling kwin compositing on/off using the hotkeys it seems that the
plasmashell stops rendering and everything is stuck at "that" time; Icons, tray
icons, icon-only taskmanager even the digital clock on the panel and widgets on
desktop are affected.

Here are two screenshots from the exact same time, however on one it seems that
it was taken several hours ago; 

Compositing on: http://i.imgur.com/xqUTxo1.png
Compositing off: http://i.imgur.com/nRqPRtE.png

I've experianced this for quite some time now, think i mentioned it in
https://bugs.kde.org/show_bug.cgi?id=361154

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

[gwenview] [Bug 378584] New: Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

Bug ID: 378584
   Summary: Zooming with CTRL+Two-finger-scrolling is too
sensitive
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
CC: myr...@kde.org
  Target Milestone: ---

When I zoom in and out of an image using CTRL+Two-finger-scrolling on the
touchpad, this goes way too fast/much too sensitive, so it is almost impossible
to get to a desired magnification.

Please have a look at https://bugs.kde.org/show_bug.cgi?id=377128 as this one
seems to be almost the same problem.

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Rick Graves]

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

--- Comment #3 from Rick Graves  ---
Bug 378330 seems to be related, but that one is only about the paste delay. I
use kate for small files (python scripts) and have no problem pasting into
small files.

If my only problem was the paste delay, I would live with it and I would never
have complained. For me, the much bigger aggravation is the arrow keys do not
work with keyboard repeat in 16.04 and 16.10, kate version 5/15 (kate says
version 15, kwrite says kate version 5).

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

[Touchpad-KCM] [Bug 378583] New: Touchpad settings do not have an effect on qt applications

[Thomas Mitterfellner]

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

Bug ID: 378583
   Summary: Touchpad settings do not have an effect on qt
applications
   Product: Touchpad-KCM
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasma-applet
  Assignee: rajeeshknamb...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

This affects version 5.9.4 (I cannot select this as versions numbers are only
available up to 5.5.5).

When I change the touchpad two-finger scrolling distance setting in the
configuration dialog, hit Apply and test the settings in the Testing area, they
do not seem to have any effect (same for settings like Reverse scrolling).
However, the values are written correctly to touchpadrc and I can see the
effect of the setting immediately when I test it in Firefox or a qt Application
like Scribus. Only after I close the System Settings and open them again, the
changed settings do show an effect.

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

[kde] [Bug 378582] New: Baloon Notification Tool crashed when finishing download

[Ralf Grauer]

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

Bug ID: 378582
   Summary: Baloon Notification Tool crashed when finishing
download
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ralf.gra...@canior.de
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.8.0-46-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
My Browser has finished a download of file. 
Then opens a dialog immediatly to notificate the crash of the notification
program.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9b4429d8c0 (LWP 1499))]

Thread 2 (Thread 0x7f99f901b700 (LWP 2762)):
[KCrash Handler]
#6  __memcpy_avx_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:163
#7  0x7f9b4348c8da in Baloo::PostingCodec::decode(QByteArray const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x7f9b43478814 in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7f9b434893c6 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x7f9b43481032 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x0041c8e0 in Baloo::NewFileIndexer::run() ()
#12 0x7f9b42d9f2d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f9b42da27be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f9b41a066ba in start_thread (arg=0x7f99f901b700) at
pthread_create.c:333
#15 0x7f9b423af82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9b4429d8c0 (LWP 1499)):
#0  0x7f9b4239f69d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9b3f5b76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9b3f573e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9b3f574330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9b3f57449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9b42fd97cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9b42f80b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9b42f88bec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x0041698c in main ()

Reported using DrKonqi

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

[plasmashell] [Bug 378581] New: gui restarted while deleting file

[bugzilla_noreply]

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

Bug ID: 378581
   Summary: gui restarted while deleting file
   Product: plasmashell
   Version: 5.8.6
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: yahyagu...@protonmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.57-18.3-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed: deleting a file from desktop.
-It happened just a little time after I rebooted the pc. There was no other
specific application running on foreground or background. I just was deleting
an .rpm file from the desktop.

The crash does not seem to be reproducible.

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

Thread 16 (Thread 0x7f5e817e9700 (LWP 1831)):
#0  0x7f5f51686ff7 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#1  0x7f5f516880fe in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f5f4d44295d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5f4d443230 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f5f4d44342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f5f5168832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f5f51635fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f5f51470f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f5e82c118f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#9  0x7f5f514759e9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#11 0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f5e94d90700 (LWP 1817)):
#0  0x7f5f4d4406d0 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5f4d4428fb in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5f4d443230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f5f4d44342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5f5168832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f5f51635fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5f51470f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f5f55300632 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f5f514759e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f5e9e13d700 (LWP 1816)):
#0  0x7f5f505890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5f30a2a413 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f5f30a29f87 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f5e9e93e700 (LWP 1815)):
#0  0x7f5f505890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5f30a2a413 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f5f30a29f87 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f5e9f13f700 (LWP 1814)):
#0  0x7f5f505890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5f30a2a413 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f5f30a29f87 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f5e9f940700 (LWP 1813)):
#0  0x7f5f505890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5f30a2a413 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f5f30a29f87 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f5ea0141700 (LWP 1812)):
#0  0x7f5f505890bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5f30a2a413 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f5f30a29f87 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f5f50584744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5f50d83d3d in clone () at /lib64/libc.so.6

Thread 9 

[neon] [Bug 378368] Kmail/Kontact crash due to missing symbol

[Bogdan Mihaila]

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

--- Comment #6 from Bogdan Mihaila  ---
OK, managed to get KMail + imap working again by downgrading all of KDE PIM to
a previous known good version. However, that meant downgrading a whooping
amount of 198 packages to a mix of different previous versions! This might or
might not work on someone else's system. It might just put your system in a
broken package state that needs manual fixing afterwards. If someone still
wants to try the downgrading PIM hack please comment and I can provide the
package list here.

However, the better way to deal with this is to have someone from Neon fix the
latest KDE PIM packaging to not have the missing symbols anymore. Not sure
though how long that takes.
I will wait with any system upgrades for a while to not break mail+calendar
again.

Bye
Bogdan

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Dominik Haumann]

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

--- Comment #2 from Dominik Haumann  ---
Just tested this: For me, following your instructions, Kate reacts snappy
without any delays, so I cannot reproduce. And if we cannot reproduce we cannot
do anything about it.

Do you have any highlighting activated?

What graphics card do you have? Could you google for this driver and kate,
whether you find other users that also have this issue?

How fast is your CPU?

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

[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Dominik Haumann]

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

--- Comment #1 from Dominik Haumann  ---
I have not yet tested this here locally, but I once heard that the graphics
driver may cause very slow behavior. It is unlikely you hit this, but still
this may be one reason. Besides that, Kate 3 uses Qt4, and Kate 5 uses Qt 5 -
so also the underlying Qt stack may cause this. This needs to be profiled.

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

[digikam] [Bug 376470] Title is not refreshed when read again metadata from file is launched [patch]

[domian . h]

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

--- Comment #5 from domian.h  ---
Thank you! Works great.

It is possible to include the subfolders of an album to the function Ablum ->
Reread Metadata from Images?

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

[pimsettingexporter] [Bug 378578] exporting all from KMail does not export filters

[Martin Koller]

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

--- Comment #2 from Martin Koller  ---
I tested this now again with:
Version 5.4.80 beta1 (my main working pc)
Version 5.5.40 alpha1 (test pc)

same result on both.
With my main working pc I have ~50 filters, on the test pc I created just one
single filter.

I export everything from "KMail" but without the Mails themselves.

Don't know if relevant: main pc has local mails in maildir, uses 2 POP3
accounts, 1 airsync account
Test PC has only local mails in maildir and one mbox

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

[digikam] [Bug 351433] pto2mk not found with Hugin 2015.0

[luca . bs]

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

luca...@gmail.com  changed:

   What|Removed |Added

 CC||luca...@gmail.com

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

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #10 from mathoj...@gmail.com ---
Hello,

Just wondering... Why is this bug still in "UNCONFIRMED" Status ?? The bug has
been reported here many times, and on duplicates as well...

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

[kontact] [Bug 378580] New: kontact kmail crash after delete

[jetojedno]

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

Bug ID: 378580
   Summary: kontact kmail crash after delete
   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: ad...@different-perspectives.com
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.57-18.3-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
logged off and back on after installing latest update of kontact / kpim &
akonadi.  Started knotact & in kmail viewed local mail & deleted (not move to
trash) item.  Switched to "normal" pop3 mailbox to start deleting unwanted
mail.  Crash

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

Thread 31 (Thread 0x7ff348c2f700 (LWP 30073)):
#0  0x7ff3785867b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff378544969 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff378545230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff37854542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff37dd6832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7ff37dd15fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7ff37db50f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7ff37db559e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff379182744 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff37d24cd3d in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7ff349430700 (LWP 30070)):
#0  0x7ff3785867d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff3785449e8 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff378545230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff37854542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff37dd6832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7ff37dd15fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7ff37db50f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7ff37db559e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff379182744 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff37d24cd3d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7ff2a2f9d700 (LWP 29857)):
#0  0x7ff3791870bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff370822ce9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7ff3708234ad in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7ff370823cd0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7ff370820a2e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7ff379182744 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff37d24cd3d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7ff2a3b40700 (LWP 29844)):
#0  0x7ff37d24449d in poll () at /lib64/libc.so.6
#1  0x7ff378545314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff37854542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff37dd6832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff37dd15fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff37db50f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff37db559e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff379182744 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff37d24cd3d in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7ff2a4341700 (LWP 29842)):
#0  0x7ff378544ce4 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#1  0x7ff3785452a8 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff37854542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff37dd6832b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff37dd15fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff37db50f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff37db559e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff379182744 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff37d24cd3d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7ff2a775b700 (LWP 29836)):
#0  0x7ff378542679 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff3785448fb in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff378545230 in  () at /usr/lib64/libglib-2.0.so.0
#3  

[neon] [Bug 378368] Kmail/Kontact crash due to missing symbol

[Bogdan Mihaila]

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

--- Comment #5 from Bogdan Mihaila  ---
Seems that the downgrade workaround mentioned in the previous post is enough to
make Kmail start without crashing but there are still missing symbols in other
PIM libraries which means KMail is unusable :(.

In particular Imap seems to not work anymore due to this
/usr/bin/akonadi_imap_resource: symbol lookup error:
/usr/bin/akonadi_imap_resource: undefined symbol:
_ZN13MailTransport10ServerTest8finishedERK5QListIiE
/usr/bin/akonadi_maildispatcher_agent: symbol lookup error:
/usr/bin/akonadi_maildispatcher_agent: undefined symbol:
_ZTIN13MailTransport22SentBehaviourAttributeE

Trying to downgrade the libkf5mailtransport5 package in the hope to fix the
above leads to a dpkg dependency blocker - not possible.
So currently Imap is non-functional in Kmail - no emails again :(.

I'll see how to downgrade the whole KDE PIM to the last known usable version
but this means downgrading 40+ packages, which will be a challenge for the
package manager.

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

[neon] [Bug 378368] Kmail/Kontact crash due to missing symbol

[Bogdan Mihaila]

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

--- Comment #4 from Bogdan Mihaila  ---
@idoitprone I can confirm the new woes after updating today. Kmail/Kontact
crashes again on startup due to a missing symbol.
Did some investigation on the new missing symbols and here is how to fix those
temporarily by downgrading packages. 

kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkmailprivate.so.5:
undefined symbol:
_ZN10MailCommon24FavoriteCollectionWidget19prefereCreateNewTabEb

can be fixed by downgrading libkf5mailcommon5 to
sudo apt install libkf5mailcommon5=4:16.12.3+p16.04+git20170310.0437-0

then one will run into another missing symbol:
kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkmailprivate.so.5:
undefined symbol:
_ZN4KPIM15ProgressManager18createProgressItemEPNS_12ProgressItemERKN7Akonadi13AgentInstanceERK7QStringS9_S9_bNS1_12CryptoStatusE

can be fixed by downgrading libkf5libkdepim5 to
sudo apt install libkf5libkdepim5=4:16.12.3+p16.04+git20170310.0145-0

then one will run into another missing symbol:
kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkmailprivate.so.5:
undefined symbol: _ZN9PimCommon4Util12isImapFolderERKN7Akonadi10CollectionERb

can be fixed by downgrading libkf5pimcommon5 to
sudo apt install libkf5pimcommon5=4:16.12.3+p16.04+git20170310.0207-0

and now finally the hunt ends and Kmail starts again without crashing.

It seems though that the missing symbol from my initial post #1 is fixed but
now we got 3 new missing ones instead. Guess there is some refactoring going on
in KDEPIM and Neon builds do not manage to build from the right versions of the
libraries so that symbols are missing each time. As hunting those down manually
and downgrading libraries without version conflicts and blockers is getting
tedious and might not work with next upgrade I highly recommend to not upgrade
any KDEPIM related libraries until this gets to a stable state. Otherwise KMail
and others will be non-functional with the next upgrade and who knows how long
it takes for it to get fixed. Not having emails and calendar for weeks doesn't
seem tempting.

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

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||markusmitsc...@gmail.com

--- Comment #9 from Elvis Angelaccio  ---
*** Bug 378563 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 378563] Permissions not right

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---


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

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

[plasmashell] [Bug 378416] Screen dark and plasma crash when laptop docked

[Sasasu]

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

Sasasu  changed:

   What|Removed |Added

 CC||lizhaolong0...@gmail.com

--- Comment #1 from Sasasu  ---
Application: plasmashell (5.9.4)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.9-1-ck-skylake x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I docked the laptop ,then two screen come back,but ervrything fine after five
seconds, I noticed  plasma had crashed

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f993bfff700 (LWP 838)):
#0  0x7f99f8d355cb in _dl_update_slotinfo () at /lib64/ld-linux-x86-64.so.2
#1  0x7f99f8d3562c in update_get_addr () at /lib64/ld-linux-x86-64.so.2
#2  0x7f99f2bd9566 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f99f2e097ba in  () at /usr/lib/libQt5Core.so.5
#4  0x7f99ed2c8c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#5  0x7f99ed2c96cb in  () at /usr/lib/libglib-2.0.so.0
#6  0x7f99ed2c98bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#7  0x7f99f2e0a06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#8  0x7f99f2db389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#9  0x7f99f2bd5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#10 0x7f99f68c0fd6 in  () at /usr/lib/libQt5Quick.so.5
#11 0x7f99f2bda6d8 in  () at /usr/lib/libQt5Core.so.5
#12 0x7f99f1a8f2e7 in start_thread () at /usr/lib/libpthread.so.0
#13 0x7f99f24ed54f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f99cf1d7700 (LWP 836)):
#0  0x7f99f1a95756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f99f85b4234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f99f85b4279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f99f1a8f2e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f99f24ed54f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f99d8f33700 (LWP 804)):
#0  0x7f99ed30ee40 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f99ed2c8b67 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f99ed2c96cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f99ed2c98bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f99f2e0a06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f99f2db389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f99f2bd5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f99f5d0d025 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f99f2bda6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f99f1a8f2e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f99f24ed54f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f99dafc1700 (LWP 769)):
#0  0x7f99f24e367d in poll () at /usr/lib/libc.so.6
#1  0x7f99ed2c97a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f99ed2c98bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f99f2e0a06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f99f2db389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f99f2bd5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f99f5d0d025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f99f2bda6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f99f1a8f2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f99f24ed54f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f99e10a6700 (LWP 719)):
#0  0x7f99ed30ee40 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f99ed2c8c99 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f99ed2c96cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f99ed2c98bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f99f2e0a06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f99f2db389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f99f2bd5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f99f395a125 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f99f2bda6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f99f1a8f2e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f99f24ed54f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f99e2eae700 (LWP 707)):
#0  0x7f99f24e367d in poll () at /usr/lib/libc.so.6
#1  0x7f99f74da8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f99f74dc679 in xcb_wait_for_event 

[pimsettingexporter] [Bug 378578] exporting all from KMail does not export filters

[Laurent Montel]

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

--- Comment #1 from Laurent Montel  ---
I really need a testcase
Which version ?

etc

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

[kate] [Bug 378579] New: kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks

[Rick Graves]

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

Bug ID: 378579
   Summary: kate (and kwrite) on large files: version 3.7 is fine,
version 15 sucks
   Product: kate
   Version: 15.12
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: gravesricha...@yahoo.com
  Target Milestone: ---

Created attachment 104928
  --> https://bugs.kde.org/attachment.cgi?id=104928=edit
It shows the cursor one line down from the top.

I am on kubuntu, so I get the kate (and kwrite) version the ubuntu people give
me.

I have been using kwrite to maintain a big file (25 mb). (Note that kwrite uses
the kate editor.)

On kubuntu 14.04 (kate version 3), kwrite worked great.

When I first tried kubuntu 16.04 (kate version 5/15) in early 2016, kwrite was
clearly not the same:

1. For the arrow keys, keyboard repeat works at the top of the file, but not
further down. In kate version 5/15, the display does not update -- you cannot
see where the cursor is. If you hold an arrow key down for a while and release,
after some seconds, the cursor freezes then reappears somewhere. In kate
version 3, anywhere in the file, you see exactly where the cursor is at every
instant, you can release the arrow key when you want, and the cursor is where
you expect it to be.

2. Pasting text into the file (anywhere except the top), kate version 5/15
takes several seconds for the text to appear. Using kate version 3, the text
appeared instantly.

After evaluating kubuntu 16.04 in early 2016, the kwrite problem was a show
stopper -- I declined to upgrade kubuntu, and I have been on 14.04 until
recently. But then in March, a more pressing consideration made me upgrade to
16.04, and kwrite is still a problem on my big file.

In 2016, I tried tweaking settings in hope of fixing the problem, but I did not
find a solution.

Note that I encountered this problem using the same hardware.  Right now, I
have two hard drives for my Lenovo Thinkpad T500 laptop with 8 GB memory, one
hard drive with kubuntu 14.04 (kate version 3), and another hard drive with
kubuntu 16.04 (kate version 5/15).  I can shut the laptop down and swap hard
drives. You can say my laptop is too slow, but kate version 3 works perfectly
OK on my laptop -- no complaints.  But on the same laptop, kate version 5/15
sucks.

I have encountered deniers, so I assembled a big file -- anyone can try it
themselves.  I googled "Richard Stallman", went to some hit pages, and copied
some text by or about him. I pasted into a file and duplicated. I used the fmt
utility to break the long lines into shorter lines (the file I edit in real
life has mostly short lines). The file is almost 27 mb (too big to attach). I
gzipped it, and uploaded it here:

http://www.advanced-app.com.hk/MiscJunk/Stallman_Richard_short.txt.gz

For both the following tests, I used wget to download the file and gzip -d to
extract it.

For the latter of the two tests below, see the attached picture. It shows the
cursor one line down from the top.  The test, conducted near the bottom of the
file, is to determine, after pressing down arrow once, how long it takes for
the cursor to appear one line down from the top (as explained in detail below).

On the Lenovo Thinkpad T500 laptop with 8 GB memory running kubuntu 16.04 (kate
version 5/15):
I went to the bottom of the file, and from the bottom I selected up to and
including the line "The consequences:". I copied the selected text. I used PgUp
several times until I came to the heading "The GNU Manifesto". Above that
heading, I hit Paste (Ctrl-V), and counted "one thousand one, one thousand two,
one thousand three, ..." The inserted text appeared between one thousand five
and one thousand six. I hit Ctrl-Z. I pressed the up arrow key, and kept
pressing it while I counted ""one thousand one, one thousand two, one thousand
three, one thousand four, one thousand five" then I released the up arrow key,
immediately pressed down arrow once (quickly) and started counting again. The
cursor did not appear one line down from the top until AFTER I counted up to
one thousand eight.

On the SAME Lenovo Thinkpad T500 laptop with 8 GB memory, running kubuntu 14.04
(kate version 3):
I went to the bottom of the file, and from the bottom I selected up to and
including the line "The consequences:". I copied the selected text. I used PgUp
several times until I came to the heading "The GNU Manifesto". Above that
heading, I hit Paste (Ctrl-V). There was no need to count, as the inserted text
appeared instantaneously (to my human perception). I hit Ctrl-Z. I pressed the
up arrow key, and kept pressing it while I counted ""one thousand one, one
thousand two, one thousand three, one thousand four, one thousand five" then I
released the up arrow key, immediately pressed down arrow once 

[kwin] [Bug 378532] fast window switching (ALT+Tab) is broken for fullscreen windows

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
> why is the minimized window put to the end of the list, thats (for me) really 
> unexpected and feels strange

I have no idea it has been like that before I joined development.

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

[kexi] [Bug 378559] changing between design and view creates a crash

[RJ]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

--- Comment #1 from RJ  ---
Provide an example project please.

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