from:"Russell"

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

--- Comment #5 from Russell Haley  ---
(In reply to Andrew Crouthamel from comment #4)
>So that is the cycles of the CPU unusable for calculations, and thus 
>considered "used".

I/O wait does not make the CPU unusuable for other calculations.  It's just
idle time that happens when some I/O request is in flight. Try running my
reproducer script from https://bugs.kde.org/show_bug.cgi?id=465768 and "stress
-c $(nproc)" at the same time.  Top will show 100% userspace utilization from
the stress command, *and* the disk reads will continue at full speed.

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

--- Comment #2 from Russell Haley  ---
Looks like I missed a few dupes.  Guess I'm the first to report this against
plasma-systemmonitor, though =P

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

[kicker] [Bug 120422] panel system monitor shows iowait as use

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

Russell Haley  changed:

   What|Removed |Added

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

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

Russell Haley  changed:

   What|Removed |Added

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

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

[ktimemon] [Bug 83143] ktimemon doesn't honor iowait for Linux 2.6 kernels

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

Russell Haley  changed:

   What|Removed |Added

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

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

Russell Haley  changed:

   What|Removed |Added

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

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

[plasma4] [Bug 339164] Cpu monitor widget counts iowait as cpu load

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

Russell Haley  changed:

   What|Removed |Added

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

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

[ksysguard] [Bug 238331] CPU utilization includes IO-wait

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

Russell Haley  changed:

   What|Removed |Added

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

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

Russell Haley  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=238331
 CC||yumpusamongus+...@gmail.com

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

Russell Haley  changed:

   What|Removed |Added

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

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

[plasma-systemmonitor] [Bug 465768] iowait is counted as cpu usage by per-core sensors

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

--- Comment #1 from Russell Haley  ---
Created attachment 156272
  --> https://bugs.kde.org/attachment.cgi?id=156272=edit
screenshot showing all 3 affected applications

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

[plasma-systemmonitor] [Bug 465768] New: iowait is counted as cpu usage by per-core sensors

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

Bug ID: 465768
   Summary: iowait is counted as cpu usage by per-core sensors
Classification: Plasma
   Product: plasma-systemmonitor
   Version: 5.26.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: yumpusamongus+...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 156271
  --> https://bugs.kde.org/attachment.cgi?id=156271=edit
script that reproduces the problem (and doesn't thrash the cache)

SUMMARY

IO wait time is counted as CPU busy time by whichever underlying library is
used plasma-systemmonitor, ksysguard, and desktop sensor widgets.

STEPS TO REPRODUCE
1. Open the "history" view of plasma-systemmonitor, or the "System Load" tab of
ksysguard, or have a system monitor widget using the "Core # Total Usage"
sensor on your panel.
2. Run the attached script.  If you don't have any SATA drives, change
"/dev/sda" to something you do have.

OBSERVED RESULT

CPU usage appears to be 100%, even though the workload is totally I/O bound.

EXPECTED RESULT

CPU usage includes only % of time the CPU is executing instructions, matching
the much lower value reported by htop.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:  Fedora Linux 37
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

This has probably been reported before, as bug 339164 against the plasma4
widget.

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

[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1

2022-11-25 Thread Russell Haley

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

Russell Haley  changed:

   What|Removed |Added

 CC||yumpusamongus+...@gmail.com

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

[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input

2022-07-25 Thread Russell Haley

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

Russell Haley  changed:

   What|Removed |Added

 CC||yumpusamongus+...@gmail.com

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

[kwin] [Bug 456697] [Wayland] Please provide a means to specify a custom modeline

2022-07-14 Thread Russell Haley

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

--- Comment #2 from Russell Haley  ---
(In reply to postix from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 356818 ***

The other bug is about exposing a UI for a thing that the Xorg server can do. 
This one is about making it possible to do at all under Wayland.

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

[kwin] [Bug 456697] New: [Wayland] Please provide a means to specify a custom modeline

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

Bug ID: 456697
Summary: [Wayland] Please provide a means to specify a custom
modeline
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: yumpusamongus+...@gmail.com
Target Milestone: ---

In Xorg, it is possible to overclock a 60 Hz monitor to 70 Hz like so:

xrandr --newmode "1920x1080_70.00" 156.240 1920 1928 1960 2000 1080 1102
1110 1116 +HSync -VSync
xrandr --addmode HDMI-1 "1920x1080_70.00"
xrandr --output HDMI-1 --mode "1920x1080_70.00"

The timing parameters are generated by edid-decode, using the reduced blanking
v2 formula to fit within the pixel clock limit of single-link DVI:

edid-decode -X --cvt w=1920,h=1080,fps=70,rb=2

There is also an updated version of the conventional `cvt` program that can
calculate RBv2 modes, at
https://github.com/kevinlekiller/cvt_modeline_calculator_12/, but it isn't
packaged in my distribution.

Other applications include:

1. 48 Hz (or 72 if your monitor goes that high) for playing 24 Hz video without
3-2 pulldown.
2. Running games at lower vsync'ed frame rates on monitors that don't support
VRR, like the Steam Deck's 40 Hz mode.
3. Exactly matching the refresh rates of screens from different vendors,
although I've never needed it for this reason.
4. Conceivably, a user might even calculate non-standard 60 Hz modes with max
pixel clock (165 MHz) and an extended front porch, similar to VRR, in order to
reduce the probability of tearing in non-vsync'ed rendering.

There's supposedly a workaround by passing a fake EDID to the kernel,
https://askubuntu.com/questions/973499/wayland-how-to-set-a-custom-resolution/973582#973582,
but I couldn't get it (or any of the forks on github) to work. The tool in the
kernel sources generated EDID blocks without correct headers or checksums. At
that point the only way forward would've been writing a program to pull the
connected monitor's EDID out of /sys/class/drm and patch it. And even if that
worked, changing the EDID at runtime requires re-plugging the monitor and a
kernel with debugfs enabled, which would be very annoying if you're
experimenting with the limits of your monitor.

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

[kdeconnect] [Bug 418402] Warnings when starting kdeconnect: QSocketNotifier: QSocketNotifier: Can only be used with threads started with QThread

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

Russell Haley  changed:

   What|Removed |Added

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

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

[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere

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

Russell Haley  changed:

   What|Removed |Added

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

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

[kde] [Bug 456696] New: "QSocketNotifier: Can only be used with threads started with QThread" everywhere

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

Bug ID: 456696
   Summary: "QSocketNotifier: Can only be used with threads
started with QThread" everywhere
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: yumpusamongus+...@gmail.com
  Target Milestone: ---

Created attachment 150603
  --> https://bugs.kde.org/attachment.cgi?id=150603=edit
Fedora 36 upgrade transaction

Many things on my system recently started printing this to stderr.  It's mostly
just annoying, but it does get into the stdout of `kscreen-console json`  and
make the json invalid, and having this warning showing up in my consoles all
the time feels a bit dodgy.


STEPS TO REPRODUCE

1. `kioclient5 stat`

... is the shortest command I know that prints the error and exits immediately,
but it's much more widespread.

OBSERVED RESULT

QSocketNotifier: Can only be used with threads started with QThread
kioclient5: Syntax error, not enough arguments

EXPECTED RESULT

kioclient5: Syntax error, not enough arguments

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora 36
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

This shows how many times the message has been logged by various programs since
boot:

journalctl -b --output cat --output-fields=_EXE MESSAGE='QSocketNotifier:
Can only be used with threads started with QThread' | sort | uniq -c | sort
-nk1,1

On my machine, it prints:

  1 /usr/bin/dolphin
  1 /usr/bin/korganizer
  1 /usr/bin/kstart
  1 /usr/bin/kwrite
  1 /usr/bin/okteta
  1 /usr/bin/plasma-discover
  1 /usr/libexec/ksmserver-logout-greeter
  2 /usr/bin/akonadi_archivemail_agent
  2 /usr/bin/akonadi_birthdays_resource
  2 /usr/bin/akonadi_control
  2 /usr/bin/akonadi_followupreminder_agent
  2 /usr/bin/akonadi_indexing_agent
  2 /usr/bin/akonadi_maildispatcher_agent
  2 /usr/bin/akonadi_mailfilter_agent
  2 /usr/bin/akonadi_mailmerge_agent
  2 /usr/bin/akonadi_migration_agent
  2 /usr/bin/akonadi_newmailnotifier_agent
  2 /usr/bin/akonadi_sendlater_agent
  2 /usr/bin/akonadi_unifiedmailbox_agent
  2 /usr/bin/akonadi_vcard_resource
  2 /usr/bin/corectrl
  2 /usr/bin/kalendarac
  2 /usr/bin/kcminit_startup
  2 /usr/bin/kded5
  2 /usr/bin/ksplashqml
  2 /usr/bin/kwalletd5
  2 /usr/bin/plasmashell
  2 /usr/libexec/baloorunner
  2 /usr/libexec/DiscoverNotifier
  2 /usr/libexec/kactivitymanagerd
  2 /usr/libexec/kdeconnectd
  2 /usr/libexec/kf5/polkit-kde-authentication-agent-1
  2 /usr/libexec/org_kde_powerdevil
  2 /usr/libexec/xdg-desktop-portal-kde
  4 /usr/bin/akonadi_akonotes_resource
  4 /usr/bin/akonadi_contacts_resource
  4 /usr/bin/akonadi_ical_resource
  4 /usr/bin/akonadi_maildir_resource
  4 /usr/bin/systemsettings
 36 /usr/bin/konsole
 39 /usr/libexec/kscreenlocker_greet

According to `sudo rg --one-file-system -Suu "Can only be used with threads"
--binary /usr`, the message probably comes from
/usr/lib64/libQt5Core.so.5.15.3, which the top culprits link against according
to `ldd`, and which is provided by the qt5-qtbase package.

According to `dnf history`, this package was updated from version 5.15.2-30 to
version 5.15.3-1 as part of the Fedora 35->36 upgrade on 2022-05-12.  I have
attached the `dnf history info` from that transaction.

Oddly, the logs show 59 occurances of the message from 2022-03-29, when the
installed qt5-qtbase version was 5.15.2, but then it didn't appear again until
many boots later on 2022-05-16, which was the SECOND (wat?) boot and login
session after the Fedora 35->36 upgrade, with no intervening dnf transactions.
Unfortunately, I have no logs from before 2022-03-29, because
plasma-systemmonitor had some kind of fit and spammed hundreds of messages per
second, which flushed the journal from before that date.

I don't know whether this is a problem with libQt or with the use of it.

This seems similar to bug 418402, but it has a much wider blast radius and
seems to have started with a different version of qt5-qtbase.

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

[amarok] [Bug 455371] CD Reports 0 Tracks in Amarok

2022-06-17 Thread Russell

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

--- Comment #4 from Russell  ---
(In reply to Heiko Becker from comment #3)
> > $dpkg -l | grep audiocd
> > ii  kio-audiocd   4:19.12.3-0ubuntu1
> > amd64transparent audio CD access for applications using the KDE
> > Platform
> > 
> > I can't find it by the original name, is this the right one?
> 
> That seems to be the right one, audiocd-kio is the upstream name. I
> currently don't have a CD or a drive with me, but can you try navigating to
> audiocd:/ in dolphin or konqueror? If the tracks show up there, it's likely
> Amarok's fault, if not, the bug is probably in audiocd-kio.

I can confirm that the tracks appear in Dolphin in the audiocd:/ path (although
it's adding a ?device=/dev/sr0 too). I also went back to Amarok after they
loaded, and nope, they're still not showing up there.

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

[amarok] [Bug 455371] CD Reports 0 Tracks in Amarok

2022-06-17 Thread Russell

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

--- Comment #2 from Russell  ---
(In reply to Heiko Becker from comment #1)
> Do you have audiocd-kio installed? It's the component that allows Amarok to
> play CDs.
> 
> (Your distro should probably list as some kind of optional runtime
> dependency)

I don't seem to have it by that exact name, but it appears to be present?

$dpkg -l | grep audiocd
ii  kio-audiocd   4:19.12.3-0ubuntu1   
   amd64transparent audio CD access for
applications using the KDE Platform

I can't find it by the original name, is this the right one?

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

[amarok] [Bug 455371] New: CD Reports 0 Tracks in Amarok

2022-06-15 Thread Russell

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

Bug ID: 455371
Summary: CD Reports 0 Tracks in Amarok
Product: amarok
Version: 2.9.71
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Collections/CD
Assignee: amarok-bugs-d...@kde.org
Reporter: rdragonr...@gmail.com
Target Milestone: kf5

Created attachment 149769
--> https://bugs.kde.org/attachment.cgi?id=149769=edit
Run log of Amarok not detecting CD tracks

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I've bought some CDs, and I was trying to put them on my MP3 player. However,
Amarok, while it detects the presence of a CD, can't seem to actually find the
tracks. Other ripping tools will display the presence of tracks, although of
those, at this point, only SoundJuicer appears able to get metadata. I've also
tried several CDs by different artists, etc.

STEPS TO REPRODUCE
1. Insert a CD with Amarok open
2. Look at the media entry for the CD
3. It says there are 0 tracks on the CD, and it can't be played or ripped.

OBSERVED RESULT
0 tracks are listed for the CD.

EXPECTED RESULT
I was expecting the appropriate number of tracks.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04 LTS 64-bit, gnome 3.36
KDE Plasma Version: N/A?
Qt: 5.12.8
KDE Frameworks: 5.68.0
kf5-config: 1.0

ADDITIONAL INFORMATION
I am using the PGomes PPA for my Amarok build, but this bug was also present
with the official package in Ubuntu 18.04 as well.

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

[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications

2022-04-15 Thread Russell

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

--- Comment #9 from Russell  ---
Created attachment 148177
  --> https://bugs.kde.org/attachment.cgi?id=148177=edit
New crash information added by DrKonqi

kwin_x11 (5.24.4) using Qt 5.15.3

- What I was doing when the application crashed:
Similar to other reports, this seems to happen randomly when browsing with
Firefox, switching tabs. I have not identified any specific pattern or trigger.

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#5  0x7fa9ecbc9fdf in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#6  0x7fa9ecb7e732 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7  0x7fa9ecb69469 in __GI_abort () at abort.c:79
#8  0x7fa9e5872e28 in _iris_batch_flush (batch=,
file=, line=) at
../mesa-22.0.1/src/gallium/drivers/iris/iris_batch.c:1105

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

[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications

2022-04-15 Thread Russell

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

Russell  changed:

   What|Removed |Added

 CC||russ...@obets.net

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

[frameworks-kwayland] [Bug 452633] New: Pkg-config file for KF5WaylandClient.pc is missing KWayland module name or namespace in include path

2022-04-14 Thread Russell

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

Bug ID: 452633
   Summary: Pkg-config file for KF5WaylandClient.pc is missing
KWayland module name or namespace in include path
   Product: frameworks-kwayland
   Version: 5.93.0
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: client
  Assignee: mgraess...@kde.org
  Reporter: russ...@obets.net
CC: kwin-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
While trying to build gnupg pinentry, I found the pkg-config file for
KF5WaylandClient is pointing to ${prefix}/include/KF5 instead of
${prefix}/include/KF5/KWayland.

The header install path was updated in a recent commit:
https://invent.kde.org/frameworks/kwayland/-/commit/de442e4a94e249a29cf2e005db8e0a5e4a6a13ed

STEPS TO REPRODUCE
On Gentoo:
1. Install/update to kde-frameworks/kwayland-5.93.0 `emerge -1
=kde-frameworks/kwayland-5.93.0`

2. Attempt to install or update app-crypt/pinentry-1.2.0 `emerge -1
=app-crypt/pinentry-1.2.0`. This fails with error:
```x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..   -I.. -I../secmem
-I/usr/include/ncursesw -I../pinentry -Wall -I/usr/include/KF5 -DQT_GUI_LIB
-I/usr/include/qt5/QtGui -I/usr/include/qt5 -DQT_CORE_LIB
-I/usr/include/qt5/QtCore   -I/usr/include/qt5/QtCore -I/usr/include/qt5
-I/usr/include/qt5/QtGui -DQT_WIDGETS_LIB -I/usr/include/qt5/QtWidgets
-DQT_GUI_LIB -DQT_CORE_LIB  -fpic -std=c++11 -DQT_X11EXTRAS_LIB
-I/usr/include/qt5/QtX11Extras -I/usr/include/qt5 -I/usr/include/qt5/QtCore
-DQT_GUI_LIB -I/usr/include/qt5/QtGui -DQT_CORE_LIB  -fpic -O2 -march=skylake
-mtune=skylake -falign-functions=32 -O3 -fgraphite-identity
-floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta
-fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe -O2 -pipe
-Wl,-O1 -Wl,--as-needed -std=gnu++11 -c -o capslock_unix.o capslock_unix.cpp
capslock_unix.cpp:29:11: fatal error: KWayland/Client/connection_thread.h: No
such file or directory
   29 | # include 
  |   ^
```

3. Check pkg-config data for KF5WaylandClient `pkg-config --cflags
KF5WaylandClient`


OBSERVED RESULT
Include path for KF5WaylandClient is /usr/include/KF5
```
# pkg-config --cflags KF5WaylandClient
-I/usr/include/KF5 -DQT_GUI_LIB -I/usr/include/qt5/QtGui -I/usr/include/qt5
-DQT_CORE_LIB -I/usr/include/qt5/QtCore 
```


EXPECTED RESULT
Expect include path to be /usr/include/KF5/KWayland/
```
# ls /usr/include/KF5/KWayland/
KWayland  kwayland_version.h  Server
```

BluezQt with a similar directory structure provides an include path of
/usr/include/KF5/BluezQt.
```
# ls /usr/include/KF5/BluezQt/
bluezqt  BluezQt  bluezqt_version.h

 # pkg-config --cflags KF5BluezQt 
-I/usr/include/KF5/BluezQt/ -I/usr/include/qt5/QtCore -I/usr/include/qt5
-DQT_NETWORK_LIB -I/usr/include/qt5/QtNetwork -DQT_DBUS_LIB
-I/usr/include/qt5/QtDBus -DQT_CORE_LIB 
```

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Plasma 5.24.4 on Gentoo ~x86_64
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Looks like even build prep is enough to see the resulting pkg-config file.

```
 russell@russell-blade ~/git/kwayland/build  master $ git show --oneline -s
f565454 (HEAD -> master, origin/master, origin/HEAD) [plasmawindowmanagement]
Add resourceName
 russell@russell-blade ~/git/kwayland/build  master $ cmake ..
...
 russell@russell-blade ~/git/kwayland/build  master $ cat KF5WaylandClient.pc 

prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib64
includedir=${prefix}/include/KF5

Name: KF5WaylandClient
Description: Qt-style API to interact with the wayland-client and
wayland-server API
URL: https://www.kde.org/
Version: 5.94.0
Libs: -L${prefix}/lib64 -lKF5WaylandClient
Cflags: -I${prefix}/include/KF5 
Requires: Qt5Gui
```

cmake_install.cmake shows the install path as
"${CMAKE_INSTALL_PREFIX}/include/KF5/KWayland"
```
if("x${CMAKE_INSTALL_COMPONENT}x" STREQUAL "xDevelx" OR NOT
CMAKE_INSTALL_COMPONENT)
  file(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/include/KF5/KWayland" TYPE
FILE FILES "/home/russell/git/kwayland/build/kwayland_version.h")
endif()
```

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

[kwin] [Bug 433700] On a ultrawide monitor, when the Present Windows effect is active, a tint is always visible

2021-10-20 Thread Russell Sim

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

Russell Sim  changed:

   What|Removed |Added

 CC||russell@gmail.com

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

[kwin] [Bug 444088] New: Blurry windows after resume

2021-10-20 Thread Russell Sim

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

Bug ID: 444088
   Summary: Blurry windows after resume
   Product: kwin
   Version: 5.23.0
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: russell@gmail.com
  Target Milestone: ---

Created attachment 142654
  --> https://bugs.kde.org/attachment.cgi?id=142654=edit
Blurry window example

SUMMARY

When resuming from sleep out of focus windows are all blurry and unreadable.

I have attached a screenshot to show the issue, the image is taken with the
immediate option in the screenshot program, otherwise the windows are in focus,
i don't know if kwin changes behavior if it detects that a screenshot is being
taken.

The lower left of the terminal shows what the window should look like when it's
in focus, as it appears to be in the middle of rendering the effect on that
window.

The problem doesn't exist on login, only after suspending/resuming.


STEPS TO REPRODUCE
1. Suspend system
2. Resume system

OBSERVED RESULT

On resume windows fade in and out of focus, the active window will phase back
into focus as the background windows blur so much that they are unreadable, the
blurring doesn't look intentional, the text is being pixelated so the effect is
not a smooth blurring.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian GNU/Linux unstable
(available in About System)
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version 5.14.0-3-amd64
Graphics Platform: X11

ADDITIONAL INFORMATION

$ glxinfo -B
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 8192 MB
Total available memory: 8192 MB
Currently available dedicated video memory: 7439 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 2080/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.74
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 470.74
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.74
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

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

[valgrind] [Bug 420780] PPCle erroneous report on strncmp use.

2021-10-06 Thread Rusty Russell

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

Rusty Russell  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Rusty Russell  ---
Reopened.  Apparently still triggered on valgrind master.

With recent gcc's you need to compile with -Og to reproduce (not -O3).  Or try
the asm directly?

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

[dolphin] [Bug 442370] 24hour time not displayed in Dolphin

2021-09-13 Thread Russell

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

Russell  changed:

   What|Removed |Added

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

--- Comment #3 from Russell  ---

editing /etc/env.d/02locale adding: LC_TIME="C"
editing ~/bashrc adding: export LC_TIME="C"
restarted the system

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

[dolphin] [Bug 442370] 24hour time not displayed in Dolphin

2021-09-13 Thread Russell

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

--- Comment #2 from Russell  ---
thanks for the tip!
It all fell into place after editing /etc/env.d/02locale and adding LC_TIME="C"
and restarted the system

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

[dolphin] [Bug 442370] New: 24hour time not displayed in Dolphin

2021-09-13 Thread Russell

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

Bug ID: 442370
   Summary: 24hour time not displayed in Dolphin
   Product: dolphin
   Version: 21.04.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: russell.da...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

24 hour time in iso format is not possible to display

STEPS TO REPRODUCE
1. open Dolphin > Menu > Settings > Configure Dolphin > View Modes > Details
2.
3. 

OBSERVED RESULT
 only have "Relative (eg 30 minutes ago)" or "Absolute (eg 13/9/31 3:56PM)"

EXPECTED RESULT
no setting to have Absolute time eg 13/09/31 15:56:00

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.21.5
(available in About System)
KDE Plasma Version: 5.82.0
KDE Frameworks Version: /-
Qt Version: 5.15.2

ADDITIONAL INFORMATION
running in Calculate Linux (based on Gentoo)

kde packages ($ qlist -Iv | /bin/grep kde)
kde-apps/ark-21.04.3
kde-apps/baloo-widgets-21.04.3
kde-apps/dolphin-21.04.3
kde-apps/dolphin-plugins-dropbox-21.04.3
kde-apps/dolphin-plugins-git-21.04.3
kde-apps/dolphin-plugins-mercurial-21.04.3
kde-apps/dolphin-plugins-subversion-21.04.3
kde-apps/ffmpegthumbs-21.04.3
kde-apps/gwenview-21.04.3
kde-apps/k3b-21.04.3
kde-apps/kaccounts-integration-21.04.3
kde-apps/kdecore-meta-21.04.3
kde-apps/kdenlive-21.04.3-r1
kde-apps/kdialog-21.04.3
kde-apps/keditbookmarks-21.04.3
kde-apps/kfind-21.04.3-r1
kde-apps/khelpcenter-21.04.3
kde-apps/kio-extras-21.04.3-r2
kde-apps/kipi-plugins-21.04.3-r1
kde-apps/kompare-21.04.3
kde-apps/konsole-21.04.3-r3
kde-apps/kwrite-21.04.3
kde-apps/libkcddb-21.04.3
kde-apps/libkdcraw-21.04.3
kde-apps/libkexiv2-21.04.3
kde-apps/libkipi-21.04.3
kde-apps/libkomparediff2-21.04.3
kde-apps/libksane-21.04.3
kde-apps/thumbnailers-21.04.3
kde-apps/umbrello-21.04.3
kde-frameworks/attica-5.82.0
kde-frameworks/baloo-5.82.0
kde-frameworks/bluez-qt-5.82.0
kde-frameworks/breeze-icons-5.82.0
kde-frameworks/extra-cmake-modules-5.82.0
kde-frameworks/frameworkintegration-5.82.0
kde-frameworks/kactivities-5.82.0
kde-frameworks/kactivities-stats-5.82.0
kde-frameworks/karchive-5.82.0
kde-frameworks/kauth-5.82.0
kde-frameworks/kbookmarks-5.82.0
kde-frameworks/kcmutils-5.82.0
kde-frameworks/kcodecs-5.82.0
kde-frameworks/kcompletion-5.82.0
kde-frameworks/kconfig-5.82.0
kde-frameworks/kconfigwidgets-5.82.0
kde-frameworks/kcoreaddons-5.82.0
kde-frameworks/kcrash-5.82.0
kde-frameworks/kdbusaddons-5.82.0
kde-frameworks/kdeclarative-5.82.0
kde-frameworks/kded-5.82.0
kde-frameworks/kdelibs4support-5.82.0
kde-frameworks/kdesu-5.82.0
kde-frameworks/kdnssd-5.82.0
kde-frameworks/kdoctools-5.82.0
kde-frameworks/kemoticons-5.82.0
kde-frameworks/kf-env-5
kde-frameworks/kfilemetadata-5.82.0
kde-frameworks/kglobalaccel-5.82.0-r1
kde-frameworks/kguiaddons-5.82.0
kde-frameworks/kholidays-5.82.0
kde-frameworks/khtml-5.82.0
kde-frameworks/ki18n-5.82.0
kde-frameworks/kiconthemes-5.82.0
kde-frameworks/kidletime-5.82.0
kde-frameworks/kimageformats-5.82.0
kde-frameworks/kinit-5.82.0
kde-frameworks/kio-5.82.0-r2
kde-frameworks/kirigami-5.82.0
kde-frameworks/kitemmodels-5.82.0
kde-frameworks/kitemviews-5.82.0
kde-frameworks/kjobwidgets-5.82.0
kde-frameworks/kjs-5.82.0
kde-frameworks/knewstuff-5.82.0
kde-frameworks/knotifications-5.82.0
kde-frameworks/knotifyconfig-5.82.0
kde-frameworks/kpackage-5.82.0
kde-frameworks/kparts-5.82.0
kde-frameworks/kpeople-5.82.0
kde-frameworks/kpty-5.82.0
kde-frameworks/kquickcharts-5.82.0
kde-frameworks/krunner-5.82.0
kde-frameworks/kservice-5.82.0
kde-frameworks/ktexteditor-5.82.0
kde-frameworks/ktextwidgets-5.82.0
kde-frameworks/kunitconversion-5.82.0
kde-frameworks/kwallet-5.82.0
kde-frameworks/kwayland-5.82.0
kde-frameworks/kwidgetsaddons-5.82.0
kde-frameworks/kwindowsystem-5.82.0
kde-frameworks/kxmlgui-5.82.0
kde-frameworks/modemmanager-qt-5.82.0
kde-frameworks/networkmanager-qt-5.82.0
kde-frameworks/plasma-5.82.0
kde-frameworks/prison-5.82.0
kde-frameworks/purpose-5.82.0
kde-frameworks/qqc2-desktop-style-5.82.0
kde-frameworks/solid-5.82.0
kde-frameworks/sonnet-5.82.0
kde-frameworks/syntax-highlighting-5.82.0
kde-frameworks/threadweaver-5.82.0
kde-plasma/bluedevil-5.21.5-r1
kde-plasma/breeze-5.21.5-r1
kde-plasma/breeze-gtk-5.21.5
kde-plasma/drkonqi-5.21.5-r1
kde-plasma/kactivitymanagerd-5.21.5
kde-plasma/kde-cli-tools-5.21.5
kde-plasma/kde-gtk-config-5.21.5
kde-plasma/kdecoration-5.21.5
kde-plasma/kdeplasma-addons-5.21.5
kde-plasma/kgamma-5.21.5
kde-plasma/khotkeys-5.21.5
kde-plasma/kinfocenter-5.21.5
kde-plasma/kmenuedit-5.21.5
kde-plasma/kscreen-5.21.5
kde-plasma/kscreenlocker-5.21.5
kde-plasma/ksshaskpass-5.21.5
kde-plasma/ksysguard-5.21.5
kde-plasma/kwallet-pam-5.21.5
kde-plasma/kwayland-integration-5.21.5
kde-plasma/kwayland-server-5.21.5
kde-plasma/kwin-5.21.5-r1

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2021-08-17 Thread Russell

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

Russell  changed:

   What|Removed |Added

 CC|prusselltechgr...@gmail.com |

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

[kwin] [Bug 439308] New: Reproducible reset of multi-mon layout config w/Blockout II app in fullscreen ;-)

2021-06-29 Thread Chris Russell

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

Bug ID: 439308
   Summary: Reproducible reset of multi-mon layout config
w/Blockout II app in fullscreen ;-)
   Product: kwin
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: c...@encapsule.io
  Target Milestone: ---

SUMMARY
I have 3 x 4K monitors connected to a single graphics card that I have
positioned normally for a large wrap-around desktop. 
If I install the old BlockOut II game (available in Software Center) and run
that app in full-screen mode, it resets the screen layout so that all three
desktops are on top of each other (i.e. if you go to System Settings | Hardware
| Display and Monitors you'll see _one_ display monitor (w/the other two
apparently missing). Dragging the one visible monitor reveals the 2nd, and so
on... It would not seem that the app should be able to persistently alter these
settings?

STEPS TO REPRODUCE
1. Install Blockout II
2. Launch game in full-screen mode
3. Exit the game

OBSERVED RESULT
Multi-monitor screen layout data is reset persistently requiring that I go back
into Display and Monitor and re-arrange the display monitors. What's not great
about this is that it's not immediately obvious what happened or how to fix it. 

EXPECTED RESULT
No persistent changes to multi-monitor screen layout settings (i.e. settings
restored) on exit from app.

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.

[konsole] [Bug 437689] New: Konsole crashed on exit

2021-05-25 Thread Robert R. Russell

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

Bug ID: 437689
   Summary: Konsole crashed on exit
   Product: konsole
   Version: 21.04.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: rob...@rrbrussell.com
  Target Milestone: ---

Application: konsole (21.04.1)

Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.11.0-18-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.5
Distribution: Ubuntu Impish Indri (development branch)

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

I was exiting my console session. This happens every time I type exit to finish
a session.

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault

[KCrash Handler]
#4  0x7f097ec531d8 in
Konsole::PlainTextDecoder::decodeLine(Konsole::Character const*, int, unsigned
char) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#5  0x7f097ec07a11 in
Konsole::TerminalDisplay::inputMethodQuery(Qt::InputMethodQuery) const () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#6  0x7f097e0c4245 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f097e083173 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f097f15b22a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0979e64e71 in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#10 0x7f097d97bb4b in
QGuiApplicationPrivate::_q_updateFocusObject(QObject*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x7f097f192b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f097d98b4c6 in QWindow::focusObjectChanged(QObject*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7f097e0be2bb in QWidget::clearFocus() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f097e0bf378 in QWidget::~QWidget() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f097eb9ec95 in ?? () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#16 0x7f097ebfa0e3 in Konsole::TerminalDisplay::~TerminalDisplay() () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#17 0x7f097ebfa2dd in Konsole::TerminalDisplay::~TerminalDisplay() () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.21
#18 0x7f097f188063 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f097e083173 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f097f15b22a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f097f15dd01 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f097f1b4f37 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f097cd2f8eb in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f097cd82d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f097cd2d023 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f097f1b4594 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f097f159b8b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f097f162024 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f097f4c49d5 in kdemain () from
/lib/x86_64-linux-gnu/libkdeinit5_konsole.so
#30 0x7f097ece0565 in __libc_start_main (main=0x564866a2f100, argc=1,
argv=0x7fffe3cf4d38, init=, fini=,
rtld_fini=, stack_end=0x7fffe3cf4d28) at ../csu/libc-start.c:332
#31 0x564866a2f13e in ?? ()
[Inferior 1 (process 3358167) detached]

Possible duplicates by query: bug 436863, bug 429973, bug 413345, bug 403101,
bug 381101.

Reported using DrKonqi

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

[kate] [Bug 424176] New: Feature Request: Open Bookmarks in the Sidebar as a scrollable list

2020-07-13 Thread Russell

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

Bug ID: 424176
   Summary: Feature Request: Open Bookmarks in the Sidebar as a
scrollable list
   Product: kate
   Version: 20.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: prusselltechgr...@gmail.com
  Target Milestone: ---

In Kate Version 3.14.2, KDE Development Platform 4.14.2, when a user clicks the
menu item "Bookmarks", a window is displayed with an unlimited number of
columns of booksmarks. The spacing between the columns is large. There is also
a lot of space between bookmarks in a column.

In Kate Version 20.04.1, it is similar except there is a limit of 3 columns and
more space.

Rather than display the bookmarks in a window, display the bookmarks in a
scrollable list in the Sidebar (View > Tool Views > Show Sidebars).


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

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

[kate] [Bug 424172] There are no more chars for next bookmark

2020-07-13 Thread Russell

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

--- Comment #1 from Russell  ---
Something lead me done the path that the message would only appear if in Vi
Input mode. I'm not in Vi mode, so I don't think the message should be shown.

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

[kate] [Bug 424172] New: There are no more chars for next bookmark

2020-07-13 Thread Russell

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

Bug ID: 424172
   Summary: There are no more chars for next bookmark
   Product: kate
   Version: 20.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: prusselltechgr...@gmail.com
  Target Milestone: ---

SUMMARY
When the 27th bookmark is added, a red popup message is displayed in the lower
right corner with the text, "There are no more chars for the next bookmark. The
bookmarks are still added. They are also remembered when the document is closed
and re-opened. In addition, the menu item Bookmarks only displays a max of 56
bookmarks in two columns.

STEPS TO REPRODUCE
1. Open document
2. Add 27 bookmarks. Should see pop message on the 27th one.
3. Now add 30 more bookmarks for a total of 57. Look at the menu item
Bookmarks. The 57th bookmark is not listed.
4. Delete a bookmark and look at the menu item Bookmarks again. The 57th
bookmark is now visible. The bookmarks are always recorded, just not visible on
the Bookmarks menu item. Prev & Next Bookmarks do work.

OBSERVED RESULT
Popup message is displayed when more than 26 bookmarks are added. The message
goes away when a line in the document is clicked, but reappears when another
bookmark is added.

The Bookmarks menu item only displays 56 bookmarks in 2 columns. The first
column contains 26 bookmarks, the second 30 bookmarks.

EXPECTED RESULT
No popup message. Unlimited bookmarks.

All bookmarks are visible on the Bookmarks menu item.

SOFTWARE/OS VERSIONS
KDE Plasma Version:  5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
I don't know if the number of bookmarks on the Bookmarks menu item changes with
a user's Style. There is a lot space between bookmarks.

This behavior is different than Kate Version 3.14.2; Using KDE Development
Platform 4.14.2. There is no message and the Bookmarks menu item displays as
many columns as necessary to display all bookmarks. Bookmarks are unlimited.

The document is an asciidoc document and the bookmarks are placed on the titles
==, ===, , =, thus the large number.

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

[valgrind] [Bug 420780] PPCle erroneous report on strncmp use.

2020-04-29 Thread Rusty Russell

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

--- Comment #1 from Rusty Russell  ---
Michael Ellerman reports that gcc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2) needsa
"-Og" to reproduce this (though of course, the asm works).

He also produced a fix, but he's unsure if it's correct:

https://gist.github.com/mpe/fcb6aa57af7db43f27721bb52f4410ac

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

[valgrind] [Bug 420780] New: PPCle erroneous report on strncmp use.

2020-04-29 Thread Rusty Russell

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

Bug ID: 420780
   Summary: PPCle erroneous report on strncmp use.
   Product: valgrind
   Version: 3.15 SVN
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: ru...@rustcorp.com.au
  Target Milestone: ---

SUMMARY

Both valgrind 3.15 and git (60a7ebedc0b53e2cdcea112635a285d8136b68a8) report an
error. This seems similar to https://bugs.kde.org/show_bug.cgi?id=386945

Reduced from a real test cast at
https://github.com/ElementsProject/lightning/issues/3672

/* Compile with -O3 */
#include 
#include 

int main(int argc, char *argv[])
{
char *s = strdup("02aaa201000");

for (size_t i = 0; i < strlen(s); i++) {
if (!strncmp(s + i, " * ", 3))
return 1;
}
return 0;
}


STEPS TO REPRODUCE
1. Enter the above trivial program, and compile with -O3.
2. Run valgrind ./test-valgrind


OBSERVED RESULT

==12951== Memcheck, a memory error detector
==12951== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==12951== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright
info
==12951== Command: ./test-valgrind
==12951== 
==12951== Invalid read of size 4
==12951==at 0x180774: main (in /home/rusty/test-valgrind)
==12951==  Address 0x4b1004d is 13 bytes inside a block of size 16 alloc'd
==12951==at 0x48942AC: malloc (vg_replace_malloc.c:307)
==12951==by 0x499C5E3: strdup (strdup.c:42)
==12951==by 0x18071B: main (in /home/rusty/test-valgrind)
==12951== 
==12951== 
==12951== HEAP SUMMARY:
==12951== in use at exit: 16 bytes in 1 blocks
==12951==   total heap usage: 1 allocs, 0 frees, 16 bytes allocated
==12951== 
==12951== LEAK SUMMARY:
==12951==definitely lost: 16 bytes in 1 blocks
==12951==indirectly lost: 0 bytes in 0 blocks
==12951==  possibly lost: 0 bytes in 0 blocks
==12951==still reachable: 0 bytes in 0 blocks
==12951== suppressed: 0 bytes in 0 blocks
==12951== Rerun with --leak-check=full to see details of leaked memory
==12951== 
==12951== For lists of detected and suppressed errors, rerun with: -s
==12951== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)




EXPECTED RESULT

No error (except the memleak, sure).

SOFTWARE/OS VERSIONS

Linux falco.openpower.xyz 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:13
UTC 2020 ppc64le ppc64le ppc64le GNU/Linux

libc6 version: 2.27-3ubuntu1

ADDITIONAL INFORMATION

Here's the assembler from gcc -S:

.file   "test-valgrind.c"
.abiversion 2
.section".text"
.globl strncmp
.section.text.startup,"ax",@progbits
.align 2
.p2align 4,,15
.globl main
.type   main, @function
main:
.LCF0:
0:  addis 2,12,.TOC.-.LCF0@ha
addi 2,2,.TOC.-.LCF0@l
.localentry main,.-main
mflr 0
std 28,-32(1)
std 29,-24(1)
addis 3,2,.LC0@toc@ha
std 30,-16(1)
std 31,-8(1)
addi 3,3,.LC0@toc@l
addis 30,2,.LC1@toc@ha
addi 30,30,.LC1@toc@l
li 28,0
std 0,16(1)
stdu 1,-64(1)
bl strdup
nop
mr 31,3
bl strlen
nop
add 29,31,3
b .L2
.p2align 4,,15
.L17:
bl strncmp
nop
.L4:
cmpwi 7,3,0
addi 31,31,1
beq 7,.L9
.L2:
cmpld 5,31,29
rldicl 9,31,0,52
cmpdi 7,9,4092
li 5,3
mr 4,30
mr 3,31
beq 5,.L16
bge 7,.L17
lwbrx 9,0,31
lwbrx 10,0,30
rldicr 9,9,32,23
rldicr 10,10,32,23
subf. 3,10,9
cmpb 8,9,10
cmpb 7,9,28
orc 8,7,8
cntlzd 8,8
beq 0,.L4
addi 8,8,8
addi 31,31,1
rldcl 3,9,8,56
rldcl 10,10,8,56
subf 3,10,3
cmpwi 7,3,0
bne 7,.L2
.L9:
li 3,1
b .L7
.L16:
li 3,0
.L7:
addi 1,1,64
ld 0,16(1)
ld 28,-32(1)
ld 29,-24(1)
ld 30,-16(1)
ld 31,-8(1)
mtlr 0
blr
.long 0
.byte 0,0,0,1,128,4,0,0
.size   main,.-main
.section.rodata.str1.8,"aMS",@progbits,1
.align 3
.LC0:
.string "02aaa201000"
.LC1:
.string " * "
.ident  "GCC: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0"
.section.note.GNU-stack,"",@progbits

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2020-04-18 Thread Russell

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

--- Comment #330 from Russell  ---
Happened again with environment:

KDE Plasma 5.18.4 KDE Framework 5.69.0

Solution is to go to the bottom of  ~/.config/plasmashellrc and remove the
additional/invalid DisplayPort under [ScreenConnectors].

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2020-02-22 Thread Russell

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

Russell  changed:

   What|Removed |Added

 CC||prusselltechgr...@gmail.com

--- Comment #329 from Russell  ---
This entry solved my problem (Dan Duris from comment #312).

Environment:
Desktop machine with 2 permanent monitors (DisplayPort-0, DisplayPort-1) 
Manjaro KDE Distribution (based on archlinux)
KDE Plasma 5.17.5 KDE Framework 5.66.0

Resources:
File [1]: ~/.config/plasma-org.kde.plasma.desktop-appletsrc
File [2]: ~/.config/plasmashellrc

I have two monitors that are the exact same hardware. I had configured the
desktops with a different background and panel, etc., many months ago.

DisplayPort-0 has a desktop image of DarkestHour. DisplayPort-1 has a desktop
image of Path. 
The Default desktop image is Elarun.

I turned the machine on today and DisplayPort-1 reverted to the default
background, no panels, nothing else. All my customizations were gone on
DisplayPort-1.

I used the command: grep -iB6 image= File [1] 

I could see the Containments in File [1]. All three images existed in this
file. The Elarun section was in a section [Containments][151].

1. I logged out and opened a virtual terminal.
2. I made a backup of File [1] and removed any section that referenced 151.
3. I deleted any plasma cache I could find under $HOME, /var/tmp or /tmp.
4. I logged backed in.
5. No change. 
6. When I checked File [1], [Containments][151] was back with the Elarun image.

I did a lot of searching and Bug 356225 #312 helped me find a solution.

1. I went to the bottom of File [2] and there were 3 lines in the
[ScreenConnectors] section:

  0=DisplayPort-0
  1=DisplayPort-1
  2=DisplayPort-1

2. I removed 2=DisplayPort-1 and logged off/on and DisplayPort-1 had the
correct desktop configuration. 

A [151] section was still re-added to File [1], but it only contains
PreloadWeight=2. There is no Elarun image in File [1]. There are many sections
that contain only a PreloadWeight and nothing else. 

[Containments][151][Configuration]
PreloadWeight=2

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

[kate] [Bug 414997] Custom user syntax highlighting file does not override system syntax highlighting file

2019-12-21 Thread Russell

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

--- Comment #2 from Russell  ---
That worked.  

In my custom file, I changed the language attribute from 'version="2"' to
'version="992"'. The system file was at 'version="3"'. 

Would it be possible to change this to a documentation update for
https://docs.kde.org/stable5/en/applications/katepart/highlight.html.

Documentation suggestion:

+
Custom .xml highlight definition files are located in
org.kde.syntax-highlighting/syntax/ in your user folder found with
qtpaths--paths GenericDataLocation which usually is $HOME/.local/share.
Regarding the language element, if multiple .xml files on your system have the
same name attribute, the file with the highest version attribute will be
loaded. 
+

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

[kate] [Bug 414997] New: Custom user syntax highlighting file does not override system syntax highlighting file

2019-12-09 Thread Russell

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

Bug ID: 414997
   Summary: Custom user syntax highlighting file does not override
system syntax highlighting file
   Product: kate
   Version: 19.08.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: prusselltechgr...@gmail.com
  Target Milestone: ---

SUMMARY

Cannot override a system KDE Kate syntax highlighting file located at
/usr/share/org.kde.syntax-highlighting/syntax/ with a user defined KDE Kate
syntax highlighting file installed at
$HOME/.local/share/org.kde.syntax-highlighting/syntax/ per KDE KatePart
documentation.

The KDE KatePart documentation is located here:
https://docs.kde.org/trunk5/en/applications/katepart/highlight.html

The pertinent text is:
-
The formal definition, also known as the XSD you find in Syntax Highlighting
repository in the file language.xsd

Custom .xml highlight definition files are located in
org.kde.syntax-highlighting/syntax/ in your user folder found with
qtpaths--paths GenericDataLocation which usually is $HOME/.local/share
-

STEPS TO REPRODUCE
1. Create a valid custom asciidoc.xml file
2. Copy to $HOME/.local/share/org.kde.syntax-highlighting/syntax/asciidoc.xml
3. Start kate
4. Review menu paths: Tools > Highlighting > Markup and Tools > Highlighting >
Other
5. Rename /usr/share/org.kde.syntax-highlighting/syntax/asciidoc.xml
6. Repeat steps 3 and 4

OBSERVED RESULT
A user custom xml file exists at
$HOME/.local/share/org.kde.syntax-highlighting/syntax/asciidoc.xml

When the system xml file exists at
/usr/share/org.kde.syntax-highlighting/syntax/asciidoc.xml, the KDE Kate menu
appears:

Tools > Highlighting > Markup > AsciiDoc
Tools > Highlighting > Other > not there

When the system xml file does not exist at
/usr/share/org.kde.syntax-highlighting/syntax/asciidoc.xml, the KDE Kate menu
appears:

Tools > Highlighting > Markup > not there
Tools > Highlighting > Other > AsciiDoc

NOTE: 

The user custom syntax highlighting/code folding file for asciidoc has a
language element with these attributes:

-
 Highlighting > Markup > not there
Tools > Highlighting > Other > AsciiDoc

A custom user xml file should override the system xml.

SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
KATE: 19.08.3

ADDITIONAL INFORMATION

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

[kmail2] [Bug 412663] New: kmail will SEGV repeatedly if I run it and immediately exit

2019-10-06 Thread Russell Coker

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

Bug ID: 412663
   Summary: kmail will SEGV repeatedly if I run it and immediately
exit
   Product: kmail2
   Version: 5.9.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: russ...@coker.com.au
  Target Milestone: ---

Application: kmail (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-6-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

-- Information about the crash:
I just started kmail when logged in to the system via "ssh -Y localhost" and
then quit it immediately.

Every time I do this it crashes.

This is a Debian system with some Debian packages recompiled with debugging
code so the backtrace will be more useful.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc984c20f00 (LWP 26890))]

Thread 29 (Thread 0x7fc8fbfff700 (LWP 26951)):
#0  0x7fc9990fe3f9 in futex_reltimed_wait_cancelable (private=0,
reltime=0x7fc8fbffe400, expected=0, futex_word=0x7fc8fbffe5e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fc9990fe3f9 in __pthread_cond_wait_common (abstime=0x7fc8fbffe4a0,
mutex=0x7fc8fbffe598, cond=0x7fc8fbffe5c0) at pthread_cond_wait.c:533
#2  0x7fc9990fe3f9 in __pthread_cond_timedwait (cond=0x7fc8fbffe5c0,
mutex=0x7fc8fbffe598, abstime=0x7fc8fbffe4a0) at pthread_cond_wait.c:667
#3  0x7fc992b48a37 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc992b4b30a in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc992b4b3f2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fc992b4f981 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc992b50c7f in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fc992b59c81 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fc9990f7fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fc99b6c24cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fc8ea139700 (LWP 26949)):
#0  0x7fc9990fe3f9 in futex_reltimed_wait_cancelable (private=0,
reltime=0x7fc8ea138400, expected=0, futex_word=0x7fc8ea1385e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fc9990fe3f9 in __pthread_cond_wait_common (abstime=0x7fc8ea1384a0,
mutex=0x7fc8ea138598, cond=0x7fc8ea1385c0) at pthread_cond_wait.c:533
#2  0x7fc9990fe3f9 in __pthread_cond_timedwait (cond=0x7fc8ea1385c0,
mutex=0x7fc8ea138598, abstime=0x7fc8ea1384a0) at pthread_cond_wait.c:667
#3  0x7fc992b48a37 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fc992b4b30a in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fc992b4b3f2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fc992b4f981 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc992b50c7f in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fc992b59c81 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fc9990f7fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fc99b6c24cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fc91cff9700 (LWP 26932)):
#0  0x7fc99b6cf71b in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:63
#1  0x7fc99b6d14e4 in ___fprintf_chk (fp=0x7fc99b7868b0
<_IO_stdfile_2_lock>, flag=1, format=0x7fc98dce4848 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7fc98dccca5a in event_logv_ () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7fc98d34 in event_warn () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#4  0x7fc98dcce588 in  () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#5  0x7fc98dcc4329 in event_base_loop () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#6  0x7fc992b1d7cd in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fc992b3cc8b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fc992b5e204 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fc992b59c81 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7fc9990f7fa3 in start_thread (arg=) at
pthread_create.c:486
#11 0x7fc99b6c24cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7fc91d7fa700 (LWP 26931)):
#0  0x7fc9990fe3f9 in futex_reltimed_wait_cancelable (private=0,
reltime=0x7fc91d7f93c0, expected=0, futex_word=0x7fc91d7f95a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fc9990fe3f9 in __pthread_cond_wait_common (abstime=0x7fc91d7f9460,

[KScreen] [Bug 396552] OSD for shows continuously, forever.

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

--- Comment #6 from Charles Russell  ---
As for clarification, the issue occurs once I connect HDMI cable to laptop HDMI
port, it will continue even if i remove the HDMI cable. The only way to stop it
is, reboot computer or stop kscreen background service.

Thank you for you time and patience.

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

[KScreen] [Bug 396552] OSD for shows continuously, forever.

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

--- Comment #4 from Charles Russell  ---
Created attachment 113995
  --> https://bugs.kde.org/attachment.cgi?id=113995=edit
config1

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

[KScreen] [Bug 396552] OSD for shows continuously, forever.

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

--- Comment #5 from Charles Russell  ---
Created attachment 113996
  --> https://bugs.kde.org/attachment.cgi?id=113996=edit
config2

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

[KScreen] [Bug 396552] OSD for shows continuously, forever.

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

--- Comment #3 from Charles Russell  ---
Created attachment 113994
  --> https://bugs.kde.org/attachment.cgi?id=113994=edit
kscreen.log

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

[KScreen] [Bug 396552] OSD for shows continuously, forever.