[krunner] [Bug 470622] New: Krunner runs/starts whatever is currently highlighted when pressing return, but it should finish the search and then run/start

[Julian]

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

Bug ID: 470622
   Summary: Krunner runs/starts whatever is currently highlighted
when pressing return, but it should finish the search
and then run/start
Classification: Plasma
   Product: krunner
   Version: 5.27.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: d...@hackinger.io
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
I came from Gnome and used Super + Application Name to start apps, it works so
nice and is super fast and never started wrong apps for me. However with
KRunner i have the problem that i type and hit return so fast that the search
for the application name i wan't to start did not even run / finish, so it just
starts whatever is currently highlighted (can be results from previous searches
or whatever).
Imo if i press enter and the search was not performed / finished with the last
input letter before return then perform / wait for the search and start the
right thing.


STEPS TO REPRODUCE
1. Use KRunner to search for an app name
2. as soon as you fully typed the app name hit return as fast as possible

OBSERVED RESULT
KRunner starts whatever was highlighted in the search before

EXPECTED RESULT
KRunner should check if the search was completely done with all letters before
the return and then doing the run with the correct search result


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 38
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel: 6.3.4-201.fc38.x86_64 (64-bit)

ADDITIONAL INFORMATION
- I have this problem on Kubuntu and Fedora
- Wayland

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

[dolphin] [Bug 471016] New: MTP merge directories not working

[Julian]

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

Bug ID: 471016
   Summary: MTP merge directories not working
Classification: Applications
   Product: dolphin
   Version: 23.04.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: d...@hackinger.io
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Unable to merge directories on MTP access


STEPS TO REPRODUCE
1. Attach phone for MTP access and open in Dolphin
2. Copy a directory (which exists with the same name on the phone) and paste it
in the parent directory on the phone in order to merge the 2 dirs
3. See the error message: "Could not make folder /path/to/dir"

OBSERVED RESULT
Error

EXPECTED RESULT
Merge directories should work recursively

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora KDE Spin
Kernel: 6.3.7-200
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Wayland

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

[okular] [Bug 471158] New: Add a way to permanently silence "This document has forms" dialogue

[Julian]

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

Bug ID: 471158
   Summary: Add a way to permanently silence "This document has
forms" dialogue
Classification: Applications
   Product: okular
   Version: 21.12.3
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

SUMMARY
***
PDF with forms will display the dialogue "This document has forms. Click the
button to interact with them, or use View -> Show Forms." every time the
document is saved. There is no way of permanently silencing it.
***


STEPS TO REPRODUCE
1. Open a document with forms.
2. Close dialogue.
3. Make a change, e.g., highlight a sentence
4. Save your changes. The dialogue reappears.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.04, Okular 21.12.3 installed via apt.

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

[plasmashell] [Bug 460048] New: Editing Plasma panel crashes plasma

[Julian]

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

Bug ID: 460048
   Summary: Editing Plasma panel crashes plasma
Classification: Plasma
   Product: plasmashell
   Version: 5.25.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: julian.astro...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.25.5)

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.15.0-48-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
I was editing the panel and moved other panels to my screen when it suddenly
crashed. I did not have a second display but wanted to edit the second displays
panel so i just drag it over

The reporter is unsure if this crash is reproducible.

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

[New LWP 3247]
[New LWP 3354]
[New LWP 3449]
[New LWP 3514]
[New LWP 3748]
[New LWP 3878]
[New LWP 4465]
[New LWP 6995]
[New LWP 7072]
[New LWP 9253]
[New LWP 11102]
[New LWP 11103]
[New LWP 11104]
[New LWP 11105]
[New LWP 11106]
[New LWP 11107]
[New LWP 11108]
[New LWP 11109]
[New LWP 0]
[New LWP 1]
[New LWP 2]
[New LWP 3]
[New LWP 4]
[New LWP 5]
[New LWP 6]
[New LWP 7]
[New LWP 13808]
[New LWP 13818]
[New LWP 13820]
[New LWP 13821]
[New LWP 13822]
[New LWP 13979]
[New LWP 14166]
[New LWP 14878]
[New LWP 14879]
[New LWP 14910]
[New LWP 14935]
[New LWP 14958]
[New LWP 16893]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb5fa6a799f in __GI___poll (fds=0x7ffc0e671a78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="onActiveChanged",file="/usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/shellcontainmentconfiguration/Delegate.qml",fullname="/usr/share/plasma/shel".
-
(beware that frames may have been optimized out)

[Current thread is 1 (Thread 0x7fb5f67c42c0 (LWP 3225))]

Thread 40 (Thread 0x7fb4e67fc700 (LWP 16893)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55f88f6dde40) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f88f6dddf0,
cond=0x55f88f6dde18) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55f88f6dde18, mutex=0x55f88f6dddf0) at
pthread_cond_wait.c:647
#3  0x7fb5faa3d5eb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb5fc6da394 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fb5fc6da809 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fb5faa37543 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb5fa268609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb5fa6b4133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 39 (Thread 0x7fb4fcff9700 (LWP 14958)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55f88d1e0fb4) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f88d1e0f60,
cond=0x55f88d1e0f88) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55f88d1e0f88, mutex=0x55f88d1e0f60) at
pthread_cond_wait.c:647
#3  0x7fb5faa3d5eb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb5fc6da394 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fb5fc6da809 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fb5faa37543 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb5fa268609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb5fa6b4133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 38 (Thread 0x7fb4fe7fc700 (LWP 14935)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7fb5d52f6674) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fb5d52f6620,
cond=0x7fb5d52f6648) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7fb5d52f6648, mutex=0x7fb5d52f6620) at
pthread_cond_wait.c:647
#3  0x7fb5faa3d5eb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb5fc6da394 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fb5fc6da809 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fb5faa37543 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb5fa268609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb5fa6b4133 in clone () at
../sysdeps/unix/s

[kde] [Bug 460168] New: No puedo hacer que arranque Digikam 7.8.0.0

[Julian]

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

Bug ID: 460168
   Summary: No puedo hacer que arranque  Digikam 7.8.0.0
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: juliangem...@gmail.com
  Target Milestone: ---

Created attachment 152667
  --> https://bugs.kde.org/attachment.cgi?id=152667&action=edit
Esto es lo que dice

Mi problema es que después de la instalación del digicam 7.8.0.0 en mi pc
cuando quiero abrirlo no se abre pero el otro programa Showfoto si abre, mésale
un cuadro que me dice que no tiene permiso

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

[kde] [Bug 460168] No puedo hacer que arranque Digikam 7.8.0.0

[Julian]

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

--- Comment #1 from Julian  ---
Comment on attachment 152667
  --> https://bugs.kde.org/attachment.cgi?id=152667
Esto es lo que dice

No tiene suficientes privilegios es la base de datos.
No tiene asignados los privilegios siguientes: CREATE TABLE
Compruebe sus privilegios en la base de datos y reinicie digikam

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

[kde] [Bug 460168] No puedo hacer que arranque Digikam 7.8.0.0

[Julian]

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

Julian  changed:

   What|Removed |Added

 CC||juliangem...@gmail.com

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

[kdevelop] [Bug 460465] New: Theming (dark) is broken on Windows

[Julian]

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

Bug ID: 460465
   Summary: Theming (dark) is broken on Windows
Classification: Applications
   Product: kdevelop
   Version: 5.5.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: d...@hackinger.io
  Target Milestone: ---

Created attachment 152830
  --> https://bugs.kde.org/attachment.cgi?id=152830&action=edit
This is kdevelop on Windows with Breeze Dark as Theme.

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


STEPS TO REPRODUCE
1. Install the Windows binary
2. Switch to Breeze Dark
3. Look at the toolbar (still in light mode), and all the icons in the whole
application (still light mode)

OBSERVED RESULT
Toolbar and Icons are still in light mode, this makes the Windows build
unusable in dark mode.

EXPECTED RESULT
All elements should be themed as it should be and icons for dark mode should be
included and used on dark themes.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
There is no documentation how to setup the project / build on windows, so i am
not even able to contribute fixes.

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

[kdevelop] [Bug 460466] New: Dark theming broken on popups

[Julian]

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

Bug ID: 460466
   Summary: Dark theming broken on popups
Classification: Applications
   Product: kdevelop
   Version: 5.9.220801
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: d...@hackinger.io
  Target Milestone: ---

Created attachment 152831
  --> https://bugs.kde.org/attachment.cgi?id=152831&action=edit
The light mode popup

SUMMARY
Popups are in light-mode while IDE is in dark-mode


STEPS TO REPRODUCE
1. Install kdevelop 
2. Change to the Breeze Dark theme
3. Hover a Class or something in the Editor window

OBSERVED RESULT
Popup window is in light mode

EXPECTED RESULT
Popup window is in dark mode

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

ADDITIONAL INFORMATION
On Wayland

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

[kde] [Bug 479998] All apps crash on docking station connect if dbeaver is running

[Julian]

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

--- Comment #3 from Julian  ---
I don't know if plasma crashes, what i see is that every application is gone.

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

[plasmashell] [Bug 487120] New: NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6

[Julian]

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

Bug ID: 487120
   Summary: NVIDIA 3080, proprietary drivers with Wayland constant
crashes plasma 6
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: cammaratajulig...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.4)

Qt Version: 6.7.0
Frameworks Version: 6.2.0
Operating System: Linux 6.8.9-arch1-2 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
Every time I open the search bar, or do anything related to plasma, plasmashell
crashes, this only happends on wayland, but I have really poor performance on
x11 so I use wayland.

The crash can be reproduced every time.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Aborted


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 47823]
[New LWP 47817]
[New LWP 47873]
[New LWP 47871]
[New LWP 47868]
[New LWP 47872]
[New LWP 47848]
[New LWP 47821]
[New LWP 47865]
[New LWP 47894]
[New LWP 47904]
[New LWP 47867]
[New LWP 47898]
[New LWP 47883]
[New LWP 47885]
[New LWP 47896]
[New LWP 47866]
[New LWP 47893]
[New LWP 47899]
[New LWP 47887]
[New LWP 47822]
[New LWP 47954]
[New LWP 47906]
[New LWP 47902]
[New LWP 47890]
[New LWP 48144]
[New LWP 47972]
[New LWP 47958]
[New LWP 48131]
[New LWP 47901]
[New LWP 48146]
[New LWP 47949]
[New LWP 48134]
[New LWP 48138]
[New LWP 47957]
[New LWP 47955]
[New LWP 48133]
[New LWP 47965]
[New LWP 48141]
[New LWP 47959]
[New LWP 47969]
[New LWP 47950]
[New LWP 47974]
[New LWP 47981]
[New LWP 47960]
[New LWP 47911]
[New LWP 48136]
[New LWP 48142]
[New LWP 47970]
[New LWP 48145]
[New LWP 47884]
[New LWP 48147]
[New LWP 47956]
[New LWP 48148]
[New LWP 47964]
[New LWP 47891]
[New LWP 48143]
[New LWP 47908]
[New LWP 47951]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --replace'.
Program terminated with signal SIGABRT, Aborted.
#0  0x75aabdca8e44 in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x75aab28006c0 (LWP 47823))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x75aab28006c0 (LWP 47823))]

Thread 59 (Thread 0x75aa274006c0 (LWP 47951)):
#0  0x75aabdd1c39d in poll () at /usr/lib/libc.so.6
#1  0x75aabcfb78fd in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x75aabcf54f95 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x75aabe593389 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x75aabe348350 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x75aabe432a20 in QThread::exec() () at /usr/lib/libQt6Core.so.6
#6  0x75aa7aa422fe in KCupsConnection::run() () at
/usr/lib/libkcupslib.so.6.0.4
#7  0x75aabe4bb619 in ??? () at /usr/lib/libQt6Core.so.6
#8  0x75aabdca6ded in ??? () at /usr/lib/libc.so.6
#9  0x75aabdd2a0dc in ??? () at /usr/lib/libc.so.6

Thread 58 (Thread 0x75aa6d4006c0 (LWP 47908)):
#0  0x75aabdd1c910 in ppoll () at /usr/lib/libc.so.6
#1  0x75aabe4b3d83 in qt_safe_poll(pollfd*, unsigned long, QDeadlineTimer)
() at /usr/lib/libQt6Core.so.6
#2  0x75aabd754023 in ??? () at /usr/lib/libQt6Network.so.6
#3  0x75aabd6e58ac in ??? () at /usr/lib/libQt6Network.so.6
#4  0x75aabd6dd88a in QAbstractSocket::waitForReadyRead(int) () at
/usr/lib/libQt6Network.so.6
#5  0x75aabe0c2c0a in ??? () at /usr/lib/libKF6KIOCore.so.6
#6  0x75aabe1aef0d in ??? () at /usr/lib/libKF6KIOCore.so.6
#7  0x75aabe184024 in ??? () at /usr/lib/libKF6KIOCore.so.6
#8  0x75aabe4bb619 in ??? () at /usr/lib/libQt6Core.so.6
#9  0x75aabdca6ded in ??? () at /usr/lib/libc.so.6
#10 0x75aabdd2a0dc in ??? () at /usr/lib/libc.so.6

Thread 57 (Thread 0x75a9f4a006c0 (LWP 48143)):
#0  0x75aabdca34e9 in ??? () at /usr/lib/libc.so.6
#1  0x75aabdca6242 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x75aabe4bef68 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x75aabe4c0161 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x75aabe4bb619 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x75aabdca6ded in ??? () at /usr/lib/libc.so.6
#6  0x75aabdd2a0dc in ??? () at /usr/lib/libc.so.6

Thread 56 (Thread 0x75aa860006c0 (LWP 47891)):
#0  0x75aabdca34e9 in ??? () at /usr/lib/libc.so.6
#1  0x75aabdca5ed9 in pthread_cond_wait () 

[plasmashell] [Bug 487120] NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6

[Julian]

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

--- Comment #1 from Julian  ---
crash in action: https://youtu.be/HYeuXPCncC8

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

[krita] [Bug 456774] New: No animation :(

[Julian]

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

Bug ID: 456774
   Summary: No animation :(
   Product: krita
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: juliantitusdelga...@gmail.com
  Target Milestone: ---

I cant find the animation docker in dockers

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

[okular] [Bug 457245] New: Tablet or touchscreen-friendly settings

[Julian]

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

Bug ID: 457245
   Summary: Tablet or touchscreen-friendly settings
   Product: okular
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

I am using Okular on a surface-style tablet with a detachable keyboard. It
works incredibly well, kudos to the team. Some behaviors I noticed that would
make the experience even better, which might simply be flags to be set in the
background.

1. Okular has a function to keep scrolling after clicking and dragging, when
you leave off with momentum so to say (sorry I cannot describe it any better).
This makes it so that when you lift your finger off the touch screen, sometimes
the screen will go flying. I haven't really seen that in any other program, and
generally it is a welcome feature, but it is a little bit to easy to set off
with a touchscreen. You have to make a conscious effort to lift your finger
right off, or the document will unintentionally go flying. Would be great to
have an option to turn that off, or turn the sensitivity down.

2. The pinch gesture is used in wayland to go to the overview of open windows.
That work with Okular, too, but unfortunately, it will unset your viewing
settings, in particular "Fit Width". So it would be great if there was an
option to lock "Fit Width" or any other zoom setting.

3. Wouldn't be surprised if there is nothing that can be done over this, but I
seem to be unable to change textbox sizes when I add an Inline Note. I can only
move the note around.

Overall, very good experience though! I bought the device just to use Okular,
and it's great! I wish I could convey just over text how stoked I am. This is a
love letter as much as it is a feature request.

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

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

[Julian]

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

--- Comment #1 from Julian  ---
Edit: version is 1.10.70, could not find that in the drop down menu.

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

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

[Julian]

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

--- Comment #3 from Julian  ---
1. Glad to hear that scrolling is fixed.

2. Yes, turning off the pinch gesture is what I had in mind. One could imagine
some more fine grained control options regarding when zoom gets actuated, but
that might hardly be worth the effort. My main machine has a touch screen, too,
and I can attest that zooming is never something I want to do when I touch the
screen, it only ever happens on accident. Folks who look at more technical
documents with detailed diagram probably appreciate the feature more than me
though.

3. The eight squares are there. I did a little bit more of trial and error on
my two machines, and I think I figured out what the problem is. They are just
two small two hit with a finger, and even with a stylus it is very difficult to
hit them--I vaguely remember having that issue with my mouse, too, when I first
started using Okular. So the solution might be to make the clickable area a few
pixels bigger than the squares. Even when I am very intentional, I can only hit
the squares about 50% of the time on a touchscreen.

*To be more specific on the positives, if somebody from the team comes across
this*: the configurable toolbar is just a *bomb* to use on a touchscreen.
Killer feature!

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

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

[Julian]

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

--- Comment #4 from Julian  ---
Missed your last paragraph, I will open two bug reports for the two requests.

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

[okular] [Bug 457274] New: Option to turn off pinch controls for zoom

[Julian]

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

Bug ID: 457274
   Summary: Option to turn off pinch controls for zoom
   Product: okular
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

The three-finger pinch gesture is used in wayland to go to the overview of open
windows. That gesture work fine within Okular, too, but unfortunately, it also
briefly registers a two-finger pinch. So it does a brief zoom, and unsets your
zoom settings, in particular "Fit Width". So it would be great if there was an
option to lock "Fit Width" or any other zoom setting.

One could imagine some more fine grained control options regarding when zoom
gets actuated, but that might hardly be worth the effort. I have two machines,
a surface-style device and a laptop with a touchscreen, and on both the zoom
only ever happens by accident. I am sure folks who look at more technical
documents with detailed diagram probably appreciate the feature more than me,
so I think that behavior should still be there by default.

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

[okular] [Bug 457274] Option to turn off pinch controls for zoom

[Julian]

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

--- Comment #1 from Julian  ---
Edit: Version is 1.10 or 20.04, but that version is not available in the
drop-down menu at the moment.

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

[okular] [Bug 457275] New: Inline note resize box size

[Julian]

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

Bug ID: 457275
   Summary: Inline note resize box size
   Product: okular
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

I am having great trouble using the resize feature of Inline Notes on a
touchsreen, both with fingers and a styles.  The eight squares are there. I did
a little bit more of trial and error on my two machines, and I think I figured
out what the problem is. They are just too small two hit with a finger, and
even with a stylus it is very difficult to hit them--I vaguely remember having
that issue with my mouse, too, when I first started using Okular. So the
solution might be to make the clickable area a few pixels bigger than the
squares. Even when I am very intentional, I can only hit the squares about 50%
of the time on a touchscreen.

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

[okular] [Bug 432942] New: Same document opens in new window/tag

[Julian]

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

Bug ID: 432942
   Summary: Same document opens in new window/tag
   Product: okular
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

SUMMARY
When opening a document that is already open, I would expect Okular to jump to
the already open document. The default behavior seems to be to open any
document in a new window (or tab if tabs are turned on). I also tried the
--unique flag but that does not lead to the desire beavior.

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

[kde] [Bug 479998] New: All apps crash on docking station connect if dbeaver is running

[Julian]

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

Bug ID: 479998
   Summary: All apps crash on docking station connect if dbeaver
is running
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: d...@hackinger.io
  Target Milestone: ---

Created attachment 165010
  --> https://bugs.kde.org/attachment.cgi?id=165010&action=edit
var/log/messages that should contain stuff of the crash

SUMMARY
***
I do not have any backtrace, i have no clue how i should do it, every app
crashes but plasma itself keeps running, also dbeaver is a flatpak and i do not
even know if dbeaver is the issue here. I tested with Firefox alone (RPM
package) and with Firefox and dbeaver as flatpak combined and it only happened
when dbeaver is running.

I had no issues on Fedora 38 KDE, i did a complete re-install on Fedora 39 KDE
and thats where the issues started.
***


STEPS TO REPRODUCE
1. Open dbeaver flatpak
2. Connect you docking station multiple times

OBSERVED RESULT
All running apps crash

EXPECTED RESULT
...


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
- Wayland (not tested on X)
- Kernel: 6.6.9-200.fc39.x86_64

- dbeaver log in the crash window:

JVM terminated. Exit code=1
/app/jre/bin/java
-XX:+IgnoreUnrecognizedVMOptions
-Dosgi.requiredJavaVersion=17
-Dfile.encoding=UTF-8
--add-modules=ALL-SYSTEM
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED
--add-opens=java.base/java.nio.charset=ALL-UNNAMED
--add-opens=java.base/java.text=ALL-UNNAMED
--add-opens=java.base/java.time=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED
--add-opens=java.base/jdk.internal.vm=ALL-UNNAMED
--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
--add-opens=java.base/sun.security.ssl=ALL-UNNAMED
--add-opens=java.base/sun.security.action=ALL-UNNAMED
--add-opens=java.base/sun.security.util=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.jgss=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.krb5=ALL-UNNAMED
--add-opens=java.desktop/java.awt=ALL-UNNAMED
--add-opens=java.desktop/java.awt.peer=ALL-UNNAMED
--add-opens=java.sql/java.sql=ALL-UNNAMED
-Xms64m
-Xmx1024m
-jar
/app/dbeaver//plugins/org.eclipse.equinox.launcher_1.6.600.v20231106-1826.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /app/dbeaver/dbeaver
-name Dbeaver
--launcher.library
/app/dbeaver//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.800.v20231003-1442/eclipse_11802.so
-startup
/app/dbeaver//plugins/org.eclipse.equinox.launcher_1.6.600.v20231106-1826.jar
--launcher.overrideVmargs
-exitdata 8026
-vm /app/jre/bin/java
-vmargs
-XX:+IgnoreUnrecognizedVMOptions
-Dosgi.requiredJavaVersion=17
-Dfile.encoding=UTF-8
--add-modules=ALL-SYSTEM
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED
--add-opens=java.base/java.nio.charset=ALL-UNNAMED
--add-opens=java.base/java.text=ALL-UNNAMED
--add-opens=java.base/java.time=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED
--add-opens=java.base/jdk.internal.vm=ALL-UNNAMED
--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
--add-opens=java.base/sun.security.ssl=ALL-UNNAMED
--add-opens=java.base/sun.security.action=ALL-UNNAMED
--add-opens=java.base/sun.security.util=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.jgss=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.krb5=ALL-UNNAMED
--add-opens=java.desktop/java.awt=ALL-UNNAMED
--add-opens=java.desktop/java.awt.peer=ALL-UNNAMED
--add-opens=java.sql/java.sql=ALL-UNNAMED
-Xms64m
-Xmx1024m
-jar
/app/dbeaver//plugins/org.eclipse.equinox.launcher_1.6.600.v20231106-1826.jar

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

[kde] [Bug 480000] New: Scaling of Jetbrains IDEs broken since updates

[Julian]

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

Bug ID: 48
   Summary: Scaling of Jetbrains IDEs broken since updates
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: d...@hackinger.io
  Target Milestone: ---

SUMMARY
***
Something about scaling XWayland Application changed/broken since the last
couple of updates.
I have always used Jetbrains IDEs on Fedora KDE where the laptop screen is
scaled to 200% (3840x1440) and the monitor is at 100% (3440x1440) with the
settings "Apply scaling themselves" for Legacy Applications (X11), since the
last couple of updates this does not work anymore, the IDE is very small on the
monitor so it is not scaled correctly. If i move the IDE to the laptop screen
the size is normal, i have not changed any settings for this to work previously
it just worked. I have updated IntelliJ but i have not updated Android Studio
the last 3 Months and it is the same behavior for both IDEs

I cannot figure out what updates have caused this because i am not connected to
the monitor daily and i did 2 updates of all packages since i have been
connected the last time where it worked normally.

To me this looks like a bug where the IDE get told the screen scale or
whatever.
***


STEPS TO REPRODUCE
1. Open IntelliJ on up-to-date Fedora KDE with 2 different monitor scalings and
the Apply scaling themselves option
2. See the problem

OBSERVED RESULT
IDE not scaled correctly

EXPECTED RESULT
IDE scaled correctly


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 39
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
- Wayland
- Kernel: 6.6.11-200.fc39.x86_64 (64-bit)

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

[ghostwriter] [Bug 480055] New: Allow setting flags for pandoc or using custom command

[Julian]

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

Bug ID: 480055
   Summary: Allow setting flags for pandoc or using custom command
Classification: Applications
   Product: ghostwriter
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: megan.con...@kdemail.net
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

Ghostwriter would really be a lot more versatile if one could customize how the
preview is created. For instance, I was hoping I could set a resource path or
use a custom lua script. There are two basic approaches. First would be to
provide a settings fields to enter custom commands. Second is to allow yaml
headers for markdown files to be parsed by pandoc.

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

[Spectacle] [Bug 475865] New: Spectacle traps you in rectangle screenshot mode if you try to take screenshot of Citrix session window

[Julian]

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

Bug ID: 475865
   Summary: Spectacle traps you in rectangle screenshot mode if
you try to take screenshot of Citrix session window
Classification: Applications
   Product: Spectacle
   Version: 22.12.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: d...@hackinger.io
CC: k...@david-redondo.de
  Target Milestone: ---

Application: spectacle (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-34-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
I tried to take a rectangular region screenshot of something in a citrix remote
session, i was able to select the region but that was it, no way to proceed, no
way to exit until i plugged out the docking station and plugged it back in,
then spectacle crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x7f80f4f6b378 in QScreen::geometry() const () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x558534873dd4 in ?? ()
#6  0x7f80f57aec28 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f80f576bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f80f4abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f80f57a6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f80f57a7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f80f577d421 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f80f57aeee8 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f80f576bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f80f4abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f80f4abdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f80f4b157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f80f27d349d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f80f282e178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f80f27d21b0 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f80f4b14e7a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f80f4ab97cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f80f4ac1c1a in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x558534854344 in ?? ()
#24 0x7f80f4023a90 in __libc_start_call_main
(main=main@entry=0x5585348539c0, argc=argc@entry=1,
argv=argv@entry=0x7ffefc4c8c98) at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x7f80f4023b49 in __libc_start_main_impl (main=0x5585348539c0, argc=1,
argv=0x7ffefc4c8c98, init=, fini=,
rtld_fini=, stack_end=0x7ffefc4c8c88) at ../csu/libc-start.c:360
#26 0x558534854cb5 in ?? ()
[Inferior 1 (process 92913) detached]

Reported using DrKonqi

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

[okular] [Bug 434595] New: Documents always open in new window

[Julian]

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

Bug ID: 434595
   Summary: Documents always open in new window
   Product: okular
   Version: 20.12.3
  Platform: Snap
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

SUMMARY
Thanks for finally rolling out the latest version of Okular to ubuntu/snap.
Unfortunately, right now the options "Open new files in tabs" and "Switch to
existing tab if file is already open" are disregarded. When launching Okular
from the console, the following error message is printed:
```Qt: Session management error: Could not open network socket```
and
```qt.xkb.compose: failed to create compose table```

The --unique flag does not change the result.

STEPS TO REPRODUCE
1. sudo snap install okular
2. okular file.pdf
3. okular otherfile.pdf
4. okular file.pdf

OBSERVED RESULT
Three Okular windows with file.pdf open twice

EXPECTED RESULT
One Okular window with two tabs

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04
(available in About System)
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Before the recent update, tabs used to work (but the "Switch to existing tab if
file is already open" option did not exist).

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

[neon] [Bug 434595] Okular: documents always open in new window

[Julian]

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

--- Comment #1 from Julian  ---
I just installed lastest/edge via ```snap install okular --edge``` where
everything works as expected.

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

[ghostwriter] [Bug 489929] New: Syntax highlighting for yaml headers confused with horizontal rule

[Julian]

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

Bug ID: 489929
   Summary: Syntax highlighting for yaml headers confused with
horizontal rule
Classification: Applications
   Product: ghostwriter
   Version: 23.04.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: megan.con...@kdemail.net
  Reporter: barg.jul...@gmail.com
  Target Milestone: ---

SUMMARY
When you type up a markdown document with a yaml header, ghostwriter will show
the lines just above the closing `---` as though it was the document header,
bold and with bigger font.

STEPS TO REPRODUCE
Type this:

```md
---
this: is fine

this: is not fine
this: is also not
---

Main text
```

OBSERVED RESULT
The two lines above the second `---` are bold and in bigger font.

EXPECTED RESULT
Everything should have same font size, no bold.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 6.9.7-amd64 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
Sorry if that has been fixed since, I did not manage to test a more recent
version.

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

[plasmashell] [Bug 413226] New: Plasma crashed after applying settings for wallpaper slideshow

[Julian]

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

Bug ID: 413226
   Summary: Plasma crashed after applying settings for wallpaper
slideshow
   Product: plasmashell
   Version: 5.17.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jul...@langenberghe.ch
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.0)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 5.3.5-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Wallpaper settings were changed for the first time in a new activity. A folder
containing the images for the slideshow was added. Plasma crashed as soon as
the settings were applied, however the settings appear to have been applied.

- Custom settings of the application:
New activity with Folder View and Notes widgets.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f320fe3b680 (LWP 1909))]

Thread 10 (Thread 0x7f31cca84700 (LWP 2560)):
#0  0x7f3211e3fbdf in poll () from /lib64/libc.so.6
#1  0x7f32109ae3ce in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f32109ae49f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f32123e199b in QEventDispatcherGlib::processEvents
(this=0x7f31bc012620, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f321238a0db in QEventLoop::exec (this=this@entry=0x7f31cca83ca0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f32121c2021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f32121c31a2 in QThreadPrivate::start (arg=0x5629dbe75820) at
thread/qthread_unix.cpp:360
#7  0x7f321169ff2a in start_thread () from /lib64/libpthread.so.0
#8  0x7f3211e4a4af in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f31cdfff700 (LWP 2558)):
#0  0x7f32109ac967 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f32109adbfb in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f32109ae2fb in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f32109ae49f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f32123e199b in QEventDispatcherGlib::processEvents
(this=0x7f31c4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f321238a0db in QEventLoop::exec (this=this@entry=0x7f31cdffec80,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f32121c2021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f3213b4b3f5 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f32121c31a2 in QThreadPrivate::start (arg=0x5629dad68560) at
thread/qthread_unix.cpp:360
#9  0x7f321169ff2a in start_thread () from /lib64/libpthread.so.0
#10 0x7f3211e4a4af in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f31e3fff700 (LWP 2255)):
#0  0x7f3211e3b60c in read () from /lib64/libc.so.6
#1  0x7f321096070f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f32109accbe in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f32109ae372 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f32109ae49f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f32123e199b in QEventDispatcherGlib::processEvents
(this=0x7f31dc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f321238a0db in QEventLoop::exec (this=this@entry=0x7f31e3ffec60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f32121c2021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f31eca85ca8 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#9  0x7f32121c31a2 in QThreadPrivate::start (arg=0x5629d94380a0) at
thread/qthread_unix.cpp:360
#10 0x7f321169ff2a in start_thread () from /lib64/libpthread.so.0
#11 0x7f3211e4a4af in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f31fa7e5700 (LWP 2252)):
#0  0x7f321473996c in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
#1  0x7f32121c26b6 in get_thread_data () at thread/qthread_unix.cpp:238
#2  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:238
#3  0x7f32123e2081 in postEventSourcePrepare (timeout=0x0,
s=0x7f31e80239c0) at kernel/qeventdispatcher_glib.cpp:270
#4  postEventSourceCheck (source=0x7f31e80239c0) at
kernel/qeventdispatcher_glib.cpp:270
#5  0x7f32109acba9 in g_main_context_check () from
/usr/lib64/libglib-2.

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

--- Comment #3 from Julian  ---
Created attachment 124626
  --> https://bugs.kde.org/attachment.cgi?id=124626&action=edit
Crash report / backtrace on KDE Neon Developer Edition

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

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

--- Comment #4 from Julian  ---
(In reply to Christoph Feck from comment #2)
> If this is reproducible, could you add the backtrace for the crash? For more
> information, please read
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

Thank you for the advice.
I was able to reproduce the crash on the most recent KDE Neon Developer Edition
(in a virtual machine).

SOFTWARE/OS VERSIONS
Operating System: DE neon Unstable Edition
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2
Kernel Version: 5.0.0-37-generic
OS Type: 64-bit
Processors: 2 × Intel® Core™ i7-7600U CPU @ 2.80GHz
Memory: 982.8MiB of RAM

The resulting backtrace was added as an attachment to this bug report.

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

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

Julian  changed:

   What|Removed |Added

 Attachment #124626|0   |1
is obsolete||

--- Comment #5 from Julian  ---
Created attachment 124627
  --> https://bugs.kde.org/attachment.cgi?id=124627&action=edit
Crash report / backtrace on KDE Neon Developer Edition incl debug symbols for
libQt5Core

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

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

Julian  changed:

   What|Removed |Added

 Attachment #124627|Crash report / backtrace on |Crash report / backtrace on
description|KDE Neon Developer Edition  |KDE Neon Developer Edition
   |incl debug symbols for  |
   |libQt5Core  |

--- Comment #6 from Julian  ---
Comment on attachment 124627
  --> https://bugs.kde.org/attachment.cgi?id=124627
Crash report / backtrace on KDE Neon Developer Edition

incl debug symbols for libQt5Core
Gvenview version: 20.03.70

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

[gwenview] [Bug 414631] New: gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

Bug ID: 414631
   Summary: gwenview crashes with output "Floating point exception
(core dumped)"
   Product: gwenview
   Version: 19.08.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: ju-0...@gmx.ch
  Target Milestone: ---

Created attachment 124168
  --> https://bugs.kde.org/attachment.cgi?id=124168&action=edit
image file with exif data leading to gwenview crash

gwenview crashes with output "Floating point exception (core dumped)"

The picture was exported from darktable. The problem must be related to the
EXIF data embedded into the picture, as it does not crash if the exact same
image is exported without EXIF infomration.


STEPS TO REPRODUCE
1. open attached image in gwenview (better in terminal to see stdout):
   $ gwenview DSC00174_03.jpg
2. I have the Thumbnail Bar activated. The issue might be related to thumbnail
loading... 


OBSERVED RESULT
gwenview crashes with message "Floating point exception (core dumped)" printed
to stdout.

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 4.19.85-1-MANJARO
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-7600U CPU @ 2.80GHz
Memory: 19.5 GiB of RAM

Many thanks for looking into this issue.
Please let me know, if darktable is exporting a problematic / invalid EXIF tag
which is causing the problem.

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

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

Julian  changed:

   What|Removed |Added

 CC||ju-0...@gmx.ch

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

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

[Julian]

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

--- Comment #1 from Julian  ---
The problem only occurs when the Thumbnail Bar is activated.

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

[krita] [Bug 391025] overwriting a brush setting remove the tags of the brush

[Julian]

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

Julian  changed:

   What|Removed |Added

 CC||juliando...@googlemail.com

--- Comment #7 from Julian  ---
Created attachment 114397
  --> https://bugs.kde.org/attachment.cgi?id=114397&action=edit
Krita 4.1.1 Brushpreset overwriting bug

In my attached video you can observe the behaviour in krita 4.1.1

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

[plasmashell] [Bug 464771] Trying to increase screen brightness when it's already at its maximum, by scrolling over the icon or using shortcut keys, does not show the OSD

[Julian]

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

Julian  changed:

   What|Removed |Added

 CC||jul...@jcarvajal.com

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

[kate] [Bug 500382] New: Editor font could optionally follows system's "Fixed width" font

[Julian]

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

Bug ID: 500382
   Summary: Editor font could optionally follows system's "Fixed
width" font
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: jul...@jcarvajal.com
  Target Milestone: ---

SUMMARY
Feature Request: Kate's editor font configuration could include an option to
use the system "Fixed width" font.

There is precedent for this with Konsole and Kate's integrated terminal.
Konsole's default profile follows the system font. New Konsole profiles default
to the current font, but will no longer follow the system.

I think both a custom or inherited font choice make sense for this core app.

STEPS TO REPRODUCE
1. Change system "Fixed width" font.

OBSERVED RESULT
- Konsole (with default profile) and Kate's integrated terminal change to the
new font when refreshed.

EXPECTED RESULT
- Kate's editor font to change to the new font by default.

SOFTWARE/OS VERSIONS
(general)

ADDITIONAL INFORMATION

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

[kate] [Bug 500382] Editor font could optionally follows system's "Fixed width" font

[Julian]

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

--- Comment #2 from Julian  ---
(In reply to Waqar Ahmed from comment #1)
> We use system fixed font by default as well. I am not sure about introducing
> a new option in the config for this and also watching the system font so
> that we can refresh when that changes.

Am I understanding correctly that when Kate starts for the *first* time it uses
the system fixed font, but never checks again? I agree that watching for font
changes doesn't sound great. Konsole doesn't seem to watch for changes while it
runs either, rather it seems to check at startup. Is this approach more
convincing?

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

[kate] [Bug 500382] Editor font could optionally follows system's "Fixed width" font

[Julian]

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

--- Comment #4 from Julian  ---
It does seem overkill if most applications do this, I was going entirely off my
experience with Konsole's default profile experience. Thank you all for
considering. Do I go ahead and close this now? This is my first time on
bugs.kde

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

[valgrind] [Bug 372120] c++ demangler demangles symbols which are not c++

[Julian Seward]

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

--- Comment #2 from Julian Seward  ---
(In reply to Mark Wielaard from comment #1)
> Yeah, I think it would be a good idea to at least recognize the
> default (gnu_v3) style c++ mangling, which always starts with _Z.
> Something like the following should work:

I would be in favour of this, which is simple and at least makes it
less flaky than it currently is.  With the orig != NULL test added
back in for safety.

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

[valgrind] [Bug 371916] execution tree xtree concept

[Julian Seward]

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

--- Comment #18 from Julian Seward  ---
Some comments on the v3 patch:

Mostly it looks fine.  Below [1] some small comments.

Larger comments:

* I assume there are no regressions with correctness or performance
  with this, yes?  Could you do a self-host Memcheck run at some point?

* The large size of the patch concerns me a bit.  I would be happier
  if it could be split into two parts:

  (1) that creates m_xtree.c and refactors Massif to use it, but
  does not change the user-visible functionality at all.  So
  it is an implementation-only change, and

  (2) a patch that builds on (1), that supplies the new functionality.

  Is that possible, if it is not a lot of work?


[1] Small comments:



+typedef
+   struct { Addr a; const HChar* sym_name; PtrdiffT offset; }
+   Sym_Name_CacheEnt;

I prefer to have something more descriptive than just "a" for the
first field.  Since it is debug-info related, it would also be good to
clarify whether this is an SVMA or an AVMA or something else, per
comment at the top of m_debuginfo/debuginfo.c.  I suspect it's a SVMA,
in which case a good name would by "sym_svma".



+"--xtree-memory=none|allocs|full   profile heap memory in an xtree
[none]\n"
+"  and produces a report at the end of the
execution\n"
+"  none: no profiling, allocs: current
allocated\n"
+"  size/blocks, full: profile current and
cumulative\n"
+"  allocated size/blocks and freed size/blocks.\n"
+"--xtree-memory-file=   xtree memory report file
[xtmemory.kcg.%%p]\n"

This flag only has effect for tools that replace malloc, correct?  Is
it listed in the section "user options for Valgrind tools that replace
malloc:" ?



+   This file is part of Valgrind, a dynamic binary instrumentation
+   framework.
+
+   Copyright (C) 2016-2016 Philippe Waroquiers

For m_xtree.c, if there is a lot of code in there which has been moved
from massif and/or callgrind, and is not much changed, I think it
would be diplomatic to add a line or two explaining that the original
authors were Nick and/or Josef.  See the top of coregrind/m_wordfm.c for
an example.



 // growing such a block, but for consistency (it also simplifies things) we
 // ignore such reallocs as well.
+// XTREE??? why can't we just consider that a realloc of an ignored
+// alloc is just a new alloc (i.e. do not remove the old sz from the stats).

and again later.  The "XTREE???" is confusing -- I don't know what it
signifies.  Can you maybe write instead something like "PW Nov 2016,
xtree work:"?  I do that in comments from time to time.



Per previous comments in the bug re CamelCase vs snake_case, I really
have no problem mixing them.  I like to use camelcase, with a capital
first letter for type names, and snake case when function names get
long.  But no fixed rules.

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

[kde] [Bug 372655] New: Baloo crash

[Julian Schmidt]

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

Bug ID: 372655
   Summary: Baloo crash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jul...@chipmusik.de
  Target Milestone: ---

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
Whenever I start a VirtualBox VM the Baloo daemon crashes. Consistent behaviour
for several weeks now. I have Win 7 as a guest OS, but the crash happens
immediately when I hit the start VM button.  Random crashes happen without VM
use, too. But not as regular.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f729e469428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f729e46b02a in __GI_abort () at abort.c:89
#8  0x7f729cc6e002 in mdb_assert_fail (env=0x19d5260,
expr_txt=expr_txt@entry=0x7f729cc6fa5f "rc == 0",
func=func@entry=0x7f729cc70398 <__func__.7098> "mdb_page_dirty",
line=line@entry=2065, file=0x7f729cc6fa40 "mdb.c") at mdb.c:1481
#9  0x7f729cc636a5 in mdb_page_dirty (txn=0x19cb4a0, mp=) at
mdb.c:2065
#10 0x7f729cc64863 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7ffd5fc1b468, mc=0x7ffd5fc1b8e0) at mdb.c:2246
#11 0x7f729cc64ac9 in mdb_page_touch (mc=mc@entry=0x7ffd5fc1b8e0) at
mdb.c:2364
#12 0x7f729cc66704 in mdb_cursor_touch (mc=mc@entry=0x7ffd5fc1b8e0) at
mdb.c:6267
#13 0x7f729cc6a857 in mdb_cursor_del (mc=0x7ffd5fc1b8e0, flags=32) at
mdb.c:6826
#14 0x7f729cc6bdc0 in mdb_del0 (txn=0x19cb4a0, dbi=8, key=0x7ffd5fc1bcc0,
data=0x0, flags=32, flags@entry=0) at mdb.c:8305
#15 0x7f729cc6c151 in mdb_del (txn=, dbi=,
key=key@entry=0x7ffd5fc1bcc0, data=, data@entry=0x0) at
mdb.c:8265
#16 0x7f729f5fe86e in Baloo::IdFilenameDB::del
(this=this@entry=0x7ffd5fc1be00, docId=docId@entry=82775955508100099) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/idfilenamedb.cpp:127
#17 0x7f729f612ffb in
Baloo::DocumentUrlDB::replace
> (shouldDeleteFolder=..., url=..., docId=82775955508100099,
this=0x7ffd5fc1bdf0) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/documenturldb.h:96
#18
Baloo::DocumentUrlDB::del
> (shouldDeleteFolder=..., docId=82775955508100099, this=0x7ffd5fc1bdf0) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/documenturldb.h:53
#19 Baloo::WriteTransaction::removeDocument (this=,
id=id@entry=82775955508100099) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:132
#20 0x7f729f60bff9 in Baloo::Transaction::removeDocument
(this=this@entry=0x7ffd5fc1bed0, id=id@entry=82775955508100099) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:235
#21 0x00429632 in Baloo::MetadataMover::removeMetadata
(this=this@entry=0x19d5380, tr=tr@entry=0x7ffd5fc1bed0, url=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:82
#22 0x0042a012 in Baloo::MetadataMover::moveFileMetadata
(this=0x19d5380, from=..., to=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/metadatamover.cpp:53
#23 0x7f729f13cbaf in QtPrivate::QSlotObjectBase::call (a=0x7ffd5fc1c030,
r=0x7ffd5fc1c6f0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#24 QMetaObject::activate (sender=sender@entry=0x19c8510,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffd5fc1c030) at kernel/qobject.cpp:3698
#25 0x7f729f13d537 in QMetaObject::activate (sender=sender@entry=0x19c8510,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd5fc1c030)
at kernel/qobject.cpp:3578
#26 0x0042aaba in KInotify::moved (this=this@entry=0x19c8510, _t1=...,
_t2=...) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/obj-x86_64-linux-gnu/src/file/moc_kinotify.cpp:330
#27 0x0042cbff in KInotify::slotEvent (this=,
socket=) at
/build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/kinotify.cpp:421
#28 0x7f729f13cbaf in QtPrivate::QSlotObjectBase::call (a=0x7ffd5fc1c2c0,
r=0x19c8510, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#29 QMetaObject::activate (sender=sender@entry=0x19bb0a0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd5fc1c2c0) at kernel/qobject.cpp:3698
#30 0x7f729f13d537 in QMetaObject::activate (sender=sender@entry=0x19bb0a0,
m=m@entry=0x7f729f357780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5fc1c2c0)
at kernel/qobject.cpp:3578
#31 0x7f729f1bc24e in QSocketNotifier::activated

[frameworks-baloo] [Bug 372655] Baloo crash

[Julian Schmidt]

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

--- Comment #1 from Julian Schmidt  ---
the crash also happens when I copy/create a file with dolphin. Seems like a
general HD access problem.

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Julian Seward]

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

--- Comment #12 from Julian Seward  ---
Probably your least-worst option at this point is to compile the test
program in the configuration where the errors are not reported, and hope
that it all gets compiled into a single function (which it looks like
it will).  Then disassemble it and maybe we can see if the compiler
stuck in some instructions to zero out the array on the stack before
use.  That strikes me as the most likely outcome.

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

[valgrind] [Bug 352767] Wine/valgrind: Warning: noted but unhandled ioctl 0x5307 with no size/direction hints. (CDROMSTOP)

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Julian Seward  ---
(In reply to Austin English from comment #5)
> Created attachment 101938 [details]
> patch2

Committed, r16152.  Thanks for the patch.

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

[valgrind] [Bug 348616] Wine/valgrind: Warning: noted but unhandled ioctl 0x5390 with no size/direction hints. (DVD_READ_STRUCT)

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Julian Seward  ---
Committed, r16153.  Thanks for the patch.

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

[valgrind] [Bug 369459] valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)

[Julian Seward]

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

--- Comment #16 from Julian Seward  ---
I would be happy to make a generalised version of Maran's fixes,
so as to get arm{32,64} working on these cores.  I don't really
want it to be the default implementation though, since we lose 
correctness w.r.t. the ABA problem against other processes in
shared memory, relative to using the existing implementation.

Ideally I'd like to have a command line argument 

  --fallback-llsc=[no|yes|auto]

to enable the alternative implementation when necessary, with
it defaulting to |auto| so as to not to have to bother the user
with selecting flags for what is an arcane detail.  So the real
question here is how to reliably auto-detect when the fallback
implementation should be used.

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

[valgrind] [Bug 372794] LibVEX 'Assertion szBlg2 <= 3'

[Julian Seward]

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

--- Comment #1 from Julian Seward  ---
Ach, the logic there that verifies whether the instruction decode is
valid, is wrong.  Try this:

change

 // Paranoia ..
 vassert(szBlg2 <= 3);
 if (szBlg2 < 3) { vassert(tt2 == 16/*invalid*/); }
else { vassert(tt2 <= 14); }
 if (isLoad) { vassert(dd == 16/*invalid*/); }
else { vassert(dd <= 14); }
 // If we're still good even after all that, generate the IR.

by wrapping "if (gate) { .. }" around it:

if (gate) {
 // Paranoia ..
 vassert(szBlg2 <= 3);
 if (szBlg2 < 3) { vassert(tt2 == 16/*invalid*/); }
else { vassert(tt2 <= 14); }
 if (isLoad) { vassert(dd == 16/*invalid*/); }
else { vassert(dd <= 14); }
 // If we're still good even after all that, generate the IR.
}

This isn't a proper fix, though.  Can you use objdump to find the insn
it is failing on?  I'll need that to test it properly.

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

[valgrind] [Bug 371989] PCMPISTRM $0x72 and PCMPISTRI $0x12 validity bit propagation is imprecise

[Julian Seward]

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

--- Comment #4 from Julian Seward  ---
I'd fix this, if I could think of a sane way to do so.  Alas ..

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

[valgrind] [Bug 372358] vex amd64->IR: unhandled instruction bytes: 0xC5 0xFA 0x7F 0x45 0x80 0xC5 0xFA 0x7F 0x4D 0x90

[Julian Seward]

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

--- Comment #2 from Julian Seward  ---
I can't reproduce this.  Are you sure this is right?  I tried 
thusly:

int main ( void )
{
   __asm__ __volatile__(
  ".byte 0xC5, 0xFA, 0x7F, 0x45, 0x80, 0xC5, 0xFA, 0x7F, 0x4D, 0x90"
  ::: "cc","memory");
   return 0;
}

giving

004004f6 :
  4004f6:   c5 fa 7f 45 80  vmovdqu %xmm0,-0x80(%rbp)
  4004fb:   c5 fa 7f 4d 90  vmovdqu %xmm1,-0x70(%rbp)
  400500:   b8 00 00 00 00  mov$0x0,%eax
  400505:   c3  retq   
  400506:   66 2e 0f 1f 84 00 00nopw   %cs:0x0(%rax,%rax,1)
  40050d:   00 00 00 

(sure, there are 2 complete insns there, but it doesn't matter)

and although it segfaults (as it does natively), it runs correctly
through  the front end:

$ ./zzz6
Segmentation fault (core dumped)

$ v312BRANCH ./zzz6
==5911== Memcheck, a memory error detector
==5911== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==5911== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==5911== Command: ./zzz6
==5911== 
==5911== 
==5911== Process terminating with default action of signal 11 (SIGSEGV)
==5911==  Bad permissions for mapped region at address 0x400490
==5911==at 0x4004F6: main (zzz6.c:3)
==5911== 
==5911== HEAP SUMMARY:
==5911== in use at exit: 0 bytes in 0 blocks
==5911==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==5911== 
==5911== All heap blocks were freed -- no leaks are possible
==5911== 
==5911== For counts of detected and suppressed errors, rerun with: -v
==5911== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

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

[valgrind] [Bug 372358] vex amd64->IR: unhandled instruction bytes: 0xC5 0xFA 0x7F 0x45 0x80 0xC5 0xFA 0x7F 0x4D 0x90

[Julian Seward]

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

--- Comment #4 from Julian Seward  ---
Are you running this test on a machine whose CPUID says that AVX isn't
supported?  Does the test actually run natively on the machine?  I'm pretty
sure VEX will decline to decode the insn if the surrounding Valgrind tells
it this is not an AVX capable cpu.  That would explain it.

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Julian Seward]

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

--- Comment #21 from Julian Seward  ---
(In reply to Tom Hughes from comment #19)
My assumption about what __builtin_aa does is: it moves RSP down by the
specified amount, zeroes out the new area, and then returns.  Except ..
how does it return?  It must have to copy its own return address to just
below the newly allocated area, and only then return.

It would be possible to intercept it, but you'd have to hand-write a
replacement in assembly, since the above isn't doable in C.

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Julian Seward]

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

--- Comment #23 from Julian Seward  ---
(In reply to Carl Ponder from comment #22)
> I know they're not zeroing out the space.

That doesn't sync with my understanding of the discussion above.

I think your chances of getting a definitive answer are low
without providing an executable test case, with symbols, that 
we can try out.

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

[valgrind] [Bug 380942] Experimental: add MESI protocol simulation to Callgrind

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 Attachment #105965|0   |1
is obsolete||

--- Comment #3 from Julian Seward  ---
Created attachment 156636
  --> https://bugs.kde.org/attachment.cgi?id=156636&action=edit
valgrind-bug380942-Callgrind-MESI.diff-2023Feb23-rebased

Here's the same patch rebased to V sources of 23 Feb 2023.  --fair-sched=yes
has been hardwired (see comment 1) and the scheduling quantum has been reduced
from 1200 to 800, for safety.

TL;DR to build is now:

  git clone https://sourceware.org/git/valgrind.git mesi2023
  cd mesi2023
  patch -p1 < valgrind-bug380942-Callgrind-MESI.diff-2023Feb23-rebased
  ./autogen.sh
  ./configure --prefix=`pwd`/Inst --enable-only64bit
  make -j 8 all
  make -j 8 install

To run:

  /path/to/mesi2023/Inst/bin/valgrind \
 --tool=callgrind --simulate-mesi=yes 
  kcachegrind callgrind.out.

See comment 1 for more details on the RFO events.  These are the "requests for
ownership" (cache line transfers) which contain the info of interest here.

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

[kdevelop] [Bug 428688] KDevelop does not handle gdb in version 10.x properly

[Julian Wolff]

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

Julian Wolff  changed:

   What|Removed |Added

 CC||wo...@julianwolff.de

--- Comment #7 from Julian Wolff  ---
I can reproduce this with gdb 13.1, KDevelop 5.10.221203

My .gdbinit ends with a few 'skip' lines:

skip -gfi /usr/include/c++/*/*/*
skip -gfi /usr/include/c++/*/*
skip -gfi /usr/include/c++/*

KDevelop seems to to be trying to interpret the output of those lines ("File(s)
/usr/include/c++/*/*/* will be skipped when stepping.") as the version number.

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

[kdevelop] [Bug 428688] KDevelop does not handle gdb in version 10.x properly

[Julian Wolff]

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

--- Comment #8 from Julian Wolff  ---
Created attachment 158187
  --> https://bugs.kde.org/attachment.cgi?id=158187&action=edit
error message indicating that the wrong output line is interpreted as the
version number

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

[valgrind] [Bug 203380] Add a client request to register debug info for code ranges

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

  Attachment #36062|0   |1
is obsolete||
  Attachment #57659|0   |1
is obsolete||

--- Comment #6 from Julian Seward  ---
Created attachment 158504
  --> https://bugs.kde.org/attachment.cgi?id=158504&action=edit
Majorly revised and improved patch

Here's a revised and improved patch that I have used recently for profiling
webassembly applications running on SpiderMonkey.  It's still not particularly
sophisticated, but works well enough to be useful.  It retains the basic design
of earlier versions of the patch, in that it stands outside the per-object
DebugInfo mechanism used for AOT code.  Hence it is localised complexity that
does not impact the existing mechanisms.

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

[valgrind] [Bug 203380] Add a client request to register debug info for code ranges

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 Attachment #158504|0   |1
is obsolete||

--- Comment #7 from Julian Seward  ---
Created attachment 158505
  --> https://bugs.kde.org/attachment.cgi?id=158505&action=edit
Majorly revised and improved patch, take 2 (with debug printing removed)

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

[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop

[Julian Borrero]

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

--- Comment #34 from Julian Borrero  ---
I'm not affected by this bug anymore. Maybe the origial author of this bug
report could confirm?

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

[i18n] [Bug 489133] New: kscreenlocker loginctl misspelling

[Julian Klemann]

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

Bug ID: 489133
   Summary: kscreenlocker loginctl misspelling
Classification: Translations
   Product: i18n
   Version: unspecified
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: fi
  Assignee: lasse.li...@gmail.com
  Reporter: jklem...@codeweavers.com
CC: kim.enkova...@iki.fi
  Target Milestone: ---

In po/fi/kscreenlocker.po on line 72, it says "logictl" instead of "loginctl".

This is shown whenever display manager crashes and gives instructions on
logging in.

Linux: 6.9.6-arch1-1
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

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

[Elisa] [Bug 478388] New: No obvious way to close playlist on mobile

[Julian Groß]

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

Bug ID: 478388
   Summary: No obvious way to close playlist on mobile
Classification: Applications
   Product: Elisa
   Version: 23.08.4
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: julia...@posteo.de
  Target Milestone: ---

Created attachment 164084
  --> https://bugs.kde.org/attachment.cgi?id=164084&action=edit
Screenshot of the expanded playlist view

SUMMARY
There is no obvious way to close the playlist view on mobile.

STEPS TO REPRODUCE
1. Play an album
2. Expand the playlist
3. Now you are stuck and cannot leave the playlist again

OBSERVED RESULT
No obvious wax to close the playlist view.

EXPECTED RESULT
It should be possible to close the playlist view by swiping or via a toggle
button.

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

[KClock] [Bug 471064] Alarm doesn't work if the sound is muted

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

 CC||julia...@posteo.de

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

[KClock] [Bug 465346] Let the user dismiss/snooze alarms without unlocking

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

 CC||julia...@posteo.de

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

[KClock] [Bug 478415] New: Sound alarm through all speakers

[Julian Groß]

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

Bug ID: 478415
   Summary: Sound alarm through all speakers
Classification: Applications
   Product: KClock
   Version: 23.08.4
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: espi...@gmail.com
  Reporter: julia...@posteo.de
CC: hanyo...@protonmail.com
  Target Milestone: ---

SUMMARY
When using a device with multiple speakers, such as the xiaomi-wt88047 phone,
the alarm will ring from the back speaker.
If you have such a device laying with the back on something soft, such as your
mattress, the alarm might become completely inaudible.


STEPS TO REPRODUCE
1. Set alarm
2. Set device speaker side down on a mattress
3. Alarm is inaudible when it rings

OBSERVED RESULT
The alarm only rings through the main speaker.

EXPECTED RESULT
The alarm should also ring through the secondary speaker, to improve the
chances of it being heard.

ADDITIONAL INFORMATION
Other dealings with the audio system have been discussed here:
https://bugs.kde.org/show_bug.cgi?id=471064

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

[plasma-mobile] [Bug 482860] New: Gesture-only mode was removed

[Julian Groß]

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

Bug ID: 482860
   Summary: Gesture-only mode was removed
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Apparently the gesture-only mode was removed from Plasma Mobile “for the time
being”. The news mention this, but I was unable to find any open issue for
tracking purposes. https://plasma-mobile.org/2024/03/01/plasma-6/

The gesture-only mode has been extremely useful on tablets with connected
keyboards, as it almost exclusively provided functionality that was hard to do
with just keyboard shortcuts, and didn't use valuable screen space.
And example for such a device would be the Lenovo IdeaPad Duet Chromebook,
which I am happily using with Plasma Mobile at school.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-08)
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

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

[plasma-mobile] [Bug 482863] New: invisible cursor

[Julian Groß]

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

Bug ID: 482863
   Summary: invisible cursor
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Upgrading from Plasma Mobile 5 to 6 makes the cursor invisible on touchpad
devices.

OBSERVED RESULT
The cursor is always invisible, even when using the touchpad.

EXPECTED RESULT
The cursor should appear when using the touchpad, as it did in Plasma Mobile 5.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-08)
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Keep in mind that the cursor is only invisible. You can still hover over things
and interact with them.

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

[plasma-mobile] [Bug 482866] New: bottom panel covers the bottom of every maximized window

[Julian Groß]

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

Bug ID: 482866
   Summary: bottom panel covers the bottom of every maximized
window
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Upgrading from Plasma Mobile 5 to 6 caused the bottom panel to always appear
over top of any maximized window.

OBSERVED RESULT
The bottom panel overlaps with open windows.

EXPECTED RESULT
On Plasma Mobile 5, windows not maximize under the bottom panel, but leave that
part "empty".

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-08)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Gesture-only mode was enabled before the upgrade to Plasma Mobile 6.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #1 from Julian Groß  ---
Created attachment 166708
  --> https://bugs.kde.org/attachment.cgi?id=166708&action=edit
bottom panel covering the bottom of "Qalculate!"

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

[plasma-mobile] [Bug 482863] invisible cursor

[Julian Groß]

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

--- Comment #1 from Julian Groß  ---
I just noticed that the cursor appears fine on top of GTK windows. It
disappears as soon as it leaves Firefox, Gimp, Xournal++, or presumably any
other GTK application.

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

[plasma-mobile] [Bug 482869] New: on-screen keyboard appears even with physical keyboard plugged in

[Julian Groß]

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

Bug ID: 482869
   Summary: on-screen keyboard appears even with physical keyboard
plugged in
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
After upgrading from Plasma Mobile 5 to 6, the on-screen keyboard started to
appear even with a physical keyboard plugged in.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
The on-screen keyboard appears, even when a physical keyboard is present.

EXPECTED RESULT
Arguably, the on-screen keyboard should only appear when no physical keyboard
is present.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-08)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2 

ADDITIONAL INFORMATION
This issue can be worked around by just disabling the virtual keyboard manually
when a physical keyboard is attached.

Constantly attaching and detaching the physical keyboard is a realistic
workflow in a school setting, where one might switch from stylus input to
keyboard input and vice versa. Especially in the age of magnetically attaching
keyboards.

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

[plasma-mobile] [Bug 482870] New: Super-key only works on the home screen

[Julian Groß]

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

Bug ID: 482870
   Summary: Super-key only works on the home screen
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
After upgrading from Plasma Mobile 5 to 6, the super-key now only works on the
home screen.

OBSERVED RESULT
When pressing the super-key with any window open, nothing happens.

EXPECTED RESULT
In Plasma Mobile 5, pressing the super-key would open the app drawer, which was
extremely convenient for opening applications.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-08)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2 

ADDITIONAL INFORMATION
Without this super-key shortcut, there is no quick way to open the app-drawer
or go to the home screen without the Plasma-button on the bottom panel (which
would be disabled in gesture only mode).
As a workaround, one can use Alt+F2 and use the run menu to start applications.
If the attached keyboard even has an F2-key that is.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #2 from Julian Groß  ---
As a workaround, one can press Super + Up, to make the window maximize to only
the top half of the screen.

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

[plasma-mobile] [Bug 483225] New: Virtual keyboard setting does not persist across reboots

[Julian Groß]

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

Bug ID: 483225
   Summary: Virtual keyboard setting does not persist across
reboots
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
The virtual keyboard setting does not persist across reboots.


STEPS TO REPRODUCE
1. disable virtual keyboard using the top right quick-menu
2. reboot machine
3. virtual keyboard is now enabled again


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated circa 2024-03-09)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
The virtual keyboard can be enabled from the lock-screen; Meaning that
remembering the state should not have any negative impact.

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

[plasma-mobile] [Bug 483273] New: Applications cannot be removed from folders on the home screen

[Julian Groß]

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

Bug ID: 483273
   Summary: Applications cannot be removed from folders on the
home screen
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 166974
  --> https://bugs.kde.org/attachment.cgi?id=166974&action=edit
Screenshot of a folder on the home screen with two applications.

SUMMARY
When adding an application to a folder on the home screen, the remove button
stops working.


STEPS TO REPRODUCE
1. Add application to home screen.
2. Add second application on top, to create a folder.
3. Enter the folder.
4. Hold on one of the application till the remove option becomes visible.
5. Press remove.
6. Nothing happens.

OBSERVED RESULT
The remove button doesn't do anything.

EXPECTED RESULT
The remove button should just remove the application shortcut.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated circa 2024-03-09)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
The problem can be worked around by moving the application shortcut out of the
folder before deleting it.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #10 from Julian Groß  ---
Is it know what is causing this? Otherwise I might do a git bisect.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #9 from Julian Groß  ---
Still happening on Plasma Mobile 6.0.3

Operating System: postmarketOS Edge (updated 2024-04-15)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

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

[plasma-mobile] [Bug 484054] Lock screen sometimes not unlockable

[Julian Groß]

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

--- Comment #6 from Julian Groß  ---
A workaround on postmarketOS is to type `loginctl unlock-session c1` in a
different TTY (Ctrl + Alt + 2), and then switch back (Ctrl + Alt + 1).
This can also be used to test the issue. Unfortunately, I haven't been able to
find a sure-fire way of reproducing the issue. I run into it multiple times a
day though, so I can try whatever might be needed to figure this one out.

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

[plasma-mobile] [Bug 482863] invisible cursor

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

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

--- Comment #10 from Julian Groß  ---
I just updated to Plasma Mobile 6.0.3 with KDE-Frameworks 6.0.0 and Qt 6.6.3
and the cursor issue reappeared.

Looking at the desktop settings cursor theme suggests that the dark Breeze
theme cannot be applied. As in, I only get a cursor if I select another theme,
or select another theme and then switch back to dark Breeze, which will keep
the previous theme's cursor.
According to your comment https://bugs.kde.org/show_bug.cgi?id=482863#c3 dark
Breeze is just missing on postmarketOS.

This means that the issue most likely never actually got fixed and was just
worked around temporarily by switching cursor themes.
I will reopen this issue for now; Please tell me if I should rather move it to
the postmarketOS or Alpine Linux issue tracker.

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

[plasma-mobile] [Bug 482863] invisible cursor

[Julian Groß]

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

--- Comment #12 from Julian Groß  ---
(In reply to Devin Lin from comment #11)
> Is this specific to when you have the Breeze Dark theme installed?

I am convinced that it only happens with Breeze Dark. However, I haven't
specifically installed it. At least I am very sure that it came with the
default installation.

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

[plasma-mobile] [Bug 484054] Lock screen sometimes not unlockable

[Julian Groß]

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

--- Comment #4 from Julian Groß  ---
(In reply to Julian Groß from comment #3)
> I forgot to try the normal on-screen keyboard. I will try to remember next
> time it happens.

The normal on-screen keyboard also doesn't work in this scenario.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

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

--- Comment #4 from Julian Groß  ---
(In reply to Devin Lin from comment #3)
> Was fixed in 6.0.1

The issue still persists for me on:
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

Is the KDE Frameworks version outdated, or is that irrelevant?
I will attach a screenshot of how it looks on Plasma 6.0.2.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #5 from Julian Groß  ---
Created attachment 167202
  --> https://bugs.kde.org/attachment.cgi?id=167202&action=edit
Issue on Plasma 6.0.2.

Notice how the panel changed size, but still overlaps.

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

[plasma-mobile] [Bug 482870] Super-key only works on the home screen

[Julian Groß]

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

--- Comment #5 from Julian Groß  ---
I can confirm that this is fixed in Plasma Mobile 6.0.2

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

[plasma-mobile] [Bug 482863] invisible cursor

[Julian Groß]

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

--- Comment #8 from Julian Groß  ---
(In reply to Devin Lin from comment #7)
> Likely should be fixed for 6.0.2, will only close once confirmed

I needed to change the cursor theme via the desktop Plasma settings and change
it back for the cursor to appear.
Maybe the update just broke the configuration?
I might not have tried changing the theme before, because the apply button was
obstructed by the bottom panel.

Please reopen the issue if you feel that this is appropriate.

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

[plasma-mobile] [Bug 482870] Super-key only works on the home screen

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

   Version Fixed In||6.0.2

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

[plasma-mobile] [Bug 483273] Applications cannot be removed from folders on the home screen

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

   Version Fixed In||6.0.2

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

Julian Groß  changed:

   What|Removed |Added

 Attachment #167202|0   |1
is obsolete||

--- Comment #7 from Julian Groß  ---
Created attachment 167254
  --> https://bugs.kde.org/attachment.cgi?id=167254&action=edit
Issue on Plasma 6.0.2.

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

[plasma-mobile] [Bug 482866] bottom panel covers the bottom of every maximized window

[Julian Groß]

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

--- Comment #8 from Julian Groß  ---
(In reply to Devin Lin from comment #6)
> Hmm, is this a separate issue? I'm not sure if the window is actually under
> the bottom bar there (…)

Sorry, I uploaded the wrong screenshot. I have replaced it.

> (…) but the bottom bar certainly is too small. I have
> heard another report that this happened after an upgrade, could I have your
> ~/.config/plasmashellrc

I will open a separate issue for this.

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

[plasma-mobile] [Bug 483663] New: Bottom panel too small after update

[Julian Groß]

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

Bug ID: 483663
   Summary: Bottom panel too small after update
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Shell
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 167256
  --> https://bugs.kde.org/attachment.cgi?id=167256&action=edit
Screenshot of downscaled bottom panel

SUMMARY
The bottom panel is too small after updating from Plasma Mobile 5 to 6.0.0 to
6.0.2.


STEPS TO REPRODUCE (untested)
1. Get an old version of postmarketOS with Plasma Mobile 5
2. Upgrade to Plasma Mobile 6.0.2

OBSERVED RESULT
The bottom panel is downscaled.

EXPECTED RESULT
The bottom panel should look the same as in Plasma 6.0.0

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated circa 2024-03-10)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Gesture only mode was enabled in Plasma Mobile 5.
Screenshot attached.

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

[plasma-mobile] [Bug 483663] Bottom panel too small after update

[Julian Groß]

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

--- Comment #1 from Julian Groß  ---
Created attachment 167260
  --> https://bugs.kde.org/attachment.cgi?id=167260&action=edit
plasmashellrc file

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

[plasma-mobile] [Bug 483663] Bottom panel too small after update

[Julian Groß]

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

--- Comment #5 from Julian Groß  ---
(In reply to Devin Lin from comment #3)
> If you remove "navigationPanelEnabled" in ~/.config/plasmamobilerc and
> reboot, does it fix itself?

That indeed fixes the issue.

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

[plasma-mobile] [Bug 483729] New: Wifi encryption is not shown in settings

[Julian Groß]

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

Bug ID: 483729
   Summary: Wifi encryption is not shown in settings
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 167300
  --> https://bugs.kde.org/attachment.cgi?id=167300&action=edit
Security type being shown as "none"

SUMMARY
When connected to a wifi network with encryption, going into the settings and
pressing "edit", the encryption is not shown.

STEPS TO REPRODUCE
1. Connect to encrypted wifi network.
2. Go to the Plasma Mobile settings
3. Go to the wifi tab
4. Click on "Edit"
5. Click on the settings icon next to the wifi network
6. Notice how the "security type" shows up as "none"

OBSERVED RESULT
It shows up as "none" which suggests that the network isn't encrypted.

EXPECTED RESULT
It should show "WPA3 personal" or similar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated 2024-03-16)
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
In my case, I am using a WPA2/3 network, so the device is using WPA3 personal,
which isn't in the list of available options.

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

[plasma-mobile] [Bug 483729] Wifi encryption is not shown in settings

[Julian Groß]

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

--- Comment #1 from Julian Groß  ---
Created attachment 167301
  --> https://bugs.kde.org/attachment.cgi?id=167301&action=edit
Available security types

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

[plasma-mobile] [Bug 483729] Wifi encryption is not shown in settings

[Julian Groß]

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

--- Comment #2 from Julian Groß  ---
Created attachment 167302
  --> https://bugs.kde.org/attachment.cgi?id=167302&action=edit
nmtui showing the currently used/configured encryption

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

[plasma-mobile] [Bug 484054] New: Lock screen sometimes not unlockable

[Julian Groß]

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

Bug ID: 484054
   Summary: Lock screen sometimes not unlockable
Classification: Plasma
   Product: plasma-mobile
   Version: unspecified
  Platform: postmarketOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-mobile-bugs-n...@kde.org
  Reporter: julia...@posteo.de
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Sometimes, the lockscreen will stop accepting keyboard input.
This appears to be a regression in Plasma Mobile 6, since I have never observed
it in Plasma Mobile 5.
It may work at first and then just stop while typing. It feels like the input
field stops being selectable, since switching to the on-screen number keyboard
also doesn't allow any input.


STEPS TO REPRODUCE
1. lock your screen
2. try unlocking
3. sometimes it won't be possible to input the password

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS Edge (updated circa 2024-03-19)
KDE Plasma Version: 6.0.2
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.

[plasma-mobile] [Bug 484054] Lock screen sometimes not unlockable

[Julian Groß]

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

--- Comment #3 from Julian Groß  ---
(In reply to Devin Lin from comment #1)
> Both the pin-pad and keyboard stop working? Or just the keyboard? Does
> pressing the "keyboard" button refocus it?

Both, the pin-pad and the physical keyboard stop working.
I forgot to try the normal on-screen keyboard. I will try to remember next time
it happens.

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

[valgrind] [Bug 446103] New: Memcheck: `--track-origins=yes` causes extreme slowdowns for large mmap/munmap

[Julian Seward]

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

Bug ID: 446103
   Summary: Memcheck: `--track-origins=yes` causes extreme
slowdowns for large mmap/munmap
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: jsew...@acm.org
  Target Milestone: ---

Created attachment 143957
  --> https://bugs.kde.org/attachment.cgi?id=143957&action=edit
C test case

The attached test program repeatedly mmaps/munmaps a 2GB chunk of memory.
Without `--track-origins=yes`, it runs in about 0.7 seconds.  But with origin
tracking enabled, it takes 95.5 seconds, that is, it runs 137 times slower.

The problem occurs because the 2GB mmaps/munmaps cause Memcheck to perform a
set-address-range-perms operation on the area, changing it to "defined" and
then back to "noaccess".  Large-range SARPs are (highly) optimised for the
V/A-bit (normal) Memcheck shadow memory, but they are very inefficient for the
origin-tracking shadow area.  Origin-tracking shadows are kept in a 64MB 2-way
set associative cache, which is pretty fast.  But lines ejected from that are
kept in a OSet (AVL-tree) based backing store.  Because these SARP lengths
greatly exceed the size of the cache, a huge AVL tree is created, which is
very time- and space-inefficient.

This was initially noticed in
https://bugzilla.mozilla.org/show_bug.cgi?id=1742851.

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

[krita] [Bug 428080] Krita does not handle focus gain properly when switching to its workspace using a keyboard shortcut

[Julian Squires]

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

Julian Squires  changed:

   What|Removed |Added

 CC||jul...@cipht.net

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