[dolphin] [Bug 469990] New: Microsoft Store error pop-up every time I launch Dolphin

2023-05-19 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=469990

Bug ID: 469990
   Summary: Microsoft Store error pop-up every time I launch
Dolphin
Classification: Applications
   Product: dolphin
   Version: 23.04.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: me...@gmx.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 159098
  --> https://bugs.kde.org/attachment.cgi?id=159098&action=edit
Screenshot of error pop-up

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. I launch Dolphin
2. 
3. 

OBSERVED RESULT
Every time I launch Dolphin I get a Windows pop-up saying that I will 'need a
new app to open this ms-gamingoverlay link'. The pop-up disappears when I click
anywhere on the screen, and then Dolphin works as expected. 

EXPECTED RESULT
There should be no pop-up. 

SOFTWARE/OS VERSIONS
Windows: Windows 10 64bit 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[dolphin] [Bug 469994] New: 'Show on startup: Folders, tabs...' has no effect.

2023-05-19 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=469994

Bug ID: 469994
   Summary: 'Show on startup: Folders, tabs...' has no effect.
Classification: Applications
   Product: dolphin
   Version: 23.04.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: me...@gmx.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Dolphin doesn't remember my startup settings. Instead of starting with the tabs
and folders I had open in the previous session, it always starts with one tab
showing Home. 

STEPS TO REPRODUCE
1. In settings, select 'Folders, tabs...' for 'Show on startup'  
2. Open multiple tabs showing different folders 
3. Restart Dolphin 


OBSERVED RESULT
Dolphin restarts with one tab showing Home. 

EXPECTED RESULT
It should open with the tabs and folders from last time

SOFTWARE/OS VERSIONS
Windows: 10 64bit 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[dolphin] [Bug 469990] Microsoft Store error pop-up every time I launch Dolphin

2023-05-20 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=469990

--- Comment #2 from meso5  ---
I just switched off Xbox Game Bar in Windows settings and the popup stopped
appearing. This is not an issue for me any more but it is still an issue for
Dolphin. Dolphin does something that in certain circumstances unnecessarily
triggers that unnecessary Windows error message which I had never seen before.
It is even more confusing when the system is like mine, never used for gaming.

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

[okular] [Bug 478304] New: Okular exits every time I open a digitally signed PDF

2023-12-09 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=478304

Bug ID: 478304
   Summary: Okular exits every time I open a digitally signed PDF
Classification: Applications
   Product: okular
   Version: 23.08.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: me...@gmx.com
  Target Milestone: ---

Application: okular (23.08.4)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.2.0-37-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 5.27
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Every time I open a certain digitally signed PDF, Okular exits without warning.
This happens with Okular on KDE Neon and on Windows 10. Acrobat Pro and
PDF-XChange on Windows 10 open it as normal and display the digital signature
info banner. Master PDF on Windows 10, and Atril and Evince on Debian Sid open
it but they seem to be unaware of the digital signature, even in the document
Properties. I can't locate another digitally signed PDF to compare, and can't
provide the PDF above because of confidentiality.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault

[KCrash Handler]
#4  0x7f0d6de45059 in NSSSignatureVerification::NSSSignatureVerification
(p7data=..., this=0x559979344660) at ./poppler/NSSCryptoSignBackend.cc:779
#5  std::make_unique > > () at
/usr/include/c++/11/bits/unique_ptr.h:962
#6  NSSCryptoSignBackend::createVerificationHandler (this=,
pkcs7=...) at ./poppler/NSSCryptoSignBackend.cc:1189
#7  0x7f0d6dd2963e in FormFieldSignature::validateSignature
(this=0x559978f22ea0, doVerifyCert=doVerifyCert@entry=true,
forceRevalidation=forceRevalidation@entry=false, validationTime=-1,
ocspRevocationCheck=, enableAIA=enableAIA@entry=false) at
./poppler/Form.cc:2387
#8  0x7f0d6dd29b9c in FormWidgetSignature::validateSignature
(this=this@entry=0x559979338fa0, doVerifyCert=doVerifyCert@entry=true,
forceRevalidation=forceRevalidation@entry=false, validationTime=, ocspRevocationCheck=, enableAIA=enableAIA@entry=false) at
./poppler/Form.cc:579
#9  0x7f0d740bfa6a in Poppler::FormFieldSignature::validate
(this=this@entry=0x55997933e020, opt=opt@entry=1, validationTime=...) at
./qt5/src/poppler-form.cc:1044
#10 0x7f0d740bff14 in Poppler::FormFieldSignature::validate
(this=0x55997933e020,
opt=Poppler::FormFieldSignature::ValidateVerifyCertificate) at
./qt5/src/poppler-form.cc:978
#11 0x7f0d7413e5cb in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
#12 0x7f0d7414504c in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
#13 0x7f0d7413472d in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so
#14 0x7f0d940d1fa2 in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.11
#15 0x7f0d940db71e in Okular::Document::openDocument(QString const&, QUrl
const&, QMimeType const&, QString const&) () from
/lib/x86_64-linux-gnu/libOkular5Core.so.11
#16 0x7f0d8cee7995 in Okular::Part::doOpenFile(QMimeType const&, QString
const&, bool*) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#17 0x7f0d8cee91c3 in Okular::Part::openFile() () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#18 0x7f0d9c99ac65 in ?? () from /lib/x86_64-linux-gnu/libKF5Parts.so.5
#19 0x7f0d9c9a0b27 in KParts::ReadOnlyPart::openUrl(QUrl const&) () from
/lib/x86_64-linux-gnu/libKF5Parts.so.5
#20 0x7f0d8cee5dcb in Okular::Part::openUrl(QUrl const&, bool) () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so
#21 0x55997693263b in ?? ()
#22 0x559976934289 in ?? ()
#23 0x7f0d9aef4394 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f0d9aef4394 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f0d9bc62a06 in QAbstractButton::clicked(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7f0d9bc62c8e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f0d9bc648b4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7f0d9bc64ad7 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x7f0d9bbaf95e in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7f0d9bb6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#31 0x7f0d9bb743a4 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x7f0d9aebc8ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7f0d9bb72e87 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouse

[okular] [Bug 478304] Okular exits every time I open a digitally signed PDF

2023-12-10 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=478304

--- Comment #2 from meso5  ---
(In reply to Albert Astals Cid from comment #1)
> Would it be possible for us to have access to that file?

The file is technically confidential even though there is nothing particularly
exciting in there. Would the file still be useful if I redacted identifying
info? The digital signature would then fail but the file may still reveal the
problem. If I could locate more digitally signed PDFs I could try them out.

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

[okular] [Bug 478304] Okular exits every time I open a digitally signed PDF

2023-12-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=478304

--- Comment #4 from meso5  ---
As it turns out, Acrobat Pro won't let me redact anything because the file is
signed, which makes sense. As I said, there is nothing important or interesting
in the file and I wouldn't mind sending it to you somehow for debugging as long
as it's not publicly available on the web and you commit to discarding it
afterwards, but I can't find a way to submit a file confidentially.

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

[okular] [Bug 478304] Okular exits every time I open a digitally signed PDF

2023-12-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=478304

--- Comment #6 from meso5  ---
I just emailed it to you.

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

[plasmashell] [Bug 454245] New: Pop-ups stealing clicks

2022-05-22 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=454245

Bug ID: 454245
   Summary: Pop-ups stealing clicks
   Product: plasmashell
   Version: master
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: me...@gmx.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

It is incredibly annoying when you click on something and a pop-up appears out
of nowhere in precisely the wrong place stealing the mouse click. Particularly
frustrating when you know you just OKed something but you don't know what
because the pop-up disappeared immediately. It doesn't happen often but when it
does it can be very dangerous too. It is surprising it can still happen in
every environment I am aware of, but I think KDE could be the first DE to do
the sensible thing: A clickable element shouldn't be clickable until it is
reasonably possible for a human being to have clicked on it on purpose. Clicks
that are faster than this are either stolen clicks or robo-clicks. One idea is
to grey-out the buttons for a fraction of a second before they become really
clickable. If this takes a fraction of a second, in the vast majority of cases
that a pop-up appears the user won't even know this delay was injected. In the
spirit of KDE this could be made optional.

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

[kwin] [Bug 454245] Pop-ups stealing clicks

2022-05-24 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=454245

--- Comment #2 from meso5  ---
I am aware of focus stealing prevention. My understanding is that it would turn
click-stealing and many more pop-ups into pop-behinds. Then, you would have to
bring the dialogue to the front to click its button. This adds friction and
penalises the user. A tiny delay in making the buttons active would work
seamlessly. In the vast majority of cases, users won't even realise
click-stealing is designed out, until the day a click-stealing situation occurs
to them. At that point they will be hugely impressed if they realise the
protection is by design. I appreciate though a delay may be too difficult to
implement.

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

[dolphin] [Bug 441006] New: Dolphin crashed when I pressed Ctrl+C to copy a folder

2021-08-15 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=441006

Bug ID: 441006
   Summary: Dolphin crashed when I pressed Ctrl+C to copy a folder
   Product: dolphin
   Version: 20.12.2
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: me...@gmx.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (20.12.2)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.0-8-amd64 x86_64
Windowing system: X11
Distribution: Debian GNU/Linux 11 (bullseye)

-- Information about the crash:
- What I was doing when the application crashed:

I navigated to a folder in the right pane, selected the folder name (with the
branch collapsed), and just pressed Ctrl+C to copy the whole folder. 

- Unusual behavior I noticed:

I noticed 30 minutes or so earlier, but in the same Dolphin session, Dolphin
was very busy, taking up 50% CPU utilisation for at least 15 minutes. This is
an old, slow desktop but it was still excessive. Then, utilisation dropped to
normal levels, below 5%.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7ff8d7562c18 in QMetaObject::cast(QObject const*) const () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff8d14b434c in QQuickShortcutContext::matcher(QObject*,
Qt::ShortcutContext) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#6  0x7ff8d79604ef in QShortcutMap::find(QKeyEvent*, int) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7ff8d7963390 in QShortcutMap::nextState(QKeyEvent*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7ff8d7964641 in QShortcutMap::tryShortcut(QKeyEvent*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x7ff8d790dcae in QWindowSystemInterface::handleShortcutEvent(QWindow*,
unsigned long, int, QFlags, unsigned int, unsigned int,
unsigned int, QString const&, bool, unsigned short) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x7ff8d79304cb in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x7ff8d790a64c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x7ff8d241e7da in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#13 0x7ff8d52abe6b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7ff8d52ac118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7ff8d52ac1cf in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7ff8d75b151f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7ff8d755898b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7ff8d7560c00 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7ff8d96ad9e0 in kdemain () from
/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so
#20 0x7ff8d94c1d0a in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#21 0x55fe17e1108a in _start ()
[Inferior 1 (process 8562) detached]

Possible duplicates by query: bug 437968, bug 434310, bug 427149, bug 330508.

Reported using DrKonqi

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

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

2021-07-22 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=439132

meso5  changed:

   What|Removed |Added

 CC||me...@gmx.com

--- Comment #4 from meso5  ---
I am seeing this with several applications (but not with Thunderbird). Eg
clicking on any link in Okular and LibreOffice among other applications
triggers kioexec caching and then the cached copy of the web page is opened in
Firefox. That copy often doesn't look as it should, and the actual URL is not
available on the Firefox address bar. Also, there is no trace of the page or
URL in the next session as the cache is apparently flushed between sessions.
More details here:
https://www.reddit.com/r/kde/comments/oj1gc5/kioexec_caches_web_pages_for_firefox/
 

Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-8-amd64
OS Type: 64-bit

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

[Breeze] [Bug 476890] New: Text in tooltips is distorted

2023-11-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=476890

Bug ID: 476890
   Summary: Text in tooltips is distorted
Classification: Plasma
   Product: Breeze
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: me...@gmx.com
CC: uhh...@gmail.com
  Target Milestone: ---

Created attachment 163085
  --> https://bugs.kde.org/attachment.cgi?id=163085&action=edit
Today's screenshot. Top line affected.

STEPS TO REPRODUCE
1. Hover over any of the taskbar icons (Application Launcher, clock, tray
icons, running application etc)  
2. 
3. 

OBSERVED RESULT
Some of the tooltip text is distorted as in screenshot1. It is always the text
on the first row, in the bigger font that is affected. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.27
(available in About System)
KDE Plasma Version:  5.27.9 
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

Kernel Version: 6.2.0-36-generic (64-bit)
Graphics Platform: X11
Processors: 2 × Pentium® Dual-Core CPU E6300 @ 2.80GHz
Memory: 3.8 GiB of RAM
Graphics Processor: NV96

ADDITIONAL INFORMATION
A few weeks I was getting the same kind of distortion in tooltips with both
Wayland and X11 but all fonts were affected. See additional screenshots 2-4.
Somehow the problem is now reduced to the top line text.

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

[Breeze] [Bug 476890] Text in tooltips is distorted

2023-11-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=476890

--- Comment #1 from meso5  ---
Created attachment 163086
  --> https://bugs.kde.org/attachment.cgi?id=163086&action=edit
Older example.

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

[Breeze] [Bug 476890] Text in tooltips is distorted

2023-11-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=476890

--- Comment #2 from meso5  ---
Created attachment 163087
  --> https://bugs.kde.org/attachment.cgi?id=163087&action=edit
Another older example

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

[Breeze] [Bug 476890] Text in tooltips is distorted

2023-11-12 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=476890

--- Comment #3 from meso5  ---
Created attachment 163088
  --> https://bugs.kde.org/attachment.cgi?id=163088&action=edit
And another older example.

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

[kwin] [Bug 476890] Text in QtQuick views is distorted

2023-11-16 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=476890

--- Comment #5 from meso5  ---
(In reply to Nate Graham from comment #4)
> Please report this issue to the NVIDIA folks

I would but I very much doubt anyone will want to fix a bug in 14 years old
hardware. They will probably say I can get a complete more modern system for
50€ on ebay. Thanks anyway.

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

[okular] [Bug 387834] Okular does not display replies to "sticky notes"

2024-12-22 Thread meso5
https://bugs.kde.org/show_bug.cgi?id=387834

meso5  changed:

   What|Removed |Added

 CC||me...@gmx.com

--- Comment #3 from meso5  ---
This is a major bug that makes Okular completely unsuitable when PDFs go back
and forth between collaborating authors, eg when multiple reviewers add replies
to a comment. This scenario is very common in academic, publishing and admin
environments. 

The worst part is that, as the reporter said, Okular gives you no indication at
all that there is something missing. So, you have to assume that you have to
double-check with another application every time (or simply use that other
application in the first place and forget about Okular).

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