[kontact] [Bug 361605] kmail crash on double click email

[Christian Trippe via KDE Bugzilla]

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

--- Comment #4 from Christian Trippe  ---
Thanks for the quick fix and for the hint about kdepim-addons. Installing this
missing packages also "fixes" the crash for me.

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

[konsole] [Bug 361841] Konsole crash during session restore with ggdb info

[Techwolf via KDE Bugzilla]

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

Techwolf  changed:

   What|Removed |Added

Summary|Konsole crash during|Konsole crash during
   |session restore |session restore with ggdb
   ||info

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

[konsole] [Bug 361841] Konsole crash during session restore

[Techwolf via KDE Bugzilla]

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

--- Comment #1 from Techwolf  ---
Sources compiled with debug info, should help. Also, DrKonqi would not let me
attacted this crash report to another bug. I could only create a new bug
report.

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

[konsole] [Bug 361841] New: Konsole crash during session restore

[Techwolf via KDE Bugzilla]

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

Bug ID: 361841
   Summary: Konsole crash during session restore
   Product: konsole
   Version: 15.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: bugs.kde@trap.wereanimal.net

Application: konsole (15.12.3)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.4.6-zen x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
This happened after doing a startx from the command line to start my GUI
desktop

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

Thread 2 (Thread 0x7f2412b69700 (LWP 2673)):
#0  0x7f2423467b8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f241c224a72 in poll (__timeout=-1, __nfds=1, __fds=0x7f2412b68d00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x129aff0, cond=cond@entry=0x129b030,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f241c226627 in xcb_wait_for_event (c=0x129aff0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f2414f00b99 in QXcbEventReader::run (this=0x1293280) at
qxcbconnection.cpp:1229
#5  0x7f241feb17d2 in QThreadPrivate::start (arg=0x1293280) at
thread/qthread_unix.cpp:331
#6  0x7f241bdf942c in start_thread (arg=0x7f2412b69700) at
pthread_create.c:334
#7  0x7f2423470a9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f242399c7c0 (LWP 2671)):
[KCrash Handler]
#6  Konsole::Session::sessionId (this=this@entry=0x0) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/Session.cpp:897
#7  0x7f2423124a90 in Konsole::ViewManager::createTerminalDisplay
(this=this@entry=0x13a6dc0, session=session@entry=0x0) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/ViewManager.cpp:747
#8  0x7f242312b159 in Konsole::ViewManager::createView
(this=this@entry=0x13a6dc0, session=session@entry=0x0, container=0x149be40,
index=index@entry=11) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/ViewManager.cpp:523
#9  0x7f242312c450 in Konsole::ViewManager::createView
(this=this@entry=0x13a6dc0, session=session@entry=0x0) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/ViewManager.cpp:583
#10 0x7f242312c6db in Konsole::ViewManager::restoreSessions
(this=0x13a6dc0, group=...) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/ViewManager.cpp:941
#11 0x7f242273b5a0 in KMainWindow::readPropertiesInternal
(this=this@entry=0x13995b0, config=0x134db60, number=number@entry=1) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.20.0/work/kxmlgui-5.20.0/src/kmainwindow.cpp:648
#12 0x7f242273b602 in KMainWindow::restore (this=0x13995b0,
number=number@entry=1, show=show@entry=true) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.20.0/work/kxmlgui-5.20.0/src/kmainwindow.cpp:473
#13 0x7f2423750a94 in restoreSession (app=...) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/main.cpp:329
#14 0x7f2423751a7d in kdemain (argc=3, argv=0x7ffddf335328) at
/var/tmp/portage/kde-apps/konsole-15.12.3/work/konsole-15.12.3/src/main.cpp:124
#15 0x7f24233aa610 in __libc_start_main (main=0x400790 ,
argc=3, argv=0x7ffddf335328, init=, fini=,
rtld_fini=, stack_end=0x7ffddf335318) at libc-start.c:289
#16 0x004007c9 in _start ()

Possible duplicates by query: bug 359428, bug 356270, bug 355421.

Reported using DrKonqi

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[via KDE Bugzilla]

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

vindica...@live.com changed:

   What|Removed |Added

 CC||vindica...@live.com

--- Comment #1 from vindica...@live.com ---
Same: "upgraded plasma-framework (5.20.0-2 -> 5.21.0-1)"
Except I think it happens ALL of the time for me. I know, because I always have
my trash at the bottom left corner and with every restart, I have to move it
back.

Then on top of that, I can't have the widgets locked because that would block
any icon "drag" from happening which is another posted bug.

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

[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content

[via KDE Bugzilla]

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

--- Comment #3 from vindica...@live.com ---
Another big archlinux update today and it still exists: "upgraded
plasma-framework (5.20.0-2 -> 5.21.0-1)"

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

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[PGillespie via KDE Bugzilla]

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

PGillespie  changed:

   What|Removed |Added

 CC||vtp...@myfairpoint.net

--- Comment #21 from PGillespie  ---
After the most recent update (as of April 15th 2016) :

Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5
   Distro: Ubuntu 16.04 xenial


I'm also experiencing this bug. This appears to be a direct result of the
upgrade, as I never previously experienced his bug.

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

[krita] [Bug 360725] [INTEL] Krita crashes when I click OK to close the preference window

[tokiedian via KDE Bugzilla]

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

--- Comment #9 from tokiedian  ---
I confirmed the bug doesn't happen in this build!

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

[user-manager] [Bug 361832] System settings doesn't show the other users.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |afies...@kde.org
  Component|general |kcontrol module
Product|systemsettings  |user-manager

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

[plasma4] [Bug 361839] Inkscape crash on start

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |plasma4
  Component|general |plasma-netbook
   Assignee|unassigned-b...@kde.org |notm...@gmail.com

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

[kdelibs] [Bug 356214] Cannot type accented Asturian vowels áéíóú and umlaut ü in any KDE application

[Enol P . via KDE Bugzilla]

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

--- Comment #5 from Enol P.  ---
bump

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

[frameworks-solid] [Bug 361785] processor cores are shown in incorrect sequence is > 10

[Marius Cirsta via KDE Bugzilla]

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

--- Comment #1 from Marius Cirsta  ---
Created attachment 98416
  --> https://bugs.kde.org/attachment.cgi?id=98416=edit
patch to sort processors based on cpu number

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

[plasmashell] [Bug 361674] X11 damage events not generated when the desktop is exposed

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #10 from Thomas Lübking  ---
The X11 server is "unfortunately" pretty much free in deciding when to create
expose events (it does so, because it has no data for the window), this could
be defeated by a cache (backing store) or bypassing overlay output (not
uncommon for GLX)

There's afaik no method to get all frontbuffer updates from the server.
VNC keeps a copy of the framebuffer and compares the pixels of n with n-1 to
know which regions to update.

Combining Damage and Un/Map and ConfigureNotify events (alongside a Z test for
the latter two) might get you a complete idea on the flattened update region...
:-(

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

[kwin] [Bug 361837] Black decoration after closing a specific game, with Nvidia drivers

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #2 from Elvis Angelaccio  ---
(In reply to Thomas Lübking from comment #1)
> Left 4 Dead being a steam game?

Yes, it's a steam game running openGL. Thanks, I'll check the duplicate bug.

> 
> *** This bug has been marked as a duplicate of bug 361154 ***

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

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

[via KDE Bugzilla]

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

s...@linuxhowtos.org changed:

   What|Removed |Added

 CC||s...@linuxhowtos.org

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

[korganizer] [Bug 361840] New: Kontact 5.1.90 Crashes When Entering Event

[via KDE Bugzilla]

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

Bug ID: 361840
   Summary: Kontact 5.1.90 Crashes When Entering Event
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: caxilb...@iasinfo.com

Application: korganizer (5.1.90 rc)

Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: When entering event, the
application crashes.  I am using 5.1.90 rc on Frameworks 5.21.o on Qt 5.6.0 on
Opensuse Leap 42.1 64bit.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7fdc392e9700 (LWP 23221)):
#0  0x7fdc5901ebbd in poll () at /lib64/libc.so.6
#1  0x7fdc4df4d422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fdc4df4f00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fdc3b882979 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fdc59939079 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fdc507ea0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fdc59026fed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fdc332a1700 (LWP 23222)):
#0  0x7fdc59931aba in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7fdc59b4aa15 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fdc502c58f1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdc502c5df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fdc502c5f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fdc59b4a3fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fdc59af804b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fdc599345da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fdc58521095 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7fdc59939079 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fdc507ea0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fdc59026fed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fdc31e89700 (LWP 23226)):
#0  0x7fdc50307d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fdc502c58e9 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fdc502c5df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fdc502c5f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fdc59b4a3fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fdc59af804b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fdc599345da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fdc59939079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fdc507ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fdc59026fed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fdc31688700 (LWP 23228)):
#0  0x7fdc5901ac8d in read () at /lib64/libc.so.6
#1  0x7fdc50306b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fdc502c5999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdc502c5df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fdc502c5f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fdc59b4a3fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fdc59af804b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fdc599345da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fdc59939079 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fdc507ea0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fdc59026fed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fdc30e87700 (LWP 23230)):
#0  0x7fdc5901ebbd in poll () at /lib64/libc.so.6
#1  0x7fdc502c5e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fdc502c5f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fdc59b4a3fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fdc59af804b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fdc599345da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fdc59939079 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fdc507ea0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fdc59026fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fdc23fff700 (LWP 23232)):
#0  0x7fdc5901ebbd in poll () at /lib64/libc.so.6
#1  0x7fdc502c5e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  

[kwin] [Bug 361837] Black decoration after closing a specific game, with Nvidia drivers

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
Left 4 Dead being a steam game?

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

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||elvis.angelac...@kdemail.ne
   ||t

--- Comment #50 from Thomas Lübking  ---
*** Bug 361837 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 361715] After wake up PC Krita crash

[eliotJ via KDE Bugzilla]

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

--- Comment #3 from eliotJ  ---
>From IRC disscusion about this bug:

" Not sure if related since I'm on Linux but after waking up
from sleep there is all kinds of random noise on teh canvas until I do
something to update it."

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

[kde] [Bug 361839] New: Inkscape crash on start

[via KDE Bugzilla]

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

Bug ID: 361839
   Summary: Inkscape crash on start
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ash...@bbcb.co.uk

Application: plasma-netbook (0.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed: Just tried to start Inkscape. 
Crash happens then.  Started it from search
in kde.  Fresh boot of kde.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Netbook Shell (plasma-netbook), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc7d3e7a7c0 (LWP 2553))]

Thread 12 (Thread 0x7fc7acb1c700 (LWP 2556)):
#0  0x7fc7d37b912d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc7c8268fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc7c82690ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc7d0f1c7be in QEventDispatcherGlib::processEvents
(this=0x7fc7a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7fc7d0eee0af in QEventLoop::processEvents
(this=this@entry=0x7fc7acb1bde0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc7d0eee3a5 in QEventLoop::exec (this=this@entry=0x7fc7acb1bde0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc7d0deac5f in QThread::exec (this=this@entry=0x1df8420) at
thread/qthread.cpp:537
#7  0x7fc7d0ecf823 in QInotifyFileSystemWatcherEngine::run (this=0x1df8420)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fc7d0ded32f in QThreadPrivate::start (arg=0x1df8420) at
thread/qthread_unix.cpp:349
#9  0x7fc7c9b04182 in start_thread (arg=0x7fc7acb1c700) at
pthread_create.c:312
#10 0x7fc7d37c647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 11 (Thread 0x7fc7a7fff700 (LWP 2557)):
#0  0x7fc7d37b912d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc7c8268fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc7c82690ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc7d0f1c7be in QEventDispatcherGlib::processEvents
(this=0x7fc7a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7fc7d0eee0af in QEventLoop::processEvents
(this=this@entry=0x7fc7a7ffede0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc7d0eee3a5 in QEventLoop::exec (this=this@entry=0x7fc7a7ffede0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc7d0deac5f in QThread::exec (this=this@entry=0x1e02360) at
thread/qthread.cpp:537
#7  0x7fc7d0ecf823 in QInotifyFileSystemWatcherEngine::run (this=0x1e02360)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fc7d0ded32f in QThreadPrivate::start (arg=0x1e02360) at
thread/qthread_unix.cpp:349
#9  0x7fc7c9b04182 in start_thread (arg=0x7fc7a7fff700) at
pthread_create.c:312
#10 0x7fc7d37c647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7fc7a650e700 (LWP 2558)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc7d215fffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7fc7d2160039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7fc7c9b04182 in start_thread (arg=0x7fc7a650e700) at
pthread_create.c:312
#4  0x7fc7d37c647d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 9 (Thread 0x7fc70ca8e700 (LWP 2830)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc7d0ded816 in wait (time=18446744073709551615, this=0x1eea100) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1f14148, mutex=0x1dd3b50,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7fc7cc87ce6c in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f14120,
th=0x34cac50) at ../../../threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7fc7cc87f903 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1dc1ce0, th=0x34cac50, previous=0x0) at
../../../threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7fc7cc87f91c in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1dc1ce0, th=0x34cac50, previous=0x1a87700) at
../../../threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7fc7cc87e61f in ThreadWeaver::Thread::run (this=0x34cac50) at
../../../threadweaver/Weaver/Thread.cpp:98
#7  0x7fc7d0ded32f in QThreadPrivate::start (arg=0x34cac50) at
thread/qthread_unix.cpp:349
#8  

[kdenlive] [Bug 361838] New: Colour picker for Colour Clip can't work due to darkened background

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 361838
   Summary: Colour picker for Colour Clip can't work due to
darkened background
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

Trying to create a colour clip with the same colour as a background in another
clip is currently impossible with the colour picker tool, due to background
darkening.

Reproducible: Always

Steps to Reproduce:
When choosing 'Add Colour Clip' in the Project Bin, I often want to replicate
an existing background colour of another element in my edit. 
So from the colour dropdown, I choose "custom..."
In the dialogue box that appears, I choose 'pick screen colour'
I can then pick a colour from the clip in the project monitor - but everything
else has been darkened slightly to highlight the colour dialogue box.

Actual Results:  
The resulting colour clip is much darker than the colour I was trying to
sample.

Expected Results:  
Darkening the background in order to highlight the dialogue box is useful in
all other situations, so maybe the solution should be that the background stays
darkened until the 'pick screen colour" button is pressed - from this moment
until a colour is selected, everything would be shown at normal brightness
levels, and then once selected, the background would be darkened again.


Kdenlive version 16.07.70 - I'm using the kdenlive-testing ppa on kubuntu
15.10.

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

[kwin] [Bug 361837] Black decoration after closing a specific game, with Nvidia drivers

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

Summary|Black decoration after  |Black decoration after
   |closing a speficic game,|closing a specific game,
   |with Nvidia drivers |with Nvidia drivers

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

[kwin] [Bug 361837] New: Black decoration after closing a speficic game, with Nvidia drivers

[Elvis Angelaccio via KDE Bugzilla]

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

Bug ID: 361837
   Summary: Black decoration after closing a speficic game, with
Nvidia drivers
   Product: kwin
   Version: 5.6.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: elvis.angelac...@kdemail.net

Hi,
I recently upgraded my nvidia gpu and I'm now experiencing an annoying bug. I'm
using the proprietary drivers.
Consider the following screenshot:
https://share.kde.org/index.php/s/iiajoJ9qAXaBvdx

Reproducible: Always

Steps to Reproduce:
1. Start the "Left 4 Dead 2" game from Plasma
2. Quit the game
3. Open any other window

Actual Results:  
A broken black decoration in the new window

Expected Results:  
A normal decoration in the new window

I cited Left 4 dead 2 because it seems the only game to trigger the bug.
However with my old gpu (always a Nvidia with proprietary drivers) everything
was working as expected.

I know that this is probably going to be difficult to reproduce for you, so
please let me know what exactly can I provide you to debug this.

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

[kontact] [Bug 361605] kmail crash on double click email

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdep
   ||im/648eb9094de4584135641de4
   ||49c6ba0a0f5e11be
 Resolution|--- |FIXED
   Version Fixed In||5.2.1

--- Comment #3 from Laurent Montel  ---
Git commit 648eb9094de4584135641de449c6ba0a0f5e11be by Montel Laurent.
Committed on 15/04/2016 at 21:31.
Pushed by mlaurent into branch 'Applications/16.04'.

Fix Bug 361605 - kmail crash on double click email

FIXED-IN: 5.2.1

M  +3-1kmail/kmreadermainwin.cpp

http://commits.kde.org/kdepim/648eb9094de4584135641de449c6ba0a0f5e11be

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

[krita] [Bug 361715] After wake up PC Krita crash

[eliotJ via KDE Bugzilla]

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

--- Comment #2 from eliotJ  ---
Hi Boud

Very strange is that in v2.9.10.2 Animation Edition 64 bit (I using it for
weeks now, everyday) this crash not appear... Maybe this is qt5 related
somehow...

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

[plasma4] [Bug 361836] New: High CPU usage when I open the applications launcher

[Gerard via KDE Bugzilla]

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

Bug ID: 361836
   Summary: High CPU usage when I open the applications launcher
   Product: plasma4
   Version: unspecified
  Platform: Ubuntu Packages
   URL: http://i.imgur.com/b8jTBGa.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: containment-desktop
  Assignee: plasma-b...@kde.org
  Reporter: scitech...@gmail.com

CPU usage increases a lot (from 0-2% to ~30%) and it keeps high all the time
when I open the applications launcher by clicking on the desktop with the
mouse.

This is the applications launcher I'm mentioning:
http://i.imgur.com/L9fzkGx.png

The problem is not happening using the other menus, like KDE menu in both
versions (Classical and default).

I changed the icons to the default, I disabled Kwin, I switched xrender, OpenGL
1.2, 2.0 & 3.0, disabled vsync, I changed the button of the mouse, and I even
renamed to ~/.kde folder in order to reset the KDE settings to find the
problem. But the bug persists in all this conditions.

The bug doesn't occur using clearlooks, CDE, Plastik or QtCurve. Only in
Oxygen.

Reproducible: Always

Steps to Reproduce:
1. Open the Desktop Settings, go to Mouse Actions
2. Select the Applications launcher in one mouse button
3. Now click the configured button in the desktop and check how the CPU usage
increases. Navigate through the menus, all the menus, and the CPU usage will
increase even more.

Actual Results:  
CPU usage increased a lot and it stays high until I reset the computer. See the
screenshot attached: http://i.imgur.com/b8jTBGa.png

Expected Results:  
CPU usage should decrease to normal values after opening the menu, or at least,
after closing it. CPU usage gets stuck in high values when it shouldn't.

I'm using KDE 4.13.3 (this version was not in the list).

For me, I can stop using that menu and it's not a big problem. I use Krunner
most of times and I like it. But knowing there's a bug I wanted to notify you.

I was not sure if to publish that bug in Oxygen section or plasma4. I decided
to publish it here because it's an option from the plasma settings. There's a
correlation between this bug and Oxygen, but that doesn't mean there's
causality.

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

[kate] [Bug 361569] Kate crashed - possible python plugin issue

[via KDE Bugzilla]

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

--- Comment #1 from iruc...@mail2world.com ---
I have just attempted to run Kate from Konsole and the output follows:


$ kate
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kate(8287)/Kate (On-The-Fly Spellcheck)
KateOnTheFlyChecker::KateOnTheFlyChecker: created
Object::connect: No such signal
KateBuffer::respellCheckBlock(KateDocument*,int,int)
kate(8287)/Kate (On-The-Fly Spellcheck) KateOnTheFlyChecker::updateConfig:
kate(8287)/Kate (On-The-Fly Spellcheck) KateOnTheFlyChecker::freeDocument:
kate(8287)/kate-filetree KateFileTreePluginView::KateFileTreePluginView: BEGIN:
mw: Kate::MainWindow(0x26f8720)
kate(8287)/kate-filetree ProxyItem::ProxyItem:
ProxyItem(0x3788680,0x0,-1,QObject(0x0) ,"m_root")
kate(8287)/kate-filetree ProxyItem::ProxyItem:
ProxyItem(0x3788720,0x0,-1,QObject(0x0) ,"Untitled")
kate(8287)/kate-filetree KateFileTreeModel::documentOpened: before add:
ProxyItem(0x3788720,0x0,-1,KateDocument(0x292a6c0) , "Untitled" )
kate(8287)/kate-filetree KateFileTreeModel::setupIcon: BEGIN!
kate(8287)/kate-filetree KateFileTreeModel::setupIcon: END!
kate(8287)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(8287)/kate-filetree KateFileTreeModel::handleInsert: empty item
kate(8287)/kate-filetree ProxyItem::addChild: added
ProxyItem(0x3788720,0x3788680,0,KateDocument(0x292a6c0) , "Untitled" )   to
ProxyItemDir(0x3788680,0x0,-1,"m_root", children:1)
kate(8287)/kate-filetree KateFileTreeModel::documentOpened: after add:
ProxyItem(0x3788720,0x3788680,0,KateDocument(0x292a6c0) , "Untitled" )
kate(8287)/kate-filetree KateFileTreeProxyModel::KateFileTreeProxyModel: BEGIN!
kate(8287)/kate-filetree KateFileTreePluginView::setListMode: BEGIN
kate(8287)/kate-filetree KateFileTreePluginView::setListMode: treeMode
kate(8287)/kate-filetree KateFileTreePluginView::setListMode: END
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
/usr/lib/python2.7/dist-packages/IPython/frontend.py:30: UserWarning: The
top-level `frontend` package has been deprecated. All its subpackages have been
moved to the top `IPython` level.
kate: /build/buildd/sip4-4.15.5/siplib/siplib.c:8407:
sip_api_can_convert_to_type: Assertion `(((td)->td_flags & 0x0007) == 0x)
|| (((td)->td_flags & 0x0007) == 0x0002)' failed.
KCrash: Application 'kate' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/uoxyh/.kde/socket-uoy/kdeinit4__0

[1]+  Stopped kate
uoxyh@uoy:/usr/lib/python2.7/dist-packages/IPython$ QSocketNotifier: Invalid
socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
Unable to start Dr. Konqi
Not forwarding the crash to Apport.

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

[kmail2] [Bug 361834] Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

--- Comment #6 from Kjetil Kilhavn  ---
Created attachment 98415
  --> https://bugs.kde.org/attachment.cgi?id=98415=edit
Window screenshot of message in separate window (for easier recreation of same
window size)

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

[kmail2] [Bug 361834] Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

--- Comment #5 from Kjetil Kilhavn  ---
Created attachment 98414
  --> https://bugs.kde.org/attachment.cgi?id=98414=edit
Message displayed as HTML with external resources

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

[kmail2] [Bug 361834] Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

--- Comment #3 from Kjetil Kilhavn  ---
Created attachment 98412
  --> https://bugs.kde.org/attachment.cgi?id=98412=edit
Message displayed as HTML without external resources (top of message)

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

[kmail2] [Bug 361834] Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

--- Comment #2 from Kjetil Kilhavn  ---
Created attachment 98411
  --> https://bugs.kde.org/attachment.cgi?id=98411=edit
Message displayed as plain text (default in my configuration)

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

[kmail2] [Bug 361834] Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

--- Comment #1 from Kjetil Kilhavn  ---
Created attachment 98410
  --> https://bugs.kde.org/attachment.cgi?id=98410=edit
Message that caused the erratic behaviour

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

[konsole] [Bug 361835] New: Environment variables inside command line <-e> option are expanded even when they must not

[Egor via KDE Bugzilla]

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

Bug ID: 361835
   Summary: Environment variables inside command line <-e> option
are expanded even when they must not
   Product: konsole
   Version: 2.14.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: egor_skriptun...@myway.com

Any $VAR in command line after <-e> option gets replaced with its value despite
of enclosing with single quotes

Reproducible: Always

Steps to Reproduce:
$ konsole -e bash -c 'echo $SHELL;echo '\''$SHELL'\'';read'

Actual Results:  
/bin/bash
/bin/bash

Expected Results:  
/bin/bash
$SHELL

1. Lets consider the following command:
echo $SHELL;echo '$SHELL';read
It prints two lines: expanded and non-expanded $SHELL
First line of output: /bin/bash
Second line of output: $SHELL

2.  Wrap the command from step #1 with single quotes:
'echo $SHELL;echo '\''$SHELL'\'';read'

3. Append  to the string from step #2:
bash -c 'echo $SHELL;echo '\''$SHELL'\'';read'
This command does exactly the same as command from step #1.

4. Use some other terminal emulator (for example, xterm) to use command from
step #3 as argument for <-e> option:
xterm -e bash -c 'echo $SHELL;echo '\''$SHELL'\'';read'
It works as expected: it prints expanded $SHELL and non-expanded $SHELL:
/bin/bash
$SHELL

5. Now test the command from step #3 with <-e> option using konsole:
konsole -e bash -c 'echo $SHELL;echo '\''$SHELL'\'';read'
It prints:
/bin/bash
/bin/bash
konsole seems to always expand environment variables in <-e command args>.
This behavior looks like a bug.

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

[kmail2] [Bug 361834] New: Incorrect calculation of repaint region when message display pane is close to requiring scroll bars?

[Kjetil Kilhavn via KDE Bugzilla]

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

Bug ID: 361834
   Summary: Incorrect calculation of repaint region when message
display pane is close to requiring scroll bars?
   Product: kmail2
   Version: 5.1.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: kje...@kilhavn.no

An email message that in its HTML form contains a background image which is an
external resource leads to a display anomaly when loading external resources.
The problem occurs only for specific window sizes, so I suspect it is related
to calculation of the region that must be repainted.

I accidentally discovered that if I turn on display of message structure
(displayed below message pane) the problem does not occur! So I experimented a
little more with the message opened in a separate window and discovered that
the problem did not occur then either. However; it turns out that it depends on
the window size - so when changed the size of the separate message window to
match the message area size in KMail the problem occurred again. It did not
occur for a smaller window, nor for a larger window. 
I suspect that with a larger screen I would be able to reproduce the problem
also with the message structure displayed.

Reproducible: Always

Steps to Reproduce:
If required, change KMail settings to display plain text email by default and
display HTML status bar in message window before attempting to reproduce the
problem.

1. Load attached message into KMail
2. Switch to HTML version
3. Load external resources

Actual Results:  
The right edge of the window (where the scroll bar was before loading external
resources) is not repainted correctly. It shows the mail header and parts of
the background - from the size distortion it seems there is an initial
rendering run, and the scroll bar area shows the result of this rendering.

Expected Results:  
The message should have displayed without a strange artefact in the scrollbar
area.

I am setting the severity to Normal instead of Minor because I hope there can
also be some performance gained from fixing this bug - assuming a fix leads to
a 50% reduction in rendering runs (from 2 to 1).

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Boudhayan Gupta via KDE Bugzilla]

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

--- Comment #10 from Boudhayan Gupta  ---
I can confirm that I've reproduced this bug on my computer. I strongly suspect
this is a Qt 5.6 problem.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Boudhayan Gupta via KDE Bugzilla]

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

--- Comment #9 from Boudhayan Gupta  ---
Right, I'll try and fix this tomorrow

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

[krita] [Bug 361530] Filter preview of an area under selection is becomes white , it is normal when there is no selection

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/006eb79faf8e3239addf63260
   ||6b3d54dc27eb8a3
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Dmitry Kazakov  ---
Git commit 006eb79faf8e3239addf632606b3d54dc27eb8a3 by Dmitry Kazakov.
Committed on 15/04/2016 at 19:26.
Pushed by dkazakov into branch 'master'.

Fix creating a cloned in LoD mode

Fixes T2217

M  +6-2libs/image/kis_paint_device.cc

http://commits.kde.org/krita/006eb79faf8e3239addf632606b3d54dc27eb8a3

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

[konversation] [Bug 361833] New: next/previous icons missing on buttons in search

[Fuchs via KDE Bugzilla]

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

Bug ID: 361833
   Summary: next/previous icons missing on buttons in search
   Product: konversation
   Version: frameworks
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: deve...@fuchsnet.ch

Apparently in the KF5 version the icons on prev/next buttons in the search are
missing. 

Icon set used is the default (breeze)

Reproducible: Always

Steps to Reproduce:
1. Open the search (Ctrl+F)
2. Look at the prev / next buttons


Actual Results:  
They don't have an icon but blank space on the left

Expected Results:  
They have an icon or no blank space on the left

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

[umbrello] [Bug 351103] Umbrello crashes when changing type for an operation for a class

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Blocks||331655

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

[umbrello] [Bug 331655] auto-generated getters and settersto atributes are private in generated java classes

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 CC||ralf.habac...@freenet.de
 Depends on||351103

--- Comment #3 from Ralf Habacker  ---
(In reply to Benedikt Geißler from comment #2)
> Unfortunately I do not see any further options for the export of Java code.
> I'm using Umbrello 2.18.3 from OpenSUSE Leap 42.1 and there setting further
> options is only possible at the C++ code export.
New codegenerator is only enabled in the git master branch because of major
design issues. See bug 351103

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

[systemsettings] [Bug 361832] New: System settings doesn't show the other users.

[Theo Sutton-Marceau via KDE Bugzilla]

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

Bug ID: 361832
   Summary: System settings doesn't show the other users.
   Product: systemsettings
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: theosuttonmarc...@gmail.com

Doesn't show the other users in account details in system settings. I'm using
Kubuntu 15.10 .

Reproducible: Always

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

[kontact] [Bug 361605] kmail crash on double click email

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
(In reply to Christian Trippe from comment #1)
> I am not sure if this is related
> but starting with kmail 16.03.90 where also the header in the normal mail
> view is missing and cannot be chosen from the menu.

Installing kdepim-addons should fix that.
We need to add a dependency there...

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

[muon] [Bug 342390] Not always possible to unmark a package action

[Carlo Vanini via KDE Bugzilla]

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

Carlo Vanini  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/libq
   ||apt/6db42277651409eeb92fa4f
   ||67c64f85434db387e
 Resolution|--- |FIXED

--- Comment #1 from Carlo Vanini  ---
Git commit 6db42277651409eeb92fa4f67c64f85434db387e by Carlo Vanini.
Committed on 15/04/2016 at 17:30.
Pushed by vanini into branch 'master'.

Fix "ReInstall" action not being enabled.

Fix mark/Unmark for ReInstall of a package.

Testing Done:
* select an installed package
* mark for re-install
* mark for keep or click Undo
Related: bug 342389
REVIEW: 127545

M  +5-1src/backend.cpp
M  +4-1src/package.cpp

http://commits.kde.org/libqapt/6db42277651409eeb92fa4f67c64f85434db387e

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

[muon] [Bug 342389] Unable to mark packages for re-install

[Carlo Vanini via KDE Bugzilla]

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

Carlo Vanini  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/libq
   ||apt/6db42277651409eeb92fa4f
   ||67c64f85434db387e

--- Comment #5 from Carlo Vanini  ---
Git commit 6db42277651409eeb92fa4f67c64f85434db387e by Carlo Vanini.
Committed on 15/04/2016 at 17:30.
Pushed by vanini into branch 'master'.

Fix "ReInstall" action not being enabled.

Fix mark/Unmark for ReInstall of a package.

Testing Done:
* select an installed package
* mark for re-install
* mark for keep or click Undo
Related: bug 342390
REVIEW: 127545

M  +5-1src/backend.cpp
M  +4-1src/package.cpp

http://commits.kde.org/libqapt/6db42277651409eeb92fa4f67c64f85434db387e

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #8 from Kai Uwe Broulik  ---
Just encountered it yesterday, I can confirm that with the new QML-UI it's
broken, I reverted back 15.12 branch and there it works.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Boudhayan Gupta via KDE Bugzilla]

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

--- Comment #7 from Boudhayan Gupta  ---
But we specifically tested with QT_DEVICE_PIXEL_RATIO=2 and confirmed the new
implementation was working. We even made minor corrections to the code to fix
edge cases.

Kai, if you have some free time could you verify this bug?

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

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

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC|mklape...@kde.org   |

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

[krita] [Bug 361577] Clone tool brush stroke causes crash

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/krit
   ||a/39ce4e79e84658fb5414a314d
   ||3ba08293a484643
 Resolution|--- |FIXED

--- Comment #7 from Dmitry Kazakov  ---
Git commit 39ce4e79e84658fb5414a314d3ba08293a484643 by Dmitry Kazakov.
Committed on 15/04/2016 at 18:46.
Pushed by dkazakov into branch 'master'.

Fix clone brush

Do not skip calling parent class implementation

Fixes T2246

M  +1-1   
plugins/paintops/defaultpaintops/duplicate/kis_duplicateop_settings.cpp

http://commits.kde.org/krita/39ce4e79e84658fb5414a314d3ba08293a484643

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

[systemsettings] [Bug 356444] Fonts on the rigth side of the font manager appear without smoothed edges

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||wba...@tmo.at
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Wolfgang Bauer  ---
Seems to be the same as Bug#336089, which should be fixed in 5.5.4...

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

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

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

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||slartibar...@gmail.com

--- Comment #68 from Wolfgang Bauer  ---
*** Bug 356444 has been marked as a duplicate of this bug. ***

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

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

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #17 from Wolfgang Bauer  ---
(In reply to Walter Nicholls from comment #16)
> Since commit was to Plasma 5.4, then seems iike that it will be solved in
> Kubuntu 16.04 (which ships Plasma 5.5) . Here's hoping.

This bug report was about the progress dialog being shown forever (and
systemsettings5 being completely frozen) in the KF5 version, even when only
installing *one* font.
And this should be fixed in 5.4 and up.

The problem you describe with multiple fonts is still reproduceable here with
5.6.2.
But it's probably a completely different bug and should be reported separately.

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

[clazy] [Bug 361691] Suggestion to turn string into QStringLiteral instead of QLatin1String

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

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

--- Comment #8 from Sergio Martins  ---
I think that settles it then

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

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

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||herald...@gmail.com

--- Comment #67 from Wolfgang Bauer  ---
*** Bug 357001 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 357001] Font management tool does not render preview properly

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||wba...@tmo.at
 Resolution|--- |DUPLICATE

--- Comment #2 from Wolfgang Bauer  ---
(In reply to St Weiss from comment #1)
> Duplicate, see #336089

Right, and it should be fixed since 5.5.4.

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

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

[kdevplatform] [Bug 361831] New: Please implement action "Cut" in project tree

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 361831
   Summary: Please implement action "Cut" in project tree
   Product: kdevplatform
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: project
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aspotas...@gmail.com

Please implement action "Cut" in project tree to support two-step moving of
files between project subdirectories ("Cut", then "Paste").

Reproducible: Always

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

[krita] [Bug 361721] various issues with small grid sizes

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/krit
   ||a/e6c23b2765dd007b7b10ec480
   ||036d657d443d159

--- Comment #2 from Dmitry Kazakov  ---
Git commit e6c23b2765dd007b7b10ec480036d657d443d159 by Dmitry Kazakov.
Committed on 15/04/2016 at 18:22.
Pushed by dkazakov into branch 'master'.

Fix wrong values of Grid spacing when changing the spin box

1) KisAspectRatioLocker blocks the signal of the second spinbox,
   but the configuration should be updated only when both the
   spinboxes are updated. Therefore a new signal in KisAspectRatioLocker
   has been implemented, which notifies the receivers that both boxes
   are ready.

2) Allow 1 px grid :)

Fixes T2245

M  +5-0libs/ui/kis_aspect_ratio_locker.cpp
M  +4-0libs/ui/kis_aspect_ratio_locker.h
M  +6-8plugins/dockers/griddocker/grid_config_widget.cpp
M  +8-8plugins/dockers/griddocker/grid_config_widget.ui

http://commits.kde.org/krita/e6c23b2765dd007b7b10ec480036d657d443d159

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

[kdevplatform] [Bug 361830] New: Create only one VCS output when moving multiple files

[Alexander Potashev via KDE Bugzilla]

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

Bug ID: 361830
   Summary: Create only one VCS output when moving multiple files
   Product: kdevplatform
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: vcs
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aspotas...@gmail.com

When moving multiple files at once to another folder, KDevelop creates a VCS
output log for each "git mv" operation (in the "Version Control" panel). It
would be better to have all the "git mv" commands in one log.

Reproducible: Always

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

[digikam] [Bug 361829] New: rotated mp4 videos ("Orientation" flag) are not played back in the correct rotation angle

[Jens B . Benecke via KDE Bugzilla]

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

Bug ID: 361829
   Summary: rotated mp4 videos ("Orientation" flag) are not played
back in the correct rotation angle
   Product: digikam
   Version: 4.14.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Preview
  Assignee: digikam-de...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de

I have a lot of videos shot on iPhones or iPads in portrait mode. These are MOV
(or MP4) files which have an "Orientation" metadata flag set. In iPhoto they
are displayed correctly rotated, but in Digikam 4.14 they are not. (I can't
test Digikam 5 because even on my Virtualbox Kubuntu 15.10, Digikam 5beta5
packages by philip5 flatly refuse to preview or show videos at all right now.)

I would wish for Digikam's player (phonon, gstreamer, ...) to correctly respect
the "Orientation" flag in MOV and MP4 files (I don't know about other video
formats) and to display the videos correctly.
If required, please reassign this bug to the correct project if Digikam itself
cannot do anything about this.

Thank you!

Reproducible: Always

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

[plasmashell] [Bug 361826] New: plasma crash while restoring minimized window

[Luís Henrique Camargo Quiroz via KDE Bugzilla]

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

Bug ID: 361826
   Summary: plasma  crash while restoring minimized window
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: luis...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing-updates (sid)

-- Information about the crash:
- What I was doing when the application crashed:
I selected one of 4 minimized instances of Firefox and plasma crashed. After a
while it automatically restarted, however.

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

Thread 7 (Thread 0x7f9504373700 (LWP 9786)):
#0  0x7f9513a4be4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9517afe382 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9517a7 in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f950566a789 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f95141307fe in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9513254454 in start_thread (arg=0x7f9504373700) at
pthread_create.c:334
#6  0x7f9513a54ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f9501b2a700 (LWP 9789)):
#0  0x7f95141e0bc6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f95143654e9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9514365a55 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9514366e3e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f95107f68bd in g_main_context_prepare
(context=context@entry=0x7f94f4000990, priority=priority@entry=0x7f9501b29b30)
at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3442
#5  0x7f95107f725b in g_main_context_iterate
(context=context@entry=0x7f94f4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3820
#6  0x7f95107f743c in g_main_context_iteration (context=0x7f94f4000990,
may_block=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#7  0x7f9514367a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f951430ed6a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f951412b854 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f95169be105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f95141307fe in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f9513254454 in start_thread (arg=0x7f9501b2a700) at
pthread_create.c:334
#13 0x7f9513a54ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f94f2fe6700 (LWP 9791)):
#0  0x7f951083ba79 in g_mutex_lock (mutex=mutex@entry=0x7f94ec000990) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gthread-posix.c:1338
#1  0x7f95107f7428 in g_main_context_iteration (context=0x7f94ec000990,
may_block=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3900
#2  0x7f9514367a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f951430ed6a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f951412b854 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f95169be105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f95141307fe in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9513254454 in start_thread (arg=0x7f94f2fe6700) at
pthread_create.c:334
#8  0x7f9513a54ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f94f0ff3700 (LWP 9799)):
#0  0x7f9513a4be4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f95107f732c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f94e4003070, timeout=, context=0x7f94e4000990) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x7f95107f732c in g_main_context_iterate
(context=context@entry=0x7f94e4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3835
#3  0x7f95107f743c in g_main_context_iteration (context=0x7f94e4000990,
may_block=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#4  0x7f9514367a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[kontact] [Bug 361605] kmail crash on double click email

[Christian Trippe via KDE Bugzilla]

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

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

--- Comment #1 from Christian Trippe  ---
I see the same crash in openSUSE. It also happens with standalone kmail, so I
guess this might be the better product. I am not sure if this is related but
starting with kmail 16.03.90 where also the header in the normal mail view is
missing and cannot be chosen from the menu.

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

[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings

[Stefano Forli via KDE Bugzilla]

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

Stefano Forli  changed:

   What|Removed |Added

 CC||ntro...@gmail.com

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

[plasma4] [Bug 238817] Executing Plasma Desktop Scripts within a bash script

[Cristiano Guadagnino via KDE Bugzilla]

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

Cristiano Guadagnino  changed:

   What|Removed |Added

 CC||crigu...@gmail.com

--- Comment #16 from Cristiano Guadagnino  ---
+1

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

[krita] [Bug 361728] Files with filter layers or fill layers assert in an instant preview related part.

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/krit
   ||a/0bbe01be4395e41b88401d0c6
   ||552284cbc387b1d
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Dmitry Kazakov  ---
Git commit 0bbe01be4395e41b88401d0c6552284cbc387b1d by Dmitry Kazakov.
Committed on 15/04/2016 at 17:30.
Pushed by dkazakov into branch 'master'.

Fix initialization of the default bounds object for filter and fill layers

Fixes T2247

M  +1-1libs/image/kis_selection_based_layer.cpp

http://commits.kde.org/krita/0bbe01be4395e41b88401d0c6552284cbc387b1d

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

[krita] [Bug 361824] New: Brush tip/outline preview doesn't refresh while resizing.

[Quiralta via KDE Bugzilla]

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

Bug ID: 361824
   Summary: Brush tip/outline preview doesn't refresh while
resizing.
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: rjquira...@gmail.com

While using shift-leftbutton (stroke with a pen) to resize, the outline of the
brush doesn't refresh, it gets "stuck" until I stop the stroke, then it "jumps"
the final size, it looks like it flickers, some brushes like the "ink_brush_25"
would work only if the stroke is very slow with some slight flickering, I found
that the "Bristles_hairy" resizing works normal, no lag/flickering.

I am using Nvidia proprietary drivers on a Archlinux box, Krita build from
source.

Reproducible: Always

Steps to Reproduce:
1.Open Document
2.Select a brush (Airbrushes are good example)
3.Resize by Shift+leftbutton (pen stroking)

Actual Results:  
Outline of the brush would not refresh, lag and flicker.

Expected Results:  
Smoothly increase decrease the size of the brush outline.

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

[krdc] [Bug 361823] New: I missed all my bookmarks after upgrade to KDE Applications 16.03.90

[Juan R . Rodriguez via KDE Bugzilla]

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

Bug ID: 361823
   Summary: I missed all my bookmarks after upgrade to KDE
Applications 16.03.90
   Product: krdc
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: uwol...@kde.org
  Reporter: juanrr...@gmail.com

After upgrade KRDC version 15.12.3 to version 16.03.90 I don't have any of my
bookmarks and don't know how to import / convert them.

Reproducible: Didn't try



Expected Results:  
All my bookmarks from the previus version be imported automatically.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

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

--- Comment #5 from Weng Xuetian  ---
Now I'm on 16.03.90 (with Qt 5.6.0 KF 5.21), I notice that "Rectangle region"
had the this problem again. It only shows the left top 1/4 part of the screen.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #6 from Weng Xuetian  ---
I have no problem with 15.12.3 if I downgrade only spectacle.

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

[kdenlive] [Bug 361822] New: git 16.04: resetting effect does not work for bin effects

[via KDE Bugzilla]

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

Bug ID: 361822
   Summary: git 16.04: resetting effect does not work for bin
effects
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: wegwerf-1-...@gmx.de

Resetting the parameters of a bin effect (using the hamburger menu of the
effect) does not reset the parameters to their default settings.

Reproducible: Always

Steps to Reproduce:
1. Create a Kdenlive project, such as FullHD 25fps.
2. Add a clip to the project bin.
3. Add an effect to the clip in the project bin, such as Lift/Gamma/Gain.
4. Change the effect parameters
5. Chose "Reset Effect" from the effect's Hamburger menu.

Actual Results:  
Effect parameters don't get reset to their defaults.

Expected Results:  
Effect parameters should be reset to their defaults.

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

[plasmashell] [Bug 361821] New: Plasma crash after clicking Launcher & typing four letters to search for an application

[via KDE Bugzilla]

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

Bug ID: 361821
   Summary: Plasma crash after clicking Launcher & typing four
letters to search for an application
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lpmccrac...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-0.slh.1-aptosid-amd64 x86_64
Distribution (Platform): Debian stable

-- Information about the crash:
- What I was doing when the application crashed:
I clicked the Launcher on the left side of the panel, typed the first few
letters of chromium, maybe four or five letters, pressed enter, then the plasma
shell crashed.  The panel with the Launcher & the system tray went away.  The
Crash reported started, Chromium started, & after 10 to 20 seconds, the panel
came back.

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

Thread 14 (Thread 0x7fae44940700 (LWP 17690)):
#0  0x7fae5712195a in QMutex::lock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fae5735ffdf in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fae537ef8bd in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fae537f025b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fae537f043c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fae57360a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fae57307d6a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fae57124854 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fae599b7105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fae571297fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fae5624d454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#11 0x7fae56a4dedd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 13 (Thread 0x7fae3d193700 (LWP 17692)):
#0  0x7fae53834a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fae537ef8c9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fae537f025b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fae537f043c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fae57360a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fae57307d6a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fae57124854 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fae599b7105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fae571297fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fae5624d454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7fae56a4dedd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 12 (Thread 0x7fae35f8b700 (LWP 17695)):
#0  0x7fae53834a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fae537ef8c9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fae537f025b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fae537f043c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fae57360a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fae57307d6a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fae57124854 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fae599b7105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fae571297fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fae5624d454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7fae56a4dedd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 11 (Thread 0x7fae2700 (LWP 17696)):
#0  0x7fae5625304f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7fae5bd641c4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fae5bd64209 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fae5624d454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7fae56a4dedd in clone () from 

[kdelibs] [Bug 324975] (regression) Volume gets restored to 100% after each knotify event

[via KDE Bugzilla]

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

--- Comment #110 from redbo...@gmail.com ---
(In reply to Rex Dieter from comment #109)
> fedora includes the fixes referenced here, if you're still seeing similar
> symptoms, the cause is (most likely) different.

So, if I already ran "dnf update" it will have already included the bug fix
discussed in this thread?

Ok, Thanks for the quick reply.  I'll keep searching the "interwebs" ;)

Kelly

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

[kdelibs] [Bug 324975] (regression) Volume gets restored to 100% after each knotify event

[via KDE Bugzilla]

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

redbo...@gmail.com changed:

   What|Removed |Added

 CC||redbo...@gmail.com

--- Comment #108 from redbo...@gmail.com ---
I realize this is an old thread, but I'm new to Fedora (and Linux for that
matter) I just loaded and updated Fedora 23 on a Lenovo T450.  I have the same
problem as most of the others on this thread.  I can adjust my volume below
100% but as soon as a sound plays it will reset to 100%.

Is there a quick fix or do I have to keep my sound muted until Fedora patches
it?

Thanks in advance

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

[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper

[Ken Vermette via KDE Bugzilla]

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

--- Comment #1 from Ken Vermette  ---
For reference we offer resolutions up to 3200x2000 right now.  4K has a
resolution of 3840x2160 being the consumer standard. There are some people out
there starting to float 8K (7680x4320 !!!) as a thing and while it sounds
ludicrous now, there was a time when 4K was crazy. But we also have to remember
some people have multiple monitors and may want to span their wallpapers across
multiple 4K monitors anyway. Really, I'd like a solution where we can
reasonably bundle 8K wallpapers as well to be future-proofed.

The main problem I think we're facing (and the push-back we'll see) is
filesize. Right now we're using PNG format images, and depending on complexity
the wallpapers have run filesizes between 10-30MB. A 4K wallpaper runs about
~3MB on its own (for skylight), a pretty big hit... But encoded in JPG at 98%
quality we halve it to 1.4MB, where I think 8K would become feasible too. Even
then, we can encode these ultra-high-def images at slightly lower qualities as
pixel-level compression artifacts becomes less visible on these screens.

There were issues with JPG and configuration hardcoding stuff, and because of
how we release software, we may need to wait a release or two for 4K/8K
wallpapers if we wait for JPG. I'll light some fires under people or try to get
some patches in to begin correcting this. Right now the way we distribute
wallpapers will cause size complaints if we include them as we do now; we need
to fix that first, I think.

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

[kdelibs] [Bug 324975] (regression) Volume gets restored to 100% after each knotify event

[Rex Dieter via KDE Bugzilla]

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

--- Comment #109 from Rex Dieter  ---
fedora includes the fixes referenced here, if you're still seeing similar
symptoms, the cause is (most likely) different.

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

[plasmashell] [Bug 361820] New: Random plasmashell crash

[via KDE Bugzilla]

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

Bug ID: 361820
   Summary: Random plasmashell crash
   Product: plasmashell
   Version: 5.6.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aaron.zakh...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.2)

Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.5.1-1.gf5f7dfc-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Had a Web browser open and was trying to add a shared wireless connection

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

Thread 9 (Thread 0x7fefbb015700 (LWP 2456)):
#0  0x7fefd0a475bf in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fefd0a32bb2 in poll () at /lib64/libc.so.6
#2  0x7fefcd11ae64 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fefcd11af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fefd13403fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fefd12ee04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fefd112a5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fefd20ab095 in  () at /usr/lib64/libQt5DBus.so.5
#8  0x7fefd112f079 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fefd023c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fefd0a3afed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fefb97d7700 (LWP 2461)):
#0  0x7fefd0a2ec8d in read () at /lib64/libc.so.6
#1  0x7fefcd15bb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fefcd11a999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fefcd11adf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fefcd11af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fefd13403fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fefd12ee04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fefd112a5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fefd44274d8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fefd112f079 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fefd023c0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fefd0a3afed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fefb13fc700 (LWP 2484)):
#0  0x7fefd024003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fefb27fa123 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7fefb27f9927 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7fefd023c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fefd0a3afed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fefa52d5700 (LWP 2498)):
#0  0x7fefcd15ccf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fefcd11a78e in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fefcd11adf8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fefcd11af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fefd13403fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fefd12ee04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fefd112a5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fefd44274d8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fefd112f079 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fefd023c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fefd0a3afed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fef9fa33700 (LWP 2507)):
#0  0x7fefd0a32bbd in poll () at /lib64/libc.so.6
#1  0x7fefcd11ae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fefcd11af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fefd13403fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fefd12ee04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fefd112a5da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fefd44274d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fefd112f079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fefd023c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fefd0a3afed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fef9e168700 (LWP 2579)):
#0  0x7fefd024003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fefd6c0997b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fefd6c099a9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fefd023c0a4 in start_thread () at 

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #13 from Tom Hughes  ---
I'm pretty sure that it's a bug in glibc that should be fixed anyway - you're
only supposed to call __libc_freeres when the process is exiting and in that
case there shouldn't be any need to rewind any descriptor if you discard the
buffer.

Of course there's an interesting issue here in that I suspect forking and
calling setvbuf() on a channel in the fork will have much the same effect on
the parent that you are sharing the descriptor with...

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

[krita] [Bug 361682] Internal error: sanityCheckAllJobsAreCancellable()

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/krit
   ||a/2063e1698fb12d053e1e404b1
   ||ebcb6abd9f43fed
 Resolution|--- |FIXED

--- Comment #2 from Dmitry Kazakov  ---
Git commit 2063e1698fb12d053e1e404b1ebcb6abd9f43fed by Dmitry Kazakov.
Committed on 15/04/2016 at 16:04.
Pushed by dkazakov into branch 'master'.

Fix an assert in KisStroke::cancelStroke()

LodN strokes can have an uncancellable jobs ('suspend'), and not
be started yet. This is a normal situation.

Fixes T2287

M  +10   -4libs/image/kis_stroke.cpp

http://commits.kde.org/krita/2063e1698fb12d053e1e404b1ebcb6abd9f43fed

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

[kdenlive] [Bug 361819] New: git 16.04: changing bin effect parameters does not mark project as changed

[via KDE Bugzilla]

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

Bug ID: 361819
   Summary: git 16.04: changing bin effect parameters does not
mark project as changed
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: wegwerf-1-...@gmx.de

When changing the parameters of a bin effect the project does not get marked as
changed and the Save button does not get enabled. The project thus cannot be
saved using ^S or File>Save until another change is made that correctly sets
the project as "dirty".

Reproducible: Always

Steps to Reproduce:
1. Start new project, such as FullHD 25fps.
2. Add clip to project bin.
3. Add effect, such as Bézier Curves to the clip in the project bin.
4. Save project.
5. Edit Bézier Curves effect of project bin clip.

Actual Results:  
Albeit parameters have been changed, the project has not been marked as
changed; Save button doesn't get enabled.

Expected Results:  
Project should be marked as changed so that the Save button gets enabled.

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #12 from Mark Wielaard  ---
Maybe --child-silent-after-fork=yes should imply run-libc-freeres=no for
the fork? As I understand correctly the output sink is set to -1 for the fork
already, so there cannot be any output. So running __libc_freeres is not very
useful anyway (and we wouldn't do that if the forked child would call exec in
the first place).

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #11 from Tom Hughes  ---
See http://valgrind.org/docs/manual/faq.html#faq.exit_errors for more
information.

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #10 from Tom Hughes  ---
The call to __libc_freeres is not normally made at all - it is forced by
valgrind (unless you use that switch) so that people won't moan about "still
reachable" blocks of memory in the leak report due to glibc still having stuff
allocated.

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Richard Jones via KDE Bugzilla]

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

--- Comment #9 from Richard Jones  ---
(In reply to Tom Hughes from comment #6)
> It's something in glibc doing it when __libc_freeres is run as the child
> exits.
> 
> If you add run-libc-freeres=no to the valgrind options then it doesn't
> happen.

The child calls _exit on every return path, so surely no libc functions should
be called?

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

[plasmashell] [Bug 361818] New: Plasma crash after KDE partition manager partitioning of USB stick

[via KDE Bugzilla]

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

Bug ID: 361818
   Summary: Plasma crash after KDE partition manager partitioning
of USB stick
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jwi...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

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

-- Information about the crash:
- What I was doing when the application crashed:  Seems similar/identical to
350301 but I cannot figure out how to actually report that.  The "+suggest this
is similar report (or whatever) button seems to do nothing only leading to an
endless loop. 
SO... Partitioned USB stick using KDE partition manager, Baloo crashed then
Plasma immediately reported as crash.  Both seemed to restart.
Good luck with this.  This reporting method is very unclear to me, a noob, but
seriously, many buttons or options that don't seem to actually do anthing.

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

Thread 16 (Thread 0x7f954d25a700 (LWP 974)):
#0  0x7f955c3b288d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f95603f9bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f95603fb74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f954f5a4a39 in QXcbEventReader::run (this=0x11f88a0) at
qxcbconnection.cpp:1105
#4  0x7f955caa52be in QThreadPrivate::start (arg=0x11f88a0) at
thread/qthread_unix.cpp:337
#5  0x7f955bb946aa in start_thread (arg=0x7f954d25a700) at
pthread_create.c:333
#6  0x7f955c3bde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f9546b48700 (LWP 1013)):
#0  0x7f955915ed6f in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f955915f250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f955915f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f955ccdc29b in QEventDispatcherGlib::processEvents
(this=0x7f9548c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f955cc8275a in QEventLoop::exec (this=this@entry=0x7f9546b47da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f955caa03d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f955f2c8f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f955caa52be in QThreadPrivate::start (arg=0x12b78d0) at
thread/qthread_unix.cpp:337
#8  0x7f955bb946aa in start_thread (arg=0x7f9546b48700) at
pthread_create.c:333
#9  0x7f955c3bde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f953b792700 (LWP 1016)):
#0  0x7f95591a3869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f955915e789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f955915f11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f955915f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f955ccdc29b in QEventDispatcherGlib::processEvents
(this=0x7f95340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f955cc8275a in QEventLoop::exec (this=this@entry=0x7f953b791da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f955caa03d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f955f2c8f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f955caa52be in QThreadPrivate::start (arg=0x15dcf70) at
thread/qthread_unix.cpp:337
#9  0x7f955bb946aa in start_thread (arg=0x7f953b792700) at
pthread_create.c:333
#10 0x7f955c3bde9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f9538f52700 (LWP 1020)):
#0  0x7f955c3ae44d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f95591a24e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f955915ecd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f955915f190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f955915f2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f955ccdc29b in QEventDispatcherGlib::processEvents
(this=0x7f9538c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f955cc8275a in QEventLoop::exec (this=this@entry=0x7f9538f51da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f955caa03d4 in QThread::exec (this=) at

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #6 from Tom Hughes  ---
It's something in glibc doing it when __libc_freeres is run as the child exits.

If you add run-libc-freeres=no to the valgrind options then it doesn't
happen.

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

[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #4 from Boudewijn Rempt  ---
I'm sorry, but no. If people really want something else than fusion, they can
patch Krita, but they aren't allowed to report bugs anymore.

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

[krita] [Bug 361813] Wacom CTL-460/Intuos Pro Small+Krita 2.9.11: Stylus Side Buttons Not Working with Click-Based Shortcuts

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
  Component|general |tablet support

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

[Baloo] [Bug 361817] New: Baloo crashe during KDE partition manager partitioning USB stick

[via KDE Bugzilla]

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

Bug ID: 361817
   Summary: Baloo crashe during KDE partition manager partitioning
USB stick
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: jwi...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.15.0)

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

-- Information about the crash:
- What I was doing when the application crashed:  Applying new file system to
USB stick using KDE partition manager.  Baloo reported crash while indexing new
incomplete file system.  Note that this bug reporting system is a very obtuse
process, not really sure if this will be relevant information.  This crash
seems similar to two others yet the method of 'attaching' this report to that
similar bug seems impossible to execute only leading to an endless loop of
select, +suggest similar then go back??? good luck.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f109e178267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f109e179eca in __GI_abort () at abort.c:89
#8  0x7f109ec26c88 in qt_message_fatal (context=..., message=...) at
global/qlogging.cpp:1422
#9  QMessageLogger::fatal (this=this@entry=0x7fff044de9c0,
msg=msg@entry=0x7f10a025ced8 "Cannot construct placeholder type QDBusRawType")
at global/qlogging.cpp:643
#10 0x7f10a02374e2 in QDBusRawTypeHandler::construct () at
qdbusmetaobject.cpp:144
#11 0x7f109ee5b1e8 in QMetaType::construct (copy=0x0, where=0x7fff044deae0,
this=0x7fff044dea20) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:2018
#12 (anonymous namespace)::customConstruct (d=0x7fff044deae0, copy=0x0) at
kernel/qvariant.cpp:865
#13 0x7f109ee5b6ef in QVariant::QVariant (this=0x7fff044deae0,
typeId=, copy=) at kernel/qvariant.cpp:1498
#14 0x7f109ee258df in QMetaProperty::read (this=this@entry=0x7fff044deb80,
object=object@entry=0x247d920) at kernel/qmetaobject.cpp:2861
#15 0x7f109ee4832f in QObject::property (this=0x247d920, name=0x26de5f8
"MountPoints") at kernel/qobject.cpp:3897
#16 0x7f109fe1b054 in Solid::Backends::UDisks2::DeviceBackend::checkCache
(this=0x15071a0, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185
#17 0x7f109fe1b273 in
Solid::Backends::UDisks2::DeviceBackend::propertyExists (this=0x15071a0,
key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132
#18 0x7f109fe12e6e in Solid::Backends::UDisks2::Device::propertyExists
(this=this@entry=0x1e77750, key=...) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:126
#19 0x7f109fe14c2f in Solid::Backends::UDisks2::Device::isMounted
(this=0x1e77750) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:818
#20 0x7f109fe2e371 in Solid::Backends::UDisks2::StorageAccess::isAccessible
(this=0x1510d10) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:75
#21 0x7f109fe2e5a4 in Solid::Backends::UDisks2::StorageAccess::updateCache
(this=0x1510d10) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:138
#22 Solid::Backends::UDisks2::StorageAccess::StorageAccess (this=0x1510d10,
device=0x1e77750, __in_chrg=, __vtt_parm=) at
../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:36
#23 0x7f109fe13030 in
Solid::Backends::UDisks2::Device::createDeviceInterface (this=0x1e77750,
type=) at
../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:174
#24 0x7f109fddc26f in Solid::Device::asDeviceInterface
(this=this@entry=0x7fff044deed0, type=@0x7fff044dee70:
Solid::DeviceInterface::StorageAccess) at
../../../src/solid/devices/frontend/device.cpp:154
#25 0x004221a9 in Solid::Device::as
(this=0x7fff044deed0) at /usr/include/KF5/Solid/solid/device.h:247
#26 Baloo::StorageDevices::createCacheEntry (this=this@entry=0x144ee50,
dev=...) at ../../../src/file/storagedevices.cpp:79
#27 0x004223f9 in Baloo::StorageDevices::slotSolidDeviceAdded
(this=0x144ee50, udi=...) at ../../../src/file/storagedevices.cpp:96
#28 0x7f109ee4978a in QMetaObject::activate (sender=0x1450310,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff044df030) at kernel/qobject.cpp:3717
#29 0x7f109ee49f87 in QMetaObject::activate (sender=,
m=m@entry=0x7f10a006aee0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff044df030)
at kernel/qobject.cpp:3582
#30 0x7f109fddc792 in Solid::DeviceNotifier::deviceAdded (this=, _t1=...) at 

[kmail2] [Bug 358679] kmail5 crash on reload when config to empty trash on exit

[Ian via KDE Bugzilla]

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

--- Comment #6 from Ian  ---
(In reply to Laurent Montel from comment #5)
> backtrace please as it's too different bug as first comment
> Thanks

It doesn;t crash in a way that i can get a back trace any more so i guess the
failure is different.  if i reload kmail, it shows it is loading on the taskbar
then it disappears and nothing happens.  if i call up System Activity with
ctrl-esc, and filter the display by inputting kmail, it shows kmail is still
loaded with 5 copies of "file.so" under kdeinit5.  if i kill kmail via
SystemActivity, i can then successfully reload kmail but the wastebin is still
not emptied

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #8 from Tom Hughes  ---
Of course the buffer isn't really shared (this is fork, not threads...) but the
file position is.

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #7 from Tom Hughes  ---
I think the problem is that __libc_freeres calls (among many other things) the
_IO_unbuffer_write to free the buffers for stdio streams.

That "unbuffers" each file by calling _IO_SETBUF (fp, NULL, 0) to drop the
buffer, but that (which is just the internal implementation of setbuf/setvbuf)
rewinds the stream over any data which has been read into the buffer but not
yet consumed.

Of course when the buffer is shared between multiple processes the question of
what has been consumed is something of an open one...

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

[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut

[vpiotr via KDE Bugzilla]

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

--- Comment #14 from vpiotr  ---
This also happens when "present windows" is triggered via a screen corner.

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

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

[via KDE Bugzilla]

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

franz.berges...@gmail.com changed:

   What|Removed |Added

 CC||franz.berges...@gmail.com

--- Comment #1 from franz.berges...@gmail.com ---
I have the same problem on openSUSE Tumbleweed (20160412) (x86_64) with
Qt: 5.5.1
KDE Frameworks: 5.21.0

~> kcmshell5 kcm_fileindexer
Error loading plugin "kcm_fileindexermonitor" "The shared library was not
found." 
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
fetched suspend state
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
KInit could not launch 'khelpcenter5'.

~>

The File Indexer Monitor is fired up, but show only some button, as shown in
the attachment.

A "File Indexer Monitor" app is visible both in the application dashboard and
krunner, but nothing happens.
The "File Indexer Monitor" in KInfoCenter freezes the GUI for about a minute
before showing it and there what it looks like a progress bar, but I'm not sure
it makes sense, given the issues just described

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

--- Comment #5 from Tom Hughes  ---
Ah, if you add the childs you will see each one do:

3992  lseek(0, -8, SEEK_CUR)= 4

for some reason...

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

[plasma-nm] [Bug 361808] plasma-nm crashes Plasma upon switching WiFI network

[via KDE Bugzilla]

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

--- Comment #2 from madc...@atlas.cz ---
Updated backtrace with debugging symbols installed for plasma-nm and
networkmanager-qt

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

Thread 10 (Thread 0x7f00edf60700 (LWP 891)):
#0  0x7f00fe6ebc3d in poll () from /usr/lib/libc.so.6
#1  0x7f01036ecae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f01036ee757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f00ef882a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f00e7fff700 (LWP 895)):
#0  0x7f00fe6ebc3d in poll () from /usr/lib/libc.so.6
#1  0x7f00fab6c0fc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f00fab6c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f00ff003cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f00fefac6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f00ffd96a55 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f00e69c8700 (LWP 908)):
#0  0x7f00fabb0879 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7f00fab6b090 in g_main_context_acquire () from
/usr/lib/libglib-2.0.so.0
#2  0x7f00fab6bfb5 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f00fab6c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f00ff003cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f00fefac6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5
#8  0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f00dd4a1700 (LWP 919)):
#0  0x7f00fab6b708 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7f00fab6c02b in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f00fab6c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f00ff003cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f00fefac6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f00d3848700 (LWP 923)):
#0  0x7f00fe6e7c0d in read () from /usr/lib/libc.so.6
#1  0x7f00fabaf4f0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f00fab6bbe4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f00fab6c0a0 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f00fab6c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f00ff003cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f00fefac6fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5
#9  0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f00d1f40700 (LWP 938)):
#0  0x7f00fdef403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f01049d5134 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f01049d5179 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f004b20e700 (LWP 943)):
#0  0x7f00fabaf4d2 in ?? () from /usr/lib/libglib-2.0.so.0
#1  0x7f00fab6bbe4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#2  0x7f00fab6c0a0 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f00fab6c20c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f00ff003cab in
QEventDispatcherGlib::processEvents(QFlags) ()
from 

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Tom Hughes via KDE Bugzilla]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #4 from Tom Hughes  ---
Frankly it makes no sense at all. Here's an strace of that valgrind, from the
first read on fd 0 to the second:

read(0, "abc\ndef\nghi\n", 4096)= 12
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "J", 1)  = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3115
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
gettid()= 3114
write(1029, "K", 1) = 1
sched_yield()   = 0
gettid()= 3114
read(1028, "K", 1)  = 1
close(5)= 0
gettid()= 3114
write(1029, "L", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
read(4, "\2\0\0\0", 4)  = 4
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "L", 1)  = 1
close(4)= 0
gettid()= 3114
write(1029, "M", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
wait4(3115, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3115
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3115, si_uid=2067,
si_status=0, si_utime=1, si_stime=0} ---
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "M", 1)  = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(0x60224000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x60224000
gettid()= 3114
write(1029, "N", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
write(1, "mask 2 buf abc\n", 15)= 15
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "N", 1)  = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3116
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
gettid()= 3114
write(1029, "O", 1) = 1
sched_yield()   = 0
gettid()= 3114
read(1028, "O", 1)  = 1
close(5)= 0
gettid()= 3114
write(1029, "P", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
read(4, "\2\0\0\0", 4)  = 4
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "P", 1)  = 1
close(4)= 0
gettid()= 3114
write(1029, "Q", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
wait4(3116, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3116
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3116, si_uid=2067,
si_status=0, si_utime=1, si_stime=0} ---
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "Q", 1)  = 1
gettid()= 3114
write(1029, "R", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
write(1, "mask 2 buf def\n", 15)= 15
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "R", 1)  = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3117
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL 

[zanshin] [Bug 357130] Not able to enable or add todo collection (existing (sub)calendar on ownCloud server)

[Kevin Ottens via KDE Bugzilla]

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

--- Comment #3 from Kevin Ottens  ---
Right, adding collections is a different thing and not supported yet. Clearly a
missing feature (I'm not reopening just because it's tracked on our roadmap,
it'll appear at some point and I'd like this report to be more about the
enable/disable issue you had initially).

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

[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #13 from Thomas Lübking  ---
Might have relation to bug #351112
The question is whether the keyboard grab fails after randr events or it is
released afterwards.

Does this also happen if you trigger present windows via a screen corner (run
"kcmshell5 kwinscreenedges" for configuration)?

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

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Richard Jones via KDE Bugzilla]

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

--- Comment #3 from Richard Jones  ---
For reference here is the actual test that fails for us:

https://github.com/libguestfs/libguestfs/blob/master/fish/test-find0.sh#L25-L30

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

[akregator] [Bug 361816] New: Akregator crashes at the begining

[Juanmi via KDE Bugzilla]

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

Bug ID: 361816
   Summary: Akregator crashes at the begining
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: saldi...@yahoo.es

Application: akregator (4.14.10)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e2df1d800 (LWP 3885))]

Thread 11 (Thread 0x7f5e0c1a8700 (LWP 3896)):
#0  0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e13070eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f5e13070ee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f5dcac5b700 (LWP 3899)):
#0  0x7f5e2a9e6c8d in read () at /lib64/libc.so.6
#1  0x7f5e252fdb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5e252bc999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5e252bcdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f5e252bcf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f5e2c33bfde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7f5e2c30dd4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f5e2c30e045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7f5e2c20b4df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7f5e2c20dbbf in  () at /usr/lib64/libQtCore.so.4
#10 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f5dc96bd700 (LWP 3930)):
#0  0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e12de3b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f5e13098a06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f5dc3fff700 (LWP 3955)):
#0  0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f5e2c201bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7f5e2c20dbbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f5dc37fe700 (LWP 3956)):
#0  0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f5e2c201bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7f5e2c20dbbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f5dc2ffd700 (LWP 3957)):
#0  0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f5e2c201bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7f5e2c20dbbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f5dc27fc700 (LWP 3958)):
#0  0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQtCore.so.4
#2  0x7f5e2c201bda in  () at /usr/lib64/libQtCore.so.4
#3  0x7f5e2c20dbbf in  () at /usr/lib64/libQtCore.so.4
#4  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5e2a9f2fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f5d9dd9e700 (LWP 3973)):
#0  0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5d9de05d79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f5d9de06819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f5e2a9f2fed in clone () at 

[plasmashell] [Bug 361815] New: Plasma shell crashed while repositioning plasmoid underneath existing window

[Michael Mol via KDE Bugzilla]

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

Bug ID: 361815
   Summary: Plasma shell crashed while repositioning plasmoid
underneath existing window
   Product: plasmashell
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mike...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.1.15-gentoo-r1 x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
Attempting to move plasmoid from upper right corner of desktop to lower left
corner. There happened to be a window between the source and destination
points.

- Unusual behavior I noticed:

I have three displays. I tried moving a plasmoid from the leftmost display to
the rightmost display, and it disappeared, though the plasmoid counter
indicated it was still...somewhere.

Also, for the life of me, I cannot seem to get a panel to *stay* on the right
edge of this rightmost display. Log out and back in, and it reappears on the
right edge of my leftmost display.

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

Thread 34 (Thread 0x7f25da3f5700 (LWP 31133)):
#0  0x7f25ef3c411d in read () from /lib64/libc.so.6
#1  0x7f25eb4a6550 in g_wakeup_acknowledge () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f25eb46399c in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f25eb463e90 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f25eb463ffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f25efc2a66c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f25efbdc22a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f25f2234695 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#9  0x7f25efa32e92 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0
#11 0x7f25ef3d112d in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f25d0e36700 (LWP 31172)):
#0  0x7f25efa2bd82 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1  0x7f25efc2a3eb in postEventSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f25eb4638f1 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f25eb463e90 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f25eb463ffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f25efc2a66c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f25efbdc22a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f25f2234695 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#9  0x7f25efa32e92 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0
#11 0x7f25ef3d112d in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f25cad92700 (LWP 31173)):
#0  0x7f25efc2a3c3 in postEventSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#1  0x7f25eb46342d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f25eb463e18 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f25eb463ffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f25efc2a66c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f25efbdc22a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f25f2234695 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f25efa32e92 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0
#10 0x7f25ef3d112d in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f25c943e700 (LWP 31177)):
#0  0x7f25eebd700f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f25f461e6e4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7f25f461e729 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /usr/lib64/libQt5Script.so.5
#3  

[valgrind] [Bug 361810] valgrind duplicate stdin after fork

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@redhat.com

--- Comment #2 from Mark Wielaard  ---
I can replicate this, but only with redirected input, like in the shell script
or when putting the input in a file and running with valgrind ./forktest <
input_file. When stdin isn't redirected from some (here) file, but comes direct
or through a pipe (cat input | valgrind ./forktest) it works as intended.

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