[KScreen] [Bug 433262] suspending by closing laptop lid on Wayland causes laptop screen to be disabled after waking up laptop.

2021-02-21 Thread Ryszard
https://bugs.kde.org/show_bug.cgi?id=433262

Ryszard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||jezierski.rysz...@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #1 from Ryszard  ---
Can confirm, this exact bug is also happening to me. Except, I couldn't manage
to re-enable laptop screen while logged to Wayland session, because kwin always
crashes and leaves black screen with only mouse cursor visible. To enable the
screen, it's necessary to log in to Xorg.

Using "systemctl suspend" or clicking the "sleep" button are the only
workarounds I've found so far.

SYSTEM INFORMATION:
Operating System: Arch Linux
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-arch2-1
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

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

[kontact] [Bug 378729] New: Kontakt crash after few seconds

2017-04-13 Thread Ryszard
https://bugs.kde.org/show_bug.cgi?id=378729

Bug ID: 378729
   Summary: Kontakt crash after few seconds
   Product: kontact
   Version: 5.4.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ri...@rikos.pl
  Target Milestone: ---

Application: kontact (5.4.3)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.10.8-200.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
I have updated Fedora Version from 23 to 24, and finally to 25.
I hat the similiar problem with Fedora 24 (After start), the Kontact have
Crashed,
Now the crash happend also but much Faster.
I was able to send mail but after few seconds Kontact Crashed again.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f90e3a8c640 (LWP 8546))]

Thread 29 (Thread 0x7f8fdca14700 (LWP 8620)):
#0  0x7ffcc3357b12 in clock_gettime ()
#1  0x7f90faad2726 in clock_gettime () at /lib64/libc.so.6
#2  0x7f90fb767b31 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f90fb8bcd99 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f90fb8bd195 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f90fb8be38c in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f90fb8be455 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f90ede1b69d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f90ede1c08b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f90ede1c27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f90fb8be6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f90fb86f68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f90fb6cc5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f90fb6d09ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7f90f28b76ca in start_thread () at /lib64/libpthread.so.0
#15 0x7f90faac3f7f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f8fde5b1700 (LWP 8619)):
#0  0x7f90f28bd460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f90f6e32c49 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f90f6e33289 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f90f6e33440 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f90f6e2ffdc in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f90f28b76ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f90faac3f7f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f8fdf84f700 (LWP 8607)):
#0  0x7f90faab3bed in read () at /lib64/libc.so.6
#1  0x7f90ede604d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f90ede1bc83 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f90ede1c104 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f90ede1c27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f90fb8be6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f90fb86f68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f90fb6cc5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f90fb6d09ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f90f28b76ca in start_thread () at /lib64/libpthread.so.0
#10 0x7f90faac3f7f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f8fe0050700 (LWP 8596)):
#0  0x7f90f28bd460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f90f6e32c49 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f90f6e33289 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f90f6e33440 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f90f6e2ffdc in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f90f28b76ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f90faac3f7f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f8fe6515700 (LWP 8581)):
#0  0x7f90faab3bed in read () at /lib64/libc.so.6
#1  0x7f90ede604d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0

[gwenview] [Bug 383205] New: Gwenview crashed on some files

2017-08-06 Thread Ryszard Klos
https://bugs.kde.org/show_bug.cgi?id=383205

Bug ID: 383205
   Summary: Gwenview crashed on some files
   Product: gwenview
   Version: 16.12.3
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: ry...@iname.com
  Target Milestone: ---

Application: gwenview (16.12.3)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.40-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
It looks like application is crashing on pictures with EXIF or other info added
- in my case by Pentax cameras. My old files made on Epson camera are opened
fine. Pictures are in jepg format.

The crash can be reproduced every time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa536557840 (LWP 19555))]

Thread 4 (Thread 0x7fa52a650700 (LWP 19562)):
#0  0x7fa53f8d8ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa544e47d46 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fa544e43764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7fa544e46ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7fa53f8d366d in start_thread () at /lib64/libpthread.so.0
#5  0x7fa54475fe4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fa52bfff700 (LWP 19559)):
#0  0x7fa54475400d in poll () at /lib64/libc.so.6
#1  0x7fa53f3b0c94 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fa53f3b0d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fa54505ce2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fa54500849a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fa544e423bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fa549775635 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fa544e46ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fa53f8d366d in start_thread () at /lib64/libpthread.so.0
#9  0x7fa54475fe4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fa53219c700 (LWP 19557)):
#0  0x7fa54475400d in poll () at /lib64/libc.so.6
#1  0x7fa53d10a902 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fa53d10c657 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fa534843be9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fa544e46ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fa53f8d366d in start_thread () at /lib64/libpthread.so.0
#6  0x7fa54475fe4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa536557840 (LWP 19555)):
[KCrash Handler]
#6  0x7fa544014eef in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const
() at /lib64/libexiv2.so.26
#7  0x7fa544059af1 in
Exiv2::Internal::PentaxMakerNote::printShutterCount(std::ostream&, Exiv2::Value
const&, Exiv2::ExifData const*) () at /lib64/libexiv2.so.26
#8  0x7fa548efc870 in void
Gwenview::ImageMetaInfoModelPrivate::fillExivGroup >(QModelIndex const&,
Gwenview::MetaInfoGroup*, Exiv2::ExifData const&) () at
/lib64/libgwenviewlib.so.5
#9  0x7fa548ef9933 in
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () at
/lib64/libgwenviewlib.so.5
#10 0x7fa548ebbe15 in
Gwenview::Document::setExiv2Image(std::auto_ptr) () at
/lib64/libgwenviewlib.so.5
#11 0x7fa548ebafd4 in
Gwenview::AbstractDocumentImpl::setDocumentExiv2Image(std::auto_ptr)
() at /lib64/libgwenviewlib.so.5
#12 0x7fa548ec82fa in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded()
() at /lib64/libgwenviewlib.so.5
#13 0x7fa545035859 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#14 0x7fa544e3ec21 in QFutureWatcherBase::event(QEvent*) () at
/lib64/libQt5Core.so.5
#15 0x7fa546300d0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#16 0x7fa546305e76 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#17 0x7fa54500a628 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#18 0x7fa54500c44b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#19 0x7fa54505c9f3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#20 0x7fa53f3b0ac7 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#21 0x7fa53f3b0cf8 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#22 0x7fa53f3b0d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#23 0x7fa54505ce06 in
QEventDispatcherGlib::p

[kde] [Bug 506506] New: The orca screen reader should read KRunner, search actionable item

2025-07-02 Thread Arkadiusz Ryszard Świętnicki
https://bugs.kde.org/show_bug.cgi?id=506506

Bug ID: 506506
   Summary: The orca screen reader should read KRunner, search
actionable item
Classification: I don't know
   Product: kde
  Version First unspecified
   Reported In:
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: nuno...@gmail.com
  Target Milestone: ---

Currently when using KRunner or the kDE's search facilities the Orca user is
not informed of the result which will be invoked by pressing the Enter key.
Given the example
1. Press META key
2. Type "Fire" to start matching Firefox
3. Press Enter

A sighted user knows right away what they are activating because the item is
highlighted.
As it currently stands a blind user needs to press the Down arrow once so that
Orca focuses the list of results, thus reading the focused item which adds
unnecessary friction for cannonicaly rapid task which is keyboard-based
workflow of KRunner and the like.

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

[plasmashell] [Bug 506505] New: The search widget traps the keyboard cursor

2025-07-02 Thread Arkadiusz Ryszard Świętnicki
https://bugs.kde.org/show_bug.cgi?id=506505

Bug ID: 506505
   Summary: The search widget traps the keyboard cursor
Classification: Plasma
   Product: plasmashell
  Version First 6.4.1
   Reported In:
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Search widget
  Assignee: plasma-b...@kde.org
  Reporter: nuno...@gmail.com
CC: alexander.loh...@gmx.de
  Target Milestone: 1.0

SUMMARY
Entering the Search widget with the TAB key results in keyboard cursor trapping

STEPS TO REPRODUCE
1. Add a "Search" widget to your desktop, together with another widget, such as
"Clipboard history".
2. Enter your desktop (Press META+D)
3. Use the TABV key to navigate the widgets.

OBSERVED RESULT
Entering the search widget field makes it impossible to exit it to get to
another widget - the Tab key does not work

EXPECTED RESULT
The tab key should get out of the widget's search field and navigate to other
elements on desktop

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.16.0-0.rc3.250627g67a993863163.35.fc43.aarch64 (64-bit)
Graphics Platform: Wayland
Processors: 8
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: Parallels International GmbH.
Product Name: Parallels ARM Virtual Machine
System Version: 0.1

ADDITIONAL INFORMATION
I am using the Orca screenreader

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

[kde] [Bug 506445] New: Orca Screenreader uses wrong keyboard bindings for structural navigation on websites

2025-07-01 Thread Arkadiusz Ryszard Świętnicki
https://bugs.kde.org/show_bug.cgi?id=506445

Bug ID: 506445
   Summary: Orca Screenreader uses wrong keyboard bindings for
structural navigation on websites
Classification: I don't know
   Product: kde
  Version First unspecified
   Reported In:
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: nuno...@gmail.com
  Target Milestone: ---

SUMMARY
The Orca Screenreader incorrectly binds modifier keys to structural navigation
keys on websites

STEPS TO REPRODUCE
1. With Orca enabled, open any website with Mozilla Firefox or Chromium.
2. Press Orca Key + H to turn on learn mode
3. Press modifier keys by thgemselves (left CTRL. left shift, left alt, right
control, right shift, right alt)

OBSERVED RESULT
Below is the list of bindings Orca ssigns to those actions
- Left CTRL: goes to the last live region that made an announcement
- Left Shift: Go to the next image
- Left alt: goes to the next button.
- Right shift: Go to next combo box.
- Enter: go to next table.


EXPECTED RESULT
Modifier keys, by themselves never had actions bound to them. I expect the
modifiers, especially shift to behave like it always did, allowing m to reverse
structural navigation.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.16.0-0.rc3.250627g67a993863163.35.fc43.aarch64 (64-bit)
Graphics Platform: Wayland
Processors: 8
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: Parallels International GmbH.
Product Name: Parallels ARM Virtual Machine
System Version: 0.1

ADDITIONAL INFORMATION
Orca version: 48.6

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