[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2023-07-17 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=438883

--- Comment #70 from RobinK  ---
Re Comment # 69 - indeed.  May we know if anyone is working on it at all?

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

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2023-01-10 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=438883

--- Comment #60 from RobinK  ---
In reply to Paul Hands, Comment #58

Sorry; I've no VBox Linux guest, only Windows, and therefore can't say.

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

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2023-01-10 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=438883

--- Comment #58 from RobinK  ---
Re Comment #57, I have that version working in both Leap 15.4 and Tumbleweed,
but it's really only a demo of possibilities - which is very encouraging but
it's of limited practical use in its present form.

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

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

2022-11-26 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=443410

--- Comment #65 from RobinK  ---
Thanks.  I'll ask

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

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

2022-11-24 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=443410

--- Comment #62 from RobinK  ---
Is anyone actually working on restoring the cube, or is it dead?

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

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2022-04-24 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=438883

RobinK  changed:

   What|Removed |Added

 CC||ro...@xtra.co.nz

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

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

2021-10-18 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=443410

--- Comment #23 from RobinK  ---
(In reply to Maximilian Böhm from comment #20)
> (Please forgive my grammatical errors, writing while shedding tears is not
> the optimal circumstance for using a bugtracker.)

True; but I endorse all that you say.  I've bave been a Cube-user since before
KDE4 provided most of the effects previously provided by Compiz; and the Cube
was until its recent rejection one of the main reasons I've stayed with KDE and
Plasma ever since.  To me it's a core facility without which KDE's Desktop
Effects are merely insipid. 

I wonder where the stipulation that few people use the Cube came from?

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

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

2021-10-09 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=443410

RobinK  changed:

   What|Removed |Added

 CC||ro...@xtra.co.nz

--- Comment #12 from RobinK  ---
(In reply to Nate Graham from comment #10)
> (In reply to Patrick Silva from comment #8)
> > dupe of bug 438883 ?
> Oops, indeed.
> 
> For the people upset about this, I hear you and I agree. It's simply a sad
> fact of life that sometimes old things need to get broken to fix other
> things. It's not about abstractly making the code better, it's to support
> current and future needs. We'll try to get this effect re-implemented at
> some point.
> 
> *** This bug has been marked as a duplicate of bug 438883 ***

Thank you.  As a simple user I'd be very obliged if the cube and animations
were restored.

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

[plasmashell] [Bug 421488] Plasma crashes after login

2020-05-15 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=421488

--- Comment #2 from RobinK  ---
I'm happy to report that the updates to Plasma and related that have been made
available over the last couple of days seem to have fixed the problem.

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

[plasmashell] [Bug 421488] Plasma crashes after login

2020-05-14 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=421488

--- Comment #1 from RobinK  ---
OK; after a cold reboot the desktop came up and was usable.  

However, if I try to reposition *any* of the desktop icons, Plasma crashes to
an unusable blank (black) screen.  Killing the desktop and re-logging in
doesn't help.  But a further cold reboot does lead to a usable desktop - until
I try to reposition an icon by grabbing it with the mouse, at which point the
errant behaviour repeats itself.

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

[plasmashell] [Bug 421488] New: Plasma crashes after login

2020-05-13 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=421488

Bug ID: 421488
   Summary: Plasma crashes after login
   Product: plasmashell
   Version: 5.18.5
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ro...@xtra.co.nz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.5)

Qt Version: 5.14.1
Frameworks Version: 5.70.0
Operating System: Linux 4.12.14-lp151.28.48-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
- What I was doing when the application crashed: On login, KDE desktop opened
with default wallpaper and icons repositioned.  While restoring custom config,
desktop crashed to blank (black) and unresponsive screen 

- Unusual behavior I noticed:  Several reboots all resulted in similar
behaviour, ending with Plasma crash and black screen

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7f943e1fd700 (LWP 2716)):
#0  0x7f949d8fe87d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f94a09f90db in QWaitConditionPrivate::wait (deadline=...,
this=0x5629349b0740) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x5629349baf40,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f94a09f9259 in QWaitCondition::wait (this=this@entry=0x5629349baf48,
mutex=mutex@entry=0x5629349baf40, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#4  0x7f94a4b35213 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x5629349baf38) at
/usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255
#5  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x5629349baea0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905
#6  0x7f94a4b35671 in QSGRenderThread::run (this=0x5629349baea0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000
#7  0x7f94a09f2b2c in QThreadPrivate::start (arg=0x5629349baea0) at
thread/qthread_unix.cpp:342
#8  0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0
#9  0x7f94a02eaf2f in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f9445563700 (LWP 2682)):
#0  0x7f94a02e06db in poll () from /lib64/libc.so.6
#1  0x7f947b0e92e4 in ?? () from /usr/lib64/libnvidia-glcore.so.440.36
#2  0x7f947b1d1105 in ?? () from /usr/lib64/libnvidia-glcore.so.440.36
#3  0x7f947b0c7c4e in ?? () from /usr/lib64/libnvidia-glcore.so.440.36
#4  0x7f9481bb0f04 in ?? () from /usr/lib64/libGLX_nvidia.so.0
#5  0x7f9481b86061 in glXSwapBuffers () from /usr/lib64/libGLX_nvidia.so.0
#6  0x7f9482048242 in ?? () from
/usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#7  0x7f94a1222d8f in QOpenGLContext::swapBuffers(QSurface*) () from
/usr/lib64/libQt5Gui.so.5
#8  0x7f94a4b31717 in QSGRenderThread::syncAndRender
(this=this@entry=0x562933c496c0, grabImage=grabImage@entry=0x0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:841
#9  0x7f94a4b3562f in QSGRenderThread::run (this=0x562933c496c0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:980
#10 0x7f94a09f2b2c in QThreadPrivate::start (arg=0x562933c496c0) at
thread/qthread_unix.cpp:342
#11 0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0
#12 0x7f94a02eaf2f in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f9450814700 (LWP 2649)):
#0  0x7f94a02e06db in poll () from /lib64/libc.so.6
#1  0x7f949a2ed749 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f949a2ed85c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f94a0c417eb in QEventDispatcherGlib::processEvents
(this=0x7f9448000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f94a0be0d4a in QEventLoop::exec (this=this@entry=0x7f9450813c70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7f94a09f1657 in QThread::exec (this=) at
thread/qthread.cpp:536
#6  0x7f9453137c37 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f94a09f2b2c in QThreadPrivate::start (arg=0x562933b05390) at
thread/qthread_unix.cpp:342
#8  0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0
#9  0x7f94a02eaf2f in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f945b23e700 (LWP 

[plasmashell] [Bug 416719] Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly)

2020-01-25 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=416719

--- Comment #2 from RobinK  ---
(In reply to Christoph Feck from comment #1)
> Please update Qt from KDE:Qt5 repository again.
> 
> *** This bug has been marked as a duplicate of bug 416715 ***

Re-update of Qt5 fixed it.  Thank you.  Much obliged

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

[plasmashell] [Bug 416719] Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly)

2020-01-24 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=416719

RobinK  changed:

   What|Removed |Added

 CC||ro...@xtra.co.nz

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

[plasmashell] [Bug 416719] Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly)

2020-01-24 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=416719

RobinK  changed:

   What|Removed |Added

Summary|Segmentation fault in   |Segmentation fault in
   |Plasma when I try to open   |Plasma when I try to open
   |Dolphin (either directly or |Dolphin (either directly or
   |indirectly theough another  |indirectly)
   |app |

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

[plasmashell] [Bug 416719] New: Segmentation fault in Plasma when I try to open Dolphin (either directly or indirectly theough another app

2020-01-24 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=416719

Bug ID: 416719
   Summary: Segmentation fault in Plasma when I try to open
Dolphin (either directly or indirectly theough another
app
   Product: plasmashell
   Version: 5.17.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ro...@xtra.co.nz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.90)

Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 4.12.14-lp151.28.36-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.1"

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

I'd just updated a number of libQT5 packages (19 of them) to level
5.14.0-lp151.3.2

Now Dolphin doesn't work at all.  Trying to open it from the command line gives
me this:

Icon theme "MacUltimate_Leopard" not found.
Icon theme "Lero_0.3" not found.
Icon theme "Papirus" not found.
Segmentation fault (core dumped)

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f980a965700 (LWP 8532)):
#0  0x7f9865d508ad in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9868e47eeb in QWaitConditionPrivate::wait (deadline=...,
this=0x562fe956cc30) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x562fe9c8cb40,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f9868e48069 in QWaitCondition::wait (this=this@entry=0x562fe9c8cb48,
mutex=mutex@entry=0x562fe9c8cb40, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#4  0x7f986cf91fe3 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x562fe9c8cb38) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255
#5  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x562fe9c8caa0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905
#6  0x7f986cf92441 in QSGRenderThread::run (this=0x562fe9c8caa0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000
#7  0x7f9868e4193c in QThreadPrivate::start (arg=0x562fe9c8caa0) at
thread/qthread_unix.cpp:342
#8  0x7f9865d4a569 in start_thread () from /lib64/libpthread.so.0
#9  0x7f98687379ef in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f9811de1700 (LWP 8509)):
#0  0x7f9868728c98 in read () from /lib64/libc.so.6
#1  0x7f9862552880 in g_wakeup_acknowledge () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f986250b257 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f986250b6f0 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f986250b85c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f986908fa3b in QEventDispatcherGlib::processEvents
(this=0x7f980c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f986902f03a in QEventLoop::exec (this=this@entry=0x7f9811de0c70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x7f9868e40467 in QThread::exec (this=) at
thread/qthread.cpp:536
#8  0x7f9814703bd7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#9  0x7f9868e4193c in QThreadPrivate::start (arg=0x562fe9b31860) at
thread/qthread_unix.cpp:342
#10 0x7f9865d4a569 in start_thread () from /lib64/libpthread.so.0
#11 0x7f98687379ef in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f98239c9700 (LWP 8379)):
#0  0x7f9865d508ad in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9868e47eeb in QWaitConditionPrivate::wait (deadline=...,
this=0x562fe93fb8c0) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x562fe93fd9f0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f9868e48069 in QWaitCondition::wait (this=this@entry=0x562fe93fd9f8,
mutex=mutex@entry=0x562fe93fd9f0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#4  0x7f986cf91fe3 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x562fe93fd9e8) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255
#5  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x562fe93fd950) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905
#6  0x7f986cf92441 in QSGRenderThread::run (this=0x562fe93fd950) at

[digikam] [Bug 387059] Selection of Transitions - Video Slideshow

2017-11-18 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=387059

RobinK <ro...@xtra.co.nz> changed:

   What|Removed |Added

 CC||ro...@xtra.co.nz

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

[digikam] [Bug 387059] New: Selection of Transitions - Video Slideshow

2017-11-18 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=387059

Bug ID: 387059
   Summary: Selection of Transitions - Video Slideshow
   Product: digikam
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Export-VideoSlideshow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: ro...@xtra.co.nz
  Target Milestone: ---

This is not so much a bug as a request for enhanced functionality in the (new)
video slideshow tool.

It would in my view improve the product immensely if, when creating a video
slideshow using random transitions between slides, it were possible to select
the desired transition effects from the list of available transitions, either
by selecting them into a desired list for the given slideshow, or by
de-selecting the effects not required.

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

[kgpg] [Bug 373408] kgpg segfault on boot and every later run

2017-01-08 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=373408

--- Comment #5 from RobinK <ro...@xtra.co.nz> ---
16.12 fixed it.  Thanks

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

[kgpg] [Bug 374609] New: kgpg fails to start

2017-01-05 Thread RobinK
https://bugs.kde.org/show_bug.cgi?id=374609

Bug ID: 374609
   Summary: kgpg fails to start
   Product: kgpg
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: ro...@xtra.co.nz
  Target Milestone: ---

Application: kgpg (16.11.90)

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

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

kgpg crashes both on KDE startup and whenever I try to start it subesquently.

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7fc381631700 (LWP 3445)):
#0  0x7fc3abba049d in poll () from /lib64/libc.so.6
#1  0x7fc3a5022314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fc3a502242c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fc3ac6b29eb in QEventDispatcherGlib::processEvents
(this=0x7fc37c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc3ac6622db in QEventLoop::exec (this=this@entry=0x7fc381630d10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fc3ac4a7fca in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x2d03890) at
thread/qthread_unix.cpp:368
#7  0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc3abba8d3d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc390a54700 (LWP 3440)):
#0  0x7fc3abba049d in poll () from /lib64/libc.so.6
#1  0x7fc3a5022314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fc3a502242c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fc3ac6b29eb in QEventDispatcherGlib::processEvents
(this=0x7fc3840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc3ac6622db in QEventLoop::exec (this=this@entry=0x7fc390a53ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fc3ac4a7fca in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fc3acd24a25 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x7fc3acf8bd00) at
thread/qthread_unix.cpp:368
#8  0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0
#9  0x7fc3abba8d3d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc392fba700 (LWP 3438)):
#0  0x7fc3abba049d in poll () from /lib64/libc.so.6
#1  0x7fc3a6c963e2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fc3a6c97fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fc3954cf779 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc3ac4ac7f9 in QThreadPrivate::start (arg=0x26aaaf0) at
thread/qthread_unix.cpp:368
#5  0x7fc3a7bc9734 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc3abba8d3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc3b1f938c0 (LWP 3436)):
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x280001) at /usr/include/c++/4.8/bits/atomic_base.h:496
#7  QAtomicOps::load (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:96
#8  QBasicAtomicInteger::load (this=0x280001) at
/usr/include/qt5/QtCore/qbasicatomic.h:116
#9  QtPrivate::RefCount::ref (this=0x280001) at
/usr/include/qt5/QtCore/qrefcount.h:49
#10 QString::QString (other=..., this=0x2ccc258) at
/usr/include/qt5/QtCore/qstring.h:890
#11 KgpgCore::KgpgKeySubPrivate::KgpgKeySubPrivate (this=0x2ccc220, id=...,
size=, trust=..., algo=..., type=..., date=..., curve=...) at
/usr/src/debug/kgpg-16.11.90/core/kgpgkey.cpp:55
#12 0x00438aad in KgpgCore::KgpgKeySub::KgpgKeySub
(this=0x7fff49042bf0, id=..., size=2048, trust=..., algo=..., type=...,
date=..., curve=...) at /usr/src/debug/kgpg-16.11.90/core/kgpgkey.cpp:74
#13 0x004ac57c in readPublicKeysProcess (p=...,
readNode=readNode@entry=0x0) at
/usr/src/debug/kgpg-16.11.90/kgpginterface.cpp:206
#14 0x004aec60 in KgpgInterface::readPublicKeys (ids=...) at
/usr/src/debug/kgpg-16.11.90/kgpginterface.cpp:302
#15 0x00441de6 in KGpgRootNode::addKeys (this=0x2af3ce0, ids=...) at
/usr/src/debug/kgpg-16.11.90/core/KGpgRootNode.cpp:70
#16 0x00454d3c in KGpgItemModel::refreshAllKeys (this=0x2b0d700) at
/usr/src/debug/kgpg-16.11.90/model/kgpgitemmodel.cpp:474
#17 0x00489ca0 in KeysManager::refreshkey (this=0x2aab180) at
/usr/src/debug/kgpg-16.11.90/keysmanager.cpp:2648
#18 0x004e9fca in KeysManager::qt_static_metacall (_o=0x2aab180,
_c=, _id=, _a=) at
/usr/src/debug/kgpg-16.11.90/build/moc_keysmanager.cpp:431
#19 

[plasmashell] [Bug 364523] Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

2016-06-19 Thread RobinK via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364523

--- Comment #2 from RobinK <ro...@xtra.co.nz> ---
Thank you.  Will do.  Sorry to bother you.

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


[plasmashell] [Bug 364523] New: Task Manager and Launcher (Application Menu) inoperative after update to Plasma 5.6.95 openSUSE Leap 42.1

2016-06-19 Thread RobinK via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364523

Bug ID: 364523
   Summary: Task Manager and Launcher (Application Menu)
inoperative after update to Plasma 5.6.95 openSUSE
Leap 42.1
   Product: plasmashell
   Version: 5.6.95
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: ro...@xtra.co.nz
CC: plasma-b...@kde.org

Recent update to plasma 5.6.95 openSUSE Leap 42.1 with openSUSE repositories
.KDE:/Frameworks5/openSUSE_Leap_42.1/ and
..KDE:/Qt5/openSUSE_Leap_42.1/ active.  After the update, in the desktop
both the Task Manager section of the Panel and the KDE Application Launcher are
permanently inoperative, though the individual application icons on the panel
continue to work.  I can also invoke GUI apps successfully from the command
line, (though this is a pain).  

Trying to invoke the launcher from the panel gives this error message:

"Error loading QML file:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1:
plugin cannot be loaded for module "org.kde.plasma.private.kicker": Cannot load
library /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so:
(libKF5ActivitiesStats.so.1: cannot open shared object file: No such file or
directory)"

I don't know if it's relevant, but I also note that although Yast2 tells me
that plasma components are at level 5.6.95, the KInfoCentre tells me they are
at level 5.5.5 (with QT at 5.6.1)   

Reproducible: Always

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