[plasmashell] [Bug 469810] When using non-password auth method, always show the UI in the lock screen without having to move the mouse first

2023-05-23 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=469810

--- Comment #2 from Ray Leon  ---
It seems like unlimited timeouts / timeouts greater than 99 seconds are
currently broken in pam_fprintd
(https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/147), so this might
not be fixable at the moment.

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

2023-05-21 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=468295

--- Comment #4 from Ray Leon  ---
(In reply to Ray Leon from comment #3)
> Clicking anywhere on the "Night color temperature" slider in System Settings
> (and then closing without saving) also seems to reset it.

Should've read more than the last comment. Sorry for the duplicate lol

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

2023-05-21 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=468295

--- Comment #3 from Ray Leon  ---
Clicking anywhere on the "Night color temperature" slider in System Settings
(and then closing without saving) also seems to reset it.

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

2023-05-21 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=468295

Ray Leon  changed:

   What|Removed |Added

 CC||maxwellleon55...@gmail.com

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

[kscreenlocker] [Bug 469810] New: Allow unlocking without pressing Enter or moving the mouse (for passwordless authentication)

2023-05-15 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=469810

Bug ID: 469810
   Summary: Allow unlocking without pressing Enter or moving the
mouse (for passwordless authentication)
Classification: Plasma
   Product: kscreenlocker
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

SUMMARY
I've recently set up fingerprint authentication with the KDE lock screen, but I
still need to get to the password entry screen by moving the mouse before
fingerprint authentication starts working. It'd be nice if I could just press
on the fingerprint reader in order to unlock the screen.

STEPS TO REPRODUCE
1. Set up fprintd and add 'auth sufficient pam_fprintd.so' to /etc/pam.d/kde
2. Lock the screen
3. Try to use the fingerprint reader without using the mouse

OBSERVED RESULT
Screen should unlock if fingerprint matches

EXPECTED RESULT
I have to disturb the screen somehow before I can unlock it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (rolling)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Here's my `/etc/pam.d/kde`:
```
#%PAM-1.0

authsufficient  pam_fprintd.so
authinclude system-login

account include system-login

passwordinclude system-login

session include system-login
```

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

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

2022-09-29 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449717

--- Comment #5 from Ray Leon  ---
(In reply to andreas.naumann from comment #3)
> In you videos, you show two pages side by side. Does it help, if you disable
> the "continous view" and show only one page? 
> In that configuration, okular stays at the page and zooms only.
> 
> If I enable the view mode "overview", I get your behavior.  In that
> configuration, I would rather ask, what zoom in means to the developer.  
> Looks to me, like okular increases the view starting from the upper left
> corner. 
> 
> It would feel more natural, if okular zooms into the area next to the finger
> position. Do we know the mouse position, when zooming?

Sorry for the late response. Disabling continuous view doesn't solve the
problem, although I guess it makes it easier to manage since the view's only
moving around on one page if that makes sense.
I also think you're right about the 'increasing view from the upper left
corner' part.

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

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

2022-03-20 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449717

--- Comment #2 from Ray Leon  ---
This appears to only happen in browse mode (not when text selection or
highlight are selected)

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-03-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #7 from Ray Leon  ---
make code blocks?

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-03-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #6 from Ray Leon  ---
Thanks, I think that fixed it!
Changing "ConversationAddress sender = message.addresses().first();" in
conversationmodel.cpp to 
`
>ConversationAddress sender;
>if (!message.addresses().isEmpty()) {
>sender = message.addresses().first();
>}
`
seems to prevent the crashing.
I don't really know how to commit the changes though, would you mind doing
that?
P.S. how do you

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-02-16 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #3 from Ray Leon  ---
(In reply to Nathan from comment #2)
> I have this issue all the time, and right now I need it more than ever as I
> dropped my phone last weekend which smashed the display. Now KDE Connect is
> the only way I can access the data on my old phone but because of this major
> bug I am unable to access the sms conversations. I have noticed that this
> issue seems to 'build up'. For example if I open a small length
> conversation, they will display fine but will segfault opening a second. If
> I open a large one it will immediately segfault

This mirrors what I've been experiencing

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-02-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #1 from Ray Leon  ---
Actual backtrace: 
Thread 1 "kdeconnect-sms" received signal SIGSEGV, Segmentation fault.
ConversationModel::createRowFromMessage(ConversationMessage const&, int) [clone
.constprop.0] (this=this@entry=0x7fffe0003f20, message=..., pos=0) at
/usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:145
145ConversationAddress sender = message.addresses().first();
(gdb) backtrace
#0  ConversationModel::createRowFromMessage(ConversationMessage const&, int)
[clone .constprop.0] (
this=this@entry=0x7fffe0003f20, message=..., pos=0)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:145
#1  0x555699f5 in ConversationModel::handleConversationUpdate (msg=...,
this=0x7fffe0003f20)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:189
#2  ConversationModel::qt_static_metacall (_o=0x7fffe0003f20, _c=, _id=, 
_a=0x7fffdaf0) at
/usr/src/debug/build/smsapp/kdeconnect-sms_autogen/EWIEGA46WW/moc_conversationmodel.cpp:161
#3  0x76484ddf in ?? () from /usr/lib/libQt5Core.so.5
#4  0x77f6e481 in
OrgKdeKdeconnectDeviceConversationsInterface::conversationUpdated (_t1=..., 
this=) at
/usr/src/debug/build/interfaces/conversationsinterface.moc:265
#5  OrgKdeKdeconnectDeviceConversationsInterface::qt_static_metacall
(_o=0x567a7510, _c=, 
_id=, _a=0x7fffdc40) at
/usr/src/debug/build/interfaces/conversationsinterface.moc:138
#6  0x77f5b873 in
OrgKdeKdeconnectDeviceConversationsInterface::qt_metacall (_a=0x7fffdc40,
_id=4, 
_c=QMetaObject::InvokeMetaMethod, this=0x567a7510)
at /usr/src/debug/build/interfaces/conversationsinterface.moc:223
#7  DeviceConversationsDbusInterface::qt_metacall (this=0x567a7510,
_c=QMetaObject::InvokeMetaMethod, 
_id=, _a=0x7fffdc40)
at
/usr/src/debug/build/interfaces/kdeconnectinterfaces_autogen/EWIEGA46WW/moc_dbusinterfaces.cpp:958
#8  0x7746afae in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x76477e76 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x76ec61a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#11 0x7645416a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#12 0x76454c69 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /usr/lib/libQt5Core.so.5
#13 0x7649b548 in ?? () from /usr/lib/libQt5Core.so.5
#14 0x74d64f13 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#15 0x74dbb0d9 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x74d62485 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#17 0x7649f44a in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#18 0x7644c44b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#19 0x76457b97 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#20 0x555603ef in main (argc=, argv=0x7fffe218)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/main.cpp:87

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

[kdeconnect] [Bug 449719] New: KDE Connect crashes when opening a message

2022-02-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449719

Bug ID: 449719
   Summary: KDE Connect crashes when opening a message
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

Created attachment 146359
  --> https://bugs.kde.org/attachment.cgi?id=146359=edit
Video of the aforementioned crash.

SUMMARY
When opening a conversation in the KDE Connect messages app, the app segfaults.


STEPS TO REPRODUCE
1. Hook up KDE Connect to your Android phone (I have a Samsung Galaxy S21
running Android 12)
2. Open the KDE Connect SMS app and click on a conversation

OBSERVED RESULT

qrc:/qml/ChatMessage.qml:109: TypeError: Cannot read property 'length' of
undefined
qrc:/qml/SendingArea.qml:69:17: QML TextArea: Possible anchor loop detected on
fill.

Thread 1 "kdeconnect-sms" received signal SIGSEGV, Segmentation fault.


EXPECTED RESULT
Conversation opens.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64, with all packages up to date
(available in About System)
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Backtrace (and additional stuff):
> gdb kdeconnect-sms
> 
GNU gdb (GDB) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdeconnect-sms...
Reading symbols from /usr/lib/debug/usr/bin/kdeconnect-sms.debug...
(gdb) run
Starting program: /usr/bin/kdeconnect-sms 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x70af2640 (LWP 802069)]
[New Thread 0x702f1640 (LWP 802070)]
[New Thread 0x7fffefaf0640 (LWP 802071)]
[New Thread 0x7fffee11d640 (LWP 802072)]
[New Thread 0x7fffde1f1640 (LWP 802073)]
[New Thread 0x7fffdd9f0640 (LWP 802074)]
[New Thread 0x7fffdd1ef640 (LWP 802075)]
[New Thread 0x7fffdc9ee640 (LWP 802076)]
[New Thread 0x7fffd17d1640 (LWP 802077)]
[New Thread 0x7fffd0fd0640 (LWP 802078)]
[New Thread 0x7fffbbfff640 (LWP 802079)]
qrc:/qml/ConversationList.qml:51: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:267: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:267: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:51: TypeError: Cannot read property 'text' of
null
no addresses! "A"
no addresses! "Should I bring anything?"
no addresses! ""
[New Thread 0x7fffbb7fe640 (LWP 802081)]
[New Thread 0x7fffbaffd640 (LWP 802082)]
[New Thread 0x7fffba5fc640 (LWP 802083)]
file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/InlineMessage.qml:261:9:
QML ActionToolBar: Binding loop detected for property "atBottom"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: 

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

2022-02-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449717

Ray Leon  changed:

   What|Removed |Added

 Attachment #146357|0   |1
is obsolete||

--- Comment #1 from Ray Leon  ---
Created attachment 146358
  --> https://bugs.kde.org/attachment.cgi?id=146358=edit
Video transcoded to .webm. Apologies, I skimmed the bug reporting guidelines a
bit too fast.

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

[okular] [Bug 449717] New: When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

2022-02-06 Thread Ray Leon
https://bugs.kde.org/show_bug.cgi?id=449717

Bug ID: 449717
   Summary: When zooming with 2 fingers on a touchscreen, Okular
also scrolls through the document, causing me to lose
my place.
   Product: okular
   Version: 21.12.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

Created attachment 146357
  --> https://bugs.kde.org/attachment.cgi?id=146357=edit
Video of me zooming in and out on a digital copy of a textbook

SUMMARY
When zooming on a multi-page document with touchscreen gestures, Okular also
scrolls through the document rather than staying in place.


STEPS TO REPRODUCE
1. Use a device with a Wacom touchscreen (I have a Lenovo Yoga c940)
2. Open a document with multiple pages in Okular.
3. Try to zoom using two fingers on the touchscreen.

OBSERVED RESULT
Other pages on the document zoom by. Zooming out increases the page number,
while zooming in increases.

EXPECTED RESULT
The document stays on the same page, as it does when zooming with ctrl + / ctrl
-

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64, with all packages up-to-date
(available in About System)
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION

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