[plasmashell] [Bug 389771] Activity bar gets stuck sometimes after I press the shortcut

[Ivan Čukić]

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

--- Comment #6 from Ivan Čukić  ---
Not the refresh rate timing.

What I think is happening is plasma being slow to show the bar and when it gets
shown, the keys are already un-pressed, so it does not hide the bar. Or
something along those lines.

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

[kwin] [Bug 391371] New: kwin Crash when i shade window with wobbly windows

[bugzilla_noreply]

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

Bug ID: 391371
   Summary: kwin Crash when i shade window with wobbly windows
   Product: kwin
   Version: 5.12.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mickth...@hotmail.com
  Target Milestone: ---

Application: kwin_x11 (5.12.2)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:  when the window is in shade
mode 
when i move it with wobbly windows enabled it will crash kwin

- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9313257940 (LWP 2929))]

Thread 4 (Thread 0x7f92e1f38700 (LWP 2940)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f930efcfdb4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f930efcfdf9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f930bd456ba in start_thread (arg=0x7f92e1f38700) at
pthread_create.c:333
#4  0x7f9312c6f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f92eedee700 (LWP 2937)):
#0  0x7f9312c63811 in __GI_ppoll (fds=fds@entry=0x7f92dc000ac8,
nfds=nfds@entry=1, timeout=, timeout@entry=0x0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x7f93100b4001 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:77
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f92dc000ac8) at
kernel/qcore_unix.cpp:112
#3  qt_safe_poll (fds=0x7f92dc000ac8, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:133
#4  0x7f93100b5692 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f931005f64a in QEventLoop::exec (this=this@entry=0x7f92eededc60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f930fe7f554 in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7f930aa1ba35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f930fe846eb in QThreadPrivate::start (arg=0x24f36b0) at
thread/qthread_unix.cpp:376
#9  0x7f930bd456ba in start_thread (arg=0x7f92eedee700) at
pthread_create.c:333
#10 0x7f9312c6f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f92f582a700 (LWP 2933)):
#0  0x7f9312c63811 in __GI_ppoll (fds=fds@entry=0x7f92e800ef08,
nfds=nfds@entry=1, timeout=, timeout@entry=0x0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x7f93100b4001 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:77
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f92e800ef08) at
kernel/qcore_unix.cpp:112
#3  qt_safe_poll (fds=0x7f92e800ef08, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:133
#4  0x7f93100b5692 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f931005f64a in QEventLoop::exec (this=this@entry=0x7f92f5829c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f930fe7f554 in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7f93098d62c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f930fe846eb in QThreadPrivate::start (arg=0x7f9309b4ad60) at
thread/qthread_unix.cpp:376
#9  0x7f930bd456ba in start_thread (arg=0x7f92f582a700) at
pthread_create.c:333
#10 0x7f9312c6f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9313257940 (LWP 2929)):
[KCrash Handler]
#6  0x7f9312b9d428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f9312b9f02a in __GI_abort () at abort.c:89
#8  0x7f9312b95bd7 in __assert_fail_base (fmt=,
assertion=assertion@entry=0x7f930f847ce8 "x1 < x2 && y1 < y2 && x1 >= left() &&
x2 <= right() && y1 >= top() && y2 <= bottom()", file=file@entry=0x7f930f847c90
"/workspace/build/libkwineffects/kwineffects.cpp", line=line@entry=980,
function=function@entry=0x7f930f8481e0  "KWin::WindowQuad
KWin::WindowQuad::makeSubQuad(double, double, double, double) const") at
assert.c:92
#9  0x7f9312b95c82 in __GI___assert_fail
(assertion=assertion@entry=0x7f930f847ce8 "x1 < x2 && y1 < y2 && x1 >= left()
&& x2 <= right() && y1 >= top() && y2 <= bottom()",
file=file@entry=0x7f930f847c90

[konversation] [Bug 391306] Konversation crashes after going into standby mode

[Eli MacKenzie]

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

Eli MacKenzie  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
Version|unspecified |1.5.1

--- Comment #1 from Eli MacKenzie  ---
copying attachment to comment:

Application: konversation (1.5-master #4303)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-108-generic x86_64
Distribution: Trisquel GNU/Linux 7.0, Belenos

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

I put the computer into standby mode and came back an hour later to find
konversation had crashed.

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

Thread 4 (Thread 0x7f55ab979700 (LWP 3278)):
#0  g_main_context_prepare (context=context@entry=0x2a29110,
priority=priority@entry=0x7f55ab978e18) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3296
#1  0x7f55bb478f03 in g_main_context_iterate (context=0x2a29110,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3714
#2  0x7f55bb47930a in g_main_loop_run (loop=0x2a290a0) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3928
#3  0x7f55b2e35336 in gdbus_shared_thread_func (user_data=0x2a290e0) at
/build/buildd/glib2.0-2.40.2/./gio/gdbusprivate.c:273
#4  0x7f55bb49df05 in g_thread_proxy (data=0x29e1cf0) at
/build/buildd/glib2.0-2.40.2/./glib/gthread.c:764
#5  0x7f55bd129184 in start_thread (arg=0x7f55ab979700) at
pthread_create.c:312
#6  0x7f55bf60b03d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f55ab178700 (LWP 3279)):
#0  0x7f55bd12c7de in __pthread_mutex_unlock_usercnt (decr=1,
mutex=0x2a31210) at pthread_mutex_unlock.c:57
#1  __GI___pthread_mutex_unlock (mutex=0x2a31210) at pthread_mutex_unlock.c:310
#2  0x7f55bb4ba9b1 in g_mutex_unlock (mutex=mutex@entry=0x2a2df80) at
/build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:228
#3  0x7f55bb4790f6 in g_main_context_iteration (context=0x2a2df80,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3796
#4  0x7f55bb479129 in glib_worker_main (data=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:5541
#5  0x7f55bb49df05 in g_thread_proxy (data=0x29e1ed0) at
/build/buildd/glib2.0-2.40.2/./glib/gthread.c:764
#6  0x7f55bd129184 in start_thread (arg=0x7f55ab178700) at
pthread_create.c:312
#7  0x7f55bf60b03d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f559833c700 (LWP 3281)):
#0  0x7f55bb4ba61a in g_mutex_get_impl (mutex=0x7f5599a0) at
/build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:120
#1  0x7f55bb4ba979 in g_mutex_lock (mutex=mutex@entry=0x7f5599a0) at
/build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:209
#2  0x7f55bb478699 in g_main_context_prepare
(context=context@entry=0x7f5599a0, priority=priority@entry=0x7f559833bca8)
at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3354
#3  0x7f55bb478f03 in g_main_context_iterate
(context=context@entry=0x7f5599a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3714
#4  0x7f55bb4790ec in g_main_context_iteration (context=0x7f5599a0,
may_block=1) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#5  0x7f55c0fc77be in QEventDispatcherGlib::processEvents
(this=0x7f5598c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f55c0f990af in QEventLoop::processEvents
(this=this@entry=0x7f559833bde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f55c0f993a5 in QEventLoop::exec (this=this@entry=0x7f559833bde0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f55c0e95c5f in QThread::exec (this=this@entry=0x2d33dc0) at
thread/qthread.cpp:537
#9  0x7f55c0f7a823 in QInotifyFileSystemWatcherEngine::run (this=0x2d33dc0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f55c0e9832f in QThreadPrivate::start (arg=0x2d33dc0) at
thread/qthread_unix.cpp:349
#11 0x7f55bd129184 in start_thread (arg=0x7f559833c700) at
pthread_create.c:312
#12 0x7f55bf60b03d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f55c45b27c0 (LWP 3277)):
[KCrash Handler]
#6  count (this=0x10) at /usr/include/qt4/QtCore/qmap.h:390
#7  connectionCount (this=0x0) at ../../src/connectionmanager.h:32
#8  MainWindow::confirmQuit (this=this@entry=0x2ba8aa0) at
../../src/mainwindow.cpp:564
#9  0x0047a176 in MainWindow::queryClose (this=0x2ba8aa0) at
../../src/mainwindow.cpp:632
#10 0x7f55c1ac806c in KMainWindow::closeEvent (this=0x2ba8aa0,

[konversation] [Bug 252081] Konversation crashed upon quit [@ connectionCount]

[Eli MacKenzie]

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

Eli MacKenzie  changed:

   What|Removed |Added

 CC||tomlukeyw...@fastmail.co.uk

--- Comment #18 from Eli MacKenzie  ---
*** Bug 391306 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 388353] Scrolling with the touchpad is too fast

[Henrik Fehlauer]

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

--- Comment #9 from Henrik Fehlauer  ---
I'm not sure how a fix in Plasmashell can possibly affect Gwenview, but if you
think moving it there helps resolving it faster…

In my book it's either a libinput/Qt related issue, or it has to be solved
separately in every app.

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

[okular] [Bug 391363] okular crashes when refreshing deleted document

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||rk...@lab12.net

--- Comment #1 from Henrik Fehlauer  ---
Thanks for the report, but cannot reproduce.

Does this happen for every file and every storage location? Which Okular +
Poppler version is this? Could you provide a backtrace?

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

[plasmashell] [Bug 391339] Cannot use arrow keys in the alt+tab window

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

Product|kwin|plasmashell
   Target Milestone|--- |1.0
   Assignee|kwin-bugs-n...@kde.org  |plasma-b...@kde.org
  Component|effects-tabbox  |Look & Feel package
 CC||plasma-b...@kde.org

--- Comment #2 from Martin Flöser  ---
Reassigning to the long package which needs to implement it in qml.

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

[okular] [Bug 381328] Okular crashes when editing forms in a PDF that's located inside an archive

[Henrik Fehlauer]

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

--- Comment #5 from Henrik Fehlauer  ---
Would "protocol" be a more appropriate terminology? Regardless, let's focus on
the crash in this bug.

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

[Spectacle] [Bug 391299] Rectangular Region: Remember selected area by default

[Henrik Fehlauer]

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

--- Comment #5 from Henrik Fehlauer  ---
>> Personally, I'm not in favor
> Could you detail what the problem is if we did make it the default? So far
> your commment does not contain anything we could try to tackle to make any
> perceived problem go away.
Ping. You are avoiding to analyse the root issue ;)

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

[kwin] [Bug 391341] In wayland, Alt+Tab closes the entire environment

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
(In reply to Michail Vourlakos from comment #2)
> > We need a backtrace
> 
> I could provide but I dont know how to catch it for kwin_wayland! :) any
> ideas?
Gdb in from another system

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

[kwin] [Bug 391349] Plastik window decoration lacks rounded edges

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
No

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

--- Comment #32 from David Mattatall  ---
Here's my valgrind output.

It's absolutely massive, I hope it's useful.
https://we.tl/2rAd4UrD49

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

--- Comment #31 from David Mattatall  ---
Here's my valgrind output.

It's absolutely massive, I hope it's useful.
https://we.tl/2rAd4UrD49

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

[Falkon] [Bug 391370] New: bundled qtsingleapplication

[David Geiger]

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

Bug ID: 391370
   Summary: bundled qtsingleapplication
   Product: Falkon
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: geiger.david68...@gmail.com
  Target Milestone: ---

Hi,

For now falkon uses only a bundled qtsingleapplication from source, so Is it
possible to propose two choices, please? first, as it is, using the bundled one
and the second using the system one.

- use bundled qtsingleappliction
- use system qtsingleapplication

Regards,
David

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

[krusader] [Bug 390994] [dev] Compiler warnings with gcc-6.4.0

[Nikita Melnichenko]

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

--- Comment #3 from Nikita Melnichenko  ---
Git commit dd7d756f65137ccaf0df7b126fd375201f86c061 by Nikita Melnichenko.
Committed on 02/03/2018 at 07:04.
Pushed by melnichenko into branch 'master'.

Fixed a crash when browsing dirs with malformed symlinks

Two major changes for improved stability:
* check the status of lstat and show a "broken" file entry
* use new readLinkSafely function which does not consider stat_p.st_size
but gradually increases buffer until the link destination path fits into
the buffer - this helps in case st_size contains garbage
(some network fs don't care about setting the right size)

As a complementary bonus, the change fixes the following warning:
filesystem.cpp:239:35: warning: variable length array ‘buffer’ is used

FIXED: [ 389413 ] Krusader crashes when entering directories with read errors
Related: bug 389413

Differential Revision: https://phabricator.kde.org/D10761

M  +8-0krusader/FileSystem/fileitem.cpp
M  +3-1krusader/FileSystem/fileitem.h
M  +58   -23   krusader/FileSystem/filesystem.cpp
M  +4-1krusader/FileSystem/filesystem.h

https://commits.kde.org/krusader/dd7d756f65137ccaf0df7b126fd375201f86c061

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

[krusader] [Bug 389413] Krusader crashes when entering directories with read errors

[Nikita Melnichenko]

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

Nikita Melnichenko  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/kru
   ||sader/dd7d756f65137ccaf0df7
   ||b126fd375201f86c061
 Resolution|--- |FIXED

--- Comment #16 from Nikita Melnichenko  ---
Git commit dd7d756f65137ccaf0df7b126fd375201f86c061 by Nikita Melnichenko.
Committed on 02/03/2018 at 07:04.
Pushed by melnichenko into branch 'master'.

Fixed a crash when browsing dirs with malformed symlinks

Two major changes for improved stability:
* check the status of lstat and show a "broken" file entry
* use new readLinkSafely function which does not consider stat_p.st_size
but gradually increases buffer until the link destination path fits into
the buffer - this helps in case st_size contains garbage
(some network fs don't care about setting the right size)

As a complementary bonus, the change fixes the following warning:
filesystem.cpp:239:35: warning: variable length array ‘buffer’ is used

FIXED: [ 389413 ] Krusader crashes when entering directories with read errors
Related: bug 390994

Differential Revision: https://phabricator.kde.org/D10761

M  +8-0krusader/FileSystem/fileitem.cpp
M  +3-1krusader/FileSystem/fileitem.h
M  +58   -23   krusader/FileSystem/filesystem.cpp
M  +4-1krusader/FileSystem/filesystem.h

https://commits.kde.org/krusader/dd7d756f65137ccaf0df7b126fd375201f86c061

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

[kde] [Bug 391332] plasmashell crash when selecting the wallpaper settings

[Bhushan Shah]

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

Bhushan Shah  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 391369] plasmashell crashes when reordering tasks

[Bhushan Shah]

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

Bhushan Shah  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
Product|kde |plasmashell
Version|unspecified |master
 CC||plasma-b...@kde.org
  Component|general |Task Manager
   Assignee|unassigned-b...@kde.org |h...@kde.org

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

[kde] [Bug 391369] New: plasmashell crashes when reordering tasks

[Bhushan Shah]

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

Bug ID: 391369
   Summary: plasmashell crashes when reordering tasks
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bhus...@gmail.com
  Target Milestone: ---

Application: plasmashell (5.12.80)
 (Compiled from sources)
Qt Version: 5.10.1
Frameworks Version: 5.44.0
Operating System: Linux 4.15.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

- I tried to reorder the tasks using drag and drop
- this resulted in crash

Note that I am using wayland session

The crash can be reproduced every time.

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

Thread 20 (Thread 0x7fe2111d3700 (LWP 1436)):
#0  0x7fe2f420f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe2f5b9802c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe24c4722a5 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x563de010c9f0, th=0x563de00c63f0) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:594
#3  0x7fe24c471f26 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x563de010c9f0, th=0x563de00c63f0, threadWasBusy=false,
suspendIfInactive=false, justReturning=false) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:554
#4  0x7fe24c47ba68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563ddd095fd0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/workinghardstate.cpp:66
#5  0x7fe24c472079 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563de010c9f0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:568
#6  0x7fe24c47bb6b in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563ddd095fd0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/workinghardstate.cpp:73
#7  0x7fe24c472079 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563de010c9f0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:568
#8  0x7fe24c47bb6b in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563ddd095fd0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/workinghardstate.cpp:73
#9  0x7fe24c472079 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563de010c9f0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:568
#10 0x7fe24c47bb6b in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563ddd095fd0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/workinghardstate.cpp:73
#11 0x7fe24c472079 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563de010c9f0, th=0x563de00c63f0, wasBusy=false) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:568
#12 0x7fe24c47bb6b in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563ddd095fd0, th=0x563de00c63f0, wasBusy=true) at
/home/bshah/kdesrc/source/threadweaver/src/workinghardstate.cpp:73
#13 0x7fe24c472079 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x563de010c9f0, th=0x563de00c63f0, wasBusy=true) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:568
#14 0x7fe24c477a1d in ThreadWeaver::Thread::run() (this=0x563de00c63f0) at
/home/bshah/kdesrc/source/threadweaver/src/thread.cpp:103
#15 0x7fe2f5b96b4d in  () at /usr/lib/libQt5Core.so.5
#16 0x7fe2f420908c in start_thread () at /usr/lib/libpthread.so.0
#17 0x7fe2f4f3be7f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fe2119d4700 (LWP 1435)):
#0  0x7fe2f420f3bd in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe2f5b9802c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe24c4722a5 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x563de010c9f0, th=0x563de03c2ff0) at
/home/bshah/kdesrc/source/threadweaver/src/weaver.cpp:594
#3  0x7fe24c471f26 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x563de010c9f0, th=0x563de03c2ff0, threadWasBusy=false,

[choqok] [Bug 391276] Fedora's Choqok packaging has invalid appStream file

[bugzilla_noreply]

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

--- Comment #4 from evo8...@gmail.com ---
Thanks, I've created Bug report 1551266 on the Red Hat bugzilla, and linked
this bug to it.

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

[krita] [Bug 391368] New: Gradient button in scratchpad crash

[Scott Petrovic]

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

Bug ID: 391368
   Summary: Gradient button in scratchpad crash
   Product: krita
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: scottpetro...@gmail.com
  Target Milestone: ---

I am on my surface pro 4 building from source. Clicking the gradient button on
the scratchpad is crashing krita. Dr. Mingw doesn't have anything, I attached a
debugger to Krita and this is the last step I could see before my QtCreator
locked up.

kis_scratch_pad.cpp: 489

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

[Spectacle] [Bug 391299] Rectangular Region: Remember selected area by default

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
> Another option would be to make the checkbox to turn off remembering easily 
> accessible in the overlay UI.

Now *that* I would approve of! Putting settings closer to the features they
touch if often a good idea, and I think it makes a lot of sense here. If we do
this, we probably don't need to enable it by default because it will completely
discoverable and obvious for the people with use cases that could benefit from
it.

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

[krita] [Bug 310554] Occasional crash when deselecting

[Sam Hagin]

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

Sam Hagin  changed:

   What|Removed |Added

   Platform|unspecified |Windows CE
 OS|All |MS Windows

--- Comment #3 from Sam Hagin  ---
Selecting color deleting them then deselecting then it cause Krita to become
unresponsive then crashed.

Error occurred on Saturday, March 3, 2018 at 22:03:46.

krita.exe caused an Access Violation at location 7FF9D01C8892 in module
Qt5Core.dll Writing to location 000C.

AddrPC   Params
7FF9D01C8892 7FF9CEEF5F93 7FF9D0500120  
Qt5Core.dll!0x28892 QBasicMutex::unlockInternal+0x12
7FF9CEBA9814 005FB460 005FB508 005FB508 
libkritaui.dll!0x289814 KisDocument::initiateSavingInBackground+0x234
7FF9CEBA99D3  7FF9C9314201 0001000A 
libkritaui.dll!0x2899d3 KisDocument::exportDocumentImpl+0x103
7FF9CEBA9D41 005FB7F0 7FF9CE9754CE  
libkritaui.dll!0x289d41 KisDocument::saveAs+0x81
7FF9CEBA9E20 005FB740  1272DE80 
libkritaui.dll!0x289e20 KisDocument::save+0x60
7FF9CEBCDA69  7FF9CEEF1270 04C67248 
libkritaui.dll!0x2ada69 KisMainWindow::saveDocument+0x3a9
7FF9CEBCF4C4   1905FA88 
libkritaui.dll!0x2af4c4 KisMainWindow::slotFileSave+0x34
7FF9CEBD3D36 0017 28AAC6B8  
libkritaui.dll!0x2b3d36 KisMainWindow::qt_static_metacall+0x1e6
7FF9D03D317A 13922870 0018 13922870 
Qt5Core.dll!0x23317a QMetaObject::activate+0x7fa
7FF9C96E3E7E 005FBD88 7FF9D03B43F9 7FF9D0502400 
Qt5Widgets.dll!0x3e7e QAction::activate+0xfe
7FF9C96E48B3 005FFB90  0001 
Qt5Widgets.dll!0x48b3 QAction::event+0x23
7FF9C96E7B5C 005FBC28 005FBBCC 005FBD88 
Qt5Widgets.dll!0x7b5c QApplicationPrivate::notify_helper+0x9c
7FF9C96EEEB0 1272DE80 7FF9D01D273F 190580A0 
Qt5Widgets.dll!0xeeb0 QApplication::notify+0x2f0
7FF9CEB9D3A6 140261C0 0001 003FBB49 
libkritaui.dll!0x27d3a6 KisApplication::notify+0x16
7FF9D03AB1C8 189BE070 00020001  
Qt5Core.dll!0x20b1c8 QCoreApplication::notifyInternal2+0x198
7FF9CCC8B2DE 04896268 7FF9CCC5A6D5 04B4FE88 
Qt5Gui.dll!0x6b2de QShortcutMap::dispatchEvent+0xee
7FF9CCC8B4F2 000E 0120 04E8CCCE40B0 
Qt5Gui.dll!0x6b4f2 QShortcutMap::tryShortcut+0x1b2
7FF9CCC371A0 264AB2B0 7FF9EFA17C24 13A2C448 
Qt5Gui.dll!0x171a0 QWindowSystemInterface::handleShortcutEvent+0x170
7FF9CCC55515 04AD0C01 04AD0BE8  
Qt5Gui.dll!0x35515 QGuiApplicationPrivate::processKeyEvent+0x95
7FF9CCC5A6D5 02FE6440 04BFACD0 00050500 
Qt5Gui.dll!0x3a6d5 QGuiApplicationPrivate::processWindowSystemEvent+0xe5
7FF9CCC31CA0 0401 00050500  
Qt5Gui.dll!0x11ca0 QWindowSystemInterface::sendWindowSystemEvents+0x370
7FF9D03FFC96 8012  005FC4A8 
Qt5Core.dll!0x25fc96 QEventDispatcherWin32Private::sendTimerEvent+0x666
7FF9FA97B85D 032573B0 7FF9D03FF760 00050500 
USER32.dll!0xb85d UserCallWinProcCheckWow+0x2ad
7FF9FA97B1EF 005FC5D0 02FE6440 005FC5D0 
USER32.dll!0xb1ef DispatchMessageWorker+0x19f
7FF9D03FEF8B 04BFACD0 0024 0488B820 
Qt5Core.dll!0x25ef8b QEventDispatcherWin32::processEvents+0x5cb
7FF9CD5DEFC5 0080 0014 1286EA60 
qwindows.dll!0x5efc5 qt_plugin_instance+0x28e5
7FF9D03A986F  04AEB280 7FF9D0500100 
Qt5Core.dll!0x20986f QEventLoop::exec+0x13f
7FF9D03B22A7 005FFC00 005FFB90 005FFC00 
Qt5Core.dll!0x2122a7 QCoreApplication::exec+0x77
000140005EF3 0001 048C0D70 000140605980 
krita.exe!0x5ef3
0001400013F7    
krita.exe!0x13f7
0001400014FB    
krita.exe!0x14fb
7FF9F9B71FE4    
KERNEL32.DLL!0x11fe4 BaseThreadInitThunk+0x14
7FF9FC19EFC1    
ntdll.dll!0x6efc1 RtlUserThreadStart+0x21

00014000-000140615000 krita.exe
7FF9FC13-7FF9FC31 ntdll.dll 6.2.16299.248
7FF9F9B6-7FF9F9C0E000 KERNEL32.DLL  6.2.16299.15
7FF9F8F4-7FF9F91A6000 KERNELBASE.dll6.2.16299.248
7FF9EAE3-7FF9EAE7C000 SuperShieldHookCpy64.dll  

[krita] [Bug 310554] Occasional crash when deselecting

[Sam Hagin]

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

Sam Hagin  changed:

   What|Removed |Added

 CC||randallha...@gmail.com

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[H L Prasad]

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

H L Prasad  changed:

   What|Removed |Added

 CC||hlpr...@gmail.com

--- Comment #30 from H L Prasad  ---
I am also facing the same issue. I'm using KDE Neon User Edition with
kdeconnect version 1.2.1-0neon+16.04+xenial+build31, on laptop, and kdeconnect
app v1.7.1 on Android. I observed that if I disable 'Receive Notifications' on
KDEConnect android, then this crash of kdeconnectd does not happen on my
laptop.

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

[frameworks-kio] [Bug 391367] New: KIO 5.43: FTBFS with musl libc on 64-bit platforms

[awilfox]

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

Bug ID: 391367
   Summary: KIO 5.43: FTBFS with musl libc on 64-bit platforms
   Product: frameworks-kio
   Version: 5.43.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

musl is strictly POSIX conformant, which means it uses int for msg_iovlen and
socklen_t for msg_controllen in the msghdr struct.  (See
http://git.musl-libc.org/cgit/musl/commit/arch/x86_64/bits/socket.h?id=7168790763cdeb794df52be6e3b39fbb021c5a64
for more information.)

POSIX defines msghdr as containing "at least" the standard members.  (See
http://pubs.opengroup.org/onlinepubs/009696699/basedefs/sys/socket.h.html for
citation.)

Since the new shared fd code in KIO (non-conformantly) assumes the members and
layout of msghdr in its ctor, it FTBFS on 64-bit musl platforms (including
x86_64, ppc64, aarch64):

In file included from
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/fdreceiver.cpp:23:0:
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h: In
constructor 'FDMessageHeader::FDMessageHeader()':
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:37:
error: invalid conversion from 'char (*)[24]' to 'int' [-fpermissive]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
 ^
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:55:
error: invalid conversion from 'long unsigned int' to 'void*' [-fpermissive]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
   ^~~~
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:66:
warning: missing initializer for member 'msghdr::__pad2'
[-Wmissing-field-initializers]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
  ^
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:66:
warning: missing initializer for member 'msghdr::msg_flags'
[-Wmissing-field-initializers]

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

[kdevelop] [Bug 391324] KDevelor crash upon restoring session

[bugzilla_noreply]

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

--- Comment #1 from kdebugtrac...@impulseforge.com ---
Crash no longer occurs once restarting Kdevelop and clearing cache.

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

[krusader] [Bug 388420] Dotted line artifact when switching focused item

[Eirikl]

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

--- Comment #10 from Eirikl  ---
Created attachment 69
  --> https://bugs.kde.org/attachment.cgi?id=69=edit
.config/krusaderrc

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

[kde] [Bug 194694] No access to camera, Unknown Error 50, Unspecified Error

[Ben Creasy]

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

Ben Creasy  changed:

   What|Removed |Added

 CC||b...@bencreasy.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #2 from Ben Creasy  ---
Please let us know if this is still happening.

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

[frameworks-kcoreaddons] [Bug 391366] plasma-desktop doesn't build with git master

[Bhushan Shah]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||kosse...@kde.org

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

[frameworks-kcoreaddons] [Bug 391366] New: plasma-desktop doesn't build with git master

[Bhushan Shah]

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

Bug ID: 391366
   Summary: plasma-desktop doesn't build with git master
   Product: frameworks-kcoreaddons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: bhus...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

CMake Error: File /usr/lib64/cmake/KF5Init/kde5init_dummy.cpp.in does not
exist.
CMake Error at /opt/kde/lib64/cmake/KF5Init/KF5InitMacros.cmake:19
(configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  kaccess/CMakeLists.txt:10 (kf5_add_kdeinit_executable)


CMake Error at kaccess/CMakeLists.txt:12 (target_link_libraries):
  Cannot specify link libraries for target "kdeinit_kaccess" which is not
  built by this project.


I had to revert : 2af64ee1e2953fb0db58885bb093897ea38972f3 locally to get it
built

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

[dolphin] [Bug 65701] sound choosing as icon choosing

[Ben Creasy]

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

Ben Creasy  changed:

   What|Removed |Added

  Component|general |general
   Assignee|unassigned-b...@kde.org |dolphin-bugs-n...@kde.org
 CC||b...@bencreasy.com,
   ||elvis.angelac...@kde.org
Product|kde |dolphin

--- Comment #1 from Ben Creasy  ---
This seems like it might be a Dolphin thing since that's the file manager? I'm
sending it over there in hopes that it might get more attention. Feel free to
move it back if that's mistaken.

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

[krita] [Bug 345074] Gradient color stops get deleted by clicking on them

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Scott Petrovic  ---
Thanks for updating this... closing

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

[Discover] [Bug 391365] New: Regression from 5.12: App page's Install button no longer turns into a progress bar and cancel button when clicked

[Nate Graham]

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

Bug ID: 391365
   Summary: Regression from 5.12: App page's Install button no
longer turns into a progress bar and cancel button
when clicked
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

With Discover's fancy new Kirigami-based toolbar, when you're on the App page
and you click on the Install button, it's no longer replaced with with a
progress bar and a cancel button the way the old button was. Instead, it just
disappears during the installation.

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

[frameworks-plasma] [Bug 391343] Screen edge effect broken with glowbar.svgz

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kwin] [Bug 391339] Cannot use arrow keys in the alt+tab window

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
  Component|general |effects-tabbox
 CC||n...@kde.org
Product|Breeze  |kwin

--- Comment #1 from Nate Graham  ---
How is using the arrow keys faster if your finger is already necessarily under
the tab key? if you miss, you can go back with ctrl-shift-tab.

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

[kmymoney] [Bug 391364] New: Reconciliation completion does not then revert window to normal account ledger view.

[Steffie . . .]

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

Bug ID: 391364
   Summary: Reconciliation completion does not then revert window
to normal account ledger view.
   Product: kmymoney
   Version: 5.0.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: stef...@vivaldi.net
  Target Milestone: ---

In KMM 4.8.1, once i successfully completed any account reconciliation process,
the KMM window would revert to the standard ledger view for that now-reconciled
account [once i closed the popup reconciliation report window]. 

In v5.0 that view-reversion does not occur, for 100% of the times i have done
reconciliation in v 5. Instead a broken [or maybe "empty" might be a better
description] reconciliation view remains on-screen [once i close the popup
reconciliation report window], usually now with no entries. My workaround is to
leave Ledger-view altogether [eg, back to Home], then manually return to the
Ledger, which then behaves correctly. Not always, but sometimes, this
workaround causes KMM to crash.

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

[kate] [Bug 391353] Drag and drop crashes applications in wayland

[Michael D]

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

Michael D  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 390435] Plasma crashed, and after rebooting many things aren't working.

[Mina]

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

--- Comment #3 from Mina <842m...@gmail.com> ---
It should be reproducible but I uninstalled the system. I replaced it with kde
neon.

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

[Breeze] [Bug 355447] Mouse cursor theme partially fails on first login with new user account

[Martin Walch]

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

Martin Walch  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Walch  ---
(In reply to Edmund Kasprzak from comment #4)
> Can you recreate it on a more recent version of your distribution?

No, I can not recreate it any more with recent packages. This seems to be
fixed. (Downstream I guess?)

Anyway, it is fixed, so I close this bug.

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

[konsole] [Bug 358083] Modifying the default profile does not work

[Wolfgang Bauer]

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

--- Comment #8 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #7)
> Maybe related to bug#390629 (or maybe not)
Might also be related to bug#389725 ...

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

[neon] [Bug 379721] neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|INVALID |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #8 from Nate Graham  ---
Not sure this bug should be marked RESOLVED INVALID. It seems that from a
normal user perspective, the issue persists.

Can we investigate substituting the gstreamer backend when the phonon backend
is requested to be removed? It's really not a great user experience to have
your system blown up when you uninstall a common and popular piece of software
like VLC.

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

[choqok] [Bug 391276] Fedora's Choqok packaging has invalid appStream file

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DOWNSTREAM
 Status|NEEDSINFO   |RESOLVED
Summary|Choqok does not look good   |Fedora's Choqok packaging
   |in discover |has invalid appStream file

--- Comment #3 from Nate Graham  ---
Yep, that'll do it. However, the version in our source repo[1] seems fine:

$  appstreamcli validate ~/org.kde.choqok.appdata.xml
I - org.kde.choqok.appdata.xml:org.kde.choqok.desktop:46
The component summary should not end with a "." [Cliente para
microblogues.]

Validation was successful: infos: 1


It also has a screenshot, a Description tag, a Summary tag, and a variety of
other bits that should make it look great in Discover. This is a Fedora
packaging issue; please file a bug on their bug tracker asking them to use our
upstream AppData file instead of the invalid one that they're using.



[1] https://cgit.kde.org/choqok.git/plain/choqok/org.kde.choqok.appdata.xml

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

[konsole] [Bug 358083] Modifying the default profile does not work

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

Version|17.12.2 |unspecified
   Platform|Archlinux Packages  |unspecified
  Component|font|general

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

[konsole] [Bug 358083] Modifying the default profile does not work

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Wolfgang Bauer  ---
(In reply to Sergio Torres Soldado from comment #6)
> This still happens for me, specifically I wan't to set the font to bold.

This bug report was about profile changes were not saved at all.

In your case they are saved obviously, just setting the font to bold apparently
doesn't work somehow.

Maybe related to bug#390629 (or maybe not), but definitely a completely
different problem than I originally reported here.

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

[choqok] [Bug 391276] Choqok does not look good in discover

[bugzilla_noreply]

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

--- Comment #2 from evo8...@gmail.com ---
I need to figure out where the AppStream file in Fedora is stored, but the one
included with the source downloaded from the Choqok website seems to get an
error:

$ appstreamcli validate org.kde.choqok.appdata.xml 
E - org.kde.choqok.appdata.xml:org.kde.choqok.desktop
The component is missing a summary ( tag).

Validation failed: errors: 1, pedantic: 1

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

[Discover] [Bug 390480] Discover software Center crashes when clicking settings

[Christoph Feck]

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

--- Comment #12 from Christoph Feck  ---
See also bug 379721.

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

[digikam] [Bug 391340] Mysql Migration fails (makeUpdates 8 to 9)

[bugzilla_noreply]

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

--- Comment #2 from danielbl...@gmail.com ---
Ok, I will do that, thank you.

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

[Discover] [Bug 137243] WISH KDE4: You need XYZ, would you like to install it? (Integration between Apps and Package Managers)

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #9 from Aleix Pol  ---
Most of these things are already being done.

For starters we have appstream urls, so any application can easily trigger a
url that will show the software center with the relevant package to install.

Also GStreamer has had a similar system for packages.

In any case, I suggest opening issues for every issue: we have mechanisms to do
that, if this should be done anywhere, let's look into the issue.

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

[juk] [Bug 391308] Provide option to hide menu bar

[Michael D]

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

--- Comment #2 from Michael D  ---
Fantastic! Fastest wish implementation ever! Thanks!

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #11 from Zakhar  ---
It was enabled without me knowing it. Is there a bug to fix zooming with trim
margins enabled?

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

[okular] [Bug 391363] New: okular crashes when refreshing deleted document

[Andrius Štikonas]

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

Bug ID: 391363
   Summary: okular crashes when refreshing deleted document
   Product: okular
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: andr...@stikonas.eu
  Target Milestone: ---

Okular crashes here when I:

1) Open PDF file
2) delete it
3) Click F5 in Okular

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

[Discover] [Bug 390480] Discover software Center crashes when clicking settings

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #11 from Nate Graham  ---
Great, thanks for the information. Let's open new bugs about subsequent issues.

FYI, the issue of VLC uninstalling the whole world when removed is a packaging
bug in Neon, and I would encourage you to file a bug there if you can still
reproduce it.

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

[okular] [Bug 381328] Okular crashes when editing forms in a PDF that's located inside an archive

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #4 from Albert Astals Cid  ---
Henrik where did you get a zip ioslave from?

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

[okular] [Bug 386111] Selecting text moves it one pixel towards the bottom

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Albert Astals Cid  ---
yes, i can reproduce when using QT_SCALE_FACTOR=1.5

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

[kdebugsettings] [Bug 390752] Kdebugsettings overwrites default debug level for all log categories

[Stefan Brüns]

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

--- Comment #7 from Stefan Brüns  ---
Thanks a lot!
I saw you also made some adjustments to qDebug usage in kdepim and oauth, very
welcome as well!

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Albert Astals Cid]

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

--- Comment #10 from Albert Astals Cid  ---
(In reply to Zakhar from comment #9)
> Just found were trim margins is disabled it and no issue. 

You mean you had it enabled and when you disabled it the bug is gone?

> This IS a
> legitimate bug, the least that can be done is ship Okular with trim margins
> disabled.

Trim Margins is disabled by default, you must have enabled it at some point.

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

[kwin] [Bug 391341] In wayland, Alt+Tab closes the entire environment

[Michail Vourlakos]

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

--- Comment #2 from Michail Vourlakos  ---
> We need a backtrace

I could provide but I dont know how to catch it for kwin_wayland! :) any ideas?

> I assume it's the very common crash in the radeon driver caused from 
> somewhere in QtQuick.

I have an Optimus laptop that uses i915+nouveau :)

1.VGA compatible controller: Intel Corporation Skylake Integrated Graphics
2.NVIDIA Corporation GM107M


very happy to have manage finally to make it work with wayland :).

I suppose it is the nouveau driver because I use an external monitor with it
and I have disabled the laptop screen.

I dont use neither bumblebee or optimus things...

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

[amarok] [Bug 391362] New: Amarok crash on start

[Jonathan]

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

Bug ID: 391362
   Summary: Amarok crash on start
   Product: amarok
   Version: 2.8.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: jonat...@schots-alsuguren.com
  Target Milestone: 2.9

Application: amarok (2.8.0)

Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.15.7-1-ck-piledriver x86_64
Distribution (Platform): Archlinux Packages

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

Start amarok, crash everytime attempt to launch it.

Distribution: Arch

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe08ffb7b40 (LWP 8063))]

Thread 3 (Thread 0x7fe038423700 (LWP 8066)):
#0  0x7fe08b7a5786 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe042bc2308 in  () at /usr/lib/libmysqld.so.18
#2  0x7fe042b6f61b in  () at /usr/lib/libmysqld.so.18
#3  0x7fe08b79f08c in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fe08cc2de7f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe05927f700 (LWP 8065)):
#0  0x7fe08cc1f3d8 in read () at /usr/lib/libc.so.6
#1  0x7fe077a857c2 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-11.1.so
#2  0x7fe083e3c7af in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7fe083e3d241 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7fe083e3d301 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7fe083e4b6ae in  () at /usr/lib/libpulse.so.0
#6  0x7fe077ab581c in  () at /usr/lib/pulseaudio/libpulsecommon-11.1.so
#7  0x7fe08b79f08c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fe08cc2de7f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe08ffb7b40 (LWP 8063)):
[KCrash Handler]
#6  0x7fe07490cc02 in get_charset () at /usr/lib/libsmbconf.so.0
#7  0x7fe0429e7242 in thd_init_client_charset(THD*, unsigned int) () at
/usr/lib/libmysqld.so.18
#8  0x7fe04296c154 in check_embedded_connection () at
/usr/lib/libmysqld.so.18
#9  0x7fe042974b09 in mysql_real_connect () at /usr/lib/libmysqld.so.18
#10 0x7fe058877a85 in MySqlEmbeddedStorage::MySqlEmbeddedStorage(QString
const&) () at /usr/lib/kde4/amarok_collection-mysqlecollection.so
#11 0x7fe058876a07 in  () at
/usr/lib/kde4/amarok_collection-mysqlecollection.so
#12 0x7fe08f8d9834 in
CollectionManager::loadPlugins(QList const&)
() at /usr/lib/libamaroklib.so.1
#13 0x7fe08f8d9cc9 in
CollectionManager::handleNewFactories(QList const&) ()
at /usr/lib/libamaroklib.so.1
#14 0x7fe08f9f164b in Plugins::PluginManager::init() () at
/usr/lib/libamaroklib.so.1
#15 0x7fe08f9f1d4d in Plugins::PluginManager::PluginManager(QObject*) () at
/usr/lib/libamaroklib.so.1
#16 0x7fe08f9f1e67 in Plugins::PluginManager::instance() () at
/usr/lib/libamaroklib.so.1
#17 0x7fe08f9e3da7 in MainWindow::MainWindow() () at
/usr/lib/libamaroklib.so.1
#18 0x7fe08f9c986b in App::continueInit() () at /usr/lib/libamaroklib.so.1
#19 0x7fe08f9caaba in App::App() () at /usr/lib/libamaroklib.so.1
#20 0x5603931e4e80 in  ()
#21 0x7fe08cb58f4a in __libc_start_main () at /usr/lib/libc.so.6
#22 0x5603931e6bfa in _start ()

Possible duplicates by query: bug 369494.

Reported using DrKonqi

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

[Discover] [Bug 390480] Discover software Center crashes when clicking settings

[Bruce]

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

--- Comment #10 from Bruce  ---
(In reply to Aleix Pol from comment #9)
> Please reopen when you have more information.

Hi Aleix, I think it was part user error a while back I wanted to use VLC as a
snap so I thought I would uninstall VLC that came natively, it did ask me to
uninstall other packages besides VLC and I was not thinking at the time and it
uninstalled a bunch of other stuff such as discover had to do apt install
neon-desktop to get everything back. That was when I started getting that error
there are still a couple glitches in discover but nothing worth reinstalling
the operating system for. I still use discover to do my updates and I am still
using the same install of neon.

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #9 from Zakhar  ---
Just found were trim margins is disabled it and no issue. This IS a legitimate
bug, the least that can be done is ship Okular with trim margins disabled.

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

[Discover] [Bug 390148] No feedback when I try to add an invalid source URI/URL

[Nate Graham]

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

--- Comment #10 from Nate Graham  ---
I've submitted a patch that fixes all of the above-mentioned issues:
https://phabricator.kde.org/D11003

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

[ark] [Bug 391361] New: Ark with Dolphin integration does not display compression progress dialog

[Zakhar]

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

Bug ID: 391361
   Summary: Ark with Dolphin integration does not display
compression progress dialog
   Product: ark
   Version: 17.12.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: zakhar.nasi...@gmail.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Steps to reproduce:
-Open Dolphin
-Righ Click on directory big enough so ark takes at least 45seconds to compress
-Select Compress --> any item

Results: No progress dialog

This is horrible when selecting a large directory causing me to revert to
command line with verbose output.

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

[juk] [Bug 391308] Provide option to hide menu bar

[Michael Pyne]

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

Michael Pyne  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/juk
   ||/32597af7dd02e42a1c2095b7d1
   ||26caec987ab8ab
   Version Fixed In||18.04
 Resolution|--- |FIXED

--- Comment #1 from Michael Pyne  ---
Git commit 32597af7dd02e42a1c2095b7d126caec987ab8ab by Michael Pyne.
Committed on 03/03/2018 at 22:56.
Pushed by mpyne into branch 'master'.

Enable the standard "show menu bar" action.

As nicely requested in bug 391308.
FIXED-IN:18.04

M  +2-0juk.cpp
M  +2-1jukui-rtl.rc
M  +2-1jukui.rc

https://commits.kde.org/juk/32597af7dd02e42a1c2095b7d126caec987ab8ab

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Albert Astals Cid]

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

--- Comment #8 from Albert Astals Cid  ---
(In reply to Zakhar from comment #5)
> No, not to my knowledge.

Maybe your knowledge is wrong, could you please check?

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #6 from Zakhar  ---
The first page is the non zoom out page.

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #7 from Zakhar  ---
Rest of the pages seem to work well.

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #5 from Zakhar  ---
No, not to my knowledge.

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

[kde] [Bug 391360] New: crash when there is a gap in the video track

[bugzilla_noreply]

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

Bug ID: 391360
   Summary: crash when there is a gap in the video track
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: steven...@gmail.com
  Target Milestone: ---

Application: kdenlive (17.12.1)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.14.22-1-desktop x86_64
Distribution: "openSUSE Leap 42.3"

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

editing a video (1 video + 1 audio track) the video track has a gap about 1 sec
and starts with a transition

The crash can be reproduced every time.

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

Thread 45 (Thread 0x7f8b0eff5700 (LWP 26885)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 44 (Thread 0x7f8b0f7f6700 (LWP 26884)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 43 (Thread 0x7f8b0fff7700 (LWP 26883)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 42 (Thread 0x7f8b30808700 (LWP 26882)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 41 (Thread 0x7f8b31009700 (LWP 26881)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 40 (Thread 0x7f8b3180a700 (LWP 26880)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 39 (Thread 0x7f8b3200b700 (LWP 26879)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f8b3280c700 (LWP 26878)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f8b33ff7700 (LWP 26877)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8ba75d82be in  () at /usr/lib64/libavcodec.so.57
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f8b337f6700 (LWP 26876)):
#0  0x7f8bd2c8d0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8b9af0b373 in  () at /usr/lib64/mlt-6/libmltsdl.so
#2  0x7f8bd2c88724 in start_thread () at /lib64/libpthread.so.0
#3  0x7f8bd44cce8d in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f8b34807700 (LWP 26875)):
#0  0x7f8bcb48f2a2 in pa_queue_pop () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#1  0x7f8bcb48dcbe in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f8bcb48ebed in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#3  0x7f8bcb48efad in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#4  0x7f8bcb48f84a in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#5  0x7f8bceba5a14 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0
#6  0x7f8bceba5dea in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#7  0x7f8b9a228a7b in  () at /usr/lib64/libSDL-1.2.so.0
#8  0x7f8b9a1fc3b0 in  () at /usr/lib64/libSDL-1.2.so.0
#9  

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Albert Astals Cid]

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

--- Comment #4 from Albert Astals Cid  ---
I can mouse wheel zoom just fine in that file.

Ah wait are you using Trim Margins? Don't do that, it's buggy.

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

[plasmashell] [Bug 391359] System Monitor Plasma Widgets break rendering in Plasma Shell

[Dan]

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

Dan  changed:

   What|Removed |Added

 CC||dan.f.k...@gmail.com

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

[plasmashell] [Bug 391359] New: System Monitor Plasma Widgets break rendering in Plasma Shell

[Dan]

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

Bug ID: 391359
   Summary: System Monitor Plasma Widgets break rendering in
Plasma Shell
   Product: plasmashell
   Version: 5.12.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: dan.f.k...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 68
  --> https://bugs.kde.org/attachment.cgi?id=68=edit
Broken rendering in plasmashell

Widgets part of org.kde.plasma.systemmonitor seem to break rendering when added
to plasmashell after my latest update.

Version of Plasma installed:
extra/plasma-desktop 5.12.2-1 (plasma) [installed]
KDE Plasma Desktop
extra/plasma-framework 5.43.0-1 (kf5) [installed]
Plasma library and runtime components based upon KF5 and Qt5


The only widget that appears to not break rendering is Disk Usage. Everything
else will cause the widget appearance to turn completely black. This rendering
bug persists after removing the widget, but if the widget is removed and you
stop and start a new session, rendering is restored. It occurs irrelevant of
the Desktop theme used for me. 

Attached is a screenshot.

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #3 from Zakhar  ---
Okular 17.12.2

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Zakhar]

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

--- Comment #2 from Zakhar  ---
Sure, download here because it exceeds size limit:
https://nofile.io/f/GkbszdO37C2/Pentagon+Aliens+William+Lyne.pdf

totally reproducible.

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

[plasmashell] [Bug 391358] New: Plasma crashes at login

[Gunnar]

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

Bug ID: 391358
   Summary: Plasma crashes at login
   Product: plasmashell
   Version: 5.12.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: philip.e.g.anders...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.2)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:
Starting the computer and loging in through SDDM.

- Unusual behavior I noticed:
The last few times I've booted my computer, plasma seems to crash right when it
tries to start. Adding about ten seconds to the startup time. Seems to happen
every time I boot my computer.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), 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 0x7fdb970758c0 (LWP 1488))]

Thread 14 (Thread 0x7fdac700 (LWP 1791)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdb6b4d248b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fdb6b4d2397 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7fdb8fc936ba in start_thread (arg=0x7fdac700) at
pthread_create.c:333
#4  0x7fdb906fb41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fdadea41700 (LWP 1790)):
#0  0x7ffef50c9b6d in clock_gettime ()
#1  0x7fdb90709876 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7fdadea409f0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fdb91021ed1 in qt_clock_gettime (ts=0x7fdadea409f0, clock=) at kernel/qelapsedtimer_unix.cpp:111
#3  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#4  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#5  0x7fdb910206c9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fdad0002ed0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7fdb91020c35 in QTimerInfoList::timerWait (this=0x7fdad0002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7fdb9102233e in timerSourcePrepareHelper (timeout=0x7fdadea40ac4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7fdadea40ac4) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7fdb8b5e291d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fdb8b5e32bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fdb8b5e349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7fdb910225cb in QEventDispatcherGlib::processEvents
(this=0x7fdad8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7fdb90fc964a in QEventLoop::exec (this=this@entry=0x7fdadea40c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#14 0x7fdb90de9554 in QThread::exec (this=) at
thread/qthread.cpp:522
#15 0x7fdb94b051c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7fdb90dee6eb in QThreadPrivate::start (arg=0x2f7ff90) at
thread/qthread_unix.cpp:376
#17 0x7fdb8fc936ba in start_thread (arg=0x7fdadea41700) at
pthread_create.c:333
#18 0x7fdb906fb41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fdadf242700 (LWP 1762)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdb6b4d248b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fdb6b4d2397 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7fdb8fc936ba in start_thread (arg=0x7fdadf242700) at
pthread_create.c:333
#4  0x7fdb906fb41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fdadfa43700 (LWP 1761)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdb6b4d248b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fdb6b4d2397 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7fdb8fc936ba in start_thread (arg=0x7fdadfa43700) at
pthread_create.c:333
#4  0x7fdb906fb41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fdae0244700 (LWP 1760)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdb6b4d248b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7fdb6b4d2397 in ?? () from

[kmymoney] [Bug 391357] New: Backup says "Error mounting device" when I point to my floppy backup

[Mark Hunter]

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

Bug ID: 391357
   Summary: Backup says "Error mounting device" when I point to my
floppy backup
   Product: kmymoney
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bugtracker
  Assignee: kmymoney-de...@kde.org
  Reporter: mark.s.hun...@bell.net
  Target Milestone: ---

I am working with the new version of KMyMoney 5.0.0 and when I try to do a
backup (I have been running a backup for a long time to this device), I get
"Error mounting device".
I can see the device and even "Chose" the device from the list.  I always
remove the old backup before I do a new backup, so I know the device is ok.
It seems the KMM does not see the device for some reason.
I did a search and did not find anything matching this issue.

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

[okular] [Bug 391352] Okular does not zoom out with mouser wheel.

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
Which version are you running?

Can you attach a document you have this problem with?

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

[kio-gdrive] [Bug 391356] KIO GDrive should provide file transnsfer stats for uploads and downloads

[Zakhar]

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

Zakhar  changed:

   What|Removed |Added

   Platform|Other   |Gentoo Packages

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

[kio-gdrive] [Bug 391356] New: KIO GDrive should provide file transnsfer stats for uploads and downloads

[Zakhar]

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

Bug ID: 391356
   Summary: KIO GDrive should provide file transnsfer stats for
uploads and downloads
   Product: kio-gdrive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: zakhar.nasi...@gmail.com
  Target Milestone: ---

Perhaps using the graph style as described in this bug:
https://bugs.kde.org/show_bug.cgi?id=391199

since it is already a dolphin integrated package.

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

[KBibTeX] [Bug 391355] New: kbibtex crashes immediately after startup

[Gandalf Lechner]

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

Bug ID: 391355
   Summary: kbibtex crashes immediately after startup
   Product: KBibTeX
   Version: git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: gandalflech...@gmail.com
  Target Milestone: ---

compiled from git, kbibtex crashes immediately after starting it:

Application: KBibTeX (kbibtex), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f956c2500 (LWP 6546))]

Thread 3 (Thread 0x7f3f60e94700 (LWP 6548)):
#0  0x7f3f82062640 in g_poll () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3f82053169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f8205327c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f901dd49b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3f90182e3a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3f8ffa23ca in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3f8e47de45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f3f8ffa729d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3f8315d7fc in start_thread (arg=0x7f3f60e94700) at
pthread_create.c:465
#9  0x7f3f8f8a9b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3f68a9f700 (LWP 6547)):
#0  0x7f3f8f89d951 in __GI___poll (fds=0x7f3f68a9e938, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3f81dec747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3f81dee53a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3f6a99df09 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f3f8ffa729d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3f8315d7fc in start_thread (arg=0x7f3f68a9f700) at
pthread_create.c:465
#6  0x7f3f8f8a9b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3f956c2500 (LWP 6546)):
[KCrash Handler]
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:356
#7  0x7f3f85ef6dfa in QByteArray::realloc(int) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f3f943be8f8 in QDebug::~QDebug() () from /usr/lib/libqoauth.so.1
#9  0x56001c3267f6 in main (argc=1, argv=0x7ffe4b00a238) at
/home/gandalf/down/git/kbibtex/src/program/program.cpp:62

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

[krita] [Bug 389524] Text parts outside of "frame" draw a "tracks" when the "frame" is dragged around

[bugzilla_noreply]

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

--- Comment #7 from kali...@wp.pl ---
For me it occurs both when it's on and off - only when it's off, the issue gets
worse (not only cropped parts, but also text inside the frame leaves artifacts.

I don't have the latest version though - for some reason every download from
the nightlies hangs on about 16-20% for me and won't move on...

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

[kwin] [Bug 391349] Plastik window decoration lacks rounded edges

[bugzilla_noreply]

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

--- Comment #2 from matheus4...@hotmail.com ---
(In reply to Martin Flöser from comment #1)
> Design changes, implementations changes. It's not rounded any more and that
> won't change. I'm sorry.

Is it impossible to do now?

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

[juk] [Bug 391354] New: Juk doesn't start in wayland when using the default run command

[Michael D]

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

Bug ID: 391354
   Summary: Juk doesn't start in wayland when using the default
run command
   Product: juk
   Version: 17.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: whee...@kde.org
  Reporter: nortex...@gmail.com
CC: mp...@kde.org
  Target Milestone: ---

If I run "juk" it starts just fine, but when I try to run it from the menu it
doesn't work. I don't recall what the default command is anymore because I
changed it in kmenuedit and wayland's clipboard is broken.

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

[kmymoney] [Bug 391337] KMyMoney just upgraded to 5.0.0 and it won`t let me enter a new Payee

[Mark Hunter]

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

--- Comment #2 from Mark Hunter  ---
   Ok thanks. Kind of a strange process to me but hopefully the updated
   version will have the fixes in. As of right now the old version worked
   much better and I have been using that for many years now.

   Mark Hunter
   105 Baxter Street
   Bowmanville, Ontario
   L1C 5P8
   mark.s.hun...@bell.net

 -- Original Message --
 From: Thomas Baumgart 
 Date: March 3, 2018 at 8:34 AM


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

 Thomas Baumgart  changed:

 What |Removed |Added


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

 --- Comment #1 from Thomas Baumgart  ---
 Thanks for the report. Most of the things have been reported
 before and have
 received fixes in the meantime. The resp. numbers here on b.k.o
 are 390232,
 390264 and 391048.

 Regarding the settings it has been decided to take them out.
 Please use the KDE
 tools that configure your desktop. Change the date to your locale.
 There was a
 report about the position of the currency symbol position that was
 wrong for
 certain locales. That is also corrected.

 I agree with you on the quality side. Testing efforts this time
 were at a bare
 minimum due to time constraints. 5.0.1 included the fixes is in
 the works.

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

 --
 You are receiving this mail because:
 You reported the bug.

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

[kmymoney] [Bug 390232] Don't add new payee from new operation panel

[Mark Hunter]

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

--- Comment #7 from Mark Hunter  ---
It seems as though they had something that worked quite well and made it not
work very well.  That does not seem to be much of an "upgrade".

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

[kmymoney] [Bug 390232] Don't add new payee from new operation panel

[Mark Hunter]

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

--- Comment #8 from Mark Hunter  ---
It seems as though they had something that worked quite well and made it not
work very well.  That does not seem to be much of an "upgrade".

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

[kate] [Bug 391353] New: Drag and drop crashes applications in wayland

[Michael D]

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

Bug ID: 391353
   Summary: Drag and drop crashes applications in wayland
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: nortex...@gmail.com
  Target Milestone: ---

Application: kate (17.12.2)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.15.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
Drag and drop causes KDE applications to crash. It works fine for the GTK apps
I tried, such as Firefox and Libreoffice Writer. For KDE I tried Dolphin, Kate,
Falkon, and k3b. I tried Telegram's official qt application and drag and drop
worked fine.

Plasma 5.12.1 and 5.12.2, opensuse tumbleweed.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f682d936700 (LWP 2894)):
#0  0x7f68401a3179 in poll () from /lib64/libc.so.6
#1  0x7f6839e58109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6839e5821c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6840ae0aab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f6840a879da in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f68408aebfa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6840f04a35 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f68408b3bf0 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f683bea259b in start_thread () from /lib64/libpthread.so.0
#9  0x7f68401ada1f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6845857900 (LWP 2893)):
[KCrash Handler]
#6  0x7f68329961b0 in QtWaylandClient::QWaylandScreen::display() const ()
from /usr/lib64/libQt5WaylandClient.so.5
#7  0x7f6832991938 in
QtWaylandClient::QWaylandWindow::QWaylandWindow(QWindow*) () from
/usr/lib64/libQt5WaylandClient.so.5
#8  0x7f6832996799 in
QtWaylandClient::QWaylandShmWindow::QWaylandShmWindow(QWindow*) () from
/usr/lib64/libQt5WaylandClient.so.5
#9  0x7f6832985470 in
QtWaylandClient::QWaylandIntegration::createPlatformWindow(QWindow*) const ()
from /usr/lib64/libQt5WaylandClient.so.5
#10 0x7f6841769d26 in QWindowPrivate::create(bool, unsigned long long) ()
from /usr/lib64/libQt5Gui.so.5
#11 0x7f684176b2e0 in QWindowPrivate::setVisible(bool) () from
/usr/lib64/libQt5Gui.so.5
#12 0x7f684175413f in QBasicDrag::recreateShapedPixmapWindow(QScreen*,
QPoint const&) () from /usr/lib64/libQt5Gui.so.5
#13 0x7f6841754195 in QBasicDrag::startDrag() () from
/usr/lib64/libQt5Gui.so.5
#14 0x7f68329aef4c in QtWaylandClient::QWaylandDrag::startDrag() () from
/usr/lib64/libQt5WaylandClient.so.5
#15 0x7f6841754342 in QBasicDrag::drag(QDrag*) () from
/usr/lib64/libQt5Gui.so.5
#16 0x7f6841772581 in QDragManager::drag(QDrag*) () from
/usr/lib64/libQt5Gui.so.5
#17 0x7f684176ef9a in QDrag::start(QFlags) () from
/usr/lib64/libQt5Gui.so.5
#18 0x7f6845294a80 in ?? () from /usr/lib64/libKF5TextEditor.so.5
#19 0x7f684529eea4 in ?? () from /usr/lib64/libKF5TextEditor.so.5
#20 0x7f6841fa4338 in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x7f6841f6801c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#22 0x7f6841f6f86f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#23 0x7f6840a891c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#24 0x7f6841f6e8bf in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib64/libQt5Widgets.so.5
#25 0x7f6841fbe68b in ?? () from /usr/lib64/libQt5Widgets.so.5
#26 0x7f6841fc0ab1 in ?? () from /usr/lib64/libQt5Widgets.so.5
#27 0x7f6841f6801c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#28 0x7f6841f6f314 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#29 0x7f6840a891c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#30 0x7f68417600dc in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib64/libQt5Gui.so.5
#31 0x7f6841761a25 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib64/libQt5Gui.so.5
#32 0x7f684173aeab in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib64/libQt5Gui.so.5
#33 

[okular] [Bug 391352] New: Okular does not zoom out with mouser wheel.

[Zakhar]

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

Bug ID: 391352
   Summary: Okular does not zoom out with mouser wheel.
   Product: okular
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: zakhar.nasi...@gmail.com
  Target Milestone: ---

Steps to reproduce:
-Open PDF with few pages
-Zoom out with mousewheel

Results: Does not zoom out past current zoom setting, or at least 1 step after
it.

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

[plasmashell] [Bug 391063] Memory Leak in Plasmashell

[bugzilla_noreply]

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

kde_bug_rep...@yahoo.com changed:

   What|Removed |Added

   Assignee|notm...@gmail.com   |k...@davidedmundson.co.uk
  Component|Desktop Dashboard   |general
 CC||plasma-b...@kde.org

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

[krita] [Bug 391351] New: [retro-compatibility] Text scaling issue after opening Krita 3.x *.kra

[David REVOY]

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

Bug ID: 391351
   Summary: [retro-compatibility] Text scaling issue after opening
Krita 3.x *.kra
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Created attachment 67
  --> https://bugs.kde.org/attachment.cgi?id=67=edit
[^ screenshot of the scaling issue: 3.x file in 4.0 ]

Hi,

I tried to open my old files containing texts with Krita 4.0beta. I saw a big
scaling issue (visible on the screenshot in attachment).

To reproduce, I join a zip with the Krita *.kra file and a *.jpg export done
with 3.x :
https://www.peppercarrot.com/extras/temp/2018-03-03_bug-text-scaling-krita40.zip
(7,8MB) ; The font is an open one; Yanone Kaffeesatz and you can download the
family here: https://www.dafont.com/yanone-kaffeesatz.font

Note: I'm not expecting a pixel-perfect matching between 3.x and 4.x, but a
roughly similar scaling/positioning/size would be great!

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

[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Flöser  ---
This is not a bug in KWin, but just incorrect configuration. You cannot use a
subpart of a shortcut for keyboard layout switching. That's a limitation of X
server and totally outside the control of our software stack.

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

[konsole] [Bug 358083] Modifying the default profile does not work

[Sergio Torres Soldado]

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

Sergio Torres Soldado  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
Version|unspecified |17.12.2
  Component|general |font
   Platform|Other   |Archlinux Packages
 CC||torres.sold...@gmail.com

--- Comment #6 from Sergio Torres Soldado  ---
This still happens for me, specifically I wan't to set the font to bold. The
set profile at $HOME/.local/share/konsole/ has the right settings:

"""
[Appearance]
ColorScheme=WhiteOnBlack
Font=Hack,9,-1,5,75,0,0,0,0,0,Bold

[General]
Name=New Profile
Parent=FALLBACK/
"""

But the font is always regular.

I don't know if it is relevant but looking at strace I see:

"""
close(12)   = 0
openat(AT_FDCWD, "/usr/share/fonts/TTF/Hack-Bold.ttf", O_RDONLY) = 12
fcntl(12, F_SETFD, FD_CLOEXEC)  = 0
fstat(12, {st_mode=S_IFREG|0644, st_size=318100, ...}) = 0
mmap(NULL, 318100, PROT_READ, MAP_PRIVATE, 12, 0) = 0x7f9d84154000
close(12)   = 0
openat(AT_FDCWD, "/usr/share/fonts/TTF/Hack-Regular.ttf", O_RDONLY) = 12
fcntl(12, F_SETFD, FD_CLOEXEC)  = 0
"""

As expected overwriting the actual font file is the workaround I am currently
using..

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

[kwin] [Bug 391349] Plastik window decoration lacks rounded edges

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
Design changes, implementations changes. It's not rounded any more and that
won't change. I'm sorry.

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

[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)

[Nicola]

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

--- Comment #4 from Nicola  ---
I read upgrading the buildToolsVersion to 27 solves the problem in other apps
with the same problem. I tried to compile and test the change locally and it
worked even with kdeconnect. Compiling with:

buildToolsVersion '26.0.2': bootloop just after install
buildToolsVersion '27.0.3': works fine

I don't know if this change have some collateral effect, I'm not and Android
developer.

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

[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly

[Thomas Lübking]

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

--- Comment #2 from Thomas Lübking  ---
Thomas didn't use KDE for over 3 years...


Anyway, the actual bug is correctly identified and not at all related to kwin
(and only to a minor extent to kglobalaccel):
"Alt+Shift should only be triggerd when those keys are released"

Qt (and KDE) fires shortcuts on key presses (at least that's what it used to
be) and this also prominently blocked the usage of the meta key as menu trigger
(unless you had a specific shortcut daemon for this function running and iirc
this specific feature has recently been somehow included in kglobalaccel??)

The only solution is to make (all) global shortcuts different from local ones
(to fire on release)

Kate & Firefox are client specific issues and totally unrelated - firefox isn't
even a Qt client.

No idea about the ALt+Shift/Meta+Shift confusion, sounds like a GUI (only) bug.

Shift+Backtab is somehow a tautology, Shift+Tab is Backtab - this constantly
causes bugs in the symbol handling, but as long as it works, "Shift+Backtab" is
probably the least ambigious declaration.

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

[konsole] [Bug 345476] Ctrl+Alt+Space behaves like Ctrl+Space

[Ahmad Samir]

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

Ahmad Samir  changed:

   What|Removed |Added

 CC||a.samir...@gmail.com

--- Comment #2 from Ahmad Samir  ---
You can fine tune the escape sequences sent by key combos using the konsole key
bindings editor. Did you try that?

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

[konsole] [Bug 376770] Impossible to unbind Shift + Up/Down

[Ahmad Samir]

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

Ahmad Samir  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |RESOLVED

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

[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly

[Tore Havn]

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

--- Comment #1 from Tore Havn  ---
Added Thomas Lübking to this, as it seems from the other bug reports that he
may have a better idea of what's going on. :)

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

[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly

[Tore Havn]

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

Tore Havn  changed:

   What|Removed |Added

 CC||thomas.luebk...@gmail.com

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

[kwin] [Bug 391350] New: Shortcuts: Alt and Shift modifiers is not handled correctly

[Tore Havn]

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

Bug ID: 391350
   Summary: Shortcuts: Alt and Shift modifiers is not handled
correctly
   Product: kwin
   Version: 5.12.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: v...@veqz.net
  Target Milestone: ---

It seems the Alt+Shift modifiers do not work correctly together when using the
Tab key to walk through windows. I intiially assumed it was a hardware bug
(recently got a new laptop), but I have finally been able to get some details
of what is happening.

1.
I also have Alt+Shift set to walk through keyboard layouts. Alt+Shift+Tab is
never triggered because KWin has already triggered on Alt+Shift being pressed.
Disabling Alt+Shift to walk through keyboard layouts made Alt+Shift+Tab
function again.

The correct behaviour should be that Alt+Shift should only be triggerd when
those keys are released, and while just being pressed and held should function
as modifiers waiting for the next key to be pressed.

2.
A similar thing happens when cycling through tabs in applications.

2.1 Firefox
Ctrl+Tab will cycle through tabs, and works as it should. Ctrl+Shift+Tab
however, does not work. Holding Ctrl+Shift and hiting Tab appears to do
nothing. Continuing to hold Ctrl+Shift and hiting Tab again will bring the
focus to the address bar.

To correctly reverse cycle through tabs in Firefox, it is necessary to hold
Ctrl and hit Tab, to start the tab cycling process. By continuing to hold Ctrl
and now also holding Shift, it is possible to hit Tab to reverse cycle through
the tab list.

2.2 Kate
Holding Ctrl and hiting Tab will cycle through the open documents, as it
should. Holding Ctrl+Shift and hiting Tab, however, will start by cycling one
document forward, and then function as reverse cycling through documents.

3.
While experimenting with KWin's shortcut settings in System Settings, I noticed
a funny behaviour when trying to set a custom keyboard shortcut:

First pressing and holding Alt, and then pressing and holding Shift, will
display the shortcut as "Alt+Shift+...". A key combo like Alt+Shift+Tab can
then be set by hiting Tab.

However, by first pressing and holding Shift, and then pressing and holding
Alt, will display the shortcut as "Meta+Shift+..."! By hiting Tab it will
change to Alt+Shift+Tab again and work as before.

I don't know what is happening there, but I suspect there might be some bug in
the code which modifies Alt to appear as Meta. I'm including this here in case
it is related to the Alt+Shift bug. Utilising the Meta key in a combination
seems to make all three appear ("Meta+Alt+Shift+...").

4.
After looking through the bug tracker, I found several open, unconfirmed bugs
which I suspect are other symptoms of this bug:

- Alt + Shfit +  shortcut bug (2018)
https://bugs.kde.org/show_bug.cgi?id=391056

* kwin takes control over shortcut input and does not allow for "unshifting"
(2016) https://bugs.kde.org/show_bug.cgi?id=359206

- Keyboard layout switching ignores settings, sometimes it does not work at
all. (2016) https://bugs.kde.org/show_bug.cgi?id=370734

- Custom Alt+` shortcut brings up task switcher, but does not walk through
applications (2016) https://bugs.kde.org/show_bug.cgi?id=359141

- inconsistent behavior with alt+7 (2016)
https://bugs.kde.org/show_bug.cgi?id=365255

- Impossible to use AltGr as modifier (2016)
https://bugs.kde.org/show_bug.cgi?id=359146

- Remapping Num Lock with xmodmap breaks all Alt+* key shortcuts in KDE! O_OOO
(2015-2016) https://bugs.kde.org/show_bug.cgi?id=345816

- Shortcuts bound to F keys ignore state of ISO_Level3_Shift (2015)
https://bugs.kde.org/show_bug.cgi?id=357127

- Keyboard input shortcut keys do not work (2015)
https://bugs.kde.org/show_bug.cgi?id=348456

- Broken canvas input shortcut naming when pressing keys used to switch
keyboard layouts (2014-2017, Confirmed)
https://bugs.kde.org/show_bug.cgi?id=333431

- when connecting to a remote host, some modifier key (shift, or alt) is
permanently pressed (2014-2016) https://bugs.kde.org/show_bug.cgi?id=329951

- Ambigous shortcut detected with pressing Ctrl+Shift+w (2013-2017, Confirmed)
https://bugs.kde.org/show_bug.cgi?id=319172

- Keyboard shortcuts doesn't work if non-english keyboard layout is set before
english one (2012-2018, Confirmed) https://bugs.kde.org/show_bug.cgi?id=309193

- custom shortcuts: send keyboard input does not work for keys requiring AltGr
(2012-2018) https://bugs.kde.org/show_bug.cgi?id=295633

- Walk Through Windows (Reverse) does not work (2012-2017, Kde4+5)
https://bugs.kde.org/show_bug.cgi?id=294249

- Unsupported Key message when adding a custom Alt+Shift+ shortcut
(2012-2013) https://bugs.kde.org/show_bug.cgi?id=294245

- Alt-Tab menu cannot use Alt-Shift-Tab for going back through