[plasmashell] [Bug 485456] Qith Qt 6.7, System Tray popup is inappropriately resized to a tiny nub

[Mustafa]

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

Mustafa  changed:

   What|Removed |Added

 CC||kde115...@outlook.com

--- Comment #9 from Mustafa  ---
So I was messing around earlier with my (OpenSuse Tumbleweed) system and I
removed some packages that I did not need, those being PackageKit and Discover
and then rebooted my system. System tray icons now are working with no issues.
I rebooted my system again just to make sure, and they're still working. Not
sure if this actually has anything to do with this bug, but I figured I should
at least mention it.

KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

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

[Powerdevil] [Bug 490836] New: KDE Power Management crash after the screen turns off.

[Mustafa]

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

Bug ID: 490836
   Summary: KDE Power Management crash after the screen turns off.
Classification: Plasma
   Product: Powerdevil
   Version: 6.1.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kde115...@outlook.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
After I lock the screen and the screen turns off (or if I'm idle and it locks
the screen automatically), I get a KDE Power Management crash notification when
I unlock the screen. It always happens after the screen turns off, but never
when the screen only locks. Locking and unlocking the screen before it turns
off doesn't crash anything.


STEPS TO REPRODUCE
1. Lock the screen manually or wait for it to lock automatically.
2. Wait until the monitor turns off.
3. Unlock the screen.

OBSERVED RESULT
After unlocking the screen, I get a notification saying that KDE Power
Management has closed unexpectedly.

EXPECTED RESULT
Nothing should crash after unlocking the screen.

SOFTWARE/OS VERSIONS 
Operating System: OpenSUSE Tumbleweed.
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.9-1-default (64-bit)
Graphics Platform: Wayland.

ADDITIONAL INFORMATION
CPU: AMD Ryzen 2600
GPU: AMD RX 580

[KCrash Handler]
Application: KDE Power Management System (org_kde_powerdevil), signal:
Segmentation fault

[New LWP 13373]
[New LWP 13392]
[New LWP 13393]
[New LWP 13390]
[New LWP 13395]
[New LWP 13391]
[New LWP 13404]
[New LWP 13394]
[New LWP 13396]
[New LWP 13397]
[New LWP 13389]
[New LWP 13406]
[New LWP 13405]

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/org_kde_powerdevil'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fdc6e2949dc in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fdc68af3ac0 (LWP 13373))]
python sentry-sdk not installed :(
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fdc68af3ac0 (LWP 13373))]

Thread 13 (Thread 0x7fdc47e006c0 (LWP 13405)):
#0  0x7fdc6e30578f in poll () from /lib64/libc.so.6
#1  0x7fdc6d11434f in ?? () from /lib64/libglib-2.0.so.0
#2  0x7fdc6d114a5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdc6d114aa1 in ?? () from /lib64/libglib-2.0.so.0
#4  0x7fdc6d14132e in ?? () from /lib64/libglib-2.0.so.0
#5  0x7fdc6e292ba2 in start_thread () from /lib64/libc.so.6
#6  0x7fdc6e31400c in clone3 () from /lib64/libc.so.6

Thread 12 (Thread 0x7fdc474006c0 (LWP 13406)):
#0  0x7fdc6e30578f in poll () from /lib64/libc.so.6
#1  0x7fdc6d11434f in ?? () from /lib64/libglib-2.0.so.0
#2  0x7fdc6d114c7f in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x7fdc68f9b2e6 in ?? () from /lib64/libgio-2.0.so.0
#4  0x7fdc6d14132e in ?? () from /lib64/libglib-2.0.so.0
#5  0x7fdc6e292ba2 in start_thread () from /lib64/libc.so.6
#6  0x7fdc6e31400c in clone3 () from /lib64/libc.so.6

Thread 11 (Thread 0x7fdc686006c0 (LWP 13389)):
#0  0x7fdc6e30578f in poll () from /lib64/libc.so.6
#1  0x7fdc6d11434f in ?? () from /lib64/libglib-2.0.so.0
#2  0x7fdc6d114a5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdc6edc1adc in QEventDispatcherGlib::processEvents
(this=0x7fdc6b70, flags=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qeventdispatcher_glib.cpp:394
#4  0x7fdc6eb993db in QEventLoop::exec (this=0x7fdc685ffa50, flags=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:34
#5  0x7fdc6ec74a64 in QThread::exec (this=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:74
#6  0x7fdc6fac270a in ?? () from /lib64/libQt6DBus.so.6
#7  0x7fdc6eced139 in operator() (__closure=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:326
#8  (anonymous
namespace)::terminate_on_exception >
(t=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:262
#9  QThreadPrivate::start (arg=0x7fdc6fb45b20) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:285
#10 0x7fdc6e292ba2 in start_thread () from /lib64/libc.so.6
#11 0x7fdc6e31400c in clone3 () from /lib64/libc.so.6

Thread 10 (Thread 0x7fdc5cc006c0 (LWP 13397)):
#0  0x7fdc6e28efee in __futex_abstimed_wait_commo

[yakuake] [Bug 375030] New: Yakuake crash on exit under wayland session

[Mustafa Muhammad]

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

Bug ID: 375030
   Summary: Yakuake crash on exit under wayland session
   Product: yakuake
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.2+)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.0-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
I use KDE git packages from openSUSE repos for Tumbleweed, yakuake crashes
everytime I close it (from the x button), I use wayland which may have
something to do with the crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a61eedd40 (LWP 2248))]

Thread 2 (Thread 0x7f5a4c53c700 (LWP 2249)):
#0  0x7f5a5c9ef66d in poll () from /lib64/libc.so.6
#1  0x7f5a57374886 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5a5737499c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5a5d31048b in QEventDispatcherGlib::processEvents
(this=0x7f5a440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5a5d2b95ea in QEventLoop::exec (this=this@entry=0x7f5a4c53bcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5a5d0e6b03 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f5a5eea2b99 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f5a5d0eb906 in QThreadPrivate::start (arg=0x7f5a5f116d20) at
thread/qthread_unix.cpp:368
#8  0x7f5a58ea3454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5a5c9f837f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5a61eedd40 (LWP 2248)):
[KCrash Handler]
#6  0x7f5a4ef2af49 in wl_map_insert_at () from
/usr/lib64/libwayland-client.so.0
#7  0x7f5a4ef2716e in wl_proxy_destroy () from
/usr/lib64/libwayland-client.so.0
#8  0x7f5a4e198415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#9  KWayland::Client::WaylandPointer::release
(this=0x1ffcb20, this=0x1ffcb20) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/wayland_pointer_p.h:53
#10 KWayland::Client::Registry::release (this=this@entry=0x1ffca80) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:358
#11 0x7f5a4e19843c in KWayland::Client::Registry::~Registry
(this=0x1ffca80, __in_chrg=) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:353
#12 0x7f5a4e1984d9 in KWayland::Client::Registry::~Registry
(this=0x1ffca80, __in_chrg=) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:354
#13 0x7f5a5d2e5e51 in QObjectPrivate::deleteChildren
(this=this@entry=0x1ffc7c0) at kernel/qobject.cpp:1970
#14 0x7f5a5d2ef22f in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#15 0x7f5a428367e3 in WaylandIntegration::~WaylandIntegration
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:51
#16 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:37
#17 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:43
#18 0x7f5a5c945ea0 in __run_exit_handlers () from /lib64/libc.so.6
#19 0x7f5a5c945efa in exit () from /lib64/libc.so.6
#20 0x7f5a5c92f298 in __libc_start_main () from /lib64/libc.so.6
#21 0x00417aaa in _start ()

Reported using DrKonqi

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

[kwin] [Bug 375971] New: kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

Bug ID: 375971
   Summary: kwin_wayland take 100% CPU
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Created attachment 103804
  --> https://bugs.kde.org/attachment.cgi?id=103804&action=edit
strace -t

Using Neon Wayland Dev Unstable (git master), kwin_wayland is taking 100 of CPU
core, and memory usage wet up to 2G then down again, but CPU stayed 100% (about
an hour now), I asked in #kwin and they suggested using strace, so this is some
output, something wrong with sendmsg and recvmsg.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
Created attachment 103805
  --> https://bugs.kde.org/attachment.cgi?id=103805&action=edit
strace

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
Created attachment 103806
  --> https://bugs.kde.org/attachment.cgi?id=103806&action=edit
strace -c

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
It happens sometimes, I didn't use gdb before, I used:
gdb -p `pidof kwin_wayland` -ex bt -ex 'thread apply all bt full' -ex detach
-ex quit &> kwin_wayland_trace

to create the attached file, hope it helps, please let me know if there is
anything else I can provide

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #5 from Mustafa Muhammad  ---
Created attachment 103904
  --> https://bugs.kde.org/attachment.cgi?id=103904&action=edit
kwin_wayland trace

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #7 from Mustafa Muhammad  ---
Created attachment 103912
  --> https://bugs.kde.org/attachment.cgi?id=103912&action=edit
trace with debug packages installed

I installed all debug packages I could find in the file and generated a new
trace.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #9 from Mustafa Muhammad  ---
It is the same process, still running until now if you want something, maybe
different timing can cause different gdb output :)

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

[Discover] [Bug 380146] New: Discover crashes on start

[Mustafa Muhammad]

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

Bug ID: 380146
   Summary: Discover crashes on start
   Product: Discover
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.90)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.1-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Just started the latest Discover from openSUSE KDE git repos

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f307cbe28c0 (LWP 1952))]

Thread 10 (Thread 0x7f30397c0700 (LWP 1980)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfbbc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3078c6547b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3078c1110a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3078a4eb3b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3078a533ca in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#8  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f303a5ed700 (LWP 1961)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfe32 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f303bd36ef6 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f3072d07385 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f303adee700 (LWP 1960)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfbbc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3072cdfc01 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f3072d07385 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f304a4a9700 (LWP 1958)):
#0  0x7f3074bfb9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3078a541fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3078a4d733 in QSemaphore::acquire(int) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f3078c3daf2 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3076d317a8 in QHttpThreadDelegate::encryptedSlot() () at
/usr/lib64/libQt5Network.so.5
#5  0x7f3076dd05cd in QHttpThreadDelegate::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Network.so.5
#6  0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f3076cf3c5d in QHttpNetworkConnectionChannel::_q_encrypted() () at
/usr/lib64/libQt5Network.so.5
#8  0x7f3076cf441d in
QHttpNetworkConnectionChannel::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () at /usr/lib64/libQt5Network.so.5
#9  0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f3076dc59c7 in QSslSocketBackendPrivate::continueHandshake() () at
/usr/lib64/libQt5Network.so.5
#11 0x7f3076dc99f3 in QSslSocketBackendPrivate::startHandshake() () at
/usr/lib64/libQt5Network.so.5
#12 0x7f3076dca3ce in QSslSocketBackendPrivate::transmit() () at
/usr/lib64/libQt5Network.so.5
#13 0x7f3076db57e1 in QSslSocket::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Network.so.5
#14 0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#15 0x7f3076d85373 in QAbstractSocketPrivate::emitReadyRead(int) () at
/usr/lib64/libQt5Network.so.5
#16 0x7f3076d8542c in QAbstractSocketPrivate::canReadNotification() () at
/usr/lib64/libQt5Network.so.5
#17 0x7f3076d96b31 in QReadNotifier::event(QEvent*) () at
/usr/lib64/libQt5Network.so.5
#18 0x7f307a1e3fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f307a1eb2e1 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f3078c12968 in QCoreApplicati

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #1)
> Interesting. Would you be able to provide a backtrace with debug symbols?
> That would make it much easier to find where the issue is.

I think I already did, I installed debug symbols, and reloaded the backtrace,
which is here in the bug.

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

--- Comment #8 from Mustafa Muhammad  ---
I think this should become confirmed, happens to me on openSUSE Tumbleweed too,
with 5.8.5 and with latest git packages (from openSUSE unstable KDE repos)

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

[kinfocenter] [Bug 374835] New: kinfocenter crashes under wayland session when selecting X-Server info

[Mustafa Muhammad]

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

Bug ID: 374835
   Summary: kinfocenter crashes under wayland session when
selecting X-Server info
   Product: kinfocenter
   Version: 5.8.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: kinfocenter (5.8.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Under wayland session, I opened kinfocenter -> Graphical Information ->
X-Server, and kinfocenter crashed, this happens everytime on multiple
configurations (openSUSE Tumbleweed with 5.8.5 and latest git packages, I also
remember seeing this on Fedora and Neon

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7fcfdefca700 (LWP 2118)):
#0  0x7fcff12f166d in poll () from /lib64/libc.so.6
#1  0x7fcfebaa5876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fcfebaa598c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fcff1c1118b in QEventDispatcherGlib::processEvents
(this=0x7fcfd80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fcff1bbaaea in QEventLoop::exec (this=this@entry=0x7fcfdefc9cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fcff19e8813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fcfefb35385 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fcff19ed4c8 in QThreadPrivate::start (arg=0x7fcfefda6d20) at
thread/qthread_unix.cpp:368
#8  0x7fcfeda7d454 in start_thread () from /lib64/libpthread.so.0
#9  0x7fcff12fa37f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fcff48628c0 (LWP 2117)):
[KCrash Handler]
#6  0x7fcfe2b36f49 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7fcfe2b3316e in proxy_destroy (proxy=0x1d49630) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x1d49630) at src/wayland-client.c:442
#9  0x7fcfe1b7c415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer::release
(this=0x1f617e0, this=0x1f617e0) at
/usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::Registry::release (this=this@entry=0x1f60a30) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358
#12 0x7fcfe1b7c43c in KWayland::Client::Registry::~Registry
(this=0x1f60a30, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353
#13 0x7fcfe1b7c4d9 in KWayland::Client::Registry::~Registry
(this=0x1f60a30, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354
#14 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f63b80) at kernel/qobject.cpp:1970
#15 0x7fcff1bf02bf in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#16 0x7fcfd2a26df9 in WaylandModule::~WaylandModule (this=0x1b64f50,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/base/info_wayland.cpp:48
#17 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f2fd30) at kernel/qobject.cpp:1970
#18 0x7fcff28edeeb in QWidget::~QWidget (this=0x1ca53a0,
__in_chrg=) at kernel/qwidget.cpp:1694
#19 0x7fcff2b65489 in QTreeWidget::~QTreeWidget (this=0x1ca53a0,
__in_chrg=) at itemviews/qtreewidget.cpp:2559
#20 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f17bd0) at kernel/qobject.cpp:1970
#21 0x7fcff28edeeb in QWidget::~QWidget (this=0x1f61a60,
__in_chrg=) at kernel/qwidget.cpp:1694
#22 0x7fcff2a3bc09 in QStackedWidget::~QStackedWidget (this=0x1f61a60,
__in_chrg=) at widgets/qstackedwidget.cpp:149
#23 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1bb4c00) at kernel/qobject.cpp:1970
#24 0x7fcff28edeeb in QWidget::~QWidget (this=0x1b87bd0,
__in_chrg=) at kernel/qwidget.cpp:1694
#25 0x7fcff3cd53fd in KCModule::~KCModule (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kconfigwidgets-5.29.0/src/kcmodule.cpp:177
#26 0x7fcfd2a20bde in KInfoListWidget::~KInfoListWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/info.h:36
#27 KWaylandInfoWidget::~KWaylandInfoWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/main.cpp:57
#28 KWaylandInfoWidget::~KWaylandInfoWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/main.cpp:57
#29 0x7fc

[ksmserver] [Bug 374836] New: ksmserver-logout-greeter crashes on logout from wayland session

[Mustafa Muhammad]

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

Bug ID: 374836
   Summary: ksmserver-logout-greeter crashes on logout from
wayland session
   Product: ksmserver
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Using openSUSE Tumbleweed, ksmserver-logout-greeter crashes when I try to
logout from wayland session, also drkonkqi5 says it can't report the crash
because ksmserver-logout-greeter doesn't offer bug reporting address.

Here is the crash log:

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7027867480 (LWP 9091))]

Thread 2 (Thread 0x7f7011304700 (LWP 9092)):
#0  0x7f70231db66d in poll () from /lib64/libc.so.6
#1  0x7f701bed7876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f701bed798c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7023afb18b in QEventDispatcherGlib::processEvents
(this=0x7f700c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7023aa4aea in QEventLoop::exec (this=this@entry=0x7f7011303c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f70238d2813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f702464e385 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f70238d74c8 in QThreadPrivate::start (arg=0x7f70248bfd20) at
thread/qthread_unix.cpp:368
#8  0x7f701dbf9454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f70231e437f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7027867480 (LWP 9091)):
[KCrash Handler]
#6  0x7f701e683f49 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7f701e68016e in proxy_destroy (proxy=0x161dec0) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x161dec0) at src/wayland-client.c:442
#9  0x7f7026ba6415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer::release
(this=0x161d4f0, this=0x161d4f0) at
/usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::Registry::release (this=this@entry=0x161e6e0) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358
#12 0x7f7026ba643c in KWayland::Client::Registry::~Registry
(this=0x161e6e0, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353
#13 0x7f7026ba64d9 in KWayland::Client::Registry::~Registry
(this=0x161e6e0, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354
#14 0x7f7023ad0f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x162c270) at kernel/qobject.cpp:1970
#15 0x7f7023ada2bf in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#16 0x7f70081da753 in ?? () from
/usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#17 0x7f7023131ea0 in __run_exit_handlers () from /lib64/libc.so.6
#18 0x7f7023131efa in exit () from /lib64/libc.so.6
#19 0x7f702311b298 in __libc_start_main () from /lib64/libc.so.6
#20 0x004060fa in _start ()

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

[Discover] [Bug 381188] New: Discover crash on start

[Mustafa Muhammad]

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

Bug ID: 381188
   Summary: Discover crash on start
   Product: Discover
   Version: 5.10.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.1)

Qt Version: 5.7.1
Frameworks Version: 5.35.0
Operating System: Linux 4.11.0-2.fc26.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Just opened discover on a fresh installation of F26 beta, happens everytime.
I think I know the problem, flatpack is not installed, maybe this is causing
the crash.
I didn't generate better backtrace because I think I knew the problem, I can do
so if you want, but after installing flatpak it doesn't crash on start anymore.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb920c268c0 (LWP 5289))]

Thread 5 (Thread 0x7fb8f702e700 (LWP 5294)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb9202af8a6 in QQuickPixmapReader::run() () from
/lib64/libQt5Quick.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fb8fd788700 (LWP 5292)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb91d4bf3c5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb8fe999700 (LWP 5291)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb920d74709 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb90708a700 (LWP 5290)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb9149fec97 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fb914a00a8a in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fb90b74cb99 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#6  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb920c268c0 (LWP 5289)):
[KCrash Handler]
#6  0x7fb8e72e35fd in FlatpakBackend::setupFlatpakInstallations(_GError**)
() from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#7  0x7fb8e72e9a38 in FlatpakBackend::FlatpakBackend(QObject*) () from
/usr/lib64/qt5/plugins/discover/flatpak-backend.so
#8  0x7fb8e72ec6bb in FlatpakBackendFactory::newInstance(QObject*, QString
const&) const () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#9  0x7fb91ff77427 in DiscoverBackendsFactory::backendForFile(QString
const&, QString const&) const () from
/usr/lib64/plasma-discover/libDiscoverCommon.so
#10 0x7fb91ff77abb in DiscoverBackendsFactory::backe

[plasmashell] [Bug 381431] New: Plasma crashes when I traverse through the application menu

[Mustafa Muhammad]

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

Bug ID: 381431
   Summary: Plasma crashes when I traverse through the application
menu
   Product: plasmashell
   Version: 5.10.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mustafa10...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.34.0
Operating System: Linux 4.10.1-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was walking through the application menu in a wayland plasma session.

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 0x7f5a751058c0 (LWP 1537))]

Thread 12 (Thread 0x7f59a1eae700 (LWP 1818)):
[KCrash Handler]
#6  0x7f5a6d6515c0 in wl_proxy_create_wrapper () at
/usr/lib64/libwayland-client.so.0
#7  0x7f59cce97b81 in  () at /usr/lib64/libEGL_mesa.so.0
#8  0x7f59cce8657e in  () at /usr/lib64/libEGL_mesa.so.0
#9  0x7f59cd54c870 in  () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f59cd54aebd in  () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#11 0x7f5a6f8675ee in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib64/libQt5Gui.so.5
#12 0x7f5a72b69f14 in  () at /usr/lib64/libQt5Quick.so.5
#13 0x7f5a72b714db in  () at /usr/lib64/libQt5Quick.so.5
#14 0x7f5a72b707d7 in  () at /usr/lib64/libQt5Quick.so.5
#15 0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#16 0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#18 0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f59a28cd700 (LWP 1817)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f59a3343700 (LWP 1783)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f59a882d700 (LWP 1770)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f59ab62c700 (LWP 1610)):
#0  0x7f5a6e70e08d in poll () at /lib64/libc.so.6
#1  0x7f5a6953cce9 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5a6953cdfc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5a6f02975b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5a6efd2d0a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5a6ee0505a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f59adec3f37 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f59c48ba700 (LWP 1593)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x000

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #5 from Mustafa Muhammad  ---
Sorry for the late response
mustafa@mustafa-pc:~> plasma-discover --listbackends
Available backends:
 * kns-backend
 * packagekit-backend


mustafa@mustafa-pc:~> plasma-discover 
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:9 Type Kirigami.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/ApplicationWindow.qml:25
Type Base.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationWindow.qml:97 Type
AbstractApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:21
plugin cannot be loaded for module "QtQuick.Controls": Cannot load library
/usr/lib64/qt5/qml/QtQuick/Controls.2/libqtquickcontrols2plugin.so:
(/usr/lib64/libQt5QuickControls2.so.5: symbol
_ZNK14QPlatformTheme22standardButtonShortcutEi, version Qt_5.9.0_PRIVATE_API
not defined in file libQt5Gui.so.5 with link time reference)

Errors when loading the GUI
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "servicemenu.knsrc"
Discarding invalid backend "ksysguard.knsrc"
setting currentApplicationBackend PackageKitBackend(0x55c7b6668720)

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

[systemsettings] [Bug 381518] New: systemsettings5 crash on start

[Mustafa Muhammad]

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

Bug ID: 381518
   Summary: systemsettings5 crash on start
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

I am using plasma from git branches (openSUSE KDE unstable repos), I can't
start systemsettings

mustafa@mustafa-pc:~> systemsettings5
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kpackage-genericqml.desktop, tried
("/home/mustafa/.local/share", "/usr/share")
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:31:5:
Type CategoriesPage unavailable 
 CategoriesPage { 
 ^
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:22:1:
plugin cannot be loaded for module "QtQuick.Controls": Cannot load library
/usr/lib64/qt5/qml/QtQuick/Controls.2/libqtquickcontrols2plugin.so:
(/usr/lib64/libQt5QuickControls2.so.5: symbol
_ZNK14QPlatformTheme22standardButtonShortcutEi, version Qt_5.9.0_PRIVATE_API
not defined in file libQt5Gui.so.5 with link time reference) 
 import QtQuick.Controls 2.0 as QtControls2 
 ^
Segmentation fault (core dumped)

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

[systemsettings] [Bug 381518] systemsettings5 crash on start

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
(In reply to Luca Beltrame from comment #3)
> Please update from the unstable repositories:
> 
> > usr/lib64/libQt5QuickControls2.so.5: symbol 
> > _ZNK14QPlatformTheme22standardButtonShortcutEi
> 
> There was a change in the Qt packages, I rebuilt everything and it is fixed.

It is fixed, thanks, I was using the "KDE:/Qt59" branch (before the instruction
update), now on "KDE:/Unstable:/Qt" everything works fine.

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

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #8 from Mustafa Muhammad  ---
Sorry for the delay, I was away from this machine, it is working fine now,
thanks.

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

[konsole] [Bug 369316] Crash in Konsole::TerminalDisplay::updateCursor

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Kurt Hindenburg from comment #1)
> Do you have any non-default settings w/ respect to the cursor?  or any other
> info about when it crashes?

No, I don't think I do, and now I am using Tumbleweed and I don't see it
anymore, feel free to close it and if it happens again, I'll report.

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

[Discover] [Bug 381188] Discover crash on start

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Christoph Feck from comment #1)
> Related to bug 380496.
> 
> Does installing 'flatpak' help to resolve the crash?

Yes, it does.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #15 from Mustafa Muhammad  ---
(In reply to Martin Flöser from comment #14)
> What I need is to know where the problem happens. For that I ideally get a
> backtrace with debug symbols. Without that all is just guessing
> unfortunately.

I'll try to provide another backtrace with debug symbols (I think I already
provided one), but the session is very unstable these days (crash when I
traverse the menu), so maybe later.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #17 from Mustafa Muhammad  ---
(In reply to Alexander Mentyu from comment #16)
> Is this issue still reproducible?

I don't think so, at least not for me, I don't mind closing it, it's your call.

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

[Discover] [Bug 372277] New: Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

Bug ID: 372277
   Summary: Discover crashes when used to open rpm file
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

I tried to open chrome rpm using plasma-discover and it crashed, this is the
backtrace (drkonqi couldn't report it because it says "plasma-discover doesn't
provide a bug reporting address")


Application: plasma-discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 62: movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f70fd067900 (LWP 7793))]

Thread 5 (Thread 0x7f70e0b77700 (LWP 7798)):
#0  g_mutex_unlock (mutex=0x7f70d8000990) at gthread-posix.c:1348
#1  0x7f7102299ffd in g_main_context_iterate
(context=context@entry=0x7f70d8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3877
#2  0x7f710229a26c in g_main_context_iteration (context=0x7f70d8000990,
may_block=may_block@entry=1) at gmain.c:3990
#3  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e0b76cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f7109d6e643 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x7f70d4003650) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e0b77700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f70e1378700 (LWP 7797)):
#0  0x7f71022df7f9 in g_mutex_lock (mutex=mutex@entry=0x7f70d4000990) at
gthread-posix.c:1336
#1  0x7f710229a258 in g_main_context_iteration (context=0x7f70d4000990,
may_block=may_block@entry=1) at gmain.c:3989
#2  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e1377c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#4  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c70825080) at
thread/qthread.cpp:507
#5  0x7f710cfd6ca6 in QQuickPixmapReader::run (this=0x564c70825080) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/util/qquickpixmapcache.cpp:823
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c70825080) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e1378700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f70e3fff700 (LWP 7796)):
#0  0x7f710915a00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f710229a156 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f70dc002e70, timeout=, context=0x7f70dc000990)
at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f70dc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3924
#3  0x7f710229a26c in g_main_context_iteration (context=0x7f70dc000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e3ffeca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c6f3b4ad0) at
thread/qthread.cpp:507
#7  0x7f710a824735 in QQmlThreadPrivate::run (this=0x564c6f3b4ad0) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#8  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c6f3b4ad0) at
thread/qthread_unix.cpp:344
#9  0x7f71076ac6ca in start_thread (arg=0x7f70e3fff700) at
pthread_create.c:333
#10 0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f70e97f6700 (LWP 7795)):
[KCrash Handler]
#6  0x7f7109f3c87d in QObject::disconnect (sender=0x7f70d8003860,
signal=signal@entry=0x0, receiver=receiver@entry=0x7f70e4014a70,
method=method@entry=0x0) at kernel/qobject.cpp:2956
#7  0x7f710d877fd0 in QObject::disconnect (member=0x0,
receiver=0x7f70e4014a70, this=) at
../../src/corelib/kernel/qobject.h:359
#8  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7f70e4014a70) at
qdbusintegrator.cpp:1133
#9  0x7f710d8648c2 in QDBusConnectionManager::run (this=0x7f710d8da060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbus

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #1)
> Please fill version and platform fields.
> 
> Also how do you open an rpm file?

Couldn't find 5.8.1 in versions, thus I chose unspecified.
Fedora 25 RC, plasma-discover 5.8.1

Right clicked the rpm, and chose plasma-discover from the "Open
With->Other->(searched for it)"

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
(In reply to Rex Dieter from comment #3)
> I didn't think discover supported installing packages directly, it's desktop
> file only contains:
> MimeType=x-scheme-handler/appstream;
> 
> (no mention of package mimetypes)

Maybe it doesn't, I was trying, and I think it should support this.

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

[plasmashell] [Bug 390778] New: plasmashell crash probably related to search

[Mustafa Muhammad]

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

Bug ID: 390778
   Summary: plasmashell crash probably related to search
   Product: plasmashell
   Version: 5.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 110838
  --> https://bugs.kde.org/attachment.cgi?id=110838&action=edit
Saved bug report with backtrace

Opened the menu and searched, also krunner crashes on search, so probably
search related. I am using Fedora Rawhide with Plasma 5.12.1

Application: plasmashell (5.12.1)

Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.16.0-0.rc1.git4.1.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Rawhide)"

I tried to report using DrKonqi but got error code 114 from bugzilla "Comments
cannot be longer then 65535"

Attached the saved bug report (with backtrace)

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

--- Comment #6 from Mustafa Muhammad  ---
Created attachment 109265
  --> https://bugs.kde.org/attachment.cgi?id=109265&action=edit
New crash information added by DrKonqi

plasma-discover (5.11.3) using Qt 5.9.2

- What I was doing when the application crashed:

Just searching in Discover.

I attached full debug info, I use version 5.11.3 you mentioned on Fedora 27
(test-updates).

In case this is related, I use the flatpak backend, not likely, but may be
related.

-- Backtrace (Reduced):
#7  0x7f2435fd2de2 in AbstractResourcesBackend::Filters::shouldFilter
(this=0x5558562a45c0, res=0x555854205190) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:114
#8  0x7f2435fd30fd in AbstractResourcesBackend::Filters::filterJustInCase
(this=this@entry=0x5558562a45c0, input=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:127
#9  0x7f2435fcaf12 in ResourcesProxyModel::addResources
(this=0x5558562a4590, _res=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesProxyModel.cpp:174
[...]
#11 0x7f2435fe23d2 in ResultsStream::resourcesFound
(this=this@entry=0x5558562ca0d0, _t1=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/x86_64-redhat-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:142
#12 0x7f2435fc2ec0 in AggregatedResultsStream::emitResults
(this=0x5558562ca0d0) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesModel.cpp:284

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[dolphin] [Bug 387842] New: Dolphin crash while moving files

[Mustafa Muhammad]

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

Bug ID: 387842
   Summary: Dolphin crash while moving files
   Product: dolphin
   Version: 17.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mustafa10...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.08.1)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.16-302.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
- What I was doing when the application crashed:
I was moving a large directory from one partition to another, maybe I hit
ctrl+z after finishing copying, but I think dolphin crashed when it was
creating the 2000+ nested directories to move the files.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc0fad84940 (LWP 2169))]

Thread 4 (Thread 0x7fc0c992e700 (LWP 2173)):
#0  0x7fc0f26c18bb in poll () from /lib64/libc.so.6
#1  0x7fc0ea1bfed9 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc0ea1bffec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc0f352c35b in QEventDispatcherGlib::processEvents
(this=0x7fc0c4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc0f34da0ea in QEventLoop::exec (this=this@entry=0x7fc0c992dc70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fc0f332b8ba in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x555829ab7a70) at
thread/qthread_unix.cpp:368
#7  0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc0d9ada700 (LWP 2172)):
#0  0x7fc0f26bce38 in read () from /lib64/libc.so.6
#1  0x7fc0ea2040e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fc0ea1bf9e8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fc0ea1bfe80 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fc0ea1bffec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fc0f352c35b in QEventDispatcherGlib::processEvents
(this=0x7fc0cc000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fc0f34da0ea in QEventLoop::exec (this=this@entry=0x7fc0d9ad9c30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fc0f332b8ba in QThread::exec (this=this@entry=0x7fc0f5763060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:515
#8  0x7fc0f54ef479 in QDBusConnectionManager::run (this=0x7fc0f5763060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x7fc0f5763060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#10 0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#11 0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc0dbdf8700 (LWP 2171)):
#0  0x7fc0f26c18bb in poll () from /lib64/libc.so.6
#1  0x7fc0e972efe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fc0e9730dda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fc0ddf5aa49 in QXcbEventReader::run (this=0x5558294f26d0) at
qxcbconnection.cpp:1335
#4  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x5558294f26d0) at
thread/qthread_unix.cpp:368
#5  0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc0fad84940 (LWP 2169)):
[KCrash Handler]
#6  QMetaObject::activate (sender=sender@entry=0x55582f071650, signalOffset=3,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff645bcff0)
at kernel/qobject.cpp:3638
#7  0x7fc0f3504237 in QMetaObject::activate
(sender=sender@entry=0x55582f071650, m=m@entry=0x7fc0f54d5f00
, local_signal_index=local_signal_index@entry=4,
argv=argv@entry=0x7fff645bcff0) at kernel/qobject.cpp:3628
#8  0x7fc0f5282341 in KJob::description (this=this@entry=0x55582f071650,
_t1=, _t1@entry=0x55582f071650, _t2=..., _t3=..., _t4=...) at
/usr/src/debug/kf5-kcoreaddons-5.40.0-1.fc27.x86_64/x86_64-redhat-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:577
#9  0x7fc0f88f9948 in KIO::UndoJob::emitMoving (dest=..., src=...,
this=0x55582f071650) at
/usr/src/debug/kf5-kio-5.40.0-2.fc27.x86_64/src/widgets/fileundomanager.cpp:131
#10 KIO::FileUndoManagerPrivate::stepMovingFiles
(this=this@entry=0x555829591a50) at
/usr/src/debug/kf5-kio-5.40.0-2.fc27.x86_64/src/widgets/fileundomanager.cpp:55

[Discover] [Bug 388978] New: Sometimes searching crashes Discover

[Mustafa Muhammad]

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

Bug ID: 388978
   Summary: Sometimes searching crashes Discover
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.11.90)

Qt Version: 5.9.3
Frameworks Version: 5.42.0
Operating System: Linux 4.13.0-26-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:
Searching in Discover, I opened a new report because this is an up to date neon
dev (from git)

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fece67358c0 (LWP 5014))]

Thread 9 (Thread 0x7fec97dd3700 (LWP 5045)):
#0  0x7fece1bc024d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc9316f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ede74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fecdc8ee330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fec97dd2d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#8  0x7fece25ca709 in QThreadPrivate::start (arg=0x2a19f90) at
thread/qthread_unix.cpp:368
#9  0x7fecde7776ba in start_thread (arg=0x7fec97dd3700) at
pthread_create.c:333
#10 0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7feca60e0700 (LWP 5024)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca60dfd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2d78db0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca60e0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7feca7d96700 (LWP 5021)):
#0  0x7fecdc932a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fecdc8ee23d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca7d95d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2c264d0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca7d96700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fecadfa0700 (LWP 5020)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fecadf9fd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x3d96820) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7fecadfa0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fecb9a12700 (LWP 5019)):
#0  __GI___pthread_getspecific (key=3) at pthread_getspecific.c:30
#1  0x7

[Discover] [Bug 388990] New: Discover fails to install flatpak application

[Mustafa Muhammad]

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

Bug ID: 388990
   Summary: Discover fails to install flatpak application
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Flatpak Backend
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

Discover fails to install an application, I tested Telegram, I started Discover
from terminal and got this log:

mustafa@mustafa-pc:~$ plasma-discover 
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x21e4ee0)
Failed to install "org.telegram.desktop" :
"GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file does
not start with a group"

Using Neon dev git-unstable, Discover version 5.11.90
With flatpak backend installed

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

[Discover] [Bug 388990] Discover fails to install flatpak application

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
OK, the problem is probably in flatpak, it didn't install it from console too:

mustafa@mustafa-pc:~$ flatpak install flathub org.telegram.desktop
Installing: org.telegram.desktop/x86_64/stable from flathub
[] 1 metadata, 0 content objects fetched; 569 B transferred
in 1 se
error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file
does not start with a group

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

[Discover] [Bug 388990] Discover fails to install flatpak application

[Mustafa Muhammad]

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

--- Comment #3 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #2)
> Please check your installation.

Yes, it was fixed by the upstream flatpak fix, thank you.

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

[frameworks-kirigami] [Bug 488326] After update to KF 6.3, many systemsettings pages of Plasma 6.0.90 show an error message

[Mustafa Kamran]

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

Mustafa Kamran  changed:

   What|Removed |Added

 CC||mmkthecool...@gmail.com

--- Comment #10 from Mustafa Kamran  ---
I'd like to share my experience. I'm on Fedora 40 KDE Plasma Spin and I also
get the same issue. Deleting the qmlcache folder does not solve this issue, but
I have managed to find a way to consistently reproduce the bug:

1. Open the System Settings applet
2. Go to "Mouse and Touchpad" section, then go back
3. Go to "Colors and Themes" section and the following error appears

qrc:/kcm/kcm_lookandfeel/main.qml:86 Type NewStuff.Action unavailable
qrc:/qt/qml/org/kde/newstuff/Action.qml:167 Type NewStuff.Page unavailable
qrc:/qt/qml/org/kde/newstuff/Page.qml:133 Type Kirigami.InlineMessage
unavailable
file:///usr/lib64/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type
KT.InlineMessage unavailable
qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:123 Cannot assign
object of type "TP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_90*" as the former is neither the same as the
latter nor a sub-class of it.

System Information:
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20RD002RUS
System Version: ThinkPad E15

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

[plasmashell] [Bug 436318] Save session doesn't work under Wayland

[Mustafa Kamran]

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

Mustafa Kamran  changed:

   What|Removed |Added

 CC||mmkthecool...@gmail.com

--- Comment #128 from Mustafa Kamran  ---
(In reply to undoIT from comment #121)
> Updated Arch with Plasma 6.1, rebooted, didn't work. Then, switched setting
> to: "When session was manually saved" and rebooted. Don't remember seeing a
> button to "Save Session" but it worked same as setting: "On last logout".
> Switched back to "On last logout" and it is still working. Very pleased!
> Thanks to everyone who put in the hard work to make this happen for Plasma 6.

I am on Fedora 40 and I pretty much had to go through the same steps to
actually enable this feature. Also the manual option didn't make the "save
session" button show up even after reboot.

System Info:
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20RD002RUS
System Version: ThinkPad E15

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

[plasmashell] [Bug 436318] Save session doesn't work under Wayland

[Mustafa Kamran]

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

--- Comment #133 from Mustafa Kamran  ---
I am also in the camp that windows not remembering which desktops were in is a
dealbreaker for me. I sometimes use multiple desktops in my workflow and this
feature may be more tedious to deal with than having session restore disabled.
I'd rather have the feature disabled and start over from each reboot than have
to sort through lots of windows to their right desktops.

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

[Discover] [Bug 401300] Discover can't install missing flatpak backend in Fedora

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #9 from Mustafa Muhammad  ---
Sorry for the delay, on new installation of Fedora 33, Discover has no "Missing
Backends" part, even though the snap backend (plasma-discover-snap) is not
installed.
Nowadays Fedora ship flatpak backend by default, so not sure if this (hiding
the "Missing Backends") is the intended behaviour.

Regards
Mustafa

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

[yakuake] [Bug 399006] Yakuake crash after changing settings

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #2 from Mustafa Muhammad  ---
Hello Justin,
I tested now with the latest Neon Developer Edition and the problem is not
reproducible anymore, works for me :)

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

[ark] [Bug 414149] Ark crash on close while loading archive

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[ark] [Bug 414149] Ark crash on close while loading archive

[Mustafa Muhammad]

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

--- Comment #3 from Mustafa Muhammad  ---
Created attachment 131393
  --> https://bugs.kde.org/attachment.cgi?id=131393&action=edit
New crash information added by DrKonqi

ark (20.08.0) using Qt 5.15.0

- What I was doing when the application crashed:

Opening a large archive and close the window while it was still "Loading
archive"

-- Backtrace (Reduced):
#4  0x7f44c17a361e in KJob::kill (this=0x557cd67f1d00,
verbosity=verbosity@entry=KJob::Quietly) at
/usr/src/debug/kcoreaddons-5.73.0-1.2.x86_64/src/lib/jobs/kjob.cpp:106
#5  0x7f44b83203f3 in JobTracker::~JobTracker (this=,
this=) at
/usr/src/debug/ark-20.08.0-1.2.x86_64/part/jobtracker.cpp:42
#6  0x7f44b8320459 in JobTracker::~JobTracker (this=,
this=) at
/usr/src/debug/ark-20.08.0-1.2.x86_64/part/jobtracker.cpp:44
#7  0x7f44c070f74e in QObjectPrivate::deleteChildren
(this=this@entry=0x557cd637b640) at kernel/qobject.cpp:2104
#8  0x7f44c1278896 in QWidget::~QWidget (this=0x557cd66c1ab0,
__in_chrg=) at kernel/qwidget.cpp:1523

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

[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures

[Mustafa YAMAN]

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

Mustafa YAMAN  changed:

   What|Removed |Added

 CC||m.yaman9...@gmail.com

--- Comment #16 from Mustafa YAMAN  ---
Please I need this to use KDE its only reason why I'm using gnome...

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

[i18n] [Bug 428598] New: Some translates already done in .po file not changing language

[Mustafa YAMAN]

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

Bug ID: 428598
   Summary: Some translates already done in .po file not changing
language
   Product: i18n
   Version: 20.12.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tr
  Assignee: gor...@gelecek.com.tr
  Reporter: m.yaman9...@gmail.com
  Target Milestone: ---

Created attachment 132962
  --> https://bugs.kde.org/attachment.cgi?id=132962&action=edit
Explain as screenshot

SUMMARY

Translating .po files not working as expected. Some already translated lines
doesnt work tho


STEPS TO REPRODUCE
1. Download latest trunk by svn or stable
2. Observe it and compile or change with your defaults (no matter I think)
3. Some strings not changed.

OBSERVED RESULT

Translating not working as expected


EXPECTED RESULT

Translated entry should change

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch 
(available in About System)
KDE Plasma Version:  5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

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

[plasmashell] [Bug 426368] Plasma crashed while switching between Global Themes

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
Created attachment 133161
  --> https://bugs.kde.org/attachment.cgi?id=133161&action=edit
New crash information added by DrKonqi

plasmashell (5.20.2) using Qt 5.15.1

- What I was doing when the application crashed:

On plasma wayland, when I change the global theme AND tick "Use desktop layout
from them", plasma crashes, everytime.

-- Backtrace (Reduced):
#6  0x7f36c57c1b07 in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=, msg=) at
global/qlogging.cpp:893
#9  0x7f36b40583ee in QtWaylandClient::QWaylandDisplay::flushRequests() ()
from /lib64/libQt5WaylandClient.so.5
#10 0x7f36c59b6290 in doActivate (sender=0x557d84d7abc0,
signal_index=4, argv=0x7ffd92b8e210) at kernel/qobject.cpp:3898
#11 0x7f36c59d2a6c in QEventDispatcherGlib::processEvents
(this=0x557d84d7abc0, flags=...) at kernel/qeventdispatcher_glib.cpp:430

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

[plasmashell] [Bug 426368] Plasma crashed while switching between Global Themes

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[plasma-nm] [Bug 390518] Fedora27: By default connection editor sets Ethernet to "no auto", 100MBits/s half duplex

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

--- Comment #12 from Mustafa Muhammad  ---
(In reply to Jan Grulich from comment #8)
> It seems to be this NM change:
> https://github.com/NetworkManager/NetworkManager/commit/
> 12b9d30ae625000c578d6b4f4bcf8c3a119132dc

But why DSL disable auto-negotiation while Wired (normal ethernet DHCP) enables
it? Why manually change it if it can be negotiated?

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

[neon] [Bug 368548] Plasma Wayland session doesn't work (blank) without kwin-wayland-backend-x11

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
Please close this if you want.

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

[yakuake] [Bug 443249] New: Yakuake crashes while closing the last tab

[Mustafa Muhammad]

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

Bug ID: 443249
   Summary: Yakuake crashes while closing the last tab
   Product: yakuake
   Version: 21.08.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: yakuake (21.08.0)

Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.14.9-200.fc34.x86_64 x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: Fedora 34 (KDE Plasma)

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

I closed the last tab (ctrl+shift+r)

I tried again, multiple times, same result.

I also closed it using the mouse from the red x in the buttom-right corner,
same crash.

Using up to date Fedora 34

Yakuake 21.08.0

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault

[KCrash Handler]
#4  0x7fae460b9d13 in QListData::size (this=0x5623c42454a0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:115
#5  QList::size (this=0x5623c42454a0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:176
#6  QStackedLayout::widget (this=0x5623c4163d80, index=0) at
kernel/qstackedlayout.cpp:403
#7  0x7fadca2a3a1d in Konsole::TabbedViewContainer::viewSplitterAt(int) ()
from /lib64/libkonsoleprivate.so.21
#8  0x7fadca2a68a6 in Konsole::TabbedViewContainer::currentTabViewCount()
() from /lib64/libkonsoleprivate.so.21
#9  0x7fadca24e849 in Konsole::ViewManager::sessionFinished() () from
/lib64/libkonsoleprivate.so.21
#10 0x7fae455f33a9 in QtPrivate::QSlotObjectBase::call (a=0x7ffeda99e1b0,
r=, this=0x5623c41b2bb0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x5623c41aa110, signal_index=4,
argv=0x7ffeda99e1b0) at kernel/qobject.cpp:3886
#12 0x7fae455f33a9 in QtPrivate::QSlotObjectBase::call (a=0x7ffeda99e2f0,
r=, this=0x5623c41aee60) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x5623c41ac320, signal_index=11,
argv=0x7ffeda99e2f0) at kernel/qobject.cpp:3886
#14 0x7fae455ee327 in QMetaObject::activate
(sender=sender@entry=0x5623c41ac320, m=m@entry=0x7fae45893060
, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7ffeda99e2f0) at kernel/qobject.cpp:3946
#15 0x7fae45546e73 in QProcess::finished (this=this@entry=0x5623c41ac320,
_t1=, _t2=) at .moc/moc_qprocess.cpp:339
#16 0x7fae4554b433 in QProcessPrivate::_q_processDied
(this=this@entry=0x5623c40cf340) at io/qprocess.cpp:1184
#17 0x7fae4554f102 in QProcessPrivate::waitForFinished
(this=0x5623c40cf340, msecs=1000) at io/qprocess_unix.cpp:877
#18 0x7fadca2b8b3a in Konsole::Session::closeInNormalWay() () from
/lib64/libkonsoleprivate.so.21
#19 0x7fadca2af13a in Konsole::Session::close() () from
/lib64/libkonsoleprivate.so.21
#20 0x7fae455f33a9 in QtPrivate::QSlotObjectBase::call (a=0x7ffeda99e5e0,
r=, this=0x5623c4240d70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x5623c3e059c0, signal_index=0,
argv=0x7ffeda99e5e0) at kernel/qobject.cpp:3886
#22 0x7fae455ee327 in QMetaObject::activate
(sender=sender@entry=0x5623c3e059c0, m=m@entry=0x7fae4588c3e0
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffeda99e5e0) at kernel/qobject.cpp:3946
#23 0x7fae455ee3e3 in QObject::destroyed (this=this@entry=0x5623c3e059c0,
_t1=, _t1@entry=0x5623c3e059c0) at .moc/moc_qobject.cpp:219
#24 0x7fae460d1813 in QWidget::~QWidget (this=0x5623c3e059c0,
__in_chrg=) at kernel/qwidget.cpp:1497
#25 0x7fadca2891dd in Konsole::TerminalDisplay::~TerminalDisplay() () from
/lib64/libkonsoleprivate.so.21
#26 0x7fae455e878a in QObjectPrivate::deleteChildren
(this=this@entry=0x5623c3e17b30) at kernel/qobject.cpp:2104
#27 0x7fae460d1556 in QWidget::~QWidget (this=0x5623c42412a0,
__in_chrg=) at kernel/qwidget.cpp:1522
#28 0x7fadca22d6f5 in Konsole::ViewSplitter::~ViewSplitter() () from
/lib64/libkonsoleprivate.so.21
#29 0x7fae455e878a in QObjectPrivate::deleteChildren
(this=this@entry=0x5623c3e89c80) at kernel/qobject.cpp:2104
#30 0x7fae460d1556 in QWidget::~QWidget (this=0x5623c4163d10,
__in_chrg=) at kernel/qwidget.cpp:1522
#31 0x7fae4624e88d in QStackedWidget::~QStackedWidget (this=0x5623c4163d10,
__in_chrg=) at widgets/qstackedwidget.cpp:147
#32 0x7fae455e878a in QObjectPrivate::deleteChildren
(this=this@entry=0x5623c3c9ea50) at kernel/qobject.cpp:2104
#33 0x7fae460d1556 in QWidget::~QWidget (this=0x5623c416cc80,
__in_chrg=) at kernel/qwidget.cpp:1522
#34 0x7fadca2a39dd in Konsole::TabbedViewContainer::~TabbedViewContainer()
() from /lib64/libkonsoleprivate.so.21
#35 0x7fae455e878a in QObje

[Discover] [Bug 399005] New: Discover crashes after changing a software source

[Mustafa Muhammad]

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

Bug ID: 399005
   Summary: Discover crashes after changing a software source
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.14.80)

Qt Version: 5.11.1
Frameworks Version: 5.51.0
Operating System: Linux 4.15.0-34-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
After I untick a souftware source in discover, there is no save button, so I
assumed I should just go to other partition and the settings will be saved.
After pressing Applications or Updates (was on Settings page), discover
crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f786c8a7c80 (LWP 5596))]

Thread 10 (Thread 0x7f781f3b3700 (LWP 5609)):
#0  0x7f7867e14bf9 in __GI___poll (fds=0x7f7814002960, nfds=1,
timeout=8502) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7862384439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f786238454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7868754a9b in QEventDispatcherGlib::processEvents
(this=0x7f7814000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f78686f8dea in QEventLoop::exec (this=this@entry=0x7f781f3b2da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f7868523b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f786852eaab in QThreadPrivate::start (arg=0x558a561d6440) at
thread/qthread_unix.cpp:367
#7  0x7f786451f6db in start_thread (arg=0x7f781f3b3700) at
pthread_create.c:463
#8  0x7f7867e2188f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f782d0fe700 (LWP 5605)):
#0  0x7f7867e100b4 in __GI___libc_read (fd=21, buf=0x7f782d0fdb90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f78623c8a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7862383f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78623843e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f786238454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f7868754a9b in QEventDispatcherGlib::processEvents
(this=0x7f7824000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f78686f8dea in QEventLoop::exec (this=this@entry=0x7f782d0fdda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#7  0x7f7868523b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#8  0x7f786852eaab in QThreadPrivate::start (arg=0x558a58095430) at
thread/qthread_unix.cpp:367
#9  0x7f786451f6db in start_thread (arg=0x7f782d0fe700) at
pthread_create.c:463
#10 0x7f7867e2188f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f782ef3c700 (LWP 5603)):
#0  0x7f7867e100b4 in __GI___libc_read (fd=18, buf=0x7f782ef3bb90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f78623c8a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7862383f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78623843e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f786238454c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f7868754a9b in QEventDispatcherGlib::processEvents
(this=0x7f782b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f78686f8dea in QEventLoop::exec (this=this@entry=0x7f782ef3bda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#7  0x7f7868523b8a in QThread::exec (this=) at
thread/qthread.cpp:525
#8  0x7f786852eaab in QThreadPrivate::start (arg=0x558a56338e20) at
thread/qthread_unix.cpp:367
#9  0x7f786451f6db in start_thread (arg=0x7f782ef3c700) at
pthread_create.c:463
#10 0x7f7867e2188f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f782700 (LWP 5602)):
#0  0x7f7867e14bf9 in __GI___poll (fds=0x558a56307040, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7862384439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f78623847d2 in g_main_loop_run () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78374bef66 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f78623abe85 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f786451f6db in start_thread (arg=0x7f782700) at
pth

[yakuake] [Bug 399006] New: Yakuake crash after changing settings

[Mustafa Muhammad]

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

Bug ID: 399006
   Summary: Yakuake crash after changing settings
   Product: yakuake
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.5+)

Qt Version: 5.11.1
Frameworks Version: 5.51.0
Operating System: Linux 4.15.0-34-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
I changed Yakuake settings then tried to split the yakuake screen ctrl+shift+(
but it crashed, I tried again without changing setting and no crash, then
changed settings and only closed the tab and got another crash.
It might be related to shortcuts.

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe4f3d80800 (LWP 2151))]

Thread 4 (Thread 0x7fe4c938b700 (LWP 2166)):
#0  0x7fe4ea0af9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55d66091b784) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55d66091b730,
cond=0x55d66091b758) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55d66091b758, mutex=0x55d66091b730) at
pthread_cond_wait.c:655
#3  0x7fe4ee9b991b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55d66091b730) at
thread/qwaitcondition_unix.cpp:143
#4  QWaitCondition::wait (this=this@entry=0x7fe4d8002f10,
mutex=mutex@entry=0x7fe4d8002f08, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#5  0x7fe4efb289c5 in QFileInfoGatherer::run (this=0x7fe4d8002ef8) at
dialogs/qfileinfogatherer.cpp:251
#6  0x7fe4ee9b8aab in QThreadPrivate::start (arg=0x7fe4d8002ef8) at
thread/qthread_unix.cpp:367
#7  0x7fe4ea0a96db in start_thread (arg=0x7fe4c938b700) at
pthread_create.c:463
#8  0x7fe4ee2ab88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fe4d6e4d700 (LWP 2153)):
#0  0x7fe4eebde796 in timerSourcePrepare (source=0x7fe4d0004c90,
timeout=0x7fe4d6e4cba4) at kernel/qeventdispatcher_glib.cpp:153
#1  0x7fe4e8536998 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe4e853736b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe4e853754c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe4eebdea9b in QEventDispatcherGlib::processEvents
(this=0x7fe4db20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fe4eeb82dea in QEventLoop::exec (this=this@entry=0x7fe4d6e4cd70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7fe4ee9adb8a in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7fe4f07ebe45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7fe4ee9b8aab in QThreadPrivate::start (arg=0x7fe4f0a63d60) at
thread/qthread_unix.cpp:367
#9  0x7fe4ea0a96db in start_thread (arg=0x7fe4d6e4d700) at
pthread_create.c:463
#10 0x7fe4ee2ab88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fe4de9d8700 (LWP 2152)):
#0  0x7fe4ee29ebf9 in __GI___poll (fds=0x7fe4de9d7ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fe4ec36f747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fe4ec37136a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fe4e1999129 in QXcbEventReader::run (this=0x55d6601edc40) at
qxcbconnection.cpp:1388
#4  0x7fe4ee9b8aab in QThreadPrivate::start (arg=0x55d6601edc40) at
thread/qthread_unix.cpp:367
#5  0x7fe4ea0a96db in start_thread (arg=0x7fe4de9d8700) at
pthread_create.c:463
#6  0x7fe4ee2ab88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fe4f3d80800 (LWP 2151)):
[KCrash Handler]
#6  Konsole::ColorScheme::colorTable (this=this@entry=0x7270206120666f20) at
./src/ColorScheme.cpp:329
#7  0x7fe4ca8a3f17 in Konsole::ColorScheme::colorEntry
(this=this@entry=0x7270206120666f20, index=index@entry=0,
randomSeed=randomSeed@entry=62) at ./src/ColorScheme.cpp:244
#8  0x7fe4ca8a4187 in Konsole::ColorScheme::getColorTable
(this=this@entry=0x7270206120666f20, table=table@entry=0x7fff81663f70,
randomSeed=62) at ./src/ColorScheme.cpp:289
#9  0x7fe4ca92de02 in Konsole::ViewManager::applyProfileToView
(this=this@entry=0x55d66096e5a0, view=0x55d66072f6a0, profile=...) at
./src/ViewManager.cpp:774
#10 0x7fe4ca93044a in Konsole::ViewManager::createView
(this=this@entry=0x55d66096e5a0, session=session@entry=0x55d6609608a0,
container=0x55d6605259c0, index=index@entry=-1) at ./src/ViewManager.c

[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

--- Comment #19 from Mustafa Muhammad  ---
(In reply to Shmerl from comment #18)
> It can be a downstream issue with Debian specifically (since according to
> Mesa developers, it doesn't happen on Arch). So I also opened a Debian bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636

I'm not a developer, but I suggest you try booting the latest Neon ISO to check
if it works on your hardware, if it does, it is upstream or distribution issue.

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

[Discover] [Bug 395388] QQmlDelegateModel: Software Center Discover Crashed

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[Discover] [Bug 395388] QQmlDelegateModel: Software Center Discover Crashed

[Mustafa Muhammad]

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

--- Comment #15 from Mustafa Muhammad  ---
Created attachment 116467
  --> https://bugs.kde.org/attachment.cgi?id=116467&action=edit
New crash information added by DrKonqi

plasma-discover (5.14.3) using Qt 5.11.1

- What I was doing when the application crashed:

I searched for yakuake in krunner, it was not installed and was suggested for
installation "Software CenterGet Yakuake", when I pressed enter, discover
started on Yakuake page and then crashed.

Using newly installed Fedora 29 with test updates (plasma-discover-5.14.3)

-- Backtrace (Reduced):
#8  0x7ff5c1e6ab34 in qobject_cast
(object=) at /usr/include/qt5/QtCore/qobject.h:499
#9  QQmlDelegateModelItem::dataForObject (object=object@entry=0x55745a42eca0)
at types/qqmldelegatemodel.cpp:1986
#10 0x7ff5c1e71cb2 in QQmlDelegateModelPrivate::release
(this=0x55745ecf47d0, object=0x55745a42eca0) at types/qqmldelegatemodel.cpp:543
#11 0x7ff5c1e71d56 in QQmlDelegateModelPrivate::release (object=, this=) at types/qqmldelegatemodel.cpp:567
#12 QQmlDelegateModel::release (this=, item=) at
types/qqmldelegatemodel.cpp:567

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

[Discover] [Bug 401300] New: Discover can't install missing flatpak backend in Fedora

[Mustafa Muhammad]

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

Bug ID: 401300
   Summary: Discover can't install missing flatpak backend in
Fedora
   Product: Discover
   Version: 5.14.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

SUMMARY
Using discover on Fedora, in the settings, I had "Missing Backends" part, I
pressed the button in front of "Flatpak Backend", it wasn't installed, and the
whole "Missing Backends" part disappeared.
Even after I close Discover and start it again, it gets hidden immediately
after I press Settings.

STEPS TO REPRODUCE
1. Open Discover on a newly installed Fedora KDE with updates and test updates
applied (Maybe not required, but in my case, these are the details)
2. In Discover Settings, press install in front of "Flatpak Backend"
3. 

OBSERVED RESULT
The "Missing Backends" part disappears

EXPECTED RESULT

The backend should be installed.

Operating System: Fedora 29
KDE Plasma Version: 5.14.3
Qt Version: 5.11.1
KDE Frameworks Version: 5.52.0
Kernel Version: 4.19.2-301.fc29.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 15.4 GiB of RAM

ADDITIONAL INFORMATION

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

[Discover] [Bug 401417] New: Searching menu for an app then trying to manage it (right click -> manage) opens then crashes discover

[Mustafa Muhammad]

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

Bug ID: 401417
   Summary: Searching menu for an app then trying to manage it
(right click -> manage) opens then crashes discover
   Product: Discover
   Version: 5.14.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.14.3)

Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.19.4-300.fc29.x86_64 x86_64
Distribution: "Fedora release 29 (Twenty Nine)"

-- Information about the crash:
Trying to manage app (using discover), by right clicking it and pressing
"Manage Ktorrent", causes discover to be opened, shows ktorrent 'Install'
button, which is wrong, because it is already installed, there should be
"Remove" and "Launch", and after a second, discover crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc591fd8940 (LWP 7993))]

Thread 21 (Thread 0x7fc5357fa700 (LWP 8026)):
#0  0x7fc5951d23d1 in poll () from /lib64/libc.so.6
#1  0x7fc5926ba5a6 in ?? () from /lib64/libglib-2.0.so.0
#2  0x7fc5926ba6d0 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc59588182b in QEventDispatcherGlib::processEvents
(this=0x7fc508000b50, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc59583017b in QEventLoop::exec (this=this@entry=0x7fc5357f9c60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fc595698046 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fc5956a14bb in QThreadPrivate::start (arg=0x7fc580008de0) at
thread/qthread_unix.cpp:367
#7  0x7fc594df458e in start_thread () from /lib64/libpthread.so.0
#8  0x7fc5951dd653 in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fc5367fc700 (LWP 8025)):
#0  0x7fc5951cdf34 in read () from /lib64/libc.so.6
#1  0x7fc592700aa0 in ?? () from /lib64/libglib-2.0.so.0
#2  0x7fc5926ba09b in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fc5926ba550 in ?? () from /lib64/libglib-2.0.so.0
#4  0x7fc5926ba6d0 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fc59588182b in QEventDispatcherGlib::processEvents
(this=0x7fc514000b50, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fc59583017b in QEventLoop::exec (this=this@entry=0x7fc5367fbc60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7fc595698046 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7fc5956a14bb in QThreadPrivate::start (arg=0x7fc5640eb8a0) at
thread/qthread_unix.cpp:367
#9  0x7fc594df458e in start_thread () from /lib64/libpthread.so.0
#10 0x7fc5951dd653 in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fc536ffd700 (LWP 8018)):
#0  0x7fc594dfab68 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc5956a1a25 in QWaitConditionPrivate::wait_relative (time=3,
this=0x55cd68798ed0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x55cd68798ed0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x55cd6a7fb5f0,
mutex=mutex@entry=0x55cd6853cfe0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7fc595699cd2 in QThreadPoolThread::run (this=0x55cd6a7fb5e0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:240
#5  0x7fc5956a14bb in QThreadPrivate::start (arg=0x55cd6a7fb5e0) at
thread/qthread_unix.cpp:367
#6  0x7fc594df458e in start_thread () from /lib64/libpthread.so.0
#7  0x7fc5951dd653 in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7fc5377fe700 (LWP 8017)):
#0  0x7fc594dfab68 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc5956a1a25 in QWaitConditionPrivate::wait_relative (time=3,
this=0x55cd6aa01ae0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x55cd6aa01ae0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x55cd68ae6b40,
mutex=mutex@entry=0x55cd6853cfe0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7fc595699cd2 in QThreadPoolThread::run (this=0x55cd68ae6b30) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:240
#5  0x7fc5956a14bb in QThreadPrivate::start (arg=0x55cd68ae6b30) at
thread/qthread_unix.cpp:367
#6  0x7fc594df458e in start_thread () from /lib64/libpthread.so.0
#7  0x7fc5951dd653 in clone () from /lib64/libc.so.6

Thread 17 (Thr

[plasmashell] [Bug 390778] New: plasmashell crash probably related to search

[Mustafa Muhammad]

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

Bug ID: 390778
   Summary: plasmashell crash probably related to search
   Product: plasmashell
   Version: 5.12.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 110838
  --> https://bugs.kde.org/attachment.cgi?id=110838&action=edit
Saved bug report with backtrace

Opened the menu and searched, also krunner crashes on search, so probably
search related. I am using Fedora Rawhide with Plasma 5.12.1

Application: plasmashell (5.12.1)

Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.16.0-0.rc1.git4.1.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Rawhide)"

I tried to report using DrKonqi but got error code 114 from bugzilla "Comments
cannot be longer then 65535"

Attached the saved bug report (with backtrace)

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #17 from Mustafa Muhammad  ---
(In reply to Alexander Mentyu from comment #16)
> Is this issue still reproducible?

I don't think so, at least not for me, I don't mind closing it, it's your call.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #15 from Mustafa Muhammad  ---
(In reply to Martin Flöser from comment #14)
> What I need is to know where the problem happens. For that I ideally get a
> backtrace with debug symbols. Without that all is just guessing
> unfortunately.

I'll try to provide another backtrace with debug symbols (I think I already
provided one), but the session is very unstable these days (crash when I
traverse the menu), so maybe later.

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

[Discover] [Bug 388978] New: Sometimes searching crashes Discover

[Mustafa Muhammad]

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

Bug ID: 388978
   Summary: Sometimes searching crashes Discover
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.11.90)

Qt Version: 5.9.3
Frameworks Version: 5.42.0
Operating System: Linux 4.13.0-26-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:
Searching in Discover, I opened a new report because this is an up to date neon
dev (from git)

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fece67358c0 (LWP 5014))]

Thread 9 (Thread 0x7fec97dd3700 (LWP 5045)):
#0  0x7fece1bc024d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc9316f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ede74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fecdc8ee330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fec97dd2d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#8  0x7fece25ca709 in QThreadPrivate::start (arg=0x2a19f90) at
thread/qthread_unix.cpp:368
#9  0x7fecde7776ba in start_thread (arg=0x7fec97dd3700) at
pthread_create.c:333
#10 0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7feca60e0700 (LWP 5024)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7fec9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca60dfd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2d78db0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca60e0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7feca7d96700 (LWP 5021)):
#0  0x7fecdc932a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fecdc8ee23d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7feca7d95d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x2c264d0) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7feca7d96700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fecadfa0700 (LWP 5020)):
#0  0x7fece1bc470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fecdc8ee38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fecdc8ee49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fece27f46cb in QEventDispatcherGlib::processEvents
(this=0x7feca80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fece279ce2a in QEventLoop::exec (this=this@entry=0x7fecadf9fd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fece25c58f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fece25ca709 in QThreadPrivate::start (arg=0x3d96820) at
thread/qthread_unix.cpp:368
#7  0x7fecde7776ba in start_thread (arg=0x7fecadfa0700) at
pthread_create.c:333
#8  0x7fece1bd03dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fecb9a12700 (LWP 5019)):
#0  __GI___pthread_getspecific (key=3) at pthread_getspecific.c:30
#1  0x7

[Discover] [Bug 388990] New: Discover fails to install flatpak application

[Mustafa Muhammad]

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

Bug ID: 388990
   Summary: Discover fails to install flatpak application
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Flatpak Backend
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

Discover fails to install an application, I tested Telegram, I started Discover
from terminal and got this log:

mustafa@mustafa-pc:~$ plasma-discover 
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x21e4ee0)
Failed to install "org.telegram.desktop" :
"GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file does
not start with a group"

Using Neon dev git-unstable, Discover version 5.11.90
With flatpak backend installed

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

[Discover] [Bug 388990] Discover fails to install flatpak application

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
OK, the problem is probably in flatpak, it didn't install it from console too:

mustafa@mustafa-pc:~$ flatpak install flathub org.telegram.desktop
Installing: org.telegram.desktop/x86_64/stable from flathub
[] 1 metadata, 0 content objects fetched; 569 B transferred
in 1 se
error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file
does not start with a group

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

[Discover] [Bug 388990] Discover fails to install flatpak application

[Mustafa Muhammad]

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

--- Comment #3 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #2)
> Please check your installation.

Yes, it was fixed by the upstream flatpak fix, thank you.

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

--- Comment #6 from Mustafa Muhammad  ---
Created attachment 109265
  --> https://bugs.kde.org/attachment.cgi?id=109265&action=edit
New crash information added by DrKonqi

plasma-discover (5.11.3) using Qt 5.9.2

- What I was doing when the application crashed:

Just searching in Discover.

I attached full debug info, I use version 5.11.3 you mentioned on Fedora 27
(test-updates).

In case this is related, I use the flatpak backend, not likely, but may be
related.

-- Backtrace (Reduced):
#7  0x7f2435fd2de2 in AbstractResourcesBackend::Filters::shouldFilter
(this=0x5558562a45c0, res=0x555854205190) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:114
#8  0x7f2435fd30fd in AbstractResourcesBackend::Filters::filterJustInCase
(this=this@entry=0x5558562a45c0, input=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:127
#9  0x7f2435fcaf12 in ResourcesProxyModel::addResources
(this=0x5558562a4590, _res=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesProxyModel.cpp:174
[...]
#11 0x7f2435fe23d2 in ResultsStream::resourcesFound
(this=this@entry=0x5558562ca0d0, _t1=...) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/x86_64-redhat-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:142
#12 0x7f2435fc2ec0 in AggregatedResultsStream::emitResults
(this=0x5558562ca0d0) at
/usr/src/debug/plasma-discover-5.11.3-1.fc27.x86_64/libdiscover/resources/ResourcesModel.cpp:284

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

[Discover] [Bug 385554] Discover crashes in AbstractResourcesBackend::Filters::shouldFilter() while searching

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

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

[dolphin] [Bug 387842] New: Dolphin crash while moving files

[Mustafa Muhammad]

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

Bug ID: 387842
   Summary: Dolphin crash while moving files
   Product: dolphin
   Version: 17.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mustafa10...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.08.1)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.16-302.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
- What I was doing when the application crashed:
I was moving a large directory from one partition to another, maybe I hit
ctrl+z after finishing copying, but I think dolphin crashed when it was
creating the 2000+ nested directories to move the files.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc0fad84940 (LWP 2169))]

Thread 4 (Thread 0x7fc0c992e700 (LWP 2173)):
#0  0x7fc0f26c18bb in poll () from /lib64/libc.so.6
#1  0x7fc0ea1bfed9 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc0ea1bffec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc0f352c35b in QEventDispatcherGlib::processEvents
(this=0x7fc0c4000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc0f34da0ea in QEventLoop::exec (this=this@entry=0x7fc0c992dc70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fc0f332b8ba in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x555829ab7a70) at
thread/qthread_unix.cpp:368
#7  0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc0d9ada700 (LWP 2172)):
#0  0x7fc0f26bce38 in read () from /lib64/libc.so.6
#1  0x7fc0ea2040e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fc0ea1bf9e8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fc0ea1bfe80 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fc0ea1bffec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fc0f352c35b in QEventDispatcherGlib::processEvents
(this=0x7fc0cc000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fc0f34da0ea in QEventLoop::exec (this=this@entry=0x7fc0d9ad9c30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fc0f332b8ba in QThread::exec (this=this@entry=0x7fc0f5763060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:515
#8  0x7fc0f54ef479 in QDBusConnectionManager::run (this=0x7fc0f5763060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x7fc0f5763060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#10 0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#11 0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc0dbdf8700 (LWP 2171)):
#0  0x7fc0f26c18bb in poll () from /lib64/libc.so.6
#1  0x7fc0e972efe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fc0e9730dda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fc0ddf5aa49 in QXcbEventReader::run (this=0x5558294f26d0) at
qxcbconnection.cpp:1335
#4  0x7fc0f332fb92 in QThreadPrivate::start (arg=0x5558294f26d0) at
thread/qthread_unix.cpp:368
#5  0x7fc0eeb4d609 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc0f26cde6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc0fad84940 (LWP 2169)):
[KCrash Handler]
#6  QMetaObject::activate (sender=sender@entry=0x55582f071650, signalOffset=3,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff645bcff0)
at kernel/qobject.cpp:3638
#7  0x7fc0f3504237 in QMetaObject::activate
(sender=sender@entry=0x55582f071650, m=m@entry=0x7fc0f54d5f00
, local_signal_index=local_signal_index@entry=4,
argv=argv@entry=0x7fff645bcff0) at kernel/qobject.cpp:3628
#8  0x7fc0f5282341 in KJob::description (this=this@entry=0x55582f071650,
_t1=, _t1@entry=0x55582f071650, _t2=..., _t3=..., _t4=...) at
/usr/src/debug/kf5-kcoreaddons-5.40.0-1.fc27.x86_64/x86_64-redhat-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:577
#9  0x7fc0f88f9948 in KIO::UndoJob::emitMoving (dest=..., src=...,
this=0x55582f071650) at
/usr/src/debug/kf5-kio-5.40.0-2.fc27.x86_64/src/widgets/fileundomanager.cpp:131
#10 KIO::FileUndoManagerPrivate::stepMovingFiles
(this=this@entry=0x555829591a50) at
/usr/src/debug/kf5-kio-5.40.0-2.fc27.x86_64/src/widgets/fileundomanager.cpp:55

[Discover] [Bug 380146] New: Discover crashes on start

[Mustafa Muhammad]

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

Bug ID: 380146
   Summary: Discover crashes on start
   Product: Discover
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.90)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.1-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Just started the latest Discover from openSUSE KDE git repos

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f307cbe28c0 (LWP 1952))]

Thread 10 (Thread 0x7f30397c0700 (LWP 1980)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfbbc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3078c6547b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3078c1110a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3078a4eb3b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3078a533ca in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#8  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f303a5ed700 (LWP 1961)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfe32 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f303bd36ef6 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f3072d07385 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f303adee700 (LWP 1960)):
#0  0x7f30780447bd in poll () at /lib64/libc.so.6
#1  0x7f3072cdfaa6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3072cdfbbc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3072cdfc01 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f3072d07385 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3074bf5537 in start_thread () at /lib64/libpthread.so.0
#6  0x7f307804e04f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f304a4a9700 (LWP 1958)):
#0  0x7f3074bfb9a6 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3078a541fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3078a4d733 in QSemaphore::acquire(int) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f3078c3daf2 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3076d317a8 in QHttpThreadDelegate::encryptedSlot() () at
/usr/lib64/libQt5Network.so.5
#5  0x7f3076dd05cd in QHttpThreadDelegate::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Network.so.5
#6  0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f3076cf3c5d in QHttpNetworkConnectionChannel::_q_encrypted() () at
/usr/lib64/libQt5Network.so.5
#8  0x7f3076cf441d in
QHttpNetworkConnectionChannel::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () at /usr/lib64/libQt5Network.so.5
#9  0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f3076dc59c7 in QSslSocketBackendPrivate::continueHandshake() () at
/usr/lib64/libQt5Network.so.5
#11 0x7f3076dc99f3 in QSslSocketBackendPrivate::startHandshake() () at
/usr/lib64/libQt5Network.so.5
#12 0x7f3076dca3ce in QSslSocketBackendPrivate::transmit() () at
/usr/lib64/libQt5Network.so.5
#13 0x7f3076db57e1 in QSslSocket::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Network.so.5
#14 0x7f3078c3d887 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#15 0x7f3076d85373 in QAbstractSocketPrivate::emitReadyRead(int) () at
/usr/lib64/libQt5Network.so.5
#16 0x7f3076d8542c in QAbstractSocketPrivate::canReadNotification() () at
/usr/lib64/libQt5Network.so.5
#17 0x7f3076d96b31 in QReadNotifier::event(QEvent*) () at
/usr/lib64/libQt5Network.so.5
#18 0x7f307a1e3fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f307a1eb2e1 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f3078c12968 in QCoreApplicati

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #1)
> Interesting. Would you be able to provide a backtrace with debug symbols?
> That would make it much easier to find where the issue is.

I think I already did, I installed debug symbols, and reloaded the backtrace,
which is here in the bug.

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

[Discover] [Bug 381188] New: Discover crash on start

[Mustafa Muhammad]

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

Bug ID: 381188
   Summary: Discover crash on start
   Product: Discover
   Version: 5.10.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.1)

Qt Version: 5.7.1
Frameworks Version: 5.35.0
Operating System: Linux 4.11.0-2.fc26.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Just opened discover on a fresh installation of F26 beta, happens everytime.
I think I know the problem, flatpack is not installed, maybe this is causing
the crash.
I didn't generate better backtrace because I think I knew the problem, I can do
so if you want, but after installing flatpak it doesn't crash on start anymore.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb920c268c0 (LWP 5289))]

Thread 5 (Thread 0x7fb8f702e700 (LWP 5294)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb9202af8a6 in QQuickPixmapReader::run() () from
/lib64/libQt5Quick.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fb8fd788700 (LWP 5292)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb91d4bf3c5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb8fe999700 (LWP 5291)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb915100599 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fb9151006ac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb91cc04d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb91cbb4b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb91ca09efa in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb920d74709 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#7  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#9  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb90708a700 (LWP 5290)):
#0  0x7fb91bde8dad in poll () from /lib64/libc.so.6
#1  0x7fb9149fec97 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7fb914a00a8a in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7fb90b74cb99 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7fb91ca0e1ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fb91a95736d in start_thread () from /lib64/libpthread.so.0
#6  0x7fb91bdf4e9f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb920c268c0 (LWP 5289)):
[KCrash Handler]
#6  0x7fb8e72e35fd in FlatpakBackend::setupFlatpakInstallations(_GError**)
() from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#7  0x7fb8e72e9a38 in FlatpakBackend::FlatpakBackend(QObject*) () from
/usr/lib64/qt5/plugins/discover/flatpak-backend.so
#8  0x7fb8e72ec6bb in FlatpakBackendFactory::newInstance(QObject*, QString
const&) const () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#9  0x7fb91ff77427 in DiscoverBackendsFactory::backendForFile(QString
const&, QString const&) const () from
/usr/lib64/plasma-discover/libDiscoverCommon.so
#10 0x7fb91ff77abb in DiscoverBackendsFactory::backe

[plasmashell] [Bug 381431] New: Plasma crashes when I traverse through the application menu

[Mustafa Muhammad]

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

Bug ID: 381431
   Summary: Plasma crashes when I traverse through the application
menu
   Product: plasmashell
   Version: 5.10.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mustafa10...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.34.0
Operating System: Linux 4.10.1-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was walking through the application menu in a wayland plasma session.

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 0x7f5a751058c0 (LWP 1537))]

Thread 12 (Thread 0x7f59a1eae700 (LWP 1818)):
[KCrash Handler]
#6  0x7f5a6d6515c0 in wl_proxy_create_wrapper () at
/usr/lib64/libwayland-client.so.0
#7  0x7f59cce97b81 in  () at /usr/lib64/libEGL_mesa.so.0
#8  0x7f59cce8657e in  () at /usr/lib64/libEGL_mesa.so.0
#9  0x7f59cd54c870 in  () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f59cd54aebd in  () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#11 0x7f5a6f8675ee in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib64/libQt5Gui.so.5
#12 0x7f5a72b69f14 in  () at /usr/lib64/libQt5Quick.so.5
#13 0x7f5a72b714db in  () at /usr/lib64/libQt5Quick.so.5
#14 0x7f5a72b707d7 in  () at /usr/lib64/libQt5Quick.so.5
#15 0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#16 0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#18 0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f59a28cd700 (LWP 1817)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f59a3343700 (LWP 1783)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f59a882d700 (LWP 1770)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f59ab62c700 (LWP 1610)):
#0  0x7f5a6e70e08d in poll () at /lib64/libc.so.6
#1  0x7f5a6953cce9 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5a6953cdfc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5a6f02975b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5a6efd2d0a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5a6ee0505a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f59adec3f37 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5a6dfd14e7 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5a6e717a2f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f59c48ba700 (LWP 1593)):
#0  0x7f5a6dfd75ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5a6ee0aa5b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5a72b70748 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f5a72b70b7a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f5a6ee0973e in  () at /usr/lib64/libQt5Core.so.5
#5  0x000

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #5 from Mustafa Muhammad  ---
Sorry for the late response
mustafa@mustafa-pc:~> plasma-discover --listbackends
Available backends:
 * kns-backend
 * packagekit-backend


mustafa@mustafa-pc:~> plasma-discover 
QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:9 Type Kirigami.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/ApplicationWindow.qml:25
Type Base.ApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationWindow.qml:97 Type
AbstractApplicationWindow unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:21
plugin cannot be loaded for module "QtQuick.Controls": Cannot load library
/usr/lib64/qt5/qml/QtQuick/Controls.2/libqtquickcontrols2plugin.so:
(/usr/lib64/libQt5QuickControls2.so.5: symbol
_ZNK14QPlatformTheme22standardButtonShortcutEi, version Qt_5.9.0_PRIVATE_API
not defined in file libQt5Gui.so.5 with link time reference)

Errors when loading the GUI
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "servicemenu.knsrc"
Discarding invalid backend "ksysguard.knsrc"
setting currentApplicationBackend PackageKitBackend(0x55c7b6668720)

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

[systemsettings] [Bug 381518] New: systemsettings5 crash on start

[Mustafa Muhammad]

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

Bug ID: 381518
   Summary: systemsettings5 crash on start
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

I am using plasma from git branches (openSUSE KDE unstable repos), I can't
start systemsettings

mustafa@mustafa-pc:~> systemsettings5
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kpackage-genericqml.desktop, tried
("/home/mustafa/.local/share", "/usr/share")
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:31:5:
Type CategoriesPage unavailable 
 CategoriesPage { 
 ^
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:22:1:
plugin cannot be loaded for module "QtQuick.Controls": Cannot load library
/usr/lib64/qt5/qml/QtQuick/Controls.2/libqtquickcontrols2plugin.so:
(/usr/lib64/libQt5QuickControls2.so.5: symbol
_ZNK14QPlatformTheme22standardButtonShortcutEi, version Qt_5.9.0_PRIVATE_API
not defined in file libQt5Gui.so.5 with link time reference) 
 import QtQuick.Controls 2.0 as QtControls2 
 ^
Segmentation fault (core dumped)

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

[systemsettings] [Bug 381518] systemsettings5 crash on start

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
(In reply to Luca Beltrame from comment #3)
> Please update from the unstable repositories:
> 
> > usr/lib64/libQt5QuickControls2.so.5: symbol 
> > _ZNK14QPlatformTheme22standardButtonShortcutEi
> 
> There was a change in the Qt packages, I rebuilt everything and it is fixed.

It is fixed, thanks, I was using the "KDE:/Qt59" branch (before the instruction
update), now on "KDE:/Unstable:/Qt" everything works fine.

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

[Discover] [Bug 380146] Discover crashes on start

[Mustafa Muhammad]

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

--- Comment #8 from Mustafa Muhammad  ---
Sorry for the delay, I was away from this machine, it is working fine now,
thanks.

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

[konsole] [Bug 369316] Crash in Konsole::TerminalDisplay::updateCursor

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Kurt Hindenburg from comment #1)
> Do you have any non-default settings w/ respect to the cursor?  or any other
> info about when it crashes?

No, I don't think I do, and now I am using Tumbleweed and I don't see it
anymore, feel free to close it and if it happens again, I'll report.

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

[Discover] [Bug 381188] Discover crash on start

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Christoph Feck from comment #1)
> Related to bug 380496.
> 
> Does installing 'flatpak' help to resolve the crash?

Yes, it does.

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

[Discover] [Bug 372277] New: Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

Bug ID: 372277
   Summary: Discover crashes when used to open rpm file
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

I tried to open chrome rpm using plasma-discover and it crashed, this is the
backtrace (drkonqi couldn't report it because it says "plasma-discover doesn't
provide a bug reporting address")


Application: plasma-discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 62: movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f70fd067900 (LWP 7793))]

Thread 5 (Thread 0x7f70e0b77700 (LWP 7798)):
#0  g_mutex_unlock (mutex=0x7f70d8000990) at gthread-posix.c:1348
#1  0x7f7102299ffd in g_main_context_iterate
(context=context@entry=0x7f70d8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3877
#2  0x7f710229a26c in g_main_context_iteration (context=0x7f70d8000990,
may_block=may_block@entry=1) at gmain.c:3990
#3  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e0b76cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f7109d6e643 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x7f70d4003650) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e0b77700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f70e1378700 (LWP 7797)):
#0  0x7f71022df7f9 in g_mutex_lock (mutex=mutex@entry=0x7f70d4000990) at
gthread-posix.c:1336
#1  0x7f710229a258 in g_main_context_iteration (context=0x7f70d4000990,
may_block=may_block@entry=1) at gmain.c:3989
#2  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e1377c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#4  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c70825080) at
thread/qthread.cpp:507
#5  0x7f710cfd6ca6 in QQuickPixmapReader::run (this=0x564c70825080) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/util/qquickpixmapcache.cpp:823
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c70825080) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e1378700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f70e3fff700 (LWP 7796)):
#0  0x7f710915a00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f710229a156 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f70dc002e70, timeout=, context=0x7f70dc000990)
at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f70dc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3924
#3  0x7f710229a26c in g_main_context_iteration (context=0x7f70dc000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e3ffeca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c6f3b4ad0) at
thread/qthread.cpp:507
#7  0x7f710a824735 in QQmlThreadPrivate::run (this=0x564c6f3b4ad0) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#8  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c6f3b4ad0) at
thread/qthread_unix.cpp:344
#9  0x7f71076ac6ca in start_thread (arg=0x7f70e3fff700) at
pthread_create.c:333
#10 0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f70e97f6700 (LWP 7795)):
[KCrash Handler]
#6  0x7f7109f3c87d in QObject::disconnect (sender=0x7f70d8003860,
signal=signal@entry=0x0, receiver=receiver@entry=0x7f70e4014a70,
method=method@entry=0x0) at kernel/qobject.cpp:2956
#7  0x7f710d877fd0 in QObject::disconnect (member=0x0,
receiver=0x7f70e4014a70, this=) at
../../src/corelib/kernel/qobject.h:359
#8  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7f70e4014a70) at
qdbusintegrator.cpp:1133
#9  0x7f710d8648c2 in QDBusConnectionManager::run (this=0x7f710d8da060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbus

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
(In reply to Aleix Pol from comment #1)
> Please fill version and platform fields.
> 
> Also how do you open an rpm file?

Couldn't find 5.8.1 in versions, thus I chose unspecified.
Fedora 25 RC, plasma-discover 5.8.1

Right clicked the rpm, and chose plasma-discover from the "Open
With->Other->(searched for it)"

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
(In reply to Rex Dieter from comment #3)
> I didn't think discover supported installing packages directly, it's desktop
> file only contains:
> MimeType=x-scheme-handler/appstream;
> 
> (no mention of package mimetypes)

Maybe it doesn't, I was trying, and I think it should support this.

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

[yakuake] [Bug 375030] New: Yakuake crash on exit under wayland session

[Mustafa Muhammad]

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

Bug ID: 375030
   Summary: Yakuake crash on exit under wayland session
   Product: yakuake
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.2+)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.0-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
I use KDE git packages from openSUSE repos for Tumbleweed, yakuake crashes
everytime I close it (from the x button), I use wayland which may have
something to do with the crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a61eedd40 (LWP 2248))]

Thread 2 (Thread 0x7f5a4c53c700 (LWP 2249)):
#0  0x7f5a5c9ef66d in poll () from /lib64/libc.so.6
#1  0x7f5a57374886 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5a5737499c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5a5d31048b in QEventDispatcherGlib::processEvents
(this=0x7f5a440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5a5d2b95ea in QEventLoop::exec (this=this@entry=0x7f5a4c53bcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5a5d0e6b03 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f5a5eea2b99 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f5a5d0eb906 in QThreadPrivate::start (arg=0x7f5a5f116d20) at
thread/qthread_unix.cpp:368
#8  0x7f5a58ea3454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f5a5c9f837f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5a61eedd40 (LWP 2248)):
[KCrash Handler]
#6  0x7f5a4ef2af49 in wl_map_insert_at () from
/usr/lib64/libwayland-client.so.0
#7  0x7f5a4ef2716e in wl_proxy_destroy () from
/usr/lib64/libwayland-client.so.0
#8  0x7f5a4e198415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#9  KWayland::Client::WaylandPointer::release
(this=0x1ffcb20, this=0x1ffcb20) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/wayland_pointer_p.h:53
#10 KWayland::Client::Registry::release (this=this@entry=0x1ffca80) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:358
#11 0x7f5a4e19843c in KWayland::Client::Registry::~Registry
(this=0x1ffca80, __in_chrg=) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:353
#12 0x7f5a4e1984d9 in KWayland::Client::Registry::~Registry
(this=0x1ffca80, __in_chrg=) at
/usr/src/debug/kwayland-5.30.0git.20170108T154523~168f3c2/src/client/registry.cpp:354
#13 0x7f5a5d2e5e51 in QObjectPrivate::deleteChildren
(this=this@entry=0x1ffc7c0) at kernel/qobject.cpp:1970
#14 0x7f5a5d2ef22f in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#15 0x7f5a428367e3 in WaylandIntegration::~WaylandIntegration
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:51
#16 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:37
#17 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.8.90git~20170112T153549~41373d2/src/windowsystem/waylandintegration.cpp:43
#18 0x7f5a5c945ea0 in __run_exit_handlers () from /lib64/libc.so.6
#19 0x7f5a5c945efa in exit () from /lib64/libc.so.6
#20 0x7f5a5c92f298 in __libc_start_main () from /lib64/libc.so.6
#21 0x00417aaa in _start ()

Reported using DrKonqi

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

[kwin] [Bug 375971] New: kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

Bug ID: 375971
   Summary: kwin_wayland take 100% CPU
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Created attachment 103804
  --> https://bugs.kde.org/attachment.cgi?id=103804&action=edit
strace -t

Using Neon Wayland Dev Unstable (git master), kwin_wayland is taking 100 of CPU
core, and memory usage wet up to 2G then down again, but CPU stayed 100% (about
an hour now), I asked in #kwin and they suggested using strace, so this is some
output, something wrong with sendmsg and recvmsg.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #1 from Mustafa Muhammad  ---
Created attachment 103805
  --> https://bugs.kde.org/attachment.cgi?id=103805&action=edit
strace

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #2 from Mustafa Muhammad  ---
Created attachment 103806
  --> https://bugs.kde.org/attachment.cgi?id=103806&action=edit
strace -c

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
It happens sometimes, I didn't use gdb before, I used:
gdb -p `pidof kwin_wayland` -ex bt -ex 'thread apply all bt full' -ex detach
-ex quit &> kwin_wayland_trace

to create the attached file, hope it helps, please let me know if there is
anything else I can provide

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #5 from Mustafa Muhammad  ---
Created attachment 103904
  --> https://bugs.kde.org/attachment.cgi?id=103904&action=edit
kwin_wayland trace

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #7 from Mustafa Muhammad  ---
Created attachment 103912
  --> https://bugs.kde.org/attachment.cgi?id=103912&action=edit
trace with debug packages installed

I installed all debug packages I could find in the file and generated a new
trace.

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

[kwin] [Bug 375971] kwin_wayland take 100% CPU

[Mustafa Muhammad]

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

--- Comment #9 from Mustafa Muhammad  ---
It is the same process, still running until now if you want something, maybe
different timing can cause different gdb output :)

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Mustafa Muhammad]

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

Mustafa Muhammad  changed:

   What|Removed |Added

 CC||mustafa10...@gmail.com

--- Comment #8 from Mustafa Muhammad  ---
I think this should become confirmed, happens to me on openSUSE Tumbleweed too,
with 5.8.5 and with latest git packages (from openSUSE unstable KDE repos)

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

[kinfocenter] [Bug 374835] New: kinfocenter crashes under wayland session when selecting X-Server info

[Mustafa Muhammad]

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

Bug ID: 374835
   Summary: kinfocenter crashes under wayland session when
selecting X-Server info
   Product: kinfocenter
   Version: 5.8.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Application: kinfocenter (5.8.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Under wayland session, I opened kinfocenter -> Graphical Information ->
X-Server, and kinfocenter crashed, this happens everytime on multiple
configurations (openSUSE Tumbleweed with 5.8.5 and latest git packages, I also
remember seeing this on Fedora and Neon

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7fcfdefca700 (LWP 2118)):
#0  0x7fcff12f166d in poll () from /lib64/libc.so.6
#1  0x7fcfebaa5876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fcfebaa598c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fcff1c1118b in QEventDispatcherGlib::processEvents
(this=0x7fcfd80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fcff1bbaaea in QEventLoop::exec (this=this@entry=0x7fcfdefc9cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fcff19e8813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fcfefb35385 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fcff19ed4c8 in QThreadPrivate::start (arg=0x7fcfefda6d20) at
thread/qthread_unix.cpp:368
#8  0x7fcfeda7d454 in start_thread () from /lib64/libpthread.so.0
#9  0x7fcff12fa37f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fcff48628c0 (LWP 2117)):
[KCrash Handler]
#6  0x7fcfe2b36f49 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7fcfe2b3316e in proxy_destroy (proxy=0x1d49630) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x1d49630) at src/wayland-client.c:442
#9  0x7fcfe1b7c415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer::release
(this=0x1f617e0, this=0x1f617e0) at
/usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::Registry::release (this=this@entry=0x1f60a30) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358
#12 0x7fcfe1b7c43c in KWayland::Client::Registry::~Registry
(this=0x1f60a30, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353
#13 0x7fcfe1b7c4d9 in KWayland::Client::Registry::~Registry
(this=0x1f60a30, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354
#14 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f63b80) at kernel/qobject.cpp:1970
#15 0x7fcff1bf02bf in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#16 0x7fcfd2a26df9 in WaylandModule::~WaylandModule (this=0x1b64f50,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/base/info_wayland.cpp:48
#17 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f2fd30) at kernel/qobject.cpp:1970
#18 0x7fcff28edeeb in QWidget::~QWidget (this=0x1ca53a0,
__in_chrg=) at kernel/qwidget.cpp:1694
#19 0x7fcff2b65489 in QTreeWidget::~QTreeWidget (this=0x1ca53a0,
__in_chrg=) at itemviews/qtreewidget.cpp:2559
#20 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1f17bd0) at kernel/qobject.cpp:1970
#21 0x7fcff28edeeb in QWidget::~QWidget (this=0x1f61a60,
__in_chrg=) at kernel/qwidget.cpp:1694
#22 0x7fcff2a3bc09 in QStackedWidget::~QStackedWidget (this=0x1f61a60,
__in_chrg=) at widgets/qstackedwidget.cpp:149
#23 0x7fcff1be6f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x1bb4c00) at kernel/qobject.cpp:1970
#24 0x7fcff28edeeb in QWidget::~QWidget (this=0x1b87bd0,
__in_chrg=) at kernel/qwidget.cpp:1694
#25 0x7fcff3cd53fd in KCModule::~KCModule (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kconfigwidgets-5.29.0/src/kcmodule.cpp:177
#26 0x7fcfd2a20bde in KInfoListWidget::~KInfoListWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/info.h:36
#27 KWaylandInfoWidget::~KWaylandInfoWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/main.cpp:57
#28 KWaylandInfoWidget::~KWaylandInfoWidget (this=0x1b87bd0,
__in_chrg=) at
/usr/src/debug/kinfocenter-5.8.5/Modules/info/main.cpp:57
#29 0x7fc

[ksmserver] [Bug 374836] New: ksmserver-logout-greeter crashes on logout from wayland session

[Mustafa Muhammad]

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

Bug ID: 374836
   Summary: ksmserver-logout-greeter crashes on logout from
wayland session
   Product: ksmserver
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

Using openSUSE Tumbleweed, ksmserver-logout-greeter crashes when I try to
logout from wayland session, also drkonkqi5 says it can't report the crash
because ksmserver-logout-greeter doesn't offer bug reporting address.

Here is the crash log:

Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7027867480 (LWP 9091))]

Thread 2 (Thread 0x7f7011304700 (LWP 9092)):
#0  0x7f70231db66d in poll () from /lib64/libc.so.6
#1  0x7f701bed7876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f701bed798c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7023afb18b in QEventDispatcherGlib::processEvents
(this=0x7f700c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7023aa4aea in QEventLoop::exec (this=this@entry=0x7f7011303c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f70238d2813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f702464e385 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f70238d74c8 in QThreadPrivate::start (arg=0x7f70248bfd20) at
thread/qthread_unix.cpp:368
#8  0x7f701dbf9454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f70231e437f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7027867480 (LWP 9091)):
[KCrash Handler]
#6  0x7f701e683f49 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7f701e68016e in proxy_destroy (proxy=0x161dec0) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x161dec0) at src/wayland-client.c:442
#9  0x7f7026ba6415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer::release
(this=0x161d4f0, this=0x161d4f0) at
/usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::Registry::release (this=this@entry=0x161e6e0) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358
#12 0x7f7026ba643c in KWayland::Client::Registry::~Registry
(this=0x161e6e0, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353
#13 0x7f7026ba64d9 in KWayland::Client::Registry::~Registry
(this=0x161e6e0, __in_chrg=) at
/usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354
#14 0x7f7023ad0f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x162c270) at kernel/qobject.cpp:1970
#15 0x7f7023ada2bf in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#16 0x7f70081da753 in ?? () from
/usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#17 0x7f7023131ea0 in __run_exit_handlers () from /lib64/libc.so.6
#18 0x7f7023131efa in exit () from /lib64/libc.so.6
#19 0x7f702311b298 in __libc_start_main () from /lib64/libc.so.6
#20 0x004060fa in _start ()

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

[kate] [Bug 478230] Kate snippets: crash when editing a snippet repository

[Abd AlHaleem Bakkor Mustafa]

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

Abd AlHaleem Bakkor Mustafa  changed:

   What|Removed |Added

 CC||abode...@gmail.com

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

[kate] [Bug 478230] Kate snippets: crash when editing a snippet repository

[Abd AlHaleem Bakkor Mustafa]

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

--- Comment #4 from Abd AlHaleem Bakkor Mustafa  ---
Created attachment 171482
  --> https://bugs.kde.org/attachment.cgi?id=171482&action=edit
New crash information added by DrKonqi

kate (23.08.5) using Qt 5.15.13

I had another Kate window open, then I tried to add a snippet into a snippet
folder that I made.

Although I've added snippets so mant times, I Didn't experience this before,
this time the difference is that I had another Kate window  opened.

-- Backtrace (Reduced):
#4  0x7f346ea4f422 in EditSnippet::EditSnippet(SnippetRepository*,
Snippet*, QWidget*) () from
/usr/lib64/qt5/plugins/ktexteditor/katesnippetsplugin.so
#5  0x7f346ea43a1e in SnippetView::slotAddSnippet() () from
/usr/lib64/qt5/plugins/ktexteditor/katesnippetsplugin.so
#6  0x7f34908eac81 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f34915a7d44 in QAction::triggered(bool) () from
/lib64/libQt5Widgets.so.5
#8  0x7f34915aab9b in QAction::activate(QAction::ActionEvent) () from
/lib64/libQt5Widgets.so.5

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

[plasmashell] [Bug 356317] New: Only a black screen after login on Fedora Rawhide with Plasma 5.4.95

[Mustafa Muhammad via KDE Bugzilla]

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

Bug ID: 356317
   Summary: Only a black screen after login on Fedora Rawhide with
Plasma 5.4.95
   Product: plasmashell
   Version: 5.4.95
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mustafa10...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

After updating to 5.4.95, after login there is no panel and no desktop, only
black space, I can still run applications using krunner.

Reproducible: Always

Steps to Reproduce:
1. Use an up to date Fedora Rawhide
2. Login to Plasma
3.

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

[plasmashell] [Bug 356317] Only a black screen after login on Fedora Rawhide with Plasma 5.4.95

[Mustafa Muhammad via KDE Bugzilla]

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

--- Comment #1 from Mustafa Muhammad  ---
Tested on bare metal (Intel GPU), and KVM virtual machine

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

[plasmashell] [Bug 356318] New: I can run wayland plasma session from terminal, not from sddm

[Mustafa Muhammad via KDE Bugzilla]

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

Bug ID: 356318
   Summary: I can run wayland plasma session from terminal, not
from sddm
   Product: plasmashell
   Version: 5.4.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mustafa10...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Using openSUSE Tumbleweed with latest Plasma from openSUSE KDE repos (following
git), I can start (and use) wayland session from terminal, but not from sddm.
If I try to log into Plasma on wayland, sddm looks freezed and I only have a
mouse curser moving.

Reproducible: Always

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

[plasmashell] [Bug 356317] Only a black screen after login on Fedora Rawhide with Plasma 5.4.95

[Mustafa Muhammad via KDE Bugzilla]

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

--- Comment #2 from Mustafa Muhammad  ---
Now I tested on F23 with 5.4.95 copr and it works fine, probably Rawhide
problem, not Plasma.

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