[umbrello] [Bug 373780] Application crashes when opening an UML/XMI class diagram

[Ralf Habacker]

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

--- Comment #3 from Ralf Habacker  ---
Comment on attachment 102852
  --> https://bugs.kde.org/attachment.cgi?id=102852
Crash backtrace

>/usr/lib/libQtGui.so.4
This is a Qt4 build which differs from the initial description

#0 .. __cxxabiv1::__dynamic_cast(void const*,...) (src_ptr=0x0,...) 
#1 .. in UMLObject::asUMLClassifier() (this=) at
/home/daniel/builds/CUSTOM/umbrello/umbrello/umlmodel/umlobject.cpp:1236
#2 .. in UMLClassifierListItem::getType() const (this=this@entry=0x15baab0) at
/home/daniel/builds/CUSTOM/umbrello/umbrello/umlmodel/classifierlistitem.cpp:103

This indicates that UMLObject::asUMLClassifier() got a zero pointer at 

UMLClassifier * UMLClassifierListItem::getType() const
{
return m_pSecondary->asUMLClassifier();
}

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

[kwin] [Bug 373872] error kde virtualbox

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the back trace is lacking debug symbols as normal for Arch based
distros. This means we cannot investigate at all.

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

[plasmashell] [Bug 373878] New: systematic plasmashell segmentation fault

[bugzilla_noreply]

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

Bug ID: 373878
   Summary: systematic plasmashell segmentation fault
   Product: plasmashell
   Version: master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: frank_maes...@hotmail.com
  Target Milestone: 1.0

systematic plasmashell segmentation fault: I've been have to reproduce trying
to open, KDE search field, and looking for whatever subject ends with that
segmentation fault issue...

Would you help.

Below the trace, I can get:

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

Thread 16 (Thread 0x7f85a9ffb700 (LWP 25526)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f868a4a2a5b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f85d2e932bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f85d2e974e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f85d2e97542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f85d2e95353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f868a4a17be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f868958e6ba in start_thread (arg=0x7f85a9ffb700) at
pthread_create.c:333
#10 0x7f8689db782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f85aa7fc700 (LWP 25525)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f868a4a2a5b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f85d2e932bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f85d2e974e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f85d2e97542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f85d2e95353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f868a4a17be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f868958e6ba in start_thread (arg=0x7f85aa7fc700) at
pthread_create.c:333
#10 0x7f8689db782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f85aaffd700 (LWP 25524)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f868a4a2a5b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f85d2e932bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f85d2e974e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f85d2e97542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f85d2e9246d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f85d2e95353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f868a4a17be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f868958e6ba in start_thread (arg=0x7f85aaffd700) at
pthread_create.c:333
#10 0x7f8689db782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f85ab7fe700 (LWP 25523)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f868a4a2a5b in QWaitCondition::wait(QMutex*, unsigned long) () from

[kdialog] [Bug 373677] Command line '--title' option is no longer actioned

[Kai Uwe Broulik]

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

--- Comment #2 from Kai Uwe Broulik  ---
Possible patch https://phabricator.kde.org/D3727

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

[kdialog] [Bug 373677] Command line '--title' option is no longer actioned

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |CONFIRMED

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

[systemsettings] [Bug 373877] New: Segfault when returning to root menu from "Screen Locking"

[bugzilla_noreply]

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

Bug ID: 373877
   Summary: Segfault when returning to root menu from "Screen
Locking"
   Product: systemsettings
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: patrickrif...@yandex.com
  Target Milestone: ---

Created attachment 102869
  --> https://bugs.kde.org/attachment.cgi?id=102869=edit
Stack trace of systemsettings5 at time of crash

OS version: Arch Linux x86_64
KDE Plasma version: 5.8.4
KDE Frameworks version: 5.29.0
Qt version: 5.7.1

## DESCRIPTION ##
When pressing the "All Settings" button at the top left of the System Settings
window while in the "Screen Locking" section under "Workspace", systemsettings
will suffer a segmentation fault.

## STEPS TO REPLICATE ##
1) Open System Settings
2) Select "Desktop Behaviour"
3) Select "Screen Locking"
4) Select "All Settings"
5) System Settings will now segfault

## EXPECTED BEHAVIOUR ##
System Settings is returned to the root menu.

## ACTUAL BEHAVIOUR ##
Segmentation fault, program crashes.

Please see stack trace at time of crash. Unsure if it is complete, I did
recompile systemsettings with debug symbols and install Qt debug packages from
repository as instructed in Arch wiki.

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

[kalzium] [Bug 372671] solver doesn't build with ocaml 4.04

[David Kredba]

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

David Kredba  changed:

   What|Removed |Added

 CC||nheghathivhis...@gmail.com

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

[konsole] [Bug 350651] Konsole has scrolling artifacts if HiDPI screen with scaling in Qt

[bugzilla_noreply]

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

--- Comment #8 from lukebe...@hotmail.com ---
The fractional scaling factor version of this bug was fixed in 

Konsole Version 16.12.0
KDE Frameworks 5.29.0
Qt 5.7.1 (built against 5.7.1)

Although my artifacts seemed slightly different than these artifacts, I think
it was the same issue and it has been resolved.

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[bugzilla_noreply]

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

lukebe...@hotmail.com changed:

   What|Removed |Added

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

--- Comment #3 from lukebe...@hotmail.com ---
Arch upgrade Konsole to Version 16.12.0
This issue has been resolved.

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

[partitionmanager] [Bug 373796] Partition Manager uses different config when not launched from terminal emulator

[bugzilla_noreply]

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

--- Comment #4 from ras...@gmail.com ---
> I'm actually not sure what Arch does to make it use ~/.config/. Is it some 
> environmental variable?

I have no idea, hoping the package maintainer can figure it out. Here's a link:

https://bugs.archlinux.org/task/52204

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

[frameworks-kimageformats] [Bug 373838] Add support for android's VectorDrawable xml format

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Import  |general
 CC||caulier.gil...@gmail.com,
   ||kdelibs-b...@kde.org
Version|5.3.0   |unspecified
   Assignee|digikam-de...@kde.org   |alex.me...@kde.org
Product|digikam |frameworks-kimageformats

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

[digikam] [Bug 373876] digicam crash on start up

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
You mix Qt4 and Qt5 on your system :

Thread 1 (Thread 0x7f412a5b8880 (LWP 12593)):
[KCrash Handler]
#6  0x7f40eaaabed5 in QMetaObject::className() const () at
/usr/lib64/libQt5Core.so.5
#7  0x7f40ebc8215f in  () at /usr/lib64/libQt5Widgets.so.5

digiKam 4.14 is based on Qt4 only. Report this proble to your distro packagers.

I recommend to use digiKam universal Linux Bundle instead.

Gilles Caulier

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

[partitionmanager] [Bug 373796] Partition Manager uses different config when not launched from terminal emulator

[Andrius Štikonas]

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

--- Comment #3 from Andrius Štikonas  ---
Well, I wouldn't recommend running it manually (except for testing) with "sudo
partitionmanager" precisely because it can rerun itself using kdesu and pass
required environmental variables (sudo eats them).

As for the config file, we obviously want it to be consistent. So whichever way
is easier. But I guess /root/.config might be easier since this is how it works
in all other distros.

I'm actually not sure what Arch does to make it use ~/.config/. Is it some
environmental variable?

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

[digikam] [Bug 373876] New: digicam crash on start up

[Carl]

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

Bug ID: 373876
   Summary: digicam crash on start up
   Product: digikam
   Version: 4.14.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: admfu...@gmail.com
  Target Milestone: ---

Application: digikam (4.14.0)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Just starting digikam from the
kde menu. suse leap 42.1 
segmentation fault (11)

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f4101bba700 (LWP 12598)):
#0  0x7f412183303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4123b19066 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f4128d03c3a in  () at /usr/lib64/libdigikamcore.so.4.14.0
#3  0x7f4123b18b7f in  () at /usr/lib64/libQtCore.so.4
#4  0x7f412182f0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f4122fbc02d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f41023bb700 (LWP 12596)):
#0  0x7f411b462cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f411b420387 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f411b420d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f411b420f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4123c46f9e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f4123c18d0f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f4123c19005 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f4123b1649f in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f4123bfa613 in  () at /usr/lib64/libQtCore.so.4
#9  0x7f4123b18b7f in  () at /usr/lib64/libQtCore.so.4
#10 0x7f412182f0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f4122fbc02d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4102bbc700 (LWP 12595)):
#0  0x7f412183303f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4123b19066 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x005e460e in  ()
#3  0x7f4123b18b7f in  () at /usr/lib64/libQtCore.so.4
#4  0x7f412182f0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f4122fbc02d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f410dc96700 (LWP 12594)):
#0  0x7f4122fb3bfd in poll () at /lib64/libc.so.6
#1  0x7f410e3a7888 in  () at /usr/lib64/libusb-1.0.so.0
#2  0x7f412182f0a4 in start_thread () at /lib64/libpthread.so.0
#3  0x7f4122fbc02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f412a5b8880 (LWP 12593)):
[KCrash Handler]
#6  0x7f40eaaabed5 in QMetaObject::className() const () at
/usr/lib64/libQt5Core.so.5
#7  0x7f40ebc8215f in  () at /usr/lib64/libQt5Widgets.so.5
#8  0x7f412a4208ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x7f412a4209d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x7f412a424b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x7f412a4207a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x7f412a4242fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x7f4119e4802b in dlopen_doit () at /lib64/libdl.so.2
#14 0x7f412a4207a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x7f4119e485dd in _dlerror_run () at /lib64/libdl.so.2
#16 0x7f4119e480c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#17 0x7f40f1ae5b7f in  () at /usr/lib64/libvlccore.so.8
#18 0x7f40f1acb1db in  () at /usr/lib64/libvlccore.so.8
#19 0x7f40f1acb4bb in  () at /usr/lib64/libvlccore.so.8
#20 0x7f40f1acb404 in  () at /usr/lib64/libvlccore.so.8
#21 0x7f40f1acb969 in  () at /usr/lib64/libvlccore.so.8
#22 0x7f40f1acbea7 in  () at /usr/lib64/libvlccore.so.8
#23 0x7f40f1a52bcd in libvlc_InternalInit () at /usr/lib64/libvlccore.so.8
#24 0x7f40f18235e3 in libvlc_new () at /usr/lib64/libvlc.so.5
#25 0x7f40f1d6ffe9 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x7f40f1d54e18 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x7f40f1d5597b in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x7f4123bfe4d1 in QPluginLoader::instance() () at
/usr/lib64/libQtCore.so.4
#29 0x7f40f22b2f8b in  () at 

[partitionmanager] [Bug 373796] Partition Manager uses different config when not launched from terminal emulator

[bugzilla_noreply]

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

--- Comment #2 from ras...@gmail.com ---
I fixed the theme issue by copying kdeglobals from ~/.config to /root/.config.

Regarding partitionmanagerrc:

If I dont use sudo, it opens kdesu. On Arch, it uses
~/.config/partitionmanagerrc (owned by root). On Neon it uses
/root/.config/partitionmanagerrc. Either way it runs as root.

The Arch package maintainer and I would like confirmation on what the intended
behavior is. Is it always supposed to use root's config even if it's launched
from the terminal without sudo?

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

[plasmashell] [Bug 373875] New: Plasma crash when i close group of the windows or exact window by right-click on taskbar

[Sergey Mikhailov]

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

Bug ID: 373875
   Summary: Plasma crash when i close group of the windows or
exact window by right-click on taskbar
   Product: plasmashell
   Version: 5.8.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mikhailo...@soft-logic.ru
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.13-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
I have some windows opened, they are grouped into one button on the taskbar.
usually it is (Dolphin or Ark)
Every time when i try to close this windows by right-clicking a taskbar button
and choose "Close" plasma will almost always crash and re-start  taskbar and
widget panel 
plasma also sometimes crash in the same manner when taskbar button is not a
group, but exact single window/application. But this a rare case

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 0x7fcf46d87940 (LWP 1471))]

Thread 15 (Thread 0x7f8e573ed700 (LWP 30729)):
#0  0x7fcf557c4f62 in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7fcf557a71c2 in read () from /lib64/libc.so.6
#2  0x7fcf487b9b31 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-8.0.so
#3  0x7fcf49050d7e in pa_mainloop_prepare () from /lib64/libpulse.so.0
#4  0x7fcf490517f0 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#5  0x7fcf490518b0 in pa_mainloop_run () from /lib64/libpulse.so.0
#6  0x7fcf4905f8c9 in thread () from /lib64/libpulse.so.0
#7  0x7fcf487e718b in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-8.0.so
#8  0x7fcf54b075ca in start_thread () from /lib64/libpthread.so.0
#9  0x7fcf557b70ed in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7fce77fff700 (LWP 18534)):
#0  0x7fcf4905115a in pa_mainloop_poll () from /lib64/libpulse.so.0
#1  0x7fcf490517fe in pa_mainloop_iterate () from /lib64/libpulse.so.0
#2  0x7fcf490518b0 in pa_mainloop_run () from /lib64/libpulse.so.0
#3  0x7fcf4905f8c9 in thread () from /lib64/libpulse.so.0
#4  0x7fcf487e718b in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-8.0.so
#5  0x7fcf54b075ca in start_thread () from /lib64/libpthread.so.0
#6  0x7fcf557b70ed in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7fce6df37700 (LWP 2992)):
#0  0x7fcf54b0cbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcf563c403a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fce965638c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5
#3  0x7fce96567a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#4  0x7fce96562a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fce96567ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#6  0x7fce96562a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fce96565909 in ThreadWeaver::Thread::run() () from
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fcf563c39ba in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fcf54b075ca in start_thread () from /lib64/libpthread.so.0
#10 0x7fcf557b70ed in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7fce6e738700 (LWP 2991)):
#0  0x7fcf54b0cbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcf563c403a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fce965638c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5
#3  0x7fce96567a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#4  0x7fce96562a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fce96567ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#6  0x7fce96562a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from

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

[John Andersen]

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

John Andersen  changed:

   What|Removed |Added

 CC||jsam...@gmail.com

--- Comment #213 from John Andersen  ---
(In reply to Jonathan Marten from comment #212)

> Please don't comment on this bug report or bother the Plasma developers
> about this - it is unofficial and nothing to do with the Plasma project.

Sorry, but I just can't help posting a THANK YOU for this Jonathan. 
Very cool.  I've been waiting for over 2 years. 
Thank You.

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

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[Jack]

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

--- Comment #2 from Jack  ---
gpgme 1.8 is now thread safe, so it no longer provides libgpgme-pthread because
it is no longer necessary.  The problem is that many programs (kmymoney
included) need to be modified to not use libgpgme-pthread if gpgme is version
1.8 or above.  Creating that temporary symlink can be a short-term workaround,
but eventually, all programs that link to gpgme will need to be modified (or
perhaps have their build system modified) because of this.  (This applies to
both 4.8.x and git master.)

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

[user-manager] [Bug 373874] New: Cannot create new user

[John Salatas]

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

Bug ID: 373874
   Summary: Cannot create new user
   Product: user-manager
   Version: 5.8.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: jsala...@gmail.com
  Target Milestone: ---

It seems that adding a new user through "System Settings" -> "Account Details"
-> "New User" doesn't work: I fill in the new user's details and when I click
"Apply" it turns back to grey and nothing happens. 

Running system settings from a console, it gives the following output

> systemsettings5 
log_user_manager: 1000
log_user_manager: Checking password
log_user_manager: Verify password is empty
log_user_manager: Checking password
log_user_manager: Verify password is empty
log_user_manager: Checking password
log_user_manager: Quality:  31
log_user_manager: Saving on Index:  1 
> 


No sure when it first appeared. I just noticed it in KDE Neon user edition
having latest packages installed (as of December 18th).

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

[systemsettings] [Bug 373873] New: KDE plasma application style

[Armando]

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

Bug ID: 373873
   Summary: KDE plasma application style
   Product: systemsettings
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: zuk...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I lunc the application and after changing some settings and close it, it show
the error.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb9c82661c0 (LWP 2093))]

Thread 6 (Thread 0x7fb990fa9700 (LWP 2106)):
#0  0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6
#1  0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb9be34a89c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb9c488a2db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fb9c4833d3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fb9c3f707df in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7fb992fe6700 (LWP 2102)):
#0  0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6
#1  0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb9be34a89c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb9c488a2db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fb9c4833d3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fb9c3f707df in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7fb26700 (LWP 2100)):
#0  0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6
#1  0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb9be34a89c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb9c488a2db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fb9c4833d3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fb9c29a9e75 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb9c3f707df in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7fb9ac1c9700 (LWP 2096)):
#0  0x7fb9be38fdd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7fb9be34a8a6 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#2  0x7fb9c488a2db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#3  0x7fb9c4833d3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#4  0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#5  0x7fb9c519fde5 in ?? () from /usr/lib/libQt5DBus.so.5
#6  0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fb9c3f707df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fb9b4acd700 (LWP 2095)):
#0  0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6
#1  0x7fb9c08b88e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fb9c08ba679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fb9b6c1f789 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fb9c3f707df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fb9c82661c0 (LWP 2093)):
[KCrash Handler]
#6  0x7fb9c287acc0 in QV4::PersistentValueStorage::freePage(void*) () from
/usr/lib/libQt5Qml.so.5
#7  0x7fb9c287b3a2 in QV4::WeakValue::free() () from
/usr/lib/libQt5Qml.so.5
#8  0x7fb9c28ebe42 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/libQt5Qml.so.5
#9  0x7fb9c278263f in QV4::MemoryManager::sweep(bool) () from
/usr/lib/libQt5Qml.so.5
#10 0x7fb9c2783a4c in QV4::MemoryManager::~MemoryManager() () from

[kwin] [Bug 373872] New: error kde virtualbox

[Rodrigo Lopez]

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

Bug ID: 373872
   Summary: error kde virtualbox
   Product: kwin
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rodlinux...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.38-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

Estaba usando virtualbox cuando mando un error, de hecho estaba configurando
una maquina virtual
Esperemos que la informacion les sirva

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd4efbc2840 (LWP 977))]

Thread 5 (Thread 0x7fd4bf7ff700 (LWP 1628)):
#0  0x7fd4eccb0345 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#1  0x7fd4ecc5d24a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#3  0x7fd4e75f62d5 in  () at /usr/lib/libQt5Qml.so.5
#4  0x7fd4eca84d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fd4b7fff700 (LWP 1128)):
#0  0x7fd4e889e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd4ebbf4ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fd4ebbf4b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fd4cca73700 (LWP 1123)):
#0  0x7fd4ef601551 in ppoll () at /usr/lib/libc.so.6
#1  0x7fd4eccaead9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7fd4eccb03c8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fd4ecc5d24a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fd4e75f62d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7fd4eca84d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fd4cf19b700 (LWP 1041)):
#0  0x7fd4ef601551 in ppoll () at /usr/lib/libc.so.6
#1  0x7fd4eccaead9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7fd4eccb03c8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fd4ecc5d24a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fd4e67c0e55 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7fd4eca84d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fd4efbc2840 (LWP 977)):
[KCrash Handler]
#6  0x8028 in  ()
#7  0x7fd4ecc90d00 in QObject::connect(QObject const*, char const*, QObject
const*, char const*, Qt::ConnectionType) () at /usr/lib/libQt5Core.so.5
#8  0x7fd4ebc36f6f in  () at /usr/lib/libQt5Script.so.5
#9  0x7fd4ebc37034 in  () at /usr/lib/libQt5Script.so.5
#10 0x7fd4ebc372b2 in QScriptEngine::newQObject(QObject*,
QScriptEngine::ValueOwnership, QFlags const&)
() at /usr/lib/libQt5Script.so.5
#11 0x7fd4ef20b97c in  () at /usr/lib/libkwin.so.5
#12 0x7fd4ebc37565 in  () at /usr/lib/libQt5Script.so.5
#13 0x7fd4ebc5ffb6 in  () at /usr/lib/libQt5Script.so.5
#14 0x7fd4ebc68281 in  () at /usr/lib/libQt5Script.so.5
#15 0x7fd4ecc8a804 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#16 0x7fd4ec43ffc8 in
KWin::EffectsHandler::desktopPresenceChanged(KWin::EffectWindow*, int, int) ()
at /usr/lib/libkwineffects.so.9
#17 0x7fd4ec441981 in  () at /usr/lib/libkwineffects.so.9
#18 0x7fd4ecc8b4c9 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#19 0x7fd4ed93ee0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#20 0x7fd4ed946581 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#21 0x7fd4ecc5edf0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7fd4ecc6157d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#23 0x7fd4eccb020a in

[plasmashell] [Bug 373738] Panel is unable to receive focus after opening Youtube video on Firefox

[fragabr]

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

frag...@gmail.com  changed:

   What|Removed |Added

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

--- Comment #6 from frag...@gmail.com  ---
(In reply to Eike Hein from comment #3)
> My guess is the plasmashell process takes 100% CPU and becomes unresponsive.

Eike, good news! Problem solved. After struggling for a week with this issue,
the problem was with the xf86-video-intel driver. Since it defaults to DRI2, I
simply enabled DRI3 (--enable-dri3) and added on my xorg.conf:

Option "DRI" "3"

This results on the following:

[56.746] (**) intel(0): Option "DRI" "3"
[56.902] (II) intel(0): [DRI2] Setup complete
[56.902] (II) intel(0): [DRI2]   DRI driver: i965
[56.902] (II) intel(0): [DRI2]   VDPAU driver: va_gl
[56.902] (II) intel(0): direct rendering: DRI2 DRI3 enabled
[57.862] (II) GLX: Initialized DRI2 GL provider for screen 0

There's only 1 line which mentions DRI3 and I read somewhere the Intel driver
doesn't use DRI3 at all. Well, I'm using the latest git version
2.99.917-746-g169c74fa and it indeed does solve the issue (or maybe this is an
indirect consequence?). I don't know.

So I'll mark this bug as WORKSFORME. Maybe it helps someone using the same
setup.

Ps: and I tested it with UXA and SNA. The only way to solve it is enabling
DRI3.

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

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[John Salatas]

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

John Salatas  changed:

   What|Removed |Added

 CC||jsala...@gmail.com

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

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[Michael Tunnell]

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

Michael Tunnell  changed:

   What|Removed |Added

 CC||m...@michaeltunnell.com

--- Comment #1 from Michael Tunnell  ---
I had the same issue with missing libgpgme-pthread.so.11 but inside of
Rhythmbox rather that KMyMoney. I've also seen reports of other applications
being affected by this issue so I think it is a larger problem than just
KMyMoney.

The solution I used to temporarily solve this problem was to create a symlink
of "libgpgme-pthread.so.11" to "libgpgme.so.11" inside of
"/usr/lib/x86_64-linux-gnu/".

Forum Thread discussing this topic, this thread contains the symlink
workaround. https://forum.kde.org/viewtopic.php?f=309=137494

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

[digikam] [Bug 373605] Failed to update database schema from version 7 to version 8

[Kusi]

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

--- Comment #5 from Kusi  ---
Created attachment 102868
  --> https://bugs.kde.org/attachment.cgi?id=102868=edit
sql script to detect FK violations

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[rosas]

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

rosas <07690120...@gmail.com> changed:

   What|Removed |Added

 CC||07690120...@gmail.com

--- Comment #40 from rosas <07690120...@gmail.com> ---
They say it'll help if I install an older version of my Ugee 1910b driver,
but...
Does anyone know where I can download an older driver? Or maybe one of you have
one that you can send me through Gmail?

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

[calligrasheets] [Bug 373743] Inserting columns crash

[David Ferrone]

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

--- Comment #1 from David Ferrone  ---
I thought I should attempt to provide a few more details. Oddly this occurs in
a very specific way.

I have an .ods file with 30 students scores (10 quizzes, 3 exams, etc.)

When I click on B (the second column header) and insert a column there, it
inserts with no issue.  When I repeat this step, to insert a second column in
that same location, Calligra Sheets crashes.

This happens with another .ods file as well. I can cause this crash every time. 

But this crash ONLY occurs when I insert a column IN THE SECOND COLUMN. (and
again, only the second time I do this. First insert is fine. Second insert
causes a crash.)

I can insert as many columns as I want in column A, or column C, or seemingly
any other column.  But B causes trouble on the second insert. Weird!

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

[kwin] [Bug 373798] Super (Windows) Key does not open the menu after suspend.

[silentz0r]

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

silentz0r  changed:

   What|Removed |Added

Version|unspecified |5.8.4

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

[krita] [Bug 373869] Unable to move docker

[Jade]

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

--- Comment #1 from Jade  ---
Unable to upload the video due to size.

https://www.dropbox.com/s/9a4an119k2o29vv/2016-12-18-1658-38.flv

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

[krita] [Bug 373869] New: Unable to move docker

[Jade]

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

Bug ID: 373869
   Summary: Unable to move docker
   Product: krita
   Version: 3.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: jadegod...@gmail.com
  Target Milestone: ---

Windows 10 running 3.1.1. 

When I click and drag a docked window, I'm unable to move it to any location.
I'm not seeing any errors or signs I shouldn't be able to move it, the screen
adjusts and the area on the side bars highlight as I would expect. But when I
hover over the new location, it will snap back to its original position.

I'm unable to move from left, right, top, bottom, or even re-order windows.

I've attached a video that shows my actions. Out of every attempt I made, it
only worked once, and then I couldn't move that successful dock back to its
original location.

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

[krunner] [Bug 373868] New: krunner and plasma crash when switching away from openSUSE Leap with KVM

[Adam Reed]

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

Bug ID: 373868
   Summary: krunner and plasma crash when switching away from
openSUSE Leap with KVM
   Product: krunner
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: adamr...@alum.mit.edu
  Target Milestone: ---

Application: krunner (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Switching from the openSUSE Leap computer to Mac Mini with Iogear Miniview DVI
2 port USB KVMP switch.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f749ac827c0 (LWP 2267))]

Thread 4 (Thread 0x7f747288b700 (LWP 2300)):
#0  0x7f7493e41d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7493dff4a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7493dffd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7493dfff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7497230d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f74971d7d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f7496ff961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f74998fbe18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f7496ffe32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f749499a0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f749690c02d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f747870b700 (LWP 2280)):
#0  0x7f749499e03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f747f161a73 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f747f1611f7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f749499a0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f749690c02d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7485911700 (LWP 2268)):
#0  0x7f7496903bfd in poll () at /lib64/libc.so.6
#1  0x7f7495e0c422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f7495e0e00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f7487a623c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7496ffe32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f749499a0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f749690c02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f749ac827c0 (LWP 2267)):
[KCrash Handler]
#6  0x7f749685c0c7 in raise () at /lib64/libc.so.6
#7  0x7f749685d478 in abort () at /lib64/libc.so.6
#8  0x7f7496899784 in  () at /lib64/libc.so.6
#9  0x7f749689f026 in malloc_printerr () at /lib64/libc.so.6
#10 0x7f749689fd53 in _int_free () at /lib64/libc.so.6
#11 0x7f748781c3f1 in XIQueryDevice () at /usr/lib64/libXi.so.6
#12 0x7f7487a83d74 in QXcbConnection::touchDeviceForId(int) () at
/usr/lib64/libQt5XcbQpa.so.5
#13 0x7f7487a854ed in QXcbConnection::xi2SetupDevices() () at
/usr/lib64/libQt5XcbQpa.so.5
#14 0x7f7487a85ba0 in QXcbConnection::xi2HandleHierachyEvent(void*) () at
/usr/lib64/libQt5XcbQpa.so.5
#15 0x7f7487a8793b in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () at
/usr/lib64/libQt5XcbQpa.so.5
#16 0x7f7487a6034d in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() at /usr/lib64/libQt5XcbQpa.so.5
#17 0x7f7487a6201b in QXcbConnection::processXcbEvents() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f749720aac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f749814ae7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#20 0x7f749814fcc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#21 0x7f74971d9e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#22 0x7f74971dc057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#23 0x7f74972318f3 in  () at /usr/lib64/libQt5Core.so.5
#24 0x7f7493dffc84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f7493dffed8 in  () at /usr/lib64/libglib-2.0.so.0
#26 0x7f7493dfff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#27 0x7f7497230d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#28 0x7f74971d7d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#29 0x7f74971df8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#30 0x00408c68 in main ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You 

[ksudoku] [Bug 373840] In game "killer sudoku" there are multiple solutions

[Ian Wadham]

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

Ian Wadham  changed:

   What|Removed |Added

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

--- Comment #1 from Ian Wadham  ---
In Killer Sudoku all the rules for Classic Sudoku apply, plus the numbers in
each cage must add up to the cage's total.

In the example you attached, you can apply the rule that the 3x3 boxes of a
Classic Sudoku must each contain the digits 1 to 9.

The number in column 1, row 3 must be a 4, not a 7, because there is already a
7 in the top-left 3x3 box. The number in column 1, row 4 must be a 7, not a 4,
because there is already a 4 in its 3x3 box... etc.

I am sorry the 3x3 boxes are not clearly marked in the Killer Sudoku.  I could
not find an easy way of doing that which would work with all themes on all
platforms and not look messy.  You must just imagine they are there.

Hint: Often a 3x3 box will be filled with cages, except for one cell. You can
then deduce that cell's number early in the game by subtracting the cage-totals
from 45 (the sum of the digits 1 to 9). Similarly, if a 3x3 box is covered by
cages and has one cell sticking out, you an subtract 45 from the total of the
cages.

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

[krita] [Bug 373867] New: Krita Crahes when saving as anything other than .Kra

[eli haun]

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

Bug ID: 373867
   Summary: Krita Crahes when saving as anything other than .Kra
   Product: krita
   Version: 3.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: eli.h...@yahoo.com
  Target Milestone: ---

I can only save in .kra.  No other file format will save, and instead the
program crashes. I have tried saving in Tiff, PSD, ORA, and PDF.  I NEED the
layers to be saved (so no png or jpeg), and the only format that will not crash
is .kra, and kra won't load in photoshop

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

[konqueror] [Bug 373866] konqueror directory 'F9' and normal shortcuts gone in frameworks 5

[David Rankin]

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

David Rankin  changed:

   What|Removed |Added

 Attachment #102865|0   |1
is obsolete||

--- Comment #1 from David Rankin  ---
Created attachment 102867
  --> https://bugs.kde.org/attachment.cgi?id=102867=edit
attachment 1 - showing drag where single-click should place focus for focus
follows mouse users

replacement for original snapshot which omitted the mouse cursor. The mouse
cursor shows where a single-click should provide the focus for the file/folder
without having to do a 2-pixel drag.

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

[kwin] [Bug 373851] Plastik decoration sometimes shows black button icons

[Martin Koller]

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

--- Comment #2 from Martin Koller  ---
Created attachment 102866
  --> https://bugs.kde.org/attachment.cgi?id=102866=edit
kwin support info

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

[konqueror] [Bug 373866] New: konqueror directory 'F9' and normal shortcuts gone in frameworks 5

[David Rankin]

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

Bug ID: 373866
   Summary: konqueror directory 'F9' and normal shortcuts gone in
frameworks 5
   Product: konqueror
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

Created attachment 102865
  --> https://bugs.kde.org/attachment.cgi?id=102865=edit
attachment 1 - showing drag where single-click should place focus for focus
follows mouse users

Version 5.0.97

Pressing 'F9' in konqueror no longer open the home, root, services, system,
media left side view pane. The best you can do is a kludgy side-by-side view,
but THANK YOU FOR FIXING katepart preview in advanced text editor!! We now how
preview with SYNTAX HIGHLIGHTING working again!!

The focus model is still all screwed up for users of 'single-click' focus
follows mouse, and there is no way to click to the right of the filename to
provide focus to the file or folder (and it is totally bewildering why dragging
over 2-pixels provides the focus just fine, but for reasons unexplained the
konquer dev has been unable to provide that same functionality with a click in
the same area...) See attachment 1 for an example of a 2-px drag doing what a
single-click should.

The jury is still out on whether this will provide the replacement konqueror
for power-users we were promised when kde4 gave us the dumbed-down dolphin, but
this looks like a step in the right direction. Thanks for fixing katepart
preview, and I'll work with this and provide additional requests as warranted.

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

[kwin] [Bug 373851] Plastik decoration sometimes shows black button icons

[Martin Gräßlin]

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

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

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

[kwin] [Bug 373798] Super (Windows) Key does not open the menu after suspend.

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
OK. So on Linux super and meta key are the same thing. That confused me.

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

[frameworks-plasma] [Bug 373771] Log spam on WindowThumbnail unredirect

[Martin Gräßlin]

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

--- Comment #4 from Martin Gräßlin  ---
Yeah quite easy. KWin does so in events.cpp for example.

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

[krita] [Bug 373846] [brush-editor] "+Stamp" button is broken

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from mvowada  ---
(Krita 3.1.1 appimage btw, on Ubuntu 14.04). Confirming.

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

[krita] [Bug 373846] [brush-editor] "+Stamp" button is broken

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
Hi David, I can reproduce what you described in Krita 3.1.1 too.
(The '+Stamp' button doesn't take the selected area on canvas while the
'Clipboard' workaround, well, it works).

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

[krita] [Bug 373859] Can't delete instrumet tags

[mvowada]

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

--- Comment #2 from mvowada  ---
(At the end it says: "Note  The default brushes that come with Krita cannot
have their default tags removed. ")

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

[plasmashell] [Bug 373865] New: plasmashell crashes on usb disconnect

[Thomas Mitterfellner]

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

Bug ID: 373865
   Summary: plasmashell crashes on usb disconnect
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tho...@mitterfellner.at
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I have a dual monitor setup where the external monitor is connected to the
laptop and has an usb hub to which mouse and keyboard are connected. When I
disconnect that hub from the laptop, sometimes I get this crash. The laptop
screen is turned off, if that matters; I'm writing this because I also had
other crashes in connection with the monitor (kwin crashed twice, also not 100%
reproducible) when I turned the monitor off (with gwenview in fullscreen mode).

The crash can be reproduced sometimes.

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

Thread 11 (Thread 0x7fd9a70f0700 (LWP 16808)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x26e9070) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x272e720, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x272e6a0) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fd9adc1f700 (LWP 16807)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x24cf820) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x24cf2b0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x24cf230) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fd9af011700 (LWP 16802)):
#0  0x7fda7e91cbfd in poll () at /lib64/libc.so.6
#1  0x7fda799f8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fda799f8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fda7f2229eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd9a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fda7f1d22db in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd9af010dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7fda7f017fca in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7fd9b0439cf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x23d79a0) at
thread/qthread_unix.cpp:368
#8  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fd9c60d7700 (LWP 16783)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x1258fc0) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0xd86b10, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0xd86a90) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fd9c6ff7700 (LWP 16782)):
#0  0x7fda7e91cbfd in poll () at /lib64/libc.so.6
#1  0x7fda799f8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fda799f8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  

[krita] [Bug 373859] Can't delete instrumet tags

[mvowada]

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from mvowada  ---
Hi Denis,
I guess those come by default and I think they can't be deleted by users:
https://docs.krita.org/Tag_System

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

[kdeconnect] [Bug 373775] Run command fails whenever the command includes any special character

[bugzilla_noreply]

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

--- Comment #3 from llamal...@maillama.com ---
*sigh* Understood and will do.

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

[kmailtransport] [Bug 373833] Kmail 16.12 fails to send emails

[avlas]

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

--- Comment #2 from avlas  ---
This issue and https://bugs.kde.org/show_bug.cgi?id=373832 might be packaging
issues (?). 

At least this issue can be somehow workarounded now after some combination of:

- manually stopping the Akonadi server
- reinstalling the Akonadi agent in charge of sending emails
- restarting Kontact

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

[knotes] [Bug 373864] New: Knotes color scheme buggy after upgrade to 16.10

[Hamid]

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

Bug ID: 373864
   Summary: Knotes color scheme buggy after upgrade to 16.10
   Product: knotes
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: accessibility, usability
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: hamidrjaf...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

Created attachment 102864
  --> https://bugs.kde.org/attachment.cgi?id=102864=edit
Desktop shows Knotes previous notes and new notes after upgrade rendered
differently

Hello!

After upgrade to 16.10 knotes widget on the panel opens notes in all black that
is foreground and background set to black with red wavy underlines showing
typos. The application run from command line ($knotes &) and making new notes
works Ok but accessing previous notes from the panel widget shows small windows
and black over black. Check the image. I have opened all notes plus added new
notes which are correct.

(Synaptic) Installed version: 4:16.04.3-0ubuntu2
$ knotes -v
knotes 5.2.3

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

[kmail2] [Bug 373832] Kmail 16.12 crashes due to overdue time to lock

[avlas]

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

--- Comment #2 from avlas  ---
I tried to reproduce the issue Today and couldn't (I upgraded from 16.08.3 to
16.12 again). So it might be a packaging issue that got somehow fixed, perhaps?
I'll keep version 16.12 and I will upload here the output from the terminal if
the issue reappears at some point...

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

[okular] [Bug 373863] New: Regression Okular 1.0.0 (KDE Applications 16.12.0): Always prints duplex even if told not to.

[Gunter Ohrner]

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

Bug ID: 373863
   Summary: Regression Okular 1.0.0 (KDE Applications 16.12.0):
Always prints duplex even if told not to.
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

I just upgraded Okular from the Applications 16.08.x version to the version
from Applications 16.12.0.

If I try to print a single-page PDF non-duplex, Okular still activates duplex
printing, rotates the paper and prints on the backside. ("Duplex: none" is
chosen in the print dialog.)

This worked fine before and now gives me a big headache with my paper with
pre-printed letterheads... :-/

My printer is a Brother DCP-7065DN, duplex printing works fine from the command
line and in all other applications I tested (like Chromium, LibreOffice, Adobe
Reader and previous Okular versions).

Maybe related to #373133, which basically is a report of the opposite problem?
In any case, this looks like as if there is definitely something messed up
concerning duplex-printing in the new Okular release...

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

[frameworks-solid] [Bug 373862] Solid::Backends::UDev::input_str_to_bitmask can't handle some bits

[bugzilla_noreply]

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

clickwir...@gmail.com changed:

   What|Removed |Added

Version|unspecified |5.26.0

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

[frameworks-solid] [Bug 373862] New: Solid::Backends::UDev::input_str_to_bitmask can't handle some bits

[bugzilla_noreply]

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

Bug ID: 373862
   Summary: Solid::Backends::UDev::input_str_to_bitmask can't
handle some bits
   Product: frameworks-solid
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: clickwir...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Turned on monitor today, notices strange artifacts at the unlock screen.
Unlocked and all other windows appear to have artifacts and trouble displaying
text and images. Sometimes it's fine and everything is great, maybe the next
tab in Firefox has lots of artifacts and the next has none. Konsole, chromium,
kcalc and the desktop itself all showed some display corruption of some sort.

I was going to reboot, when I noticed the following in a konsole window I had
left open for a few days. I hadn't used the konsole window in over 24 hours and
no hardware has changed in that time.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

sudo apt-cache showpkg kdebase-apps 
Package: kdebase-apps
Versions: 
4:16.04.3-0ubuntu1

KDE Framework: 5.26.0
Qt 5.6.1 (built against 5.6.1)


Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f",
"0", "0", "0", "0", "483", "17aff32d", "bf56", "0", "0", "1", "130c13",
"b17c007", "ffbf7bfa", "d941dfff", "febeffdf", "ffef", "",
"fffe") 
Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f",
"0", "0", "0", "0", "483", "17aff32d", "bf56", "0", "0", "1", "130c13",
"b17c007", "ffbf7bfa", "d941dfff", "febeffdf", "ffef", "",
"fffe") 
Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f",
"0", "0", "0", "0", "483", "17aff32d", "bf56", "0", "0", "1", "130c13",
"b17c007", "ffbf7bfa", "d941dfff", "febeffdf", "ffef", "",
"fffe") 
Solid::Backends::UDev::input_str_to_bitmask can't handle some bits ("3007f",
"0", "0", "0", "0", "483", "17aff32d", "bf56", "0", "0", "1", "130c13",
"b17c007", "ffbf7bfa", "d941dfff", "febeffdf", "ffef", "",
"fffe")

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

[dolphin] [Bug 373861] non disruptive dialog

[Timothy Danielson]

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

Timothy Danielson  changed:

   What|Removed |Added

   Platform|Other   |Debian stable

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

[dolphin] [Bug 373861] New: non disruptive dialog

[Timothy Danielson]

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

Bug ID: 373861
   Summary: non disruptive dialog
   Product: dolphin
   Version: 4.14.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: timothydaniel...@yahoo.com
  Target Milestone: ---

This is a first time occurance and I know nothing of the bug. I hope the bug
report can send something useful.

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

[plasmashell] [Bug 373860] New: Plasmoids cannot be placed at the screen edge

[Alexander Schier]

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

Bug ID: 373860
   Summary: Plasmoids cannot be placed at the screen edge
   Product: plasmashell
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: a...@laxu.de
  Target Milestone: 1.0

When placing a plasmoid on the desktop at a screen edge (i.e. bottom of
plasmoid to the bottom of the screen), it slides up a bit. When i move the
plasmoid on the screen back to to bottom, it slides up again. With plasma4, it
worked to place it directly on the edge.

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

[print-manager] [Bug 341429] duplex is wrongly greyed out and with wrong default selected

[Gunter Ohrner]

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

Gunter Ohrner  changed:

   What|Removed |Added

 CC||kdeb...@customcdrom.de

--- Comment #1 from Gunter Ohrner  ---
Duplicate of #311656?

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

[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.

[Axel Braun]

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

--- Comment #20 from Axel Braun  ---
Correction - happens as well after s2ram

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

[krita] [Bug 373859] New: Can't delete instrumet tags

[Denis]

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

Bug ID: 373859
   Summary: Can't delete instrumet tags
   Product: krita
   Version: 3.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: otziga...@yandex.ru
  Target Milestone: ---

"demo"
"ink"
"paint"
"sketch"

I can't delete this tags. After reload krita it's back.

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

[plasmashell] [Bug 373858] New: Plasma crash during normal work with external monitor connected

[Raf]

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

Bug ID: 373858
   Summary: Plasma crash during normal work with external monitor
connected
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raf...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Plasma crash occured duing normal work on dekstop. My laptop was connected to
external monitor via Display Port.

The crash can be reproduced sometimes.

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

Thread 16 (Thread 0x7f74797fa700 (LWP 4051)):
#0  0x7f75531e203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f75540d034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f74971c865f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f74971cc43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f74971ca005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f75540cf32f in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f75531de0a4 in start_thread () at /lib64/libpthread.so.0
#18 0x7f75539dd02d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f7479ffb700 (LWP 4050)):
#0  0x7f75531e203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f75540d034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f74971c865f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f74971cc43a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f74971cc481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f74971c66cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f74971ca005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f75540cf32f in  () at /usr/lib64/libQt5Core.so.5
#15 0x7f75531de0a4 in start_thread () at /lib64/libpthread.so.0
#16 0x7f75539dd02d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f747a7fc700 (LWP 4049)):
#0  0x7f75531e203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f75540d034b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f74971c865f in

[krita] [Bug 373853] New: Crash when using instant preview proly related to autosave due cloning.(gdb backtrace)

[wolthera]

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

Bug ID: 373853
   Summary: Crash when using instant preview proly related to
autosave due cloning.(gdb backtrace)
   Product: krita
   Version: 3.1 Beta
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Instant Preview
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

Got a crash when using instant preview on a 16bit float image. I suspect that
instant preview was calculating and something went awry with cloning for the
autosave. Haven't tried reproducing yet.

Backtrace:

ASSERT (krita): "!rhs.m_d->projectionUpdatesFilter" in file
/home/krita/kde/src/krita/libs/image/kis_image.cc, line 321

Thread 1 "krita" received signal SIGABRT, Aborted.
0x74b7e428 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) thread apply backtrace all
Invalid thread ID: backtrace all
(gdb) thread apply all backtrace

Thread 6751 (Thread 0x7fff6fdf9700 (LWP 19291)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75554738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75550467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75553c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeea6170a in start_thread (arg=0x7fff6fdf9700)
at pthread_create.c:333
#5  0x74c4f82d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6750 (Thread 0x7fff799fe700 (LWP 19290)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75554738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75550467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75553c89 in ?? ()
---Type  to continue, or q  to quit---
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeea6170a in start_thread (arg=0x7fff799fe700)
at pthread_create.c:333
#5  0x74c4f82d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6749 (Thread 0x7fff705fa700 (LWP 19289)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75554738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75550467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75553c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeea6170a in start_thread (arg=0x7fff705fa700)
at pthread_create.c:333
#5  0x74c4f82d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6748 (Thread 0x7fff6b83e700 (LWP 19288)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
---Type  to continue, or q  to quit---
#1  0x75554738 in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75550467 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75553c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeea6170a in start_thread (arg=0x7fff6b83e700)
at pthread_create.c:333
#5  0x74c4f82d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fff99386700 (LWP 31628)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755547eb in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7672aaa2 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5
#3  0x75553c89 in ?? ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeea6170a in start_thread (arg=0x7fff99386700)
at pthread_create.c:333
#5  0x74c4f82d in clone ()
---Type  to continue, or q  to quit---
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fff99b87700 (LWP 31627)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755547eb in QWaitCondition::wait(QMutex*, unsigned long) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7554e116 in QSemaphore::tryAcquire(int, int) ()
   from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5

#3  0x72c32033 in KisTileDataSwapper::waitForWork (
this=)
at

[choqok] [Bug 373857] Choqok 1.6 ignores special application/window settings

[Wulf]

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

--- Comment #2 from Wulf  ---
addition2 (sorry):
If I close to tray and reopen the window, the window position is right

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

[telepathy] [Bug 373849] Re-entering a chat room does not show your own content

[Ken Koster]

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

--- Comment #1 from Ken Koster  ---
I forgot to add that this is while using XMPP in a conference session and that
time stamps are also ignored and all show as the time the session is open.

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

[choqok] [Bug 373857] Choqok 1.6 ignores special application/window settings

[Wulf]

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

--- Comment #1 from Wulf  ---
addition: I always start with a clear session

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

[KSystemLog] [Bug 304310] 'More information...' link does not work

[Burkhard Lueck]

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

--- Comment #3 from Burkhard Lueck  ---
./src/modes/cron/cronConfigurationWidget.h-55-"These files will
be analyzed to show the Cron Logs (i.e. planned tasks logs). More information...");

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

[choqok] [Bug 373857] New: Choqok 1.6 ignores special application/window settings

[Wulf]

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

Bug ID: 373857
   Summary: Choqok 1.6 ignores special application/window settings
   Product: choqok
   Version: 1.6
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mehrdad.mom...@gmail.com
  Reporter: wulf.richa...@gmx.de
CC: scarp...@kde.org
  Target Milestone: ---

After Update to Framework 5.29 and KDE 16.12 with Choqok 1.6 Choqok ignores
special application/window settings.
My special application windows settings:
- Apply initially
- Position: 1250,70
- Size: 375,950

Monitor resolution: 1680x1050

If I choose to enforce the window settings choqok respects the horizontal
value, but not the vertical - weird

change of ~/.config/choqokrc did not help

I did not have this problem before the update.

It seems, it's only choqok, I tested also kcalc and okular, they have no
problems to respect the special windows settings.

I tested with a brand new user: Same issue

I do not have different activities.

My startup window position for all windows is "centered"

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

[kinfocenter] [Bug 373856] New: KInfoCenter doesn't report core profile version for OpenGL

[Shmerl]

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

Bug ID: 373856
   Summary: KInfoCenter doesn't report core profile version for
OpenGL
   Product: kinfocenter
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL
  Assignee: hubn...@gmail.com
  Reporter: shm...@mykolab.com
  Target Milestone: ---

Currently, KIinfoCenter reports OpenGL version as compatibility profile only,
which is basically what's not supposed to be used by any normal application.
I.e. it's more relevant to show core profile. When reporting single version
like that, report core profile, or you can report both (core and
compatibility). That would make more sense.

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

[frameworks-syntax-highlighting] [Bug 373713] [PATCH] JavaScript Syntax Highlighting broken when using E4X

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

  Component|syntax  |general
Summary|JavaScript Syntax   |[PATCH] JavaScript Syntax
   |Highlighting broken when|Highlighting broken when
   |using E4X   |using E4X
Product|kate|frameworks-syntax-highlight
   ||ing

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

[plasmashell] [Bug 373761] Task Manager crashes leading to no plasma at all

[Lapineige]

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

Lapineige  changed:

   What|Removed |Added

 CC||lp.com...@lavache.com

--- Comment #4 from Lapineige  ---
I have this bug too, using the backports on Kubuntu 16.10.
I have it since the update to Plasma 5.7.5.
Plasmashell crash if I have a Task manager widget anywhere on the
desktop/panel. Without it, everything is working smoothly.

I have no "report bug" windows shown.

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

[okular] [Bug 373855] New: Forward search/named_destination feature not working anymore

[bugzilla_noreply]

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

Bug ID: 373855
   Summary: Forward search/named_destination feature not working
anymore
   Product: okular
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: peter.dieter...@gmx.de
  Target Milestone: ---

Created attachment 102863
  --> https://bugs.kde.org/attachment.cgi?id=102863=edit
PDF file containing some anchors for verification

Since okular (>=0.99.80) the forward search or 'named_destination' feature in
okular seems to be broken.
When trying to open a pdf at a named destination, e.g., through emacs and
synctex, I get the following output in stdout:

$ okular mypdf.pdf#page.3
org.kde.kcoreaddons: doesn't know ".../mypdf/mypdf.pdf#page.3"
org.kde.kcoreaddons: doesn't know ".../mypdf"

and I get the error "Could not open file:///[..]/mypdf.pdf%23page.3".

The same command works with okular 0.26.1.

I suspect that something was changed in how okular processes its command line
arguments: In the error message '#' got replaced with the HTML code %23.

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

[umbrello] [Bug 373854] New: My solution: umbrello there was a problem saving, in Ubuntu 16.04

[Matias W . Vera]

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

Bug ID: 373854
   Summary: My solution: umbrello there was a problem saving, in
Ubuntu 16.04
   Product: umbrello
   Version: 2.18.3 (KDE Applications 15.12.3)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: matiaswv...@gmail.com
  Target Milestone: ---

I solved it this way.

sudo apt-get install kinit
sudo apt-get install kio

and the error disappeared.

Bye.
Matias W. Vera

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

[okular] [Bug 373745] Page number textfield resizing do not work properly

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

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

--- Comment #1 from Oliver Sander  ---
I remember seeing this as well, but it was fixed eventually (I don't remember
when exactly).  Can you try a newer version of Okular?

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

[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small

[Alejandro Villar]

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

Alejandro Villar  changed:

   What|Removed |Added

 CC||alx5...@alx5000.net

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

[kmail2] [Bug 373852] New: Unread email counter in system tray not available

[Matthijs]

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

Bug ID: 373852
   Summary: Unread email counter in system tray not available
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: mtijink.b...@gmail.com
  Target Milestone: ---

Since updating to KMail 5.4, the option to show the number of unread emails in
the system tray is not available anymore.

Could you re-enable this?

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

[kwin] [Bug 373851] New: Plastik decoration sometimes shows black button icons

[Martin Koller]

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

Bug ID: 373851
   Summary: Plastik decoration sometimes shows black button icons
   Product: kwin
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kol...@aon.at
  Target Milestone: ---

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

I just upgraded openSuse 13.2 -> leap 42.2 and start to use plasma5
What I found is that sometimes in my konsole window the buttons in the
window title bar just get black and stay this way, regardless if the window is
active or inactive, whether I resize, minimze, restore the konsole window.

See attached screenshot. The top right area is from the konsole window, the
normally displayed buttons are from the konqueror window

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

[Breeze] [Bug 373667] Missing bottom border of Cancel button on Logout screen using Liberation fonts

[bugzilla_noreply]

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

pjsingh5...@gmail.com changed:

   What|Removed |Added

Product|neon|Breeze
Version|unspecified |5.8.4
  Component|Packages User Edition   |general

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

[kdev-python] [Bug 373850] New: Highlighting ranges often wrong for constructors/__call__()/indexing.

[Francis Herne]

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

Bug ID: 373850
   Summary: Highlighting ranges often wrong for
constructors/__call__()/indexing.
   Product: kdev-python
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@flherne.uk
  Target Milestone: ---

In these cases, the magic-method's name doesn't appear in the code, so we
highlight the opening paren or square-bracket.
```
mc = MyClass()  # <- `(` links to MyClass.__init__
mc[2] # <- `[` links to MyClass.__getitem__
```

In some cases, completely the wrong character is highlighted:
```
 class MyClass:
def __call__(self):
return 12
def __getitem__(self, key):
return 1.2

foo = {}
foo['aaa'] = MyClass()

bar = foo['aaa'][2] # First 'a' is highlighted instead of second '['
baz = foo['aaa'](2) # ')' is highlighted instead of '('
# Not sure why these behave differently
```

This seems particularly common after string literals.

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

[telepathy] [Bug 373849] New: Re-entering a chat room does not show your own content

[Ken Koster]

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

Bug ID: 373849
   Summary: Re-entering a chat room  does not show your own
content
   Product: telepathy
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: text-ui
  Assignee: kde-telepathy-b...@kde.org
  Reporter: n7...@wetnet.net
  Target Milestone: Future

When entering a chat room where you've had a previous conversation I expect to
see my own comments interleaved in the discussion.  Instead the only text shown
is content from the other users.   My own content is completely missing.

Other clients (Pidgin, Psi+) display the chat room contents correctly but I'd
really rather use the integrated telepathy code.

ktp-text-ui has never shown this correctly.

My current version is: 
Version 16.08.3
Using:
KDE Frameworks 5.28.0
Qt 5.7.0 (built against 5.7.0)

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

[digikam] [Bug 286373] DNG don't get filtered as raw (group of items relevant)

[AT]

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

AT  changed:

   What|Removed |Added

 Resolution|FIXED   |---
Version|4.12.0  |5.3.0
 Status|RESOLVED|UNCONFIRMED

--- Comment #19 from AT  ---
I have the same problem again/ still with digikam 5.3 on Sabayon using the
gentoo ebuild, though it feels like it is happening less frequently.
After batch-renaming a bunch of imades dgn is not recognized as raw until I
re-read the metadata.

Can't test with 5.4 appimage, stopped running after a crash with segfault.

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

[neon] [Bug 373667] Missing bottom border of Cancel button on Logout screen using Liberation fonts

[bugzilla_noreply]

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

--- Comment #1 from pjsingh5...@gmail.com ---
Created attachment 102861
  --> https://bugs.kde.org/attachment.cgi?id=102861=edit
Button border missing in Update widget using Liberation Sans Fonts

Here is an other example where the bottom portion of the button border is
missing.

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

[kalarm] [Bug 373848] New: Indicator not showing in Ubuntu Unity 16.10 (4:16.04.3-0ubuntu2)

[Sienile]

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

Bug ID: 373848
   Summary: Indicator not showing in Ubuntu Unity 16.10
(4:16.04.3-0ubuntu2)
   Product: kalarm
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: sie...@gmx.net
  Target Milestone: ---

I have no indicator icon when no alarm is set on Ubuntu Unity 16.10. Ubuntu
package version is 4:16.04.3-0ubuntu2, not sure what version that is based on.

Kalarm is running, but does not show an indicator icon unless and active alarm
is set. Shouldn't there be at least a disabled alarm icon?

Also any attempt to bring the window open via relaunching in terminal causes a
crash with the message:
"Message recipient disconnected from message bus without replying"

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

[kdev-python] [Bug 373847] New: No argument type-hints for __{get,set}__item

[Francis Herne]

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

Bug ID: 373847
   Summary: No argument type-hints for __{get,set}__item
   Product: kdev-python
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@flherne.uk
  Target Milestone: ---

Particularly for __setitem__, this can be a problem:

```
class MyClass:
   def __init__(self):
   self._contents = []

   def __getitem__(self, key):
   return self._contents[key]

   def __getitem__(self, key, value):
   self._contents[key] = value
```

...because then we don't deduce the type of MyClass._contents.

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

[krita] [Bug 373846] New: [brush-editor] "+Stamp" button is broken

[David REVOY]

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

Bug ID: 373846
   Summary: [brush-editor] "+Stamp" button is broken
   Product: krita
   Version: 3.1.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,
The button "+Stamp" in brush-editor>Pixel>Brush-tip>Predefined is broken in
3.1.

# How to reproduce:
- Open a new document
- Add a new layer
- Paint a little shape
- Select the shape ( rectangular selection around it )
- Open the brush-editor
- in brush-editor>Pixel>Brush-tip>Predefined press the button "+Stamp"

# Result:
- The preview proposed in the dialog is empty
- The selection do not send the bitmap to "+Stamp"
- If no selection, "+Stamp" doesn't take the full image too
- Impossible to create a brush-tip with it

# Workaround:
- Use 'Clipboard' button ( and press Ctrl+C on the selection prior using this
button ).

Note: affect this video tutorial (3:30) :
http://www.davidrevoy.com/article313/custom-brushes-stencil-stamps-with-krita ,
https://youtu.be/fgA4BcO3Nq8

Reproductible on Git~krita/3.1, appimage 3.0.94, appimage 3.0.92, appimage
alpha 3.0.1

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

[KSystemLog] [Bug 304310] 'More information...' link does not work

[Aniketh]

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

Aniketh  changed:

   What|Removed |Added

 CC||anikethgire...@gmail.com

--- Comment #2 from Aniketh  ---
Actually, where should this link be re-directed to then?

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

[kdev-python] [Bug 373845] New: Self argument can be included in *args

[Francis Herne]

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

Bug ID: 373845
   Summary: Self argument can be included in *args
   Product: kdev-python
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@flherne.uk
  Target Milestone: ---

```
class MyClass:
   def foo(*args):
   # args[0] is self, should have type `MyClass`.
```

Not really sure why anyone would do this, but it's valid

Currently KDevelop displays an erroneous warning ("first argument should be
self"), and `args` is an empty tuple.

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

[kdev-python] [Bug 373844] New: Class aliases often get converted to instances

[Francis Herne]

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

Bug ID: 373844
   Summary: Class aliases often get converted to instances
   Product: kdev-python
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: m...@flherne.uk
  Target Milestone: ---

e.g.
```
class MyClass:
   pass

class_list = [MyClass]

class_type = class_list[0]()  # should be an alias of 'MyClass', is instead an
instance.

foo = class_type()  # should be a MyClass instance, but is mixed
```

This is because classes and their instances share the same AbstractType, we
rely on the declaration which gets lost easily.

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

[kmailtransport] [Bug 373833] Kmail 16.12 fails to send emails

[avlas]

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

--- Comment #1 from avlas  ---
I get this message in the terminal when trying to unsuccessfully send an email:

org.kde.pim.akonadicore: Got a stale notification for an item which was already
removed. 327594 ""

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

[kmail2] [Bug 373843] kmail 5.4.0 "Act on new/unread mail in this folder" option not working

[Dimitris Damigos]

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

Dimitris Damigos  changed:

   What|Removed |Added

 CC||dami...@gmail.com

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

[kmail2] [Bug 373843] New: kmail 5.4.0 "Act on new/unread mail in this folder" option not working

[Dimitris Damigos]

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

Bug ID: 373843
   Summary: kmail 5.4.0 "Act on new/unread mail in this folder"
option not working
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: dami...@gmail.com
  Target Milestone: ---

I just noticed that "Act on new/unread mail in this folder" option is not
working anymore. I don't know since what version. When I change the value of
the option and click OK, if I reopen folder properties the previous value is
restored. The only way to change the value is through Settings-->Plugins-->New
Email Notifier-->Folders

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

[kwin] [Bug 373798] Super (Windows) Key does not open the menu after suspend.

[silentz0r]

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

--- Comment #4 from silentz0r  ---
(In reply to Martin Gräßlin from comment #3)
> > I've had this bug ever since the Meta key was changed to Super
> 
> What do you mean by that?

A few months ago the meta key was changed from a modifier key to work as a
super key, i.e. both as a modifier and as a single key, so we can finally use
it to open up the application menu/dashboard.

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

[kdevelop] [Bug 373842] New: Cannot format closed files

[bugzilla_noreply]

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

Bug ID: 373842
   Summary: Cannot format closed files
   Product: kdevelop
   Version: 5.0.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: astyle
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: alex-...@hotmail.com
  Target Milestone: ---

Trying to format files that are not opened in the editor results in "file
already exist" errors. 

Using the appimage.

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

[kaffeine] [Bug 372667] Crash with virtual adapter

[knossos456]

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

--- Comment #4 from knossos456  ---
my diseqc propblem is solved, I've changed the switch.

I have now problems on some DVB-S2 - 8PSK transponder.
DVB-S2 QPSK seem to be OK in all cases.
For example, i can't scan :
http://fr.kingofsat.net/tp.php?tp=259
my parameters for this transponder in scanfile.dvb are :
S2 11681000 H 2750 3/4 25 8PSK
What is wrong ?

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[knossos456]

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

--- Comment #14 from knossos456  ---
oups in wrong section

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[knossos456]

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

--- Comment #13 from knossos456  ---
my diseqc propblem is solved, I've changed the switch.

I have now problems on some DVB-S2 - 8PSK transponder.
DVB-S2 QPSK seem to be OK in all cases.
For example, i can't scan :
http://fr.kingofsat.net/tp.php?tp=259
my parameters for this transponder in scanfile.dvb are :
S2 11681000 H 2750 3/4 25 8PSK
What is wrong ?

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

[krita] [Bug 373837] New: Last used brush won't be remembered at next start, if it has been chosen from the (toolbar >) "Choose brush preset" dialog - (Krita 3.1.1 - Ubuntu 14.04)

[mvowada]

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

Bug ID: 373837
   Summary: Last used brush won't be remembered at next start, if
it has been chosen from the (toolbar >) "Choose brush
preset" dialog - (Krita 3.1.1 - Ubuntu 14.04)
   Product: krita
   Version: 3.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

(Krita 3.1.1 - Ubuntu 14.04)

If you choose a brush preset from the (main toolbar >) "Choose brush preset"
dialog window, it will not be remembered at the next start of Krita:

1) Start Krita.
2) Go to: (main toolbar) > "Choose brush preset" (the brush preset window will
open).
3) Select any of the brush presets from the list.
4) Restart Krita.

Actual Results: The last selected brush preset will not be active at the next
start.
Expected Results: It should be active at the next start of Krita.

---
Note 1: No problem when choosing the brush preset from the "Brush Presets"
docker: it will be correctly remembered at next start of Krita.

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

[kgpg] [Bug 373841] New: KGpg crashes on desktop start

[Christopher Burroughs]

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

Bug ID: 373841
   Summary: KGpg crashes on desktop start
   Product: kgpg
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: mon...@gmail.com
  Target Milestone: ---

Application: kgpg (16.11.90)

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

-- Information about the crash:
On each startup, KGpg crashes immediately. On most occasions, the password
prompt to unlock the key appears immediately afterwards without the need to
press Restart. However, if one does press Restart, then the application crashes
again immediately. On some occasions, it is impossible to unlock my KDE Wallet
due to KGpg unsuccessfully starting.

The crash can be reproduced every time.

-- Backtrace:
Application: KGpg (kgpg), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f02a2b18900 (LWP 2249))]

Thread 4 (Thread 0x7f0272833700 (LWP 2271)):
#0  0x7f029729e9a1 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f029729f230 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f029729f42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f029d1c732b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f029d174fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f029cfaff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f029cfb49e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f02986d3734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f029c6acd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f0282880700 (LWP 2265)):
#0  0x7f029c6a449d in poll () at /lib64/libc.so.6
#1  0x7f029729f314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f029729f42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f029d1c732b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f029d174fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f029cfaff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f029d8371d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f029cfb49e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f02986d3734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f029c6acd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f0283d9b700 (LWP 2263)):
#0  0x7f029c6a449d in poll () at /lib64/libc.so.6
#1  0x7f02979c23e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f02979c3fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f0285ea7839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f029cfb49e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f02986d3734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f029c6acd3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f02a2b18900 (LWP 2249)):
[KCrash Handler]
#6  0x7f029c5f78d7 in raise () at /lib64/libc.so.6
#7  0x7f029c5f8caa in abort () at /lib64/libc.so.6
#8  0x7f029c6351b4 in  () at /lib64/libc.so.6
#9  0x7f029c63a9d6 in malloc_printerr () at /lib64/libc.so.6
#10 0x7f029c63ef29 in realloc () at /lib64/libc.so.6
#11 0x7f029cfb7ab1 in QByteArray::reallocData(unsigned int,
QFlags) () at /usr/lib64/libQt5Core.so.5
#12 0x7f029cfb7cdf in QByteArray::resize(int) () at
/usr/lib64/libQt5Core.so.5
#13 0x7f029d0b22f6 in QIODevice::readAll() () at /usr/lib64/libQt5Core.so.5
#14 0x7f029d0b882a in QProcess::readAllStandardOutput() () at
/usr/lib64/libQt5Core.so.5
#15 0x004b4b1a in KLineBufferedProcessPrivate::_k_receivedStdout()
(this=0x251ec50) at
/usr/src/debug/kgpg-16.11.90/klinebufferedprocessprivate.cpp:31
#16 0x7f029d1a11c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#17 0x7f029d0b73bf in  () at /usr/lib64/libQt5Core.so.5
#18 0x7f029d1137a2 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7f029d0b83a2 in QProcess::waitForFinished(int) () at
/usr/lib64/libQt5Core.so.5
#20 0x004af2d9 in KgpgInterface::readSecretKeys(QStringList const&)
(ids=...) at /usr/src/debug/kgpg-16.11.90/kgpginterface.cpp:413
#21 0x00441e16 in KGpgRootNode::addKeys(QStringList const&)
(this=0x2303840, ids=...) at
/usr/src/debug/kgpg-16.11.90/core/KGpgRootNode.cpp:71
#22 0x00454d3c in KGpgItemModel::refreshAllKeys() (this=0x22fe9b0) at
/usr/src/debug/kgpg-16.11.90/model/kgpgitemmodel.cpp:474
#23 0x00489ca0 in KeysManager::refreshkey() (this=0x23029b0) at
/usr/src/debug/kgpg-16.11.90/keysmanager.cpp:2648
#24 0x004e9fca in KeysManager::qt_static_metacall(QObject*,

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

[Kristian Karl]

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

--- Comment #1 from Kristian Karl  ---
I noticed this first, when using a maximized Digikam window on a 4K monitor,
where enough faces/thumbnails were rendered to cause the flickering.

Reducing the size of the Digikam window will make the flickering go away.

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

[ksudoku] [Bug 373840] New: In game "killer sudoku" there are multiple solutions

[andreamal]

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

Bug ID: 373840
   Summary: In game "killer sudoku" there are multiple solutions
   Product: ksudoku
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: iandw...@gmail.com
  Reporter: andreamalfa...@tiscali.it
CC: kde-games-b...@kde.org
  Target Milestone: ---

Created attachment 102860
  --> https://bugs.kde.org/attachment.cgi?id=102860=edit
A game whit multiple solution

I'm sorry for my english.
In this game (and is not the first time) the end is uncertain.
If you look at the saved game you will understand without words

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

[digikam] [Bug 373839] New: Continuously face thumbnails flicker/update

[Kristian Karl]

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

Bug ID: 373839
   Summary: Continuously face thumbnails flicker/update
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Thumbnails
  Assignee: digikam-de...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

When opening the people view in a large window allowing for many faces, the
thumbnails will flicker continuously.

Steps to reproduce
==
1) Use the faces images from http://cswww.essex.ac.uk/mv/allfaces/faces94.html
   http://cswww.essex.ac.uk/mv/allfaces/faces94.zip
2) Create test folder and put the images there.
3) Create a new test database, and use the images above
5) Open the People view, and scan all images for faces using the default
options.
5) Look for Unknown, and set the size of the face thumbnails to smallest
(124px)
6) Make the window size for Digikam large enough until the flicker starts. I
usually get it with > ~210 faces (thumbnails).

Expected result

People view displays the thumbnails without flicker.

Actual result
===
People view displays the thumbnails constant flickering

Additional info
===
See video of flickering at https://youtu.be/AwmapnWNDBw
I get this on my laptop and desktop.

I was using digikam built from sources
(d72b486b7109fd80f6071fd78af2b9509de56044)

Observation
===
It seems that applying following patch makes the flicker go away. But I'm not
sure  what the downside of the patch is...

krikar@krikar-desktop:~/dev/kde/digikam/core$ git diff
diff --git a/app/items/imagecategorizedview.cpp
b/app/items/imagecategorizedview.cpp
index d5847c7..ba6dd47 100644
--- a/app/items/imagecategorizedview.cpp
+++ b/app/items/imagecategorizedview.cpp
@@ -737,14 +737,14 @@ ImageInfoList ImageCategorizedView::resolveGrouping(const
QModelIndexList indexe
 void ImageCategorizedView::paintEvent(QPaintEvent* e)
 {
 // We want the thumbnails to be loaded in order.
-ImageThumbnailModel* const thumbModel = imageThumbnailModel();
+/*ImageThumbnailModel* const thumbModel = imageThumbnailModel();

 if (thumbModel)
 {
 QModelIndexList indexesToThumbnail =
imageFilterModel()->mapListToSource(categorizedIndexesIn(viewport()->rect()));
 d->delegate->prepareThumbnails(thumbModel, indexesToThumbnail);
 }
-
+*/
 ItemViewCategorized::paintEvent(e);
 }

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

[kmail2] [Bug 373832] Kmail 16.12 crashes due to overdue time to lock

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Hi,
perhaps you can give us more info :)
For example info from console etc.

We don't have enough information to help you

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

[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[digikam] [Bug 373838] New: Add support for android's VectorDrawable xml format

[Teddy]

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

Bug ID: 373838
   Summary: Add support for android's VectorDrawable xml format
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: a1875...@trbvm.com
  Target Milestone: ---

Created attachment 102859
  --> https://bugs.kde.org/attachment.cgi?id=102859=edit
icon.xml (decompiled)

You need to decompile the apk using "APK Easy Tool" or similar.
The attached file belongs to:

Android application:
package:/system/priv-app/LGSystemUI/LGSystemUI.apk=com.android.systemui

Resource file inside the apk once decompiled:
res/drawable-nodpi-v4/icon.xml

More information:
https://developer.android.com/reference/android/graphics/drawable/VectorDrawable.html
https://developer.android.com/studio/write/vector-asset-studio.html
http://stackoverflow.com/questions/33091618/is-there-a-way-to-preview-a-vector-drawable

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