[kwin] [Bug 376041] New: Kde Crash due to change desktop effects

2017-02-05 Thread Stoyan
https://bugs.kde.org/show_bug.cgi?id=376041

Bug ID: 376041
   Summary: Kde Crash due to change desktop effects
   Product: kwin
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: stoqnv...@gmail.com
  Target Milestone: ---

Application: kwin (4.11.22)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.4.14 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
Trying to change my Desktop animation settings.
Re-enabling OpenGl is crashing the Kwin app.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6606a2a7c0 (LWP 1436))]

Thread 3 (Thread 0x7f65e5217700 (LWP 23019)):
#0  0x7f6600977718 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6600c128b2 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/qt/lib/libQtCore.so.4
#2  0x7f6600c05e7f in  () at /usr/lib64/qt/lib/libQtCore.so.4
#3  0x7f6600c123bc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#4  0x7f6600971684 in start_thread () at /lib64/libpthread.so.0
#5  0x7f65fea4cefd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f65e6998700 (LWP 1443)):
#0  0x7f660097736f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f66059ee5aa in  () at /usr/lib64/qt/lib/libQtScript.so.4
#2  0x7f66059ee5d9 in  () at /usr/lib64/qt/lib/libQtScript.so.4
#3  0x7f6600971684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f65fea4cefd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6606a2a7c0 (LWP 1436)):
[KCrash Handler]
#6  0x7f65fe97b3f8 in raise () at /lib64/libc.so.6
#7  0x7f65fe97cffa in abort () at /lib64/libc.so.6
#8  0x7f65fe973c17 in __assert_fail_base () at /lib64/libc.so.6
#9  0x7f65fe973cc2 in  () at /lib64/libc.so.6
#10 0x7f6604be9d39 in  () at /usr/lib64/libX11.so.6
#11 0x7f6604be9dce in  () at /usr/lib64/libX11.so.6
#12 0x7f6604bea0ad in _XEventsQueued () at /usr/lib64/libX11.so.6
#13 0x7f6604becd05 in _XGetRequest () at /usr/lib64/libX11.so.6
#14 0x7f65ff7e9bd7 in  () at /usr/lib64/libGL.so.1
#15 0x7f65ff7e9f27 in  () at /usr/lib64/libGL.so.1
#16 0x7f655f251403 in  () at /usr/lib64/xorg/modules/dri/i965_dri.so
#17 0x7f655f2518c1 in  () at /usr/lib64/xorg/modules/dri/i965_dri.so
#18 0x7f655f2519ab in  () at /usr/lib64/xorg/modules/dri/i965_dri.so
#19 0x7f655f202746 in  () at /usr/lib64/xorg/modules/dri/i965_dri.so
#20 0x7f65ff7eb8ab in  () at /usr/lib64/libGL.so.1
#21 0x7f65ff7c9007 in glXMakeCurrentReadSGI () at /usr/lib64/libGL.so.1
#22 0x7f66065dbf5f in  () at /usr/lib64/libkdeinit4_kwin.so
#23 0x7f66065dc490 in  () at /usr/lib64/libkdeinit4_kwin.so
#24 0x7f66065d6ac4 in  () at /usr/lib64/libkdeinit4_kwin.so
#25 0x7f66065b9a42 in  () at /usr/lib64/libkdeinit4_kwin.so
#26 0x7f660653b825 in  () at /usr/lib64/libkdeinit4_kwin.so
#27 0x7f6600d2ae30 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#28 0x7f6600c02777 in QFutureWatcherBase::event(QEvent*) () at
/usr/lib64/qt/lib/libQtCore.so.4
#29 0x7f65ffe6d48c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#30 0x7f65ffe73f5c in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#31 0x7f6601a3b8ea in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#32 0x7f6600d17c0d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#33 0x7f6600d1ae6e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/qt/lib/libQtCore.so.4
#34 0x7f65fff11129 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#35 0x7f6600d165d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#36 0x7f6600d168e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#37 0x7f6600d1bec9 in QCoreApplication::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#38 0x7f660656c826 in kdemain () at /usr/lib64/libkdeinit4_kwin.so
#39 0x7f65fe9667d0 in __libc_start_main () at /lib64/libc.so.6
#40 0x00400a09 in _start ()

Reported using DrKonqi

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

[kmymoney] [Bug 398580] New: Why notifications are not shown on fullscreen?

2018-09-13 Thread stoyan
https://bugs.kde.org/show_bug.cgi?id=398580

Bug ID: 398580
   Summary: Why notifications are not shown on fullscreen?
   Product: kmymoney
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: bugtracker
  Assignee: kmymoney-de...@kde.org
  Reporter: stoyan.min...@gmail.com
  Target Milestone: ---

Sometimes i play game or watch YouTube video in fullscreen mode on my laptop
which is not connected to AC power, and i can`t see "low battery"
notifications. Laptop just turn off. If this isn`t bug, but a feature  then for
some use cases it`s very bad feature. Please change the notification system
behaivor in next releases of Plasma. Thank you!

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

[kmymoney] [Bug 398580] Why notifications are not shown on fullscreen?

2018-09-13 Thread stoyan
https://bugs.kde.org/show_bug.cgi?id=398580

stoyan  changed:

   What|Removed |Added

   Assignee|kmymoney-de...@kde.org  |kde-bugzi...@plasma.cx

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

[kdeconnect] [Bug 398931] New: Feature reuqest

2018-09-21 Thread stoyan
https://bugs.kde.org/show_bug.cgi?id=398931

Bug ID: 398931
   Summary: Feature reuqest
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: stoyan.min...@gmail.com
  Target Milestone: ---

Is this possible to use phone fingerprint as password verification backend on
desktop?

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

[kdeconnect] [Bug 492882] New: Notifications without a 'quick action' can't be cleared

2024-09-09 Thread Stoyan Georgiev
https://bugs.kde.org/show_bug.cgi?id=492882

Bug ID: 492882
   Summary: Notifications without a 'quick action' can't be
cleared
Classification: Applications
   Product: kdeconnect
   Version: 23.08.5
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: stoya...@yahoo.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

I’m successfully receiving notifications from my mobile phone on my desktop.

For a few of the applications (FairMail, Notion, Viber and a few more), when I
receive a notification and I clear it on my desktop, it gets cleared on the
mobile phone as well.

But for the majority of applications, the notification pops out, but even after
clearing from the PC - they remain on the mobile device.

I noticed that notifications that have a 'quick action' such as "reply", "mark
as read", "delete", etc. - there is no problem.

For all the notifications that have no 'quick action' - there is a problem. 

I tried some information gathering on my side via "dbus-monitor
interface=org.freedesktop.Notifications"

That's how a "good" notification looks like:

signal time=1725722554.180846 sender=:1.45 -> destination=(null destination)
serial=16839 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=ActionInvoked
   uint32 193
   string "1"
method call time=1725722554.569287 sender=:1.60 ->
destination=org.freedesktop.Notifications serial=892
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications;
member=CloseNotification
   uint32 193
signal time=1725722554.569969 sender=:1.45 -> destination=(null destination)
serial=16840 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 193
   uint32 3

And that's how a "bad" notification looks like:

signal time=1725722811.298946 sender=:1.45 -> destination=(null destination)
serial=16931 path=/org/freedesktop/Notifications;
interface=org.freedesktop.Notifications; member=NotificationClosed
   uint32 197
   uint32 2

STEPS TO REPRODUCE
1. Receive a notification on the Android device that offers no "Quick action"
2. Press "X" or "Clear all notifications" from the Notification Center on the
desktop.
3. The notification will clear on the desktop, but not on the Android device.

OBSERVED RESULT
The notifications clear from the desktop, but not from the mobile device.

EXPECTED RESULT
The notifications to clear on the mobile device as well.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux Mint 22 Cinnamon

KDE Connect: 23.08.5
Android device: Samsung S24 Ultra, Android 14, OneUI 6.1

ADDITIONAL INFORMATION

I also decided to test with KDE Plasma so I ran Kubuntu via live USB, paired
with my Android device and tried to reproduce the bug. On KDE Plasma everything
was working properly. So the problem persists on Linux Mint 22 Cinnamon, but
not on Kubuntu.

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

[kdeconnect] [Bug 492882] Notifications without a 'quick action' can't be cleared

2024-09-09 Thread Stoyan Georgiev
https://bugs.kde.org/show_bug.cgi?id=492882

Stoyan Georgiev  changed:

   What|Removed |Added

 CC||stoya...@yahoo.com

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

[kwin] [Bug 372576] Present Windows lags when closing window

2019-06-10 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=372576

Stoyan Stoyanov  changed:

   What|Removed |Added

 CC||eng.sps...@gmail.com

--- Comment #31 from Stoyan Stoyanov  ---
Can someone confirm if the fix mentioned in comment 27 will be included in
feature updates in KDE Neon?

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

[systemsettings] [Bug 408573] New: Thumbnails of splash screens are missing in "System Settings > Startup and shutdown > Boot Splash"

2019-06-11 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=408573

Bug ID: 408573
   Summary: Thumbnails of splash screens are missing in "System
Settings > Startup and shutdown > Boot Splash"
   Product: systemsettings
   Version: 5.16.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: eng.sps...@gmail.com
  Target Milestone: ---

Created attachment 120790
  --> https://bugs.kde.org/attachment.cgi?id=120790&action=edit
screenshot of the broken thumbnails

SUMMARY
Thumbnails of splash screens are missing in "System Settings > Startup and
shutdown > Boot Splash"

STEPS TO REPRODUCE
1. Open system settings
2. Navigate to "Startup and Shutdown > Boot Splash"


OBSERVED RESULT
Splash screen thumbnails are broken or with missing images. There is irrelevant
text floating around (see screenshot)

EXPECTED RESULT
Correct splash screen thumbnails and aligned text

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.16
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Hardware: Dell XPS13 9350

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

[kwin] [Bug 372576] Present Windows lags when closing window

2019-06-25 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=372576

--- Comment #37 from Stoyan Stoyanov  ---
I can confirm, bug is gon on my XPS 13 9350 with i5 :) Awesome!

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

[kwin] [Bug 372576] Present Windows lags when closing window

2019-06-25 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=372576

--- Comment #39 from Stoyan Stoyanov  ---
A(In reply to Pascal d'Hermilly from comment #38)
> Mostly gone. You can still trigger it by moving the mouse in and out over
> the close icon of the window.
> It almost feels like it's some bad connection between the animation of the
> close icon and the enlarge window under mouse animation.

Actually you are right! Sorry about my previous comment - the bug is still
existing on XPS 13 9350 although the bad animation on hover does feel different
:(

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

[Touchpad-KCM] [Bug 405399] New: Disable touchpad when typing not working for touchpad clicks

2019-03-12 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=405399

Bug ID: 405399
   Summary: Disable touchpad when typing not working for touchpad
clicks
   Product: Touchpad-KCM
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: rajeeshknamb...@gmail.com
  Reporter: eng.sps...@gmail.com
  Target Milestone: ---

Created attachment 118752
  --> https://bugs.kde.org/attachment.cgi?id=118752&action=edit
touchpad bug video

SUMMARY


STEPS TO REPRODUCE
1. Go to System Settings > Input Devices > Touchpad > Enable/Disable Touchpad
2. Select "Disable touchpad while typing" option
3. Deselect "Disable taps and scrolling only" option and apply the settings
4. Start typing anywhere (e.g in kwrite) and try to click(not tap) with the
touchpad

OBSERVED RESULT
touchpad clicks are enabled

EXPECTED RESULT
touchpad clicks should be disabled

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: KDE Neon 5.15
(available in About System)
KDE Plasma Version: 5.15.2
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
HARDWARE: Dell XPS13 9350

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

[plasmashell] [Bug 394190] New: System tray stops opening after using MinimizeAll while it is open

2018-05-12 Thread Stoyan Stoyanov
https://bugs.kde.org/show_bug.cgi?id=394190

Bug ID: 394190
   Summary: System tray stops opening after using MinimizeAll
while it is open
   Product: plasmashell
   Version: 5.12.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: eng.sps...@gmail.com
  Target Milestone: 1.0

Created attachment 112610
  --> https://bugs.kde.org/attachment.cgi?id=112610&action=edit
A short video showing the described bug

Software versions:
KDE Plasma version: 5.12.5.
KDE Frameworks version: 5.46.0
QT Version: 5.10.0
Kernel Version: 4.13.0-41

Hardware: Dell XPS 13 9350

Brief description:
If I use minimizeAll by a keyboard shortcut or hot corner while system tray is
open then system tray cannot open again afterwards.

Steps to reproduce:
1. Click an open system tray
2. Use hot corner or keyboard shortcut with minimizeAll functionality
3. Click on system tray
4. System tray doesn't open

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

[plasmashell] [Bug 353975] Black screen on second display.

2016-07-27 Thread Stoyan Tsalev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353975

Stoyan Tsalev  changed:

   What|Removed |Added

 CC||sto...@tzalev.com

--- Comment #41 from Stoyan Tsalev  ---
Exactly the same thing here, plus I'm using vertical screens. Fully updated
Fedora 24,  plasma 5.71. Workaround is indeed disabling then re-enabling the
second screen.

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