[kontact] [Bug 372942] New: Kontact frequently crashes upon startup

[bugzilla_noreply]

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

Bug ID: 372942
   Summary: Kontact frequently crashes upon startup
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: hauser.el...@gmx.de
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

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

-- Information about the crash:
- What I was doing when the application crashed:
Either scrolling through the mail list or trying to open a message.

The crash can be reproduced every time.

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

Thread 32 (Thread 0x7f41ca745700 (LWP 3184)):
#0  0x7f42dd471ec4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f42dd42c71d in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f42dd42c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f42e2d10aab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f42e2cb86fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f42e2ade3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f42e2ae32e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f42de080454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f42e21db39f in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f41cb9fb700 (LWP 3181)):
#0  0x7f42e21d268d in poll () at /lib64/libc.so.6
#1  0x7f42dd42c876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f42dd42c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f42e2d10aab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f42e2cb86fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f42e2ade3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f42e2ae32e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f42de080454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f42e21db39f in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f41cc77c700 (LWP 3173)):
#0  0x7f42de08610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f42d5805d49 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f42d5806460 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f42d5806630 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f42d580323d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f42de080454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f42e21db39f in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f41cf214700 (LWP 3156)):
#0  0x7f42e21d268d in poll () at /lib64/libc.so.6
#1  0x7f42dd42c876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f42dd42c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f42e2d10aab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f42e2cb86fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f42e2ade3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f42e2ae32e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f42de080454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f42e21db39f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f41cfa15700 (LWP 3154)):
#0  0x7f42e2adb009 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f42e2d102a9 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f42dd42c269 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f42dd42c814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f42dd42c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f42e2d10aab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f42e2cb86fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f42e2ade3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f42e2ae32e8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f42de080454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f42e21db39f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f41d2e00700 (LWP 3149)):
#0  0x7f42e2adb013 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f42e2d1013f in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f42dd42bd79 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f42dd42c79b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f42dd42c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f42e2d10aab in

[kate] [Bug 372208] kwrite File -> New directory fails to follow current, defaults to $HOME

[David Rankin]

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

--- Comment #1 from David Rankin  ---
This occurs with both kate and kwrite. When you open a new session in kate (or
a file in kwrite) and save a source file at $HOME/prg/src-c/tmp/debug. If you
then create a new document (ctrl+n) and attempt to save the second file.
Instead of offering to save the document in the directory where the first file
was just saved, kate/kwrite defaults to asking to save in $HOME, instead of in
$HOME/prg/src-c/tmp/debug. This requires that you again navigate to the
directory of interest. That is unexpected behavior.

Similarly, if you use dolphin or konqueror to navigate and open a file in
kwrite (or kate, depending on you file association order set in file
properties), then 'save-as' in a new directory, kwrite or kate will always
default to saving all new documents created with (ctrl+n) to the directory
where the first file was opened, completely ignoring the directory where the
most recent file was saved. This seems to be the same failure to update the
directory information based on the last save.

For more than a decade I've used kate/kwrite and I have never had a problem
with them not remembering and following the last saved directory. This should
be common to the file save dialog in KDE, not just kate/kwrite, but it is very
much a problem when dealing with multiple source files in a highly nested
directory structure. This is occurring with:

Kate/Kwrite Versions 16.08.3
Kate Part version 5.28

KDE Frameworks 5.28.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

Let me know if you need any additional information, I'm happy to provide
anything needed to help get this fixed. This, along with the other handful of
bugs I've filed recently, are the top annoyances I find in trying to use
Plasma/FW5, moving from KDE3. These very simple things, that have always just
worked correctly in KDE, are what made KDE so wonderfully efficient and a joy
to use. It is very notable when these things don't work. I'm committed to
helping make Plasma/FW5 as efficient and enjoyable to use as KDE3, but the
simple things that make KDE KDE, really need to work. There is no reason anyone
should ever have to repeatedly click down a 10 component directory path just to
save a file in the same location.

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

[digikam] [Bug 361848] When writing metadata to files is disabled, digikam still displays "Writing metadata to files"

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0

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

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.0.0   |5.4.0

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

[digikam] [Bug 372900] When starting Digikam5, it crashes before opening the program, but after the splash screen.

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
My previous comment is a question of course. Can you reproduce the problem with
AppImage bundle for Linux ?

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

[digikam] [Bug 372900] When starting Digikam5, it crashes before opening the program, but after the splash screen.

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
This problem is reproducible using digiKam AppImage bundle 5.4.0 pre release
available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[marble] [Bug 372941] New: Map Rotation

[Victor Tran]

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

Bug ID: 372941
   Summary: Map Rotation
   Product: marble
   Version: unspecified
  Platform: Android
OS: Android 5.x
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android
  Assignee: marble-b...@kde.org
  Reporter: victor.tr...@live.com
  Target Milestone: ---

Rotation of the map would be really good, especially during navigation, because
if the vehicle is moving south, the directions can be very confusing.

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

[marble] [Bug 372940] New: Night mode

[Victor Tran]

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

Bug ID: 372940
   Summary: Night mode
   Product: marble
   Version: unspecified
  Platform: Android
OS: Android 5.x
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android
  Assignee: marble-b...@kde.org
  Reporter: victor.tr...@live.com
  Target Milestone: ---

A night mode would be good (at least during navigation) so that the phone does
not shine into the vehicle.

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

[marble] [Bug 372939] New: Rerouting can become annoying

[Victor Tran]

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

Bug ID: 372939
   Summary: Rerouting can become annoying
   Product: marble
   Version: unspecified
  Platform: Android
OS: Android 5.x
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: android
  Assignee: marble-b...@kde.org
  Reporter: victor.tr...@live.com
  Target Milestone: ---

When you deviate from the route, Marble says "deviated from the route" and
reroutes you. However, this does not take into account the direction that the
user is currently moving, thus if it decides that the best route from there is
to go backwards, it will reroute, and then immediately say "deviated from the
route" again, until either the user turns around, or the routing system finds a
better route.

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

[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin  ---
Please provide the output of
qdbus org.kde.KWin /KWin supportInformation

If you are able please gdb into the hung KWin and provide a backyard of all
threads. Of course I don't see this problem...

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

[karbon] [Bug 326258] Calligra crashed when editing file

[Anthony]

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

Anthony  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||bvb...@abv.bg

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

[karbon] [Bug 326258] Calligra crashed when editing file

[Anthony]

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

--- Comment #2 from Anthony  ---
Git commit f3f26b78c7b792e9f5de480d2fd00c98a48d8ba2 by Anthony Fieroni.
Committed on 26/11/2016 at 05:32.
Pushed by anthonyfieroni into branch 'master'.

[connectionTool] Check dynamic_cast result pointer

REVIEW: 129514

Signed-off-by: Anthony Fieroni 

M  +4-1plugins/defaultTools/connectionTool/ConnectionTool.cpp

https://commits.kde.org/calligra/f3f26b78c7b792e9f5de480d2fd00c98a48d8ba2

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

[skrooge] [Bug 372938] New: merge imported operations wrong warning about different amounts

[Aaron Wolf]

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

Bug ID: 372938
   Summary: merge imported operations wrong warning about
different amounts
   Product: skrooge
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: wolft...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

I had a split entry that had several categories, when I tried to merge that
with the corresponding imported operation, I got a warning asking about forcing
the merge since the amounts were different. But the amounts were exactly the
same.

I'm using Skrooge 2.5 in KDE Neon.

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

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[Curtis Seizert]

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

--- Comment #19 from Curtis Seizert  ---
Forgot to turn off stripping the binaries!  Here's another backtrace:

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

Thread 15 (Thread 0x7f22c88a7700 (LWP 5315)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f22cef7f700 (LWP 4268)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f22d039f700 (LWP 4264)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f22de7fd700 (LWP 4218)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f22deffe700 (LWP 4202)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f22d8c5e700 (LWP 4183)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f22eb4cb700 (LWP 4182)):
#0  0x7f23bb6b548d in poll () at /usr/lib/libc.so.6
#1  0x7f23b6977786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f23b697789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f23bbfd772b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f23bbf8123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f23bbda40f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f22e9dbe0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f230d00e700 (LWP 4010)):
#0  0x7f23baebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23bbda9c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23bfd12395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23bfd12c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23bbda8d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23baeb8454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23bb6be7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f230c80d700 (LWP 3995)):
#0  0x7f23bb6b14ed in read () at 

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[Curtis Seizert]

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

--- Comment #18 from Curtis Seizert  ---
I built plasma-workspace with -DCMAKE_BUILD_TYPE=RelWithDebInfo (the crash
handler would not launch with the Debug option) and plamsa-desktop with
-DCMAKE_BUILD_TYPE=Debug.  The backtrace seems the same to me, so please let me
know what else I might do.



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

Thread 15 (Thread 0x7f22e4cdd700 (LWP 4773)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f22da36f700 (LWP 4240)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f22daf7f700 (LWP 4236)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f22e56de700 (LWP 4189)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f22e5edf700 (LWP 4188)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f22e7530700 (LWP 4159)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f23113fe700 (LWP 4156)):
#0  0x7f23c8d6348d in poll () at /usr/lib/libc.so.6
#1  0x7f23c4025786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f23c402589c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f23c968572b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f23c962f23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f23c94520f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f22f86170a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f23c8566454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f23c8d6c7df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f231a684700 (LWP 4062)):
#0  0x7f23c856c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23c9457c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f23cd3c0395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f23cd3c0c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f23c9456d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23c8566454 in start_thread 

[kdevelop] [Bug 372937] New: kdevelop crashes when removing breakpoint

[Evgeny]

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

Bug ID: 372937
   Summary: kdevelop crashes when removing breakpoint
   Product: kdevelop
   Version: 4.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: xeng...@mail.ru
  Target Milestone: ---

Application: kdevelop (4.7.3)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.8.0-28-generic x86_64
Distribution: Ubuntu 16.10

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

After several debugging sessions removing a breakpoint causes crash.
GDB: GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git
GCC: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
binutils: 2.27-8ubuntu2

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f252db0d900 (LWP 15304))]

Thread 21 (Thread 0x7f241f7fe700 (LWP 17521)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f252a8e23a6 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x203afb0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7f252066c180 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740,
th=0x90c4e20) at ./threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fe7d00, th=0x90c4e20, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x90c4e20) at
./threadweaver/Weaver/Thread.cpp:98
#6  0x7f252a8e1e3c in QThreadPrivate::start (arg=0x90c4e20) at
thread/qthread_unix.cpp:352
#7  0x7f25267076ca in start_thread (arg=0x7f241f7fe700) at
pthread_create.c:333
#8  0x7f252a2200af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 20 (Thread 0x7f241700 (LWP 17520)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f252a8e23a6 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x203afb0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7f252066c180 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740,
th=0x8a78670) at ./threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fe7d00, th=0x8a78670, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x8a78670) at
./threadweaver/Weaver/Thread.cpp:98
#6  0x7f252a8e1e3c in QThreadPrivate::start (arg=0x8a78670) at
thread/qthread_unix.cpp:352
#7  0x7f25267076ca in start_thread (arg=0x7f241700) at
pthread_create.c:333
#8  0x7f252a2200af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7f2424d75700 (LWP 15950)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f252a8e23a6 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x203afb0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7f252066c180 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740,
th=0x1ed5940) at ./threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fe7d00, th=0x1ed5940, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7f252066e9fc in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fe7d00, th=0x1ed5940, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7f252066e9fc in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fe7d00, th=0x1ed5940, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:71
#7  0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x1ed5940) at
./threadweaver/Weaver/Thread.cpp:98
#8  0x7f252a8e1e3c in QThreadPrivate::start (arg=0x1ed5940) at
thread/qthread_unix.cpp:352
#9  0x7f25267076ca in start_thread (arg=0x7f2424d75700) at
pthread_create.c:333
#10 0x7f252a2200af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7f2456768700 (LWP 15949)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[Curtis Seizert]

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

--- Comment #17 from Curtis Seizert  ---
I'll rebuild with debugging symbols.  Give me an hour or so.

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

[plasmashell] [Bug 372936] New: Plasma crashing every time I use search

[George Diamantopoulos]

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

Bug ID: 372936
   Summary: Plasma crashing every time I use search
   Product: plasmashell
   Version: 5.8.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: georged...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

-- Information about the crash:
I was typing a search string into K menu. Plasma crashes 99% of the time when I
do that. It also crashes when the search is performed in Plasma search widget
(Alt+F2).

This behaviour has been manifesting for quite some time (several months), but
only now have I decided it was annoying enough to recompile everything with
debugging symbols and issue this report.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
allocator_get_magazine_threshold (allocator=0x7f68735af2a0 ,
allocator=0x7f68735af2a0 , ix=) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gslice.c:583
[Current thread is 1 (Thread 0x7f687c9cf840 (LWP 3465))]

Thread 23 (Thread 0x7f676bfff700 (LWP 13886)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6877b43c1a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4e0e8f0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3cc0c30,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f67c07b559b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x29c4fa0, th=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:594
#4  0x7f67c07b63f0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x29c4fa0,
th=, th@entry=0x7f6778002990,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:554
#5  0x7f67c07ba408 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4752830, th=0x7f6778002990, wasBusy=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/workinghardstate.cpp:66
#6  0x7f67c07b5509 in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6778002990, wasBusy=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:568
#7  0x7f67c07ba452 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4752830, th=0x7f6778002990, wasBusy=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/workinghardstate.cpp:73
#8  0x7f67c07b5509 in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6778002990, wasBusy=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:568
#9  0x7f67c07b83d9 in ThreadWeaver::Thread::run (this=0x7f6778002990) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/thread.cpp:103
#10 0x7f6877b4360b in QThreadPrivate::start (arg=0x7f6778002990) at
thread/qthread_unix.cpp:344
#11 0x7f6876bf73b4 in start_thread (arg=0x7f676bfff700) at
pthread_create.c:333
#12 0x7f68773f1a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7f6784bb9700 (LWP 13885)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6877b43c1a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4e0e8f0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3cc0c30,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f67c07b559b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x29c4fa0, th=) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:594
#4  0x7f67c07b63f0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x29c4fa0,
th=, th@entry=0x7f676c0027d0,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:554
#5  0x7f67c07ba408 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4752830, th=0x7f676c0027d0, wasBusy=) at

[krunner] [Bug 372017] Krunner chrashes on every input

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cyberan...@gmail.com

--- Comment #6 from Christoph Feck  ---
*** Bug 372784 has been marked as a duplicate of this bug. ***

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

[kontact] [Bug 372803] Kontact crashes on launch

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||kice...@gmail.com

--- Comment #2 from Christoph Feck  ---
*** Bug 372856 has been marked as a duplicate of this bug. ***

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

[kontact] [Bug 372856] Kontact crashes after being launched

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[kontact] [Bug 372803] Kontact crashes on launch

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Crash is in nvidia OpenGL binary drivers. Please report this issue to nvidia
developers.

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

[kmix] [Bug 372792] Change volume via mouse wheel (scrolling) on kmix symbol in smaller steps (e.g. 1% instead 7%)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

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

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #16 from Christoph Feck  ---
Backtrace still has no debug symbols, but it indeed looks like the same crash.
Reopening.

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

[krunner] [Bug 369419] krunner crashes when typing

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Should be fixed by e1692f1a21458986fac18daf6eb1d1037c9d5051

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

[krunner] [Bug 372784] krunner crashes when "Windowed widgets" plugin is enabled

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---


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

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

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[Curtis Seizert]

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

--- Comment #15 from Curtis Seizert  ---
I am still having this problem in 5.8.4.

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

Thread 16 (Thread 0x7fe58a3ee700 (LWP 4476)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fe58abef700 (LWP 4475)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fe5f521f700 (LWP 4200)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fe616b1e700 (LWP 4083)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fe61731f700 (LWP 4079)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fe62f5fd700 (LWP 4074)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fe62fdfe700 (LWP 4073)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fe658ea9700 (LWP 4042)):
#0  0x7fe73562110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe73650cc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe73a475395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe73a475c8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe73650bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe73561b454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe735e217df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fe66d0d4700 (LWP 4040)):
#0  0x7fe735e1848d in poll () at /usr/lib/libc.so.6
#1  0x7fe7310da786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe7310da89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe73673a72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[Breeze] [Bug 372851] programs without rtl lang translation still reverse ui

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED
   Assignee|kwin-bugs-n...@kde.org  |scionicspec...@gmail.com
  Component|general |gtk theme
Product|kwin|Breeze

--- Comment #4 from Christoph Feck  ---
It looks like an issue with Breeze GTK. If not, please close again.

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

[systemsettings] [Bug 372910] System Clock - KDE Clock Crash when trying to authorize to update time zone.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Fixed in Plasma 5.

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

[kde-gtk-config] [Bug 372927] Can't load "local themes" for gnome/gtk applications

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||aleix...@kde.org
Product|systemsettings  |kde-gtk-config
   Assignee|tibi...@kde.org |manutortosa@chakra-project.
   ||org
  Component|kcm_style   |general

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

[kstars] [Bug 372935] After 1 hour of imaging kstars/ekos became unresponsive

[Jasem Mutlaq]

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

--- Comment #1 from Jasem Mutlaq  ---
Did you check memory consumption? Did you have INDI debug enabled to client?
i.e. debug message getting printed in the INDI control panel?

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

[digikam] [Bug 372540] fileSize field in Images table limited to 4GB

[Kusi]

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

Kusi  changed:

   What|Removed |Added

 CC||k...@forum.titlis.org

--- Comment #1 from Kusi  ---
I can confirm that 

ALTER TABLE Images MODIFY COLUMN fileSize BIGINT NULL;

does the trick. Nowadays, it's common to have movies larger than 2G

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

[kstars] [Bug 372926] EKOS crash on opening Control tab. It did render it though.

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kst
   ||ars/043526fe49fef98fee0473a
   ||981ae3d1fad7ced7d
 Resolution|--- |FIXED

--- Comment #1 from Jasem Mutlaq  ---
Git commit 043526fe49fef98fee0473a981ae3d1fad7ced7d by Jasem Mutlaq.
Committed on 26/11/2016 at 00:04.
Pushed by mutlaqja into branch 'master'.

Check for widgt before calling mapFromParent

M  +4-1kstars/fitsviewer/fitsview.cpp

https://commits.kde.org/kstars/043526fe49fef98fee0473a981ae3d1fad7ced7d

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||peter.eszl...@gmail.com

--- Comment #16 from Albert Astals Cid  ---
*** Bug 372899 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 372899] Blurry font with HiDPI and scale factor 2

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Albert Astals Cid  ---


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

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

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

[Simon]

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

--- Comment #17 from Simon  ---
Hi Gilles,

This problem is still the same. I reduced it for me by using internal
mysql database and preloading most of the database to memory.
When testing with appimage, sqlite on system hd and data on separate hd
(no ssl in my laptop :) ), now even the UI gets unresponsive during
writing. Maybe it would be more efficient to remember which files were
written and issue a rescan after writing of metadata is done?
Generally the only issue I have with syncthing is its constant scanning
of stuff on the HD. Whenever I start it causes tons of read access (to
images, not database) producing command line output like
"digikam.dimg***: JPEG file identified" and "digikam.metaengine:
Orientation => Exif.Image.Orientation => 1", as if these files were new
or modified (they are not).

Cheers,
Simon

On 25/11/16 15:38, bugzilla_nore...@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=362023
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #16 from caulier.gil...@gmail.com ---
> What's about this file using digiKam AppImage bundle 5.4.0 pre release given 
> at
> this url :
>
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
>
> Gilles Caulier
>

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

[plasmashell] [Bug 372890] default LVDS is left without widgets

[David Heidelberg]

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

--- Comment #2 from David Heidelberg  ---
When I add default panel on LVDS screen is also present on DVI output when
connected in dockstation.

Can be this logic avoided?

Solution preferably use LVDS setup from screen which include at least >= 1
widgets. Screen which has only background can be ignored when different screen
is used.

Not sure how to manage it in plasmashell logic,

maybe use PRIMARY display widgets when only LVDS is used.

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

[kstars] [Bug 372935] New: After 1 hour of imaging kstars/ekos became unresponsive

[Hans Lambermont]

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

Bug ID: 372935
   Summary: After 1 hour of imaging kstars/ekos became
unresponsive
   Product: kstars
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: h...@lambermont.dyndns.org
  Target Milestone: ---

After imaging about 5*10 min frames kstars became very sluggish up to the point
where it was not responding to anything anymore.
Gnome made the program dark as it's not responding to anything.
Click close button. Window is not responding, force quit ? Yes
Here's a backtrace in the hope that it's helpful


#0  0x7fffec63e730 in xcb_setup_vendor_end () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#1  0x7fffec63e759 in xcb_setup_pixmap_formats () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fffe423f257 in ?? () from
/usr/lib/x86_64-linux-gnu/libxcb-image.so.0
#3  0x7fffe424037e in xcb_image_native () from
/usr/lib/x86_64-linux-gnu/libxcb-image.so.0
#4  0x7fffe424054f in xcb_image_shm_put () from
/usr/lib/x86_64-linux-gnu/libxcb-image.so.0
#5  0x7fffe4eda839 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x7fffe4edac49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x746ad095 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x74ad9a7a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x74ada796 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x74adc8bf in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x74adca8c in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x74afac1f in QWidgetPrivate::syncBackingStore() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x74b11d88 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x74c27d7b in QMainWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x77033147 in KMainWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#16 0x7706b4e5 in KXmlGuiWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#17 0x74acf05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x74ad4516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x74add1bf in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x74adde5d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x74afd612 in QWidget::repaint(QRect const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x74c6e89e in QStatusBar::hideOrShow() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x74c6e94a in QStatusBar::showMessage(QString const&, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x005e2b85 in INDI_D::updateMessageLog (this=0x3b7efe0,
idv=, messageID=)
at
/build/kstars-bleeding-qSmJ00/kstars-bleeding-16.10+201611202010~ubuntu16.04.1/kstars/indi/indidevice.cpp:284
#26 0x73d22c01 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x74b11cdb in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x74acf05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x74ad4516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x73cf5786 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x73d493c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7fffef0fc1a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7fffef0fc400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x7fffef0fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x73d497cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x73cf0b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x73cf8bec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#39 0x00483c23 in main (argc=1, argv=)
at

[digikam] [Bug 361848] When writing metadata to files is disabled, digikam still displays "Writing metadata to files"

[Simon]

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

--- Comment #2 from Simon  ---
Hi Gilles,
No, I do not see this behaviour any more. Sorry I completely forgot
about this - thanks for the reminder.
Cheers,
Simon

On 25/11/16 15:37, bugzilla_nore...@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=361848
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #1 from caulier.gil...@gmail.com ---
> What's about this file using digiKam AppImage bundle 5.4.0 pre release given 
> at
> this url :
>
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
>
> Gilles Caulier
>

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

[kget] [Bug 372934] New: KGet crashed when adding a download link

[Lastique]

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

Bug ID: 372934
   Summary: KGet crashed when adding a download link
   Product: kget
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: andy...@mail.ru
  Target Milestone: ---

Application: kget (2.14.16)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.8.0-27-generic x86_64
Distribution: Ubuntu 16.10

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

I added a download link through the FlashGot plugin in Firefox. The "New
Download" window opened, I pressed OK and KGet crashed.

-- Backtrace:
Application: KGet (kget), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbd4b4122c0 (LWP 18938))]

Thread 3 (Thread 0x7fbd3261f700 (LWP 18951)):
#0  0x7fbd470f80bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbd439309d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd43930aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd48b1b22e in QEventDispatcherGlib::processEvents
(this=0x7fbd240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fbd48ae912f in QEventLoop::processEvents
(this=this@entry=0x7fbd3261ec80, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fbd48ae9495 in QEventLoop::exec (this=this@entry=0x7fbd3261ec80,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fbd489d8549 in QThread::exec (this=this@entry=0x2875ea0) at
thread/qthread.cpp:538
#7  0x7fbd48ac91c3 in QInotifyFileSystemWatcherEngine::run (this=0x2875ea0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fbd489dae3c in QThreadPrivate::start (arg=0x2875ea0) at
thread/qthread_unix.cpp:352
#9  0x7fbd4669670a in start_thread (arg=0x7fbd3261f700) at
pthread_create.c:333
#10 0x7fbd471040af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fbd33586700 (LWP 18940)):
#0  0x7fbd470f80bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbd439309d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd43930aec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd48b1b22e in QEventDispatcherGlib::processEvents
(this=0x7fbd2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fbd48ae912f in QEventLoop::processEvents
(this=this@entry=0x7fbd33585c80, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fbd48ae9495 in QEventLoop::exec (this=this@entry=0x7fbd33585c80,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fbd489d8549 in QThread::exec (this=this@entry=0x2651830) at
thread/qthread.cpp:538
#7  0x7fbd48ac91c3 in QInotifyFileSystemWatcherEngine::run (this=0x2651830)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fbd489dae3c in QThreadPrivate::start (arg=0x2651830) at
thread/qthread_unix.cpp:352
#9  0x7fbd4669670a in start_thread (arg=0x7fbd33586700) at
pthread_create.c:333
#10 0x7fbd471040af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fbd4b4122c0 (LWP 18938)):
[KCrash Handler]
#6  QMutex::lockInline (this=0x27dd4ca) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:187
#7  QMutexLocker::QMutexLocker (m=0x27dd4ca, this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:109
#8  QUrl::scheme (this=this@entry=0x2883a80) at io/qurl.cpp:4538
#9  0x7fbd491f925a in KUrl::prettyUrl (this=0x2883a80,
trailing=KUrl::LeaveTrailingSlash) at ./kdecore/io/kurl.cpp:1097
#10 0x7fbd4ae516df in ?? () from /usr/lib/libkgetcore.so.4
#11 0x7fbd35debb45 in ?? () from /usr/lib/kde4/kget_multisegkiofactory.so
#12 0x7fbd35dec7ab in ?? () from /usr/lib/kde4/kget_multisegkiofactory.so
#13 0x7fbd48afef70 in QMetaObject::activate (sender=0x28969c0, m=, local_signal_index=, argv=) at
kernel/qobject.cpp:3567
#14 0x7fbd4ae474a1 in DataSourceFactory::dataSourceFactoryChange(int) ()
from /usr/lib/libkgetcore.so.4
#15 0x7fbd4ae479fb in DataSourceFactory::slotUrlChanged(KUrl const&, KUrl
const&) () from /usr/lib/libkgetcore.so.4
#16 0x7fbd48afef70 in QMetaObject::activate (sender=0x2937100, m=, local_signal_index=, argv=) at
kernel/qobject.cpp:3567
#17 0x7fbd4ae452ca in TransferDataSource::urlChanged(KUrl const&, KUrl
const&) () from /usr/lib/libkgetcore.so.4
#18 0x7fbd35de65ce in ?? () from /usr/lib/kde4/kget_multisegkiofactory.so
#19 0x7fbd35de98a1 in ?? () from /usr/lib/kde4/kget_multisegkiofactory.so
#20 0x7fbd48afef70 in QMetaObject::activate (sender=0x287e2b0, m=, local_signal_index=, argv=) at
kernel/qobject.cpp:3567
#21 0x7fbd35de1e7c in ?? () from /usr/lib/kde4/kget_multisegkiofactory.so
#22 

[Akonadi] [Bug 372236] Akonadi will not start

[Etienne]

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

--- Comment #8 from Etienne  ---
Same report for me on KDE 5, Kubuntu 16.10 up to date.
Daniel's workaround not worked for me either.

Using "aconadictl start" gives me :
titi@TiTi-MSI-GT70-2OC:~$ sudo akonadictl start
Starting Akonadi Server...
   done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
titi@TiTi-MSI-GT70-2OC:/var/lib$ akonadiprivate_log: search paths: 
("/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin",
"/snap/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec",
"/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin",
"/opt/mysql/sbin")
Found mysql_install_db:  "/usr/bin/mysql_install_db"
Found mysqlcheck:  "/usr/bin/mysqlcheck"
Using mysqld: "/usr/sbin/mysqld-akonadi"
mysqld reports version 5.7.16 (Oracle MySQL)
Executing:  "/usr/sbin/mysqld-akonadi"
"--defaults-file=/etc/xdg/akonadi/mysql-global.conf --initialize
--datadir=/home/titi/.local/share/akonadi/db_data/"
mysqld: [ERROR] Could not open required defaults file:
/etc/xdg/akonadi/mysql-global.conf
mysqld: [ERROR] Fatal error in defaults handling. Program aborted!
Executing: "/usr/sbin/mysqld-akonadi"
"--defaults-file=/home/titi/.local/share/akonadi/mysql.conf
--datadir=/home/titi/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-root.gPGaHw/mysql.socket"
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/titi/.local/share/akonadi/mysql.conf",
"--datadir=/home/titi/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-root.gPGaHw/mysql.socket")
stdout: ""
stderr: "mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - No
such file or directory)\n2016-11-25T22:44:21.765496Z 0 [Warning] The syntax
'--log_warnings/-W' is deprecated and will be removed in a future release.
Please use '--log_error_verbosity' instead.\n2016-11-25T22:44:21.765542Z 0
[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use
--explicit_defaults_for_timestamp server option (see documentation for more
details).\n2016-11-25T22:44:21.765585Z 0 [ERROR] Failed to access directory for
--secure-file-priv. Please make sure that directory exists and is accessible by
MySQL Server. Supplied value :
/var/lib/mysql-files\n2016-11-25T22:44:21.765589Z 0 [ERROR]
Aborting\n\n2016-11-25T22:44:21.765601Z 0 [Note] Binlog end\n"
exit code: 1
process error: "Unknown error"
terminating service threads
terminating connection threads
stopping db process
Failed to remove Unix socket
Failed to remove runtime connection config file
Application 'akonadiserver' exited normally...

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

[Akonadi] [Bug 372236] Akonadi will not start

[Etienne]

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

Etienne  changed:

   What|Removed |Added

 CC||etie...@gabaut.fr

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

[digikam] [Bug 366777] No preview for Time Adjust tool

[Kristian]

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

Kristian  changed:

   What|Removed |Added

 CC||kde-b...@kristiankoch.com

--- Comment #1 from Kristian  ---
As the voting feature of the KDE bugtracker seems to be gone (at least I can't
find it anymore), I like to add that I badly would like to see the feature come
back to digikam. This would improve the horrible usability of the
BatchQueueManager-Tool-TimeAdjust at least a little bit.

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

[plasmashell] [Bug 372873] Move To Current Desktop

[H . d . V .]

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

H.d.V.  changed:

   What|Removed |Added

 CC||josef...@freenet.de

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

[kde] [Bug 372901] 16.12 - Crash after messing with Volume keyframes and restore

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |INVALID

--- Comment #2 from Christoph Feck  ---
Same report.

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

[kdenlive] [Bug 372932] KDEnlive Crash on initial boo

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |User Interface
   Assignee|unassigned-b...@kde.org |j...@kdenlive.org
Product|kde |kdenlive

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

[plasmashell] [Bug 372914] Digital clock setting crash

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |general
   Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk
Product|kde |plasmashell
Version|unspecified |5.8.0
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org
   Target Milestone|--- |1.0

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

[frameworks-solid] [Bug 345871] Solid::Backends::UDisks2::DeviceBackend::checkCache() causes crash after partition changes

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||constantine.karnacevych@gma
   ||il.com

--- Comment #32 from Christoph Feck  ---
*** Bug 372913 has been marked as a duplicate of this bug. ***

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

[kde] [Bug 372913] plasma crashed and restarted upon restaring docker service

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[digikam] [Bug 372900] When starting Digikam5, it crashes before opening the program, but after the splash screen.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |digikam
   Assignee|unassigned-b...@kde.org |digikam-de...@kde.org
  Component|general |general
Version|unspecified |5.3.0

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

[user-manager] [Bug 372933] New: user manager is empty

[bugzilla_noreply]

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

Bug ID: 372933
   Summary: user manager is empty
   Product: user-manager
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: johann.jacobs...@directbox.com
  Target Milestone: ---

Created attachment 102443
  --> https://bugs.kde.org/attachment.cgi?id=102443=edit
the empty user list

On Fedora 24 and 25, users are not listed in the user manager application and
thus cannot be edited.

I reported this problem first at
https://bugzilla.redhat.com/show_bug.cgi?id=1398704 but was ask to report this
here.

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

[kde] [Bug 372932] New: KDEnlive Crash on initial boo

[Steve]

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

Bug ID: 372932
   Summary: KDEnlive Crash on initial boo
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sfx.k...@gmail.com
  Target Milestone: ---

Application: kdenlive (16.08.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.9-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: Running openSUSE Tunbleweed. 
I removed a kdenlive5 installation because I could not start it.  It did not
appear in my Start menu and could not be booted from the console. I installed
kdenlive, found it listed in my Start menu (Multimedia) and attempted to start
it.  it crashed and crashed again upon trying again.  No other applicatione
were running.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f80e19ca8c0 (LWP 22636))]

Thread 3 (Thread 0x7f80c9545700 (LWP 22638)):
#0  0x7f80d9fc168d in poll () at /lib64/libc.so.6
#1  0x7f80d4aed876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f80d4aed98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f80dabe479b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f80dab8e1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f80da9bc8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f80dc59b3e5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f80da9c1558 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f80d8480454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f80d9fca39f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f80cb2fa700 (LWP 22637)):
#0  0x7f80d9fc168d in poll () at /lib64/libc.so.6
#1  0x7f80d40033e0 in  () at /usr/lib64/libxcb.so.1
#2  0x7f80d4005179 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f80cd8655f9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f80da9c1558 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f80d8480454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f80d9fca39f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f80e19ca8c0 (LWP 22636)):
[KCrash Handler]
#6  0x7f80a444ed24 in  () at /usr/lib64/libQtGui.so.4
#7  0x7f80e182347a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#8  0x7f80e182358b in _dl_init () at /lib64/ld-linux-x86-64.so.2
#9  0x7f80e1827ab8 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x7f80e1823324 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#11 0x7f80e1827259 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x7f80d8696ee9 in dlopen_doit () at /lib64/libdl.so.2
#13 0x7f80e1823324 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#14 0x7f80d8697521 in _dlerror_run () at /lib64/libdl.so.2
#15 0x7f80d8696f82 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#16 0x7f80e0a065b4 in mlt_repository_init () at /usr/lib64/libmlt.so.6
#17 0x7f80e0a05d78 in mlt_factory_init () at /usr/lib64/libmlt.so.6
#18 0x7f80e07d334b in Mlt::Factory::init(char const*) () at
/usr/lib64/libmlt++.so.3
#19 0x007aacf6 in BinController::BinController(QString)
(this=0x1482120, profileName=...) at
/usr/src/debug/kdenlive-16.08.3/src/mltcontroller/bincontroller.cpp:36
#20 0x00844bfd in Core::initialize() (this=0xf9de70) at
/usr/src/debug/kdenlive-16.08.3/src/core.cpp:63
#21 0x00827a75 in MainWindow::MainWindow(QString const&, QUrl const&,
QString const&, QWidget*) (this=0xf9bf70, MltPath=..., Url=...,
clipsToLoad=..., parent=, __in_chrg=,
__vtt_parm=) at
/usr/src/debug/kdenlive-16.08.3/src/mainwindow.cpp:222
#22 0x0048fdcb in main(int, char**) (argc=,
argv=) at /usr/src/debug/kdenlive-16.08.3/src/main.cpp:154

Reported using DrKonqi

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

[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)

[eduardo]

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

--- Comment #1 from eduardo  ---
to reproduce the bug, I have to grab the window with the mouse and (while
keeping the left button pressed) move it to any edge of the screen until the
cursor touch the edge. In that moment, the pc gets frozen.

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

[kwin] [Bug 372931] New: Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)

[eduardo]

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

Bug ID: 372931
   Summary: Plasma 5 get frozen if I grab a window and move it to
any edge of the screen (on wayland)
   Product: kwin
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: edoantoni...@hotmail.com
  Target Milestone: ---

In wayland if I grab a window (any window, it does not matter if a native
wayland application like dolphin or something using xwayland as firefox), and
move it to any edge of the screen, the PC get frozen. So I have to abruptly
force a restart to continue using the PC.

This on Manjaro, intel hardware, on Wayland

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

[digikam] [Bug 365331] digikam not loading because rpath information missing from libQt5Qml, libQt5Script and libQt5Quick

[RJVB]

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

--- Comment #5 from RJVB  ---
Edit: it would *seem* that the issue has resolved itself in 5.3.0 .

I agree something was wrong, but digiKam is the only application where I've
seen this happen with my build settings, and only for a few Qt libraries.
I don't know how the AppImage stuff is finagled together, but I'm not using
that. I'm just using unpatched CMake files and everything KF5 is built with the
settings required to apply full rpaths to all binaries. Qt5 itself is built
that way too.

I'd agree the problem was fully on my end if I saw this happening to all Qt
libraries (in DK or in other applications too), but that isn't the case.

The simplest explanation would be that somehow the rpath information is dropped
for the affected Qt libraries

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

[kdeplasma-addons] [Bug 372930] New: Weather applet crashes

[Alexey Putz]

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

Bug ID: 372930
   Summary: Weather applet crashes
   Product: kdeplasma-addons
   Version: 5.7.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: weather
  Assignee: kosse...@kde.org
  Reporter: putz.ale...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

1. Add weather applet to the plasma desktop.
2. Open weather settings for this applet right clicking it.
3. In search window input "Moscow".
4. Choose "Moscow, Russia, bbcukmet".
5. Click apply. 
6. Crash.

Reproducible : Couldn't reproduce after the first crash.

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

Thread 20 (Thread 0x7f1be4b8d700 (LWP 17059)):
#0  0x7f1cc26db0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1cbf41b9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1cbf41baec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1cc30094ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1cc2fb10fa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1cc2dd6d43 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1cc2ddbc68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1cc1ebb70a in start_thread (arg=0x7f1be4b8d700) at
pthread_create.c:333
#8  0x7f1cc26e70af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7f1be37ea700 (LWP 17058)):
#0  0x7f1cc26db0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1cbf41b9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1cbf41baec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1cc30094ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1cc2fb10fa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1cc2dd6d43 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1cc56d9c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f1cc2ddbc68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1cc1ebb70a in start_thread (arg=0x7f1be37ea700) at
pthread_create.c:333
#9  0x7f1cc26e70af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7f1be0d47700 (LWP 9209)):
#0  0x7ffd8ddb7937 in ?? ()
#1  0x7ffd8ddb7bc9 in clock_gettime ()
#2  0x7f1cc26f5846 in __GI___clock_gettime (clock_id=1, tp=0x7f1be0d46a40)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f1cc2e87726 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1cc3007039 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1cc30075e5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1cc300899e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1cbf41aed9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f1cbf41b8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f1cbf41baec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f1cc30094ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f1cc2fb10fa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f1cc2dd6d43 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f1cc56d9c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f1cc2ddbc68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f1cc1ebb70a in start_thread (arg=0x7f1be0d47700) at
pthread_create.c:333
#16 0x7f1cc26e70af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f1be67fc700 (LWP 1877)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1cc2ddcb2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1c07de7270 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f1c07deb4a8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f1c07de63ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f1c07de92b9 in 

[konqueror] [Bug 372929] New: Konqui crashes from time to time

[Dieter Nützel]

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

Bug ID: 372929
   Summary: Konqui crashes from time to time
   Product: konqueror
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: die...@nuetzel-hh.de
  Target Milestone: ---

Application: konqueror (4.14.8)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 4.9.0-rc6-1.g5f5c2ad-default x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

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

Nothing special.
Only some (three tabs) websites were open.
One tab was phoronix.com.

It always crash in the same lib, like in this backtrace.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb3990fb780 (LWP 2545))]

Thread 10 (Thread 0x7fb37ae94700 (LWP 2621)):
#0  0x7fb3979ce03f in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb38bbca686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7fb38bbca6b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7fb3979ca0a4 in start_thread (arg=0x7fb37ae94700) at
pthread_create.c:309
#4  0x7fb3967366ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fb3380b7700 (LWP 2623)):
#0  0x7fb39672e2bd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb393838be4 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb3300013e0, timeout=9753, context=0x7fb339a0) at gmain.c:4076
#2  0x7fb393838be4 in g_main_context_iterate
(context=context@entry=0x7fb339a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3776
#3  0x7fb393838cec in g_main_context_iteration (context=0x7fb339a0,
may_block=1) at gmain.c:3842
#4  0x7fb397d8f0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7fb397d60e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fb397d61165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7fb397c5e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7fb397c6079f in  () at /usr/lib64/libQtCore.so.4
#9  0x7fb3979ca0a4 in start_thread (arg=0x7fb3380b7700) at
pthread_create.c:309
#10 0x7fb3967366ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7fb336e88700 (LWP 2625)):
#0  0x7fb3979ce3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7fb38bbf27c6 in WTF::ThreadCondition::timedWait(WTF::Mutex&, double)
() at /usr/lib64/libQtWebKit.so.4
#2  0x7fb38b93cd7c in JSC::BlockAllocator::waitForRelativeTime(double) ()
at /usr/lib64/libQtWebKit.so.4
#3  0x7fb38b93cde8 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#4  0x7fb38bbf21e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#5  0x7fb3979ca0a4 in start_thread (arg=0x7fb336e88700) at
pthread_create.c:309
#6  0x7fb3967366ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7fb334f81700 (LWP 2662)):
#0  0x7fb39672e2bd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb393838be4 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb32c0013e0, timeout=-1, context=0x7fb32c0009a0) at gmain.c:4076
#2  0x7fb393838be4 in g_main_context_iterate
(context=context@entry=0x7fb32c0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3776
#3  0x7fb393838cec in g_main_context_iteration (context=0x7fb32c0009a0,
may_block=1) at gmain.c:3842
#4  0x7fb397d8f0de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7fb397d60e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7fb397d61165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7fb397c5e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7fb38ed71c1e in KIO::NameLookUpThread::run() () at
/usr/lib64/libkio.so.5
#9  0x7fb397c6079f in  () at /usr/lib64/libQtCore.so.4
#10 0x7fb3979ca0a4 in start_thread (arg=0x7fb334f81700) at
pthread_create.c:309
#11 0x7fb3967366ed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7fb31cd71700 (LWP 2677)):
#0  0x7fb39672e2bd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb393838be4 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb3180010c0, timeout=-1, context=0x3481dc0) at gmain.c:4076

[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

[Sergey]

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

--- Comment #16 from Sergey  ---
I have never been in this menu. According to my experience it's bad practice to
interfere there. I set everything long time ago inside /etc/ and other configs.
Also time zone is set in config files long time ago using console. Once I tried
to change in KDE4 settings my time zone or other thing and it was bad
experience. It broke my "console" settings. Also I don't change things which
work well.

Well, in your example I see that "en_US.UTF-8" != "C".

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

[plasmashell] [Bug 372928] New: Plasma crashed

[John Walker]

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

Bug ID: 372928
   Summary: Plasma crashed
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: johngeoffreywal...@yahoo.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I had locked the account and was working in another one. When I returned Plasma
crashedwith the message "We are sorry, Plasma closed unexpectedly"
This does not happen every time. It seems to go through phases of happening
every time then not happening at all.

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7fdb3bfff700 (LWP 3805)):
#0  0x7fdbf2858bfd in poll () at /lib64/libc.so.6
#1  0x7fdbeef35e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fdbeef35f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdbf3185d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fdbf312cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fdbf2f4e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fdbf6dfe282 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7fdbf2f5332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fdbf20620a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fdbf286102d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fdbc77ba700 (LWP 3804)):
#0  0x7fdbf206603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fdbf8a3186b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fdbf8a31899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fdbf20620a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fdbf286102d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fdbcd17f700 (LWP 3803)):
#0  0x7ffe2fed3b26 in clock_gettime ()
#1  0x7fdbf286dc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fdbf30047d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fdbf31843b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fdbf3184945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fdbf3185b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fdbeef354ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fdbeef35d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fdbeef35f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fdbf3185d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fdbf312cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fdbf2f4e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fdbf6262e18 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7fdbf2f5332f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7fdbf20620a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7fdbf286102d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fdbce95d700 (LWP 3802)):
#0  0x7fdbf2858bfd in poll () at /lib64/libc.so.6
#1  0x7fdbeef35e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fdbeef35f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdbf3185d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fdbf312cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fdbf2f4e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fdbf6262e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fdbf2f5332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fdbf20620a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fdbf286102d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fdbdafc1700 (LWP 3801)):
#0  0x7fdbf2858bfd in poll () at /lib64/libc.so.6
#1  0x7fdbeef35e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fdbeef35f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdbf3185d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fdbf312cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fdbf2f4e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fdbf6262e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fdbf2f5332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fdbf20620a4 in start_thread 

[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)

[Alex Bikadorov]

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

--- Comment #15 from Alex Bikadorov  ---

> It looks like krusader only knows LC_ALL and ignores other language variables.

That can't be it. My settings are:
$locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

But all filenames are fine - English, Russian, Japanese...

Do have regional settings set in KDEs "system settings"?

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

[digikam] [Bug 203714] Play animated GIF files in preview mode

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
This can be done with video preview, if right GStreamer codec is installed. Do
you try this solution ?

Gilles Caulier

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

[digikam] [Bug 360714] JPGEG2000 thumbnails shows as dimension 0x0 pixel

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[systemsettings] [Bug 372927] New: Can't load "local themes" for gnome/gtk applications

[Tony]

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

Bug ID: 372927
   Summary: Can't load "local themes" for gnome/gtk applications
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_style
  Assignee: tibi...@kde.org
  Reporter: jodr...@live.com
  Target Milestone: ---

Created attachment 102442
  --> https://bugs.kde.org/attachment.cgi?id=102442=edit
Evidence

The installer does not recognize compressed packages other than ".tar.gz". and
even if your theme is compressed as such the "Install GTK Theme" stays gray
out.

I can decompress the file into "~/.themes" and they will show as GTK2/3 themes,
s well as install them from api.kde-look.org.

To reproduce:
Head to systemsettings>application style> GTK style.
Click "get new themes" and select "install local theme"
On box select your compress theme (.tar.gz).

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

[digikam] [Bug 354819] Specific pictures not showing up in digikam

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 365331] digikam not loading because rpath information missing from libQt5Qml, libQt5Script and libQt5Quick

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
I don't know where is your problem, but certainly something is wrong when you
compile DK and co.

The bundle are relocatable under Linux. The AppImage for ex can be executed
from everywhere 

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 337931] Thumbnail order does not match window order

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 365744] GPS information not found in 4.12, but existing in the JPG files

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 321145] GoogleMaps : lost zoom function via mouse wheel and keyboard shortcuts

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 342352] Relocate "Show tracks on map" option on GUI

[bugzilla_noreply]

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

--- Comment #1 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 278975] Geolocation no longer looks up altitude automatically

[bugzilla_noreply]

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

--- Comment #9 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 342689] Map in image/geolocalisation is always at minimum zoom

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 329353] Make slow processing better

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 350350] Moving images notifies me moving finished when it did not finish yet

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 362132] Cannot connect to smb shared collection

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[neon] [Bug 372918] KDE Neon wont boot after install

[Rohit]

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

Rohit  changed:

   What|Removed |Added

 CC||rohitnai...@gmail.com

--- Comment #2 from Rohit  ---
Experienced exactly the same problem with the latest iso i.e
neon-useredition-20161124-1018-amd64.iso

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

[digikam] [Bug 341111] MYSQL : deleting an image involves "too many" queries

[bugzilla_noreply]

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

--- Comment #11 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming

[bugzilla_noreply]

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

--- Comment #11 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 365354] MYSQL : Application crash on scanning for faces in large picture set.

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 331878] GROUP : the «grouped images icon» disapears when working on the main (front) image

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[digikam] [Bug 232391] PRINT : scaling images is broken

[bugzilla_noreply]

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

--- Comment #13 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 320263] FILEIO : some PNG files are not rendered with "IDAT: CRC error"

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 338462] FILEIO : Image Editor hungs at attempt to create new image version on a samba share

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 363998] DigiKam sees Nikon D700 but cannot import files

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
 Resolution|--- |FIXED

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

[kstars] [Bug 372926] New: EKOS crash on opening Control tab. It did render it though.

[Hans Lambermont]

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

Bug ID: 372926
   Summary: EKOS crash on opening Control tab. It did render it
though.
   Product: kstars
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: h...@lambermont.dyndns.org
  Target Milestone: ---

#0  0x74afa8c0 in QWidget::mapFromParent(QPoint const&) const () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#1  0x0064d25b in FITSView::getImagePoint (this=this@entry=0x3e04f40,
viewPortPoint=...)
at
/build/kstars-bleeding-qSmJ00/kstars-bleeding-16.10+201611202010~ubuntu16.04.1/kstars/fitsviewer/fitsview.cpp:1479
#2  0x00652be1 in FITSView::wheelEvent (this=0x3e04f40,
event=0x7fffd260)
at
/build/kstars-bleeding-qSmJ00/kstars-bleeding-16.10+201611202010~ubuntu16.04.1/kstars/fitsviewer/fitsview.cpp:1432
#3  0x74b11f88 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x74c10b4e in QFrame::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x73cf3172 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QE vent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x74acf03c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x74ad6206 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x74b2d7ae in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x74b2ec23 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x74acf05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x74ad4516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x73cf338b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7451b010 in
QGuiApplicationPrivate::processWheelEvent(QWindowSystemInterfacePrivate::WheelEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x74520195 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#16 0x74503f08 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x7fffe4eee060 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#18 0x7fffef0fc1a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7fffef0fc400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7fffef0fc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x73d497cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x73cf0b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x73cf8bec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00483c23 in main (argc=1, argv=)
at
/build/kstars-bleeding-qSmJ00/kstars-bleeding-16.10+201611202010~ubuntu16.04.1/kstars/main.cpp:277

A second run did not reproduce this crash so I'm not sure what I caught here.

kstars-bleeding  5:16.10+201611202010~ubuntu16.04.1
Ubuntu 16.04.1 LTS

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

[kdevelop] [Bug 372925] New: Code will never be executed helper solutions should be merged

[Avihay]

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

Bug ID: 372925
   Summary: Code will never be executed helper solutions should be
merged
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@avihay.baratz.org
  Target Milestone: ---

Created attachment 102441
  --> https://bugs.kde.org/attachment.cgi?id=102441=edit
semantic analysis tooltip for "code will never be executed"

Attached: an image to demonstrate the situation
How to reproduce:
1) open a new c++ project
2) add "if(false)" between "main" and print "hello world"
3) Hover over the semantic analysis marker (should be under the last <<
operator)

The tool-tip suggests two solutions:
S1) prepend "/* DISABLE CODE */ ("
S2) append ")"

preforming either solution creates a new code error (due to adding a '(' or ')'
to the code).
Preforming S1 and then S2 from the same tool-tip (since it doesn't disappear)
results in S2's ')' inserted in the original position, changing the code and
very possible insert an error to the code.
Performing S2 and then S1 from the same tool-tip (since it doesn't disappear)
solves the issue properly, since appending doesn't change the prepending
position.

I believe the solutions should be merged to one solution.

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

[kdevelop] [Bug 372924] Include clipboard support to tool tips and tool views

[Avihay]

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

Avihay  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[kdevelop] [Bug 372924] New: Include clipboard support to tool tips and tool views

[Avihay]

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

Bug ID: 372924
   Summary: Include clipboard support to tool tips and tool views
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@avihay.baratz.org
  Target Milestone: ---

Tooltips and Especially the problem field of the problems toolview contain info
one would usualy like to copy to clipboard.

User story: User works on some code. User sees there are Problems he doesn't
understand the nature of. user wants to copy the error from the Problems
toolview to paste in a search engine of his choice to get a better
understanding of the error.

Currently you can only copy stuff into the selection (not clipboard) from the
tool-tip. some people aren't comfortable with selection, some people prefer
using the clipboard. KDE is all about choice, so having both could be nice.

In MS Visual Studio, you can only select the whole error table row (including
stuff you would have to clean up after pasting in the user story scenario). Be
smart. Don't be like MS Visual Studio.

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

[digikam] [Bug 363998] DigiKam sees Nikon D700 but cannot import files

[Ray Di Mascio]

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

--- Comment #17 from Ray Di Mascio  ---
I found the answer.  The camera has to be UNMOUNTED for DK to work !

Now we can all get some sleep.

All the best,

Ray


On 25/11/16 17:06, bugzilla_nore...@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=363998
>
> --- Comment #16 from caulier.gil...@gmail.com ---
> Stop imediatly (:=)))...
>
> Read well my previous comments : YOU DONT need to install anything on your
> system to run the AppImage bundle.
>
> Download the AppImage bundle on your computer, somewhere in your account. Make
> the file executable and start it as well from a console. That all. The bundle
> is an archive which will be decompressed in memory as a virtual file system. 
> In
> this archive you have all shared libs that digiKam need to run. Also digiKam
> executable is also in the bundle of course. Running the bundle == run digiKam
> from the bundle.
>
> It's simple simple simple. The libgphoto 2.5.11 is already in the bundle and
> digiKam will use it. Alll system libraries are not use in the bundle. If
> something is broken on your computer (or is badly packaged), this will not
> perturb digiKam run time.
>
> Voilà... You know all the stuff now...
>
> Gilles Caulier
>

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

[konqueror] [Bug 39923] Completely garbled display with text displayed on top of other text

[Krishna]

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

Krishna  changed:

   What|Removed |Added

 CC||chaitanyakrishna119@gmail.c
   ||om

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

[KScreen] [Bug 359161] Screen refresh rate not saved or restored

[Beer]

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

Beer  changed:

   What|Removed |Added

 CC||arco...@gmail.com

--- Comment #2 from Beer  ---
This might be related.. my refresh rate setting always gets reverted back to
Auto

Demo:  http://i.imgur.com/MWwcCiZ.gif

Plasma 5.8.4
Frameworks 5.28.0

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

[frameworks-kio] [Bug 354503] KIO FTP protocol adds space at the beginning of some files/dirs while ftp to AIX FTP servers, which makes it unable to enter these directories

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

Version|2.4.0-beta3 "Single Step"   |unspecified
  Component|net-connection  |general
   Assignee|m...@fork.pl  |fa...@kde.org
 Status|NEEDSINFO   |UNCONFIRMED
Product|krusader|frameworks-kio
Summary|Krusader adds space at the  |KIO FTP protocol adds space
   |beginning of some   |at the beginning of some
   |files/dirs while ftp to AIX |files/dirs while ftp to AIX
   |FTP servers, which makes it |FTP servers, which makes it
   |unable to enter these   |unable to enter these
   |directories |directories
 Resolution|WAITINGFORINFO  |---
 CC||kdelibs-b...@kde.org

--- Comment #7 from Alex Bikadorov  ---

> This bug occurs also in Dolphin. This might indicate problem with some 
> library.

Yep, KIO. Moved this bug.

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

[kdenlive] [Bug 372660] Kdenlive: please LOUDLY warn when there is proxy clips

[Roman Lebedev]

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

--- Comment #2 from Roman Lebedev  ---
Hi Jean-Baptiste Mardelle.

I have not yet tried the recent-enough version with that commit, but looking at
the changes, i **think** it is not what i meant.
I do not want to see a warning simply when the toggle "Render using proxy
clips".

I want to see a warning when that toggle is DISABLED, but a proxy is enabled
for one of the clips (yellow "P" icon on the thumbnail in "Project Bin"(?)).
Because in such a case, for that particular clip, the proxy _WILL_ be used. No
matter the value of "Render using proxy clips" toggle.

I.e. that warning should be about the actual usage of proxy clips in the
render, not some settings.

Roman.

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

[kdeplasma-addons] [Bug 372921] Add magnifier while picking a color

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin  ---
As on Wayland color picking is done through an effect we can do something like
a magnifier. But I'm not sure whether it's a good solution.

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

[telepathy] [Bug 372631] OTR messages in chat history are not decrypted (history not readable)

[bugzilla_noreply]

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

pi...@gmx.de changed:

   What|Removed |Added

 CC||pi...@gmx.de

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

[digikam] [Bug 312551] showFoto displays camera jpegs with AdobeRGB DCF information with a blue color cast

[bugzilla_noreply]

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

--- Comment #8 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 340609] impossible to use [meta:Exif.Photo.LensModel] in rename function

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[kmail2] [Bug 366652] Drag and drop attachments in Kmail has stopped working

[Rigo Wenning]

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

Rigo Wenning  changed:

   What|Removed |Added

 CC||r...@w3.org

--- Comment #4 from Rigo Wenning  ---
I can confirm that bug for Opensuse Leap 42.2 with Kontact 5.3.0. So I will ask
the devs to upgrade Leap 42.2 to 5.4.0. Essentially, it will not accept
dragging attachments. Attachments can only be saved via "save-as". But as it is
fixed now, this is fine and just a matter of the distro

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

[digikam] [Bug 166614] Animations on UI changes

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #5 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 272730] Sidebar does not adjust scroll area size automatically

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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