[kpat] [Bug 357558] New: kpat crashes after start

[Marcin via KDE Bugzilla]

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

Bug ID: 357558
   Summary: kpat crashes after start
   Product: kpat
   Version: 3.6
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: mf6...@wp.pl
CC: kde-games-b...@kde.org

Application: kpat (3.6)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.13-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:
I just opened kpat and tried to play freecell - then application crashed.

-- Backtrace:
Application: Pasjans (kpat), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fae60257780 (LWP 5552))]

Thread 2 (Thread 0x7fae3b060700 (LWP 5560)):
[KCrash Handler]
#5  0x7fae5ebb645e in KSharedDataCache::insert(QString const&, QByteArray
const&) () at /lib64/libkdecore.so.5
#6  0x7fae5f10f571 in KImageCache::insertImage(QString const&, QImage
const&) () at /lib64/libkdeui.so.5
#7  0x7fae5fe86ff2 in RenderingThread::run() () at /lib64/libkcardgame.so
#8  0x7fae5e523fff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7fae5a3405bd in start_thread () at /lib64/libpthread.so.0
#10 0x7fae5cf235cd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fae60257780 (LWP 5552)):
#0  0x7fae5cf136ad in read () at /lib64/libc.so.6
#1  0x7fae586d6880 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7fae586956a4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7fae58695b1b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7fae58695c8c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7fae5e651e1e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#6  0x7fae5da564f6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#7  0x7fae5e623931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#8  0x7fae5e623c45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#9  0x7fae5e628e59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#10 0x00418f0a in main ()

The reporter indicates this bug may be a duplicate of or related to bug 309824.

Possible duplicates by query: bug 321881.

Reported using DrKonqi

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

[kmix] [Bug 342107] KMix is not showing all sound outputs/inputs

[Sergiu Bivol via KDE Bugzilla]

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

Sergiu Bivol  changed:

   What|Removed |Added

 CC||ser...@cip.md

--- Comment #3 from Sergiu Bivol  ---
This bug is in no way related to bug 257551. That one is specifically about the
monitor sources, which are simply ignored by "Audio Hardware Setup" and Kmix.

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

[KScreen] [Bug 355528] Multiple monitor support is erratic

[Murat Ursavaş via KDE Bugzilla]

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

--- Comment #6 from Murat Ursavaş  ---
Unfortunately dealing with drivers didn't help. I've installed some missing
display drivers and the behavior is still there. And this time I got the app
launcher in the wrong place (vertical offset).

Switching to VT's didn't help at all. I had to press to the display switch
button of the laptop to enable or disable plugged screens.

I guess, for my particular case, Plasma 5.5.2 is not stable enough. I'll wait
and see what happens, because KDE Plasma is my best DE by far.

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

[parley] [Bug 357508] Get new themes not working

[Dimitris Kardarakos via KDE Bugzilla]

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

--- Comment #2 from Dimitris Kardarakos  ---
Having compiled from source, it is here: 
/usr/local/etc/xdg/parley-themes.knsrc

When I installed the packaged version from repository (manjaro), it is
installed in /etc/xdg/parley-themes.knsrc and themes' download works as
expected.

Probably I was supposed to set something different as build parameters from the
ones  I set (-DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=debugfull ).

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

[krita] [Bug 357559] New: crash on opening PSD file

[Alexander Opitz via KDE Bugzilla]

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

Bug ID: 357559
   Summary: crash on opening PSD file
   Product: krita
   Version: 2.9.10
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: o...@gmx.at

Application: krita (2.9.10)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Opened a PSD file. The file is around 100MB but it is an internal project.

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0a2cf00840 (LWP 6453))]

Thread 6 (Thread 0x7f09f3fff700 (LWP 6461)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0a2aa84286 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f0a2aa80063 in QSemaphore::acquire(int) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f0a276993cb in KisTileDataPooler::waitForWork (this=0x2de9390) at
/build/krita-testing-msg5HH/krita-testing-2+git20151215+r45/krita/image/tiles3/kis_tile_data_pooler.cc:165
#4  KisTileDataPooler::run (this=0x2de9390) at
/build/krita-testing-msg5HH/krita-testing-2+git20151215+r45/krita/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x7f0a2aa83d1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f0a248856aa in start_thread (arg=0x7f09f3fff700) at
pthread_create.c:333
#7  0x7f0a2a1aceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f0a01ab6700 (LWP 6462)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0a2aa84286 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f0a2aa80483 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f0a276c1b03 in KisTileDataSwapper::waitForWork (this=) at
/build/krita-testing-msg5HH/krita-testing-2+git20151215+r45/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4  0x7f0a276c1d6a in KisTileDataSwapper::run (this=0x2de93d0) at
/build/krita-testing-msg5HH/krita-testing-2+git20151215+r45/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5  0x7f0a2aa83d1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f0a248856aa in start_thread (arg=0x7f0a01ab6700) at
pthread_create.c:333
#7  0x7f0a2a1aceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0a0b091700 (LWP 6463)):
#0  0x7f0a2a1a3743 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0a2abc0eff in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f0a2abc6c5f in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timeval*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f0a2abc7118 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f0a2ab920d1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f0a2ab92445 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f0a2aa814f9 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f0a2ab72133 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f0a2aa83d1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f0a248856aa in start_thread (arg=0x7f0a0b091700) at
pthread_create.c:333
#10 0x7f0a2a1aceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0a012b5700 (LWP 6464)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0a2aa84286 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f0a2babf29c in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#3  0x7f0a2aa83d1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f0a248856aa in start_thread (arg=0x7f0a012b5700) at
pthread_create.c:333
#5  0x7f0a2a1aceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f09f35ad700 (LWP 6465)):
#0  0x7f0a2a1a3743 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0a2abc0eff in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f0a2abc6c5f in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timeval*) () from 

[kmahjongg] [Bug 344778] libkmahjongg installs lib twice

[Raymond Wooninck via KDE Bugzilla]

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

--- Comment #3 from Raymond Wooninck  ---
Apologies, it seems that I never received the initial email indicating the bug.
I had a quick look at the CMakeLists.txt and it seems that the second install
line should be removed. 

I will do this later today. 

Apologies for this.

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

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[via KDE Bugzilla]

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

--- Comment #2 from slartibar...@gmail.com ---
Well, i forgot to mention in the original bug report that i was testing on
fedora repos5.5.1, so the bug is/was still there even with 5.5.1

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

[plasmashell] [Bug 357564] Widgets in panel freeze and becomes unremovable until one restarts the session

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #1 from Sudhir Khanger  ---
Created attachment 96467
  --> https://bugs.kde.org/attachment.cgi?id=96467=edit
screencast of the problem

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

[kwin] [Bug 357565] New: Unmanaged clients should be able to block the compositor

[Thomas Lübking via KDE Bugzilla]

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

Bug ID: 357565
   Summary: Unmanaged clients should be able to block the
compositor
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: thomas.luebk...@gmail.com

Either by scripts or relevant properties.
Needs porting of https://git.reviewboard.kde.org/r/111771/

Reproducible: Always

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

[plasmashell] [Bug 353966] Notifications cover panel if secondary display is taller than main

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[plasmashell] [Bug 357563] New: Picture download with digiKam crashes plasma (and digikam)

[Arnold Seiler via KDE Bugzilla]

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

Bug ID: 357563
   Summary: Picture download with digiKam crashes plasma (and
digikam)
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arnold338250...@web.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

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

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

Download pictures from a camera with digiKam. The popup in the system
information area (system tray) of the Plasma panel did not appear, plasma and
digiKam crashed both.
The crash reproduces in about 20-50% of the cases. Sometimes the picture
download
works and a popup in system tray is telling that the process finished,
sometimes the download works, but the popup does not appear, sometimes plasma
and digiKam crash together.

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f677e2d3700 (LWP 7129)):
#0  0x7f678dd97c1d in poll () at /lib64/libc.so.6
#1  0x7f6792cc3422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f6792cc500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f67804243c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f678e48f32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f678d5a10a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f678dda004d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f67775ef700 (LWP 7137)):
#0  0x7f678dd97c1d in poll () at /lib64/libc.so.6
#1  0x7f678a479e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f678a479f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f678e6c1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f678e668d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f678e48a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f6791775df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f678e48f32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f678d5a10a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f678dda004d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f676a2f2700 (LWP 7139)):
#0  0x7f678a4bbd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f678a479759 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f678a479dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f678a479f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f678e6c1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f678e668d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f678e48a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f6791775df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f678e48f32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f678d5a10a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f678dda004d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f67688f0700 (LWP 7144)):
#0  0x7f678dd97c1d in poll () at /lib64/libc.so.6
#1  0x7f678a479e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f678a479f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f678e6c1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f678e668d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f678e48a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f6791775df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f678e48f32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f678d5a10a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f678dda004d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f6762f7d700 (LWP 7145)):
#0  0x7f678d5a505f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6793f2a86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f6793f2a899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f678d5a10a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f678dda004d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f66db68d700 (LWP 7147)):
#0  0x7f678dd97c1d in poll () at /lib64/libc.so.6
#1  0x7f678a479e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f678a479f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f678e6c1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[kdenlive] [Bug 357534] 15.13: git master: immediate crash when starting Kdenlive with clip in library

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #2 from wegwerf-1-...@gmx.de ---
Jean-Baptiste,

a Happy New Year to you! Thank you very much for all the effort you spend on
Kdenlive!

I've pulled today's git master and gave it a try using the same existing
project from which I stored a few clips with transitions in the library; the
same clips that caused the core dump before. With the most recent git master as
of today the crash is gone. So I would propose to close this bug as RESOLVED
FIXED. Thank you very much!

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

[kwin] [Bug 348156] Add a feature to unredirect all fullscreen windows except some selected

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #18 from Thomas Lübking  ---
(In reply to jeremy9856 from comment #17)
> (In reply to Thomas Lübking from comment #16)
> > you're apparently looking for a way suspend the compositor for all 
> > fullscreen
> > windows but some exceptions, because your fullscreen windows are typically a
> > pleathora of games and only in very few specific occasions eg. "fullscreen
> > firefox" should execptionally not suspend the compositor.
> That is exactly the use case I'm thinking of !

Ok, neither scripting nor rules are ready for this since they only deal with
managed clients, but several games (engine) create "fullscreen" windows as an
override_redirect window spanning the root geometry (and grabbing input)


Notably with a game context in mind, I strongly suggest to abort any approach
reg. unredirection and focus on a solution that skips the compositor.
The unredirection gain isn't worth it. You still have +1 active GL context and
rather heavy usage of texture memory. Redirection or rather texture_from_pixmap
caused quite some load in early compositing ages but is neglectable as of today
and redirected gl contexts should sync to the compositor.

=> What needs to happen:
1. port https://git.reviewboard.kde.org/r/111771/ to KWin/5 => bug #357565
2. adapt the gamemode script to support unmanged windows (local version still
does. no idea whether I ever published that - worthless w/o above patch,
though. Unmanaged clients cannot be matched, only globally toggled)
---
3. add a config GUI to the gamemode script
4. let the user switch between whitelist and blacklist behavior there
---
5. check whether the script should be shipped w/ kwin (which scripts should be
anyway?)
6. recheck w/ HIG team why scripting is "hard to use" (hard to find? clicking
the GHNS button cannot be harder than setting up a window rule, can it?)

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

[konsole] [Bug 357552] random Konsole crashes when switching from external monitor to laptop and viceversa

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[konqueror] [Bug 357562] New: Konqueror crashes when openg twitter

[Tuxmeister via KDE Bugzilla]

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

Bug ID: 357562
   Summary: Konqueror crashes when openg twitter
   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: j...@sieslieng.org

Application: konqueror (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.6
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: It started crashing when using
twitter and clicking on a pic. But now it's just opening twitter with konqueror
and it crashes right away.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f9ab46eb700 (LWP 6552)):
#0  0x7f9acccff05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9ab956beb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f9ab956bee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f9a7319e700 (LWP 6553)):
#0  0x7f9acb9e6c1d in poll () at /lib64/libc.so.6
#1  0x7f9ac8af7e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f9ac8af7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9acd0bffde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f9acd091d4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f9acd092045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f9accf8f4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f9accf91bbf in  () at /usr/lib64/libQtCore.so.4
#8  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f9a71bb3700 (LWP 6554)):
#0  0x7f9acccff05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9ab92deb3d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f9ab9593a06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f9a69f0b700 (LWP 6563)):
#0  0x7f9acccff05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9a69f72d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f9a69f73819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9a6970a700 (LWP 6564)):
#0  0x7f9acccff05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9a69f72d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f9a69f73819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f9a68f09700 (LWP 6565)):
#0  0x7f9acccff05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9a69f72d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f9a69f73819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f9acccfb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9acb9ef04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9ace420780 (LWP 6551)):
[KCrash Handler]
#6  0x7f9ab91e23a7 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () at
/usr/lib64/libQtWebKit.so.4
#7  0x7f9ab81baa5c in
WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle,
void*, JSC::SlotVisitor&) () at /usr/lib64/libQtWebKit.so.4
#8  0x7f9ab92dda9a in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () at
/usr/lib64/libQtWebKit.so.4
#9  0x7f9ab92eb33b in
JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () at
/usr/lib64/libQtWebKit.so.4
#10 0x7f9ab92e0785 in JSC::Heap::markRoots(bool) () at
/usr/lib64/libQtWebKit.so.4
#11 0x7f9ab92e2355 in JSC::Heap::collect(JSC::Heap::SweepToggle) () at
/usr/lib64/libQtWebKit.so.4
#12 0x7f9ab94b5872 in JSC::DefaultGCActivityCallback::doWork() () at
/usr/lib64/libQtWebKit.so.4
#13 0x7f9ab92e53bd in JSC::HeapTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQtWebKit.so.4
#14 

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[Julien HENRY via KDE Bugzilla]

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

--- Comment #3 from Julien HENRY  ---
Then maybe the fact I'm not able to reproduce is due to some other changes I
did that were only taken into account after a reboot. In compositor properties
I changed to:
Rendering backend = OpenGL 2.0 (was XRender previously)
Tearing prevention "vsync" = Never (was auto)

Not sure it has any impact but maybe you can give a try.

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

[kdevplatform] [Bug 274769] Wishlist for KDE Service Menu to include QBazaar support

[Xavi via KDE Bugzilla]

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

Xavi  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|RESOLVED|CLOSED

--- Comment #3 from Xavi  ---
Yes, thanks, Kevin! I didn't use KDE for a while (the feature request was more
than 4 years ago! :-) , but other desktops (currently using MATE on Ubuntu
14.04 LTS). I've just installed dolphin and dolphin-plugins-bazaar and I could
see it in action. Thanks heaps!
I'll mark it as fixed and close it.
Thanks
 Xavi

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

[plasmashell] [Bug 357564] New: Widgets in panel freeze and becomes unremovable until one restarts the session

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 357564
   Summary: Widgets in panel freeze and becomes unremovable until
one restarts the session
   Product: plasmashell
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: sud...@sudhirkhanger.com

Sometimes a widget like App Dash will become unresponsive. They can't be
removed from panel. Killing plasmashell doesn't help. I have to restart the
session after which they are recognized as widgets and become available for
removal.

Please see the attached screencast.

Reproducible: Always

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

[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing

[Michael Kostrzewa via KDE Bugzilla]

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

--- Comment #14 from Michael Kostrzewa  ---
To off...@3demo.info:

Yes, you're right. The wacomtablet KDE applet invokes xsetwacom internally and
my changes add the '+' switches so the button mapping works for me without any
manual xsetwacom invocations (maybe the releng3.0 version does this too).

Additionally another change  I made was to make the 'switch profile' LED to
actually work. The kernel I have (4.2.0-22) doesn't have the kernel device
files needed by the original wacom tablet to control the LED while switching
between profiles.


To Thorsten:
As another Michael said - making it work under your distro is not so much of a
KDE issue but more about packaging it for the distro. 

I need to check the releng3.0 version for compilation problems and to see if
the 2 other things (xsetwacom and LED problems) are maybe fixed in this
version. If not - Michael - can I just attach the patches here to this ticket?

I can also try to investigate how to make it work under the distro I use
(kubuntu) as soon as I find some time.

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

[parley] [Bug 357508] Get new themes not working

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #3 from Andreas Cord-Landwehr  ---
You have to set the XDG_CONFIG_DIRS environment variable for this to work.
Maybe you want to have a look at the "Runtime Setup" section in
https://community.kde.org/Frameworks/Building to have an overview of the
important environment variables you have to set when you are installing
self-compiled programs to custom paths.

I am closing this report, since this is not a program bug.

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

[kdevplatform] [Bug 292745] Clickable assert errors

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Milian Wolff  ---
sadly, this is not so easy b/c assert messages usually emit just the file name,
not the full path.

see bug 354695 for more info and a preliminary patch.

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

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

[kdevelop] [Bug 354695] Error parser doesn't parse assertions

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

 CC||daviddo...@gmail.com

--- Comment #2 from Milian Wolff  ---
*** Bug 292745 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[Julien HENRY via KDE Bugzilla]

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

Julien HENRY  changed:

   What|Removed |Added

 CC||henr...@yahoo.fr

--- Comment #1 from Julien HENRY  ---
I had exactly the same problem yesterday but since the update to plasma 5.5.1 I
am no more able to reproduce.

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

[konsole] [Bug 357560] New: Konsole Crash when changing profile settings

[Laven Pillay via KDE Bugzilla]

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

Bug ID: 357560
   Summary: Konsole Crash when changing profile settings
   Product: konsole
   Version: 15.08.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: laven.pil...@darkness.co.za

Application: konsole (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64
Distribution: "Korora release 23 (Coral)"

-- Information about the crash:
- What I was doing when the application crashed:
I had just done the following : 
1. Created new Konsole Profile
2. Changed General settings for new Profile
3. Changed Appearance settings > Background image
4. When I tried to browse for the image, Konsole crashed

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

Thread 4 (Thread 0x7fa0f7b67700 (LWP 2974)):
#0  0x7fa10f4d7ffd in poll () from /lib64/libc.so.6
#1  0x7fa10b629272 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fa10b62aee7 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fa0f9cfeda9 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7fa1100e03ce in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fa10d45e60a in start_thread () from /lib64/libpthread.so.0
#6  0x7fa10f4e3a9d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fa0eec13700 (LWP 4193)):
#0  0x7fa10d463b10 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fa1100e165b in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fadae6a in QFileInfoGatherer::run() () from
/lib64/libQt5Widgets.so.5
#3  0x7fa1100e03ce in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7fa10d45e60a in start_thread () from /lib64/libpthread.so.0
#5  0x7fa10f4e3a9d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa0ed6f6700 (LWP 19367)):
#0  0x7fa10d463b10 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fa1100e165b in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fadae6a in QFileInfoGatherer::run() () from
/lib64/libQt5Widgets.so.5
#3  0x7fa1100e03ce in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7fa10d45e60a in start_thread () from /lib64/libpthread.so.0
#5  0x7fa10f4e3a9d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa1173ad940 (LWP 2973)):
[KCrash Handler]
#5  0x7fa0f9d15f08 in QXcbWindow::setParent(QPlatformWindow const*) () from
/lib64/libQt5XcbQpa.so.5
#6  0x7fa1108048bb in QWindow::setParent(QWindow*) () from
/lib64/libQt5Gui.so.5
#7  0x7fa110fdf5d5 in QWidgetPrivate::setParent_sys(QWidget*,
QFlags) () from /lib64/libQt5Widgets.so.5
#8  0x7fa110feafda in QWidget::setParent(QWidget*, QFlags)
() from /lib64/libQt5Widgets.so.5
#9  0x7fa110fec0cc in QWidget::setParent(QWidget*) () from
/lib64/libQt5Widgets.so.5
#10 0x7fa1110d211c in QDialogButtonBox::addButton(QAbstractButton*,
QDialogButtonBox::ButtonRole) () from /lib64/libQt5Widgets.so.5
#11 0x7fa0f6d36de9 in KDEPlatformFileDialog::KDEPlatformFileDialog() ()
from /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#12 0x7fa0f6d37212 in
KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper() () from
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#13 0x7fa0f6d2a35a in
KdePlatformTheme::createPlatformDialogHelper(QPlatformTheme::DialogType) const
() from /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#14 0x7faa11b5 in QDialogPrivate::platformHelper() const () from
/lib64/libQt5Widgets.so.5
#15 0x7fab4958 in QFileDialogPrivate::init(QUrl const&, QString const&,
QString const&) () from /lib64/libQt5Widgets.so.5
#16 0x7fab4c76 in QFileDialog::QFileDialog(QFileDialogArgs const&) ()
from /lib64/libQt5Widgets.so.5
#17 0x7fab4dce in QFileDialog::getOpenFileUrl(QWidget*, QString const&,
QUrl const&, QString const&, QString*, QFlags, QStringList
const&) () from /lib64/libQt5Widgets.so.5
#18 0x7fab5092 in QFileDialog::getOpenFileName(QWidget*, QString
const&, QString const&, QString const&, QString*, QFlags)
() from /lib64/libQt5Widgets.so.5
#19 0x7fa116d690b1 in Konsole::ColorSchemeEditor::selectWallpaper() () from
/lib64/libkonsoleprivate.so.15
#20 0x7fa1102f0177 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#21 0x7fa1113419e2 in QAbstractButton::clicked(bool) () from
/lib64/libQt5Widgets.so.5
#22 0x7fa1110a4524 in QAbstractButtonPrivate::emitClicked() () from
/lib64/libQt5Widgets.so.5
#23 0x7fa1110a5b39 in 

[skrooge] [Bug 357561] New: Starting skrooge freezes whatever was used to start it

[Aqeel Zafar via KDE Bugzilla]

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

Bug ID: 357561
   Summary: Starting skrooge freezes whatever was used to start it
   Product: skrooge
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: aq...@aqeeliz.com
CC: steph...@mankowski.fr

When I run skrooge from krunner, krunner freezes in it's place (Still showing
skrooge in the list), and doesn't do anything until skrooge is closed.

Same is true, when running it from kickoff menu, and even a file manager (I
tried dolphin, directly open the file.)

Killing plasma and re-starting it resumes the normal functionality, as do just
closing the Skrooge. It seems skrooge is blocking whatever app is used to run
it.

I am running skrooge 2.2.0 on:
Archlinux
Plasma 5.5.2, 
KDE Frameworks 5.17.0, 
Qt 5.5

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

[kdevelop] [Bug 290769] session should remember Filesystem's location

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.1.0

--- Comment #4 from Kevin Funk  ---
Review at: https://phabricator.kde.org/D737

Fixed by:

commit 7a61a3f6ab890894441f3e05d5b51cc7817073a5
Author: Imran Tatriev 
Date:   Tue Jan 5 02:54:02 2016 +0600

Remember Filesystem ToolView's location in each session

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

[krita] [Bug 357559] crash on opening PSD file

[Alexander Opitz via KDE Bugzilla]

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

--- Comment #3 from Alexander Opitz  ---
Hi,

bad news, I'm not allowed to send the PSD file out. :-(
I can only tell, that it was generated with CS6.

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

[Baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[David Tonhofer via KDE Bugzilla]

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

David Tonhofer  changed:

   What|Removed |Added

 CC||bugh...@gluino.name

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

[krita] [Bug 342105] Cannot right click with the Pen of Huion H610 Pro

[Thiébaut via KDE Bugzilla]

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

Thiébaut  changed:

   What|Removed |Added

 CC||tchampen...@gmail.com

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

[krunner] [Bug 343982] Krunner crashes on startup - QXcbWindow

[via KDE Bugzilla]

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

tas...@email.tg changed:

   What|Removed |Added

 Ever confirmed|0   |1

--- Comment #28 from tas...@email.tg ---
*** This bug has been confirmed by popular vote. ***

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[David Pyke via KDE Bugzilla]

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

David Pyke  changed:

   What|Removed |Added

 CC|kdeb...@loftwyr.ca  |

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

[plasmashell] [Bug 357554] Plasma Krasch when using LibreOffice Calc

[Vadym Krevs via KDE Bugzilla]

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

Vadym Krevs  changed:

   What|Removed |Added

 CC||vkr...@yahoo.com

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

[kwin] [Bug 357543] drmModeSetCrtc not called when presenting GBM buffer (Wayland)

[Jay Cornwall via KDE Bugzilla]

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

--- Comment #3 from Jay Cornwall  ---
Looks good on my Southern Islands AMD GPU.

I just noticed there is still a tiling issue on a Volcanic Islands AMD GPU but
I think it's a different problem, as I can see the kernel picking up a non-zero
tiling configuration with this change. I'll dig into that separately.

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

[kdevelop] [Bug 357585] New: ASSERT: "offset >= start" in clangutils.cpp

[via KDE Bugzilla]

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

Bug ID: 357585
   Summary: ASSERT: "offset >= start" in clangutils.cpp
   Product: kdevelop
   Version: git master
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: bunge...@gmail.com

5.0 branch, debug build:
kdevplatform 4c3129e0949ebda78704ae7e082911ad97850825
kdevelop cc6350ba51747578c69ddd8bba7b3f883009b5dc

Unfortunately, I didn't have the libclang1-3.6-dbg symbols installed at the
time, so I can't see what's in the opaque types.

Reproducible: Didn't try

Steps to Reproduce:
Was editing a header file which partially implements type traits (so very heavy
template use) from a recent build under gdb. I removed some lines and added a
few characters to an existing line, and kdevelop segfaulted on an assert.

Actual Results:  
Crash

Expected Results:  
Not crash

ASSERT: "offset >= start" in file ../languages/clang/util/clangutils.cpp, line
281

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffa1e15700 (LWP 10502)]
0x7503f267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
55  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7503f267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x75040eca in __GI_abort () at abort.c:89
#2  0x757e5c88 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x757e0dce in qt_assert(char const*, char const*, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fffb5a276df in ClangUtils::getRawContents (unit=0x7fff84c41e70,
range=...) at ../languages/clang/util/clangutils.cpp:281
#5  0x7fffb59e7d83 in (anonymous
namespace)::Visitor::setDeclData<(CXCursorKind)501> (this=0x7fffa1e13ae0,
cursor=..., decl=0x7fff90b649d0) at ../languages/clang/duchain/builder.cpp:912
#6  0x7fffb59d7a91 in (anonymous
namespace)::Visitor::createDeclarationCommon<(CXCursorKind)501,
MacroDefinition> (this=0x7fffa1e13ae0, cursor=..., id=...) at
../languages/clang/duchain/builder.cpp:372
#7  0x7fffb59c8ceb in (anonymous
namespace)::Visitor::createDeclaration<(CXCursorKind)501, MacroDefinition>
(this=0x7fffa1e13ae0, cursor=..., id=..., context=0x7fff902a7480) at
../languages/clang/duchain/builder.cpp:394
#8  0x7fffb59c0ae2 in (anonymous
namespace)::Visitor::buildDeclaration<(CXCursorKind)501, MacroDefinition, true>
(this=0x7fffa1e13ae0, cursor=...) at
../languages/clang/duchain/builder.cpp:1094
#9  0x7fffb59ba513 in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)501, (Decision)1,
(Decision)0, (detail::type)0> (this=0x7fffa1e13ae0, cursor=..., parent=...) at
../languages/clang/duchain/builder.cpp:870
#10 0x7fffb59b7a5b in (anonymous namespace)::visitCursor (cursor=...,
parent=..., data=0x7fffa1e13ae0) at ../languages/clang/duchain/builder.cpp:1405
#11 0x7fffb4db7add in ?? () from /usr/lib/llvm-3.6/lib/libclang-3.6.so.1
#12 0x7fffb4db842a in ?? () from /usr/lib/llvm-3.6/lib/libclang-3.6.so.1
#13 0x7fffb4db89f5 in ?? () from /usr/lib/llvm-3.6/lib/libclang-3.6.so.1
#14 0x7fffb4db7804 in ?? () from /usr/lib/llvm-3.6/lib/libclang-3.6.so.1
#15 0x7fffb4dbe024 in clang_visitChildren () from
/usr/lib/llvm-3.6/lib/libclang-3.6.so.1
#16 0x7fffb59b6c67 in (anonymous namespace)::Visitor::Visitor
(this=0x7fffa1e13ae0, tu=0x7fff84c41e70, file=0x7fff84690d00, includes=...,
update=true) at ../languages/clang/duchain/builder.cpp:1299
#17 0x7fffb59b7bd7 in Builder::visit (tu=0x7fff84c41e70,
file=0x7fff84690d00, includes=..., update=true) at
../languages/clang/duchain/builder.cpp:1437
#18 0x7fffb5992f0a in ClangHelpers::buildDUChain (file=0x7fff84690d00,
imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x17fbc80) at
../languages/clang/duchain/clanghelpers.cpp:181
#19 0x7fffb5992765 in ClangHelpers::buildDUChain (file=0x7fff856eaed0,
imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x17fbc80) at
../languages/clang/duchain/clanghelpers.cpp:121
#20 0x7fffb5992765 in ClangHelpers::buildDUChain (file=0x7fff84992f10,
imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x17fbc80) at
../languages/clang/duchain/clanghelpers.cpp:121
#21 0x7fffb5992765 in ClangHelpers::buildDUChain (file=0x7fff8755b270,
imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x17fbc80) at
../languages/clang/duchain/clanghelpers.cpp:121
#22 0x7fffb5992765 in ClangHelpers::buildDUChain (file=0x7fff8755b2f0,

[krita] [Bug 342105] Cannot right click with the Pen of Huion H610 Pro

[Thiébaut via KDE Bugzilla]

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

--- Comment #19 from Thiébaut  ---
I can also confirm the bug using:
Win 10 x64
Krita 2.9.10 x64
Huion 1060 Pro+

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Sellmaier via KDE Bugzilla]

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

--- Comment #36 from Thomas Sellmaier  ---
(In reply to Nikos Platis from comment #34)

> While thinking about correcting this bug, one has to remember comment #18:
> if multiple fonts are selected, they appear fine. So this may be easier to
> solve than the convolved code lets one think, and some experienced KDE
> developer could probably decipher this.

Sorry, for my System this workaround still wont work. The only difference is,
that the backround of the preview(s) change to white.

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

[k3b] [Bug 257602] K3B cannot burn Blurays (or AVCHDs)

[King_DuckZ via KDE Bugzilla]

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

King_DuckZ  changed:

   What|Removed |Added

 CC||king_du...@gmx.com

--- Comment #4 from King_DuckZ  ---
I'm also interested in a fix for this bug. Is anybody going to look into it
anytime soon? Any idea at all?

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

[kwin] [Bug 357586] New: If clients map iconified, there's no thumbnail in the compositor and an empty space in some effects

[miklos via KDE Bugzilla]

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

Bug ID: 357586
   Summary: If clients map iconified, there's no thumbnail in the
compositor and an empty space in some effects
   Product: kwin
   Version: 5.4.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mtm...@freemail.hu

I guess the missing thumbnail is inevitable, but the present windows effect
could at least display an outline for such windows.

Reproducible: Always

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

[kdevelop] [Bug 357585] ASSERT: "offset >= start" in clangutils.cpp

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Keywords||release_blocker
 Ever confirmed|0   |1
   Target Milestone|--- |5.0.0

--- Comment #1 from Kevin Funk  ---
Thanks for the detailed bug report!

I've seen this assert before, too. We definitely have to fix this before
release.

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

[plasmashell] [Bug 356727] panel disappears when dragging it to other monitor

[via KDE Bugzilla]

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

tamius@gmail.com changed:

   What|Removed |Added

 CC||tamius@gmail.com

--- Comment #15 from tamius@gmail.com ---
This bug affects me too.

Panels also disappear when changing which monitor is the default monitor (and
reappear when I physically plug/unplug the second monitor)

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Nikos Platis via KDE Bugzilla]

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

--- Comment #34 from Nikos Platis  ---
(In reply to Martin Klapetek from comment #33)
> But I'm thinking we could just add brand new font rendering
> widget to the kcm that replaces the old one and leave everything
> else in place (including the bitrotted code).
> 
> That way we could get a working Qt5 renderer and keep the old
> one around for things that may break or something. 
> 
> The whole thing desperately needs a maintainer though.

While thinking about correcting this bug, one has to remember comment #18: if
multiple fonts are selected, they appear fine. So this may be easier to solve
than the convolved code lets one think, and some experienced KDE developer
could probably decipher this.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #37 from Martin Klapetek  ---
> If so, i will come forward at the devel mailinglist.

Please do, it would be most welcome (plasma-devel at kde.org)

I think it would be nice to modernize the code quite a bit. With that
in mind, I think that the font preview could just be scrapped and done
from scratch. I imagine it's not that hard given you already have at least
some understanding of the code; you just need the font that is selected
on the left, pass it to the preview widget and have the widget paint stuff
using eg. QPainter.

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

[okular] [Bug 357579] Okular-15.12.0: page numbers text area not sized correctly when refreshing a document

[Oliver Sander via KDE Bugzilla]

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #2 from Oliver Sander  ---
I can confirm this.  There are more ways to make the mis-rendering go away
(temporarily), e.g., moving to a different page.

~ okular --version
Qt: 4.8.7
KDE: 4.14.14
Okular: 0.23.2
(from today's Debian testing, using the MATE desktop)

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

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[ultr via KDE Bugzilla]

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

--- Comment #10 from ultr  ---
> Extract archive To... [...]

This requires a lot more work than simply clicking the menu item.
And does not allow selecting several archives at once for extracting.

Plus the 'Extract Into a Subfolder' option is safest if you don't know the
structure of your archives you are about to extract. So I think it should be
easily accessible from the service menu.
Otherwise the user is left with this limited set of predefined quick actions
none of which is really safe for the data in such cases. Whichever action is
selected the user may end up having to reject many overwrite alerts, cancel all
the extractions, delete the already extracted data and start over manually
extracting archives one by one. Doesn't sound like a user friendly approach.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Thomas Sellmaier via KDE Bugzilla]

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

--- Comment #35 from Thomas Sellmaier  ---
First of all, I apologize for my harsh sounding post yesterday. My goal was not
to offend someone. But my criticism about favour implementation new features
vs. fixing (old) bugs still remains. 

After a few hours of reading i have to confess that kfontinst IS a hell of
opaque, uncommented code, but the Problem for this issue is IMHO the
/lib/FcEngine class. 

Due to the fact that the whole component is closely interweaved with the system
and that i have no clue about KDE development, it is (by now) not a good idea
to offer my work as a maintainer for this module. But I am on turn to setup a
dev environment, read docs and check whether it is possible for me to maintain
this module in future. If so, i will come forward at the devel mailinglist.

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

[trojita] [Bug 356865] Sent messages with Bcc receipients does not list Bcc

[Erik Quaeghebeur via KDE Bugzilla]

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

--- Comment #1 from Erik Quaeghebeur  ---
I've looked at the code:

In src/Composer/Submission.cpp there is the function
Submission::slotMessageDataAvailable that is responsible for creating the
messages and saving them to the sent mail folder; it calls
Submission::slotInvokeMsaNow() to send out the message. There is always an
if-then(-else) to choose between sending the message ‘raw’ or using CATENATE
(to add attachments). This function essentially (indirectly through
MessageComposer::asRawMessage or MessageComposer::asCatenateData) calls the
function MessageComposer::writeCommonMessageBeginning from
src/Composer/MessageComposer.cpp to generate the header. In this function, the
Bcc header is not included (as is appropriate for the version of the mail that
is sent out).

So it seems that what would need to be done is to keep all the necessary data
for the message in some variable, but not yet flattened to a single string.
Then it can be flattened twice, including/excluding Bcc as appropriate, much
later in the process. Does this seem like a good plan?

I may try my hand at a patch for this issue, but before starting, I need to
have a good view of the architecture that seems appropriate to the maintainers.

P.S.: How the list of recipients to be passed to the MSA is created is still
somewhat opaque to me, but my impression is that I won't need to bother with
that.

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

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #9 from Elvis Angelaccio  ---
(In reply to ultr from comment #5)
> there is no option to 'Extract Into a Subfolder',

Have you tried with: Right click -> Extract -> Extract archive To... ?
>From that dialog you can check the "Extract into subfolder" option and choose
whatever name you want for this subfolder. In this case, the default name is
going to be "mycode" and you just need to add "-v1" or "-v2".

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

[kgpg] [Bug 290221] KGpg 2.6.80 fails to start with nonexistant .gnupg directory

[Rolf Eike Beer via KDE Bugzilla]

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

--- Comment #18 from Rolf Eike Beer  ---
Distros sometimes put their configuration files at different places, so I fear
you need do "find /usr /home -name kgpgrc" to find the wrong file. Seems like
noone noticed LinuxMint to fix their 3 year old stuff in the last 3 years, so
you still get the same bug.

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

[plasmashell] [Bug 357580] New: Seg Fault in plasma shell

[Alain Toussaint via KDE Bugzilla]

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

Bug ID: 357580
   Summary: Seg Fault in plasma shell
   Product: plasmashell
   Version: 5.5.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: alain.toussa...@securivm.ca
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.1)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

run the startx command in a bash shell. My .xinitrc content use the single
line: /usr/bin/startkde

- Unusual behavior I noticed:

The plasmashell application crashes every time that I run the startx command. I
recompiled most of the KDE platform and its dependency with debugging
information (adding the -ggdb compiler flag) to have a useable backtrace
(included). Also included in the output of emerge --info on my funtoo platform
as an attachment.

Best regards,

Alain

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f0283f59700 (LWP 7240)):
#0  0x7f0290616ded in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f02943fd74b in _xcb_conn_wait (c=c@entry=0x24a10a0,
cond=cond@entry=0x24a10e0, vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#2  0x7f02943ff0af in xcb_wait_for_event (c=0x24a10a0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#3  0x7f02866c0be8 in QXcbEventReader::run (this=0x24ab270) at
qxcbconnection.cpp:1229
#4  0x7f0290c715d8 in QThreadPrivate::start (arg=0x24ab270) at
thread/qthread_unix.cpp:331
#5  0x7f028fe1c58a in start_thread (arg=0x7f0283f59700) at
pthread_create.c:310
#6  0x7f029061fbfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f027afcb700 (LWP 7245)):
#0  0x7f0290616ded in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f028c60b3ce in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f0274003070, timeout=, context=0x7f0274000990) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7f0274000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3803
#3  0x7f028c60b4e7 in g_main_context_iteration (context=0x7f0274000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x7f0290e3cce8 in QEventDispatcherGlib::processEvents
(this=0x7f02740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f0290df641e in QEventLoop::exec (this=this@entry=0x7f027afcadf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0290c6d277 in QThread::exec (this=this@entry=0x2635340) at
thread/qthread.cpp:503
#7  0x7f02932f970d in QQmlThreadPrivate::run (this=0x2635340) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f0290c715d8 in QThreadPrivate::start (arg=0x2635340) at
thread/qthread_unix.cpp:331
#9  0x7f028fe1c58a in start_thread (arg=0x7f027afcb700) at
pthread_create.c:310
#10 0x7f029061fbfd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0278fe7700 (LWP 7254)):
#0  idleTimerSourceCheck (source=) at
kernel/qeventdispatcher_glib.cpp:214
#1  0x7f028c60aec1 in g_main_context_check
(context=context@entry=0x7f026c000990, max_priority=2147483647,
fds=fds@entry=0x7f026c003270, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3649
#2  0x7f028c60b3e3 in g_main_context_iterate
(context=context@entry=0x7f026c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3805
#3  0x7f028c60b4e7 in g_main_context_iteration (context=0x7f026c000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869
#4  0x7f0290e3cce8 in QEventDispatcherGlib::processEvents
(this=0x7f026c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f0290df641e in QEventLoop::exec (this=this@entry=0x7f0278fe6df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0290c6d277 in QThread::exec (this=this@entry=0x274c680) at
thread/qthread.cpp:503
#7  0x7f02932f970d in QQmlThreadPrivate::run (this=0x274c680) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f0290c715d8 in QThreadPrivate::start 

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[ultr via KDE Bugzilla]

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

--- Comment #5 from ultr  ---
I have checked this with Ark 15.08.3 and Plasma 5.4.3 and it still does not
work.

Both service menu options for fast extraction:
- 'Extract Archive Here, Autodetect Subfolder' and
- 'Extract Archive Here'
try to overwrite files when extracting both attached archives.

Extracting first archive creates this directory tree:
- mycode
- - a.c
- - a.h
Extracting the other archive tries to overwrite it.

This is OK, but there is no option to 'Extract Into a Subfolder',
so that the directory tree would look like that:
- mycode-v1 (named after the archive file name)
- - mycode
- - - a.c
- - - a.h
- mycode-v2 (named after the archive file name)
- - mycode
- - - a.c
- - - a.h

Without the ark's --forcesubfolder parameter it is not even possible to create
the 'Extract Into a Subfolder' service menu item.

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

[kxkb] [Bug 295438] Keyboard layout switcher stops working

[ttrovo via KDE Bugzilla]

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

--- Comment #59 from ttrovo  ---
Are there any plans to fix this ANNOYING bug?
A lot of people hate KDE5 because of such things.

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

[frameworks-frameworkintegration] [Bug 356840] Crash in KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper

[Raman Gupta via KDE Bugzilla]

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

Raman Gupta  changed:

   What|Removed |Added

 CC||rocketra...@gmail.com

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

[okular] [Bug 357579] Okular-15.12.0: page numbers text area not sized correctly when refreshing a document

[Till Schäfer via KDE Bugzilla]

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

--- Comment #1 from Till Schäfer  ---
Created attachment 96474
  --> https://bugs.kde.org/attachment.cgi?id=96474=edit
screenshot of the bug

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

[plasmashell] [Bug 357580] Seg Fault in plasma shell

[Alain Toussaint via KDE Bugzilla]

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

Alain Toussaint  changed:

   What|Removed |Added

 CC||alain.toussa...@securivm.ca

--- Comment #1 from Alain Toussaint  ---
Created attachment 96475
  --> https://bugs.kde.org/attachment.cgi?id=96475=edit
Funtoo emerge --info

Platform description.

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

[umbrello] [Bug 355616] Generated python code does not have attributes or a constructor

[Sean Engelhardt via KDE Bugzilla]

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

--- Comment #18 from Sean Engelhardt  ---
Hi. 

> Did you find any time to take a look ? 
> To have the fixes in 2.18.1 (KDE Applications 15.12.1) it is required to get 
> this into 2016 
> Jan 6 (see ... )

unfortunately I will be pretty busy until 2016-01-15.

I need to finish my paper for "Model Driven Architecture" (master program)
until Feb. 15, so I will Definitly take a look at this again before KDE
Applications 15.12.2 tagging.

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

[kate] [Bug 357582] New: Japanese characters are not rendered properly (bottom is cut)

[Mislav via KDE Bugzilla]

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

Bug ID: 357582
   Summary: Japanese characters are not rendered properly (bottom
is cut)
   Product: kate
   Version: unspecified
  Platform: Archlinux Packages
   URL: http://i.imgur.com/GCUHPZA.png
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: mislav.blazev...@gmail.com

There isn't much else to add. Screenshot says it all.

Reproducible: Always

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

[konversation] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled

[Martin Ueding via KDE Bugzilla]

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

Martin Ueding  changed:

   What|Removed |Added

 CC||von.kde.org@martin-ueding.d
   ||e

--- Comment #3 from Martin Ueding  ---
I have the same problem with Klipper on Fedora 23 as I use Awesome WM.

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

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[ultr via KDE Bugzilla]

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

--- Comment #8 from ultr  ---
Created attachment 96471
  --> https://bugs.kde.org/attachment.cgi?id=96471=edit
ark-extract-menu.png

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

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[ultr via KDE Bugzilla]

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

--- Comment #7 from ultr  ---
Created attachment 96470
  --> https://bugs.kde.org/attachment.cgi?id=96470=edit
mycode-v2.tar.gz

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

[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item

[ultr via KDE Bugzilla]

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

--- Comment #6 from ultr  ---
Created attachment 96469
  --> https://bugs.kde.org/attachment.cgi?id=96469=edit
mycode-v1.tar.gz

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

[digikam] [Bug 357577] New: crashes after splash screen with ASSERT failure in QVector

[Thomas Eschenbacher via KDE Bugzilla]

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

Bug ID: 357577
   Summary: crashes after splash screen with ASSERT failure in
QVector
   Product: digikam
   Version: 5.0.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: thomas.eschenbac...@gmx.de

Created attachment 96472
  --> https://bugs.kde.org/attachment.cgi?id=96472=edit
gdb backtrace

I compiled digikam (today's latest source from git), but soon after showing the
splash screen it crashes with an assertion in Qt. This also happens with a new
dummy user account that did not use digikam-4 before and thus has no album, no
database etc.

git commit: bb7b7ef566a1b9606f35b237ddc4b3267299209f

Gentoo Linux @ x86_64
gcc-4.8.5, qt-5.5.1

I started digikam with gdb and attached the backtrace.

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

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #2 from caulier.gil...@gmail.com ---
It sound like a Qt5 bug. 

#13 0x0037b2808c61 in QAbstractItemModel::beginInsertRows (this=0x13c1c40,
parent=..., first=0, last=0)
at itemmodels/qabstractitemmodel.cpp:2602
#14 0x7795dc64 in Digikam::AbstractAlbumModel::slotAlbumAboutToBeAdded
(this=0x13c1c40, album=0x22514a0, 
parent=0x32a94c0, prev=0x0) at
/usr/src/packages/multimedia/digikam/core/libs/models/abstractalbummodel.cpp:438

When a parent album need to be inserted in the model (prev = 0),
QAbstractItemModel::beginInsertRows() i scalled with 2 arguments to 0.

I tried to reproduce the problem here, and it's not reproducible (Qt 5.5.1)

Which Qt version did you use ?

Gilles Caulier

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

[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive

[via KDE Bugzilla]

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

--- Comment #13 from jeremy9...@gmail.com ---
I just tested, for fun, the Nouveau drivers and the windows don't seem to be
unresponsive anymore !

Maybe it's a problem with the Nvidia drivers ?

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

[okular] [Bug 357579] New: Okular-15.12.0: page numbers text area not sized correctly when refreshing a document

[Till Schäfer via KDE Bugzilla]

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

Bug ID: 357579
   Summary: Okular-15.12.0: page numbers text area not sized
correctly when refreshing a document
   Product: okular
   Version: 0.24.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: till2.schae...@uni-dortmund.de

On the bottom of Okulars main window, there is the page number indicator. The
left field (where you see or type in the current page number) is sometimes not
sized correctly (see attached screenshot). This happens whenever I refresh the
underlying document, e.g. when recompiling a pdf using latex. Resizing the
window fixes the the glitch until i refresh the document again.

Reproducible: Always

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

[kontact] [Bug 357581] New: Crash when clicking on email address in message header

[Martin Tlustos via KDE Bugzilla]

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

Bug ID: 357581
   Summary: Crash when clicking on email address in message header
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com

Application: kontact ()

Qt Version: 5.4.2
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I wanted to write an email to person and clicked on the email address in an
email he had written to me. Result: crash
The crash happens both in kmail standalone as well as within kontact.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fecd8a69700 (LWP 4090)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fecfdd7748b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fecfdd774c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fecf94f66aa in start_thread (arg=0x7fecd8a69700) at
pthread_create.c:333
#4  0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fec97e3b700 (LWP 4091)):
#0  0x7fecfec5a49d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fecf88bc4e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecf8878cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fecf8879190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fecf88792fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fecff79f29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fecff74575a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fecff5633d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fecff5682be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fecf94f66aa in start_thread (arg=0x7fec97e3b700) at
pthread_create.c:333
#10 0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fec96346700 (LWP 4092)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fecfda855b4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fecfdda7341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fecf94f66aa in start_thread (arg=0x7fec96346700) at
pthread_create.c:333
#4  0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fec95b26700 (LWP 4093)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fecfda865e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fecfdda7341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fecf94f66aa in start_thread (arg=0x7fec95b26700) at
pthread_create.c:333
#4  0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fec95325700 (LWP 4094)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fecfda865e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fecfdda7341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fecf94f66aa in start_thread (arg=0x7fec95325700) at
pthread_create.c:333
#4  0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fec94b24700 (LWP 4095)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fecfda865e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fecfdda7341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fecf94f66aa in start_thread (arg=0x7fec94b24700) at
pthread_create.c:333
#4  0x7fecfec69eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fece3778880 (LWP 4088)):
[KCrash Handler]
#6  0x7fed00110c0d in QAbstractSlider::setValue(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7fecfb0f6959 in KViewStateSerializerPrivate::restoreScrollBarState
(this=0x29d5260) at ../../src/kviewstateserializer.cpp:55
#8  KViewStateSerializer::qt_static_metacall (_o=,
_id=, _a=, _c=) at
./moc_kviewstateserializer.cpp:73
#9  0x7fecff779651 in QObject::event(QEvent*) () from

[kturtle] [Bug 357576] New: Mint (Ubuntu) package lacks dependencies

[Paul Fedele via KDE Bugzilla]

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

Bug ID: 357576
   Summary: Mint (Ubuntu) package lacks dependencies
   Product: kturtle
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: c...@kde.nl
  Reporter: pfed...@gmail.com

After installing kturtle in Mint 17.3 Cinnamon (64 bit), kturtle crashed every
time file actions (open / save) were used.  The installation of
kdelibs5-plugins fixed this issue.

Please add kdelibs5-plugins as a dependency when packaging kturtle.

Reproducible: Always

Steps to Reproduce:
1. Install Mint 17.3 Cinnamon (64 bit) 
2. sudo apt-get install kturtle
3. run kturtle from the terminal (to see the errors upon crashing).
4. Click "Save", "Save As", or "Open"

Actual Results:  
kturtle crashes because it can't access KDE libraries.  The installation of
kdelibs5-plugins fixes the issue.

Expected Results:  
kturtle should have opened a save/open dialogue.

This issue occurred in multiple (30+) machines running Cinnamon.  It did not
occur using Mate.

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

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[Thomas Eschenbacher via KDE Bugzilla]

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

--- Comment #1 from Thomas Eschenbacher  ---
Created attachment 96473
  --> https://bugs.kde.org/attachment.cgi?id=96473=edit
console output up to the crash

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

[choqok] [Bug 357588] New: should use NetworkManager online status

[Lisandro Damián Nicanor Pérez Meyer via KDE Bugzilla]

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

Bug ID: 357588
   Summary: should use NetworkManager online status
   Product: choqok
   Version: 1.5
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mehrdad.mom...@gmail.com
  Reporter: perezme...@gmail.com
CC: scarp...@kde.org

Original bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809600

Dominik reported:

  Choqok autostarts with my KDE session and then immediately tries to load
  messages. If this happens before I connect to a network, Choqoks pops up
  an alert that it cannot resolve the server address.
  .
  NetworkManager provides a D-Bus interface to check whether the system is
  connected to the network, so applications like Choqok can verify that
  before trying anything like DNS or conecting to any servers.
  .
  Choqok should use this interface in order to not nag the user with
  unnecessary errors.

I will add to the above that this should happen only if NM is detected running.
Not everyone uses NM.

Reproducible: Always

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

[KBibTeX] [Bug 357568] kbibtex (git) fails to compile

[Thomas Fischer via KDE Bugzilla]

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

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |NEEDSINFO
  Latest Commit||c68189816a5e2779c99839920e4
   ||1502eb667a634

--- Comment #2 from Thomas Fischer  ---
Compiled for me, but I added an extra #include statement on QRegExp. Please
test and confirm commit c68189816a5e2779c998:
http://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/c68189816a5e2779c998

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

[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View

[Wulf via KDE Bugzilla]

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

--- Comment #11 from Wulf  ---
(In reply to Wulf from comment #10)
> I can't reproduce it anymore :-?
Sorry wrong.

It' reproducible
- two panes (one pane is my external NTFS USB Drive)
- in the other pane a folder with two different kinds of files (media and text)
- you expand the this folder (you don not change into this folder)
- you move the text file to trash
- you try to copy the folder (now with only one expanded media-file) per drag
and drop to the external pane
- error occurs

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

[trojita] [Bug 356865] Sent messages with Bcc receipients does not list Bcc

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #2 from Jan Kundrát  ---
> In this function, the
> Bcc header is not included (as is appropriate for the version 
> of the mail that is sent out).

Yeah, it seems that some MTAs out there (Exim is an example, [1]) do not 
strip out the Bcc headers during submission through ESMTP. Because Trojita 
tries to save bandwidth (see our support for BURL, CATENATE etc), there's a 
big value in only having to upload just one instance of an outgoing 
message.

It would be very easy to write out Bcc into the sent folder, but then we 
have to ensure that the Bcc is not leaked to the actual outgoing message. 
This is doable by, e.g., employing chunked message submission, where the 
composer remembers which part of the header contains this privacy-sensitive 
data, and white outs their content.

Here's how to do it:

1) Generate the plaintext of the message, place the Bcc header into a 
well-known place (end of all headers sounds like a trivial fix, if it's 
legal),
2) Remember the offsets of the beginning and end of this sensitive area,
3) Change the code to not treat the just-saved message as a single entity, 
but rather as a pair of (stuff before the whitened-out, stuff after), and 
pass this pair to BURL.

[1] http://marc.info/?l=mutt-dev=112930534206625

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

[kdenlive] [Bug 357589] New: Duplicates video clips and changes durations of audio crossfades

[Barade via KDE Bugzilla]

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

Bug ID: 357589
   Summary: Duplicates video clips and changes durations of audio
crossfades
   Product: kdenlive
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: barade.bar...@web.de

kdenlive duplicates video clips sometimes and changes durations of audio
crossfades randomly.
The whole project was broken. Two clips were duplicated.
The durations of the first and the last audio crossfade were changed. The first
duration was longer than the clip itself and the second duration become 0.
I used very small durations.

kdenlive is absolutely unusable with this bug!

I am using version 0.9.10 4.14.14, 4.14.14-4.fc23 Fedora

Reproducible: Always

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

[k3b] [Bug 357591] New: K3B Start

[via KDE Bugzilla]

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

Bug ID: 357591
   Summary: K3B Start
   Product: k3b
   Version: 2.0.80
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: mail-fuer-...@gmx.de
CC: mich...@jabster.pl, tr...@kde.org

Application: k3b (2.0.80)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
SUSE 13.1+13.2 gleicher Fehler .Hardware Dell Optiplex 755.DVD-Brenner??

The crash can be reproduced every time.

-- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0cf7f8c900 (LWP 2442))]

Thread 2 (Thread 0x7f0cdafb6700 (LWP 2443)):
#0  0x7f0cf1802c5d in poll () at /lib64/libc.so.6
#1  0x7f0cebd79be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0cebd79cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0cf2ec30de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f0cf2e94e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f0cf2e95165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f0cf2d920bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f0cf2e76783 in  () at /usr/lib64/libQtCore.so.4
#8  0x7f0cf2d9479f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f0cf15110a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f0cf180b08d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f0cf7f8c900 (LWP 2442)):
[KCrash Handler]
#5  0x7f0cf7c07050 in K3b::Device::from2Byte(unsigned char const*)
(d=d@entry=0x7ffc97f71002 ) at /usr/src/debug/k3b/libk3bdevice/k3bdeviceglobals.cpp:218
#6  0x7f0cf7bf93d8 in
K3b::Device::Device::getSupportedWriteSpeedsVia2A(QList&,
K3b::Device::MediaType) const (this=this@entry=0x1509a00, list=...,
mediaType=mediaType@entry=K3b::Device::MEDIA_UNKNOWN) at
/usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3254
#7  0x7f0cf7bf9e5b in K3b::Device::Device::determineSupportedWriteSpeeds()
const (this=this@entry=0x1509a00) at
/usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3213
#8  0x7f0cf7bf9f90 in K3b::Device::Device::determineMaximalWriteSpeed()
const (this=this@entry=0x1509a00) at
/usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3164
#9  0x7f0cf7bfb0b9 in K3b::Device::Device::init(bool) (this=0x1509a00,
bCheckWritingModes=bCheckWritingModes@entry=true) at
/usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:427
#10 0x7f0cf7c02d90 in
K3b::Device::DeviceManager::addDevice(K3b::Device::Device*)
(this=this@entry=0x11c2580, device=device@entry=0x1509a00) at
/usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:379
#11 0x7f0cf7c03173 in K3b::Device::DeviceManager::addDevice(Solid::Device
const&) (this=this@entry=0x11c2580, solidDevice=...) at
/usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:367
#12 0x0054df5d in K3b::AppDeviceManager::addDevice(Solid::Device
const&) (this=0x11c2580, solidDev=...) at
/usr/src/debug/k3b/src/k3bappdevicemanager.cpp:120
#13 0x7f0cf7c02089 in K3b::Device::DeviceManager::checkDevice(Solid::Device
const&) (this=this@entry=0x11c2580, dev=...) at
/usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:253
#14 0x7f0cf7c022a2 in K3b::Device::DeviceManager::scanBus()
(this=0x11c2580) at /usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:241
#15 0x7f0cf789a387 in K3b::Core::init() (this=this@entry=0x10a40c0) at
/usr/src/debug/k3b/libk3b/core/k3bcore.cpp:208
#16 0x0050f091 in K3b::Application::Core::init() (this=0x10a40c0) at
/usr/src/debug/k3b/src/k3bapplication.cpp:273
#17 0x0050da66 in K3b::Application::Core::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _id=,
_a=, _c=) at
/usr/src/debug/k3b/build/src/k3bapplication.moc:141
#18 0x7f0cf2eae59e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#19 0x7f0cf1fb276c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#20 0x7f0cf1fb8cad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#21 0x7f0cf719ae0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#22 0x7f0cf2e962ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#23 0x7f0cf2e9957d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#24 0x7f0cf2ec38fe in  () at /usr/lib64/libQtCore.so.4
#25 0x7f0cebd79a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#26 0x7f0cebd79c48 in  () at /usr/lib64/libglib-2.0.so.0
#27 0x7f0cebd79cec in 

[plasmashell] [Bug 357570] Copy text into clipboard in netbeans editor causes plasmashell freeze

[Michal Hlavac via KDE Bugzilla]

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

--- Comment #3 from Michal Hlavac  ---
I can see in sysout repeating line:

QXcbClipboard::setMimeData: Cannot set X11 selection owner
QXcbClipboard::setMimeData: Cannot set X11 selection owner

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

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #5 from Maik Qualmann  ---
Please try again with latest git commit. The crash is not to reproduce here.

Maik

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

[dolphin] [Bug 354558] Dolphin crashed when accessing to "Configure Dolphin"

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #12 from Wolfgang Bauer  ---
(In reply to Fabian Vogt from comment #11)
> Dolphin does indeed do some weird stuff with its Control button:
> in DolphinMainWindow::updateControlMenu:
>  
> // All actions get cleared by QMenu::clear(). The sub-menus are deleted
> // by connecting to the aboutToHide() signal from the parent-menu.
> connect(menu, ::aboutToHide, helpMenu, ::deleteLater);

This seems to be the problem indeed. Removing those connects does fix the
crashes for me...

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

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[Thomas Eschenbacher via KDE Bugzilla]

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

Thomas Eschenbacher  changed:

   What|Removed |Added

 CC||thomas.eschenbac...@gmx.de

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

[plasmashell] [Bug 357578] New: Plasma crash after disconnecting external monitor

[steffko via KDE Bugzilla]

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

Bug ID: 357578
   Summary: Plasma crash after disconnecting external monitor
   Product: plasmashell
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: s...@gmx.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.2)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-5.g008195a-default x86_64
Distribution: "openSUSE Tumbleweed (20160101) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I have used an external projector to display Firefox content (Kahoot!).
Compositing is not enabled and the internal display was turned off. I'm using a
rather weak Asus eeePC 1015PED (Intel Atom N475) after all... After closing
Firefox and disconnecting the projector Plasma crashed.

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f6ec5ece700 (LWP 1130)):
#0  0x7f6ed5cf224d in poll () from /lib64/libc.so.6
#1  0x7f6edabc3432 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f6edabc5007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f6ec801de29 in QXcbEventReader::run (this=0x2127b40) at
qxcbconnection.cpp:1229
#4  0x7f6ed63e294f in QThreadPrivate::start (arg=0x2127b40) at
thread/qthread_unix.cpp:331
#5  0x7f6ed54f94a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f6ed5cfabdd in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f6ebf1d2700 (LWP 1150)):
#0  0x7f6ed5cf224d in poll () from /lib64/libc.so.6
#1  0x7f6ed23e8264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6ed23e836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6ed660752b in QEventDispatcherGlib::processEvents
(this=0x7f6eb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6ed65b163a in QEventLoop::exec (this=this@entry=0x7f6ebf1d1cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6ed63ddb1c in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f6ed96aa9a5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f6ed63e294f in QThreadPrivate::start (arg=0x21fdb10) at
thread/qthread_unix.cpp:331
#8  0x7f6ed54f94a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6ed5cfabdd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f6eb1f84700 (LWP 1183)):
#0  0x7f6ed23e7980 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f6ed23e8193 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6ed23e836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6ed660752b in QEventDispatcherGlib::processEvents
(this=0x7f6eac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6ed65b163a in QEventLoop::exec (this=this@entry=0x7f6eb1f83cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6ed63ddb1c in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f6ed96aa9a5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f6ed63e294f in QThreadPrivate::start (arg=0x234df70) at
thread/qthread_unix.cpp:331
#8  0x7f6ed54f94a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6ed5cfabdd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f6eabfff700 (LWP 1184)):
#0  0x7f6ed5cf2227 in poll () from /lib64/libc.so.6
#1  0x7f6ed23e8264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6ed23e836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6ed660752b in QEventDispatcherGlib::processEvents
(this=0x7f6ea40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6ed65b163a in QEventLoop::exec (this=this@entry=0x7f6eabffecf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6ed63ddb1c in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f6ed96aa9a5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f6ed63e294f in QThreadPrivate::start (arg=0x237bc80) at
thread/qthread_unix.cpp:331
#8  0x7f6ed54f94a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6ed5cfabdd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f6eaadf6700 (LWP 1189)):
#0  0x7f6ed54ff07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6edbe51a84 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f6edbe51ac9 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f6ed54f94a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f6ed5cfabdd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f6e23fff700 (LWP 1194)):
#0  0x7f6ed5cee22d 

[kmahjongg] [Bug 344778] libkmahjongg installs lib twice

[Raymond Wooninck via KDE Bugzilla]

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

--- Comment #4 from Raymond Wooninck  ---
Git commit e8a37284fca8e74986ce3a3ff979afd8e70484af by Raymond Wooninck.
Committed on 05/01/2016 at 14:59.
Pushed by rwooninck into branch 'master'.

Remove the double install call for the library

M  +0-2CMakeLists.txt

http://commits.kde.org/libkmahjongg/e8a37284fca8e74986ce3a3ff979afd8e70484af

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

[kmix] [Bug 353357] kmix uses 100% cpu (with Kubuntu 15.04 and KDE5)

[Luc Lalonde via KDE Bugzilla]

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

Luc Lalonde  changed:

   What|Removed |Added

 CC||luc.lalo...@polymtl.ca

--- Comment #2 from Luc Lalonde  ---
I can confirm this problem:

Platform:  Fedora 22
Kernel:  4.2.8-200.fc22.x86_64
Kmix:  15.04

The whole Plasma 5 session becomes unuseable until I kill Kmix.

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

[kwin] [Bug 357543] drmModeSetCrtc not called when presenting GBM buffer (Wayland)

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
possible patch (not tested):

diff --git a/backends/drm/drm_backend.cpp b/backends/drm/drm_backend.cpp
index 128bdc2..7b1b240 100644
--- a/backends/drm/drm_backend.cpp
+++ b/backends/drm/drm_backend.cpp
@@ -614,7 +614,7 @@ bool DrmOutput::present(DrmBuffer *buffer)
 if (m_currentBuffer) {
 return false;
 }
-if (m_lastStride != buffer->stride()) {
+if (m_lastStride != buffer->stride() || m_lastGbm != buffer->isGbm()) {
 // need to set a new mode first
 if (!setMode(buffer)) {
 return false;
@@ -811,6 +811,7 @@ bool DrmOutput::setMode(DrmBuffer *buffer)
 {
 if (drmModeSetCrtc(m_backend->fd(), m_crtcId, buffer->bufferId(), 0, 0,
_connector, 1, _mode) == 0) {
 m_lastStride = buffer->stride();
+m_lastGbm = buffer->isGbm();
 return true;
 } else {
 qCWarning(KWIN_DRM) << "Mode setting failed";
diff --git a/backends/drm/drm_backend.h b/backends/drm/drm_backend.h
index af22594..b247776 100644
--- a/backends/drm/drm_backend.h
+++ b/backends/drm/drm_backend.h
@@ -181,6 +181,7 @@ private:
 quint32 m_crtcId = 0;
 quint32 m_connector = 0;
 quint32 m_lastStride = 0;
+bool m_lastGbm = false;
 drmModeModeInfo m_mode;
 DrmBuffer *m_currentBuffer = nullptr;
 DrmBuffer *m_blackBuffer = nullptr;
@@ -221,6 +222,9 @@ public:
 gbm_bo *gbm() const {
 return m_bo;
 }
+bool isGbm() const {
+return m_bo != nullptr;
+}
 void releaseGbm();

 private:

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

[krunner] [Bug 357583] New: Crash when using krunner

[Dariusz Ostolski via KDE Bugzilla]

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

Bug ID: 357583
   Summary: Crash when using krunner
   Product: krunner
   Version: 5.5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: dariusz.ostol...@gmail.com

Application: krunner (5.5.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160101) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
1. Used keyboard shortcut: Alt+F2
2. Entered: "konsole"
3. hit "Enter"

The crash can be reproduced sometimes.

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

Thread 19 (Thread 0x7fe008288700 (LWP 1749)):
#0  0x7fe01978224d in poll () from /lib64/libc.so.6
#1  0x7fe018c8a432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fe018c8c007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fe00a3d7e29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fe019e7394f in QThreadPrivate::start (arg=0x217b9e0) at
thread/qthread_unix.cpp:331
#5  0x7fe0175fd4a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fe01978abdd in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7fdffbbb3700 (LWP 1773)):
#0  0x7fe01978224d in poll () from /lib64/libc.so.6
#1  0x7fe016c8d264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fe016c8d36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fe01a09852b in QEventDispatcherGlib::processEvents
(this=0x7fdff40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fe01a04263a in QEventLoop::exec (this=this@entry=0x7fdffbbb2cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fe019e6eb1c in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fe01c50b9a5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7fe019e7394f in QThreadPrivate::start (arg=0x23f7b40) at
thread/qthread_unix.cpp:331
#8  0x7fe0175fd4a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fe01978abdd in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7fdfe68b5700 (LWP 2281)):
#0  0x7fe01760307f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe019e74abb in wait (time=18446744073709551615, this=0x29cd3e0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x25aed90,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fdff83dd0eb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x2500b00, th=) at
/usr/src/debug/threadweaver-5.17.0/src/weaver.cpp:594
#4  0x7fdff83dde37 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x2500b00,
th=th@entry=0x412b2e0, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/usr/src/debug/threadweaver-5.17.0/src/weaver.cpp:554
#5  0x7fdff83e1d98 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x24411b0, th=0x412b2e0, wasBusy=) at
/usr/src/debug/threadweaver-5.17.0/src/workinghardstate.cpp:66
#6  0x7fdff83dd059 in ThreadWeaver::Weaver::applyForWork (this=, th=0x412b2e0, wasBusy=) at
/usr/src/debug/threadweaver-5.17.0/src/weaver.cpp:568
#7  0x7fdff83e1de2 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x24411b0, th=0x412b2e0, wasBusy=) at
/usr/src/debug/threadweaver-5.17.0/src/workinghardstate.cpp:73
#8  0x7fdff83dd059 in ThreadWeaver::Weaver::applyForWork (this=, th=0x412b2e0, wasBusy=) at
/usr/src/debug/threadweaver-5.17.0/src/weaver.cpp:568
#9  0x7fdff83dfe23 in ThreadWeaver::Thread::run (this=0x412b2e0) at
/usr/src/debug/threadweaver-5.17.0/src/thread.cpp:103
#10 0x7fe019e7394f in QThreadPrivate::start (arg=0x412b2e0) at
thread/qthread_unix.cpp:331
#11 0x7fe0175fd4a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7fe01978abdd in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7fdfe60b4700 (LWP 2282)):
#0  0x7fe01760307f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe019e74abb in wait (time=18446744073709551615, this=0x29cd3e0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x25aed90,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fdff83dd0eb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x2500b00, th=) at
/usr/src/debug/threadweaver-5.17.0/src/weaver.cpp:594
#4  0x7fdff83dde37 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x2500b00,
th=th@entry=0x3c749e0, threadWasBusy=threadWasBusy@entry=false,

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[Thomas Eschenbacher via KDE Bugzilla]

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

--- Comment #3 from Thomas Eschenbacher  ---
as I wrote above: Qt-5.5.1
It is 100% reproducible here.

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

[konversation] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled

[Panard via KDE Bugzilla]

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

Panard  changed:

   What|Removed |Added

 CC|pan...@inzenet.org  |

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

[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird

[Vladislav Vorobiev via KDE Bugzilla]

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

--- Comment #16 from Vladislav Vorobiev  ---
(In reply to Vladislav Vorobiev from comment #15)
> My experience says that some importan't features or bugs kde team simply
> ignore, 
> Using kontact or Kmail accross many computers seems to be not realy
> important.
> I try to vote for it.

Oha, it works in  KMail 4.14.10 for me...
Thanks great KDE team!

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

[choqok] [Bug 357602] open or open then closed, causes lumina to reset with "out of swap space"

[via KDE Bugzilla]

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

--- Comment #2 from rdmyers...@gmail.com ---
Since that is the only program that displays this behaviour, I would disagree

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

[dolphin] [Bug 354848] file association loophole: application automatically as default, even if i delete it from the list

[Pavel Mendl via KDE Bugzilla]

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

Pavel Mendl  changed:

   What|Removed |Added

 CC||pavel_me...@centrum.cz

--- Comment #5 from Pavel Mendl  ---
Confirming behavior on Linux  4.3.0-1-amd64 #1 SMP Debian 4.3.3-2
(2015-12-17) x86_64 GNU/Linux (KDE version latest testing = 4:15.08.3-1)

Adding my observation about other (GUI) way to reproduce in hope this helps
with bug source insulation:
In Dolphin right click to Properties, here push File Type Options. File type
/ dialog opens. Now:
1) Using Add button and adding new application has following effects:
a) enlists this application into ~/.local/share/applications/mimeapps.list
(making it persisten)
b) adds the association as highest priority (default)
2) Edit button opens dialog showing 0B (zero bytes) length of the file (with
reported name .desktop) and does not show/allow to change
association parameters. My opinion is that this procedure somehow creates
.desktop (in some system location) with no content, while it should
be filled with some useful parameters and later mimeaps.list pointing to that
file is confused (and  thus does not process removal properly). But it may be
million other ways too as ad 2) behavior is true even for previously existing, 
properly working associations (?!).

Related as well was my bug 355194, even if strange application I used in the
exact case was misleading.  The core of problem is ill-behavior of Dolphin
(maybe even KDE core) mime associations functionality. Thanks god for the
manual mimeapps.list editing workaround, however some more systematic solution
would really suit to KDE.

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

[choqok] [Bug 357588] should use NetworkManager online status

[Mehrdad Momeny via KDE Bugzilla]

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

Mehrdad Momeny  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Target Milestone|--- |1.6
 Ever confirmed|0   |1

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

[kwin] [Bug 357605] New: Desktop Grid layouts are limited, additional layouts would be great.

[Yousef H via KDE Bugzilla]

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

Bug ID: 357605
   Summary: Desktop Grid layouts are limited, additional layouts
would be great.
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
   URL: http://askubuntu.com/questions/702456/can-you-change-t
he-desktop-grid-layout-in-kde
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: after.dark...@gmail.com

The URL describes the issue quite nicely. Please ignore this if possible.

 The current three layouts, are basically the same with one difference(AFAIK);
one row, dynamic rows, or custom rows. I am not talking about those. layouts.
The issue appears when one use multi monitors, where each monitor is showing
its view of each VD(virtual desktop). What I want to suggest is, to have the
whole VD show up in one monitor.

Reproducible: Always

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

[kompare] [Bug 329912] No underscore w/ font "DejaVu Sans Mono 10pt"

[David Korth via KDE Bugzilla]

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

David Korth  changed:

   What|Removed |Added

 CC||gerbils...@gerbilsoft.com

--- Comment #4 from David Korth  ---
I've been encountering this problem for quite some time on any program that
uses the KDE text editor widget. (KWrite, Kate, KDevelop, etc.) When using
DejaVu Sans Mono, 10pt, underscores don't render for normal text. They *do*
render if the text is bold.

Version information:
- KWrite version 4.14.7
- Using KDE development platform 4.14.12

Interestingly, Qt Designer does NOT show this problem. Underscores render
perfectly for DejaVu Sans Mono 10pt.

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

[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||m...@one.com

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

[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive

[Pulfer via KDE Bugzilla]

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

--- Comment #14 from Pulfer  ---
(In reply to jeremy9856 from comment #13)
> I just tested, for fun, the Nouveau drivers and the windows don't seem to be
> unresponsive anymore !
> 
> Maybe it's a problem with the Nvidia drivers ?

But VirtualBox with 3D Acceleration turned off is also affected.

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

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

[Thomas Eschenbacher via KDE Bugzilla]

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

--- Comment #6 from Thomas Eschenbacher  ---
how can I get this source version you are talking about?

I followed the instructions on the project homepage, which lead me to this
repo:
> git remote -v
origin  git://anongit.kde.org/digikam-software-compilation (fetch)
origin  git://anongit.kde.org/digikam-software-compilation (push)

but your change is not visible there.
I tried to "git remote set-url origin git://anongit.kde.org/digikam.git" but
that has lead to a big mess, had to restore the local repo from backup.

What should I do now?

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

[akregator] [Bug 349284] Akregator crashes when opening webpage

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED
   Version Fixed In||5.2

--- Comment #1 from Laurent Montel  ---
I ported to webkit in 5.2.
I closed it as it was khtml crashs.

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

[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird

[Vladislav Vorobiev via KDE Bugzilla]

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

Vladislav Vorobiev  changed:

   What|Removed |Added

 CC||v...@piratweb.com

--- Comment #15 from Vladislav Vorobiev  ---
My experience says that some importan't features or bugs kde team simply
ignore, 
Using kontact or Kmail accross many computers seems to be not realy important.
I try to vote for it.

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

[kdenlive] [Bug 357322] Clip Properties: rounded frame rate, b/s vs kb/s, superfluous digit in audio bitrate

[via KDE Bugzilla]

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

--- Comment #4 from qubo...@gmail.com ---
Thanks!

Two possible small issues:
1. (cosmetic) "Frame rate" values are missing " fps" at the end (ffprobe has
it)
2. (not sure) "Bitrate" might be better as "Total bitrate", at least that's
what the author of  http://video.stackexchange.com/questions/11955/ used to
differentiate between audio, video and total bitrate.

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

[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying

[Michael via KDE Bugzilla]

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

--- Comment #5 from Michael  ---
Same problem here. Started this morning.
When I open konsole through the menu or when opening it on the second screen
from XTerm it opens with the background, and its not possible to change
anything, If opening on my primary screen, it opens correctly.

The output when opening the console from XTerm:

[mih@localhost ~]$ konsole
QCoreApplication::arguments: Please instantiate the QApplication object first
[mih@localhost ~]$ The font for use in the terminal has not been matched
exactly. Perhaps it has not been found properly.
The font for use in the terminal has not been matched exactly. Perhaps it has
not been found properly.
0x29633a0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1db3800) ): Attempt to set a screen on a child window.
0x2963940 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1db3800) ): Attempt to set a screen on a child window.
0x2964630 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1db3800) ): Attempt to set a screen on a child window.
0x29d6220 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1db3800) ): Attempt to set a screen on a child window.
0x29c8d50 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1db3800) ): Attempt to set a screen on a child window.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1700, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1703, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1711, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1714, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1721, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1728, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1736, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1742, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1751, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1758, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1765, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1774, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1777, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1792, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1810, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1828, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1836, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1844, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1852, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1860, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1868, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1876, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1884, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1892, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1900, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1908, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1916, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1925, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1933, resource id: 8388711,
major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1941, resource id: 8388711,
major code: 130 (Unknown), minor code: 3

[KBibTeX] [Bug 357568] New: kbibtex (git) fails to compile

[Gandalf Lechner via KDE Bugzilla]

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

Bug ID: 357568
   Summary: kbibtex (git) fails to compile
   Product: KBibTeX
   Version: git (master)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Compiling/packaging
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: gandalflech...@gmail.com

The error message that I get when trying to compile kbibtex from its git
repository (checked out on 5 January) is attached.


Reproducible: Always

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

[krita] [Bug 357559] crash on opening PSD file

[Alexander Opitz via KDE Bugzilla]

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

--- Comment #2 from Alexander Opitz  ---
I dived a bit into the code. The illness comes from frame

#13 0x7f09e2eaa9f9 in PSDLoader::decode
https://github.com/KDE/krita/blob/master/krita/plugins/formats/psd/psd_loader.cpp#L259

newLayer seems null.


(gdb) f 13
(gdb) print newLayer
$4 = {d = 0x0}


This can only happen if layerRecord->infoBlocks.sectionDividerType != psd_other
AND groupStack.isEmpty()
(https://github.com/KDE/krita/blob/master/krita/plugins/formats/psd/psd_loader.cpp#L201
ff).


(gdb) print *layerRecord
$2 = {error = {static null = {}, static shared_null = {ref =
{_q_value = 373059}, alloc = 0, size = 0, data = 0x7f26c4b1493a
, clean = 0, 
  simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved =
0, array = {0}}, static shared_empty = {ref = {_q_value = 2305}, alloc = 0,
size = 0, 
  data = 0x7f26c4b1491a , clean = 0, simpletext =
0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, 
d = 0x7f26c4b14920 , static codecForCStrings = 0x0},
top = 0, left = 0, bottom = 0, right = 0, nChannels = 5, channelInfoRecords =
{{d = 0x3502080, 
  p = 0x3502080}}, blendModeKey = {static null = {}, static
shared_null = {ref = {_q_value = 373059}, alloc = 0, size = 0, 
  data = 0x7f26c4b1493a , clean = 0, simpletext =
0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}},
static shared_empty = {ref = {
_q_value = 2305}, alloc = 0, size = 0, data = 0x7f26c4b1491a
, clean = 0, simpletext = 0, righttoleft = 0,
asciiCache = 0, capacity = 0, reserved = 0, 
  array = {0}}, d = 0x3502130, static codecForCStrings = 0x0},
isPassThrough = 97, opacity = 255 '\377', clipping = 0 '\000',
transparencyProtected = false, visible = true, 
  irrelevant = true, layerMask = {top = 40, left = 368, bottom = 331, right =
1968, defaultColor = 255 '\377', positionedRelativeToLayer = false, disabled =
false, 
invertLayerMaskWhenBlending = false, userMaskDensity = 0 '\000',
userMaskFeather = 0, vectorMaskDensity = 0 '\000', vectorMaskFeather = 0},
blendingRanges = {data = {
  static shared_null = {ref = {_q_value = 16700}, alloc = 0, size = 0, data
= 0x9dc538  "", array = ""}, static shared_empty =
{ref = {_q_value = 271}, 
alloc = 0, size = 0, data = 0x7f26c4b147b8
 "", array = ""}, d = 0x3502160}, blackValues =
"+", whiteValues = "g", 
compositeGrayBlendDestinationRange = 7602281, sourceDestinationRanges = {{d
= 0x7f26c4b14940 , p = 0x7f26c4b14940
}}}, 
  layerName = {static null = {}, static shared_null = {ref =
{_q_value = 373059}, alloc = 0, size = 0, data = 0x7f26c4b1493a
, clean = 0, 
  simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved =
0, array = {0}}, static shared_empty = {ref = {_q_value = 2305}, alloc = 0,
size = 0, 
  data = 0x7f26c4b1491a , clean = 0, simpletext =
0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d
= 0x35021f0, 
static codecForCStrings = 0x0}, infoBlocks = {m_header = @0x7ffc3e96bad0,
error = {static null = {}, static shared_null = {ref =
{_q_value = 373059}, alloc = 0, 
size = 0, data = 0x7f26c4b1493a , clean = 0,
simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0,
array = {0}}, 
  static shared_empty = {ref = {_q_value = 2305}, alloc = 0, size = 0, data
= 0x7f26c4b1491a , clean = 0, simpletext = 0,
righttoleft = 0, asciiCache = 0, 
capacity = 0, reserved = 0, array = {0}}, d = 0x7f26c4b14920
, static codecForCStrings = 0x0}, keys =
{ = {{p = {static shared_null = {
  ref = {_q_value = 44294}, alloc = 0, begin = 0, end = 0, sharable
= 1, array = {0x0}}, d = 0x35022f0}, d = 0x35022f0}}, },
unicodeLayerName = {
  static null = {}, static shared_null = {ref = {_q_value =
373059}, alloc = 0, size = 0, data = 0x7f26c4b1493a ,
clean = 0, simpletext = 0, 
righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array =
{0}}, static shared_empty = {ref = {_q_value = 2305}, alloc = 0, size = 0, 
data = 0x7f26c4b1491a , clean = 0, simpletext
= 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}},
d = 0x35021f0, 
  static codecForCStrings = 0x0}, layerStyleXml = { = {impl =
0x0}, }, embeddedPatterns = {{d = 0x7f26c4b14940
, 
p = 0x7f26c4b14940 }}, sectionDividerType =
psd_open_folder, sectionDividerBlendMode = {static null = {},
static shared_null = {ref = {
  _q_value = 373059}, alloc = 0, size = 0, data = 0x7f26c4b1493a
, clean = 0, simpletext = 0, righttoleft = 0,
asciiCache = 0, capacity = 0, 
reserved 

[krita] [Bug 357569] New: Transformation tool rotation doesn't rotate entire selection

[via KDE Bugzilla]

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

Bug ID: 357569
   Summary: Transformation tool rotation doesn't rotate entire
selection
   Product: krita
   Version: unspecified
  Platform: unspecified
   URL: http://www.filedropper.com/kritabug
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: b8c9a...@opayq.com

After copying and pasting a section of the image repeatedly, I started to
rotate the layers little by little to create a spinning effect. The first layer
rotated perfectly fine but then the other layers weren't being fully rotated. I
also made the all of the layers invisible except for the current one I was
working on and the one below it.

Reproducible: Always

Steps to Reproduce:
1. Select part of an image
2. Copy that part and paste it many times
3. Hide all of the layers except for the one you are rotating and the one below
it
4. Rotate the layer (nothing should happen the first time)
5. Hide that layer and now move onto the next
6. Rotate it again (the parts that aren't rotated should be visible)

Actual Results:  
Rotated only part of the selection

Expected Results:  
Rotate the entire selection

I also have a drawing tablet from Intuos hooked up in Krita and the preview
shows the entire selection moving but after it's done processing, the bug
appears. In the URL section is the download to a video containing the bug.

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