[plasmashell] [Bug 479682] New: Mouse cursor does not show.

2024-01-11 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=479682

Bug ID: 479682
   Summary: Mouse cursor does not show.
Classification: Plasma
   Product: plasmashell
   Version: 5.92.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kanwar.pl...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
After upgrade to 5.92.0, the mouse cursor shows neither on the laptop screen
nor the external monitor.
I have tried changing the cursor theme too but did not help.
The session is plasma/wayland.

STEPS TO REPRODUCE
1. Install KDE Plasma 5.92.0
2. After login from sddm, there is no mouse cursor
3. Widgets can still be clicked if you "know" where the cursor is

OBSERVED RESULT
Mouse does not show although widgets/buttons can be clicked if you can tell
that the mouse is over them.

EXPECTED RESULT
Mouse cursor shows as normal

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.5.11-1 (64-bit), KDE Plasma 5.92.0 (Plasma 6 RC1)
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
None

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

[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used

2022-10-28 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=438401

Kanwar Plaha  changed:

   What|Removed |Added

 CC||kanwar.pl...@gmail.com

--- Comment #12 from Kanwar Plaha  ---
Can confirm this is still manifesting on OpenSUSE Tumbleweed with KDE Plasma
5.26.1 / Framework 5.99.0 and Qt 5.15.6.

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

[kalendar] [Bug 455902] New: Kalendar event reminders crash on startup (every time)

2022-06-24 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=455902

Bug ID: 455902
   Summary: Kalendar event reminders crash on startup (every time)
   Product: kalendar
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: kanwar.pl...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendarac (5.20.2)

Qt Version: 5.15.3
Frameworks Version: 5.95.0
Operating System: Linux 5.18.5-200.fc36.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.25.0 [KCrashBackend]

-- Information about the crash:
Kalendar 22.04.2-1 on Fedora 36 crashes and it crashes on startup when
attempting to show event reminders.

The crash can be reproduced every time.

-- Backtrace:
Application: Reminders (kalendarac), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7828b239a7 in QHashData::nextNode(QHashData::Node*) () from
/lib64/libQt5Core.so.5
#5  0x561b8edad64a in KalendarAlarmClient::checkAlarms() ()
#6  0x7f7828cdac36 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f78299a78f6 in Akonadi::EntityTreeModel::collectionPopulated(long
long) () from /lib64/libKF5AkonadiCore.so.5
#8  0x7f78299b2d52 in
Akonadi::EntityTreeModelPrivate::itemFetchJobDone(long long, KJob*) () from
/lib64/libKF5AkonadiCore.so.5
#9  0x7f7828cdac36 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f78297b5de9 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#11 0x7f78297ba1fb in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#12 0x7f7828cd1694 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f7828ca7658 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#14 0x7f7828caa9b4 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x7f7828cf8807 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#16 0x7f7826698faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#17 0x7f78266ee2c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#18 0x7f7826696940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x7f7828cf82fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#20 0x7f7828ca60ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#21 0x7f7828cae162 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#22 0x561b8eda8efd in main ()
[Inferior 1 (process 3928) detached]

The reporter indicates this bug may be a duplicate of or related to bug 447836,
bug 450377, bug 452848, bug 455687, bug 454678, bug 453395.

Reported using DrKonqi

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

[kwin] [Bug 449280] App main window requires two clicks on the close button if a child window was opened and closed from it

2022-01-27 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=449280

Kanwar Plaha  changed:

   What|Removed |Added

 CC||kanwar.pl...@gmail.com

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

[kwin] [Bug 449280] New: App main window requires two clicks on the close button if a child window was opened and closed from it

2022-01-27 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=449280

Bug ID: 449280
   Summary: App main window requires two clicks on the close
button if a child window was opened and closed from it
   Product: kwin
   Version: 5.23.90
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: aurorae
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kanwar.pl...@gmail.com
  Target Milestone: ---

SUMMARY
With the aurorae decoration engine, close button requires two clicks to close
the window.

STEPS TO REPRODUCE
1. Open any window/app. [System Settings --> Appearance --> Global Themes]
2. Click on something that will open a child/modal window. [Get New Global
Themes...]
3. Close the child/modal window. Close "Get New Global Themes" window.
4. The System Settings window now requires two clicks to close.

OBSERVED RESULT
Once a child window is closed, the main window requires two clicks on the close
button to close.

EXPECTED RESULT
Main window closes with a single click on the close button

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon (focal) / 5.23.90
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
This behaviour is noticed in the "aurorae" decorations engine. Default Breeze
decoration works fine.

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

[Falkon] [Bug 422701] New: Falkon browser does not support webauthn (public key credentials)

2020-06-09 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=422701

Bug ID: 422701
   Summary: Falkon browser does not support webauthn (public key
credentials)
   Product: Falkon
   Version: 3.1.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: kanwar.pl...@gmail.com
  Target Milestone: ---

SUMMARY

I have noticed the user agent in Falkon browser does not allow public key
credentials. In fact, it was working but shows the error "Uncaught (in promise)
DOMException: The user agent does not support public key credentials." when
accessing a corporate 2FA login (webauthn)?

This happens only on KaOS Linux. It seems to work on Kubuntu and Manjaro (with
KDE/Plasma).

STEPS TO REPRODUCE
1. Run Falkon on KaOS
2. Access a site that requires webauthn
3. Page does not load
4. When viewed in developer tools, the error "Uncaught (in promise)
DOMException: The user agent does not support public key credentials." is
reported.

OBSERVED RESULT
"Uncaught (in promise) DOMException: The user agent does not support public key
credentials."

EXPECTED RESULT
Login page loads

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KaOS Linux / KDE 5.70.0 / Plasma 5.19.0
(available in About System)
KDE Plasma Version: Plasma 5.19.0
KDE Frameworks Version: KDE 5.70.0
Qt Version: 5.15.0-1

ADDITIONAL INFORMATION
Works under KDE Neon / Kubuntu / Manjaro

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

[plasmashell] [Bug 421769] New: Plasma crashes when connecting to wifi network upon first boot

2020-05-19 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=421769

Bug ID: 421769
   Summary: Plasma crashes when connecting to wifi network upon
first boot
   Product: plasmashell
   Version: master
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kanwar.pl...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.80)

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.3.0-51-generic x86_64
Windowing system: X11
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
Booted live-cd for the first time
Booted KDE Neon for the first time after installing to hard disk

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x7f30cdb49cc1 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so
#5  0x7f30f71596d7 in QtPrivate::QSlotObjectBase::call (a=0x7f30b3ffeb90,
r=0x555d1ae69a80, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#6  doActivate (sender=0x555d19bc3960, signal_index=28,
argv=0x7f30b3ffeb90) at kernel/qobject.cpp:3870
#7  0x7f30f7153f92 in QMetaObject::activate
(sender=sender@entry=0x555d19bc3960, m=m@entry=0x7f30fb53e9a0
,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at
kernel/qobject.cpp:3930
#8  0x7f30fb084a13 in QQuickWindow::beforeRendering
(this=this@entry=0x555d19bc3960) at .moc/moc_qquickwindow.cpp:558
#9  0x7f30fb08a753 in QQuickWindowPrivate::renderSceneGraph
(this=this@entry=0x555d19af82d0, size=..., surfaceSize=...) at
items/qquickwindow.cpp:500
#10 0x7f30fb02ff58 in QSGRenderThread::syncAndRender
(this=this@entry=0x7f30e000f7d0, grabImage=grabImage@entry=0x0) at
scenegraph/qsgthreadedrenderloop.cpp:810
#11 0x7f30fb03464f in QSGRenderThread::run (this=0x7f30e000f7d0) at
scenegraph/qsgthreadedrenderloop.cpp:980
#12 0x7f30f6f2ec2c in QThreadPrivate::start (arg=0x7f30e000f7d0) at
thread/qthread_unix.cpp:342
#13 0x7f30f3a7d6db in start_thread (arg=0x7f30b3fff700) at
pthread_create.c:463
#14 0x7f30f682388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x555d1b22da10,
cond=0x555d1b22da38) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x555d1b22da38, mutex=0x555d1b22da10) at
pthread_cond_wait.c:655
#3  0x7f30f6f351db in QWaitConditionPrivate::wait (deadline=...,
this=0x555d1b22da10) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x7f30e0008cb0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f30f6f35359 in QWaitCondition::wait (this=this@entry=0x7f30e0008cb8,
mutex=mutex@entry=0x7f30e0008cb0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#6  0x7f30fb034233 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x7f30e0008ca8) at scenegraph/qsgthreadedrenderloop.cpp:255
#7  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x7f30e0008c10) at scenegraph/qsgthreadedrenderloop.cpp:905
#8  0x7f30fb034691 in QSGRenderThread::run (this=0x7f30e0008c10) at
scenegraph/qsgthreadedrenderloop.cpp:1000
#9  0x7f30f6f2ec2c in QThreadPrivate::start (arg=0x7f30e0008c10) at
thread/qthread_unix.cpp:342
#10 0x7f30f3a7d6db in start_thread (arg=0x7f309bae4700) at
pthread_create.c:463
#11 0x7f30f682388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

#1  0x7f30f03635c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f30f03636dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f30f717d7cb in QEventDispatcherGlib::processEvents
(this=0x7f309c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f30f711cd2a in QEventLoop::exec (this=this@entry=0x7f30a25cfd60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7f30f6f2d757 in QThread::exec (this=) at
thread/qthread.cpp:536
#6  0x7f30a4f2f467 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7f30f6f2ec2c in QThreadPrivate::start (arg=0x555d19b42000) at
thread/qthread_unix.cpp:342
#8  0x7f30f3a7d6db in start_thread (arg=0x7f30a25d0700) at
pthread_create.c:463
#9  0x7f30f682388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

#1  0x7f30f03635c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f30f03636dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f30f717d7cb in QEventDispatcherGlib::processEvents
(this=0x7f30b8000b20, flags=...) at 

[latte-dock] [Bug 404268] New: Cannot launch latte-dock configuration screen with mouse right-click

2019-02-12 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=404268

Bug ID: 404268
   Summary: Cannot launch latte-dock configuration screen with
mouse right-click
   Product: latte-dock
   Version: 0.8.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: kanwar.pl...@gmail.com
  Target Milestone: ---

The configuration screen for latte cannot be launched because right-click does
not do anything on the dock.


STEPS TO REPRODUCE
1. Install latte-dock
2. Run latte-dock
3. Right-click on latte-dock to open configuration screen

OBSERVED RESULT
No response occurs when right-clicked

EXPECTED RESULT
Configuration window for latte-dock opens


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Arch (4.19.12-2-MANJARO) / Plasma 5.14.5-2
(available in About System)
KDE Plasma Version: 5.14.5-2
KDE Frameworks Version: 18.12.2-1
Qt Version: 5.12.1-1

ADDITIONAL INFORMATION
n/a

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

[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting

2018-02-23 Thread Kanwar Plaha
https://bugs.kde.org/show_bug.cgi?id=385880

Kanwar Plaha <kanwar.pl...@gmail.com> changed:

   What|Removed |Added

 CC||kanwar.pl...@gmail.com

--- Comment #6 from Kanwar Plaha <kanwar.pl...@gmail.com> ---
Same here. I tried setting Style=In application in kdeglobals (both
under/usr/share and under $HOME/.config but didn't work. 

Also the configuration drop down is missing from systemsettings.

So even though rest of KDE is working smooth as under Wayland, it is unusable
due to the missing menu bar.

I've seen the same behaviour across Ubuntu, opensuse, arch and now nitrux.

Cheers.

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

[plasmashell] [Bug 365838] New: Weather widget loses city info with each reboot

2016-07-18 Thread Kanwar Plaha via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365838

Bug ID: 365838
   Summary: Weather widget loses city info with each reboot
   Product: plasmashell
   Version: 5.7.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kanwar.pl...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

The default weather widget has to be reconfigured with my city name every time
the computer is restarted. 

Reproducible: Always

Steps to Reproduce:
1. Drag weather widget to desktop or a panel
2. Configure widget to show weather for a city
3. Reboot or login/logout
4. City name/settings in the weather widget are lost


Expected Results:  
The widget/plasmoid should retain city settings once configured.

I haven't marked it Minor because it is something a weather plasmoid is meant
to do. That is its only function. So, I've marked it as a normal bug.

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