[plasmashell] [Bug 376055] Plasma crashes when switching activities after unpinning a launcher specific to an activity

[Eike Hein]

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

--- Comment #4 from Eike Hein  ---
Thank you! But unfortunately shell output isn't a backtrace ... the shell
output indicates that the crash handler is starting, are you sure you don't get
a tray icon for it after restarting plasmashell? You can click on the tray icon
to get the crash dialog and the backtrace.

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|UNMAINTAINED|---
 Status|RESOLVED|REOPENED
Version|4.12.0  |5.4.0
 Ever confirmed|0   |1

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

[plasmashell] [Bug 375860] Plasma Shell crash

[Dmitry]

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

--- Comment #4 from Dmitry  ---
I've completely similar bug.

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

[plasmashell] [Bug 375860] Plasma Shell crash

[Dmitry]

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

--- Comment #3 from Dmitry  ---
Created attachment 103916
  --> https://bugs.kde.org/attachment.cgi?id=103916=edit
Applets rc

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

[plasmashell] [Bug 375860] Plasma Shell crash

[Dmitry]

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

Dmitry  changed:

   What|Removed |Added

 CC||goldedra...@gmail.com

--- Comment #2 from Dmitry  ---
Created attachment 103915
  --> https://bugs.kde.org/attachment.cgi?id=103915=edit
Stack trace

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[court]

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

--- Comment #26 from court  ---
(In reply to CnZhx from comment #25)
> (In reply to court from comment #24)
> > ... and the issue is gone
> 
> Hi there, have you tried to deselect then enable the to-do list again? 
> 

Hey CnZhx, I looked at my PIM plugin and for me both my To-Do and my regular
calendar are lumped together into one. What is also interesting is on my
desktop which is Fedora 24 and was affected by this stopped presenting this
issue which is interesting. I don't recall getting any updates pertaining to
the clock widget

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

[dolphin] [Bug 376221] New: Local folders are not reread after mounting

[Johannes]

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

Bug ID: 376221
   Summary: Local folders are not reread after mounting
   Product: dolphin
   Version: 16.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: johannes.kin...@gmail.com
  Target Milestone: ---

Folders mounted with encfs are not displayed after reopening

Steps
1) create a folder in Home named Secret, the folder appears to be empty
2) Leave the folder Secret (go up)
3) mount an encrypted fs in Secret (eg encfs ~/Dropbox/secret.bc ~/Secret
4) Reopen the folder Secret

Actual: the folder is still displayed as empty
Expected: the folder contents is shown.

Possible work around: open the folder and press F5

Rationale: a beginning user might be confused and suspect the encrypted fs
wasn't properly mounted.

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

[kmail2] [Bug 376202] Emails are moved to folders on read, without explanation

[Olivier Churlaud]

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

--- Comment #2 from Olivier Churlaud  ---
I double/triple checked that. 

I'll try to reproduce with the debug mode on

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

[plasmashell] [Bug 375951] locally integrated menus

[Bronson]

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

--- Comment #3 from Bronson  ---
Just for reference, I found an old post where it actually worked under kde 4
https://forum.kde.org/viewtopic.php?f=88=120180

It would be great to see this added.

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

[plasmashell] [Bug 376220] New: Browsing the Plasma5 Extensions

[bugzilla_noreply]

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

Bug ID: 376220
   Summary: Browsing the Plasma5 Extensions
   Product: plasmashell
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lunaki...@protonmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.1)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Scrolling through the Plasma5 Extensions explorer inside the "install more"

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

Thread 36 (Thread 0x7fb341a38700 (LWP 16003)):
#0  0x7ffc8952b937 in  ()
#1  0x7ffc8952bbc5 in clock_gettime ()
#2  0x7ff4a87d66b6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7ff4a90e5601 in  () at /usr/lib/libQt5Core.so.5
#4  0x7ff4a90e3dc9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7ff4a90e4375 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7ff4a90e5a3e in  () at /usr/lib/libQt5Core.so.5
#7  0x7ff4a357ac89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7ff4a357b6ab in  () at /usr/lib/libglib-2.0.so.0
#9  0x7ff4a357b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x7ff4a90e646b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#11 0x7ff4a908fc9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#12 0x7ff4a8eb1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#13 0x7ff4a8eb66d8 in  () at /usr/lib/libQt5Core.so.5
#14 0x7ff4a7d70454 in start_thread () at /usr/lib/libpthread.so.0
#15 0x7ff4a87c97df in clone () at /usr/lib/libc.so.6

Thread 35 (Thread 0x7fb323fff700 (LWP 15883)):
#0  0x7ff4a7d7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff4a8eb758b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff4acc67665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff4acc67f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff4a8eb66d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff4a7d70454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff4a87c97df in clone () at /usr/lib/libc.so.6

Thread 34 (Thread 0x7ff3a55e0700 (LWP 15365)):
#0  0x7ff4a7d7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff4a8eb758b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff4acc67665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff4acc67f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff4a8eb66d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff4a7d70454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff4a87c97df in clone () at /usr/lib/libc.so.6

Thread 33 (Thread 0x7fb340ff9700 (LWP 15325)):
#0  0x7ff4a87c048d in poll () at /usr/lib/libc.so.6
#1  0x7ff4a357b786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff4a357b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff4a90e646b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff4a908fc9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff4a8eb1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fb35d83d385 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#7  0x7ff4a8eb66d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff4a7d70454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff4a87c97df in clone () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7fb35ec18700 (LWP 15083)):
#0  0x7ff4a87bc4ed in read () at /usr/lib/libc.so.6
#1  0x7ff4a35bfa10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff4a357b235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7ff4a357b724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7ff4a357b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7ff4a90e646b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7ff4a908fc9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7ff4a8eb1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7ff4a8eb66d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7ff4a7d70454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7ff4a87c97df in clone () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7fb36fff8700 (LWP 15010)):
#0  0x7ff4a87bc4ed 

[dolphin] [Bug 372160] Image Size Field not Populated and tooltip missing EXIF information

[Ken]

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

Ken  changed:

   What|Removed |Added

 CC||kenshiw...@gmail.com

--- Comment #3 from Ken  ---
I would like also to confirm and verify that I am having the same issue as
described by (David Rankin) and (Valorie Zimmerman).

My system details are as follows:

- Dolphin: 16.04.3
- KDE: 5.28.0
- Qt: 5.6.1
- Kubuntu OS: 16.10
- Kernel: 4.8.0-37-generic

Your attention to this matter will be greatly appreciated.

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

[rbugman28]

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

--- Comment #2 from rbugma...@yahoo.com  ---
Shall I put another bug report for 5.4.0? I get the same issues with Tag
ViewThanks Rick


On Thursday, February 9, 2017 12:01 AM, "bugzilla_nore...@kde.org"
 wrote:


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

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

          What    |Removed                    |Added

                CC|                            |caulier.gil...@gmail.com
            Status|UNCONFIRMED                |RESOLVED
        Resolution|---                        |UNMAINTAINED

--- Comment #1 from caulier.gil...@gmail.com ---
digiKam 4.12 is a very old version of digiKam (3 year ago). We are now in 5.4.0
with more than 400 bugs fixes since 4.X release. 

If your Linux disto do not provide a most recent version, use AppImage linux
bundle that we provide. See download page from digikam.org.

Gilles Caulier

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

[dolphin] [Bug 372160] Image Size Field not Populated and tooltip missing EXIF information

[Valorie Zimmerman]

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

Valorie Zimmerman  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kmail2] [Bug 376219] New: KMAIL won't start akonadi error message

[bugzilla_noreply]

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

Bug ID: 376219
   Summary: KMAIL won't start akonadi error message
   Product: kmail2
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: shawn.t...@gmail.com
  Target Milestone: ---

Created attachment 103913
  --> https://bugs.kde.org/attachment.cgi?id=103913=edit
Screenshot of issue

KMAIL won't start akonadi error message

on

Linux ubuntu 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

Kubuntu 16.10 x64.

Also, WMail is my backup and it won't work either.

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

[dolphin] [Bug 372160] Image Size Field not Populated and tooltip missing EXIF information

[Valorie Zimmerman]

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

Valorie Zimmerman  changed:

   What|Removed |Added

 CC||valorie.zimmer...@gmail.com

--- Comment #2 from Valorie Zimmerman  ---
One of our Kubuntu users pointed this out to me in IRC tonight. He is using
16.04.3, and described his issue here:
https://askubuntu.com/questions/881428/dolphin-is-not-showing-the-image-dimensions-metadata-when-previewing-images-on-k

I can verify that in version 16.12.1 I still cannot see anything more than
filesize; no image size is reported. I have relied on this information many
times in the past, and hope to see it return soon.

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #1 from caulier.gil...@gmail.com ---
digiKam 4.12 is a very old version of digiKam (3 year ago). We are now in 5.4.0
with more than 400 bugs fixes since 4.X release. 

If your Linux disto do not provide a most recent version, use AppImage linux
bundle that we provide. See download page from digikam.org.

Gilles Caulier

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #7 from Mustafa Muhammad  ---
Created attachment 103912
  --> https://bugs.kde.org/attachment.cgi?id=103912=edit
trace with debug packages installed

I installed all debug packages I could find in the file and generated a new
trace.

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

[krita] [Bug 375929] Full Screen needs to clicked 3 times to exit out of.

[cheteron]

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

--- Comment #4 from cheteron  ---
Canvas mode don't work correctly too

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

[krita] [Bug 376218] Krita crashes with larger brush sizes

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

   Severity|normal  |crash
   Priority|NOR |VLO
 OS|Linux   |MS Windows
   Platform|Other   |Windows CE

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

[krita] [Bug 376218] New: Krita crashes with larger brush sizes

[Scott Petrovic]

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

Bug ID: 376218
   Summary: Krita crashes with larger brush sizes
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: scottpetro...@gmail.com
  Target Milestone: ---

I updated my maximum brush size in Krita to override the 1,000px max limit in
the kritarc. When I tried to resize my brush to the larger size, Krita crashed.
The program came to a halt when I changed my brush size to about 50,000 px. 

This crash is highly reproducible. :) (joking)

We probably should set a limit when it reads that value. I am not sure what a
good default would be. I did test it out at 10,000px and it seemed to work
without crashing. It is a bit ridiculous with that size, but I am not sure if
people will be needing much bigger than that.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Nick]

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

--- Comment #237 from Nick  ---
(In reply to David Edmundson from comment #2)
> >yes, the feature has been removed and due to the huge problem and added 
> >complexity it gave, is not going back.
> 
> Then close the bug.

--
What is a camel ?
A horse designed by a very complex committee .
It seems that the good old KDE has just become a camel with lots of
complexities .

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Nick]

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

--- Comment #236 from Nick  ---
(In reply to David Edmundson from comment #2)
> >yes, the feature has been removed and due to the huge problem and added 
> >complexity it gave, is not going back.
> 
> Then close the bug.

--
What is a camel ?
A horse designed by a very complex committee .
It seems that the good old KDE has just become a camel with lots of
complexities .

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

[kdevelop] [Bug 376217] New: Crash when autostarting

[Mikael B]

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

Bug ID: 376217
   Summary: Crash when autostarting
   Product: kdevelop
   Version: 5.0.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: mikae...@yahoo.com
  Target Milestone: ---

Application: kdevelop (5.0.3)

Qt Version: 5.6.2
Frameworks Version: 5.29.0
Operating System: Linux 4.9.7-101.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

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

Desktop Environment XFCE. Set to save workspaces on logout, and recover on
login. 

I had 3 or 4 different kdevelop sessions running when I shut down the computer
earlier today, expecting kdevelop to restart with these sessions when I started
next time. Instead, I was greeted with two messages that the application had
crashed.

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

Thread 7 (Thread 0x7f8c632ca700 (LWP 2812)):
#0  0x7f8cb5c0abd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cbd57d03a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f8cc273ac56 in
QQmlThread::internalCallMethodInMain(QQmlThread::Message*) () at
/lib64/libQt5Qml.so.5
#3  0x7f8cc270fec2 in QQmlImportDatabase::importDynamicPlugin(QString
const&, QString const&, QString const&, int, QList*) () at
/lib64/libQt5Qml.so.5
#4  0x7f8cc271107b in QQmlImportsPrivate::importExtension(QString const&,
QString const&, int, int, QQmlImportDatabase*, QQmlTypeLoader::QmldirContent
const*, QList*) () at /lib64/libQt5Qml.so.5
#5  0x7f8cc2711b36 in QQmlImportsPrivate::addLibraryImport(QString const&,
QString const&, int, int, QString const&, QString const&, bool,
QQmlImportDatabase*, QList*) () at /lib64/libQt5Qml.so.5
#6  0x7f8cc2711d7e in QQmlImports::addLibraryImport(QQmlImportDatabase*,
QString const&, QString const&, int, int, QString const&, QString const&, bool,
QList*) () at /lib64/libQt5Qml.so.5
#7  0x7f8cc26dd796 in
QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*,
QList*) () at /lib64/libQt5Qml.so.5
#8  0x7f8cc26de053 in QQmlTypeData::continueLoadFromIR() () at
/lib64/libQt5Qml.so.5
#9  0x7f8cc26de7b0 in QQmlTypeData::dataReceived(QQmlDataBlob::Data const&)
() at /lib64/libQt5Qml.so.5
#10 0x7f8cc26d7992 in QQmlTypeLoader::setData(QQmlDataBlob*,
QQmlDataBlob::Data const&) () at /lib64/libQt5Qml.so.5
#11 0x7f8cc26d81a1 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlFile*) ()
at /lib64/libQt5Qml.so.5
#12 0x7f8cc26d93a9 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at
/lib64/libQt5Qml.so.5
#13 0x7f8cc26d97cd in QQmlTypeLoaderThread::loadThread(QQmlDataBlob*) () at
/lib64/libQt5Qml.so.5
#14 0x7f8cc273a884 in QQmlThreadPrivate::threadEvent() () at
/lib64/libQt5Qml.so.5
#15 0x7f8cc273aeea in QQmlThreadPrivate::event(QEvent*) () at
/lib64/libQt5Qml.so.5
#16 0x7f8cbdfa7e4c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#17 0x7f8cbdfad32f in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#18 0x7f8cbd71a9da in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#19 0x7f8cbd71ca8f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#20 0x7f8cbd76a6c3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#21 0x7f8cb2fd76ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#22 0x7f8cb2fd7a70 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#23 0x7f8cb2fd7b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#24 0x7f8cbd76a73f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#25 0x7f8cbd71981a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#26 0x7f8cbd578353 in QThread::exec() () at /lib64/libQt5Core.so.5
#27 0x7f8cc273a525 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#28 0x7f8cbd57c9ba in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#29 0x7f8cb5c055ca in start_thread () at /lib64/libpthread.so.0
#30 0x7f8cbc9700ed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f8c71d43700 (LWP 2601)):
#0  0x7f8cbc9601cd in read () at /lib64/libc.so.6
#1  0x7f8cb301a660 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f8cb2fd74d6 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f8cb2fd79a4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f8cb2fd7d92 in g_main_loop_run () at 

[plasmashell] [Bug 375625] When loading new pics as Plasma Desktop wallpaper the pic is not previewed if greater 5 meg !

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
I am not sure if the thumbnailers in KF5 read a MaximumSize setting, but if
they do, the config file is not in a KDE4 location, so you could try to adapt
the path mentioned in the duplicate.

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

[plasmashell] [Bug 375257] VirtualBox mini toolbar doesn't respond to mouse clicks

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #11 from Christoph Feck  ---
Readding Martin to check comment #9 and comment #10.

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

[tellico] [Bug 376134] Export collection in HTML does not work

[Robby Stephenson]

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

Robby Stephenson  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/tel
   ||lico/9dac9ef56e7bdceef9327e
   ||c8375c52fe1d369ea0
 Resolution|--- |FIXED
   Version Fixed In||3.0.1
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Robby Stephenson  ---
Git commit 9dac9ef56e7bdceef9327ec8375c52fe1d369ea0 by Robby Stephenson.
Committed on 09/02/2017 at 01:45.
Pushed by rstephenson into branch 'master'.

Fix relative file locations in HTML export

This was another problem relative to the KURL->QUrl transition dealing
with relative urls and invalid links.

Add another unit test for the HTML export to verify appropriate relative
links, including checkmark pics and image files.
FIXED-IN: 3.0.1

M  +4-0ChangeLog
M  +---src/tests/data/with-image.tc
M  +66   -1src/tests/htmlexportertest.cpp
M  +2-0src/tests/htmlexportertest.h
M  +37   -41   src/translators/htmlexporter.cpp
M  +5-0src/translators/htmlexporter.h

https://commits.kde.org/tellico/9dac9ef56e7bdceef9327ec8375c52fe1d369ea0

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

[kmail2] [Bug 376216] New: Error on boot

[bugzilla_noreply]

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

Bug ID: 376216
   Summary: Error on boot
   Product: kmail2
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: shawn.t...@gmail.com
  Target Milestone: ---

Error on launching software that would not give me the details. Additionally,
it would not allow me to add an email, so its not working at all.

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

[kded-appmenu] [Bug 375927] Global Menu doesn't work with LibreOffice

[PGillespie]

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

--- Comment #2 from PGillespie  ---
Just installed 5.9.1. Checked Global Menu with LibreOffice and still no love.

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

[krita] [Bug 376215] New: layer sometimes says "group not editable"

[bugzilla_noreply]

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

Bug ID: 376215
   Summary: layer sometimes says "group not editable"
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: rianis...@gmail.com
  Target Milestone: ---

sometimes when i am drawing on a SINGULAR layer and i try to draw on it it will
say "group not editable". this is on a SINGULAR layer!

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

[krita] [Bug 376214] New: layer sometimes says "group not editable"

[bugzilla_noreply]

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

Bug ID: 376214
   Summary: layer sometimes says "group not editable"
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: rianis...@gmail.com
  Target Milestone: ---

Created attachment 103911
  --> https://bugs.kde.org/attachment.cgi?id=103911=edit
you can see what happens when i try to draw

sometimes when i am drawing on a SINGULAR layer and i try to draw on it it will
say "group not editable". this is on a SINGULAR layer!

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

[rsibreak] [Bug 375931] Actions configuration can not be remembered

[Dale Wang]

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

--- Comment #3 from Dale Wang  ---
(In reply to Albert Astals Cid from comment #2)
> Git commit 27af2e51986b13882e3d4488cd24cb32e8b50a3f by Albert Astals Cid.
> Committed on 03/02/2017 at 23:05.
> Pushed by aacid into branch 'master'.
> 
> Save the changes made to the notifications ^_^
> 
> M  +1-0src/setup.cpp
> M  +8-3src/setupnotifications.cpp
> M  +7-0src/setupnotifications.h
> 
> https://commits.kde.org/rsibreak/27af2e51986b13882e3d4488cd24cb32e8b50a3f

Thanks Albert~ Looking forward to the new version!

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

[digikam] [Bug 376213] New: Tag selection fails to find tagged photo's

[rbugman28]

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

Bug ID: 376213
   Summary: Tag selection fails to find tagged photo's
   Product: digikam
   Version: 4.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: rbugma...@yahoo.com
  Target Milestone: ---

repeatable, album names are not shown (blank), thumbnails appear and disappear
or change to another photo when moused over. strange behavior.
tagged photo's not shown

Note: setting tag as filter -no problems

no issues with earlier version 3.5
note: same database as 3.5

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

[gwenview] [Bug 364805] Gwenview fails to open images with russian letters in path - Invalid url QUrl("") or file or path does not exist

[emg81]

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

--- Comment #5 from emg81  ---
(In reply to Christoph Feck from comment #4)
> Which locale do you use? If the locale uses UTF-8 encoding, are you sure all
> filenames are correctly UTF-8 encoded? If unsure, try the 'convmv' tool to
> check and correct the encoding of filenames.
> 
> https://linux.die.net/man/1/convmv

Thanks for answer.

I've tried this tool. Seems that everything is UTF-8 so far
ivan@pc ~ $ convmv -f UTF-8 -t UTF-8 -r ~/
Starting a dry run without changes...
WARNING: cannot traverse /home/ivan/.subversion/auth
WARNINGS occurred. Do you really want to continue? (y/n) y

No changes to your files done. Would have converted 0 files in 27 seconds.
Use --notest to finally rename the files.

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

[kuser] [Bug 376157] kf5 kuser

[Matthias]

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

Matthias  changed:

   What|Removed |Added

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

--- Comment #4 from Matthias  ---
I see now that Gentoo and Fedora build it without accoutservice - so its seems
to be possible, thanks a lot. (Other distros like Debian/Ubuntu build it with
that)

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

[kdenlive] [Bug 375827] No text or graphics on buttons on Mint with Cinammon Desktop

[Matthias]

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

--- Comment #14 from Matthias  ---
(In reply to Daniel from comment #11)
>Hi Mathias, I agree about your arguments, but try walking in the shoes
>of the new linux user. 

I do that every day, believe me. Thats exactly the reason, why i wrote that.
I mean the packagers, not you.

>Maybe the 90% of the new users are simply
>users, not experts. They aren't know about packagers and the GUI's
>wars.The simply users are just users. The main reason of any product
>or proyect are the users.I used the forum before search on another
>sources, and I don't found any mention about the theme. I just only
>try to use the channel that KDE offer us inside the program.I really
>apreciate your support and I only want express my opinion.

I fully agree and appreciate with you.

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

[kdenlive] [Bug 375827] No text or graphics on buttons on Mint with Cinammon Desktop

[farid]

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

--- Comment #13 from farid  ---
(In reply to Matthias from comment #10)
> Since sudo apt install kde-runtime seems to work: I found this via Google in
> some seconds: https://www.youtube.com/watch?v=m5-XPdDF9QI
> 
> This is one (of many, imho) packaging issues in Ubuntu. 
> They simply dont care about .. well, basic things like sane packaging and
> testing a software, before they ship. 
> 
> Cantata, Virtualbox and dozens of other examples prove it as well.
> 
> Such issues lead users to say that "KDE is buggy", while their packagers are
> simply incompetent.

Hi Mathias, it seems that kde-runtime is a kde4 package and it shouldn't have
fixed the issue. Either way it should be fixed soon.

Thanks for the help!

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

[kdenlive] [Bug 375827] No text or graphics on buttons on Mint with Cinammon Desktop

[farid]

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

farid  changed:

   What|Removed |Added

 Resolution|INVALID |UPSTREAM

--- Comment #12 from farid  ---
(In reply to Daniel from comment #11)
>Hi Mathias, I agree about your arguments, but try walking in the shoes
>of the new linux user. Maybe the 90% of the new users are simply
>users, not experts. They aren't know about packagers and the GUI's
>wars.The simply users are just users. The main reason of any product
>or proyect are the users.I used the forum before search on another
>sources, and I don't found any mention about the theme. I just only
>try to use the channel that KDE offer us inside the program.I really
>apreciate your support and I only want express my opinion.
> 
>El 3 feb. 2017 2:15 PM, Matthias  escribió:
> 
>  https://bugs.kde.org/show_bug.cgi?id=375827
> 
>  --- Comment #10 from Matthias  ---
>  Since sudo apt install kde-runtime seems to work: I found this via
>  Google in
>  some seconds: https://www.youtube.com/watch?v=m5-XPdDF9QI
> 
>  This is one (of many, imho) packaging issues in Ubuntu.
>  They simply dont care about .. well, basic things like sane
>  packaging and
>  testing a software, before they ship.
> 
>  Cantata, Virtualbox and dozens of other examples prove it as well.
> 
>  Such issues lead users to say that "KDE is buggy", while their
>  packagers are
>  simply incompetent.
> 
>  --
>  You are receiving this mail because:
>  You reported the bug.

Daniel and Mathias, thanks for your help. We've had some issues with missing
icons and themes that had been resolved in the forums. Here is an example:
https://forum.kde.org/viewtopic.php?f=265=135987=icon+breeze

Although due to your report we have double checked and it seems the
kdenlive-stable PPA was broken and had been causing some issues, it should be
fixed this week.

And Daniel, always feel free to express your opinions with us, be it here or in
the forums.

Cheers

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

[plasmashell] [Bug 376210] Regular folder icon and symlinked folder icon look the same

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Support for overlays and symlinks was recently added to FolderView, ie. they
have a "link" badge now as well as an italicized label. Can you check again
with 5.9 please.

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

[plasmashell] [Bug 376212] Minimize Windows widget: auto-invoke minimize action when files are dragged over

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 376212] Minimize Windows widget: auto-invoke minimize action when files are dragged over

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||h...@kde.org

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

[plasmashell] [Bug 376212] New: Minimize Windows widget: auto-invoke minimize action when files are dragged over

[Gregor Mi]

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

Bug ID: 376212
   Summary: Minimize Windows widget: auto-invoke minimize action
when files are dragged over
   Product: plasmashell
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: codestr...@posteo.org
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Reading this blog post
(https://blogs.kde.org/2017/01/31/plasma-510-spring-loading-folder-view-performance-work)
it came to my mind that in earlier days the Minimize Windows widget triggered
the minimize action automatically if the mouse hovered over it, while
"carrying" (dragging) one or more files with it.

This was a handy feature when one starts dragging a file from dolphin with the
intent to place a symlink on the desktop. Could the function be restored? This
would also be interesting for the Show Desktop widget.

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

[kdenlive] [Bug 375827] No text or graphics on buttons on Mint with Cinammon Desktop

[Daniel]

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

--- Comment #11 from Daniel  ---
   Hi Mathias, I agree about your arguments, but try walking in the shoes
   of the new linux user. Maybe the 90% of the new users are simply
   users, not experts. They aren't know about packagers and the GUI's
   wars.The simply users are just users. The main reason of any product
   or proyect are the users.I used the forum before search on another
   sources, and I don't found any mention about the theme. I just only
   try to use the channel that KDE offer us inside the program.I really
   apreciate your support and I only want express my opinion.

   El 3 feb. 2017 2:15 PM, Matthias  escribió:

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

 --- Comment #10 from Matthias  ---
 Since sudo apt install kde-runtime seems to work: I found this via
 Google in
 some seconds: https://www.youtube.com/watch?v=m5-XPdDF9QI

 This is one (of many, imho) packaging issues in Ubuntu.
 They simply dont care about .. well, basic things like sane
 packaging and
 testing a software, before they ship.

 Cantata, Virtualbox and dozens of other examples prove it as well.

 Such issues lead users to say that "KDE is buggy", while their
 packagers are
 simply incompetent.

 --
 You are receiving this mail because:
 You reported the bug.

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

[Breeze] [Bug 376211] New: Icon for application/x-awk

[bugzilla_noreply]

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

Bug ID: 376211
   Summary: Icon for application/x-awk
   Product: Breeze
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: fl...@mailoo.org
CC: kain...@gmail.com
  Target Milestone: ---

There is currently no icon for the AWK script mimetype (application/x-awk).

A possible icon compliant with the Breeze style would be an orange with a black
"A" letter. The orange would remind of the old Oxygen icon:
http://www.iconarchive.com/show/oxygen-icons-by-oxygen-icons.org/Mimetypes-application-x-awk-icon.html

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

[plasmashell] [Bug 376210] New: Regular folder icon and symlinked folder icon look the same

[Gregor Mi]

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

Bug ID: 376210
   Summary: Regular folder icon and symlinked folder icon look the
same
   Product: plasmashell
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: codestr...@posteo.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Currently, on the desktop - when used as folderview - a regular folder looks
like a symlinked folder.

It would be helpful to distinguish these two types of items at one glance.

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

[kalarm] [Bug 376209] Command options --edit-new-* do not work

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kalarm] [Bug 376209] New: Command options --edit-new-* do not work

[David Jarvie]

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

Bug ID: 376209
   Summary: Command options --edit-new-* do not work
   Product: kalarm
   Version: 2.11.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: djar...@kde.org
  Target Milestone: ---

No edit alarm dialogue is displayed when the --edit-new-* options are used.

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

[kalarm] [Bug 375568] Couldn't start kalarm. Returns a popped up error message: KDEInit couldn't start /usr/bin/kalarm

[David Jarvie]

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

--- Comment #2 from David Jarvie  ---
The issue with "kalarm -h" should now be fixed in KDE Applications 16.12.2 or
16.12.3 (not sure which release it will get into). The problem was due to
differences in how unique applications are handled under KDE Frameworks 5 as
compared to KDE 4.

Fixed in commit c5897d0eabf515a82a62429a726819cb60e255ae (16.12 branch).

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

[okular] [Bug 266537] Rectangle selection tool may leave behind visual artifacts on pages

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/oku
   ||lar/6f3970dbe48fb6b75c611ea
   ||68994e57a98791a47

--- Comment #5 from Albert Astals Cid  ---
Git commit 6f3970dbe48fb6b75c611ea68994e57a98791a47 by Albert Astals Cid, on
behalf of Walter Mollica.
Committed on 08/02/2017 at 22:16.
Pushed by aacid into branch 'Applications/16.12'.

Extend viewport update area when updating or clearing the a selection rectangle

Extending the viewport update area of the selection rectangle when dragging the
mouse while in selection mode or when canceling the selection ensures that no
artifacts remain on-screen in either case.

Differential Revision: https://phabricator.kde.org/D4487

M  +2-2ui/pageview.cpp

https://commits.kde.org/okular/6f3970dbe48fb6b75c611ea68994e57a98791a47

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

[kalarm] [Bug 374520] When KAlarm is running with --tray, running another instance doesn't show a new main window

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kal
   ||arm/c5897d0eabf515a82a62429
   ||a726819cb60e255ae
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Jarvie  ---
This was due to differences in how unique applications are handled under KDE
Frameworks 5 as compared to KDE 4.

Fixed in commit c5897d0eabf515a82a62429a726819cb60e255ae (16.12 branch).

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

[kdemultimedia] [Bug 376204] no package libqt5multimedia-dev

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||aa...@kde.org

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

[digikam] [Bug 290944] BQM Watermark tool : does not support correct placement of watermarks

[Ahmed Fathi]

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

Ahmed Fathi  changed:

   What|Removed |Added

 CC||ahmed.fathi.abdelmageed@gma
   ||il.com

--- Comment #1 from Ahmed Fathi  ---
I think this patch solves this problem 
https://bugs.kde.org/show_bug.cgi?id=338869

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

[digikam] [Bug 250642] BQM Watermark tool : signature does not respect correct orientation

[Ahmed Fathi]

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

Ahmed Fathi  changed:

   What|Removed |Added

 CC||ahmed.fathi.abdelmageed@gma
   ||il.com

--- Comment #9 from Ahmed Fathi  ---
I think this patch solves this problem : 
https://bugs.kde.org/show_bug.cgi?id=338869

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

[digikam] [Bug 338869] BQM Watermark tool : add new option to rotate text

[Ahmed Fathi]

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

--- Comment #2 from Ahmed Fathi  ---
Created attachment 103910
  --> https://bugs.kde.org/attachment.cgi?id=103910=edit
photos for the feature provided by the previous patch

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

[digikam] [Bug 338869] BQM Watermark tool : add new option to rotate text

[Ahmed Fathi]

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

Ahmed Fathi  changed:

   What|Removed |Added

 CC||ahmed.fathi.abdelmageed@gma
   ||il.com

--- Comment #1 from Ahmed Fathi  ---
Created attachment 103909
  --> https://bugs.kde.org/attachment.cgi?id=103909=edit
patch for watermark orientation feature. also handles exif data correctly

This patch provides this feature. It also handles the exif data correctly. if
the exif data specifies , for example , that the image is rotated 90 degrees
clockwise, and the user chooses to place a water mark at the bottom right of
the photo, It will be placed on the bottom right of the photo as expected. This
was the problem proposed by the following two entries : 

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

In the next comment I provide some screen shots of the watermark orientation
feature, in addition to some screenshots for the watermark orientation + exif
data orientation side by side

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

[skrooge] [Bug 375865] Quick fill: select/enter item does not lock payee

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/skr
   ||ooge/ea1f7206297c94580a2650
   ||6bba61e1c36c05be86
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #1 from Stephane MANKOWSKI  ---
Git commit ea1f7206297c94580a26506bba61e1c36c05be86 by Stephane Mankowski.
Committed on 08/02/2017 at 21:54.
Pushed by smankowski into branch 'master'.

Quick fill: select/enter item does not lock payee

M  +1-0CHANGELOG
M  +1-1plugins/skrooge/skrooge_operation/skgoperationplugin.cpp
M  +4-25   plugins/skrooge/skrooge_operation/skgoperationpluginwidget.cpp
M  +0-1plugins/skrooge/skrooge_operation/skgoperationpluginwidget.h

https://commits.kde.org/skrooge/ea1f7206297c94580a26506bba61e1c36c05be86

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

[plasmashell] [Bug 376205] Clicking on grouped window list and then ctrl-clicking on item in task bar crashes plasmashell

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Severity|major   |crash
 CC||k...@privat.broulik.de

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

[systemsettings] [Bug 376208] New: Hot new stuff and KDE settings crashed while downloading icons

[Tommy Beauclair]

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

Bug ID: 376208
   Summary: Hot new stuff and KDE settings crashed while
downloading icons
   Product: systemsettings
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tommybeaucl...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.6-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

I wanted to download an icon theme when Hot new stuff and KDE settings crashed.

-- Backtrace:
Application: Configuration du système (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe72b2b21c0 (LWP 10038))]

Thread 8 (Thread 0x7fe6ea7fc700 (LWP 10398)):
#0  0x7fe726fd34ed in read () at /usr/lib/libc.so.6
#1  0x7fe7213cfa10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe72138b235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fe72138b724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe72138b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fe7278fa48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fe7278a3e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fe7276c6053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fe7276cace8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe7230a4454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe726fe07df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fe6f1694700 (LWP 10324)):
#0  0x7fe7276c1e69 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x7fe7278f9bff in  () at /usr/lib/libQt5Core.so.5
#2  0x7fe72138ac89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe72138b6ab in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe72138b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fe7278fa48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fe7278a3e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fe7276c6053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fe7276cace8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe7230a4454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe726fe07df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fe6f25d8700 (LWP 10322)):
#0  0x7fe7230aa4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe7276cbad6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe7276c71d4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fe7276cace8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fe7230a4454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fe726fe07df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fe6c0877700 (LWP 10320)):
#0  0x7fe7213d0dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe72138b8a6 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7fe7278fa48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fe7278a3e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fe7276c6053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fe7276cace8 in  () at /usr/lib/libQt5Core.so.5
#6  0x7fe7230a4454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7fe726fe07df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fe6fccb5700 (LWP 10184)):
#0  0x7fe726fd748d in poll () at /usr/lib/libc.so.6
#1  0x7fe72138b786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe72138b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe7278fa48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe7278a3e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe7276c6053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe725a18e75 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fe7276cace8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe7230a4454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe726fe07df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fe70c869700 (LWP 10044)):
#0  0x7fe7213d0dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe72138af89 in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#2  0x7fe72138b6f8 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe72138b89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fe7278fa48b in

[akregator] [Bug 366487] Add Support for Media RSS/Atom Feeds (mrss)

[Jan Molnar]

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

Jan Molnar  changed:

   What|Removed |Added

 CC||jan.mol...@gmail.com

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

[kmail2] [Bug 376202] Emails are moved to folders on read, without explanation

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Any chance you have some misbehaving mail filter?

Otherwise, please enable "Debugger" in Akonadi Console, reproduce the case and
provide the output from it here.

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

[frameworks-kio] [Bug 369320] Changes not saved when editing .desktop files

[Mykyta Ivanchenko]

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

Mykyta Ivanchenko  changed:

   What|Removed |Added

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

--- Comment #4 from Mykyta Ivanchenko  ---
Marking this as resolved, as I can't reproduce this anymore on the latest KDE
Frameworks (5.30) and KDE Plasma (5.9.1).

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

[kaddressbook] [Bug 376207] New: Formatted name is not selectable when creating new contact

[Claus Escher]

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

Bug ID: 376207
   Summary: Formatted name is not selectable when creating new
contact
   Product: kaddressbook
   Version: 5.2.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: claus.esc...@web.de
CC: to...@kde.org
  Target Milestone: ---

Created attachment 103908
  --> https://bugs.kde.org/attachment.cgi?id=103908=edit
Creation dialogue for the contact name which does not show a possibility to
select the formatted name

When entering the name of a new contact in the addressbook you cannot select
how the formatted name shall look like. Hence new name appear always as   in the list of contacts. However some people like myself want
to sort the formatted name like this: , . 
Contacts which have been created in older versions retain their formatting and
thus appear as wanted.
When exporting the contact to vCard one can notice that the tag "FN:" is
missing.

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

[kaffeine] [Bug 376206] New: Kaffeine partly not translated

[bugzilla_noreply]

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

Bug ID: 376206
   Summary: Kaffeine partly not translated
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: yuli...@mailbox.org
  Target Milestone: ---

Hello, 
I use kaffeine in Fedora 25 (installed package from RPMFusion, but also the
newest snapshot from git, then self compiled) and in both cases some parts are
not translated. For example in all windows (properties, EPG, channels etc.) the
"Cancel"-Button is not translated (in this case the German "Abbrechen" would be
correct). Also the "open file" and "open address" dialogue is not translated. 
This seems to be something specific, as the rest of kaffeine is translated into
German. Apart from that my PC is also in German of course.

And in the "Recording Schedule" window, if there are entries, the last point
(Enabled/Disabled) is not translated.
And one small German correction: There is a full stop missing in the following
translation:
"Kaffeine hat geplante Aufnahmen\n"
should be
"Kaffeine hat geplante Aufnahmen.\n"

Thank you.

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

[plasmashell] [Bug 376205] New: Clicking on grouped window list and then ctrl-clicking on item in task bar crashes plasmashell

[RNG]

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

Bug ID: 376205
   Summary: Clicking on grouped window list and then ctrl-clicking
on item in task bar crashes plasmashell
   Product: plasmashell
   Version: 5.9.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: rga...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

If you have a grouped window list (say, many browser windows) in the task bar
and you do a (normal) click on the grouped window list the window list expands
and shows the individual windows. If you then do a ctrl-click on the item in
the task bar (ie: the root element of the expanded window list) plasmashell
crashes.

Note: all "click" actions refer to a left mouse button click.

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

[skrooge] [Bug 375866] Quick fill find operations in other account

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/skr
   ||ooge/b564b2e4cac1e4a38c9c24
   ||65200ad3d19f6d9dc0
 Status|ASSIGNED|RESOLVED

--- Comment #1 from Stephane MANKOWSKI  ---
Git commit b564b2e4cac1e4a38c9c2465200ad3d19f6d9dc0 by Stephane Mankowski.
Committed on 08/02/2017 at 20:43.
Pushed by smankowski into branch 'master'.

Quick fill find operations in other account

M  +1-0CHANGELOG
M  +4-0plugins/skrooge/skrooge_operation/skgoperation_settings.kcfg
M  +5-0plugins/skrooge/skrooge_operation/skgoperationpluginwidget.cpp
M  +45   -19  
plugins/skrooge/skrooge_operation/skgoperationpluginwidget_pref.ui

https://commits.kde.org/skrooge/b564b2e4cac1e4a38c9c2465200ad3d19f6d9dc0

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

[kdemultimedia] [Bug 376204] New: no package libqt5multimedia-dev

[Eduard Kalinowski]

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

Bug ID: 376204
   Summary: no package libqt5multimedia-dev
   Product: kdemultimedia
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-multime...@kde.org
  Reporter: eduard_kalinow...@yahoo.de
  Target Milestone: ---

it's not possible to find the header files for multimedia qt5

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

[dolphin] [Bug 376203] Dolphin (or terminal ?) crashed when trying to open it as sub-window in dolphin (F4)

[Martin Jost]

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

--- Comment #1 from Martin Jost  ---
It just happened again - same symptoms:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4f2e614900 (LWP 7649))]

Thread 4 (Thread 0x7f4f06157700 (LWP 7652)):
#0  0x7f4f2ded151d in read () at /lib64/libc.so.6
#1  0x7f4f22cfd670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4f22cbce49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4f22cbd2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4f22cbd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f4f281b132b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f4f2815efdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f4f27f99f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f4f27f9e9e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4f23844734 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4f2deddd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4f150ec700 (LWP 7651)):
#0  0x7f4f2ded549d in poll () at /lib64/libc.so.6
#1  0x7f4f22cbd314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4f22cbd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4f281b132b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4f2815efdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4f27f99f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f4f285c51d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f4f27f9e9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f4f23844734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4f2deddd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f4f16c77700 (LWP 7650)):
#0  0x7f4f2ded549d in poll () at /lib64/libc.so.6
#1  0x7f4f20c873e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f4f20c88fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f4f191d1839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f4f27f9e9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f4f23844734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4f2deddd3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4f2e614900 (LWP 7649)):
[KCrash Handler]
#6  0x7f4f04ee3270 in Konsole::Session::isRunning() const () at
/usr/lib64/libkonsoleprivate.so.16
#7  0x7f4f051c26f9 in  () at /usr/lib64/qt5/plugins/konsolepart.so
#8  0x7f4f2e2363ff in  () at /usr/lib64/libkdeinit5_dolphin.so
#9  0x7f4f2912a956 in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#10 0x7f4f290e8e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#11 0x7f4f290ed49a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#12 0x7f4f28160fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#13 0x7f4f29127438 in QWidgetPrivate::show_helper() () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7f4f2912733f in QWidgetPrivate::showChildren(bool) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7f4f2912740f in QWidgetPrivate::show_helper() () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7f4f2912a007 in QWidget::setVisible(bool) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f4f29211948 in  () at /usr/lib64/libQt5Widgets.so.5
#18 0x7f4f2818abb1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#19 0x7f4f290df892 in QAction::triggered(bool) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f4f290e242d in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQt5Widgets.so.5
#21 0x7f4f2818b1c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#22 0x7f4f290df892 in QAction::triggered(bool) () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7f4f290e242d in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQt5Widgets.so.5
#24 0x7f4f290e25f4 in QAction::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7f4f290e8e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#26 0x7f4f290ed49a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#27 0x7f4f28160fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#28 0x7f4f2896148f in QShortcutMap::dispatchEvent(QKeyEvent*) () at
/usr/lib64/libQt5Gui.so.5
#29 0x7f4f28961554 in QShortcutMap::tryShortcut(QKeyEvent*) () at
/usr/lib64/libQt5Gui.so.5
#30 0x7f4f2891dd7b in QWindowSystemInterface::handleShortcutEvent(QWindow*,
unsigned long, int, QFlags, unsigned int, unsigned int,
unsigned int, QString const&, bool, unsigned short) () at
/usr/lib64/libQt5Gui.so.5
#31 0x7f4f289324d7 in

[dolphin] [Bug 376203] New: Dolphin (or terminal ?) crashed when trying to open it as sub-window in dolphin (F4)

[Martin Jost]

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

Bug ID: 376203
   Summary: Dolphin (or terminal ?) crashed when trying to open it
as sub-window in dolphin (F4)
   Product: dolphin
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: nos...@majo.name
  Target Milestone: ---

Application: dolphin (16.08.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
I tried to open a terminal, using [F4]

- Unusual behavior I noticed:
The terminal opened (very) shortly and then closed again. (Just a sort of
flicker)
I tried this several times, after some tries dolphoin crashed with this info.
I have already seen this behaviour (terminal closes immediately) before, but no
crash.

When I retried another time, it didn't hapen; "even" not when going to the same
directory I had been in.

BUT: Suddenly the terminal now stays open (as expected)
This now also works again for the next dolphin I started.

(Don't know if thsi is helpful, given the fact, that the crash occured just
once)

The crash does not seem to be reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe6dd163900 (LWP 5837))]

Thread 4 (Thread 0x7fe6b4ca6700 (LWP 5842)):
#0  0x7fe6dca2051d in read () at /lib64/libc.so.6
#1  0x7fe6d184c670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe6d180be49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe6d180c2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fe6d180c42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fe6d6d0032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fe6d6cadfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fe6d6ae8f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fe6d6aed9e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe6d2393734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe6dca2cd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fe6bfb7e700 (LWP 5839)):
#0  0x7fe6dca2449d in poll () at /lib64/libc.so.6
#1  0x7fe6d180c314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe6d180c42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe6d6d0032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe6d6cadfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe6d6ae8f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe6d71141d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fe6d6aed9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fe6d2393734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fe6dca2cd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fe6c57c6700 (LWP 5838)):
#0  0x7fe6dca2449d in poll () at /lib64/libc.so.6
#1  0x7fe6cf7d63e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fe6cf7d7fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fe6c7d20839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fe6d6aed9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fe6d2393734 in start_thread () at /lib64/libpthread.so.0
#6  0x7fe6dca2cd3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe6dd163900 (LWP 5837)):
[KCrash Handler]
#6  0x7fe6af91f270 in Konsole::Session::isRunning() const () at
/usr/lib64/libkonsoleprivate.so.16
#7  0x7fe6afbfe6f9 in  () at /usr/lib64/qt5/plugins/konsolepart.so
#8  0x7fe6dcd853ff in  () at /usr/lib64/libkdeinit5_dolphin.so
#9  0x7fe6d7c79956 in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#10 0x7fe6d7c37e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#11 0x7fe6d7c3c49a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#12 0x7fe6d6caffc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#13 0x7fe6d7c76438 in QWidgetPrivate::show_helper() () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7fe6d7c7633f in QWidgetPrivate::showChildren(bool) () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7fe6d7c7640f in QWidgetPrivate::show_helper() () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7fe6d7c79007 in QWidget::setVisible(bool) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7fe6d7d60948 in  () at /usr/lib64/libQt5Widgets.so.5
#18 0x7fe6d6cd9bb1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#19 

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

[Wolfgang Bauer]

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

--- Comment #27 from Wolfgang Bauer  ---
(In reply to orbayo from comment #26)
> The same problem happens when you install fonts in ubuntu (unity), linux
> mint 18 KDE and also linux mint 18 MATE, then the problem does not seem to
> be KDf 5. I think the problem is the kernel, versions 4 or higher . With
> openSUSE and a v3 kernel, it never happened to me.

No, this is definitely not related to the kernel.

That it never happened to you in openSUSE is likely because you were using KDE4
then.

And the current problems are tracked in other bug reports anyway, see
comment#23.

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

[kmail2] [Bug 376202] New: Emails are moved to folders on read, without explanation

[Olivier Churlaud]

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

Bug ID: 376202
   Summary: Emails are moved to folders on read, without
explanation
   Product: kmail2
   Version: 5.4.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: oliv...@churlaud.com
  Target Milestone: ---

When I click on emails, they sometimes move to a given folder (always the same)
even if the emails are from another account. 

I cannot reproduce this all the time. Sometimes it will move 1 sometimes
several emails.

I don't know what trace I can give you. I put critical, because with the number
of email I've got, it is the same as losing them, which is not acceptable.

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

[konsole] [Bug 376200] New: Konsole crash when closing all tabs from one terminal that was initially detached

[Roger]

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

Bug ID: 376200
   Summary: Konsole crash when closing all tabs from one terminal
that was initially detached
   Product: konsole
   Version: 16.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: or...@yahoo.com
  Target Milestone: ---

Application: konsole (16.08.1)

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.13-100.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed: closing all tabs in a terminal
that was initially created from deattaching a tab from another terminal.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f82d274a940 (LWP 14608))]

Thread 3 (Thread 0x7f82c331d700 (LWP 14613)):
#0  0x7f82e0df30e4 in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7f82e0dd9b72 in poll () from /lib64/libc.so.6
#2  0x7f82dcfb918c in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f82dcfb929c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f82e1bceefb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f82e1b7f38a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f82e19dfbb4 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f82e6d22675 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#8  0x7f82e19e3fec in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f82df7ab61a in start_thread () from /lib64/libpthread.so.0
#10 0x7f82e0de55fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f82b9b2c700 (LWP 14615)):
#0  0x7f82df7b0b20 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f82c1892e43 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7f82c1892597 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7f82df7ab61a in start_thread () from /lib64/libpthread.so.0
#4  0x7f82e0de55fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f82d274a940 (LWP 14608)):
[KCrash Handler]
#6  0x7f82e2695d1d in QAction::~QAction() () from /lib64/libQt5Widgets.so.5
#7  0x7f82e2695e39 in QAction::~QAction() () from /lib64/libQt5Widgets.so.5
#8  0x7f82e1bae2a5 in QObjectPrivate::deleteChildren() () from
/lib64/libQt5Core.so.5
#9  0x7f82e26e0564 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5
#10 0x7f82e28278b9 in QMenu::~QMenu() () from /lib64/libQt5Widgets.so.5
#11 0x7f82e1ba89f8 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#12 0x7f82e26e4d0b in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#13 0x7f82e282d8c3 in QMenu::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#14 0x7f82e269f3cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#15 0x7f82e26a4906 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#16 0x7f82e1b8051a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f82e1b8253a in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7f82e1bcee63 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7f82dcfb8e5a in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f82dcfb91f0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#21 0x7f82dcfb929c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f82e1bceedf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f82e1b7f38a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f82e1b86d0c in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x7f82e6a39f45 in kdemain () from /lib64/libkdeinit5_konsole.so
#26 0x7f82e0d03580 in __libc_start_main () from /lib64/libc.so.6
#27 0x5589dc50aae9 in _start ()

Possible duplicates by query: bug 370211.

Reported using DrKonqi

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

[plasmashell] [Bug 376201] New: plasmashell crash

[Dmitry]

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

Bug ID: 376201
   Summary: plasmashell crash
   Product: plasmashell
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: goldedra...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.1)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.8-1-zen x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Plasmashell crashed every time after login quasiperiodically

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7fe4e4e40700 (LWP 13084)):
#0  0x7fe5dde4910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5def7958b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5e2cd5665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5e2cd5f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fe4e6868700 (LWP 12477)):
#0  0x7fe5dde4910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5def7958b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5e2cd5665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5e2cd5f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fe4e75ef700 (LWP 12476)):
#0  0x7fe5dde4910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5def7958b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5e2cd5665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5e2cd5f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fe4f9988700 (LWP 12472)):
#0  0x7fe5dde4910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5def7958b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5e2cd5665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5e2cd5f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fe50131b700 (LWP 12470)):
#0  0x7fe5de88448d in poll () at /usr/lib/libc.so.6
#1  0x7fe5d95b92fe in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe5d95b942c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe5df1a846b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe5df151c9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe5def73a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe503bed0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fe51d2a8700 (LWP 12467)):
#0  0x7fe5dde4910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5def7958b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5e2cd5665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5e2cd5f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5def786d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5dde43454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5de88d7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fe51e7ec700 (LWP 12463)):
#0  0x7fe5de8804ed in read () at /usr/lib/libc.so.6
#1  0x7fe5d667df55 in  () at /usr/lib/libnvidia-tls.so.340.101
#2  0x7fe5d960d3d0 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe5d95b8df6 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x7fe5d95b92a4 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fe5d95b942c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#6  0x7fe5df1a846b in

[partitionmanager] [Bug 376189] Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server

[Buck Shockley]

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

--- Comment #2 from Buck Shockley  ---
Running it with sudo causes the problem to not occur. If it helps, running it
normally gives me a prompt from KDE su. This is the command it says is being
executed:

KDE_FULL_SESSION=true XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/partitionmanager
--dontsu

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

[plasmashell] [Bug 376199] New: task manager and digital clock plasmoids do not work with Qt5.6 because of missing QtQuick2.7 dependency

[rindeal]

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

Bug ID: 376199
   Summary: task manager and digital clock plasmoids do not work
with Qt5.6 because of missing QtQuick2.7 dependency
   Product: plasmashell
   Version: 5.9.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: dev.rindeal+bugs.kde@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

After I upgraded KDE Plasma from 5.8.x to 5.9.0, I quickly noticed that the
digital clock and taskbar plasmoids stopped working. Hovering over them told me
that QtQuick 2.7 is missing. So I grepped over all plasmoids and it revealed
that these files:

   
/usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml
   
/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml
   
/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml

contain line:

import QtQuick 2.7

So I used in-place sed to change it to:

import QtQuick 2.6

and it started working again.


Commits that introduced QtQuick 2.7:

for digital clock:
https://github.com/KDE/plasma-workspace/commit/1d362c4ae2e264a80c002ab6718c1b1d9437c20c

for task manager:
https://github.com/KDE/plasma-desktop/commit/4f9198fc5f21334b989575c3d9891254d0b1e185


Btw is the minimal Qt version still 5.5 as noted here -
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/OwnQt5#Use_Qt5_Distribution_Packages?

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

[kdevplatform] [Bug 374458] Crash when dragging launches in Launch Configuration

[Aetf]

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

--- Comment #3 from Aetf <7437...@gmail.com> ---
I just tested on the latest 5.1 branch. They are not draggable any more. IMO
that makes sense because launches are associated with one project and there's
no point to drag them around.

Francis, can you reproduce this now?

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

[plasmashell] [Bug 375934] Invisible airplane icon

[Muto Lachen]

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

--- Comment #4 from Muto Lachen  ---
(In reply to Kai Uwe Broulik from comment #2)
> Can you create a screenshot? I can't reproduce the issue here. Neither when
> using Breeze Dark Plasma theme nor when just changing the color scheme to be
> dark. Thanks!

Added screenshot, not too much information, but it should give you an idea of
the problem, thank you.

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

[plasmashell] [Bug 375934] Invisible airplane icon

[Muto Lachen]

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

--- Comment #3 from Muto Lachen  ---
Created attachment 103907
  --> https://bugs.kde.org/attachment.cgi?id=103907=edit
Screenshot of problem

This is what happens when I switch to Breeze Dark, it's like this after a
reboot, as well.

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

[plasmashell] [Bug 376185] Transparency lost in Conky on update to plasma 5.9.1

[Barry Kaplan]

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

--- Comment #2 from Barry Kaplan  ---
(In reply to Kai Uwe Broulik from comment #1)
> You don't seem to have compositing enabled. Can you press Alt+Shift+F12 and
> see if it works then. Also check System Settings -> Display -> Compositor
> whether there's a warning and whether the "Enable compositing on startup" is
> checked.

Hi, Kai. Thanks for your reply.

Alt+Shift+F12 did not work; however, as you thought, when I checked System
Settings -> Display -> Compositor, there was a warning ("OpenGL compositing
(the default) has crashed KWin in the past. This was most likely due to a
driver bug"). I re-enabled OpenGL and rebooted, which did remedy the issue.
It seems stable for now.

I'm not sure why compositing crashed after the plasma update, but perhaps it
was localized to my machine and no-one else will have the issue.

In any event, thanks very much for your assistance and I'm sorry to have
troubled you with this.

Barry

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

[kdenlive] [Bug 375520] kdenlive problem for composite and affine, i change dimension of clip image, but bad result.

[bugzilla_noreply]

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

--- Comment #12 from manuel_songo...@yahoo.it ---
hi

now i CAN compiled last kdenlive from git clone and merge
(refactoring_timeline) for testing..or only master/head ?

let me know as soon thank you
kdenlive compiled Version 17.03.70

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Stefan]

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

Stefan  changed:

   What|Removed |Added

 CC|stefan.bul...@gmail.com |

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

[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display

[Thomas Weissel]

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

--- Comment #17 from Thomas Weissel  ---
Unfortunately i have to report that in 5.9.1 this is NOT fixed :)  

plasma behaves as follows: (starting with a blank new setup)

there is only one containment in  plasma-org.kde.plasma.desktop-appletsrc

[Containments][1]
activityId=86868fa6-a85a-4e74-a8d2-8abda1d6ae3e
formfactor=0
immutability=1
lastScreen=0
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image


>> Then i add an Applet - the applet part gets added to the config file to 
>> containment [1]



>> Then i attach a beamer - a new containment [21] is added to the config file:
(the beamer is placed right of the mainscreen with the maincontainment)




>> then i "clone" the two screens by using xrandr (or the kscreen configuration 
>> tool (it doesn't matter)) and the containment [21] covers containment [1]  
>> -> all widgets are hidden.


hitting alt+tab (with no applications open) still makes the switch to the
maincontainment

rebooting the system always shows the unconfigured new containment :-(

this is a real showstopper..


bug still there or did the patch miss 5.9.1 ?

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[RJVB]

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

--- Comment #136 from RJVB  ---
(In reply to Sebastian Kügler from comment #135)
> Quite simply, we're not looking for a solution, the right solution has been
> proposed already. Someone needs to sit down and do the work, it's *that*
> simple. 

There's a small difference between a proposed difference and one that only
needs to be implemented from full draft, but above all it would have been
useful to paste a pointer to that proposal here. Clearly not everyone is aware
of its existence.

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

[KScreen] [Bug 374708] Confusing design of Resolution slider (need redisign)

[Laptander]

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

--- Comment #3 from Laptander  ---
By the way, maybe we should just make a dropdown list (like on windows) instead
of slider?
See attached video, it demonstrates windows' interface for changing display
resolution.

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

[KScreen] [Bug 374708] Confusing design of Resolution slider (need redisign)

[Laptander]

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

--- Comment #2 from Laptander  ---
Created attachment 103906
  --> https://bugs.kde.org/attachment.cgi?id=103906=edit
Windows 10 display settings (change resolution and switch displays with dual
head)

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

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

[orbayo]

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

--- Comment #26 from orbayo  ---
The same problem happens when you install fonts in ubuntu (unity), linux mint
18 KDE and also linux mint 18 MATE, then the problem does not seem to be KDf 5.
I think the problem is the kernel, versions 4 or higher . With openSUSE and a
v3 kernel, it never happened to me.

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

[kwin] [Bug 343690] Missing windows tabbing

[john]

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

john  changed:

   What|Removed |Added

 CC||johnmaveric...@mail.com

--- Comment #17 from john  ---
I'm really missing this!!! It helps a lot to keep work organized!!!

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

[kaffeine] [Bug 376198] New: Slow start of kaffeine

[bugzilla_noreply]

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

Bug ID: 376198
   Summary: Slow start of kaffeine
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: yuli...@mailbox.org
  Target Milestone: ---

Hello,
kaffeine (compiled from the actual git) starts very slow on my computer, it
takes around 12 seconds, although it has 4 cores á 2.6 GHz and 4 GB RAM. As it
starts immediately if I create a new profile, and as there are many messages
about the EPG if I start it with the debug parameter, I suspect that the EPG
somehow slows it down. I remember a bug report where it was written that the
EPG code could be optimized more in order to speed up. Can't find it, though.
Anyway this is meant just as a reminder, and only for the "wish-list". Thanks.
:)

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

[krita] [Bug 376197] Flattening an animation layer with a color filter is VERY SLOW

[Bollebib]

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

--- Comment #1 from Bollebib  ---
just now i did a flatten layer operation that took 5 minuts at least

=(

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

[Stefan]

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

Stefan  changed:

   What|Removed |Added

 CC||bubi1...@antispam.de

--- Comment #67 from Stefan  ---
I've the same problem with following configuration:
* Synology DS216j (CalDAV and WebDAV --> CardDAV)
* KDE Neon User Edition (current updates installed)
* KOrganizer 5.4.1

Neither calendar nor contact items are showen in KOrganizer (Part of KDE
Kontact).

Current Thunderbird works.

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

[krita] [Bug 376197] New: Flattening an animation layer with a color filter is VERY SLOW

[Bollebib]

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

Bug ID: 376197
   Summary: Flattening an animation layer with a color filter is
VERY SLOW
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kwadraatn...@hotmail.com
  Target Milestone: ---

I use a HSV filter to colorize a grey butterfly on a range of frames (+100)
and this seems to take about 1-2 minutes on a very good machine.
This seems like overkill,but at least it doesnt have bugs like transform masks.

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

[Akonadi] [Bug 345211] mails in ~/.local/share/local-mail don't show up any more

[m . eik michalke]

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

--- Comment #3 from m.eik michalke  ---
i just wanted to open a new bug ticket when i found this old one i opened
almost two years ago.

so here we are again, but the other way around: i can see all my local mail in
kmail (version 16.04.3), but ~/.local/share/local-mail itself is almost empty.
when i create a new folder in kmail, it is also being created on disk in that
folder. if i copy mails in kmail, they are written to that folder as single
files. but if i move mails (not copying), kmail shows then in their new
location, but nothing appears in the file system.

kmail says the local mail resource holds ~6GB of mails. i can browse the
folders in kmail and open mails without problems. however, only a tiny fraction
of those mails can be found in ~/.local/share/local-mail which is only ~200MB
of size. where does kmail store my mails on disk? the have to be somewhere,
right?

the symptoms are somehow similar to what i wrote two years ago, as today, kmail
suddenly "forgot" all folder settings for one of my IMAP accounts, including
all mail filter destination folders. and this happened on two different
machines with the same IMAP account, while on both other IMAP accounts were not
affected.

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

[krita] [Bug 376179] fuzzy dynamic is not influenced by "strength"

[Bollebib]

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

--- Comment #2 from Bollebib  ---
(In reply to wolthera from comment #1)
> Fuzzy dab is affected by the curve here, but not by the strength, no.

yes, i made a mistake earlier in my config,you are correct,it does work with
curves

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

[kaffeine] [Bug 376196] New: Some windows in kaffeine have "OK" and "Cancel" instead of just "Close".

[bugzilla_noreply]

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

Bug ID: 376196
   Summary: Some windows in kaffeine have "OK" and "Cancel"
instead of just "Close".
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: yuli...@mailbox.org
  Target Milestone: ---

Hello, 
I think since kaffeine is adjusted to KF5 (so from kaffeine 2 on), there are
some windows (e.g. the EPG window and the program schedule next to it) that
show the possibilities to "Cancel" and "OK". But there is no difference between
pressing "Cancel" and "OK", so if you e.g. plan a record and press afterwards
cancel, the record is saved nonetheless. This is a bit confusing. I think in
earlier versions those windows just had a "Close" button. Thanks. :)

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

[kuser] [Bug 376157] kf5 kuser

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
I do not understand. The Plasma user KCM does not use gobjects or GTK. I
suggest to report it as a bug to your distribution.

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

[kaffeine] [Bug 376195] New: Muting kaffeine works, but the next start it's still muted, although the symbol does not show this.

[bugzilla_noreply]

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

Bug ID: 376195
   Summary: Muting kaffeine works, but the next start it's still
muted, although the symbol does not show this.
   Product: kaffeine
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: yuli...@mailbox.org
  Target Milestone: ---

Hello, 
just a minor bug I found in the Git version of kaffeine (probably also valid
for older versions). Í watch TV and everything works great, and if I press
mute, the sound is gone and the symbol changes to the speaker symbol with the
cross. Now I close kaffeine and start it again. There is no sound, although the
symbol shows not the cross. To hear sound I have to mute first and then remove
the mute again. This was pretty confusing and it would be nice to see this
fixed. Thank you.

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

[drkonqi] [Bug 370267] pt-br translation cut off in crash notification

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

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

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

[Discover] [Bug 376194] New: Text out of margins

[bugzilla_noreply]

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

Bug ID: 376194
   Summary: Text out of margins
   Product: Discover
   Version: 5.6.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: da...@ifisc.uib-csic.es
  Target Milestone: ---

Created attachment 103905
  --> https://bugs.kde.org/attachment.cgi?id=103905=edit
Screen shoot of the window application

In the home page of Discover the text of the suggested application extend out
of the margins of their window, giving a very awkward look.

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

[drkonqi] [Bug 370267] pt-br translation cut off in crash notification

[Burkhard Lueck]

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

--- Comment #4 from Burkhard Lueck  ---
If this issue is solved for you in plasma 5.9 please change the status of this
bug to Resolved -> Fixed.
I rarely see the drkonqui dialog to check if the string in question is
completely visible
Thanks

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

[kaffeine] [Bug 375811] how fix kaffeine for dvb-t ?!

[bugzilla_noreply]

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

yuli...@mailbox.org changed:

   What|Removed |Added

 CC||yuli...@mailbox.org

--- Comment #1 from yuli...@mailbox.org ---
If it stops working after a kernel update, maybe the problem is the kernel and
not kaffeine. But Mauro Carvalho Chehab maybe knows.

Which kernel version is the last version that worked and which version is the
first version that failed (4.9.5-200.fc25.x86_64)?

And you seem to use Fedora, so maybe (just a guess) it is fixed in Linux kernel
4.10, which you could test. This is pretty easy on Fedora [1]. So if you
understand the commands on the wiki page, you could install e.g. Linux 4.10 RC7
as a test, maybe it works there. Let us know, if there is any change.

If it is not fixed there, you should probably file a bug on 
https://bugzilla.kernel.org/


[1] https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories

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

[kmail2] [Bug 362803] Can't change KMail Message List font size with custom font settings.

[Maurice Batey]

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

--- Comment #12 from Maurice Batey  ---
> Committed on 17/01/2017 at 12:13.
> Pushed by mlaurent into branch 'Applications/16.12'.

Anyone know which version of Kmail this will be applied to, please?

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

[plasmashell] [Bug 376185] Transparency lost in Conky on update to plasma 5.9.1

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
You don't seem to have compositing enabled. Can you press Alt+Shift+F12 and see
if it works then. Also check System Settings -> Display -> Compositor whether
there's a warning and whether the "Enable compositing on startup" is checked.

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