[kde] [Bug 463320] New: Theme is not consistent

[Den]

https://bugs.kde.org/show_bug.cgi?id=463320

Bug ID: 463320
   Summary: Theme is not consistent
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: denis.puj...@gmail.com
  Target Milestone: ---

Created attachment 154735
  --> https://bugs.kde.org/attachment.cgi?id=154735&action=edit
screen

I have just installed Fedora KDE Plasma.
First impression is cool. Sorry but I don't like GNOME.
But have some feedback.
The theme is not consistent. After I changed the theme to Breeze Dark, the
Login screen remained the same. How can I switch the login screen to the Breeze
dark as well? So it should be the same everywhere.

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

[kde] [Bug 463320] Theme is not consistent

[Den]

https://bugs.kde.org/show_bug.cgi?id=463320

Den  changed:

   What|Removed |Added

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

--- Comment #1 from Den  ---
Sorry guys. after I upgraded Fedora 37 to the latest version (4gb) the login
screen started look the same as the theme. Thank you.
KDE Plasma is the best :-)

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

[lattedock] [Bug 410390] New: interface lags, when dock showing up

[Den]

https://bugs.kde.org/show_bug.cgi?id=410390

Bug ID: 410390
   Summary: interface lags, when dock showing up
   Product: lattedock
   Version: 0.9.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: kde...@gmail.com
  Target Milestone: ---

SUMMARY
For example: when i press f12 for Yakuake and dock is hidden, because have
active windows on it, yakuake shows up with lags(other apps same). If
latte-dock disabled, applications animation is normal. So, dock show up
animation freezes other interface animations.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 4.19.60-1-MANJARO #1 SMP PREEMPT Sun Jul 21 12:17:26
UTC 2019 x86_64 GNU/Linux
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

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

[kmail2] [Bug 321669] multipart mails incompletely displayed

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=321669

--- Comment #4 from tony den haan  ---
It definitely looks like the problem is the order in which content is placed in
the mail, if Content-type: text/html comes after the text/plain part, HTML is
not detected and the plain text bit is shown.

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

[kgpg] [Bug 369609] shows only white and blue for trust levels

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=369609

--- Comment #6 from tony den haan  ---
I find it quite confusing, signing a key is "Trust", and signing a key with
"havent checked at all" gives green, no matter what "owner trust" level i set
via key properties. I'd expect slightly different colour there :)
Maybe providing separate field/column might make things clearer?

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

[frameworks-knotifications] [Bug 455319] New: KDE notification floods

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=455319

Bug ID: 455319
   Summary: KDE notification floods
   Product: frameworks-knotifications
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: kdeb...@tuxick.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 149734
  --> https://bugs.kde.org/attachment.cgi?id=149734&action=edit
kde flood screenshot

STEPS TO REPRODUCE
1. use KDE
2. wait for something to go wrong

OBSERVED RESULT

Screen fills up with alerts. I've been seeing this on KDE for quite a while
already.


EXPECTED RESULT

a single alert

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.24 
KDE Frameworks Version: About KDE no longer shows this 
Qt Version:  5.15

ADDITIONAL INFORMATION

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

[Discover] [Bug 455319] Flood of "Restart the system now" notifications

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=455319

--- Comment #3 from tony den haan  ---
(In reply to Nate Graham from comment #1)
> > 2. wait for something to go wrong
> What does this mean exactly? The notification question is typically sent by
> Discover. Under what condition does it appear multiple times like this?

This is just one example, and it's not just this particular notification. Point
is that in such case i get multiple notifications of same issue. I remember a
case where i got over 100 :) Pretty sure i'll be able to provide another
screenshot soon enough. Sadly no idea what condition causes this.

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

[kate] [Bug 421451] Kate raises hspell error when launched from command line

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=421451

tony den haan  changed:

   What|Removed |Added

 CC||kdeb...@tuxick.net

--- Comment #18 from tony den haan  ---
(In reply to Fergal Mullally from comment #17)
> For anyone coming across this issue, I solved it by installing hspell on my
> system with apt. It's about 1.2Mb in size
> 
> ```
> sudo apt install hspell -y
> 
> 
> My guess -- and it's only a guess -- is that Kate comes bundled with hspell,
> but it missing some of the dictionary files. Installing hspell directly
> installs those dictionary files and removes the warning.

But why does it even try? I don't need Hebrew spelling.

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

[konsole] [Bug 395058] New: ssh:// link opens konsole with --noclose

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=395058

Bug ID: 395058
   Summary: ssh:// link opens konsole with --noclose
   Product: konsole
   Version: 17.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: kdeb...@tuxick.net
  Target Milestone: ---

When i follow an ssh:// link in browser konsole opens ssh session to the host,
but the --noclose causes it to just hang there after closing the session. I
can't really imagine a case where this might be useful, but could it somehow at
least be made optional/configurable?

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

[frameworks-kio] [Bug 395058] ssh:// link opens konsole with --noclose

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=395058

--- Comment #3 from tony den haan  ---
Aha thanks, that sure makes sense. Yet i'd rather have it drop to local shell,
both after closing ssh sesession and on ssh failure. But i suppose that's not
for this report.

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

[Discover] [Bug 407807] Discover says it is offline when trying to update when NetworkManager is in use but not managing any networks

[tony den haan]

https://bugs.kde.org/show_bug.cgi?id=407807

tony den haan  changed:

   What|Removed |Added

 CC||kdeb...@tuxick.net

--- Comment #13 from tony den haan  ---
What about not using nm and throw an error when things really fail?

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

[kexi] [Bug 372372] New: Kexi crashes when opening PSQL DB

[Tim Van den Langenbergh]

https://bugs.kde.org/show_bug.cgi?id=372372

Bug ID: 372372
   Summary: Kexi crashes when opening PSQL DB
   Product: kexi
   Version: 2.9.11
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: tmt_...@gmx.com
CC: a...@piggz.co.uk, in...@fables.co.za
  Target Milestone: ---

Application: kexi (2.9.11)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I was trying to open a postgresql DB, version 9.4. I'm running OpenSUSE
Tumbleweed and have set up postgresql to use MD5 passwords.

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f34ad557e00 (LWP 30707))]

Thread 3 (Thread 0x7f348354c700 (LWP 30972)):
#0  0x7f34ab3ff6fd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34a78fcb00 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f348354ba20, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7f34a78fcb00 in g_wakeup_acknowledge (wakeup=0x7f34840025a0) at
gwakeup.c:210
#3  0x7f34a78b8325 in g_main_context_check
(context=context@entry=0x7f347c0009a0, max_priority=2147483647,
fds=fds@entry=0x7f347c003010, n_fds=n_fds@entry=1) at gmain.c:3707
#4  0x7f34a78b8814 in g_main_context_iterate
(context=context@entry=0x7f347c0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3926
#5  0x7f34a78b898c in g_main_context_iteration (context=0x7f347c0009a0,
may_block=may_block@entry=1) at gmain.c:3990
#6  0x7f34ab88384e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f347c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x7f34ab851b9f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f348354bc40, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f34ab851f05 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f348354bc40, flags=...) at kernel/qeventloop.cpp:204
#9  0x7f34ab740899 in QThread::exec() (this=this@entry=0x15baf40) at
thread/qthread.cpp:538
#10 0x7f34ab831983 in QInotifyFileSystemWatcherEngine::run()
(this=0x15baf40) at io/qfilesystemwatcher_inotify.cpp:265
#11 0x7f34ab74316a in QThreadPrivate::start(void*) (arg=0x15baf40) at
thread/qthread_unix.cpp:352
#12 0x7f34a87ad454 in start_thread (arg=0x7f348354c700) at
pthread_create.c:333
#13 0x7f34ab40c39f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f3488dbe700 (LWP 30726)):
#0  0x7f34ab40368d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f34a78b8876 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f3484003210, timeout=, context=0x7f34840009a0)
at gmain.c:4228
#2  0x7f34a78b8876 in g_main_context_iterate
(context=context@entry=0x7f34840009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3924
#3  0x7f34a78b898c in g_main_context_iteration (context=0x7f34840009a0,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f34ab88384e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f34840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7f34ab851b9f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f3488dbdc40, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f34ab851f05 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3488dbdc40, flags=...) at kernel/qeventloop.cpp:204
#7  0x7f34ab740899 in QThread::exec() (this=this@entry=0x14a0980) at
thread/qthread.cpp:538
#8  0x7f34ab831983 in QInotifyFileSystemWatcherEngine::run()
(this=0x14a0980) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f34ab74316a in QThreadPrivate::start(void*) (arg=0x14a0980) at
thread/qthread_unix.cpp:352
#10 0x7f34a87ad454 in start_thread (arg=0x7f3488dbe700) at
pthread_create.c:333
#11 0x7f34ab40c39f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f34ad557e00 (LWP 30707)):
[KCrash Handler]
#6  0x7f34ab6bcc68 in main_arena () at /lib64/libc.so.6
#7  0x7f34828f6905 in pqxx::connection_base::activate() () at
/usr/lib64/libpqxx-4.0.so
#8  0x7f34828f8f62 in  () at /usr/lib64/libpqxx-4.0.so
#9  0x7f348291bc20 in pqxx::transaction_base::DirectExec(char const*, int)
() at /usr/lib64/libpqxx-4.0.so
#10 0x7f348290638f in pqxx::nontransaction::do_exec(char const*) () at
/usr/lib64/libpqxx-4.0.so
#11 0x7f348291c966 in
pqxx::transaction_base::exec(std::__cxx11::basic_string, std::allocator > const&,
std::__cxx11::basic_string, std::allocator >
const&) () at /usr/lib64/libpqxx-4.0.so
#12 0x7f3482b423bf in  () at /usr/lib64/kde4/kexidb_pqxxsqldriver.so
#13 0x7f3482b43dca in  () at /usr/lib64/

[kmail2] [Bug 372692] New: kmail crashes in first start in first login on desktop

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=372692

Bug ID: 372692
   Summary: kmail crashes in first start in first login on desktop
   Product: kmail2
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

Application: kmail (5.3.3 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.28 x86_64

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

I logged into a KDE desktop for the first time. Then I started KMail from the
start menu.
KMail showed the crash popup in the popup area. Despite that the dialog for
configuring KMail comes up.

When KMail is started again, exactly the same thing happens.

- Custom settings of the application:

Distro: NixOS

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library
"/nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24/lib/libthread_db.so.1".
To enable execution of this file add
add-auto-load-safe-path
/nix/store/20xjjp6636addc7yfi4h526xwj4pawnl-gcc-5.4.0-lib/lib/libstdc++.so.6.0.21-gdb.py
line to your configuration file "/home/kde/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/kde/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Current thread is 1 (Thread 0x7f264ae55e40 (LWP 6455))]

Thread 23 (Thread 0x7f25df7fe700 (LWP 6739)):
#0  0x7f26667e1eff in pthread_cond_wait@@GLIBC_2.3.2 () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib64/libpthread.so.0
#1  0x7f2661f8f9f0 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#2  0x7f2661f7b9e4 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#3  0x7f2661f7bbaa in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#4  0x7f2661f780a5 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#5  0x7f2663947fdd in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#6  0x7f266394822e in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#7  0x7f2663948369 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#8  0x7f2662487a72 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#9  0x7f2662472945 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#10 0x7f26624a06e6 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#11 0x7f266249ccdd in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#12 0x7f26667dc1f4 in start_thread () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib64/libpthread.so.0
#13 0x7f266a9d812f in clone () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib/libc.so.6

Thread 22 (Thread 0x7f25d700 (LWP 6738)):
#0  0x7f26667e1eff in pthread_cond_wait@@GLIBC_2.3.2 () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib64/libpthread.so.0
#1  0x7f266249f967 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#2  0x7f26624a0020 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#3  0x7f26624a01f0 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#4  0x7f266249ccdd in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#5  0x7f26667dc1f4 in start_thread () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib64/libpthread.so.0
#6  0x7f266a9d812f in clone () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib/libc.so.6

Thread 21 (Thread 0x7f25fcff9700 (LWP 6737)):
#0  0x7f26667e1eff in pthread_cond_wait@@GLIBC_2.3.2 () from
/nix/store/hwbvmr4imiyi5ziq6v2snynr7zf022b5-glibc-2.24/lib64/libpthread.so.0
#1  0x7f26624949d7 in ?? () from
/nix/store/87ykbwm7x4m2is77cajg88qmdqy2mac6-qtwebengine-5.6.1-1/lib/libQt5WebEngineCore.so.5
#2  0x7f2662494ab4 in ?? () from
/nix/stor

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #101 from Jos van den Oever  ---
For me it's fixed since Plasma 5.8.

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

[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=446674

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

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

[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=446674

--- Comment #3 from Jos van den Oever  ---
To support the proposal for fractional scaling, Qt applications need to be able
to change their scaling at runtime.

Scaling of applications is explained in <https://doc.qt.io/qt-5/highdpi.html>
and <https://doc.qt.io/qt-6/highdpi.html>. On Windows, the setting 'Per-Monitor
DPI Aware' seems close to what this proposal needs. The applications gets a
buffer corresponding the the actual pixels on the screen and also a scaling
factor at which the UI should be rendered.

A dynamic scale factor per window would be fantastic. There could be a 'zoom
resize' (shift + drag border) where the aspect ratio and layout would stay the
same, but the fonts and icons got larger or smaller.

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

[kwin] [Bug 450378] New: Per window scaling with shift-drag on window border

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=450378

Bug ID: 450378
   Summary: Per window scaling with shift-drag on window border
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

It would be nice to set a scaling factor per window. No other desktop supports
this but it could be very intuitive, like resizing pictures on a canvas.

Using shift-drag on window borders could be the way to change the scale factor.

Currently resizing windows, changes their layout. UI elements might appear or
get hidden. This can be frustrating. Also, some windows cannot deal with small
resolution screens which makes parts of the window inaccessible. In such cases,
doing shift-drag on the window border to zoom in or out would be a convenient
and intuitive way to adjust the window.

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

[kwin] [Bug 450378] Per window scaling with shift-drag on window border

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=450378

--- Comment #1 from Jos van den Oever  ---
Related issues:

https://bugs.kde.org/show_bug.cgi?id=227284  also request per-window scaling as
an accessibility feature.

https://bugs.kde.org/show_bug.cgi?id=446674 and
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/47 discuss
how fractional scaling would improve crispiness and decrease graphical buffer
size on Wayland.

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

[kwin] [Bug 450378] Per window scaling with shift-drag on window border

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=450378

--- Comment #3 from Jos van den Oever  ---
The linked Wayland protocol issue (47) has suggestions for adding per window
scaling via additions such as `wanted_scale`, `set_client_scale`,
`setting_client_scale`. Since the current method of scaling is blurry and
resource intensive I hope that these additions will be picked up soon.

E.g. if you have a 4k display with 1.25 scaling, the current scaling method on
Wayland would give a 6144x3456 (4k / 1.25 * 2) buffer to a fullscreen
application such as the always-present desktop background. That is a buffer
that is 2.56x as large as a 4k buffer. Not fun. So Wayland has a big incentive
to fix 47.

The proposed additions could be used to implement this scale-by-dragging
feature. Or vice-versa, this feature request could be one more reason to have
those Wayland additions. Scaling windows up and down by dragging makes for
wonderfully visual demo material besides simply being very handy.

Perhaps it's easier to first implement it on X11.

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

[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=425131

--- Comment #9 from Jos van den Oever  ---
The issue happened again on two machines. Removing the files
`~/.local/share/akonadi/db_data/ib_logfile*` solved the issue.

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

[neon] [Bug 482283] New: Installation in VM gives an error: "Bad main script file"

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482283

Bug ID: 482283
   Summary: Installation in VM gives an error: "Bad main script
file"
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: j...@vandenoever.info
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

Running neon-user-20240303-0009.iso in a QEmu VM on a x86_64 laptop fails
during installation.


STEPS TO REPRODUCE
1. download neon-user-20240303-0009.iso from neon.kde.org
2. boot the iso in a vm
3. start "Install system"
4 choose timezone Amsterdam, English language, Dutch locale
5. choose to erase the entire disk (55GB)
6. continue to the installation and show the logs
6.1 disk is being partitioned
6.2 rsync is run to copy files

OBSERVED RESULT

A dialog pops up: "Main script file
/usr/lib/x86_64-linux-gnu/calamares/modules/networkcfg/main.py for python job
networkcfg raised an exception.

The network in the VM is a wired connection. Browsing the web with Firefox
works from the live image.

EXPECTED RESULT

The installation of KDE Neon completes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482283

--- Comment #1 from Jos van den Oever  ---
In /tmp there are a number of calamares-* diretories. All of them are empty.
Only one is very large: calamares-root-*. No log could be found.

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

[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482283

--- Comment #3 from Jos van den Oever  ---
I confirm that my error looked that same as in Sharath's screenshot.

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

[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482283

Jos van den Oever  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Jos van den Oever  ---
I confirm that installation with neon-user-20240304-2101.iso works without
issue. The installer finishes and boots into Plasma 6.

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

[neon] [Bug 482488] New: 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482488

Bug ID: 482488
   Summary: 'Get $application... buttons in launcher give error:
"Unable to create KIO worker: Unknown protocol
'appstream'."
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: j...@vandenoever.info
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

Installing an application from the launch menu does not work. An error dialog
is shown.


STEPS TO REPRODUCE
1. Install Neon from neon-user-20240304-2101.iso
2. Log into Plasma 6
3. In the application laucher type an application name e.g. 'Libreoffice Calc'
and click on 'Get LibreOffice Calc...'

OBSERVED RESULT

A dialog is shown with the text Unable to create KIO worker: Unknown protocol
'appstream'. and only an 'Ok' button.

EXPECTED RESULT

The desired application is installed or a window is shown from where the
application can be installed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.0.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[neon] [Bug 482488] 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482488

--- Comment #1 from Jos van den Oever  ---
Created attachment 166435
  --> https://bugs.kde.org/attachment.cgi?id=166435&action=edit
screenshot of the trigger and the dialog

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

[neon] [Bug 482488] 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=482488

--- Comment #2 from Jos van den Oever  ---
Discover is installed and it is possible to install applications with it.

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

[plasmashell] [Bug 487905] Launching Elisa via GUI method (KRunner, Kickoff, Task Manager) fails with DBus error

[Stephan van den Akker]

https://bugs.kde.org/show_bug.cgi?id=487905

Stephan van den Akker  changed:

   What|Removed |Added

 CC||memelink.ak...@planet.nl

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

[plasmashell] [Bug 483434] New: Plasma crashed around lock screen

[Tim Van den Langenbergh]

https://bugs.kde.org/show_bug.cgi?id=483434

Bug ID: 483434
   Summary: Plasma crashed around lock screen
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: tmt_...@gmx.com
  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:
I had locked the session, was out for about half an hour and when I returned
and unlocked the 'plasma shell has crashed' dialog was waiting for me.

The reporter is unsure if this crash is reproducible.

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


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 38924]
[New LWP 39140]
[New LWP 39126]
[New LWP 38931]
[New LWP 38951]
[New LWP 38959]
[New LWP 38946]
[New LWP 38945]
[New LWP 39128]
[New LWP 39138]
[New LWP 41236]
[New LWP 39124]
[New LWP 39321]
[New LWP 38957]
[New LWP 39142]
[New LWP 39009]
[New LWP 39320]
[New LWP 41784]
[New LWP 39343]
[New LWP 39353]
[New LWP 39345]
[New LWP 39341]
[New LWP 39117]
[New LWP 39324]
[New LWP 44145]
[New LWP 41238]
[New LWP 41786]
[New LWP 39422]
[New LWP 39421]
[New LWP 41240]
[New LWP 39125]
[New LWP 44159]
[New LWP 38958]
[New LWP 39423]
[New LWP 44147]
[New LWP 44161]
[New LWP 39127]
[New LWP 39344]
[New LWP 39351]
[New LWP 41300]
[New LWP 44160]
[New LWP 39342]
[New LWP 39420]
[New LWP 41301]
[New LWP 41783]
[New LWP 41302]
[New LWP 41785]
[New LWP 41237]
[New LWP 41782]
[New LWP 41303]
[New LWP 44146]
[New LWP 38950]
[New LWP 41239]
[New LWP 39139]
[New LWP 41304]
[New LWP 44148]
[New LWP 39141]
[New LWP 44162]
[New LWP 44149]
[New LWP 39350]
[New LWP 38956]
[New LWP 44163]
[New LWP 39352]
[New LWP 39354]
[New LWP 39419]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x71be972ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x71be9161d9c0 (LWP 38924))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x71be9161d9c0 (LWP 38924))]

Thread 65 (Thread 0x71bdeea006c0 (LWP 39419)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be966a3c10 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x71be97dc084b in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x71be966a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#6  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 64 (Thread 0x71bdf96006c0 (LWP 39354)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 63 (Thread 0x71bdfaa006c0 (LWP 39352)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 62 (Thread 0x71bdb16006c0 (LWP 44163)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 61 (Thread 0x71be82a006c0 (LWP 38956)):
#0  0x71be972a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x71be972a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x71be685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x71be8889e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x71be972a955a in ??? () at /usr/lib/libc.so.6
#5  0x71be97326a3c in ??? () at /usr/lib/libc.so.6

Thread 60 (Thread 0x71bdfbe006c0 (LWP 39350)):
#0  0x71be972a5ebe 

[plasmashell] [Bug 483434] Plasma crashed around lock screen

[Tim Van den Langenbergh]

https://bugs.kde.org/show_bug.cgi?id=483434

--- Comment #2 from Tim Van den Langenbergh  ---
"Nate Graham"  writes:

> https://bugs.kde.org/show_bug.cgi?id=483434
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
>  CC||n...@kde.org
>  Resolution|--- |BACKTRACE
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #1 from Nate Graham  ---
> Cannot reproduce, no KDE code is implicated in what I can see from the
> backtrace, and the backtrace has no debug symbols for anything that would 
> help.
> :(
>
> If this crash is reproducible, could you please install debug symbols,
> reproduce the crash, and attach a new symbolicated backtrace? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
>
> Thanks!

Got it, I'll install debug symbols and if I get a crash that looks similar
(though hopefully that won't happen), I'll try to remember to add to this
issue.

Actually, mightn't it be better to close this issue and just have me open a new
one if something similar happens again? That way you won't have an open mystery
issue that may never be solvable due to lack of information.

Sorry for the unhelpful backtrace, the crash reporting program said it 'may be
helpful', but I guess it wasn't.

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

[rust-qt-binding-generator] [Bug 445878] Support generating and emitting custom signals

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=445878

--- Comment #1 from Jos van den Oever  ---
You can currently emit signals by modifying properties. So the machinery for
emitting signals is there. If I understand correctly, you would like to have a
way to specify signals in the bindings json file that generates rust functions
for emitting other signals.

When signals are tied to properties, it's convenient in QML to tie the state to
something in the UI. For signals that are not tied to any property, the update
would only have temporary information. To use that information later, you'd
then need to store that information in a QML property.

Can you explain your use-case?

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

[rust-qt-binding-generator] [Bug 445879] Support some of the built-in Qt types, when exposing them to Rust

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=445879

Jos van den Oever  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #1 from Jos van den Oever  ---
Calling QML code from Rust is out of scope. The design of RQBG is such that you
can crate a data model in Rust, but the Rust does not know about the QML code.
You can trigger functions in the QML by binding to property states. Calling QML
from Rust is out of scope for the current design. However, if you have ideas
for doing this is in a safe and simple way, I might add it.

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

[kwin] [Bug 452492] New: external screen brightness is not restored after wakeup

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=452492

Bug ID: 452492
   Summary: external screen brightness is not restored after
wakeup
   Product: kwin
   Version: 5.24.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---
 Flags: Wayland+, Intel+

SUMMARY
***
When the external monitor is set to turn off after a certain time of no
activity, the brightness is not fully restored after wakeup. The brightness can
be fixed with the the keyboard brightness buttons or with `ddcutil setvsp 10 +
65535`.
***


STEPS TO REPRODUCE
1.  run wayland session with dbus-run-session startplasma-wayland
2. set 'Screen energy savings' to 'Switch off after 3 min', press 'Apply'
3. wait 3 minutes until screen turns off
4. awaken screen by doing user input on keyboard

OBSERVED RESULT

The external monitor is on lowest brightness setting.

EXPECTED RESULT

The external monitor is on the same brightness as before it went to sleep.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Linux Kernel: 5.15.30
Graphics platform: Wayland

ADDITIONAL INFORMATION
The graphics is embedded Intel graphics UHD Graphics 620. The monitor is LG
connected via USB-C for display and power to the laptop. The laptop screen and
the external monitor are active. Only the laptop monitor is restored to the
initial brightness.

Related bug: https://bugs.kde.org/show_bug.cgi?id=423457

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

[kwin] [Bug 452492] external screen brightness is not restored after wakeup

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=452492

--- Comment #1 from Jos van den Oever  ---
The monitor is visible like this:
```
$ ddcutil detect
Display 1
   I2C bus:  /dev/i2c-9
   EDID synopsis:
  Mfg id:   GSM
  Model:LG HDR 4K
  Product code: 30471
  Serial number:
  Binary serial number: [..]
  Manufacture year: [..]
   VCP version: 2.1
```

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

[systemsettings] [Bug 455713] New: slider for feedback level does not fit on screen

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=455713

Bug ID: 455713
   Summary: slider for feedback level does not fit on screen
   Product: systemsettings
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_feedback
  Assignee: aleix...@kde.org
  Reporter: j...@vandenoever.info
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 150004
  --> https://bugs.kde.org/attachment.cgi?id=150004&action=edit
screenshot of the User Feedback screen in System Settings

SUMMARY

The slider for the level of user feedback reporting does not fit on the screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: PostmarketOS edge
Device: Pinephone
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

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

[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=425131

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #8 from Jos van den Oever  ---
This bug has happened on a laptop I maintain as well. The file
`~/.local/share/akonadi/db_data/mysql.err` reported that InnoDB missed
MLOG_CHECKPOINT between another checkpoint and the end. The database would not
start because of this. The user had no feedback. All they could see was a
message in KMail that akonadi would not start.

Removing the files `~/.local/share/akonadi/db_data/ib_logfile*` solved the
issue.

Perhaps a solution might be to let akonadictl make a backup of the db_data
directory and then remove the ib_logfiles and retry starting up.

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

[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=206269

--- Comment #5 from Jos van den Oever  ---
This bug is still present in KMail version 5.16.3 (20.12.3)

I tested with the command from Comment 3.
https://bugs.kde.org/show_bug.cgi?id=206269#c3

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

[kmail2] [Bug 206269] mailto links only read up to first hash (#) symbol

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=206269

Jos van den Oever  changed:

   What|Removed |Added

Product|konqueror   |kmail2
Version|SVN |5.16.3
   Assignee|konq-b...@kde.org   |kdepim-b...@kde.org
  Component|khtml   |general

--- Comment #6 from Jos van den Oever  ---
Assigning back to KMail because a comment points out that the bug is there with
an easy way to reproduce the problem.

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

[kmail2] [Bug 401050] kmail mailto invokation fails if akonadi is loaded

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=401050

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #1 from Jos van den Oever  ---
On NixOS 20.09 with KMail version 5.16.3 (20.12.3) this bug is not present.

The compose window opens when running
   kmail -qwindowtitle KMail mailto:847...@bugs.debian.org
even when kmail and akonadi were not running.

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

[kwin] [Bug 471819] kwin hangs when there is no render node e.g. in qemu

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=471819

--- Comment #2 from Jos van den Oever  ---
I tried again today with kwin_wayland for kf5 and kf6 compiled from today's git
repositories.

weston works fine in the same setup, but kwin_wayland from kf5 gives this
output:

```
No backend specified, automatically choosing drm
pci id for fd 19: 1234:, driver (null)
MESA-LOADER: failed to open bochs-drm:
/run/opengl-driver/lib/dri/bochs-drm_dri.so: cannot open shared object file: No
such file or directory (search paths /run/opengl-driver/lib/dri, suffix _dri)
pci id for fd 17: 1234:, driver (null)
kmsro: driver missing
OpenGL vendor string:   Mesa
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL version string:  4.5 (Core Profile) Mesa 23.0.3
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   23.0.3
Linux kernel version:   6.1.31
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_wayland_drm: Failed to create gamma blob! Invalid argument
```

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

[plasmashell] [Bug 471969] System Tray applet is not automatically closing on focus loss

[Peter van den Houten]

https://bugs.kde.org/show_bug.cgi?id=471969

--- Comment #2 from Peter van den Houten  ---
The problem was solved by deleting the default bottom panel and re-creating it.

To answer your questions:

1) Have not tried in a Wayland session; will change if the problem re-occurs.
2) Just a laptop screen or with external screen, makes no difference.
3) No - all defaults
4) No - all defaults
5) No - all defaults

Thanks
Peter


On 13/09/2023 20:21, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=471969
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>  Summary|System Tray applet is not   |System Tray applet is not
> |automatically minimizing|automatically closing on
> ||focus loss
>   CC||n...@kde.org
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #1 from Nate Graham  ---
> That's very strange. Some questions for debugging purposes:
> 1. Does it happen in the Wayland session too, or only on X11?
> 2. How many screens do you have connected when this happens?
> 3. Are you using a non-default window activation policy (e.g. focus follows
> mouse)?
> 4. Are you using any 3rd-party themes, scripts, or KWin effects?
> 5. Are you using any window rules?
>

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

[konsole] [Bug 475555] New: ALT-B can not be disable in keyboard-shortcuts.

[Martin van den Broek]

https://bugs.kde.org/show_bug.cgi?id=47

Bug ID: 47
   Summary: ALT-B can not be disable in keyboard-shortcuts.
Classification: Applications
   Product: konsole
   Version: 23.08.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: mbroek2...@gmail.com
  Target Milestone: ---

SUMMARY

When using a GNU Bash shell in a Konsole tab in a window that contains multiple
tabs I noticed that ALT-B is triggering the Konsole bookmark menu to open
whereas I expect my cursor to move backward one single word on my shell because
ALT-B is a common GNU Readline Library shortcut that moves the cursor backward
one word.

In a single console window without tabs the ALT-B respects the GNU Readline
Library keyboard shortcuts that are used by the GNU Bash shell. But once you
have multiple tabs open is does not. It looks like the Konsole application is
interfering with the GNU Readline shortcuts that GNU Bash is using without an
option to disable the ALT-B in the keyboard-shortcut options of the Konsole
application.

More info on GNU Readline Library can be found here:

https://tiswww.case.edu/php/chet/readline/readline.html#Readline-Movement-Commands

STEPS TO REPRODUCE
1. Open Konsole
2. Open at least 2 tabs
3. start a GNU Bash shell and and a dummy command consisting of multiple words,
e.g. "echo this && echo that"
4. Issue ALT-B

OBSERVED RESULT

1. Bookmark menu of Konsole application opens.

EXPECTED RESULT

1. Cursor should move backward one word on the shell.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20231006
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.4-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

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

[konsole] [Bug 475555] ALT-B can not be disable in keyboard-shortcuts.

[Martin van den Broek]

https://bugs.kde.org/show_bug.cgi?id=47

Martin van den Broek  changed:

   What|Removed |Added

 CC||mbroek2...@gmail.com

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

[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=409587

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #7 from Jos van den Oever  ---
I can confirm this issue. I happens every time when elisa is run.

```
Inotify Watch Capacity Low

Your open applications want to watch too many files for changes! When the
capacity is exhausted it will prevent further file monitoring from working
correctly. Either close some applications or increase the limit. Currently
using 25% of instances and 98% of watches.

Increase Watch Limit
```

Increasing the limit via the dialog (see attachments) helps to solve the
problem. With `inotify-consumers` it is possible to list the applications that
use inotify. Elisa uses over 100k monitors and the number keeps increasing.

```
$ bash /tmp/inotify-consumers 

   INOTIFY   INSTANCES
   WATCHES  PER   
COUNT PROCESS   PID USER COMMAND

  115295 5 2102749 nlnet  
/nix/store/3wvgmnm5rkqii79arggmvnda25ahqwcq-elisa-23.04.1/bin/elisa
 202 1 1954876 nlnet   /run/current-system/sw/bin/kded5
 126 2 1954922 nlnet  
/nix/store/d5dv3b5r919hvknf248xvw6rwa5ggbf1-plasma-workspace-5.27.5/bin/plasmashell
 117 3 1955567 nlnet  
/nix/store/3igqa8akmyswkanm6vpk11if4fiqrji8-firefox-113.0.2/bin/.firefox-wrapped
--name firefox
 114 1 1955198 nlnet  
/nix/store/cm63hmpc7976x74f344bbg7pa7grj0i6-thunderbird-102.10.1/bin/.thunderbird-wrapped
--name thunderbird
  19 1 2065953 nlnet  
/nix/store/0wyqlfsi1gpnqbvy9pkmlbz91vbly65r-rust-analyzer-unwrapped-2022-10-31/bin/rust-analyzer
  18 3  392486 nlnet  
/nix/store/75wxj2a3c0pdbf46bzmff8qr9vbjm5y1-systemd-253.3/lib/systemd/systemd
--user
   8 1  392718 nlnet  
/nix/store/w2rxmc5wqlw28r23rrsvl1qwxq3qlhra-dbus-1.14.6/bin/dbus-daemon
--session --address=systemd: --nofork --nopidfile
   8 1 1954664 nlnet   dbus-daemon --nofork --print-address
4 --session
   4 1 1954967 nlnet  
/nix/store/pil9rmdpn1j73j21bbcx60pgcanv30zh-kactivitymanagerd-5.27.5/libexec/kactivitymanagerd
   3 3 1945296 nlnet  
/nix/store/3a566gibjcsrmi0pbdndqpfdpv37wh6a-wireplumber-0.4.14/bin/wireplumber
   2 2  410389 nlnet   gpg-agent --homedir
/home/nlnet/.gnupg --use-standard-socket --daemon
   2 1 1954928 nlnet  
/nix/store/2nhjxk2jcxp6z64iv9r1yxpbafajpjc7-powerdevil-5.27.5/libexec/org_kde_powerdevil
   1 1 2037433 nlnet   /home/nlnet/.nix-profile/bin/konsole
   1 1 2035949 nlnet  
/nix/store/v7qc7q2w1ji5v0a4gyrh36bm1vxqqvz0-kwallet-5.106.0-bin/bin/kwalletd5
   1 1 1954954 nlnet  
/run/current-system/sw/bin/gmenudbusmenuproxy
   1 1 1954704 nlnet  
/nix/store/dvwkf9i5vyffqs6bn001ili2f94nrqx8-xdg-desktop-portal-1.16.0/libexec/xdg-desktop-portal

  115922  WATCHES TOTAL COUNT

INotify instances per user (e.g. limits specified by
fs.inotify.max_user_instances): 

INSTANCESUSER
---  --
29   nlnet
```

Elisa uses 100% CPU while setting all these watches. After running for a few
minutes, the watch capacity needs to be increased again. At this point the
number of watches is 123674. Increasing the limit more does not create more
watches. The limit is at 124304 (`cat /proc/sys/fs/inotify/max_user_watches`).
Since elisa has taken all the available inotify watches, other applications
cannot set any watches.

Closing elisa frees up the watches.

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

[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=409587

--- Comment #8 from Jos van den Oever  ---
Created attachment 159800
  --> https://bugs.kde.org/attachment.cgi?id=159800&action=edit
popup about the need for more watches

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

[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=409587

--- Comment #9 from Jos van den Oever  ---
Created attachment 159801
  --> https://bugs.kde.org/attachment.cgi?id=159801&action=edit
Dialog for increasing the number of watches

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

[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=409587

--- Comment #10 from Jos van den Oever  ---
Created attachment 159802
  --> https://bugs.kde.org/attachment.cgi?id=159802&action=edit
Script to show the number of watches per application

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

[kwin] [Bug 471819] New: kwin hangs when there is no render node e.g. in qemu

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=471819

Bug ID: 471819
   Summary: kwin hangs when there is no render node e.g. in qemu
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

SUMMARY

When there is no render node in kwin_wayland, no rendering is done. In QEmu,
when no opengl is available the rendering falls back to a primary node:
`kwin_scene_opengl: No render nodes have been found, falling back to primary
node`
kwin continues executing, but freezes at some point without rendering anything.

A solution might be to have an early check for that and automatically fall back
to CPU rendering if there are not any render nodes.

STEPS TO REPRODUCE
1. install kwin in a qemu image and 
2. start kwin

OBSERVED RESULT

kwin hangs without showing any input. 

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: master kwin: b23d707e0cc12156b0eb9613bb791365d1217f25
(available in About System)
KDE Plasma Version:  master
KDE Frameworks Version: master
Qt Version: 6.5

ADDITIONAL INFORMATION

I ran this in qemu with

```
nixos-rebuild build-vm --flake
'git+https://invent.kde.org/vandenoever/kde-nix-flake/?ref=kf6-qt6&rev=44a978ee14f0f776113369780dca10fecd7d3629#test-x86_64-linux'
result/bin/run-nixos-vm
```
This boots a qemu with a recent (~2023-06-20) git version of KDE software.

When booted, kwin_wayland is started from a user account (user tester, pwd
test)
```
qt.dbus.integration: Could not connect "org.freedesktop.login1.Session" to
handleResumeDevice(uint, uint, QDBusUnixFileDescriptor)
pci id for fd 17: 1234:, driver (null)
MESA-LOADER: failed to open bochs-drm:
/run/opengl-driver/lib/dri/bochs-drm_dri.so: cannot open shared object file: No
such file or directory (search paths /run/opengl-driver/lib/dri, suffix _dri)
pci id for fd 18: 1234:, driver (null)
kmsro: driver missing
OpenGL vendor string:   Mesa
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL version string:  4.5 (Core Profile) Mesa 23.0.3
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   23.0.3
Linux kernel version:   6.1.31
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_scene_opengl: No render nodes have been found, falling back to primary
node
kwin_core: kwin-dmabuf-feedback-table: mmap failed: Invalid argument
kwin_core: Failed to create RamFile for LinuxDmaBufV1FormatTable
kwin_wayland_drm: DPMS has unrecognized enum 'On'
kwin_wayland_drm: DPMS has unrecognized enum 'Standby'
kwin_wayland_drm: DPMS has unrecognized enum 'Suspend'
kwin_wayland_drm: DPMS has unrecognized enum 'Off'
gbm_bo_get_fd_for_plane() failed: Function not implemented
kwin_wayland_drm: Checking test buffer failed for (1)
kwin_wayland_drm: Failed to find a working setup for new outputs!
gbm_bo_get_fd_for_plane() failed: Function not implemented
kwin_wayland_drm: Checking test buffer failed for (1)
kwin_core: Applying output config failed!
kf.coreaddons: The plugin
"/nix/store/zdmvxgsb36biv1lrs4jg13vvyzs6lvac-kwin-6-20230626gitb23d707/lib/qt-6/plugins/kwin/plugins/StickyKeysPlugin.so"
explicitly states an Id in the embedded metadata, which is different from the
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
error marshalling arguments for format_table: dup failed: Bad file descriptor
error in client communication (pid 1201)
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kf.package: Invalid metadata for package structure "Plasma/Wallpaper"
kf.package: Invalid metadata for package structure "Plasma/LookAndFeel"
kscreenlocker_greet: Lockscreen QML outdated, falling back to default
kf.package: Cannot set a path in a package without structure
"org.kde.breeze.desktop"
kf.package: Cannot set a path in a package without structure "org.kde.image"
```

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

[plasmashell] [Bug 471969] New: System Tray applet is not automatically minimizing

[Peter van den Houten]

https://bugs.kde.org/show_bug.cgi?id=471969

Bug ID: 471969
   Summary: System Tray applet is not automatically minimizing
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: peter...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY

The System Tray applet is not automatically minimizing after being clicked on
and popping up. After any applet entry has been clicked on, the entry will pop
up and display the relevant information, e.g. Networks will show the network
information, Disks & Devices will show the attached drives.

The applet works OK but when finished viewing the information and clicking on
the desktop or whatever program is running, the applet does not minimize back
top the tray automatically - it used to, then something happened and it no
longer functions correctly. Now, one has to click on the applet entry once
again to minimize to the tray, otherwise it will stay on the screen.

STEPS TO REPRODUCE
1. Click on system tray applet (any entry)
2. Entry selected pops up correctly
3. Click on desktop, menu, running program, or anywhere else.

OBSERVED RESULT

System tray applet does not minimize after clicking elsewhere, only when
clicking on applet entry again.

EXPECTED RESULT

System tray applet should minimize to tray when user has clicked elsewhere.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Debian GNU/Linux 12 - kernel 6.1.0-9-amd64 (64-bit)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz
Memory: 16 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000

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

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=448087

Jos van den Oever  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Jos van den Oever  ---
I agree with the analysis. This is a fundamental problem that I did not realize
before.

One can get rid of the undefined behavior by changing all '&mut self' to
'&self' in the interface and leave the problem for the implementer. (This is
also what kdebuac.rhn  describes in https://bugs.kde.org/show_bug.cgi?id=406178
)

They might then use a Mutex. That would then lead to a deadlock instead of
undefined behavior.

The idea of a QueuedConnection would not solve the problem general problem. One
would need to guarantee that any code that calls into C++ does not call back in
Rust. The only safe way is to have only immutable references.

The read-only experimental branch might be the solution:
https://gitlab.com/rhn/rust-qt-bindings-generator/-/commits/simplify_ro

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

[rust-qt-binding-generator] [Bug 406178] Mutability of Rust objects

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=406178

Jos van den Oever  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Jos van den Oever  ---
Your analysis is correct. Going to '&self' instead of '&self mut' is the way to
go. Do you want to make a merge request from your ro branch?

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

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=448087

--- Comment #5 from Jos van den Oever  ---
That all seems a sensible. The code was originally written when I was less
familiar with rust's rules. The rust_by_function as the only way to get data is
more verbose in implementation.rs and might have performance overhead, but the
binding to a GUI is not the place to worry about that.

What would the RefCell code look like? I'm asking because I'm modifying a model
from multiple threads, so a Mutex might be more appropriate.

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

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=448087

--- Comment #9 from Jos van den Oever  ---
Yes, the resulting master should be as much functional as the current one. I'll
have a look this week to see what the means. I've two projects I'd like to test
with these changes, one public (mailmodel) and one private.

Commit squashing is not something I've a strong opinion on.

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

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=448087

--- Comment #10 from Jos van den Oever  ---
And yes to 0.4.0 in case of merge indeed.

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

[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=206269

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #3 from Jos van den Oever  ---
An escaping problem also occurs with '&' in subject or body.

kmail 'mailto:t...@example.com?subject=A%26B&body=D%26C'

gives

Subject: A
Body: D&c=

but it should be:

Subject: A&B
Body: D&C

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

[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=206269

--- Comment #4 from Jos van den Oever  ---
This happens in KMail Version 5.15.2 (20.08.2)

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

[kmail2] [Bug 406261] Kmail2 crashes when accepting meeting invitation

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=406261

Jos van den Oever  changed:

   What|Removed |Added

 CC||j...@vandenoever.info

--- Comment #1 from Jos van den Oever  ---
I can confirm this crash with KMail version 5.15.2 (20.08.2)


#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7fab13207528 in __GI_abort () at abort.c:79
#2  0x7fab135a1693 in ?? ()
   from
/nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6
#3  0x7fab135acf06 in ?? ()
   from
/nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6
#4  0x7fab135acf71 in std::terminate() ()
   from
/nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6
#5  0x7fab135ad1c4 in __cxa_throw ()
   from
/nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6
#6  0x7fab115b6ebd in Akonadi::Item::throwPayloadException(int, int) const
[clone .cold] ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#7  0x7fab11636b7f in
std::enable_if::isPolymorphic,
QByteArray>::type Akonadi::Item::payloadImpl() const ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#8  0x7fab11634fc9 in non-virtual thunk to
Akonadi::DefaultItemSerializerPlugin::serialize(Akonadi::Item const&,
QByteArray const&, QIODevice&, int&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#9  0x7fab1163483b in Akonadi::ItemSerializer::serialize(Akonadi::Item
const&, QByteArray const&, QIODevice&, int&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#10 0x7fab11635409 in Akonadi::ItemSerializer::serialize(Akonadi::Item
const&, QByteArray const&, QByteArray&, int&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#11 0x7fab116b8460 in Akonadi::ItemCreateJobPrivate::preparePart(QByteArray
const&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#12 0x7fab116b88f0 in Akonadi::ItemCreateJob::doHandleResponse(long long,
QSharedPointer const&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#13 0x7fab116c9430 in Akonadi::JobPrivate::handleResponse(long long,
QSharedPointer const&) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#14 0x7fab11681f10 in Akonadi::SessionPrivate::handleCommands() ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#15 0x7fab1167eb60 in Akonadi::Session::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
   from
/nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5
#16 0x7fab139cec99 in QObject::event(QEvent*) ()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5
#17 0x7fab146bed7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Widgets.so.5
#18 0x7fab146c7a10 in QApplication::notify(QObject*, QEvent*) ()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Widgets.so.5
#19 0x7fab139a1d8a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5
#20 0x7fab139a46b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5
#21 0x7fab139fb713 in ?? ()
   from
/nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core

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

[kmail2] [Bug 406261] Kmail2 crashes when accepting meeting invitation

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=406261

Jos van den Oever  changed:

   What|Removed |Added

Version|5.10.3  |5.15.2

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

[rust-qt-binding-generator] [Bug 423280] rust-qt-binding-generator templates fail to build with mingw64

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=423280

--- Comment #2 from Jos van den Oever  ---
If you have a patch, I can consider it. I do not have a windows system to test
on.

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

[konqueror] [Bug 190698] rotating svg cube (javascript) does not work in konqueror

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=190698

Jos van den Oever  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Jos van den Oever  ---
This now works with konqueror 20.08.2.

qsvgviewer is not packaged by my distribution any more.

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

[gcompris] [Bug 435006] New: gcompris snap 1.1 fails to load on ubuntu 20.04

[Sam Van den Eynde]

https://bugs.kde.org/show_bug.cgi?id=435006

Bug ID: 435006
   Summary: gcompris snap 1.1 fails to load on ubuntu 20.04
   Product: gcompris
   Version: unspecified
  Platform: Snap
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: jaz...@gmail.com
  Reporter: samvde+samvde-accounts-...@posteo.net
  Target Milestone: ---

SUMMARY

When trying to load gcompris on an Ubuntu 20.04 laptop, the follow
unrecoverable error occurs:

"gcompris-qt: error while loading shared libraries: libpulsecommon-13.99.so:
cannot open shared object file: No such file or directory"

I recerted the snap, the previous version works fine.

STEPS TO REPRODUCE
1. await automatic snap update to gcompris v1.1
2. start gcompris from a shell
3. observe error message

OBSERVED RESULT
gcompris-qt: error while loading shared libraries: libpulsecommon-13.99.so:
cannot open shared object file: No such file or directory

EXPECTED RESULT
gcompris starting

SOFTWARE/OS VERSIONS
Windows: 
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.

[gcompris] [Bug 435006] gcompris snap 1.1 fails to load on ubuntu 20.04

[Sam Van den Eynde]

https://bugs.kde.org/show_bug.cgi?id=435006

--- Comment #1 from Sam Van den Eynde  
---
So just in case this info is needed: this is stock Ubuntu 20.04 with Gnome DE.

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

[gcompris] [Bug 435006] gcompris snap 1.1 fails to load on ubuntu 20.04

[Sam Van den Eynde]

https://bugs.kde.org/show_bug.cgi?id=435006

--- Comment #5 from Sam Van den Eynde  
---
Hi

Unfortunately I can no longer troubleshoot this: I refreshed the snap back to
the newest version (after reverting it this morning) to add info to the bug
report but apparently this action made it work again. I have no idea why this
sort of reinstallation fixed it.

FYI I do have it installed as a snap and libpulse0 is installed. I just invoked
it from the command line to troubleshoot why the new version would not start
anymore, which spawned the error I mention. I also rebooted the machine to test
and used a previous kernel as well, all with no effect. I did not update the
system itself.

Many thanks for this very quick response.

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

[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=395192

Jos van den Oever  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

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

[konsole] [Bug 462105] New: copy from the history with keyboard

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=462105

Bug ID: 462105
   Summary: copy from the history with keyboard
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: history
  Assignee: konsole-de...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

Konsole has a history. A very common action is to select text with the mouse
and copy it into a new command or command-line application.

The applications screen and emacs offer ways to select text from the terminal
history with the keyboard instead of the mouse. It would be great to have
selection mode where a user can select a line, work or file path with just the
keyboard.

Version 22.08.3 of Konsole does not have such a feature.

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

[rust-qt-binding-generator] [Bug 400393] When using cargo for compilation, the C++ standard lib is incorrect on Windows when linking but not compiling.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400393

Jos van den Oever  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/rus
   ||t-qt-binding-generator/89c8
   ||6642f8e39c1906da72333b431e7
   ||2ba8dc268
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Jos van den Oever  ---
Git commit 89c86642f8e39c1906da72333b431e72ba8dc268 by Jos van den Oever.
Committed on 28/10/2018 at 21:05.
Pushed by vandenoever into branch 'master'.

Print the c++ library that cargo should link against

This is used when calling "cargo build" when no actual recompile is needed.

M  +19   -1src/build.rs

https://commits.kde.org/rust-qt-binding-generator/89c86642f8e39c1906da72333b431e72ba8dc268

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

[rust-qt-binding-generator] [Bug 400393] When using cargo for compilation, the C++ standard lib is incorrect on Windows when linking but not compiling.

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400393

--- Comment #2 from Jos van den Oever  ---
Thank you for the bug report and pointer.

Commit 89c86642f8e39c1906da72333b431e72ba8dc268 should fix it.

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

[rust-qt-binding-generator] [Bug 400480] cargo --verbose install qrep fails on Kubuntu 18.04

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400480

--- Comment #1 from Jos van den Oever  ---
Can you run

qmake -query QT_VERSION

and report the output?

Does

 /usr/lib/x86_64-linux-gnu/qt4/bin/qmake

exist?

It seems that you might have qmake from Qt4 installed. 

Which version of Qt do you have installed?

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

[plasmashell] [Bug 406535] New: plasmashell crashing with freebsd, with kill Xorg and sddm again....

[Miranda van den Breukelingen]

https://bugs.kde.org/show_bug.cgi?id=406535

Bug ID: 406535
   Summary: plasmashell crashing with freebsd, with kill Xorg and
sddm again
   Product: plasmashell
   Version: master
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: vanbreukelingen1...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 119411
  --> https://bugs.kde.org/attachment.cgi?id=119411&action=edit
Log file with backtrace being to long for the assistent...

Dr. Konqi crashes often when reporting bugs...

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

[plasmashell] [Bug 406535] plasmashell crashing with freebsd, with kill Xorg and sddm again....

[Miranda van den Breukelingen]

https://bugs.kde.org/show_bug.cgi?id=406535

--- Comment #2 from Miranda van den Breukelingen 
 ---
It's plasma5 5.15.3_x and Qt 5.12.1

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

[kwin] [Bug 406829] New: kwin_x11 crashes on alt-tab

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=406829

Bug ID: 406829
   Summary: kwin_x11 crashes on alt-tab
   Product: kwin
   Version: 5.15.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

SUMMARY

kwin_x11 crashes when the pressing alt-tab. Doing one alt-tab quickly,
releasing both buttons fast, is fine. Holding alt and just clicking tab causes
a crash.

STEPS TO REPRODUCE
1. Log in to Plasma
2. Open a few applications
3. Hold Alt and click tab.

OBSERVED RESULT

kwin_x11 crashes (and restarts immediately).


EXPECTED RESULT

No crash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION

Distribution: Nixos 19.04

I'm updating the KDE packages for the distribution and testing their stability.

$ valgrind kwin_x11 --replace
==26137== Memcheck, a memory error detector
==26137== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==26137== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==26137== Command: kwin_x11 --replace
==26137== 
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
--26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
==26137== Warning: set address range perms: large range [0x59c92000,
0xd9c92000) (defined)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2707, resource
id: 115343413, major code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2708,
resource id: 115343413, major code: 14 (GetGeometry), minor code: 0
==26137== Thread 5 QQmlThread:
==26137== I

[kmail2] [Bug 407163] New: compilation fails due to wrong include statement

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=407163

Bug ID: 407163
   Summary: compilation fails due to wrong include statement
   Product: kmail2
   Version: 5.11.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

SUMMARY

include/KF5/mailcommon/backupjob.h contains this include statement:

#include "libkdepim/progressmanager.h"

When compiling KMail 5.11 on NixOS 19.03, this compilation error is given:

/nix/store/zikg7mfgx01isvw6qzi969f1a1yhr7m3-mailcommon-19.04.0-dev/include/KF5/mailcommon/backupjob.h:25:10:
fatal error: libkdepim/progressmanager.h: No such file or directory
 #include "libkdepim/progressmanager.h"

that is because the directory .../include/KF5/libkdepim is given in
KF5LibkdepimTargets.cmake, but not the parent directory .../include/KF5.

There are two solutions:

 1) adapt backupjob.h
 2) adapt KF5LibkdepimTargets.cmake

I'm compiling this on NixOS 19.03.

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

[kmail2] [Bug 407163] compilation fails due to wrong include statement

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=407163

--- Comment #1 from Jos van den Oever  ---
This patch to kmail solves the issue (and one other similar issue):


diff --git a/agents/archivemailagent/CMakeLists.txt
b/agents/archivemailagent/CMakeLists.txt
index 48ed076..9c56896 100644
--- a/agents/archivemailagent/CMakeLists.txt
+++ b/agents/archivemailagent/CMakeLists.txt
@@ -22,6 +22,7 @@ ki18n_wrap_ui(libarchivemailagent_SRCS
ui/archivemailwidget.ui )
 add_library(archivemailagent STATIC ${libarchivemailagent_SRCS})
 target_link_libraries(archivemailagent
 KF5::MailCommon
+KF5::Libkdepim
 KF5::I18n
 KF5::Notifications
 KF5::IconThemes
diff --git a/agents/followupreminderagent/CMakeLists.txt
b/agents/followupreminderagent/CMakeLists.txt
index a56b730..83604cf 100644
--- a/agents/followupreminderagent/CMakeLists.txt
+++ b/agents/followupreminderagent/CMakeLists.txt
@@ -23,6 +23,7 @@ target_link_libraries(followupreminderagent
 KF5::AkonadiMime
 KF5::AkonadiAgentBase
 KF5::DBusAddons
+KF5::FollowupReminder
 KF5::XmlGui
 KF5::KIOWidgets
 KF5::Notifications

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

[kwin] [Bug 406829] kwin_x11 crashes on alt-tab

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=406829

Jos van den Oever  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME

--- Comment #2 from Jos van den Oever  ---
After upgrading Qt from 5.12.0 to 5.12.3, the bug was gone.

Setting to WORKSFORME because I do not know what fixed it.

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

[kmail2] [Bug 407163] compilation fails due to wrong include statement

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=407163

--- Comment #5 from Jos van den Oever  ---
If you have proposed or applied patch for mailcommon/src/CMakeLists.txt, I can
test it.

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

[frameworks-baloo] [Bug 411839] New: baloo_crashes on startup after a 3 month(!!!) absence update!

[Miranda van den Breukelingen]

https://bugs.kde.org/show_bug.cgi?id=411839

Bug ID: 411839
   Summary: baloo_crashes on startup after a 3 month(!!!) absence
update!
   Product: frameworks-baloo
   Version: 5.61.0
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: vanbreukelingen1...@gmail.com
  Target Milestone: ---

Application: baloo_file_extractor (5.61.0)
 (Compiled from sources)
Qt Version: 5.13.1
Frameworks Version: 5.61.0
Operating System: Linux 5.2.14-zen1-1-zen x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
After all, I had to recompile the 8192cu from source, since systemd 243
(finally) is on air. I'm very happy about that; Arch keeps it simple but it
troubles with stability in allocation of memspace; I'm gonna reinstall the
baloo_driver"

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f50b1135c80 (LWP 11940))]

Thread 3 (Thread 0x7f50af866700 (LWP 11942)):
#0  0x7f50b4562667 in poll () from /usr/lib/libc.so.6
#1  0x7f50b343c130 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f50b343c201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f50b4b06a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f50b4aad4ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f50b48df385 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f50b5ab7b37 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f50b48e05b0 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f50b3ffb57f in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f50b456d0e3 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f50b0279700 (LWP 11941)):
#0  0x7f50b4562667 in poll () from /usr/lib/libc.so.6
#1  0x7f50b33a7630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f50b33a92db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f50b0c3e101 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f50b48e05b0 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f50b3ffb57f in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f50b456d0e3 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f50b1135c80 (LWP 11940)):
[KCrash Handler]
#6  0x7f50b44ab755 in raise () from /usr/lib/libc.so.6
#7  0x7f50b4496851 in abort () from /usr/lib/libc.so.6
#8  0x7f50b41b9753 in ?? () from /usr/lib/liblmdb.so
#9  0x7f50b41b19a3 in ?? () from /usr/lib/liblmdb.so
#10 0x7f50b41b4d61 in mdb_cursor_put () from /usr/lib/liblmdb.so
#11 0x7f50b41b74ab in mdb_put () from /usr/lib/liblmdb.so
#12 0x7f50b5b81ac2 in Baloo::PostingDB::put(QByteArray const&,
QVector const&) () from /usr/lib/libKF5BalooEngine.so.5
#13 0x7f50b5b99e99 in Baloo::WriteTransaction::commit() () from
/usr/lib/libKF5BalooEngine.so.5
#14 0x7f50b5b89a80 in Baloo::Transaction::commit() () from
/usr/lib/libKF5BalooEngine.so.5
#15 0x56405c1947a5 in ?? ()
#16 0x7f50b4ae7c13 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7f50b4adb3e5 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#18 0x7f50b54684f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#19 0x7f50b5471e11 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#20 0x7f50b4aae9c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#21 0x7f50b4b05d9d in QTimerInfoList::activateTimers() () from
/usr/lib/libQt5Core.so.5
#22 0x7f50b4b0666a in ?? () from /usr/lib/libQt5Core.so.5
#23 0x7f50b343a3ae in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#24 0x7f50b343c1c1 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x7f50b343c201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#26 0x7f50b4b06a03 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#27 0x7f50b4aad4ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#28 0x7f50b4ab5326 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#29 0x56405c191283 in ?? ()
#30 0x7f50b4497ee3 in __libc_start_main () from /usr/lib/libc.so.6
#31 0x56405c19132e in ?? ()
[Inferior 1 (process 11940) detached]

Possible duplicates by query: bug 411806, bug 411660, bug 410367, bug 405101,
bug 403107.

Reported using DrKonqi

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

[kwin] [Bug 410093] New: KWin crash after switch to/from text console

[Stephan van den Akker]

https://bugs.kde.org/show_bug.cgi?id=410093

Bug ID: 410093
   Summary: KWin crash after switch to/from text console
   Product: kwin
   Version: 5.16.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: memelink.ak...@planet.nl
  Target Milestone: ---

Application: kwin_x11 (5.16.2)

Qt Version: 5.13.0
Frameworks Version: 5.59.0
Operating System: Linux 5.1.16-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I switched to a text console (Ctrl-Shift-F1) and switched back to Plasma
(Ctrl-Shift-F7). I got a message that KWin crashed. I chose "restart" and the
UI (including the compositor) is working again.

This is occuring every 2 or 3 days, usually after a "cold start" of the system,
but is not ready reproducible (doesn't happen every time).

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f88f6a36880 (LWP 2230))]

Thread 4 (Thread 0x7f88dd0d7700 (LWP 2426)):
#0  0x7f88f9939e05 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88f9ded1ea in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f88f9ded20b in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f88f9933faa in start_thread () at /lib64/libpthread.so.0
#4  0x7f88fba1773f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f88ee093700 (LWP 2418)):
#0  0x7f88fba24b3f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f88fba0cd94 in ppoll () at /lib64/libc.so.6
#2  0x7f88fa568d49 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#3  0x7f88fa56a341 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f88fa5152eb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f88fa34df91 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f88f90c6595 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f88fa34f112 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f88f9933faa in start_thread () at /lib64/libpthread.so.0
#9  0x7f88fba1773f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f88efe0c700 (LWP 2262)):
#0  0x7f88fba0cdb6 in ppoll () at /lib64/libc.so.6
#1  0x7f88fa568d49 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f88fa56a341 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f88fa5152eb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f88fa34df91 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f88f8b244f6 in  () at /usr/lib64/libQt5DBus.so.5
#6  0x7f88fa34f112 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f88f9933faa in start_thread () at /lib64/libpthread.so.0
#8  0x7f88fba1773f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f88f6a36880 (LWP 2230)):
[KCrash Handler]
#6  0x7f88f9f7b812 in  () at /usr/lib64/libkwin4_effect_builtins.so.1
#7  0x7f88fb7693c3 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#8  0x7f88f9ff274e in  () at /usr/lib64/libkwin4_effect_builtins.so.1
#9  0x7f88fb7693c3 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#10 0x7f88fb775d7b in
KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#11 0x7f88fb76fa58 in
KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#12 0x7f88fa05ccab in KWin::Effect::paintWindow(KWin::EffectWindow*, int,
QRegion, KWin::WindowPaintData&) () at /usr/lib64/libkwineffects.so.12
#13 0x7f88fb76fa03 in
KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#14 0x7f88fa05ccab in KWin::Effect::paintWindow(KWin::EffectWindow*, int,
QRegion, KWin::WindowPaintData&) () at /usr/lib64/libkwineffects.so.12
#15 0x7f88fb76fa03 in
KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib64/libkwin.so.5
#16 0x7f88fb778c35 in KWin::Scene::paintWindow(KWin::Scene::Window*, int,
QRegion, KWin::WindowQuadList) () at /usr/lib64/libkwin.so.5
#17 0x7f88fb779a36 in KWin::Scene::paintSimpleScreen(int, QRegion) () at
/usr/lib64/libkwin.so.5
#18 0x7f88ece419e3 in  () at
/usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#19 0x7f88fb778ae0 in KWin::Scene::finalPaintScreen(int, QRegion,
KWin::ScreenP

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #5 from Jos van den Oever  ---
The information for folder preferences is written to
$HOME/.config/user-dirs.dirs

I've tried to recreate the bug by renaming my Downloads folder to
Téléchargements. This gave me
```
XDG_DOWNLOAD_DIR="$HOME/Téléchargements"
``
in $HOME/.config/user-dirs.dirs
Reopening the settings dialog again showed me Téléchargements.

My environment has LANG=en_US.UTF-8.
KDE Frameworks 5.49.0 which is from before D17651.

I've tried asking LXR which code writes user-dirs.dirs.
https://lxr.kde.org/search?_filestring=&_string=user-dirs.dirs
but I'm not getting a reply.

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #6 from Jos van den Oever  ---
Got a reply now.

https://lxr.kde.org/source/kde/workspace/plasma-desktop/kcms/desktoppaths/globalpaths.cpp

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #8 from Jos van den Oever  ---
I've just written a test to recreate the issue.

void KConfigTest::testQStringUtf8()
{
QTemporaryFile file;
QVERIFY(file.open());
KConfig config(file.fileName(), KConfig::SimpleConfig);
KConfigGroup general(&config, "General");
const QString value("Téléchargements");
general.writeEntry("Utf8", value);
config.sync();
file.flush();
file.close();
QFile readFile(file.fileName());
QVERIFY(readFile.open(QFile::ReadOnly));
// check that reading works
KConfig config2(file.fileName(), KConfig::SimpleConfig);
KConfigGroup general2(&config2, "General");
QCOMPARE(value, general2.readEntry("Utf8", QByteArray()));
}

This passes. The é is escaped in the file. This is not needed. Any value above
126 is non-printable or valid UTF8 or another binary value.
Not escaping valid UTF8 sequences is an improvement. But that is not the issue
here.

"Téléchargements" is escaped on saving. That is fine. But it should be
unescaped when loading. This happens in the test, but not in
plasma-desktop/kcms/desktoppaths/globalpaths.cpp.

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #11 from Jos van den Oever  ---
globalpaths.cpp should not use KConfig to write user-dirs.dirs

KConfig escapes bytes >= 127. Improving that so that it does not escape UTF8
would be nice, but it would only solve this issue for users with UTF8 locales.
I think that `user-dirs.dirs` is written in the locale of the user.

https://code.woboq.org/qt5/qtbase/src/corelib/io/qstandardpaths_unix.cpp.html#177

This does not mention what the encoding of user-dirs.dirs is.
http://manpages.ubuntu.com/manpages/cosmic/man5/user-dirs.dirs.5.html

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #12 from Jos van den Oever  ---
xdg-user-dirs documentation says: "This file is in a shell format, so its easy
to access from a shell script." 

https://www.freedesktop.org/wiki/Software/xdg-user-dirs/

The tool xdg-user-dirs does not assume an encoding:
https://cgit.freedesktop.org/xdg/xdg-user-dirs/tree/xdg-user-dir-lookup.c#n84

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #13 from Jos van den Oever  ---
Even though KConfig should not be used by globalpaths.cpp, KConfig can be
improved.

https://phabricator.kde.org/D19107 does that.

But note that while the bug described here will probably go away for the
reporters setup, the bug in globalpaths.cpp is not really solved.

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

--- Comment #15 from Jos van den Oever  ---
Most distributions do.

The first answer on this question affirms that assuming UTF-8 is generally
safe.

https://unix.stackexchange.com/questions/2089/what-charset-encoding-is-used-for-filenames-and-paths-on-linux

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

[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=403557

Jos van den Oever  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kco
   ||nfig/2cdcd4f30666fd1095ab7c
   ||f31361e404db871075
   Version Fixed In||5.56
 Resolution|--- |FIXED

--- Comment #16 from Jos van den Oever  ---
Git commit 2cdcd4f30666fd1095ab7cf31361e404db871075 by Jos van den Oever.
Committed on 20/02/2019 at 16:19.
Pushed by vandenoever into branch 'master'.

Write valid UTF8 characters without escaping.

Summary:
commit 6a18528 introduced escaping of bytes >= 127 to ensure that
KConfig files are valid UTF8.
The simplistic approach with a cutoff results in many escaped bytes
where it is not required. Especially non-western configuration files
would have many escapes.

This commit fixes that by only escaping bytes that are not valid UTF8.
FIXED-IN: 5.56

Test Plan: ninja && ninja test

Reviewers: dfaure, arichardson, apol, #frameworks, thiago

Subscribers: rapiteanu, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D19107

M  +52   -2autotests/kconfigtest.cpp
M  +2-0autotests/kconfigtest.h
M  +113  -9src/core/kconfigini.cpp

https://commits.kde.org/kconfig/2cdcd4f30666fd1095ab7cf31361e404db871075

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

[frameworks-syntax-highlighting] [Bug 404820] New: default construction SyntaxHighlighter() crashes

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=404820

Bug ID: 404820
   Summary: default construction SyntaxHighlighter() crashes
   Product: frameworks-syntax-highlighting
   Version: 5.55.0
  Platform: Other
OS: All
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: framework
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: j...@vandenoever.info
  Target Milestone: ---

SUMMARY

SyntaxHighlighter(QObject* parent = nullptr) calls QSyntaxHighlighter(parent).

If parent == nullptr, this crashes because QSyntaxHighlighter(QObject *parent)
dereferences parent without checking for nullptr. This could be considered a
bug in QSyntaxHighlighter. However, QSyntaxHighlighter does not have a default
argument nullptr but SyntaxHighlighter does.

I do not see a way to fix SyntaxHighlighter so that SyntaxHighlighter() can be
called without crashing. Ideally, one would do this:

SyntaxHighlighter::SyntaxHighlighter(QObject* parent) :
QSyntaxHighlighter(parent ?QSyntaxHighlighter(parent)
:QSyntaxHighlighter((QTextDocument*)0)),
AbstractHighlighter(new SyntaxHighlighterPrivate)
{
qRegisterMetaType();
}

but that does not compile.

Is there a way to choose what superclass constructor to call at runtime?

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

[frameworks-syntax-highlighting] [Bug 404820] default construction SyntaxHighlighter() crashes

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=404820

--- Comment #4 from Jos van den Oever  ---
Upstream patch and removing the '= nullptr' is enough to close this bug imo.

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

[rust-qt-binding-generator] [Bug 404960] Cannot build a demo and templates

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=404960

--- Comment #1 from Jos van den Oever  ---
To build the demo, rust_qt_binding_generator should be built.
rust_qt_binding_generator is part of the parent project.

To build the demo, do this:

cd rust_qt_binding_generator
mkdir build
cd build
cmake ..
make Demo

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

[plasmashell] [Bug 411302] New: freeBSD evolution after setting back compositor to Xrender,

[Miranda van den Breukelingen]

https://bugs.kde.org/show_bug.cgi?id=411302

Bug ID: 411302
   Summary: freeBSD evolution after setting back compositor to
Xrender,
   Product: plasmashell
   Version: 5.16.4
  Platform: Compiled Sources
OS: FreeBSD
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vanbreukelingen1...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.16.4)
 (Compiled from sources)
Qt Version: 5.12.2
Frameworks Version: 5.61.0
Operating System: FreeBSD 13.0-CURRENT amd64
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
Plasma was not startable at all, it crashed right now the grafic driver
(drm-current not providable) should do shimmering into plasmashell it suddenly
hung up - so I used the XFCE-compisitor and did a "use plasma-desktop" in the
autostart. So I could change settings for kwin_x11. Now from sddm-login-screen
everything is fine (variety said, widget locked, but they are not) but not
starting plasmashell at all; systemmonitor worked already and a Alt+F2 and
kstart5 plasmashell could recover desktop with widget. 

Now Plasma5 is crashing frequently I think because of the i915 driver. Got
new-world and make kernel -j4, took me a week or so to create it. wlan0 works
now out of the box at a Dell Vostro 3550, I removed the HyperV-supervisor and
we have to do compatibility to KMS as bhyve is still under heavy development. 

llvm-devel and X -configure: no way to get a grafical WM working!

A grafical root login is to be discused?

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 411221, bug 411208, bug 411174, bug 411089,
bug 411087.

Reported using DrKonqi

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

[konqueror] [Bug 405816] New: virtualbox freebsd host=linux arch

[Miranda van den Breukelingen]

https://bugs.kde.org/show_bug.cgi?id=405816

Bug ID: 405816
   Summary: virtualbox freebsd host=linux arch
   Product: konqueror
   Version: 5.0.97
  Platform: Compiled Sources
OS: FreeBSD
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: vanbreukelingen1...@gmail.com
  Target Milestone: ---

Application: konqueror (5.0.97)
 (Compiled from sources)
Qt Version: 5.12.1
Frameworks Version: 5.56.0
Operating System: FreeBSD 13.0-CURRENT amd64
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
So the whole konqueror thing reaches back until 2002, where it was the standard
to integrate the desktop components to the web. M$ did something very ugly ...
nostalgia

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 405770, bug 405760, bug 405685, bug 405682,
bug 405637.

Reported using DrKonqi

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

[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=395192

--- Comment #4 from Jos van den Oever  ---
The functionality that you want is possible, but quite some work.

The Model/View in Qt is based on QAbstractItemModel. The current code creates
one QAbstractItemModel for a List or a Tree. Each node in the List or Tree has
the same properties.

Your binding is for a List with a top level of nodes that have `name` and
`novel_list`. Each `novel_list` of type `Source` has a list of items again:
`chapter_list`. So your model is a tree but the nodes on each level have a
different type. It is a clear and logical model from a data modelling point of
view.

A logical Rust structure for this would be

struct Sources {
name: String,
novel_list: Vec,
}
struct Source {
name: title: String,
chapter_list: Vec,
}
struct Novel {
index: u32,
title: String,
content: String,
}

In Qt Model/View each node in a tree has an index and all nodes are basically
the same. The delegates that render the nodes also treat all nodes the same.
But each property can have a different role. If you want to show this model in
a QTreeView or TreeView, you'd specify a different role or column for each
property. So the role numbers and column numbers should be unique for the
properties in the combination of Sources, Source and Novel. The solution I gave
you does that. But it does not look as nice as the structure you want.

The current code could be expanded to interpret Sources, Source and Novel as
belonging to one Tree. It would be very nice, but hard to implement such an
addition to the code generator.

The solution I gave is also flawed in that I forgot to add `optional`:


"objects": {
"Novels": {
"type": "Tree",
"itemProperties": {
"sourcesName": {
"type": "QString",
"optional": true
},
"sourceTitle": {
"type": "QString",
"optional": true
},
"novelIndex": {
"type": "quint32",
"optional": true
},
"novelTitle": {
"type": "QString",
"optional": true
},
"novelContent": {
"type": "QString",
"optional": true
}
}
}
}

This limitation in the generator is also present in Qt itself. If you write C++
code with QAbstractItemModel, you'd face the same issue that it expects each
node in the tree to be the same.

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

[rust-qt-binding-generator] [Bug 400716] Build issues on Windows

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400716

--- Comment #1 from Jos van den Oever  ---
Nice to hear you got it working on windows.

Would these changes work for you?

diff --git a/examples/todos/CMakeLists.txt b/examples/todos/CMakeLists.txt
index 9a940af..8400542 100644
--- a/examples/todos/CMakeLists.txt
+++ b/examples/todos/CMakeLists.txt
@@ -37,7 +37,11 @@ feature_summary(WHAT ALL INCLUDE_QUIET_PACKAGES
FATAL_ON_MISSING_REQUIRED_PACKAG
 ### build commands ###

 SET(RUST_DIR "${CMAKE_CURRENT_SOURCE_DIR}/rust")
-SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/librust.a")
+if (MSVC)
+  SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/rust.lib")
+else()
+  SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/librust.a")
+endif()

 # generate c++ and rust code from bindings.json
 add_custom_command(
@@ -61,6 +65,9 @@ add_custom_command(
 add_custom_target(rust_target DEPENDS "${RUST_LIB}")

 list(APPEND Libs "${RUST_LIB}")
+if (MSVC)
+  list(APPEND Libs WS2_32.LIB Userenv.lib)
+endif()
 list(APPEND Libs Qt5::Core Qt5::Quick Threads::Threads ${CMAKE_DL_LIBS})
 set(SRCS src/main.cpp src/Bindings.cpp "qml.qrc")
 add_executable(todos ${SRCS})

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

[rust-qt-binding-generator] [Bug 400716] Build issues on Windows

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400716

Jos van den Oever  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/rus
   ||t-qt-binding-generator/f678
   ||d441e9fe31d6d933f6c27b884b8
   ||07438fcad

--- Comment #3 from Jos van den Oever  ---
Git commit f678d441e9fe31d6d933f6c27b884b807438fcad by Jos van den Oever.
Committed on 11/11/2018 at 15:03.
Pushed by vandenoever into branch 'master'.

Fix building with MSVC

M  +10   -3demo/CMakeLists.txt
M  +8-1examples/todos/CMakeLists.txt
M  +5-1templates/qt_quick/CMakeLists.txt
M  +5-1templates/qt_widgets/CMakeLists.txt
M  +8-3tests/CMakeLists.txt

https://commits.kde.org/rust-qt-binding-generator/f678d441e9fe31d6d933f6c27b884b807438fcad

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

[rust-qt-binding-generator] [Bug 400716] Build issues on Windows

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=400716

--- Comment #4 from Jos van den Oever  ---
The patch also fixes the 'test' and 'demo' targets. I'm curious if the demo
application works on windows.

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

[Spectacle] [Bug 420449] New: add support for saving as (lossless) webp

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=420449

Bug ID: 420449
   Summary: add support for saving as (lossless) webp
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: j...@vandenoever.info
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY

Files saved by spectacle can be quite large. Using oxipng or optipng can often
shave 30% of the size in a fraction of a second.

oxipng /tmp/Screenshot_20200423_111228.png
Processing: /tmp/Screenshot_20200423_111228.png
1411x1217 pixels, PNG format
4x8 bits/pixel, RGBA
IDAT size = 285460 bytes
File size = 285946 bytes
Trying: 8 combinations
Found better combination:
zc = 9  zs = 0  f = 0203982 bytes
IDAT size = 203982 bytes (81478 bytes decrease)
file size = 204060 bytes (81886 bytes = 28.64% decrease)
Output: /tmp/Screenshot_20200423_111228.png


Even more space can be saved by saving as lossless webp. Webp is supported in
all new browsers. Making it the default is perhaps a bit early, but it would be
nice if spectable would remember the preference for webp.

STEPS TO REPRODUCE

$ cwebp -lossless /tmp/Screenshot_20200423_111228.png -o
/tmp/Screenshot_20200423_111228.webp
Saving file '/tmp/Screenshot_20200423_111228.webp'
File:  /tmp/Screenshot_20200423_111228.png
Dimension: 1411 x 1217
Output:92618 bytes (0.43 bpp)
Lossless-ARGB compressed size: 92618 bytes
  * Header size: 2129 bytes, image data size: 90463
  * Lossless features used: SUBTRACT-GREEN
  * Precision Bits: histogram=5 transform=5 cache=10

OBSERVED RESULT

$ ls -l /tmp/Screenshot_20200423_111228.*
285946 23 apr 11:12 /tmp/Screenshot_20200423_111228.png
 92618 23 apr 11:13 /tmp/Screenshot_20200423_111228.web


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 19.12
(available in About System)
KDE Plasma Version:  19.12
KDE Frameworks Version: 5.66
Qt Version: 5.12.7

ADDITIONAL INFORMATION

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

[Spectacle] [Bug 420449] add support for saving as (lossless) webp

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=420449

--- Comment #2 from Jos van den Oever  ---
That's great to hear. I've plugins/imageformats/libqwebp.so on my machine but
do not see an option to save to webp or set it as a default format.

Is there an option to save losslessly? webp can save lossy and losslessly and
often for screenshots the lossless version is smaller as well as more accurate.

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

[Spectacle] [Bug 420449] add support for saving as (lossless) webp

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=420449

--- Comment #3 from Jos van den Oever  ---
After installing the Qt image plugins, spectacle can save as webp. Very nice!

When I save images with webp 100% quality the files are much smaller than when
saving with 99% quality.

E.g. a screenshot of a browser is 366K when saving at 99% quality and 197K when
saving at 100% quality.

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

[rust-qt-binding-generator] [Bug 415915] Upgrading serde-xml-rs from 0.2 to 0.3.1

[Jos van den Oever]

https://bugs.kde.org/show_bug.cgi?id=415915

Jos van den Oever  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Jos van den Oever  ---
This is fixed in 4d393706b84a3c2852ece2689366811a0fc02207.

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

[Falkon] [Bug 421410] New: Show menu bar key combination

[Tim Van den Langenbergh]

https://bugs.kde.org/show_bug.cgi?id=421410

Bug ID: 421410
   Summary: Show menu bar key combination
   Product: Falkon
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: tmt_...@gmx.com
  Target Milestone: ---

For users without a mouse it would be prudent to add a key combination to show
the menu bar. Konsole binds it to Shift+M by default.

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

[Falkon] [Bug 421410] Show menu bar key combination

[Tim Van den Langenbergh]

https://bugs.kde.org/show_bug.cgi?id=421410

--- Comment #1 from Tim Van den Langenbergh  ---
I meant Ctrl+Shift+M.

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