[plasmashell] [Bug 479971] New: Plasma Crash after closing notification spam

2024-01-17 Thread Phani Pavan K
https://bugs.kde.org/show_bug.cgi?id=479971

Bug ID: 479971
   Summary: Plasma Crash after closing notification spam
Classification: Plasma
   Product: plasmashell
   Version: 5.27.10
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kphanipa...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.10)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.6.7-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
I am using OpenSUSE TW. I didn't update the system for 3 weeks now. The update
notifier started checking for updates every hour but fails with the message
"authentication failed" (not exact). I get that notification every hour and
when I closed a bunch of them lined up from last night, plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 3987 (plasmashell)
   UID: 1000 (toast)
   GID: 1000 (toast)
Signal: 11 (SEGV)
 Timestamp: Thu 2024-01-18 06:28:18 IST (43s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (toast)
   Boot ID: b450a912bb3549728cec0377b24eff78
Machine ID: 2474af29344d45209d3089ff3ab1b3ff
  Hostname: toast
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.b450a912bb3549728cec0377b24eff78.3987.170553949800.zst
(present)
  Size on Disk: 37.3M
   Message: Process 3987 (plasmashell) of user 1000 dumped core.

Stack trace of thread 3999:
#0  0x7efeb2a91dec __pthread_kill_implementation (libc.so.6
+ 0x91dec)
#1  0x7efeb2a3f0c6 raise (libc.so.6 + 0x3f0c6)
#2  0x7efeb57d8d9a _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x7d9a)
#3  0x7efeb2a3f190 __restore_rt (libc.so.6 + 0x3f190)
#4  0x7efeb2a91dec __pthread_kill_implementation (libc.so.6
+ 0x91dec)
#5  0x7efeb2a3f0c6 raise (libc.so.6 + 0x3f0c6)
#6  0x7efeb2a3f190 __restore_rt (libc.so.6 + 0x3f190)
#7  0x7efeb2b09d7f __poll (libc.so.6 + 0x109d7f)
#8  0x7efeb20c5aff n/a (libglib-2.0.so.0 + 0x5daff)
#9  0x7efeb20c620c g_main_context_iteration
(libglib-2.0.so.0 + 0x5e20c)
#10 0x7efeb35460ee
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x3460ee)
#11 0x7efeb34ebc2b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2ebc2b)
#12 0x7efeb3302f6e _ZN7QThread4execEv (libQt5Core.so.5 +
0x102f6e)
#13 0x7efeb4924517 n/a (libQt5DBus.so.5 + 0x1a517)
#14 0x7efeb330419d n/a (libQt5Core.so.5 + 0x10419d)
#15 0x7efeb2a8ff44 start_thread (libc.so.6 + 0x8ff44)
#16 0x7efeb2b184cc __clone3 (libc.so.6 + 0x1184cc)

Stack trace of thread 3987:
#0  0x7efeb2b09d7f __poll (libc.so.6 + 0x109d7f)
#1  0x7efeb57d8198 n/a (libKF5Crash.so.5 + 0x7198)
#2  0x7efeb57d8d3d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x7d3d)
#3  0x7efeb2a3f190 __restore_rt (libc.so.6 + 0x3f190)
#4  0x7efeb4c943ed _ZN5QtQml18qmlExecuteDeferredEP7QObject
(libQt5Qml.so.5 + 0x2943ed)
#5  0x7efeb5178e99
_ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject
(libQt5Quick.so.5 + 0x178e99)
#6  0x7efeb516e3a7
_ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject
(libQt5Quick.so.5 + 0x16e3a7)
#7  0x7efeb3518e5b _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x318e5b)
#8  0x7efeb43a519e
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x1a519e)
#9  0x7efeb34ed198
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2ed198)
#10 0x7efeb35454c9 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5 + 0x3454c9)
#11 0x7efeb3545dac n/a (libQt5Core.so.5 + 0x345dac)
#12 0x7efeb20c3f30 n/a 

[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out

2023-08-01 Thread Phani Pavan K
https://bugs.kde.org/show_bug.cgi?id=463247

Phani Pavan K  changed:

   What|Removed |Added

 CC||kphanipa...@gmail.com

--- Comment #9 from Phani Pavan K  ---
My Proposal:

P1. The "+New" button appears and is enabled if (valid number is present in the
search bar) AND (connected devices with sms capab is more than ZERO): Tooltip
says what it says right now
P2. The "+New" button appears but is greyed if (valid number is present in
search bar) AND (connected devices equal to ZERO): Tooltip says "No Devices
Connected"
P3. The "+New" button doesn't appear otherwise, i.e. if (number in search bar
is not valid).

Additional Enhancements:

A1. "+New" changes to "Open" if the number is already present in sms list

Questions: 
Q1. Is "+" necessary in "+New"?

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

[kdeconnect] [Bug 446337] KDE Connect KCM launched via system tray applet should open inside System Settings

2023-07-29 Thread Phani Pavan K
https://bugs.kde.org/show_bug.cgi?id=446337

Phani Pavan K  changed:

   What|Removed |Added

 CC||kphanipa...@gmail.com
   Assignee|albertv...@gmail.com|kphanipa...@gmail.com

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