[kwin] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot

2024-05-28 Thread Andreas Nordal
https://bugs.kde.org/show_bug.cgi?id=487155

--- Comment #5 from Andreas Nordal  ---
That version info I think was filled in by DrKonqui (I don't remember writing
it).

It happened again. Here is what happened to poor /dev/null when when it was
Firefox I resized, so that KDE6 crashed and can't be restarted:

> ls -l /dev/null 
-rw--- 1 root root 9 mai   29 00:47 /dev/null
> sudo xxd devnull
: 6469 7361 626c 6564 0a   disabled.

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

[plasmashell] [Bug 481113] When not using Systemd or Plasma's Systemd session launch integration, changes to pinned apps are not saved when Plasmashell quits

2024-05-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

--- Comment #47 from Andreas Sturmlechner  ---
(In reply to Nate Graham from comment #37)
> Apparently in some distros, kbuildsycoca is run frequently/repeatedly, and
> there was previously an issue that could cause some things to not get saved
> properly.
We do nothing of that kind in Gentoo ourselves unless this is somehow triggered
in rare KDE Plasma non-systemd code paths. Please note this bug means that
Plasma 6 remains masked in Gentoo for the time being, so most users still get
Plasma 5.27.11 unless taking additional steps to upgrade.

Not fixed in 6.0.90 either.

KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

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

[kphotoalbum] [Bug 444744] Recreate (video-) thumbnails selectively

2024-05-22 Thread Andreas Schleth
https://bugs.kde.org/show_bug.cgi?id=444744

--- Comment #1 from Andreas Schleth  ---
I just stumbled across this again (v5.12.0-129-g2c8635bc) and checked with a
fresh build from git master (v5.12.0-133-g1de2d467). I think the maintenance
feature "Refresh selected thumbnails and checksums" was introduced after I
filed the first report (not sure). But it still does not (yet :-) work for
video:

In my oldish version (-129-) the videothumbnail without a number (-0 ... -9) is
refreshed, but the 10 other files that make up the "flicker film" (shown on
mouse over) are not.

What happened with the demo-database (newest version):
* In the current version (-133-) I replaced the file movie.avi ("Hi I am
Jesper...") with another avi file. 
* Then "Refresh ...": Nothing happened. File date remains the same for all
videothumbnails.
* Then I deleted the files in .videothumbnails. This finally triggers the
rebuild.
* The flicker now film shows the correct video. 
* The filenames in .videothumbnails remain the same (obviously they are just a
hash of the filename).
* But the static image still shows Jesper.  :-(
* This only changes after hitting "crtl"+"+"

What happened with my own database (oldish version):
* After "Refresh..." there were two files (without the -x ending) with a new
date stamp.
* The other corresponding files (*-0 ... *-9) still had their old date stamps.
* Only after deleting all 22 files the thumbnails were correctly regenerated.

What I expect:
* on "Refresh ..." the static and the dynamic thumbnail images of a movie
should be replaced by a newer version

currently: 
KPA v5.12.0-129-g2c8635bc
KDE Frameworks Version 5.103.0
Qt Version 5.15.8

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

[kphotoalbum] [Bug 320297] Incredibly slow video thumbnailing

2024-05-22 Thread Andreas Schleth
https://bugs.kde.org/show_bug.cgi?id=320297

Andreas Schleth  changed:

   What|Removed |Added

 CC||schleth...@web.de

--- Comment #3 from Andreas Schleth  ---
This bug here might be out of date. 

Afaik, we did some work on speeding up the creation of videothumbnails in the
past.

If thumbnailing is done on each start, there is probably something wrong with
file permissions of the .videothumbnails folder ... (?)

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-05-20 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #36 from Andreas Sturmlechner  ---
Reopening, I can confirm not fixed with the patch applied to libplasma-6.0.4.

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

[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files

2024-05-20 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=485999

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

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

[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot

2024-05-17 Thread Andreas Nordal
https://bugs.kde.org/show_bug.cgi?id=487155

--- Comment #2 from Andreas Nordal  ---
Created attachment 169577
  --> https://bugs.kde.org/attachment.cgi?id=169577=edit
New crash information added by DrKonqi

kate (24.02.2) using Qt 5.15.13

Third time in a row. I think I'm discovering a more consistent way to trigger
it. I accidentally made the window quarter-screen-sized before I hit the point
where it becomes half-sized.

-- Backtrace (Reduced):
#6  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159
#7  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540,
stroker=0x7ffdf4f91ba0) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152
#8  drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int)
(stroker=0x7ffdf4f91ba0, rx1=, ry1=,
rx2=, ry2=, caps=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809
#9  0x7fe6810cb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF
const&) (this=0x7ffdf4f91ba0, p1=..., p2=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356
#10 0x7fe6810f089c in QRasterPaintEngine::drawLines(QLine const*, int)
(this=, lines=, lineCount=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198

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

[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot

2024-05-17 Thread Andreas Nordal
https://bugs.kde.org/show_bug.cgi?id=487155

--- Comment #1 from Andreas Nordal  ---
Created attachment 169576
  --> https://bugs.kde.org/attachment.cgi?id=169576=edit
New crash information added by DrKonqi

kate (24.02.2) using Qt 5.15.13

Exactly the same happened again.
I dragged Kate to the right half side of the screen.
It's usually not that often.

-- Backtrace (Reduced):
#6  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159
#7  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540,
stroker=0x7ffc49e1bc60) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152
#8  drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int)
(stroker=0x7ffc49e1bc60, rx1=, ry1=,
rx2=, ry2=, caps=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809
#9  0x7fa901ccb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF
const&) (this=0x7ffc49e1bc60, p1=..., p2=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356
#10 0x7fa901cf089c in QRasterPaintEngine::drawLines(QLine const*, int)
(this=, lines=, lineCount=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198

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

[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot

2024-05-17 Thread Andreas Nordal
https://bugs.kde.org/show_bug.cgi?id=487155

Andreas Nordal  changed:

   What|Removed |Added

 CC||andreas_norda...@hotmail.co
   ||m

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

[kate] [Bug 487155] New: KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot

2024-05-17 Thread Andreas Nordal
https://bugs.kde.org/show_bug.cgi?id=487155

Bug ID: 487155
   Summary: KDE6: Dragging windows into screen edges often crashes
the program and sometimes the whole desktop so I have
to reboot
Classification: Applications
   Product: kate
   Version: 24.02.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: andreas_norda...@hotmail.com
  Target Milestone: ---

Application: kate (24.02.2)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.8-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I like that you can maximize or half-size a window by dragging it over the top
or side edges.
This was no problem in KDE5, but in KDE6, it sometimes crashes the window.
Kate is no special. It happens to Konsole and Firefox too.
When it's firefox, the whole desktop crashes and /dev/null becomes replaced
with a regular file
(usually of zero bytes, but sometimes containing a linefeed terminated
message),
and KDE hangs forever when I try to restart it, so I have to reboot.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  0x7f48e5ac7a8e in BYTE_MUL (a=4294967040, x=Python Exception : Cannot access memory at address 0x7f4250821808
#5  sourceOver (color=4293783021, d=Python Exception :
Cannot access memory at address 0x7f4250821808
#6  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159
#7  drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540,
stroker=0x7ffc8fe21c50) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152
#8  drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int)
(stroker=0x7ffc8fe21c50, rx1=, ry1=,
rx2=, ry2=, caps=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809
#9  0x7f48e5acb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF
const&) (this=0x7ffc8fe21c50, p1=..., p2=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356
#10 0x7f48e5af089c in QRasterPaintEngine::drawLines(QLine const*, int)
(this=, lines=, lineCount=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198
#11 0x7f48e457ea16 in QPainter::drawLine(int, int, int, int) (y2=, x2=, y1=0, x1=, this=0x7ffc8fe232b0,
this=, x1=, y1=, x2=, y2=) at /usr/include/qt6/QtGui/qpainter.h:455
#12 KateRenderer::paintTextLine(QPainter&, KateLineLayout*, int, int, QRectF
const&, KTextEditor::Cursor const*, QFlags)
(this=0x55e7e6b67720, paint=..., range=0x55e7eac99d60, xStart=0, xEnd=65012,
textClipRect=, cursor=0x7ffc8fe232b8, flags=...) at
/usr/src/debug/ktexteditor-6.2.0/src/render/katerenderer.cpp:969
#13 0x7f48e45f0b9a in KateViewInternal::paintEvent(QPaintEvent*)
(this=0x55e7e77fc290, e=0x7ffc8fe23500) at
/usr/src/debug/ktexteditor-6.2.0/src/render/katetextlayout.cpp:119
#14 0x7f48e640e38d in QWidget::event(QEvent*) (this=0x55e7e77fc290,
event=0x7ffc8fe23500) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9183
#15 0x7f48e63c2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55e7e77fc290, e=0x7ffc8fe23500) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287
#16 0x7f48e518f060 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55e7e77fc290, event=0x7ffc8fe23500) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134
#17 0x7f48e518f6a9 in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1589
#18 0x7f48e63fe955 in QWidgetPrivate::sendPaintEvent(QRegion const&)
(this=this@entry=0x55e7e76c3e50, toBePainted=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:5647
#19 0x7f48e6400599 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) (this=this@entry=0x55e7e76c3e50,
pdev=pdev@entry=0x55e7e74db900, rgn=..., offset=..., flags=flags@entry=...,
sharedPainter=sharedPainter@entry=0x0, repaintManager=) at
/usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:5597
#20 0x7f48e6402849 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*, QWidgetRepaintManager*)
(this=0x55e7e7601310, pdev=0x55e7e74db900, siblings=..., 

[basket] [Bug 484855] basket-2.49b fails to compile with libgit2-1.8.0

2024-05-16 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=484855

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://invent.kde.org/util
   ||ities/basket/-/merge_reques
   ||ts/49

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

[valgrind] [Bug 486180] [Valgrind][MIPS] 'VexGuestArchState' has no member named 'guest_IP_AT_SYSCALL'

2024-04-29 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=486180

--- Comment #8 from Andreas Arnez  ---
(In reply to Mark Wielaard from comment #7)
> The current use only really is known to work for s390x.
The use for the extension mechanism, yes.  But I was under the impression that
this field is required for all architectures that use Ijk_Sys_syscall and
friends (which I thought included all arches). Consider the comment in
libvex_ir.h:

   Re Ijk_Sys_ (syscall jumps): the guest state must have a
   pseudo-register guest_IP_AT_SYSCALL, which is the size of a guest
   word.  ...

However, now I'm not sure where the field is actually used, apart from the new
usage in handle_extension().  Does anybody know more about this?

> So I would propose something like:
> [...]

That's an option, although I prefer to get rid of this altogether and just use
VG_(get_IP), like below.  Now I'm wondering why I haven't done
that before.  Is this OK?

diff --git a/coregrind/m_scheduler/scheduler.c
b/coregrind/m_scheduler/scheduler.c
index 29751bb28..cc8d070b7 100644
--- a/coregrind/m_scheduler/scheduler.c
+++ b/coregrind/m_scheduler/scheduler.c
@@ -1237,8 +1237,7 @@ static void handle_extension(ThreadId tid)
   block_signals();
   VG_(poll_signals)(tid);
} else if (err != ExtErr_OK) {
-  ThreadState* tst = VG_(get_ThreadState)(tid);
-  Addr addr = tst->arch.vex.guest_IP_AT_SYSCALL;
+  Addr addr = VG_(get_IP)(tid);
   switch (err) {
   case ExtErr_Illop:
  VG_(synth_sigill)(tid, addr);

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

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

2024-04-29 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=450705

Andreas Arnez  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #9 from Andreas Arnez  ---
Support for the NNPA instruction has also been pushed, so NNPA support should
be complete now.

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

[frameworks-kio] [Bug 485854] kde-frameworks/kio-6.1.0: [LLVM-18] src/gui/systemd/scopedprocessrunner.cpp:60:9: error: use of undeclared identifier 'close'

2024-04-26 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=485854

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://invent.kde.org/fram
   ||eworks/kio/-/merge_requests
   ||/1619

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

[neon] [Bug 482059] SDDM Theme is not being used

2024-04-24 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482059

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #12 from Andreas Sturmlechner  ---
Just for the record, at this point it is not a packaging error but a packaging
decision as I cannot personally get the Qt6 greeter to work on my system, and
this is documented with a pending bug downstream.

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

[filelight] [Bug 485936] filelight not working after system update QQmlComponent: Component is not ready org.kde.kcoreaddons not installed on gentoo+gnome45

2024-04-22 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=485936

Andreas Sturmlechner  changed:

   What|Removed |Added

 Status|CLOSED  |RESOLVED

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

[filelight] [Bug 485936] filelight not working after system update QQmlComponent: Component is not ready org.kde.kcoreaddons not installed on gentoo+gnome45

2024-04-22 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=485936

Andreas Sturmlechner  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED
 CC||ast...@gentoo.org

--- Comment #1 from Andreas Sturmlechner  ---
Thanks. This is a downstream bug, which is where it is going to be fixed.

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

[frameworks-kio] [Bug 485854] kde-frameworks/kio-6.1.0: [LLVM-18] src/gui/systemd/scopedprocessrunner.cpp:60:9: error: use of undeclared identifier 'close'

2024-04-22 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=485854

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #4 from Andreas Sturmlechner  ---
Thanks, can you please take your patch to https://invent.kde.org/frameworks/kio
by creating an MR there?

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

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

2024-04-18 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=450705

--- Comment #7 from Andreas Arnez  ---
(In reply to Andreas Arnez from comment #6)
> Created attachment 168623 [details]
> Updated version of the extension proposal
I pushed this now, as a preparation to adding NNPA support.  If there are still
any issues with this, please let me know.

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

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

2024-04-17 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=450705

--- Comment #6 from Andreas Arnez  ---
Created attachment 168623
  --> https://bugs.kde.org/attachment.cgi?id=168623=edit
Updated version of the extension proposal

This updated version of the extension proposal addresses the following:

* Add a comment that explains the use of guest_IP_AT_SYSCALL for extension
handlers.

* Ensure that compilation doesn't break on other platforms.

* Fix some issues with the PRNO implementation.

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

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

2024-04-17 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=450705

--- Comment #4 from Andreas Arnez  ---
(In reply to Mark Wielaard from comment #3)
> Extension idea was posted to the mailinglist:
> https://sourceforge.net/p/valgrind/mailman/message/58753610/
Right. I'd like to go ahead with this, if that's OK. There shouldn't be any
impact on other platforms at this point, AFAIK, and any potential improvements
can likely be performed on top without too much hassle.

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

[Spectacle] [Bug 469022] Selected area bleaches text

2024-04-16 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=469022

--- Comment #63 from Andreas  ---
But what should users of LTS distributions like Kubuntu or openSUSE Leap do?
There is no version of Spectacle in the flatpak. 
Where is this fix so that it can be backported?

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

[Spectacle] [Bug 477292] Request - Create Flatpak of Spectacle, also put on FlatHub

2024-04-12 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=477292

Andreas  changed:

   What|Removed |Added

 CC||opendr...@gmail.com

--- Comment #2 from Andreas  ---
I also support, I use all possible KDE applications in Flatpak, since I use an
LTS distribution.
The only thing missing is Spectacle and Kate.
For example, in Spectacle from the repositories I have a bug that is not in new
versions of Spectacle and I have no way out because it is not in Flatpak
https://bugs.kde.org/show_bug.cgi?id=469022

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

[Spectacle] [Bug 469022] Selected area bleaches text

2024-04-12 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=469022

Andreas  changed:

   What|Removed |Added

 CC||opendr...@gmail.com

--- Comment #58 from Andreas  ---
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.4.0-150600.12-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Xeon® E-2186M CPU @ 2.90GHz
Graphics Processor: Mesa Intel® UHD Graphics P630 / Nvidia Quadro P3200
Product Name: Precision 7530
Spectacle: 23.08.5

I have the same issue, Spectacle GUI becomes transparent when selecting
rectangular screenshot mode.
The bug is present on Intel iGPU, if you disable composer, the problem
disappears. Everything is also in order on Nvidia dGPU.
Spectacle 24.02.1 on Plasma 6.0.3 and X11 does not have this issue.

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

[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop

2024-04-12 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=478556

--- Comment #22 from Andreas Schneider  ---
And another addition/observation (hoping that this helps narrowing down where
the problem could come from): I now closed a few other windows (especially
those on the left monitor) and suddenly Goland takes mouse inputs again - even
on the main screen.

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

[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop

2024-04-12 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=478556

--- Comment #21 from Andreas Schneider  ---
Now I have it happen to an open Goland instance. Moving it to my left monitor
it works, moving it back to the main monitor and it's immediately "broken"
again. I can Meta+Left-Click to move and Meta+Right-Click to resize, but
otherwise the mouse only interacts with the window "below". Keyboard input is
forwarded (i.e. I can navigate using the keyboard and also type stuff), though,
as long as the window has focus.

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

[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop

2024-04-12 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=478556

Andreas Schneider  changed:

   What|Removed |Added

 CC||ak...@gmx.de

--- Comment #20 from Andreas Schneider  ---
I have that happen quite a lot. I also can't find a way to fix the IntelliJ
window, besides moving it to my left-most monitor, so I assume there might be
some scaling included.

My setup: 100% scaled 1280x1024 on the left, 125% scaled 3440x1440 on the
right. The right one is the main monitor.
I typically have IntelliJ in the left-half-quick-tile block of the big monitor.
I also have multiple virtual desktops I switch between.

Switching focus a few times between different windows, it can happen that
IntelliJ can't focus anymore. Mouse-over and click events seem to "fall
through" to the window below. Moving the window to the other monitor fixes it
in the meantime. Moving it back sometimes works for a while and then fails
again. I haven't had it fail on the left-most monitor yet. As long as the
window was there, all was fine.

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

[okular] [Bug 484929] New: Okular crashes when changing annotations

2024-04-02 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=484929

Bug ID: 484929
   Summary: Okular crashes when changing annotations
Classification: Applications
   Product: okular
   Version: 24.02.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: hoheneg...@web.de
  Target Milestone: ---

Application: okular (24.02.1)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.5.0-10027-tuxedo x86_64
Windowing System: Wayland
Distribution: KDE neon 6.0
DrKonqi: 6.0.3 [KCrashBackend]

-- Information about the crash:
With all PDFs I have tried so far okular crashes when I modify annotations
since upgrade to current plasma, frameworks and apps.
I also switched from Xorg to Wayland recently.
The behaviour can be triggered by adding a note (Pop-up or Inline) and deleting
it again by selecting that option from the right-click menu.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139534905563840)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139534905563840) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=139534905563840, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7ee804042476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7ee8040287f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x7ee804cdb597 in qAbort () at ./src/corelib/global/qglobal.cpp:161
#10 0x7ee804cd67f5 in qt_message_fatal (message=..., context=...)
at ./src/corelib/global/qlogging.cpp:2003
#11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=...,
msg=, ap=ap@entry=0x7ffc4d4c1340) at
./src/corelib/global/qlogging.cpp:378
#12 0x7ee804cdbfc3 in QMessageLogger::fatal (this=,
msg=) at ./src/corelib/global/qlogging.cpp:901
#13 0x7ee804ca0387 in qt_assert_x (where=,
what=what@entry=0x7ee7e43dae98 "Called object is not of the correct type (class
destructor may have already run)", file=file@entry=0x7ee7e43dae58
"/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h",
line=line@entry=129) at ./src/corelib/global/qassert.cpp:77
#14 0x7ee7e43069cd in QtPrivate::assertObjectType
(o=) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:129
#15 0x7ee7e4306c86 in QtPrivate::assertObjectType
(o=0x591570f151e0) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:526
#16 QtPrivate::FunctorCall, QtPrivate::List<>, void,
void (AnnotWindow::*)()>::call(void (AnnotWindow::*)(), AnnotWindow*, void**)
(arg=, o=0x591570f151e0, f=(void (AnnotWindow::*)(AnnotWindow *
const)) 0x7ee7e4308c50 ) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:144
#17 QtPrivate::FunctionPointer::call, void>(void (AnnotWindow::*)(),
AnnotWindow*, void**) (arg=, o=0x591570f151e0, f=(void
(AnnotWindow::*)(AnnotWindow * const)) 0x7ee7e4308c50
) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:182
#18 QtPrivate::QCallableObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=, this_=, r=0x591570f151e0, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:520
#19 0x7ee804c3c3ce in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433
#20 doActivate (sender=0x591571519e60, signal_index=7,
argv=0x7ffc4d4c1508) at ./src/corelib/kernel/qobject.cpp:4039
#21 0x7ee804c3c6ab in doActivate (sender=0x59157152fb30,
signal_index=3, argv=0x7ffc4d4c15d8) at ./src/corelib/kernel/qobject.cpp:4051
#22 0x7ee805c13c28 in QWidgetTextControl::qt_metacall (this=0x59157152fb30,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffc4d4c16d8) at
./obj-x86_64-linux-gnu/src/widgets/Widgets_autogen/include/moc_qwidgettextcontrol_p.cpp:741
#23 0x7ee804c3c4b8 in doActivate (sender=0x59157152fd10,
signal_index=4, argv=0x7ffc4d4c16d8) at ./src/corelib/kernel/qobject.cpp:4065
#24 0x7ee80534ab3c in QTextDocumentPrivate::finishEdit
(this=0x591571390f40) at ./src/gui/text/qtextdocument_p.cpp:1218
#25 0x7ee805329961 in QSyntaxHighlighter::setDocument
(this=this@entry=0x5915715981e0, doc=doc@entry=0x0) at
./src/gui/text/qsyntaxhighlighter.cpp:302
#26 0x7ee805329dbd in QSyntaxHighlighter::~QSyntaxHighlighter
(this=, this=) at
./src/gui/text/qsyntaxhighlighter.cpp:284
#27 0x7ee7e4463d5d in Sonnet::Highlighter::~Highlighter (this=, this=) at ./src/ui/highlighter.cpp:168
#28 0x7ee804bcb2ca in QObjectPrivate::deleteChildren
(this=this@entry=0x591571598640) at ./src/corelib/kernel/qobject.cpp:2207
#29 0x7ee804bd2198 in QObject::~QObject (this=,
this=) at 

[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland

2024-03-31 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=477124

--- Comment #16 from Andreas Schneider  ---
First impression with 6.0.3 is, that it's fixed (for me).

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

[systemsettings] [Bug 484662] New: Usability bug in Systemsettings Sound dialog

2024-03-28 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=484662

Bug ID: 484662
   Summary: Usability bug in Systemsettings Sound dialog
Classification: Applications
   Product: systemsettings
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_pulseaudio
  Assignee: plasma-b...@kde.org
  Reporter: hoheneg...@web.de
CC: m...@ratijas.tk
  Target Milestone: ---

SUMMARY

I may not be aware of all use cases, but the selection of the profile in the
Sound dialog of the systemsettings app appears to be counter-intuitive. 
Based on tests of the interface and comparison to pavucontrol, the selection of
a "Profile" determines which Input and Playback Devices etc. are active. 
Since the dropdownlist appears in general repeatedly, for each device or device
type, placed behind the "Port" of the device, the global role of the function
is not represented well in the GUI:
Switching the profile will affect all devices. 
It appears that it would better appear only once and be placed above the
listing of the device types.
Also, "Input Devices" may better correspond to the user's expectation than
"Recording Devices".   

STEPS TO REPRODUCE
1. Start systemsettings.
2. Go to "Input & Output" -> "Sound"
3. Observe the GUI

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

[plasmashell] [Bug 482773] Panel configuration not fully saving

2024-03-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482773

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=481113

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=482773

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

[dolphin] [Bug 482899] Dolphin can't write to folder with group write access

2024-03-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482899

--- Comment #8 from Andreas Sturmlechner  ---
At least for me this was fixed after backporting this (among other) commits.

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

[plasmashell] [Bug 484077] After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

--- Comment #5 from Andreas Schneider  ---
It doesn't happen if I lock the screensaver and unlock. But it happens if the
monitor is sent to sleep and then I unlock again.

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

[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland

2024-03-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=477124

Andreas Schneider  changed:

   What|Removed |Added

 CC||ak...@gmx.de

--- Comment #15 from Andreas Schneider  ---
I can currently reliably reproduce it with Hell Let Loose using Proton 9 on
Plasma 6.0.2 on ArchLinux. Once ingame, the mouse hits a barrier and then
starts jumping around, making it impossible to aim at anything. Works fine on
X11. It also doesn't matter if I play it windows or fullscreen. (It can be
reproduced in the training ground; one doesn't have to join a multiplayer
game.)

Elder Scrolls Online behaves a bit different: when I start the game, the mouse
jumps every few seconds, turning my camera almost 180° around. Switching the
game to window mode (alt+enter) and back fixes it, though.

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-21 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

   Keywords||wayland

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

[print-manager] [Bug 484082] Printer list is empty on every KDE6 application

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484082

Andreas Schneider  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Andreas Schneider  ---
I didn't have the package qt6-printsupport-cups installed.

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

[print-manager] [Bug 484082] New: Printer list is empty on every KDE6 application

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484082

Bug ID: 484082
   Summary: Printer list is empty on every KDE6 application
Classification: Frameworks and Libraries
   Product: print-manager
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: a...@cryptomilk.org
  Target Milestone: ---

Created attachment 167511
  --> https://bugs.kde.org/attachment.cgi?id=167511=edit
kde6-print-dialog-fail.png

SUMMARY
I have an IPP printer connected to my machine but I'm unable to print to with
KDE6 applications. As you can see in the screenshot, the printer is correctly
detected by the system settings kcm_print plugin, but I'm not able to select it
in any application using the print dialog. To be exact it doesn't show any CUPS
printer.

STEPS TO REPRODUCE
1. Add a CUPS printer
2. Try to print from an application (kmail, okular, ...)

OBSERVED RESULT
Can't select my cups printer

EXPECTED RESULT
Print on CUPS printers

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed/KDE 6 Plasma - Wayland session
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.2.2

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

[plasmashell] [Bug 484077] After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

--- Comment #4 from Andreas Schneider  ---
My monitor is set to 125% scaling.

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

[plasmashell] [Bug 484077] After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

--- Comment #3 from Andreas Schneider  ---
If I open a new application, the pager gets updated and the full panel is shown
again.

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

[plasmashell] [Bug 484077] After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

--- Comment #2 from Andreas Schneider  ---
Created attachment 167508
  --> https://bugs.kde.org/attachment.cgi?id=167508=edit
plasma6-workspace-good.webp

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

[plasmashell] [Bug 484077] After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

--- Comment #1 from Andreas Schneider  ---
Created attachment 167507
  --> https://bugs.kde.org/attachment.cgi?id=167507=edit
plasma6-workspace-bad.webp

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

[plasmashell] [Bug 484077] New: After sleep/unlocking the screen the panel widget isn't fully displayed

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484077

Bug ID: 484077
   Summary: After sleep/unlocking the screen the panel widget
isn't fully displayed
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: a...@cryptomilk.org
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
If my PC goes to sleep and I unlock my screen, my bottom panel isn't fully
displayed anymore. See attached screenshots.

STEPS TO REPRODUCE
1. Set up a panel on the bottom in the cent like in the screenshot
2. Suspend
3. Wake up
4. Unlock screen

OBSERVED RESULT
The bottom panel is reduced to a single icon.

EXPECTED RESULT
The bottom panel is fully shown.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed/Plasma 6 - Wayland Session
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.2.2

ADDITIONAL INFORMATION
GPU: AMD Radeon RX 6900 XT
Mesa: 24.0.3
Plasma Style: Otto

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

[plasma-nm] [Bug 484045] New: Please add support for Secret Service

2024-03-20 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=484045

Bug ID: 484045
   Summary: Please add support for Secret Service
Classification: Plasma
   Product: plasma-nm
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: a...@cryptomilk.org
  Target Milestone: ---

SUMMARY

Please add support to use secret service for passwords. This could be achieved
using QtKeychain which support kwalletd and secret service. It would allow to
use keepassxc to store passwords.

See also:
* https://github.com/keepassxreboot/keepassxc/issues/3679
* https://invent.kde.org/office/kmymoney/-/merge_requests/170
* https://specifications.freedesktop.org/secret-service/

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

[angelfish] [Bug 484013] New: When entering heise. into the URL field it is changed to seise. automatically on platform Mobian

2024-03-19 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=484013

Bug ID: 484013
   Summary: When entering heise. into the URL field it is changed
to seise. automatically on platform Mobian
Classification: Applications
   Product: angelfish
   Version: 23.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: j...@kaidan.im
  Reporter: andr...@immerfroehlich.de
  Target Milestone: ---

SUMMARY
When entering heise. into the URL field it is changed to seise. automatically
on platform Mobian


STEPS TO REPRODUCE
1. Open angelfish.
2. Click on the URL field at the bottom of the page.
3. Enter "heise."

OBSERVED RESULT
The text is automatically changed to "seise."

EXPECTED RESULT
The text should not be changed automatically.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Mobian
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
No additional information given.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-19 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #30 from Andreas Schneider  ---
As initially said that this is something for power users, I think using as the
command: /home/me/foo.sh %t

with foo.sh:

#!/bin/bash
TITLE=$1

echo "$TITLE"

should really not be a challenge for a power user. There is no need for option
parsing if you're the only one who controls this.

If you really need all of those variables to make a decision what to do in the
script. Then you're advanced enough to quickly code up option parsing in your
bash script. It is a 30 line switch statement in bash. Providing the expansion
on the command line allow you to use them with already existing executables.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-19 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #28 from Andreas Schneider  ---
You can pass it as command line options:

https://invent.kde.org/plasma/plasma-workspace/uploads/bc3d74f4f8a25b08c05b3553e9813316/image.png

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

[kdevelop] [Bug 483981] New: kdevelop crashes after few minutes

2024-03-19 Thread Andreas Knüpfer
https://bugs.kde.org/show_bug.cgi?id=483981

Bug ID: 483981
   Summary: kdevelop crashes after few minutes
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@posteo.de
  Target Milestone: ---

Application: kdevelop (5.12.230801 (23.08.1))

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.7.9-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
When I created a new project with a few short python scripts in it or when I
load the project again, then it waits for a couple of minutes ... while I
looked in other applications ... and then segfaults. This happened repeatedly.

The one special thing is that I specified a special python interpreter in the
project settings ... one from a newly created venv that I need for the project.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  0x7f8f69307395 in KDevelop::IndexedIdentifier::identifier() const ()
from /lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.512
#5  0x7f8f692f3a79 in KDevelop::Declaration::identifier() const () from
/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.512
#6  0x7f8f2fe5a8fb in
Python::DeclarationBuilder::addArgumentTypeHints(Python::CallAst*,
KDevelop::DUChainPointer) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#7  0x7f8f2fe5acae in
Python::DeclarationBuilder::visitCall(Python::CallAst*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#8  0x7f8f2fe561e5 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#9  0x7f8f2fe622ef in
Python::DeclarationBuilder::visitAssignment(Python::AssignmentAst*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#10 0x7f8f2fe561e5 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#11 0x7f8f2ffe050c in Python::AstDefaultVisitor::visitFor(Python::ForAst*)
() from /lib/x86_64-linux-gnu/libkdevpythonparser.so
#12 0x7f8f2fe561e5 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#13 0x7f8f2fe52060 in
Python::ContextBuilder::visitFunctionBody(Python::FunctionDefinitionAst*) ()
from /lib/x86_64-linux-gnu/libkdevpythonduchain.so
#14 0x7f8f2fe63df8 in
Python::DeclarationBuilder::visitFunctionDefinition(Python::FunctionDefinitionAst*)
() from /lib/x86_64-linux-gnu/libkdevpythonduchain.so
#15 0x7f8f2fe561e5 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#16 0x7f8f2ffdfb0c in
Python::AstDefaultVisitor::visitCode(Python::CodeAst*) () from
/lib/x86_64-linux-gnu/libkdevpythonparser.so
#17 0x7f8f2fe52d1b in Python::ContextBuilder::visitCode(Python::CodeAst*)
() from /lib/x86_64-linux-gnu/libkdevpythonduchain.so
#18 0x7f8f2fe561e5 in non-virtual thunk to
Python::DeclarationBuilder::visitNode(Python::Ast*) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#19 0x7f8f2fe64d33 in ?? () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#20 0x7f8f2fe55563 in ?? () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#21 0x7f8f2fe505e8 in Python::ContextBuilder::build(KDevelop::IndexedString
const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#22 0x7f8f2fe577b1 in
Python::DeclarationBuilder::build(KDevelop::IndexedString const&, Python::Ast*,
KDevelop::ReferencedTopDUContext const&) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#23 0x7f8f2fe5774a in
Python::DeclarationBuilder::build(KDevelop::IndexedString const&, Python::Ast*,
KDevelop::ReferencedTopDUContext const&) () from
/lib/x86_64-linux-gnu/libkdevpythonduchain.so
#24 0x7f8f2ff00034 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/512/kdevpythonlanguagesupport.so
#25 0x7f8f679700ab in
ThreadWeaver::IdDecorator::run(QSharedPointer,
ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#26 0x7f8f6796fcdf in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#27 0x7f8f67970bc3 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#28 0x7f8f679752a0 in ThreadWeaver::Thread::run() () from
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#29 0x7f8f6b4daeb1 in ?? 

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-19 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

--- Comment #23 from Andreas Sturmlechner  ---
(In reply to ollilein from comment #22)
> I made a whole new clean gentoo install on with bootloader grub and init 
> system openrc.
Please note that this is *not in any way* related to your choice of bootloader.
:)

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

[kio] [Bug 333077] Dolphin sais: Unable to request the SFTP subsystem. Make sure SFTP is enabled on the server.

2024-03-19 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=333077

Andreas Schneider  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #11 from Andreas Schneider  ---
I think this has been fixed in libssh.

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

[libkgapi] [Bug 483911] New: Feature: Allow to use app passwords for authentication

2024-03-18 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=483911

Bug ID: 483911
   Summary: Feature: Allow to use app passwords for authentication
Classification: Frameworks and Libraries
   Product: libkgapi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: dvra...@kde.org
  Reporter: a...@cryptomilk.org
  Target Milestone: ---

SUMMARY
If the authentication of your Google account is not managed by Google, but is
going to an external IdP, your account will be disconnected as soon as you
restart akonadi or after 24h.

The only way for me, that applications are able to connect, is setting up
2-Step-Verfication and use App Passwords:

https://myaccount.google.com/ -> Security -> 2-Step-Verification -> App
Passwords

Is it possible to use username & app password somehow or could it be
implemented?

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-18 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

Andreas Schneider  changed:

   What|Removed |Added

   Assignee|kdelibs-b...@kde.org|a...@cryptomilk.org
 Status|CONFIRMED   |ASSIGNED

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-18 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #24 from Andreas Schneider  ---
UI: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4096
Backend: https://invent.kde.org/frameworks/knotifications/-/merge_requests/143

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

[kontact] [Bug 483844] kontact segfaults on startup

2024-03-18 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=483844

--- Comment #3 from Andreas Schneider  ---
Thank you very much for the quick fix.

I wanted to send a email to the package maintainer at openSUSE. So in konsole I
right clicked on the mail choose "Send EMail To". This opened a new mail
dialog, but also the opened mail I didn't send out yesterday. I've sent both
mails and after that kmail/kontact started  without the segfault.

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

[konsole] [Bug 481898] No saved size & position

2024-03-17 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481898

Andreas Schneider  changed:

   What|Removed |Added

 CC||a...@cryptomilk.org

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

[kontact] [Bug 483844] kontact segfaults on startup

2024-03-17 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=483844

--- Comment #1 from Andreas Schneider  ---
(gdb) f 1
#1  0x7fff8c822a44 in KMMainWidget::updateFolderMenu (this=0x57191b90)
at /usr/src/debug/kmail-24.02.0/src/kmmainwidget.cpp:4069
4069mFolderMailingListPropertiesAction->setEnabled(folderWithContent &&
!mCurrentFolderSettings->isSystemFolder());
(gdb) l
4064QTimer::singleShot(1s, this, ::updateFolderMenu);
4065return;
4066}
4067
4068const bool folderWithContent = mCurrentFolderSettings &&
!mCurrentFolderSettings->isStructural() && mCurrentFolderSettings->isValid();
4069mFolderMailingListPropertiesAction->setEnabled(folderWithContent &&
!mCurrentFolderSettings->isSystemFolder());
4070
4071QList actionlist;
4072if (mCurrentCollection.id() ==
CommonKernel->outboxCollectionFolder().id() &&
(mCurrentCollection).statistics().count() > 0) {
4073qCDebug(KMAIL_LOG) << "Enabling send queued";
(gdb) p mFolderMailingListPropertiesAction
$1 = (QAction *) 0x0

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

[kontact] [Bug 483844] New: kontact segfaults on startup

2024-03-17 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=483844

Bug ID: 483844
   Summary: kontact segfaults on startup
Classification: Applications
   Product: kontact
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: a...@cryptomilk.org
  Target Milestone: ---

Created attachment 167372
  --> https://bugs.kde.org/attachment.cgi?id=167372=edit
kontact.gdb.log

SUMMARY
I've wrote a mail in kontact and then closed kontact (the new mail still open).
I realized that I didn't send the mail and tried to start kontact again. Now it
segfaults on start. Backtrace attached.

STEPS TO REPRODUCE
1. Start writing a new mail
2. Close kontact
3. Try to start it again

OBSERVED RESULT
Segafult

EXPECTED RESULT
Kontact starting up

SOFTWARE/OS VERSIONS
Linux: openSUSE Tumbleweed
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.2.2

kmail-24.02.0-1.1.x86_64

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

[dolphin] [Bug 482899] Dolphin can't write to folder with group write access

2024-03-16 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482899

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

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

[krusader] [Bug 483741] Krusader - Video Thumbnails dont Generate on Plasma 6

2024-03-16 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=483741

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org
 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Andreas Sturmlechner  ---
krusader is KF5-based, but your distribution package management has upgraded to
KF6-based ffmpegthumbs.

Unfortunately, ffmpegthumbs is not out-of-the-box co-installable with KF5-based
version by upstream, so this would have to be solved by your distribution, if
they are interested in providing it.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-16 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #23 from Andreas Schneider  ---
The UI must be separate, but I don't really know where. I can confirm that it
works:

$ cat .config/kalendarac.notifyrc
[Event/alarm]
Action=Sound|Popup|Execute
Sound=/usr/share/sounds/freedesktop/stereo/bell.oga
Execute=/home/asn/bin/kde-alarm-event.sh %t

Finally, my TTS tells me which appointment I have. %t is the notification title
now.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-15 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #22 from Andreas Schneider  ---
I've re-implemented the feature. However I need some help.

a) Is it possible to reload the libKF6notificatins.so without restarting the
whole desktop?
b) I don't see an additional field in the Notifications settings: System
Settings -> Notifications -> Calendar Reminders -> Alarm. Do I need to
re-implement the UI part somewhere else?

I'm @asn:matrix.org in the KDE Development Matrix channel. Some pointers would
be much appreciated.

https://invent.kde.org/anschneider/knotifications/-/commits/asn-notifyexecute

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

[kate] [Bug 483631] Legacy VI-Mode config crashes kate and kwrite

2024-03-15 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=483631

--- Comment #3 from Andreas  ---
Would that suffice (does not seem to provide a lot more info)?

~> gdb kwrite
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kwrite...
Reading symbols from
/usr/lib/debug/.build-id/da/b5cd68711f7c03f634e7e3f0e426cf8808d3cb.debug...
(gdb) run
Starting program: /usr/bin/kwrite 

This GDB supports auto-downloading debuginfo from the following URLs:
https://debuginfod.neon.kde.org/:
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x703ff640 (LWP 3265322)]
[New Thread 0x7fffeef5d640 (LWP 3265323)]
[New Thread 0x7fffee75c640 (LWP 3265324)]
[New Thread 0x7fffed952640 (LWP 3265543)]
[New Thread 0x7fffed151640 (LWP 3265750)]
[New Thread 0x7fffec950640 (LWP 3265751)]
[New Thread 0x7fffd6dff640 (LWP 3265752)]
[New Thread 0x7fffd65fe640 (LWP 3265753)]
[New Thread 0x7fffd5dfd640 (LWP 3265754)]
[New Thread 0x7fffd55fc640 (LWP 3265755)]
[New Thread 0x7fffd4dfb640 (LWP 3265756)]
[New Thread 0x7fffb7fff640 (LWP 3265757)]
[New Thread 0x7fffb77fe640 (LWP 3265758)]
[New Thread 0x7fffb6ffd640 (LWP 3265759)]
[Thread 0x7fffb6ffd640 (LWP 3265759) exited]
[Thread 0x7fffb77fe640 (LWP 3265758) exited]
[Thread 0x7fffb7fff640 (LWP 3265757) exited]
[Thread 0x7fffd4dfb640 (LWP 3265756) exited]
ASSERT: "rc <= 0x" in file
/usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h, line 79

Thread 1 "kwrite" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228689344) at
./nptl/pthread_kill.c:44
Download failed: Invalid argument.  Continuing without source file
./nptl/./nptl/pthread_kill.c.
44  ./nptl/pthread_kill.c: No such file or directory.

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

[kate] [Bug 483631] Legacy VI-Mode config crashes kate and kwrite

2024-03-15 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=483631

--- Comment #2 from Andreas  ---
As mentioned I do unfortunately not have a backtrace. How could I enforce its
creation without compiling from sources?

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

[kate] [Bug 483631] New: Legacy VI-Mode config crashes kate and kwrite

2024-03-15 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=483631

Bug ID: 483631
   Summary: Legacy VI-Mode config crashes kate and kwrite
Classification: Applications
   Product: kate
   Version: 24.02.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: hoheneg...@web.de
  Target Milestone: ---

SUMMARY

Kate and kwrite fail to digest certain legacy configuration and crash during
startup.

STEPS TO REPRODUCE
1.  Insert specific config in your $HOME/.config/katevirc :

[Kate Vi Input Mode Settings]
Command Mode Mapping Keys=
Command Mode Mappings=
Command Mode Mappings Recursion=
Insert Mode Mapping Keys=
Insert Mode Mappings=
Insert Mode Mappings Recursion=
Macro Completions=
Macro Contents=
Macro Registers=
Map Leader=,
Normal Mode Mapping Keys=,,vw
Normal Mode Mappings="+gP,"+gP,vb
Normal Mode Mappings Recursion=false,false,false
ViRegisterContents=inconclusive,\t\t\t\t\t\n\t\t\t\t\t\tIn contrast to
previous evaluation\\, the evaluator determined that no additional
packages that be acquired this time. The distribution DVDs are in fact
self-contained. \n\t\t\t\t\t\t\n\t\t\t\t\t\n,\n  
  The extended components definition in ASE_ECD.\n 
\n  \n  \n 
\n The remaining\\, non-mandatory parts of the ST.\n   
  \n  \n  \n 
 
ViRegisterFlags=0,1,0
ViRegisterNames=-,0,^
Visual Mode Mapping Keys=,,,
Visual Mode Mappings="+y,"+x,"+x,"+y
Visual Mode Mappings Recursion=false,false,false,false

2.  Run kate or kwrite
3.  Observe the crash

OBSERVED RESULT

The application crashes during startup.

Output of "strace kwrite" is:

readlink("/home", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~/.config", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid argument)
readlink("~/.config/katevirc", 0x7ffc14ffd8f0, 1023) = -1 EINVAL (Invalid
argument)
openat(AT_FDCWD, "/home/andreas/.config/katevirc", O_RDONLY|O_CLOEXEC) = 19
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
statx(19, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0600,
stx_size=1666, ...}) = 0
read(19, "[Kate Vi Input Mode Settings]\nCo"..., 16384) = 1666
read(19, "", 14718) = 0
close(19)   = 0
openat(AT_FDCWD, "/dev/tty", O_RDONLY|O_CLOEXEC) = 19
close(19)   = 0
write(2, "ASSERT: \"rc <= 0x\" in file /"..., 89ASSERT: "rc <= 0x" in
file /usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h, line 79
) = 89
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
gettid()= 680280
getpid()= 680280
tgkill(680280, 680280, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=680280, si_uid=1001}
---
+++ killed by SIGABRT +++
Aborted

I do not get offered a debug option, therefore, no complete debug logs
included.

EXPECTED RESULT

Kwrite and kate handle the apparently invalid config gracefully and startup
normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon user edition
KDE Plasma Version: 6.0.2
KDE Frameworks Version: Version 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

I upgraded from KDE Neon user edition where the config used to work.
It suffices to remove the line 
Visual Mode Mapping Keys=,,,
from above config.

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

--- Comment #20 from Andreas Sturmlechner  ---
(In reply to yamagi from comment #13)
> I'm seeing this on Arch Linux with Plasma 6.0.1 and I'm using systemd boot.
Just for clarification, which one did you mean:

1) Speaking of the bootloader:
https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/
2) Or Plasma systemd startup:
https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #19 from Andreas Sturmlechner  ---
Created attachment 167128
  --> https://bugs.kde.org/attachment.cgi?id=167128=edit
plasmashell.log

Here's a plasmashell log of me starting a wayland session from tty.

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

Andreas Sturmlechner  changed:

   What|Removed |Added

 Attachment #167127|0   |1
is obsolete||

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

--- Comment #17 from Andreas Sturmlechner  ---
Created attachment 167127
  --> https://bugs.kde.org/attachment.cgi?id=167127=edit
plasmashell.log

Here's my log from starting plasma wayland session from tty.

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also|https://bugs.kde.org/show_b |
   |ug.cgi?id=482469|
 CC||krpis...@protonmail.com

--- Comment #17 from Andreas Sturmlechner  ---
*** Bug 482469 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also|https://bugs.kde.org/show_b |
   |ug.cgi?id=481113|
 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #16 from Andreas Sturmlechner  ---
Let's keep discussions in one bug (the other one was filed earlier).

*** This bug has been marked as a duplicate of bug 481113 ***

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

[Powerdevil] [Bug 483099] Screen energy saving not working with DisplayPort screen

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=483099

--- Comment #8 from Andreas Sturmlechner  ---
In any case, can you please upgrade to 6.0.2 to make sure this hasn't been
fixed in the meantime.

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

[frameworks-kio] [Bug 483399] Properties dialog is maximized if Dolphin is maximized and you attempt to view folder properties

2024-03-13 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=483399

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #1 from Andreas Sturmlechner  ---
Yup, can confirm that here as well with same package versions.

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

2024-03-12 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481113

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=482469

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-12 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

Andreas Sturmlechner  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=481113

--- Comment #12 from Andreas Sturmlechner  ---
Nate, from this USE flag configuration we can infer this is with systemd.

(In reply to Jaroslav Krpálek from comment #0)
> plasma-workspace use flags:
> USE="calendar fontconfig policykit screencast semantic-desktop systemd

Can we let Jaroslav run a command that confirms systemd "boot feature" is being
used?

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

[Powerdevil] [Bug 483099] Screen energy saving not working with DisplayPort screen

2024-03-12 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=483099

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #3 from Andreas Sturmlechner  ---
So this is just about SDDM? Or while you are logged into your Plasma-6 session?
Please note that the lockscreen is *not* SDDM.

Since for me it works fine in Plasma 6 session with similar hardware (AMD RX
6700 attached to (a single) DisplayPort screen):

KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.21-gentoo (64-bit)
Graphics Platform: Wayland

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

[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog

2024-03-12 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481287

--- Comment #15 from Andreas Sturmlechner  ---
(In reply to Michael Weghorn from comment #13)
> How can I reproduce your scenario? Is this just setting up a Gentoo VM,
> install LO and KDE Plasma 6 and start LO there or are more steps needed?
That would be essentially it, but if Arch Linux users can reproduce it then
presumably that will get you there faster (with less compile time since none of
the packages involved are currently stable hence not available as Gentoo binary
packages).

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

[plasmashell] [Bug 483044] Plasmashell crashes inPipeWireSourceStream::~PipeWireSourceStream() after relogin

2024-03-11 Thread Andreas Hencke
https://bugs.kde.org/show_bug.cgi?id=483044

--- Comment #4 from Andreas Hencke  ---
@Nate Graham: No, I did nothing like that.

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

[systemsettings] [Bug 482048] kcm_mouse crashes when opening setting

2024-03-11 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482048

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #23 from Andreas Sturmlechner  ---
(In reply to Francois C. from comment #21)
> For some stupid reason, Gentoo disabled X support by default. 
No, you did.

For the record: Of course in Gentoo X is enabled for desktop profiles, which
you were expected to be using when running a desktop environment.

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

[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog

2024-03-11 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481287

--- Comment #12 from Andreas Sturmlechner  ---
This works, but it is testing file open - which works fine in LO calc for me as
well, not save though (currently on 24.2.2.1).

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

[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)

2024-03-10 Thread Andreas
https://bugs.kde.org/show_bug.cgi?id=480856

Andreas  changed:

   What|Removed |Added

 CC||hoheneg...@web.de

--- Comment #9 from Andreas  ---
I can report that the Reddit workaround
https://www.reddit.com/r/kdeneon/comments/1aenouy/kde_neon_wont_boot_after_fresh_install_cryptsetup/
works (where I replaced /dev/nvme0n1p2 with my root partition path inferred
from, e.g., partitionmanager)  

---

On the running system, out of curiosity I re-added the keyfile to the key slots
of my two encrypted partitions by calling this:
sudo cryptsetup luksAddKey /dev/nvme0n1p2 /crypto_keyfile.bin
To my surprise when checking sudo cryptsetup luksDump /dev/nvme0n1p2 before and
after adding of the keyfile, I found out that the new key slot data does not
match any of the old slots. It looks like the keyfile was not added correctly
to the slots before.

Also I put the /crypto_keyfile.bin back into the /etc/crypttab (replacing the
none's) but did not add back the keyscript=/bin/cat. I read in the man page of
crypttab that the third parameter is the keyfile. I didn't see the need to add
the keyscript at all.

sudo update-initramfs -c -k all 

and reboot



This can be done after booting the installed system as follows from an
(initramfs) prompt
https://discuss.kde.org/t/disk-encryption-not-working-on-recent-neon-isos-but-is-working-on-older-images/9505/4

-

cryptsetup luksOpen /dev/disk/by-id/[deviceid] luks-

and enter the password. Then run

exec run-init /root /sbin/init /root/dev/console

-

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

[Oxygen] [Bug 481402] question mark icons shown in systray when oxygen icon theme

2024-03-10 Thread Andreas Hencke
https://bugs.kde.org/show_bug.cgi?id=481402

Andreas Hencke  changed:

   What|Removed |Added

 CC||andreas.hen...@mailbox.org

--- Comment #3 from Andreas Hencke  ---
Same here (I'm the 2nd guy on the thread mentioned by firewalker).
When I go to systemsettings --> colors and designs --> icons and change to
Adwaita --> apply  then instantanously back to Oxygen --> apply
the icons (monochrome in black) appear when hovering with the mousepointer.
One'll have to redo after a reboot.

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

[plasmashell] [Bug 483044] Plasmashell crashes after relogin

2024-03-09 Thread Andreas Hencke
https://bugs.kde.org/show_bug.cgi?id=483044

--- Comment #1 from Andreas Hencke  ---
Created attachment 166833
  --> https://bugs.kde.org/attachment.cgi?id=166833=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 483044] New: Plasmashell crashes after relogin

2024-03-09 Thread Andreas Hencke
https://bugs.kde.org/show_bug.cgi?id=483044

Bug ID: 483044
   Summary: Plasmashell crashes after relogin
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: andreas.hen...@mailbox.org
  Target Milestone: 1.0

Application: plasmashell (6.0.1)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.1 [CoredumpBackend]

-- Information about the crash:
The screen was locked after a period of inactivity. After login plasmashell
crashed immediatelly .

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x76890e6ab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#7  0x76890e65a6c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x76890e6424b8 in __GI_abort () at abort.c:79
#9  0x76890e643395 in __libc_message_impl (fmt=fmt@entry=0x76890e7bb2ea
"%s\n") at ../sysdeps/posix/libc_fatal.c:132


Reported using DrKonqi

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

[frameworks-bluez-qt] [Bug 481870] Bluetooth related 25 second delay after logging in

2024-03-08 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481870

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-07 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

--- Comment #8 from Andreas Sturmlechner  ---
You're not using qt5ct or qt6ct, do you? (we block it in
kde-plasma/plasma-meta).

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

[plasmashell] [Bug 482469] Plasmashell does not remember desktop icon size or programs in the panel

2024-03-06 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482469

--- Comment #5 from Andreas Sturmlechner  ---
How can I help?

First thing I'd recommend is upgrade to Plasma 6.0.1 and check your permissions
on ~/.config, ~/.local and ~/.cache

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

[okular] [Bug 482443] okular - add build options for wayland (non X11) build options

2024-03-05 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=482443

Andreas Sturmlechner  changed:

   What|Removed |Added

 CC||ast...@gentoo.org

--- Comment #2 from Andreas Sturmlechner  ---
Thanks for your report. Indeed invent.kde.org is the way to go and get proper
review.

I have submitted quite a few MRs upstream like yours, you can have a look in
https://bugs.gentoo.org/813450 for inspiration.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-03-04 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #14 from Andreas Schneider  ---
I can look into it once I get Plasma 6 via my distribution.

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

[systemsettings] [Bug 452445] per-application keyboard layout not persisting

2024-03-01 Thread Andreas Korb
https://bugs.kde.org/show_bug.cgi?id=452445

--- Comment #24 from Andreas Korb  ---
This appears to still be a issue in KDE 6, unfortunately. Is there any plan for
this issue?
Otherwise, I'm actually willing to implement this myself, as it is the only
thing that hinders me of fully switching to Wayland. Then, I'd appreciate some
pointers, e.g., why it worked under X11 but doesn't under Wayland as of now,
and which code areas are relevant. Thanks!

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

[kfind] [Bug 93707] Find dialog: option should include archive contents

2024-02-28 Thread Andreas Schallenberg
https://bugs.kde.org/show_bug.cgi?id=93707

Andreas Schallenberg  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|LATER   |---

--- Comment #3 from Andreas Schallenberg  ---
This bug is now marked as NEEDSINFO, but what extra information can I provide?
I would still find this feature useful and encourage me to use the mechanism
more often.

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

[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog

2024-02-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481287

--- Comment #6 from Andreas Sturmlechner  ---
Works fine if started with SAL_USE_VCLPLUGIN=qt6 instead.

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

[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog

2024-02-27 Thread Andreas Sturmlechner
https://bugs.kde.org/show_bug.cgi?id=481287

Andreas Sturmlechner  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|VERIFIED|REOPENED

--- Comment #5 from Andreas Sturmlechner  ---
As mentioned in the linked MR[1] unfortunately this is still not fixed on my
system.

1. run localc
2. Ctrl + Shift + S (or File -> Save As)
3. (Enter random name) Save

File dialog reappears every time instead of saving the file.


Operating System: Gentoo 2.14
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.17-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 62,7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Product Name: X570 Phantom Gaming-ITX/TB3

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 32; OS: Linux 6.6; UI render: default; VCL: kf6 (cairo+wayland)
Locale: de-AT (de_AT.UTF-8); UI: en-US
Gentoo official package
Calc: threaded

[1] https://invent.kde.org/plasma/plasma-integration/-/merge_requests/137

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

[frameworks-knotifyconfig] [Bug 481751] "Run command" doesn't work

2024-02-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481751

Andreas Schneider  changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED

--- Comment #2 from Andreas Schneider  ---
This is really bad :-(

I finally got it working after some debugging. LC_ALL was not set, so spd-say
didn't work as it couldn't set the locale. I will comment on the bug you linked
that I use this.

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-02-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

--- Comment #11 from Andreas Schneider  ---
Here is the script I execute. I would be nice to get the event summary and
event start, but only getting the functionality in KDE6 would be enough for a
start.

cat bin/kde-alarm-event.sh
#!/bin/bash

# System Settings -> Notifications -> Application-specific settings
# Calendar Reminders -> Configure Events
# Run command: /home/asn/bin/kde-alarm-event.sh
#
# You can pass as arguments:
# %e – Event ID
# %a – Application Name
# %s – Text
# %w – WinID
# %t – window title (if it is a widget)
# %i – notification ID
# %d – Application display name
#
# None of them provide the event summary :-(

# We need to set LC_ALL or spd-say wont work!
LC_ALL=de_DE.UTF-8
export LC_ALL

/usr/bin/spd-say -l de -w "Andreas, du hast einen Termin"

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

2024-02-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481069

Andreas Schneider  changed:

   What|Removed |Added

 CC||a...@cryptomilk.org

--- Comment #10 from Andreas Schneider  ---
I'm also using this with "spd-say" to remind me about calendar events. The
notification system is not enough, korgac was much better than this small
notification.

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

[frameworks-knotifyconfig] [Bug 481751] "Run command" doesn't work

2024-02-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481751

Andreas Schneider  changed:

   What|Removed |Added

Version|unspecified |5.115.0

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

[frameworks-knotifyconfig] [Bug 481751] New: "Run command" doesn't work

2024-02-24 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=481751

Bug ID: 481751
   Summary: "Run command" doesn't work
Classification: Frameworks and Libraries
   Product: frameworks-knotifyconfig
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: a...@cryptomilk.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
I'm trying to set up a notification command for an calendar alarm as Speech
doesn't work. So I set

"Run command" to "/usr/bin/spd-say -l de "Terminerinnerung: %e"

However, I never get any speech output. If I run the command on the command
line it works just fine.

STEPS TO REPRODUCE
1. Go to System Settings -> Notifications
2. Got to Application-specific Settings
3. Select Calender Reminders
4. Klick on Configure Events...
5. Set "Run command" to "/usr/bin/spd-say -l de "Terminerinnerung: %e"

OBSERVED RESULT
Silence

EXPECTED RESULT
There should be voice ouptut from speech-dispatcher

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12

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

[Spectacle] [Bug 480794] rectangular area not visible

2024-02-18 Thread Andreas Beder
https://bugs.kde.org/show_bug.cgi?id=480794

Andreas Beder  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

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

[parley] [Bug 468591] Window does not repaint under wayland

2024-02-18 Thread Andreas Cord-Landwehr
https://bugs.kde.org/show_bug.cgi?id=468591

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ
   |ation/parley/-/commit/5e2f7 |ation/parley/-/commit/2c730
   |0bf149515a7e7d087a8b1449bf2 |388a14fe6dbd303f2e345efeeea
   |4d822c5e|28bb1b6b

--- Comment #5 from Andreas Cord-Landwehr  ---
Git commit 2c730388a14fe6dbd303f2e345efeeea28bb1b6b by Andreas Cord-Landwehr.
Committed on 18/02/2024 at 14:38.
Pushed by cordlandwehr into branch 'master'.

Fix window updates on wayland

This refactors all (wrongly) used KXmlGuiWindow objects to be just
QWidgets. This avoids wrong calls to winid() which leads to severe
window render update misses.

M  +23   -17   src/parleymainwindow.cpp
M  +2-3src/parleymainwindow.h

https://invent.kde.org/education/parley/-/commit/2c730388a14fe6dbd303f2e345efeeea28bb1b6b

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

[parley] [Bug 468591] Window does not repaint under wayland

2024-02-18 Thread Andreas Cord-Landwehr
https://bugs.kde.org/show_bug.cgi?id=468591

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||thebluequa...@mailo.com

--- Comment #4 from Andreas Cord-Landwehr  ---
*** Bug 459934 has been marked as a duplicate of this bug. ***

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

  1   2   3   4   5   6   7   8   9   10   >