[plasmashell] [Bug 369221] New: ERROR

[AlexURS via KDE Bugzilla]

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

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

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- Unusual behavior I noticed:
эта ошибка всегда возникает когда система бездействует

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7f1f6f13e700 (LWP 3943)):
#0  0x7f2049778210 in pa_mutex_unlock () at
/usr/lib64/pulseaudio/libpulsecommon-7.0.so
#1  0x7f2049de07c3 in  () at /usr/lib64/libpulse.so.0
#2  0x7f2049dd1f0c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7f2049dd257e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f2049dd2630 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f2049de0783 in  () at /usr/lib64/libpulse.so.0
#6  0x7f2049778f98 in  () at /usr/lib64/pulseaudio/libpulsecommon-7.0.so
#7  0x7f205326d0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f2053a6c02d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f1f806d4700 (LWP 3826)):
#0  0x7f2053a5fccd in read () at /lib64/libc.so.6
#1  0x7f204974bdf1 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-7.0.so
#2  0x7f2049dd1b5e in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f2049dd2572 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f2049dd2630 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f2049de0783 in  () at /usr/lib64/libpulse.so.0
#6  0x7f2049778f98 in  () at /usr/lib64/pulseaudio/libpulsecommon-7.0.so
#7  0x7f205326d0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f2053a6c02d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f1f917f2700 (LWP 29648)):
#0  0x7fff17df8d35 in clock_gettime ()
#1  0x7f2053a78c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f205420f7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f205438f3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f205438f945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f205439170c in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f20501404ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f2050140d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f2050140f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f2054390d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f2054337d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f205415961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f1f92e3ecf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#13 0x7f205415e32f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f205326d0a4 in start_thread () at /lib64/libpthread.so.0
#15 0x7f2053a6c02d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f2025f91700 (LWP 29642)):
#0  0x7f2053a785ff in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f2053a63bf2 in poll () at /lib64/libc.so.6
#2  0x7f2050140e64 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f2050140f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f2054390d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f2054337d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f205415961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f2058009282 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f205415e32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f205326d0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f2053a6c02d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f202cce6700 (LWP 29641)):
#0  0x7f205327103f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2059c3c86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f2059c3c899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f205326d0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2053a6c02d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f202e56e700 (LWP 29640)):
#0  0x7f205013e1c9 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f205014044b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f2050140d80 in  () 

[kwin] [Bug 369220] New: KWin sometimes crashes

[Carl's Son via KDE Bugzilla]

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

Bug ID: 369220
   Summary: KWin sometimes crashes
   Product: kwin
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: uvladi...@ukr.net

Application: kwin_x11 (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-rc7-Cartoon x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- Custom settings of the application:

Compozitor: OpenGL 3.1, Full screen repaints

Desktop Effects: Zoom, Background contrast, Blur, Fade, Glide, Login, Logout,
Maximize, [Morphing popups], Scale In, Sheet, [Sliding popups], Translucency,
Minimize Animation, Dialog Parent, Desktop Cube Animation, Desktop Grid,
Present Windows

Activities: 4

Virtual Desktops: 4

Desktop Theme: Maia Transparent

Window Decorations: Yosemite Transparent

KWin Scripts: Enforces Window Decorations on GTK+ window, Remember Last Desktop
Per Activity

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7f91ab5ef700 (LWP 1544)):
#0  0x7f91c91b91c3 in select () at /lib64/libc.so.6
#1  0x7f91c9fb96df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f91c9fbadd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f91c9fbb30a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f91c9f6c5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f91c9dcb343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f91d0f2f8f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f91c9dcf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f91cc0495ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f91c91c2f6d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f919d278700 (LWP 1312)):
#0  0x7f91cc04ebd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f91d1cdabc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f91d1cdac09 in  () at /lib64/libQt5Script.so.5
#3  0x7f91cc0495ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f91c91c2f6d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f91aa497700 (LWP 1299)):
#0  0x7f91c91b91c3 in select () at /lib64/libc.so.6
#1  0x7f91c9fb96df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f91c9fbadd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f91c9fbb30a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f91c9f6c5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f91c9dcb343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f91d0f2f8f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f91c9dcf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f91cc0495ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f91c91c2f6d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f91b0d16700 (LWP 1279)):
#0  0x7f91c91b91c3 in select () at /lib64/libc.so.6
#1  0x7f91c9fb96df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /lib64/libQt5Core.so.5
#2  0x7f91c9fbadd4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /lib64/libQt5Core.so.5
#3  0x7f91c9fbb30a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f91c9f6c5ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f91c9dcb343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f91cbb46559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f91c9dcf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f91cc0495ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f91c91c2f6d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f91b23d8700 (LWP 1278)):
#0  0x7f91c91b73ed in poll () at /lib64/libc.so.6
#1  0x7f91cb918f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f91cb91ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f91b30aeda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f91c9dcf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f91cc0495ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f91c91c2f6d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f91ba0de940 

[kinfocenter] [Bug 369219] New: Info Center crashed after unlocking screen and switching from Wayland info section to OpenGL info section

[via KDE Bugzilla]

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

Bug ID: 369219
   Summary: Info Center crashed after unlocking screen and
switching from Wayland info section to OpenGL info
section
   Product: kinfocenter
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: drlo...@gmail.com

Application: kinfocenter (5.7.4)

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

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

I opened the application Info Center and read several sections until I reched
the Wayland section. Left the computer alone for a few minutes. When I
returned, I unlocked the automatick lock screen and continued to read the
Wayland information section, then I switched to the OpenGL information section
when sudenly the application Info Center crashed.

-- Backtrace:
Application: Info Center (kinfocenter), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b108d1e00 (LWP 23315))]

Thread 9 (Thread 0x7f3ae1389700 (LWP 23354)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f3adbfff700 (LWP 23353)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f3adaffd700 (LWP 23326)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f3adb7fe700 (LWP 23325)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f3ae2a1f700 (LWP 23319)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f3ae3220700 (LWP 23318)):
#0  0x7f3b09a6810f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3aea5a6653 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f3aea5a64b7 in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f3af4cd0700 (LWP 23317)):
#0  0x7f3b0d2dc6ed in poll () from /lib64/libc.so.6
#1  0x7f3b09028016 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3b0902812c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3b0dc04aab in QEventDispatcherGlib::processEvents
(this=0x7f3af8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f3b0dbac6fa in QEventLoop::exec (this=this@entry=0x7f3af4ccfcd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f3b0d9d23c3 in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f3b0bb1d985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f3b0d9d72e8 in QThreadPrivate::start (arg=0x7f3b0bd90d20) at
thread/qthread_unix.cpp:341
#8  0x7f3b09a62454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3b0d2e53ff in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f3afd045700 (LWP 23316)):
#0  0x7f3b0d2dc6ed in poll () from /lib64/libc.so.6
#1  0x7f3b0630e3f0 in poll (__timeout=-1, __nfds=1, __fds=0x7f3afd044c00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x165cdf0, cond=cond@entry=0x165ce30,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:479
#3  0x7f3b06310189 in 

[frameworks-plasma] [Bug 369218] New: Icon location on Desktop is not kept during reboot / shutdown

[Jón Frímann via KDE Bugzilla]

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

Bug ID: 369218
   Summary: Icon location on Desktop is not kept during reboot /
shutdown
   Product: frameworks-plasma
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libplasma
  Assignee: notm...@gmail.com
  Reporter: jonfr1...@jonfr.com

For some reason kde 5.7.4 does not save or honour the icon location on desktop
after a reboot or a shutdown. Icons are moving around in random order along the
desktop space. Locking them down does not work, this bug is also present in
earlier versions of KDE Plasma 5. This bug is annoying and was not present in
KDE Plasma 4 (at least the latest version that I was using). I don't like to
use the folder view in KDE Plasma 5, since I find it difficult to use.

Reproducible: Sometimes

Steps to Reproduce:
1. Arrange icons on Desktop in special order. 
2. Shut down computer for a while. 
3. Power it up, there is a good chance icons are not where you placed them.
This should not happen.

Actual Results:  
Icons move around the desktop in random order after a shutdown or reboot. More
common if the reboot or shutdown doesn't go as planned or the computer has been
off-line for a few hours.

Expected Results:  
Icons to be in the place where I put them on the desktop.

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

[krita] [Bug 369217] New: G'mic Colorize[interactive] crashes

[via KDE Bugzilla]

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

Bug ID: 369217
   Summary: G'mic Colorize[interactive] crashes
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: katearche...@yandex.ru

When I chose Colorize[interactive] in g'mic filters it crashes with a message:
"Sorry! G'Mic failed, reason:*** Error in
./gimp_colorize_interactive/*if/*repeat/*substitute/ *** Command '-x_colorize':
No display available." . It shows same message with any of the parameters of
the filter chosen and this is specific to 3.0.1, colorize[interactive] in 3.0
works fine(slow on big images, it can takes up to fice-six minutes to complete
the calculations, but fine).

Reproducible: Always

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

[plasmashell] [Bug 369214] Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on.

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #41 from Leslie Zhai  ---
Git commit 076340502f14a5ecd928551500392e5f38dd2c41 by Leslie Zhai.
Committed on 23/09/2016 at 02:35.
Pushed by lesliezhai into branch 'multisession'.

Fix multisession implementation as Thomas suggested

Summary:
- Use device driver's path instead of stdin
- Stay module DataMultiSessionParameterJob so CdrskinIsoImager can use
that
- Throw error info message to user

M  +1-0libk3b/projects/datacd/k3bdatajob.cpp
M  +30   -0libk3b/projects/datacd/k3bdatamultisessionparameterjob.cpp
M  +0-41   libk3b/projects/datacd/k3bisoimager.cpp
M  +8-2libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/076340502f14a5ecd928551500392e5f38dd2c41

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

[kdialog] [Bug 369216] New: kdialog path parsing regression

[Paul via KDE Bugzilla]

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

Bug ID: 369216
   Summary: kdialog path parsing regression
   Product: kdialog
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: holle...@cs.dal.ca

kdialog --getsavefilename /path/to/newfile.ext
no longer starts in the supplied directory, but always uses a default (for me
~/Documents)
kdialog --getsavefilename file:///path/to/newfile.ext
still works, but chromium is not that smart.
This regression resulted from the recent commit REVIEW:128639
Code which prepended "file://" to the path was removed as it is not
cross-platform.
I believe QUrl::fromUserInput is doing the right thing, so I'm not sure where
it breaks.


Reproducible: Always

Steps to Reproduce:
1. kdialog --getsavefilename /path/to/newfile.ext
2.
3.

Actual Results:  
Dialog starts in ~/Documents

Expected Results:  
Dialog starts in /path/to

kdialog master, KDE frameworks 5.26, Qt 5.7, ArchLinux.

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

[krunner] [Bug 369215] New: krunner crashed while unsucessfully trying to start iceweasel

[Arthur Marsh via KDE Bugzilla]

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

Bug ID: 369215
   Summary: krunner crashed while unsucessfully trying to start
iceweasel
   Product: krunner
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: arthur.ma...@internode.on.net

Application: krunner (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.8.0-rc7+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I put machine into single user mode and returned to multi-user mode and started
plasma desktop, then used alt-F2 to attempt to start iceweasel but krunner
crashed without starting iceweasel.

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fe11c48d7c0 (LWP 31588))]

Thread 13 (Thread 0x7fe0f9ffb700 (LWP 31784)):
#0  0x003000c0d18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003011caec3b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x003105e13da0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x003105e17fc8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x003105e18022 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x003105e15de9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x003011cadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x003000c07464 in start_thread (arg=0x7fe0f9ffb700) at
pthread_create.c:333
#10 0x0030004e897f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 12 (Thread 0x7fe0fa7fc700 (LWP 31783)):
#0  0x003000c0d18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003011caec3b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x003105e13da0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x003105e17fc8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x003105e18022 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x003105e15de9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x003011cadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x003000c07464 in start_thread (arg=0x7fe0fa7fc700) at
pthread_create.c:333
#10 0x0030004e897f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 11 (Thread 0x7fe0faffd700 (LWP 31782)):
#0  0x003000c0d18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003011caec3b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x003105e13da0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x003105e17fc8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x003105e18022 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x003105e12f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x003105e15de9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x003011cadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x003000c07464 in start_thread (arg=0x7fe0faffd700) at

[plasmashell] [Bug 368018] Panels do not adapt to the screen size without restart

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
This should be fixed now, please reopen if not.

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

[plasmashell] [Bug 368080] KInfoCenter is not included in the Computer Tab

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from David Edmundson  ---
I say yes.

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

[plasmashell] [Bug 369214] New: Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on.

[Tony via KDE Bugzilla]

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

Bug ID: 369214
   Summary: Keyboard "Lock" keys (Caps/Num/Scroll) leds not
turning on.
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: jodr...@live.com

On wayland the leds for "Lock" keys (Caps/Num/Scroll) are always off. In the
case of Num Lock, the option to turn it on on plasma startup is not being
honored either.

I have one of the "supported" keyboards DELL SK-8135, and none of this happens
on X.

Reproducible: Always

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

[plasmashell] [Bug 369100] Dark theme affects aspects of applications that it should not

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from David Edmundson  ---
You might find 

unsett XDG_CURRENT_DESKTOP

will force it to not try and load any KDE settings and hopefully fix it.

Other than that I'm afraid we can't do much. Sorry.

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

[plasmashell] [Bug 346602] Application Launcher (Kickoff) not filtering search results from system settings

[Jesse via KDE Bugzilla]

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

--- Comment #16 from Jesse  ---
Haha, you all have a lot on your plate -- it's completely understandable. :)

The config option you mentioned does help in giving the user more lee-way
towards choosing what they want to show, and that's definitely closer to the
desired outcome. Are you saying that when this is selected, it uses Kickoff's
filter results in the Plasma Search section of the System Settings?

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

[kwin] [Bug 369213] When i turn on my PC KDE Plasma 5 panel isn't transparent

[Víctor via KDE Bugzilla]

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

Víctor  changed:

   What|Removed |Added

 CC||vmorenoma...@gmail.com

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

[kwin] [Bug 369213] New: When i turn on my PC KDE Plasma 5 panel isn't transparent

[Víctor via KDE Bugzilla]

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

Bug ID: 369213
   Summary: When i turn on my PC KDE Plasma 5 panel isn't
transparent
   Product: kwin
   Version: 5.7.5
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: vmorenoma...@gmail.com

When I turn on my PC KDE Plasma 5 panel isn't transparent - I have enabled
Compostitor, but my panel and the others widgets have solid background without
transparency. Other desktop effects works without problems. I can fix this
problem always with the command kwin_x11 --replace. After this command, the
transparency in the Desktop theme returns as must be after the user login. 

Reproducible: Always

Steps to Reproduce:
1. Turn on pc
2. Login the user in Plasma session
3. There is not transparency in the Desktop theme. Neither Panel or widgets,
only a color solid. 
4. The compositor are initialised because the other effects work fine.
5. Run kwin_x11 --replace on Krunner (or console)
6. Transparency in panel returns.

Actual Results:  
There is not transparency in desktop theme every time that turn on my pc.
The transparency return always when I run the command kwin_x11 --replace.

Expected Results:  
I expect transparency immediately start the desktop session, without
reinitialise the compositor or restarts kwin.

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

[plasmashell] [Bug 346602] Application Launcher (Kickoff) not filtering search results from system settings

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #15 from David Edmundson  ---
Edit: The config option "Expand search to bookmarks, files and emails" is
present in Kickoff

Don't know how I forgot. I was the one who added it.

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

[plasmashell] [Bug 346602] Application Launcher (Kickoff) not filtering search results from system settings

[Jesse via KDE Bugzilla]

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

--- Comment #14 from Jesse  ---
Appreciate the reply David. Even if the Plasma search section in the System
Settings isn't deemed the best place for Kickoff's filter settings, just having
them available somewhere would be fantastic. It's a huge benefit to be able to
filter the search results in the application menu and the application
dashboard, like Kicker is able to.

What you're proposing sounds awesome. Appreciate your consideration on this
matter! Let me know if there's something I can test, specifically, when the
changes become available for testing.

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

[plasmashell] [Bug 346602] Application Launcher (Kickoff) not filtering search results from system settings

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #13 from David Edmundson  ---
The "bug" will be present.

Kickoff does not use the filters set in that systemsettings module.

This is partly deliberate, as we want to enforce a subset of krunner's plugins
as they don't all make sense here.

Kicker (Application Menu) has a config option for toggling bookmarks, files and
emails.
(which from the sounds of it is what you want)

Kickoff (Application Launcher) shares the hidden config option "runners" that
can be manually set.
 default is shell,bookmarks,recentdocuments,locations,baloosearch 

but it has no UI facing option.

I'll sync the config option that kicker has to kickoff's UI.

Then we need to change the KCM so that it's clearer as to what it actually
affects.

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

[dolphin] [Bug 369212] New: "Open Terminal Here" menu item is not displayed

[resplin via KDE Bugzilla]

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

Bug ID: 369212
   Summary: "Open Terminal Here" menu item is not displayed
   Product: dolphin
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: richard-...@esplins.org

When right clicking in the file area, the "Open Terminal Here" menu is not
displayed.

Reproducible: Always

Steps to Reproduce:
1. Check the configuration setting: Control -> Configure Dolphin -> Service ->
Open Terminal Here
2. Close the dialog with "OK", then close and re-open Dolphin
3. Browse somewhere, right click on the folder view

Actual Results:  
* The menu option does not appear

Expected Results:  
* One of the menu options should say "Open Terminal Here".
* Selecting the option will open a terminal in a new window, with the
terminal's current directory being the same as the directory Dolphin is
viewing.

Notes:
* Shift-F4 correctly opens a terminal in the current directory.
* Control -> Tools -> Terminal correctly opens a terminal in the current
directory.

Environment:
* Fedora 24, Version 16.08.1
* Someone else also reproduced it on openSUSE 42.1

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

[kdenlive] [Bug 369211] New: git master - change "loading playlist" text to "Loading Project".

[Jesse via KDE Bugzilla]

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

Bug ID: 369211
   Summary: git master - change "loading playlist" text to
"Loading Project".
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

Just a small thing I noticed: after you choose your .kdenlive project file to
open in the "Open Recent" menu section, a window comes up that says "loading
playlist". I think this can be confusing to users, since they see this right
after opening their project. I'd suggest changing the text to say "Loading
Project", instead.

Reproducible: Always




Discovered on Kdenlive 16.11.70 via Ubuntu git-master ppa.

Kubuntu 16.10 daily build, KDE Plasma 5.7.2.

KDE Frameworks 5.24.0
Qt 5.6.1

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

[kdenlive] [Bug 369211] git master - change "loading playlist" text to "Loading Project".

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kwin] [Bug 369210] New: Wayland, changing compositor options gets me a "black screen"

[Tony via KDE Bugzilla]

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

Bug ID: 369210
   Summary: Wayland, changing compositor options gets me a "black
screen"
   Product: kwin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jodr...@live.com

Any change made to the backend, scaling or animation speed under wayland will
get you a black/no output screen as soon as you hit the apply button.

I can still switch to another vt to terminate the session, after login in again
i noticed the previous changes that caused the "crash" where applied.

This may be related to this one Bug 365471.

Reproducible: Always

Steps to Reproduce:
1.Log in to a wayland session
2.Go to system setting>display and monitor>compositor
3.Make any change and hit apply.

Actual Results:  
The screen goes black with no output, as stated by my monitor.

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

[Breeze] [Bug 369037] Gradient at LibreOffice toolbar

[Heiko Tietze via KDE Bugzilla]

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

Heiko Tietze  changed:

   What|Removed |Added

 CC||tietze.he...@gmail.com

--- Comment #3 from Heiko Tietze  ---
The issue has been fixed. It will be available in 5.3 as well the nightly
builds.

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #9 from Wolfgang Bauer  ---
Regarding the reproduction:
it is enough to delete ~/.config/plasma-org.kde.plasma.desktop-appletsrc before
logging in to trigger it.

Removing the whole ~/.config is not necessary, and removing ~/.cache/ makes no
difference.

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

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

[RJVB via KDE Bugzilla]

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

--- Comment #3 from RJVB  ---
So this appears to be related to using the Mac toplevel menubar: adding 

QCoreApplication::setAttribute(Qt::AA_DontUseNativeMenuBar);

to main() gives functional and populated Mode an Highlighting menus too.

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Carl Love via KDE Bugzilla]

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

Carl Love  changed:

   What|Removed |Added

 CC||c...@us.ibm.com,
   ||will_schm...@vnet.ibm.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Carl Love  ---
I have some what isolated where the issue when running on Power 7 BE (issue
does not occur on LE) is but at this point could use some help getting to the
root cause.  

in VEX/priv/guest_ppc_toIR.c in the function dis_av_bcd() there is a case
statement that handles the bcdadd and bcdsub instructions.  Once the result of
the operation is completed, we have to compute some values to set the CR field
6.  The calculation of the valid bit is as follows:

valid =
unop( Iop_64to32,
  binop( Iop_And64,
 is_BCDstring128( /* Signed */True, mkexpr( vA ) ),
 is_BCDstring128( /* Signed */True, mkexpr( vB ) ) ) );

Note,  is_BCDstring128() calls a clean helper written in C.   The issue is
making the two calls above leads to a segmentation fault.  I rewrote the
computation as follows to isolate out the
computations:

  assign( A_isBCDstr, is_BCDstring128( /* Signed */True, mkexpr( vA ) )
);
 //  assign( A_isBCDstr, mkU64( 0 ) );  
 assign( B_isBCDstr, is_BCDstring128( /* Signed */True, mkexpr( vB ) )
);
 //  assign( B_isBCDstr, mkU64( 0 ) );  

 valid = unop( Iop_64to32, binop( Iop_And64, mkexpr( A_isBCDstr ),
mkexpr( B_isBCDstr ) ) );
Now if I make the call to is_BCDstring128() for vA and vB I get the
segmentation fault.  If I comment out either computation and put in the
appropriate commented out line to just explicitly set the result to zero, I do
not get a segmentation fault.  The segmentation fault occurs later when the IR
code is actually executed.  I am guessing that somehow the generation of the IR
code with two back to back clean helper calls results in bad code that causes
the segmentation fault.  Unfortunately, the issue is a bit deeper in Valgrind
then I am familiar with.  I am looking for help to debug this issue.  Please
let me know if there is a way we can dump out the generated code and so we can
examine it.  Thanks.

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

[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source

[Guillaume DE BURE via KDE Bugzilla]

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

--- Comment #8 from Guillaume DE BURE  ---
Created attachment 101238
  --> https://bugs.kde.org/attachment.cgi?id=101238=edit
power settings

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

[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source

[Guillaume DE BURE via KDE Bugzilla]

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

Guillaume DE BURE  changed:

   What|Removed |Added

 CC||guillaume.deb...@gmail.com

--- Comment #7 from Guillaume DE BURE  ---
I have a very similar issue, I will provide details hoping they are related. I
will provide my settings file.

In my case, on AC, suspending is completely disabled, and closing the lid is
set to "Do Nothing". Nevertheless, when I close the lid, laptop suspends.

To answer Kai Uwe:
* Does it only happen when the screen is locked or generally? 
--> in my case, it happens only when I close the lid, even if session is not
locked
* When you set a timeout of, say 1 minute, for AC is that properly respected? 
--> No. No suspend happens unless I close the lid
* When you set a timeout of, say 1 minute, for Battery but disable it for AC,
does it still suspend after 1 minute? I need to figure out if it's actually us
(PowerDevil) suspending or some other system service
--> No, in that case, suspend is not happening

If there is anything I can provide to help nail down the issue, please ask :)

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

[plasma-nm] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[Dainius Masiliūnas via KDE Bugzilla]

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

--- Comment #18 from Dainius Masiliūnas  ---
Yea, either that or frameworks-plasma/libplasma, or most likely both (plasma-nm
should fall back to the system icon theme and the plasma framework should
actually contain these icons for the Oxygen/Air themes).

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

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||iv...@ivosh.net,
   ||rhysk...@gmail.com

--- Comment #2 from Mark Wielaard  ---
Ivo and Rhys could you double check that my patch does the right thing and the
new nocwd.vgtest passes on Solaris and Darwin?

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

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101237
  --> https://bugs.kde.org/attachment.cgi?id=101237=edit
Don't require the current working directory to exist.

At startup valgrind fetches the current working directory and stashes
it way to be used later (in debug messages, read config files or create
log files). But if the current working directory didn't exist (or there
was some other error getting its path) then valgrind would go in a
endless loop. This was caused by assuming that any error meant a larger
buffer needed to be created to store the cwd path (ERANGE). However
there could be other reasons calling getcwd failed.

Fix this by only looping and resizing the buffer when the error is
ERANGE. Any other error just means we cannot fetch and store the current
working directory. Fix all callers to check get_startup_wd() returns
NULL. Only abort startup if a relative path needs to be used for
user supplied relative log files. Debug messages will just show
"". And skip reading any config files from the startup_wd
if it doesn't exist.

Also add a new testcase that tests executing valgrind in a non-existing
directory (none/tests/nocwd.vgtest).

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #8 from Tony  ---
Similar Bug 367612

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

[valgrind] [Bug 369209] New: valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369209
   Summary: valgrind loops and eats up all memory (very slowly)
when the current working directory doesn't exist.
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

The following code in record_startup_wd():

/* Simple: just ask the kernel */
SysRes res;
SizeT szB = 0;
do {
   szB += 500;
   startup_wd = VG_(realloc)("startup_wd", startup_wd, szB);
   VG_(memset)(startup_wd, 0, szB);
   res = VG_(do_syscall2)(__NR_getcwd, (UWord)startup_wd, szB-1);
} while (sr_isError(res));

Will loop forever when getcwd() produces any error. It should check that the
error is ERANGE.
Even when fixing that and returning an error (False) will make valgrind refuse
to run the program.
This isn't really necessary because often the startup_wd isn't really used or
needed.

Reproducible: Always

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

[dolphin] [Bug 359883] Dolphin crash when I try to delete a folder (Wayland session)

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #2 from Tony  ---
.Also confirming it happens on my install of Neon :(

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

[Akonadi] [Bug 363741] akonadi server 16.08.1: crashing every few seconds

[via KDE Bugzilla]

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

hiwatari.se...@gmail.com changed:

   What|Removed |Added

 CC||hiwatari.se...@gmail.com

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

[krunner] [Bug 369208] New: krunner crashes when calculating simple expression

[Luiz Angelo De Luca via KDE Bugzilla]

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

Bug ID: 369208
   Summary: krunner crashes when calculating simple expression
   Product: krunner
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: luizl...@gmail.com

Application: krunner (5.7.4)

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

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

I was typing "16 * 32" and before hitting "=", it crashed.
I manually restarted krunner and it happens everytime.

I'm using OpenSUSE Tumbleweed.

The crash can be reproduced every time.

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

Thread 30 (Thread 0x7f3533fff700 (LWP 11063)):
#0  0x7f3724c75f1c in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7f3724c6fbb6 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7f372b53bcfd in tls_get_addr_tail () at /lib64/ld-linux-x86-64.so.2
#3  0x7f37277741fd in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f3724c6d454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f37270823ff in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f369b7fe700 (LWP 11061)):
#0  0x7f37270796ed in poll () at /lib64/libc.so.6
#1  0x7f37242f9016 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f37242f912c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f37279a1aab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f37279496fa in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f372776f3c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f37277742e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f3724c6d454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f37270823ff in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f369bfff700 (LWP 11058)):
#0  0x7f3724c7310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f372777519b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f36faf5ee90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f36faf63048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f36faf5e00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f36faf630a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f36faf5e00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f36faf60ed9 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f37277742e8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f3724c6d454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f37270823ff in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f36d0ff9700 (LWP 11057)):
#0  0x7f3724c7310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f372777519b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f36faf5ee90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f36faf63048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f36faf5e00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f36faf60ed9 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f37277742e8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f3724c6d454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f37270823ff in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f36d17fa700 (LWP 11056)):
#0  0x7f3724c7310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f372777519b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f36faf5ee90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f36faf63048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f36faf5e00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f36faf630a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f36faf5e00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at

[plasma-nm] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[pinheiro via KDE Bugzilla]

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

pinheiro  changed:

   What|Removed |Added

 CC||n...@oxygen-icons.org

--- Comment #17 from pinheiro  ---
moved to plasma then

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

[plasma-nm] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[pinheiro via KDE Bugzilla]

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

pinheiro  changed:

   What|Removed |Added

   Assignee|n...@oxygen-icons.org   |lu...@kde.org
Product|Oxygen  |plasma-nm
 CC||jgrul...@redhat.com
  Component|icons   |general

--- Comment #16 from pinheiro  ---
so

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

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

[RJVB via KDE Bugzilla]

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

--- Comment #2 from RJVB  ---
Created attachment 101236
  --> https://bugs.kde.org/attachment.cgi?id=101236=edit
screenshot of KDevelop running in X11 mode on OS X, showing a normal Tools/Mode
menu (with an additional item)

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

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

[RJVB via KDE Bugzilla]

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

--- Comment #1 from RJVB  ---
Created attachment 101235
  --> https://bugs.kde.org/attachment.cgi?id=101235=edit
screenshot of KDevelop running in native mode on OS X, showing the crippled
Tools/Mode menu

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

[kate] [Bug 369207] New: Mode & Highlighting menus remain empty on Mac OS X

[RJVB via KDE Bugzilla]

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

Bug ID: 369207
   Summary: Mode & Highlighting menus remain empty on Mac OS X
   Product: kate
   Version: 16.08
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com

I noticed that the Tools/Mode and Tools/Highlighting menus remain empty, except
for the *disabled* submenus for the various known categories and the items:

"Normal" & "New Filetype" in Tools/Mode
and
"None" in Tools/Highlighting

Both Kate5 and KDevelop5 are affected.

Curiously this happens only when I use Qt's normal/default Cocoa QPA; when I
start the applications in X11 mode (`-platform xcb`) the menus behave normally.

See the screenshots I'll be attaching.

I'm currently using Kate 16.08.0 and KTextEditor 5.24.0

Reproducible: Always

Steps to Reproduce:
1. Start Kate5 or KDevelop5
2. Open a document of a supported type for which highlighting definitions exist
3. Check the Tools/Mode and Tools/Highlighting menus

Actual Results:  
See the Cocoa screenshot and notice how the submenus are present but disabled.
The New Filetype menu item has no effect.

Expected Results:  
See the XCB screenshot: populated submenus

The highlighting mode can be selected normally via the status bar widget, so
the issue cannot be explained by missing highlighting definitions.

The same software versions do NOT have the "New Filetype" Tools/Mode menu item
on Linux.

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

[kwin] [Bug 368275] weird screen distortions with Core 2 hardware

[AT/K]

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

--- Comment #8 from Elmar Stellnberger (AT/K)  ---
Sorry for the inconvenience but there were multiple issues each interfering
with the other
* first of all I got different results with lightdm and by running startkde as
root (it finally worked with the latter)
* secondly there was also a kernel issue with 4.8.0-rc7+ though the effects
with xfce are rather hardly noticeable; however kde5 fully relying on OpenGL
2.0 likely breaks by https://bugs.freedesktop.org/show_bug.cgi?id=97614
   Finally I believe the latest updates either to Mesa and KDE have fixed some
issues. Now KDE5 really runs very stable and fast even with some desktop
effects (have not tried to reset to the default config); as far as this I could
test.

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

[ksudoku] [Bug 369206] Layout of "too easy" message has deteriorated

[james tappin via KDE Bugzilla]

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

--- Comment #1 from james tappin  ---
Created attachment 101234
  --> https://bugs.kde.org/attachment.cgi?id=101234=edit
Example of the bad dialogue

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

[ksudoku] [Bug 369206] New: Layout of "too easy" message has deteriorated

[james tappin via KDE Bugzilla]

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

Bug ID: 369206
   Summary: Layout of "too easy" message has deteriorated
   Product: ksudoku
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: iandw...@gmail.com
  Reporter: jtap...@gmail.com
CC: kde-games-b...@kde.org

Running v1.3, Manjaro packages
The message dialogue when the generated puzzle is lower than requested now 
appears all on one line, making an awkward and ugly dialogue window

Reproducible: Always

Steps to Reproduce:
1.  Generate a puzzle with a high difficulty (e.g. diabolical) requested
2.  Whenever the program fails to generate the required difficulty the message
is produced.


Actual Results:  
Ugly dialogue is generated

Expected Results:  
Nicer dialogue with line breaks in the text as in earlier versions.

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[melkor333 via KDE Bugzilla]

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

melkor333  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|BACKTRACE   |---

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

[kwin] [Bug 368275] weird screen distortions with Core 2 hardware

[AT/K]

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

Elmar Stellnberger (AT/K)  changed:

   What|Removed |Added

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

--- Comment #7 from Elmar Stellnberger (AT/K)  ---
works with mesa 12.0.3-1, kernel 4.6.0-1 and plasma-workspace 4:5.7.4-1 under
Debian Stretch.

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

[plasmashell] [Bug 346602] Application Launcher (Kickoff) not filtering search results from system settings

[Jesse via KDE Bugzilla]

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

--- Comment #12 from Jesse  ---
If anyone is running 5.7.5 or the 5.8 beta, would they be willing to test to
see if this bug is still present in those versions?

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

[plasmashell] [Bug 369100] Dark theme affects aspects of applications that it should not

[via KDE Bugzilla]

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

craigburdenmsc+ot...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from craigburdenmsc+ot...@gmail.com ---
Fair enough, I just hadn't seen it in Gnome when I was running Fedora. 

They don't really mention what toolkit they use, however their development page
mentions a modified version of Qt, so perhaps Qt.

http://wps-community.org/development

As for MatLab I can't say

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

[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."

[Pip via KDE Bugzilla]

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

--- Comment #8 from Pip  ---
I switched to MariaDB from SQLITE3 and it seemed to eliminate most of the
problems after rebuilding.

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

[kwin] [Bug 368275] weird screen distortions with Core 2 hardware

[AT/K]

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

--- Comment #6 from Elmar Stellnberger (AT/K)  ---
Ooopsla; today I have re-tested since there was a new KDE and Mesa update for
Debian Testing. If I switch off the desktop effects then it in deed shows the
desktop background (I must have pressed Strg instead of Alt the last time since
both keys are exchanged on my keyboard). However there is nothing more that I
can do: no context menu on the desktop no plasma toolbars (need to restart
lightdm).

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
Thank you for checking this, so the basis is correct.

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

[krita] [Bug 369205] New: Krita crashes when exporting to various formats

[via KDE Bugzilla]

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

Bug ID: 369205
   Summary: Krita crashes when exporting to various formats
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: smithtromb...@gmail.com

Krita crashes or sends an error message in MS Windows 10 when exporting single
images and when exporting animations. The problems happen with these formats:

--OpenRaster image
program freezes, no response

--GIF image
error message says "internal error".

--all video formats
error message says "Could not find ffmpeg binary. Saving to video formats is   
 impossible."



Reproducible: Always

Steps to Reproduce:
1. open new image or existing image in Krita
2. choose either export or export animation option
3. save under one of the formats listed in the details

Actual Results:  
Krita either crashes or sends error messages depending on the format chosen.

Expected Results:  
Krita should be able to export to these formats with no problem.

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #7 from Wolfgang Bauer  ---
And to clarify: I cannot reproduce either of both problems now on second login
on this user account.

It only happened when first logged in after creating the user account, logging
out and back in seems to make both problems disappear.
(I wasn't able to reproduce this on my existing user account either before)

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #6 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #5)
> Hm, now I got the black screen by just moving the window, and this time I
> cannot get the desktop back any more it seems.

Choosing "Add Widgets" in the panel config brought it back this time...

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #5 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #4)
> PS: I get this black screen as well (also on a fresh user account only) on
> my single monitor, but it reappears when I click on the panel.

Hm, now I got the black screen by just moving the window, and this time I
cannot get the desktop back any more it seems.

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #4 from Wolfgang Bauer  ---
PS: I get this black screen as well (also on a fresh user account only) on my
single monitor, but it reappears when I click on the panel.

This has also been reported in openSUSE:
https://bugzilla.opensuse.org/show_bug.cgi?id=1000514

Not sure if it's related though.

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #3 from Wolfgang Bauer  ---
I see this on a single-monitor system too (Plasma 5.7.95, KF5.26.0, Qt 5.7.0).

But only on a fresh user account.

Has been reported here as well:
https://bugzilla.opensuse.org/show_bug.cgi?id=1000510

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

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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

--- Comment #5 from Sven Brauch  ---
Hm, in the sample code I can't even find "import arcade" ...

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

[plasmashell] [Bug 368071] Crash in KDeclarative::Plotter with threaded render loop

[aaaSashaMGGU via KDE Bugzilla]

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

--- Comment #1 from aaaSashaMGGU  ---
Created attachment 101233
  --> https://bugs.kde.org/attachment.cgi?id=101233=edit
New crash information added by DrKonqi

plasmashell (5.5.5) using Qt 5.5.1

Crash
Crash
Crash
Crash
Crash
Crash

-- Backtrace (Reduced):
#6  0x7f78d6850418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f78d685201a in __GI_abort () at abort.c:89
[...]
#9  0x7f78d689af4a in malloc_printerr (ar_ptr=,
ptr=, str=0x7f78d69a848f "free(): invalid pointer", action=3) at
malloc.c:5007
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3868
#11 0x7f78d689eabc in __GI___libc_free (mem=) at
malloc.c:2969

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

[plasmashell] [Bug 368071] Crash in KDeclarative::Plotter with threaded render loop

[aaaSashaMGGU via KDE Bugzilla]

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

aaaSashaMGGU  changed:

   What|Removed |Added

 CC||aaasasham...@mail.ru

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Thomas Schmitt via KDE Bugzilla]

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

--- Comment #40 from Thomas Schmitt  ---
Hi,

> http://commits.kde.org/k3b/ae0413daf1df44cb2c8c6e88a5b86180f1f52c3a
> libk3b/projects/datacd/k3bisoimager.cpp

Then let's see ...

> +char* in_image = "/dev/fd/0";

This is still wrong.
We need to access the existing ISO 9660 filesystem on the medium.
So this should rather be the path to the drive with the DVD+RW.
(I.e. something like "/dev/sr0" on Linux.)


> +// Validate file descriptor
> +if (sscanf(in_image, "/dev/fd/%u", ) == 1)
> +imgfd = dup(imgfd);
> +else

This case should then not occur. (We cannot lseek() on stdin anyway.)


> +imgfd = open(in_image, O_RDONLY);

This will be in effect.

(For the subsequent code i can just hope that i did not propose too
 much nonsense. It needs to be tested when the path problem is solved.)

I do not see where you throw severe error if m_multiSessionInfo stays
with string value "0,0". This value means that we cannot use the growisofs
emulation of multi-session and that growisofs will raise protest about
-C 0,0. Without -C it would probably just overwrite the existing data
instead of adding new data. Maybe it would complain about -M without -C.

K3B should tell the user that it won't work instead of letting growisofs
or other writers do undesired things or issue cryptic error messages.


> - A generic checker for GrowisofsWriter (growisofs) and IsoImager (mkisofs)

You did not put the rounding stage into a writer specific function.
As it is now, the function in k3bisoimager.cpp  assumes that all writers
behave like growisofs.

So to stay modular (and to give cdrskin a chance to override the values
by its own findings) you should not round in k3bisoimager.cpp but
rather introduce a new writer specific function for all writers.
- The one of growisofs will round up to 16.
- The (future i hope) one of cdrskin would ask cdrskin for its own values
  for the given medium and ISO 9660 filesystem.
- The one of cdrecord would throw error, because i assume that cdrecord
  does not support on DVD+RW a write start address other than 0.

To prepare for cdrskin, the new function should know the path of the
drive's device file (e.g. "/dev/sr0").

Have a nice day :)

Thomas

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

[akregator] [Bug 369204] New: Akregator random crashes

[via KDE Bugzilla]

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

Bug ID: 369204
   Summary: Akregator random crashes
   Product: akregator
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nicolas.ducl...@estaca.eu

Application: akregator (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
Akregator crashed every time I use it. The time before the crashed is between 1
and 5 minutes.
Sometimes, just after choosing between a session restore or a new one,
sometimes when it fetches feeds and sometimes when I read an article.
This happens since the upgrade to the 16.08.1 version.

The crash can be reproduced sometimes.

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

Thread 24 (Thread 0x7f5cb99da700 (LWP 2130)):
#0  0x7f5d26797bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5d1c04bbc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f5d1c04bc09 in  () at /lib64/libQt5Script.so.5
#3  0x7f5d267925ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f5d30a8ef6d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f5cba7fc700 (LWP 2123)):
#0  0x7f5d26797bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5d2bbaeb90 in mojo::system::Waiter::Wait(unsigned long, unsigned
int*) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f5d2bb9a48c in mojo::system::Core::WaitManyInternal(unsigned int
const*, unsigned int const*, unsigned int, unsigned long, unsigned int*,
mojo::system::HandleSignalsState*) () at /lib64/libQt5WebEngineCore.so.5
#3  0x7f5d2bb9a98c in
mojo::system::Core::WaitMany(mojo::system::UserPointer,
mojo::system::UserPointer, unsigned int, unsigned long,
mojo::system::UserPointer,
mojo::system::UserPointer) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f5d2bb96de5 in MojoWaitMany () at /lib64/libQt5WebEngineCore.so.5
#5  0x7f5d2d210e47 in
mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState
const&, bool) () at /lib64/libQt5WebEngineCore.so.5
#6  0x7f5d2d21107e in
mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*,
base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5
#7  0x7f5d2d2111b9 in
mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7f5d2bc870f4 in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#9  0x7f5d2bc71f35 in base::MessageLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#10 0x7f5d2bc9fc06 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#11 0x7f5d2bc9c0fd in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#12 0x7f5d267925ca in start_thread () at /lib64/libpthread.so.0
#13 0x7f5d30a8ef6d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f5cbaffd700 (LWP 2122)):
#0  0x7f5d26797bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5d2bc9ee79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f5d2bc9f540 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f5d2bc9f710 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f5d2bc9c0fd in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f5d267925ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f5d30a8ef6d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f5cbb7fe700 (LWP 2121)):
#0  0x7f5d26797bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5d2bc9ee79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f5d2bc9f540 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f5d2bc9f710 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f5d2bc9c0fd in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f5d267925ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f5d30a8ef6d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f5cbbfff700 (LWP 2120)):
#0  0x7f5d30a833ed in poll () at /lib64/libc.so.6
#1  0x7f5d2559da06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  

[Akonadi] [Bug 369203] New: CollectionFetchJob::exec() hangs forever

[Patrick Ohly via KDE Bugzilla]

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

Bug ID: 369203
   Summary: CollectionFetchJob::exec() hangs forever
   Product: Akonadi
   Version: unspecified
  Platform: Debian testing
   URL: https://bugs.freedesktop.org/show_bug.cgi?id=97609
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libakonadi
  Assignee: kdepim-b...@kde.org
  Reporter: patrick.o...@intel.com

SyncEvolution uses the blocking API to execute jobs. That used to work fine
with older Akonadi, but on Debian Stretch (= 4.14.10-5) it just hangs. Below is
a stand-alone test program demonstrating the problem.

On Debian Jessie, the output is:
$ ./akonadi-lsDatabase "akonadi" opened using driver "QMYSQL" 
akonadi_ical_resource_0


On Debian Stretch:
$ ./akonadi-ls
^C
Shutting down "0x277afc0" ...

Here it got aborted after two hours.

Akonadi seems okay on Debian Stretch:
$ akonadictl status
Akonadi Control: running
Akonadi Server: running
akonadiprivate_log: search paths:  ("lib/x86_64-linux-gnu",
"lib/x86_64-linux-gnu/qt5/plugins/", "lib/x86_64-linux-gnu/kf5/",
"lib/x86_64-linux-gnu/kf5/plugins/", "/usr/lib/qt5/plugins/",
"/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_birthdays_resource,
akonadi_contacts_resource, akonadi_davgroupware_resource,
akonadi_googlecalendar_resource, akonadi_googlecontacts_resource,
akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource,
akonadi_invitations_agent, akonadi_kalarm_dir_resource,
akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource,
akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mbox_resource,
akonadi_migration_agent, akonadi_mixedmaildir_resource,
akonadi_newmailnotifier_agent, akonadi_notes_resource,
akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_vcard_resource,
akonadi_vcarddir_resource

akonadiconsole shows that there are collections.

Reproducible: Always

Steps to Reproduce:
1. cat >akonadi-ls.cpp <
#include 

#include 
#include 
#include 

#include 
#include 
#include 

using namespace Akonadi;

/**
 * We take over ownership of jobs by storing them in smart pointers
 * (RAII).  This is how SyncEvolution does things and more predictable
 * than assuming that a future exec() call will auto-delete them as
 * part of its event processing.
 *
 * To avoid double frees, we need to disable auto-deletion.
 * This method does that. Use like this:
 * std::auto_ptr statisticsJob(DisableAutoDelete(new
CollectionStatisticsJob(m_collection)));
 */
template J *DisableAutoDelete(J *job) { job->setAutoDelete(false);
return job; }

int main(int argc, char **argv)
{
KAboutData aboutData(// The program name used internally.
 "syncevolution",
 // The message catalog name
 // If null, program name is used instead.
 0,
 // A displayable program name string.
 ki18n("SyncEvolution"),
 // The program version string.
 "1.0",
 // Short description of what the app does.
 ki18n("Lets Akonadi synchronize with a SyncML Peer"),
 // The license this code is released under
 KAboutData::License_GPL,
 // Copyright Statement
 ki18n("(c) 2010-12"),
 // Optional text shown in the About box.
 // Can contain any information desired.
 ki18n(""),
 // The program homepage string.
 "http://www.syncevolution.org/;,
 // The bug report email address
 "syncevolut...@syncevolution.org");

KCmdLineArgs::init(argc, argv, );
KApplication app(false);

//  std::unique_ptr fetchJob(DisableAutoDelete(new
CollectionFetchJob(Collection::root(),
// CollectionFetchJob::Recursive)));
CollectionFetchJob *fetchJob = new CollectionFetchJob(Collection::root(),
CollectionFetchJob::Recursive);

   
fetchJob->fetchScope().setContentMimeTypes(QString("text/calendar").split(","));
if (!fetchJob->exec()) {
std::cerr << "Cannot fetch collections." << std::endl;
return 1;
}

Collection::List collections = fetchJob->collections();
foreach (const Collection , collections) {
std::cout << collection.name().toUtf8().constData() << std::endl;
}
return 0;
}
EOF
2. g++ -I/usr/include/KDE -I/usr/include/qt4 -I/usr/include/qt4/QtCore -g
akonadi-ls.cpp -o akonadi-ls -lakonadi-kde -lkdecore -lkdeui -lQtCore 
3. ./akonadi-ls


Actual Results:  
It hangs. gdb stacktrace:

(gdb) where

[trojita] [Bug 358485] CardDAV support

[Espen Hustad via KDE Bugzilla]

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

Espen Hustad  changed:

   What|Removed |Added

 CC||es...@ehustad.com

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

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Gregor Mi via KDE Bugzilla]

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

--- Comment #4 from Gregor Mi  ---
I pressed F5 and it did change nothing.

The .../site-packages/arcade directory looks like this:

total 180
-rw-r--r-- 1   2165 Sep 17 20:46 application.py
-rw-r--r-- 1373 Sep 17 20:46 arcade_types.py
drwxr-xr-x 3   4096 Sep 17 20:51 color
-rw-r--r-- 1  57629 Sep 17 20:46 draw_commands.py
-rw-r--r-- 1   4244 Sep 17 20:46 geometry.py
-rw-r--r-- 1716 Sep 17 20:46 __init__.py
drwxr-xr-x 3   4096 Sep 17 20:51 key
-rw-r--r-- 1  11703 Sep 17 20:46 physics_engine_2d.py
-rw-r--r-- 1   8473 Sep 17 20:46 physics_engines.py
drwxr-xr-x 2   4096 Sep 17 20:51 __pycache__
-rw-r--r-- 1   9409 Sep 17 20:46 shape_objects.py
-rw-r--r-- 1   1931 Sep 17 20:46 sound.py
-rw-r--r-- 1  26546 Sep 17 20:46 sprite.py
-rw-r--r-- 1332 Sep 17 20:46 test.py
-rw-r--r-- 1332 Sep 17 20:46 types.py
-rw-r--r-- 1 94 Sep 17 20:46 version.py
-rw-r--r-- 1   6819 Sep 17 20:46 window_commands.py

So I assume it is written in Python (this is the website:
http://pythonhosted.org/arcade/index.html)

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[via KDE Bugzilla]

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

--- Comment #2 from ker...@gmail.com ---
I've tried to play the clip with ffplay and it works fine. The same with melt
command. About Kdenlive reports version 6.3 of Mlt which seems correct as I
have git version of Mlt installed and "melt -version" displays version 6.3.0 as
well.  I've got all the ffmpeg paths set up in Kdenlive settings. With version
6.2.0 Kdenlive crashes immediately but I wasn't able to send bug report as KDE
bug report app marks it's as not useful.

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

[kwin] [Bug 369202] New: Allow speeding up of the animation for the Glide effect

[Buck Shockley via KDE Bugzilla]

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

Bug ID: 369202
   Summary: Allow speeding up of the animation for the Glide
effect
   Product: kwin
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: darkwingbuc...@gmail.com

The Glide effect doesn't allow for the timing of the animation to be changed,
and right now it feels really slow. In addition to gliding in and out and the
angle of the glide, the speed should also be a variable.

Reproducible: Always

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

[plasmashell] [Bug 369200] translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
kdeobservatory hasn't existed in years. That pot should definitely not be used.

What messages are missing and where? Please reopen this bug when you reply,
thanks.

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

[Spectacle] [Bug 369197] Spectacle is hard to find if you don't know/remember its name

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

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

--- Comment #1 from Boudhayan Gupta  ---
"screenshot", or a part thereof, when typed in KRunner or the Application
Launcher menu should show "Spectacle". The metadata has been in the .desktop
file since the very first release.

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Check with ffmplay that you have the required codecs installed for proper
decoding of your clip files. Next, check with melt that the same clips still
play. Finally, is your command line melt the same mlt version that kdenlive
sees? Check using the kdenlive about dialog, it now shows also mlt version. We
see lots of distro packager problems that only the distro packagers can solve,
they're shipping broken distros.

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

[krita] [Bug 369201] New: Brush tagging to created group(s) will reset to the top

[Franklyn via KDE Bugzilla]

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

Bug ID: 369201
   Summary: Brush tagging to created group(s) will reset to the
top
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: beasle...@gmail.com

When creating a specific group (i.e. Mix brush group), then assign a brush in
the new group, the Brush Preset docker will send (or reset) all the way back to
the top of the list. Have to search through the brushes again and resume
tagging brushes into new group; only for it to reset again. I was hoping if you
can make the docker "stay in place" when assigning brushes into new groups. I
have a lot of brushes installed and was trying to organize to my liking.
Thanks.

Reproducible: Always

Steps to Reproduce:
1. Create a specific group.
2. Assign brush to the new group.
3. Watch the docker as it sends it back up to the top of the brushes.

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

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||perenque@gmail.com

--- Comment #76 from David Edmundson  ---
*** Bug 369183 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[Antonio Orefice via KDE Bugzilla]

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

--- Comment #11 from Antonio Orefice  ---
I made a 3 minute run of that xdotool script (open and close wallpaper settings
multiple times).
Nvidia proprietary driver + QSG_RENDER_LOOP=basic
Start: 286MB
End: 486MB
Nvidia proprietary driver + unset QSG_RENDER_LOOP
Start: 281MB
End: 533MB
Nouveau + unset QSG_RENDER_LOOP
Start 289MB
End 436MB

So, in the end it seems that NVIDIA blob is using more ram, but not that much,
and plasma/qt are leaking more memory just because qt uses threads with nvidia
proprietary driver, right?

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

[plasmashell] [Bug 369200] New: translation file for plasma_applet_kdeobservatory.pot is missing in svn repository

[Freek de Kruijf via KDE Bugzilla]

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

Bug ID: 369200
   Summary: translation file for plasma_applet_kdeobservatory.pot
is missing in svn repository
   Product: plasmashell
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: freekdekru...@kde.nl
CC: bhus...@gmail.com, plasma-b...@kde.org

Using the plasma applet to update packages I found untranslated messages.
Searching the system I found that these messages should come from
plasma_applet_kdeobservatory.mo. Searching the svn repository for a file
plasma_applet_kdeobservatory.pot I found this file is not present. So
apparently at least this file is not presented for translation.
The po file is present in kde-l10n-nl-16.08.0.tar.xz, but the last translation
is from 2010, where the pot file is from 2014.

Reproducible: Always



Expected Results:  
The system should present this file for translation. Maybe other pot files are
missing as well.

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Carl Love via KDE Bugzilla]

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

Carl Love  changed:

   What|Removed |Added

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

--- Comment #7 from Carl Love  ---
patch committed valgrind commit 15977

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

[valgrind] [Bug 368419] Perf Events ioctls not implemented

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@redhat.com

--- Comment #4 from Mark Wielaard  ---
(In reply to Keno Fischer from comment #3)
> > If I interpret this correctly, ARG3 is a C style zero-terminated string 
> > that the syscall
> > reads.  Is that correct?
> 
> Essentially yes, though with the caveat that if there's no NUL after
> PAGE_SIZE-1 bytes, it'll still accept that as far as I know (as a
> PAGE_SIZE-1 sized string), since it uses strndup_user(str, PAGE_SIZE) on the
> kernel side of things.

That seems a funny corner case that I cannot imagine anybody relies on (the
caller would have to explicitly not pass a zero terminated string larger than
PAGE_SIZE, which is different on different arches). If someone does I think a
warning from valgrind seems somewhat justified. So just using PRE_MEM_RASCIIZ
here should be fine.

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

[valgrind] [Bug 126348] (rdpmc) vex x86->IR: unhandled instruction bytes: 0xF 0x33 0x89 0x45

[via KDE Bugzilla]

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

akru...@gmail.com changed:

   What|Removed |Added

 CC||akru...@gmail.com

--- Comment #2 from akru...@gmail.com ---
The RDTSC/RDTSCP instructions are supported - is RDPMC really that much more
difficult?

Would it be sufficient to pass the RDPMC instruction through to the physical
cpu, with the same ECX value? If that produces SIGILL (because PCE in CR4 is
off), kill the client program, otherwise return in EDX:EAX whatever the native
RDPMC returned. Event counts will be inflated, yes, but imo that is a
well-understood effect of running programs under Valgrind.

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

[plasmashell] [Bug 359152] No application can be run after some uptime

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #6 from David Edmundson  ---
Then you have some rogue process on your system deleting it.
It's not plasma.

Sorry, I can't help you any further. Good luck

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

[kdenlive] [Bug 369198] New: Kdenlive: Please Make Zoom Follow Mouse Cursor, not Playhead

[via KDE Bugzilla]

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

Bug ID: 369198
   Summary: Kdenlive: Please Make Zoom Follow Mouse Cursor, not
Playhead
   Product: kdenlive
   Version: 16.08.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: qubo...@gmail.com

One major usability issue of Kdenlive is the delay, which takes place when
commanding the playhead to move.

One of the consequences is that zooming into the timeline requires a lot of
stop-and-go user interactions.

You can't simply zoom into an area, you have to click the area, wait for the
playhead to appear there and then you can zoom.

Video: https://youtu.be/RlqpmZj-vaI

Reproducible: Always

Steps to Reproduce:
Zoom into the timeline with ctrl+mousewheel

Actual Results:  
You zoom into the playhead location

Expected Results:  
You zoom into the location of the cursor

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

[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andrius Štikonas  ---
ok, looks like wacomtablet kcm was causing this crash.

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

[plasmashell] [Bug 369183] nothing crashed, bug report window appeared while screen saver was running

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---
It did crash, it just restarted immediately afterwards.

Thanks for reporting. Should be fixed in newer releases.

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

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

[Spectacle] [Bug 369197] New: Spectacle is hard to find if you don't know/remember its name

[via KDE Bugzilla]

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

Bug ID: 369197
   Summary: Spectacle is hard to find if you don't know/remember
its name
   Product: Spectacle
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: daniel.goert...@gmail.com

It is difficult to launch the Spectacle program if you do not know or remember
its name:

- Searching in KDE for "snap" or "screen" does not reveal Spectacle.
- Pressing the "printscreen" button on my keyboard does nothing.
- Googling for the name of Spectacle is tricky and took me a few frustrating
minutes.
- I recall the first time I went through all this a few months ago... it was
unclear if plasma 5 even had a screenshot program.  I stumbled upon Spectacle
with a lucky Google.

I'm not that familiar with KDE search; is there some way to add metadata such
that Spectacle comes up when the user enters "screen", "snap", or "capture"? 
Or perhaps there is and my Gentoo installation is just missing it?




Reproducible: Always

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[via KDE Bugzilla]

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

ker...@gmail.com changed:

   What|Removed |Added

   Platform|unspecified |Archlinux Packages
Version|unspecified |16.08.0

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

[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

  Component|general |general
Product|frameworks-knotifications   |frameworks-kded
   Assignee|mklape...@kde.org   |afies...@kde.org

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

[frameworks-kded] [Bug 369082] kded5 crashes on Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

--- Comment #2 from Andrius Štikonas  ---
So kded5 crashes when plasma wayland starts but I can start kded5 manually.

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

[frameworks-knotifications] [Bug 369082] kded5 crashes on Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

Summary|SNI system tray icons do|kded5 crashes on Plasma
   |not work in Plasma Wayland  |Wayland session
   |session |

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[David Edmundson via KDE Bugzilla]

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

--- Comment #10 from David Edmundson  ---
please also try with 

QSG_RENDER_LOOP=basic plasmashell

and report on what that does

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[David Edmundson via KDE Bugzilla]

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

--- Comment #9 from David Edmundson  ---
Oh, then it's not the issue that I fixed in 5.26 which was purely related to
thumbnails.

The wallpaper dialog doesn't do any custom GL, so if that's leaking only on
NVidia it strongly implies the problem is higher in the stack than Plasma.

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[Antonio Orefice via KDE Bugzilla]

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

--- Comment #8 from Antonio Orefice  ---
Since it seems nouveau is not affected, I reported the very same to nvidia
https://devtalk.nvidia.com/default/topic/966824/linux/huge-memory-allocation-on-plasmashell-with-proprietary-driver-nouveau-is-fine/post/4981667/?offset=5#4981701
In there, at posted a script using xdotool that did nothing else that showing
the plasma configuration window; then the get wallpapers window, close both and
reiterate.
After 20 minutes of that, my system started swapping badly and plasma was
eating almost 6GB of ram.

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

[Akonadi] [Bug 340931] Read status of emails not updated when changed outside KMail, but only for GMail accounts via IMAP

[Martin Tlustos via KDE Bugzilla]

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

Martin Tlustos  changed:

   What|Removed |Added

 CC||martin.tlus...@gmail.com

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

[krunner] [Bug 368729] Segfault when launching krunner

[Vitaliy Gorbunov via KDE Bugzilla]

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

--- Comment #2 from Vitaliy Gorbunov  ---
Turns out it wasn't a bug.
I've ran sudo apt full-upgrade and it's fixed now.
The problem was that I used sudo apt upgrade instead and it didn't upgrade few
packages.

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

[yakuake] [Bug 369196] Initial view looks broken on Wayland

[Aleix Pol via KDE Bugzilla]

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

--- Comment #1 from Aleix Pol  ---
Created attachment 101232
  --> https://bugs.kde.org/attachment.cgi?id=101232=edit
proof

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

[yakuake] [Bug 369196] New: Initial view looks broken on Wayland

[Aleix Pol via KDE Bugzilla]

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

Bug ID: 369196
   Summary: Initial view looks broken on Wayland
   Product: yakuake
   Version: Git (Frameworks 5)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: aleix...@kde.org

I'm unsure if the problem is either HiDPI or Wayland. See photo.

Reproducible: Always

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

[krunner] [Bug 368729] Segfault when launching krunner

[Vitaliy Gorbunov via KDE Bugzilla]

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

Vitaliy Gorbunov  changed:

   What|Removed |Added

 CC||vit.gorbu...@gmail.com

--- Comment #1 from Vitaliy Gorbunov  ---
I have the same after upgrading from kubuntu-ppa/backports.
I've submitted it also to launchpad -
https://bugs.launchpad.net/kubuntu-ppa/+bug/1626590.
Perhaps it's bug in packaging.

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

[frameworks-knotifications] [Bug 369082] SNI system tray icons do not work in Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

--- Comment #1 from Andrius Štikonas  ---
Looks like org.kde.StatusNotifierWatcher interface is not present in my wayland
session

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

[frameworks-knotifications] [Bug 369082] SNI system tray icons do not work in Plasma Wayland session

[Andrius Štikonas via KDE Bugzilla]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org
   Assignee|kwin-bugs-n...@kde.org  |mklape...@kde.org
Product|kwin|frameworks-knotifications
Version|5.7.95  |unspecified
  Component|wayland-generic |general

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

[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.

[Antonio Orefice via KDE Bugzilla]

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

--- Comment #7 from Antonio Orefice  ---
New info:
with raster backend, apart from having a broken desktop, it seems plasma still
allows me to interact with panels, so i interacted with them by using the menu,
popup some tooltips, showed the calendar and so on.
Well, with export QMLSCENE_DEVICE=softwarecontext i've a ram usage that starts
with 228MB and ends to 276MB
Using classic opengl, doing the exact same things, it starts at 228MB and
reaches 420MB.

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

[krita] [Bug 356577] Adding a toggle on/off switch for pen pressure

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Scott Petrovic  ---
this was done in part of 3.0.1. The button was decided to be placed in the
toolbar. It is not added by default, but can be added through the toolbar
customization.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Dan Duris via KDE Bugzilla]

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

--- Comment #201 from Dan Duris  ---
Yes, commander. Right on.

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