[Spectacle] [Bug 487596] Screenshot region selection broken with fractional scaling on multi-monitor setups (X11)

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

   Version Fixed In||24.02.0

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

[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

 CC||m...@fsfe.org

--- Comment #65 from Mario Ebenhofer  ---
*** Bug 487596 has been marked as a duplicate of this bug. ***

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

[Spectacle] [Bug 487596] Screenshot region selection broken with fractional scaling on multi-monitor setups (X11)

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #4 from Mario Ebenhofer  ---


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

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

[Spectacle] [Bug 487596] Screenshot region selection broken with fractional scaling on multi-monitor setups (X11)

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

 CC||mano...@mailbox.org

--- Comment #3 from Mario Ebenhofer  ---
I've had this issue on an older version of Spectacle, too. It should be fixed
in a later version (apparently 24.02.0).
See https://bugs.kde.org/show_bug.cgi?id=462860

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

[Discover] [Bug 487442] Discover crashes when tiling and then resizing the window to a very small size.

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

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

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

[Discover] [Bug 487442] Discover crashes when tiling and then resizing the window to a very small size.

[Mario Ebenhofer]

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

--- Comment #4 from Mario Ebenhofer  ---
I just tried it again, and the part about the window being so narrow only
happens after I tiled another window there and resized it.
If I don't do that before, Discover takes up half of the screen like normal,
but I can still make it smaller and cause the crash.

Also, did you test it on such a rotated (and therefore narrow) display, too?
I also attached a screenshot of my current display configuration.

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

[Discover] [Bug 487442] Discover crashes when tiling and then resizing the window to a very small size.

[Mario Ebenhofer]

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

--- Comment #3 from Mario Ebenhofer  ---
Created attachment 169775
  --> https://bugs.kde.org/attachment.cgi?id=169775=edit
Display configuration

The issue only occurs on the 90° rotated HP Display.

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

[Discover] [Bug 487442] Discover crashes when tiling and then resizing the window to a very small size.

[Mario Ebenhofer]

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

--- Comment #1 from Mario Ebenhofer  ---
Also, I could not replicate that issue on my other monitors, only on one 90°
rotated 1920x1080 monitor, so it's probably only on very slim displays.

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

[Discover] [Bug 487442] New: Discover crashes when tiling and then resizing the window to a very small size.

[Mario Ebenhofer]

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

Bug ID: 487442
   Summary: Discover crashes when tiling and then resizing the
window to a very small size.
Classification: Applications
   Product: Discover
   Version: 6.0.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: mano...@mailbox.org
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 169749
  --> https://bugs.kde.org/attachment.cgi?id=169749=edit
Screen recording of the crash (and what I did before)

SUMMARY
Discover crashes when tiling and then resizing the window to a very small size
on Fedora 40 KDE (wayland, nvidia)

STEPS TO REPRODUCE
1. Open Discover
2. Move the window to the edge of a monitor to "tile" it to one side.
3. Resize the window to a small width (that is normally not possible without
first tiling it)

OBSERVED RESULT
Discover becomes unresponsive. It can no longer be resized, or maximized.
After clicking the "Minimize" or "Close" button, the window becomes grey and a
promt to end the process appears.
A screen recording is attached.

EXPECTED RESULT
Discover either not letting me resize it to such a small size or not crashing
when resized.

SOFTWARE/OS VERSIONS

Discover Version: 6.0.4
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.9.1-cb1.0.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

ADDITIONAL INFORMATION

Terminal output:

~$ plasma-discover
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x64994a91eed0)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:330:5: QML OverlaySheet:
Binding loop detected for property "implicitHeight"
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage:
Created graphical object was not placed in the graphics scene.
QQuickItem::stackBefore: Cannot stack QQuickRectangle(0x64994c51e2d0,
parent=0x64994a750300, geometry=0,0 0x0) before
QQuickPopupItem(0x64994a81eea0), which must be a sibling
Killed


GDB Backtrace (although I don't think that's any more useful than the console
output above):

[New Thread 0x7fff82a006c0 (LWP 16408)] 
[Thread 0x7fffb3e006c0 (LWP 16375) exited]
[Thread 0x7fff9aa006c0 (LWP 16386) exited]
[New Thread 0x7fff9aa006c0 (LWP 16413)]
[New Thread 0x7fffb3e006c0 (LWP 16414)]
[Thread 0x7fff9be006c0 (LWP 16384) exited]
[Thread 0x7fffb3e006c0 (LWP 16414) exited]
[New Thread 0x7fffb3e006c0 (LWP 16419)]
[New Thread 0x7fff9be006c0 (LWP 16420)]
[Thread 0x7fff9aa006c0 (LWP 16413) exited]
QQuickItem::stackBefore: Cannot stack QQuickRectangle(0x56576f30,
parent=0x55d741a0, geometry=0,0 0x0) before
QQuickPopupItem(0x55c60030), which must be a sibling
[Thread 0x7fff8dc006c0 (LWP 16392) exited]
[New Thread 0x7fff9be006c0 (LWP 16425)]
[Thread 0x7fff9be006c0 (LWP 16420) exited]
[New Thread 0x7fff8dc006c0 (LWP 16426)]
[Thread 0x7fffb3e006c0 (LWP 16419) exited]
[Thread 0x7fff8dc006c0 (LWP 16426) exited]
[New Thread 0x7fff8dc006c0 (LWP 16427)]
[New Thread 0x7fffb3e006c0 (LWP 16428)]
[Thread 0x7fff9be006c0 (LWP 16425) exited]
[Thread 0x7fffb3e006c0 (LWP 16428) exited]
[New Thread 0x7fffb3e006c0 (LWP 16429)]
[New Thread 0x7fff9be006c0 (LWP 16430)]
[Thread 0x7fff8dc006c0 (LWP 16427) exited]
[Thread 0x7fff9be006c0 (LWP 16430) exited]
[New Thread 0x7fff9be006c0 (LWP 16431)]
[Thread 0x7fffb3e006c0 (LWP 16429) exited]
[New Thread 0x7fff8dc006c0 (LWP 16432)]
[New Thread 0x7fff8dc006c0 (LWP 16433)]
[Thread 0x7fff8dc006c0 (LWP 16432) exited]
[New Thread 0x7fffb3e006c0 (LWP 16434)]
[Thread 0x7fff9be006c0 (LWP 16431) exited]
[New Thread 0x7fffb3e006c0 (LWP 16435)]
[Thread 0x7fffb3e006c0 (LWP 16434) exited]
[Thread 0x7fff8dc006c0 (LWP 16433) exited]
[New Thread 0x7fff9be006c0 (LWP 16436)]
[Thread 0x7fff9be006c0 (LWP 16436) exited]
[Thread 0x7fffb3e006c0 (LWP 16435) exited]
[New Thread 0x7fff9be006c0 (LWP 16437)]
[New Thread 0x7fff8dc006c0 (LWP 16438)]
[Thread 0x7fff8dc006c0 (LWP 16438) exited]
[New Thread 0x7fff8dc006c0 (LWP 16439)]
[New Thread 0x7fffb3e006c0 (LWP 16440)]
[Thread 0x7fff9be006c0 (LWP 16437) exited]
[Thread 0x7fffb3e006c0 (LWP 16440) exited]
[New Thread 0x7fffb3e006c0 (LWP 16441)]
[Thread 0x7fff8dc006c0 (LWP 16439) exited]
[New Thread 0x7fff9be006c0 (LWP 16442)]
[Thread 0x7fff9be006c0 (LWP 16442) exited]
[New Thread 0x7fff9be006c0 (LWP 16443)]
[New Thread 0x7fff8dc006c0 (LWP 16444)]
[Thread 0x7fffb3e006c0 (LWP 16441) exited]
[Thread 0x7fff8dc006c0 (LWP 16444) exited]
[New Thread 0x7fff8dc006c0 (LWP 16445)]
[New Thread 0x7fffb3e006c0 (LWP 16446)]
[Thread 0x7fff9be006c0 (LWP 16443) exited]

[dragonplayer] [Bug 486753] New: Dragon Player segfaults upon opening

[Mario Borna Mjertan]

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

Bug ID: 486753
   Summary: Dragon Player segfaults upon opening
Classification: Applications
   Product: dragonplayer
   Version: 24.02.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mariobo...@outlook.com
CC: myr...@kde.org, sit...@kde.org
  Target Milestone: ---

Application: dragon (24.02.0)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.0-0.rc6.49.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)"
DrKonqi: 6.0.0 [CoredumpBackend]

-- Information about the crash:
Dragon segfaults upon opening with various files. Happens consistently.

The crash can be reproduced every time.

-- Backtrace:
Application: Dragon Player (dragon), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 158992]
[New LWP 158958]
[New LWP 158959]
[New LWP 158964]
[New LWP 158999]
[New LWP 158998]
[New LWP 158961]
[New LWP 158960]
[New LWP 158954]
[New LWP 158981]
[New LWP 159002]
[New LWP 159010]
[New LWP 158963]
[New LWP 158982]
[New LWP 159009]
[New LWP 159005]
[New LWP 158980]
[New LWP 159007]
[New LWP 159006]
[New LWP 159004]
[New LWP 158985]
[New LWP 158991]
[New LWP 158993]
[New LWP 158983]
[New LWP 158994]
[New LWP 158962]
[New LWP 159000]
[New LWP 159003]
[New LWP 159001]
[New LWP 158965]
[New LWP 158979]
[New LWP 159008]
[New LWP 158966]
[New LWP 158984]
[New LWP 158986]
[New LWP 159011]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/dragon
/home/mbm/Downloads/Ben.Fogle.New.Lives.in.the.Wild.S18E08.1080'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fb0680ab184 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fb0198006c0 (LWP 158992))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fb0198006c0 (LWP 158992))]

Thread 36 (Thread 0x7fafd3e006c0 (LWP 159011)):
#0  0x7fb06812919d in syscall () at /lib64/libc.so.6
#1  0x7fb067bd9540 in g_cond_wait_until () at /lib64/libglib-2.0.so.0
#2  0x7fb067b464f3 in g_async_queue_pop_intern_unlocked () at
/lib64/libglib-2.0.so.0
#3  0x7fb067bad1ca in g_thread_pool_thread_proxy.lto_priv () at
/lib64/libglib-2.0.so.0
#4  0x7fb067bab453 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7fb0680a91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fb06812b3ac in clone3 () at /lib64/libc.so.6

Thread 35 (Thread 0x7fb0457ff6c0 (LWP 158986)):
#0  0x7fb0680a5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fb0680a8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fb047fad677 in vlc_cond_timedwait () at /lib64/libvlccore.so.9
#3  0x7fb047f75b07 in MainLoop () at /lib64/libvlccore.so.9
#4  0x7fb047f7685a in Run () at /lib64/libvlccore.so.9
#5  0x7fb0680a91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fb06812b3ac in clone3 () at /lib64/libc.so.6

Thread 34 (Thread 0x7fb0316006c0 (LWP 158984)):
#0  0x7fb06812b7b2 in epoll_wait () at /lib64/libc.so.6
#1  0x7fb04eb3b3e6 in impl_pollfd_wait () at
/usr/lib64/spa-0.2/support/libspa-support.so
#2  0x7fb04eb2d0c1 in loop_iterate () at
/usr/lib64/spa-0.2/support/libspa-support.so
#3  0x7fb047e990c7 in do_loop () at /lib64/libpipewire-0.3.so.0
#4  0x7fb0680a91f7 in start_thread () at /lib64/libc.so.6
#5  0x7fb06812b3ac in clone3 () at /lib64/libc.so.6

Thread 33 (Thread 0x7fb044c006c0 (LWP 158966)):
#0  0x7fb0680a5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fb0680a8329 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7fb04c69 in cnd_wait () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7fb04c67b9ab in util_queue_thread_func () at
/usr/lib64/dri/radeonsi_dri.so
#4  0x7fb04c69dd0c in impl_thrd_routine () at
/usr/lib64/dri/radeonsi_dri.so
#5  0x7fb0680a91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fb06812b3ac in clone3 () at /lib64/libc.so.6

Thread 32 (Thread 0x7fafe8c006c0 (LWP 159008)):
#0  0x7fb0680a5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fb0680a8329 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libc.so.6
#2  0x7fb00f0b9545 in frame_worker_thread.lto_priv () at
/lib64/libavcodec.so.60
#3  0x7fb0680a91f7 in start_thread () at /lib64/libc.so.6
#4  0x7fb06812b3ac in clone3 () at /lib64/libc.so.6

[neon] [Bug 486087] Mouse pointer has blue-ish shaddow/halo when Night Light kicks in

[Mario Splivalo]

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

--- Comment #1 from Mario Splivalo  ---
Created attachment 168880
  --> https://bugs.kde.org/attachment.cgi?id=168880=edit
Screenshot of a blue pointer, another one

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

[neon] [Bug 486087] New: Mouse pointer has blue-ish shaddow/halo when Night Light kicks in

[Mario Splivalo]

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

Bug ID: 486087
   Summary: Mouse pointer has blue-ish shaddow/halo when Night
Light kicks in
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
CC: j...@jriddell.org, neon-b...@kde.org
  Target Milestone: ---

Created attachment 168879
  --> https://bugs.kde.org/attachment.cgi?id=168879=edit
Screenshot of blue pointer.

SUMMARY
With Night Light enabled and activated the mouse pointer shows blue-ish shade
or halo around it.

STEPS TO REPRODUCE
1.  Enable Night Light
2.  Force Night Light to activate

OBSERVED RESULT
The mouse pointer has bloue shade around it. 

EXPECTED RESULT
The mouse pointer should not have blue shade around it. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 6.0
KDE Plasma Version: 6.0.4 
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Linux: 6.5.0-28-generic (64-bit)
Nvidia drivers: 550.67
Wayland 

ADDITIONAL INFORMATION
This bug did not exist on Plasma 6.0.3, only after upgrading to 6.0.4 the blue
'shade' became visible.
(The attached screenshot is taken by phone because I can't get blue shade using
Spectacle).

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

[neon] [Bug 485474] New: hexchat context menu also in top-left corner of the screen

[Mario Splivalo]

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

Bug ID: 485474
   Summary: hexchat context menu also in top-left corner of the
screen
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
CC: j...@jriddell.org, neon-b...@kde.org
  Target Milestone: ---

Created attachment 168447
  --> https://bugs.kde.org/attachment.cgi?id=168447=edit
screenshot of xchat context menu in a wrong position

SUMMARY

hexchat, an irc client, when running, has context menu not just in the System
Tray icon, but also on upper-left corner of the screen (see the attached
image). This, of course, creates issues when there is an top-screen panel
housing, say, QuickLauncher positioned on the left side of that top-screen
panel.

Hexchat's icon in system tray has context menu on right-click, where on
left-click it hides/shows (minimizes/restores) the hexchat application. But,
clicking in the upper left corner (or 5-10 pixels down/right of the top-left
corner) has the same behavior as when clicking on the icon in the system tray. 

When I right-click on hexchat icon in system tray the context menu is shown at
the correct place. It seems like hexchat icon is presenting itself at two
places - in the system tray and in the upper left corner of the screen (just
without the icon). 

I've only observed this with hexchat. 

This happens on Plasma6 with kwin_wayland (haven't tested on Plasma6 and Xorg). 


STEPS TO REPRODUCE
1. Run hexchat (doesn't have to be configured, context menu always exists)
2. Right-click close to upper-left corner of the screen

OBSERVED RESULT
Hexchat context menu is shown. 


EXPECTED RESULT
Desktop context menu should be shown (or panel context menu, or whatever is on
that part of the display). 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version:  6.0.0
Qt Version:  6.7.0

ADDITIONAL INFORMATION
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: Wayland
CPU:  Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 31,3 GiB of RAM
GPU: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2
Graphics Driver Version:  nvidia 535.171.04

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

[dolphin] [Bug 484991] Dolphin crashes on FreeBSD when dragging file or folder towards location/navigation bar

[Mario Ebenhofer]

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

--- Comment #1 from Mario Ebenhofer  ---
Not really related to this issue, but I just noticed that the crash handler
continued the "loading screen" for submitting the bugreport forever, even after
it's already available here.
I'm not really sure what I should do about that. Is it worth creating another
bugreport? I think it's pretty hard to reproduce without sending more bug
reports with the crash handler...

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

[dolphin] [Bug 484991] Dolphin crashes on FreeBSD when dragging file or folder towards location/navigation bar

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

  Component|general |bars: location

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

[dolphin] [Bug 484991] New: Dolphin crashes on FreeBSD when dragging file or folder towards location/navigation bar

[Mario Ebenhofer]

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

Bug ID: 484991
   Summary: Dolphin crashes on FreeBSD when dragging file or
folder towards location/navigation bar
Classification: Applications
   Product: dolphin
   Version: 23.08.4
  Platform: FreeBSD Ports
OS: FreeBSD
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mano...@mailbox.org
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (23.08.4)

Qt Version: 5.15.12
Frameworks Version: 5.112.0
Operating System: FreeBSD 14.0-RELEASE amd64
Windowing System: X11
Distribution (Platform): FreeBSD Ports
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Dolphin crashes when I move any file or folder towards the navigation bar
(where the file path is shown).
The crash happens as soon as the file overlaps with the bar.

I installed kde plasma and discover from the standard FreeBSD repositories
(using pkg install).

The crash can be reproduced every time.

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

(lldb) process attach --pid 4544
Process 4544 stopped
* thread #1, name = 'dolphin', stop reason = signal SIGSTOP
frame #0: 0x0008415b5e88 libc.so.7`__sys_wait4 + 8
libc.so.7`__sys_wait4:
->  0x8415b5e88 <+8>:  syscall 
0x8415b5e8a <+10>: jb 0x8415b29c8
0x8415b5e90 <+16>: retq   
0x8415b5e91:   int3   
  thread #2, name = 'dolphin', stop reason = signal SIGSTOP
frame #0: 0x0008415b5c2a libc.so.7`__sys_poll + 10
libc.so.7`__sys_poll:
->  0x8415b5c2a <+10>: jb 0x8415b29c8
0x8415b5c30 <+16>: retq   
0x8415b5c31:   int3   
0x8415b5c32:   int3   
  thread #3, name = 'dolphin', stop reason = signal SIGSTOP
frame #0: 0x0008415b5b6a libc.so.7`__sys_kevent + 10
libc.so.7`__sys_kevent:
->  0x8415b5b6a <+10>: jb 0x8415b29c8
0x8415b5b70 <+16>: retq   
0x8415b5b71:   int3   
0x8415b5b72:   int3   
  thread #4, name = 'dolphin', stop reason = signal SIGSTOP
frame #0: 0x0008415b5c2a libc.so.7`__sys_poll + 10
libc.so.7`__sys_poll:
->  0x8415b5c2a <+10>: jb 0x8415b29c8
0x8415b5c30 <+16>: retq   
0x8415b5c31:   int3   
0x8415b5c32:   int3
Executable module set to "/usr/local/bin/dolphin".
Architecture set to: x86_64-unknown-freebsd14.0.
(lldb) settings set term-width 200
(lldb) thread info
thread #1: tid = 107437, 0x0008415b5e88 libc.so.7`__sys_wait4 + 8, name =
'dolphin', stop reason = signal SIGSTOP

(lldb) bt all
* thread #1, name = 'dolphin', stop reason = signal SIGSTOP
  * frame #0: 0x0008415b5e88 libc.so.7`__sys_wait4 + 8
frame #1: 0x000849688adc libthr.so.3`___lldb_unnamed_symbol727 + 60
frame #2: 0x00082d4fe29c libKF5Crash.so.5`___lldb_unnamed_symbol229 +
332
frame #3: 0x00082d4fdd7b
libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1147
frame #4: 0x00084968653f libthr.so.3`___lldb_unnamed_symbol684 + 207
frame #5: 0x000849685afb libthr.so.3`___lldb_unnamed_symbol665 + 315
frame #6: 0x000820e102d3
frame #7: 0x00083e8d3460 libQt5Widgets.so.5`QWidget::event(QEvent*) +
1328
frame #8: 0x00083ea1be44 libQt5Widgets.so.5`QPushButton::event(QEvent*)
+ 180
frame #9: 0x00083e899af3
libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 259
frame #10: 0x00083e89b291
libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 1537
frame #11: 0x000840624161
libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 177
frame #12: 0x00083e8f1f4a
libQt5Widgets.so.5`___lldb_unnamed_symbol14092 + 1210
frame #13: 0x00083e8ef3bb
libQt5Widgets.so.5`___lldb_unnamed_symbol14079 + 747
frame #14: 0x00083e899af3
libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 259
frame #15: 0x00083e89ae9e
libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 526
frame #16: 0x000840624161
libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 177
frame #17: 0x00083d4e97e0
libQt5Gui.so.5`QGuiApplicationPrivate::processDrag(QWindow*, QMimeData const*,
QPoint const&, QFlags, QFlags,
QFlags) + 672
frame #18: 0x00083d4c7703
libQt5Gui.so.5`QWindowSystemInterface::handleDrag(QWindow*, QMimeData const*,
QPoint const&, QFlags, QFlags,
QFlags) + 275
frame #19: 0x00086bb66e95 libQt5XcbQpa.so.5`___lldb_unnamed_symbol3646
+ 1029
frame #20: 0x00086bb66192 libQt5XcbQpa.so.5`___lldb_unnamed_symbol3641
+ 1698
frame #21: 0x00083d529be7
libQt5Gui.so.5`QBasicDrag::eventFilter(QObject*, QEvent*) + 807
frame #22: 0x000840624380
libQt5Core.so.5`QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*,
QEvent*) + 224
frame #23: 

[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #9 from Mario Ray Mahardhika  ---
6.0.2 arrives to Neon, and I can confirm it's fixed.

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

[kwordquiz] [Bug 483117] New: Error when search for download new stuff

[Mario]

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

Bug ID: 483117
   Summary: Error when search for download new stuff
Classification: Applications
   Product: kwordquiz
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: mojo...@gmail.com
CC: aa...@kde.org
  Target Milestone: ---

SUMMARY
Gives a unspecific error when search is used but still produces results.

STEPS TO REPRODUCE
1. open kwordquiz
2. go to download deck
3. search someting and hit enter

OBSERVED RESULT
get a box with:
An Error Occurred
Unknown Open Collaboration Service API error.(0)


EXPECTED RESULT
should not throw an error

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

ADDITIONAL INFORMATION
terminal extract:
QList("/home/mario/.local/share/kvtml/spanisch.kvtml")
kf.coreaddons: Could not lock file:
"/home/mario/.local/share/stalefiles/kwordquiz/spanisch.kvtmlvR7file_%2Fhome%2Fmario%2F.local%2Fshare%2FkvtmlEUNcuvR7"
KEduVocKvtmlReader for kvtml version 1 files started.
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
addLanguage(  0 ,  "de" ):  "German"
addLanguage(  1 ,  "es" ):  "Spanish"
Reading user defined tense description:  "Presente"
 Add tense:  "#1"  -  "Presente"
Reading user defined tense description:  "Participio"
 Add tense:  "#2"  -  "Participio"
Reading user defined tense description:  "Gerundio"
 Add tense:  "#3"  -  "Gerundio"
Reading user defined tense description:  "Pretérito perfecto"
 Add tense:  "#4"  -  "Pretérito perfecto"
Reading user defined tense description:  "Pretérito indefinido"
 Add tense:  "#5"  -  "Pretérito indefinido"
Reading user defined tense description:  "Futuro imperfecto"
 Add tense:  "#6"  -  "Futuro imperfecto"
Reading user defined tense description:  "Condicional simple"
 Add tense:  "#7"  -  "Condicional simple"
Reading user defined tense description:  "Imperativo"
 Add tense:  "#8"  -  "Imperativo"
Reading user defined tense description:  "Subjuntivo presente"
 Add tense:  "#9"  -  "Subjuntivo presente"
QIODevice::read (QNetworkReplyHttpImpl): device not open
parseList():: XML Error:  "Premature end of document." 
In xml name "" with text "" at offset:
 0 
In XML:
 ""
qrc:/qml/SettingsPage.qml:10:1: QML SettingsPage: Created graphical object was
not placed in the graphics scene.
file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:1014:5: QML RowLayout:
StackView has detected conflicting anchors. Transitions may not execute
properly.
QIODevice::read (QNetworkReplyHttpImpl): device not open
parseList():: XML Error:  "Premature end of document." 
In xml name "" with text "" at offset:
 0 
In XML:
 ""

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

[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #7 from Mario Ray Mahardhika  ---
(In reply to Zane from comment #6)
> This seems similar to what I'm seeing in
> https://bugs.kde.org/show_bug.cgi?id=482064
> On Wayland, the frame rate is half of the refresh rate.

Could be, same Plasma 6 Wayland, despite running on totally different platform.
So we know it's not platform specific.

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

[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #5 from Mario Ray Mahardhika  ---
> Not sure if this would help the OP as his issue occurs with only one display, 
> but hopefully this helps someone with a setup similar to mine.

Not directly, but should help developers isolating the potential cause. I also
happen to have a USB-C to DP cable which I can use to test on my external
monitor, which indeed doesn't exhibit the same problem. High refresh rate
(170Hz) even works just fine. So maybe the scope can be reduced to HDMI and DSI
connector, leaving DisplayPort out.

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

[plasmashell] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #2 from Mario Ray Mahardhika  ---
`sudo dmesg | i915` is the same for both sessions, however `xrandr --verbose`
shows some differences:

Wayland
===
Screen 0: minimum 16 x 16, current 1920 x 1200, maximum 32767 x 32767
DSI-1 connected primary 1920x1200+0+0 (0x23) right (normal left inverted right
x axis y axis) 141mm x 226mm
Identifier: 0x21
Timestamp:  18133
Subpixel:   horizontal rgb
Gamma:  inf:inf:inf
Brightness: 0.40
Clones:
CRTC:   0
CRTCs:  0
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
RANDR Emulation: 1 
non-desktop: 0 
supported: 0, 1
  1200x1920 (0x23) 161.250MHz -HSync +VSync *current +preferred
h: width  1200 start 1288 end 1416 total 1632 skew0 clock  98.81KHz
v: height 1920 start 1923 end 1933 total 1978   clock  49.95Hz

X11
===
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384
DSI-1 connected primary 1920x1200+0+0 (0x47) right (normal left inverted right
x axis y axis) 0mm x 0mm
Identifier: 0x41
Timestamp:  173498
Subpixel:   horizontal rgb
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
_KDE_SCREEN_INDEX: 1 
panel orientation: Normal 
supported: Normal, Upside Down, Left Side Up, Right Side Up
scaling mode: Full aspect 
supported: Full, Center, Full aspect
link-status: Good 
supported: Good, Bad
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
0 1 
CONNECTOR_ID: 185 
supported: 185
non-desktop: 0 
range: (0, 1)
  1200x1920 (0x47) 136.887MHz +HSync +VSync *current +preferred
h: width  1200 start 1240 end 1252 total 1268 skew0 clock 107.96KHz
v: height 1920 start 2125 end 2127 total 2159   clock  50.00Hz

No idea if these matter, though.

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

[plasmashell] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #1 from Mario Ray Mahardhika  ---
Created attachment 166268
  --> https://bugs.kde.org/attachment.cgi?id=166268=edit
UFO test on Wayland

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

[plasmashell] [Bug 482178] New: Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

Bug ID: 482178
   Summary: Wayland renders the whole desktop in half refresh rate
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: leledumbo_c...@yahoo.co.id
CC: notm...@gmail.com
  Target Milestone: 1.0

Created attachment 166267
  --> https://bugs.kde.org/attachment.cgi?id=166267=edit
UFO test on X11

SUMMARY
***
Choosing Plasma Wayland session on Plasma 6.0 will present a desktop that has
everything rendered in half of what the screen refresh rate is.
***


STEPS TO REPRODUCE
1. In SDDM login screen, choose Plasma (Wayland) session
2. Do anything: move mouse, open apps, whatever, it will look choppy

OBSERVED RESULT
Any changes on the desktop are choppy

EXPECTED RESULT
Any changes on the desktop are smooth

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

ADDITIONAL INFORMATION

$ inxi -F
System:
  Host: LeleChuwi Kernel: 6.6.5-060605-generic x86_64 bits: 64
Desktop: KDE Plasma 6.0.0 Distro: KDE neon 22.04 6.0
Machine:
  Type: Laptop System: CHUWI Innovation And (ShenZhen) product: MiniBook X
v: N/A serial: 
  Mobo: N/A model: N/A serial: 
UEFI: American Megatrends LLC. v: DNN20A V2.03 date: 12/28/2023
Battery:
  ID-1: BAT0 charge: 28.9 Wh (100.0%) condition: 28.9/28.9 Wh (100.0%)
CPU:
  Info: quad core model: Intel N100 bits: 64 type: MCP cache: L2: 2 MiB
  Speed (MHz): avg: 801 min/max: 700/801 cores: 1: 801 2: 801 3: 801 4: 801
Graphics:
  Device-1: Intel driver: i915 v: kernel
  Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 resolution: 1920x1200~50Hz
  OpenGL: renderer: Mesa Intel Graphics (ADL-N)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2
Audio:
  Device-1: Intel driver: snd_hda_intel
  Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo
  Sound Server-1: ALSA v: k6.6.5-060605-generic running: yes
  Sound Server-2: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel driver: iwlwifi
  IF: wlp0s20f3 state: up mac: c0:a5:e8:40:76:62
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: C0:A5:E8:40:76:66 bt-v: 3.0
Drives:
  Local Storage: total: 476.94 GiB used: 22.99 GiB (4.8%)
  ID-1: /dev/nvme0n1 model: KPART512GBC2DVT size: 476.94 GiB
Partition:
  ID-1: / size: 455.73 GiB used: 22.99 GiB (5.0%) fs: ext4
dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 6.1 MiB (2.0%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 12.56 GiB used: 0 KiB (0.0%)
dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 217 Uptime: 26m Memory: 11.43 GiB used: 3.22 GiB (28.2%)
  Shell: Bash inxi: 3.3.13

Attached is a proof using UFO framerate test (https://www.testufo.com/), named
after the corresponding session.

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

[neon] [Bug 480809] xdg-utils ships broken /usr/bin/xdg-icon-resource - some packages fail to install/upgrade/remove

[Mario Splivalo]

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

--- Comment #4 from Mario Splivalo  ---
(In reply to redgreen925 from comment #3)
> (In reply to redgreen925 from comment #2)
> > Thanks for reporting this bug it gave me the solution when it error-ed out
> > on my install with the same problem as reported. The removing of the
> > offending backtick on line 946 as posted by Mario allows for configuring of
> > the google chrome which it stopped in my case. Thank you for taking the time
> > to post your solution to the problem Mario.
> 
> Seems to have been fixed with the update to
> xdg-utils_1.2.1-0xneon+22.04+jammy+release+build5_all.deb that was installed
> today. Also had update to google chrome  to again install for some reason in
> a strange coincidence. It installed perfectly this time after I installed
> xdg-utils first to see if the brokenness continued when installing the
> chrome after it. Thanks for the fixed package whoever did it.

Indeed, the ...build5 version of the package fixed the issue!

Mario

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

[neon] [Bug 480809] New: xdg-utils ships broken /usr/bin/xdg-icon-resource - some packages fail to install/upgrade/remove

[Mario Splivalo]

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

Bug ID: 480809
   Summary: xdg-utils ships broken /usr/bin/xdg-icon-resource -
some packages fail to install/upgrade/remove
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1.  Upgrade packages to latest version (apt update && apt dist-upgrade)
2.  Upgrade of some packages fail (google-chrome-stable and brave-browser in my
case)

OBSERVED RESULT
Running 'apt dist-upgrade', when upgrading google-chrome-stable and
brave-browser fail like this:

Setting up google-chrome-stable (121.0.6167.139-1) ...
/usr/bin/xdg-icon-resource: 12: Syntax error: end of file unexpected (expecting
";;")
dpkg: error processing package google-chrome-stable (--configure):
 installed google-chrome-stable package post-installation script subprocess
returned error exit status 2
Setting up plasma-discover (5.27.10.1-0xneon+22.04+jammy+release+build42) ...
Setting up brave-browser (1.62.156) ...
/usr/bin/xdg-icon-resource: 12: Syntax error: end of file unexpected (expecting
";;")
dpkg: error processing package brave-browser (--configure):
 installed brave-browser package post-installation script subprocess returned
error exit status 2


EXPECTED RESULT
Installation/upgrade of mentioned packages completes without an error.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.27
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION

xdg-utils package ships broken /usr/bin/xdg-icon-resource script, which error
out while being executed by post-inst scripts from google-chrome-stable and
brave-browser (in my case - I imagine there are other situations where this
would be an issue).

In line 946 of  /usr/bin/xdg-icon-resource there is a backtick which causes
sh/dash to error out when running the script.
Once the backtick is removed, script works as expected, and package
installation can continue.

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

[XWaylandVideoBridge] [Bug 479672] New: HiDPI monitor showing small section of the screen

[Mario]

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

Bug ID: 479672
   Summary: HiDPI monitor showing small section of the screen
Classification: Applications
   Product: XWaylandVideoBridge
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: a...@ellugar.co
CC: aleix...@kde.org, k...@davidedmundson.co.uk
  Target Milestone: ---

STEPS TO REPRODUCE
1. Launch XWaylandVideoBridge on a monitor with 2.0 scale factor

OBSERVED RESULT
Only a 4th section of the screen is cast

EXPECTED RESULT
The whole screen should be cast


SOFTWARE/OS VERSIONS
OS: Arch Linux x86_64
Kernel: 6.1.71-1-lts 
WM: sway

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

Mario  changed:

   What|Removed |Added

   Platform|Other   |Arch Linux

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

Mario  changed:

   What|Removed |Added

Version|18.04.3 |23.08.4

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

--- Comment #18 from Mario  ---
Created attachment 164634
  --> https://bugs.kde.org/attachment.cgi?id=164634=edit
Wsdd log

Wsdd log with the next tool:

https://github.com/christgau/wsdd

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

Mario  changed:

   What|Removed |Added

 Attachment #111699|0   |1
is obsolete||

--- Comment #17 from Mario  ---
Created attachment 164632
  --> https://bugs.kde.org/attachment.cgi?id=164632=edit
My resolution host file

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

--- Comment #16 from Mario  ---
Created attachment 164631
  --> https://bugs.kde.org/attachment.cgi?id=164631=edit
Samba config file - Mario

My smb.conf

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

[kio-extras] [Bug 392447] KIO does not use WS-discovery for SMB network resources discovery, so Dolphin shows nothing on smb:// or smb://workgroup/

[Mario]

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

Mario  changed:

   What|Removed |Added

 CC||mario156...@hotmail.com
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #15 from Mario  ---
Hello, I'm triying to use wsd but dolphin browser but when this tool is active
this allow me announce me to the neighbor computers but my computer can't
discover the neighbord samba computes.

I will attach here my samba configuration file, my wsdd logs and my mdns querys
working.

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

[kommit] [Bug 478368] Text in sidebar (tabs) getting cut off.

[Mario Ebenhofer]

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

Mario Ebenhofer  changed:

   What|Removed |Added

   Platform|Debian testing  |Flatpak

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

[kommit] [Bug 478368] New: Text in sidebar (tabs) getting cut off.

[Mario Ebenhofer]

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

Bug ID: 478368
   Summary: Text in sidebar (tabs) getting cut off.
Classification: Applications
   Product: kommit
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: hamed.mas...@gmail.com
  Reporter: mano...@mailbox.org
CC: mon...@kde.org
  Target Milestone: ---

Created attachment 164079
  --> https://bugs.kde.org/attachment.cgi?id=164079=edit
Shows where the text is cut off.

SUMMARY
The "sidebar" which shows all the "tabs" in the application gets cut off,
because it seems to be too small.
This is especially true if the window isn't high enough and a scroll bar
appears. (see screenshots in attachments)

STEPS TO REPRODUCE
1.  Open Kommit

OBSERVED RESULT
Text is cut off.

EXPECTED RESULT
Text isn't cut off.

SOFTWARE/OS VERSIONS
OS: Debian (Testing)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kommit Version: 1.0.2

ADDITIONAL INFORMATION
Graphics Platform: X11

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

[lokalize] [Bug 475166] New: Please make the "SPDX-FileCopyrightText" header configurable

[Mario Blättermann]

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

Bug ID: 475166
   Summary: Please make the "SPDX-FileCopyrightText" header
configurable
Classification: Applications
   Product: lokalize
   Version: 23.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: project management
  Assignee: sdepi...@gmail.com
  Reporter: mario.blaetterm...@gmail.com
CC: aa...@kde.org, sha...@ukr.net
  Target Milestone: ---

Hello,

currently Lokalize produces copyright headers in the following shape:

# SPDX-FileCopyrightText: 2023 Mario Blättermann 

This is not useful for the scripts in our project manpages-l10n [1]. To
generate proper addenda in translated man pages and in the authors' list, we
need the previous shape:

# Mario Blättermann , 2023.

Maybe someone really needs the SPDX stuff ... But it should be configurable in
the settings what the translator and the project needs.

[1] https://salsa.debian.org/manpages-l10n-team/manpages-l10n

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[frameworks-kiconthemes] [Bug 474812] Plasma crashes in KIconColors::KIconColors()

[Mario Barbati]

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

--- Comment #3 from Mario Barbati  ---
Hi, i just installed the KDE on Debian,I didn't change any themes or color
scheme.

Ciao

Mario

On Mon, Sep 25, 2023 at 7:32 PM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=474812
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>Target Milestone|1.0 |---
>  Status|REPORTED|NEEDSINFO
>Assignee|plasma-b...@kde.org |cf...@kde.org
> Product|plasmashell |frameworks-kiconthemes
> Summary|plasma  |Plasma crashes in
>||KIconColors::KIconColors()
>  CC||kdelibs-b...@kde.org,
>||n...@kde.org
>  Resolution|--- |WAITINGFORINFO
>   Component|general |general
> Version|5.27.5  |5.103.0
>
> --- Comment #2 from Nate Graham  ---
>
> Thread 48 (Thread 0x7fbc90dfa6c0 (LWP 5160)):
> [KCrash Handler]
> #4  0x7fbd1bf25c80 in QColor::operator=(QColor const&) () from
> /lib/x86_64-linux-gnu/libQt5Gui.so.5
> #5  0x7fbd1c4759e8 in KIconColors::KIconColors(QPalette const&) () from
> /lib/x86_64-linux-gnu/libKF5IconThemes.so.5
> #6  0x7fbd1c475ddf in KIconColors::KIconColors() () from
> /lib/x86_64-linux-gnu/libKF5IconThemes.so.5
> #7  0x7fbd1c480a8d in KIconEngine::KIconEngine(QString const&,
> KIconLoader*) () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5
> #8  0x7fbcc9e8b3b9 in ?? () from
> /usr/lib/x86_64-linux-gnu/qt5/plugins/iconengines/KIconEnginePlugin.so
> #9  0x7fbd1bdd167e in operator>>(QDataStream&, QIcon&) () from
> /lib/x86_64-linux-gnu/libQt5Gui.so.5
> #10 0x7fbd1df36969 in ?? () from
> /lib/x86_64-linux-gnu/libKF5WaylandClient.so.5
> #11 0x7fbd1b6ceef1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #12 0x7fbd1b6cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #13 0x7fbd1b4a8044 in start_thread (arg=) at
> ./nptl/pthread_create.c:442
> #14 0x7fbd1b5285fc in clone3 () at
> ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
>
>
> Are you using any 3rd-party icon themes or color schemes? If so, what are
> they,
> and does this issue reproduce if you use the default Breeze icon theme and
> Breeze color scheme?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 474812] New: plasma

[Mario Barbati]

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

Bug ID: 474812
   Summary: plasma
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mario.barb...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-12-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
i was opening a docx attachment from gmail with libreoffice writer

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#4  0x7fbd1bf25c80 in QColor::operator=(QColor const&) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x7fbd1c4759e8 in KIconColors::KIconColors(QPalette const&) () from
/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#6  0x7fbd1c475ddf in KIconColors::KIconColors() () from
/lib/x86_64-linux-gnu/libKF5IconThemes.so.5
#7  0x7fbd1c480a8d in KIconEngine::KIconEngine(QString const&,
KIconLoader*) () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5
[...]
#9  0x7fbd1bdd167e in operator>>(QDataStream&, QIcon&) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5


Reported using DrKonqi

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

[plasmashell] [Bug 474812] plasma

[Mario Barbati]

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

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

DrKonqi auto-attaching complete backtrace.

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

[okular] [Bug 420925] Add kinetic scrolling on Trackpad use too

[Mario Borna Mjertan]

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

Mario Borna Mjertan  changed:

   What|Removed |Added

 CC||mariobo...@outlook.com

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

[kde-inotify-survey] [Bug 473489] New: (wishlist) Application-specific control for enabling or disabling notification sounds when the app does not support configuring notifications on a per-event basi

[Mario Borna Mjertan]

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

Bug ID: 473489
   Summary: (wishlist) Application-specific control for enabling
or disabling notification sounds when the app does not
support configuring notifications on a per-event basis
Classification: Plasma
   Product: kde-inotify-survey
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mariobo...@outlook.com
CC: sit...@kde.org
  Target Milestone: ---

SUMMARY
Hopefully this is the right product - I am not sure. 

I would like to propose a feature that allows toggling notification sounds on
or off in a particular application's notification settings. We already have
per-app controls for showing popups, showing notifications in history, showing
notification badges and configuring per-event settings. 

If the app supports configuring notifications on a per-event basis, this is
already possible by configuring the event not to play a sound. Otherwise, this
is not possible.

My personal annoyance with this feature not being present is that I have to
entirely disable notifications from Spotify's (poor) client, as I have no way
to disable the notification chime when a notification that a new song is
playing appears. I am sure many other circumstances where such a feature would
be useful exist.

STEPS TO REPRODUCE
1. Procure an application that does not have support for configuring
notifications on a per-event basis (e.g. Firefox, Spotify)
2. Try to disable notification sounds for that particular app


OBSERVED RESULT
No setting to disable notification sounds exists.

EXPECTED RESULT
A setting exists.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 38 @ 6.4.10-200.fc38.x86_64 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

--- Comment #5 from Mario Ebenhofer  ---
I just read in Bug 414823 that this issue is fixed in QT6... So I can just
ignore it and when Plasma 6 releases (and I install it), that crashes will just
stop happening, right?

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

--- Comment #4 from Mario Ebenhofer  ---
Created attachment 160289
  --> https://bugs.kde.org/attachment.cgi?id=160289=edit
Report of another crash, that happended when I was watching a youtube video in
Google Chrome and moved the mouse near the panel.

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

--- Comment #3 from Mario Ebenhofer  ---
The crash just happened again, and like a few times before, it's saying that
the crash information is not useful. 
It says that some packages are missing, that should be installed...

The packages containing debug information for the following application and
libraries are missing:

/usr/bin/plasmashell
/lib/x86_64-linux-gnu/libQt5Core.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

--- Comment #2 from Mario Ebenhofer  ---
Note: I only switched to Debian testing yesterday. The first two crashes
happened when I was on Debian 12 and the third was on Debain testing.

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

[plasmashell] [Bug 472246] New: Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

Bug ID: 472246
   Summary: Plasma randomly crashes and restarts sometimes.
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mano...@mailbox.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.107.0
Operating System: Linux 6.3.0-1-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Sometimes, Plasma just crashes at random times. Desktop wallpaper gets black
and all panes disappear. Shortly after, everything works as usual and the Crash
Handler appears. 

I have had this issue 3 times now (since I installed Debian 12 with KDE Plasma
5 days ago), so I decided to just report it. I don't really know why it happens
and what exactly causes it, and it isn't really a problem for me, but maybe the
logs could be helpful :)

The first two times it crashed at completely random times while I wasn't doing
anything except browsing the web or similar.
The third time it happend directly after waking the system from sleep.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#4  0x7fe017965624 in QScreen::handle() const () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x7fe0122d8598 in
QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from
/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x7fe01798254d in QOpenGLContext::create() () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5
[...]
#9  0x7fe0172d1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#12 0x7fe0179493f5 in QWindow::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Gui.so.5


The reporter indicates this bug may be a duplicate of or related to bug 445327,
bug 437266.

Reported using DrKonqi

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

[Mario Ebenhofer]

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

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

DrKonqi auto-attaching complete backtrace.

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

[kalendar] [Bug 470547] Kalendar Crashes When Editing Event Calendar

[Mario Leiva]

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

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

kalendar (22.12.3) using Qt 5.15.8

La aplicación se cerró al intentar modificar el porcentaje de finalización de
una tarea de Google Calendar

-- Backtrace (Reduced):
#4  0x7fb7fa596bd0 in QDateTime::operator=(QDateTime const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#7  0x7fb7fa64bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#10 0x7fb7fa64bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#13 0x7fb7fa64bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#16 0x7fb7fa64bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5

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

[kalendar] [Bug 470547] Kalendar Crashes When Editing Event Calendar

[Mario Leiva]

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

Mario Leiva  changed:

   What|Removed |Added

 CC||mario.leiva...@gmail.com

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

[plasma-systemmonitor] [Bug 470323] System monitor no longer has the download and upload columns available

[Mario Awad]

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

Mario Awad  changed:

   What|Removed |Added

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

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

[okular] [Bug 470481] New: Wish: Option to edit multiple comments at once

[Mario Schädel]

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

Bug ID: 470481
   Summary: Wish: Option to edit multiple comments at once
Classification: Applications
   Product: okular
   Version: 23.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: mario.schae...@gmail.com
  Target Milestone: ---

SUMMARY
It would be great to have an option to edit multiple comments at once, as it is
possible in Adobe Acrobat Reader.

BACKGROUND
Sometimes there is the need to have a different author name for the annotations
in a PDF file (e.g. for an anonymous peer review document) . If you plan ahead,
Okular already has you covered, as you can easily change the author name in the
"Configure Okular" dialog. However, it happens that one does not plan ahead and
has already created numerous comments, that then need to be modified. Currently
this is only possible to do for each annotation individually, which can result
in a lot of work depending on the amount of annotations. Adobe Acrobat Reader
has implemented the option to edit multiple comments at once in the desktop
application (which is what I ended up using as a workaround).

As it is already possible to delete multiple annotations at once, I assume it
should not be too difficult to implement this feature. Okular is already the
most feature-rich PDF viewer in the Linux realm and this feature would remove
another of the very few reasons to use the Adobe counterpart instead.



OBSERVED RESULT
When selecting and right-clicking multiple comments in the left "Sidebar" under
the "Annotations" tab, the only option that appears is to delete multiple
comments.

EXPECTED RESULT
When selecting and right-clicking multiple comments in the left "Sidebar" under
the "Annotations" tab, there is an additional option "Properties" (just as when
selecting only one comment).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arco Linux with Qtile (probably irrelevant as it is a wish
and not a bug)
(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.

[plasma-systemmonitor] [Bug 470323] System monitor no longer has the download and upload columns available

[Mario Awad]

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

--- Comment #2 from Mario Awad  ---
Running plasma-systemmonitor from the terminal I notice:
Could not find attribute "netInbound"
Could not find attribute "netOutbound"

I even tried on a fresh install of KDE Neon in a VM and still get the above
when flipping through the pages of system monitor.

The dir /usr/lib/ksysguard/ does not exist for me but libs are probably
elsewhere cause everything works great except the upload/download columns. Note
that I can see the overall download and upload speeds graph in the history page
but in the application and processes tables I cannot add the download and
upload columns.

Any ideas how to fix this or how to look further into it please? Thank you!

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

[plasma-systemmonitor] [Bug 470323] New: System monitor no longer has the download and upload columns available

[Mario Awad]

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

Bug ID: 470323
   Summary: System monitor no longer has the download and upload
columns available
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: mario.a...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

The latest version of System Monitor 5.27.5 running on KDE neon 5.27 with all
updates installed no longer has the download and upload columns available when
trying to add new columns to the processes or applications tables. In previous
versions this was available out of the box.

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

[qca] [Bug 470214] Exception messages

[Mario]

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

--- Comment #3 from Mario  ---
Well, I don't know... somenthing like "Cannot read or create certificate", but
my suggestion wasn't only for my specific case... It would be a general way on
coding using 3rd party libraries.
Thank you!

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

[kdeconnect] [Bug 470214] New: Exception messages

[Mario]

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

Bug ID: 470214
   Summary: Exception messages
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: mgu...@tiscali.it
  Target Milestone: ---

SUMMARY
***
Just a quick suggestion to avoid to go crazy with 3rd parts libraries... I had
a problem with openSSL (which I didn't know) that causes kdeconnect not to read
or create the certificates. The error message from kdeconnectd at startup was:
"Failed to load Legacy provider". It was ununderstandable (at least for me)
what was the problem. I had to download the source code and debug it to
understand that the problem was on openSSL.
Maybe a better management of the exceptions and exceptions messagges could be
useful in the portion of codes that use 3rd parties libraries. 
***


STEPS TO REPRODUCE
1. delete (or invalidate) your ssl config file
2. try to launch kdeconnectd

OBSERVED RESULT


EXPECTED RESULT
Failed to load Legacy provider

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: slackware current (but ubuntu current too)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Just a suggestion for the future, nothing more. Thank you for your great job!

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

[plasma-browser-integration] [Bug 455920] Replace InstallTrigger Firefox check

[Mario Bašić]

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

Mario Bašić  changed:

   What|Removed |Added

 CC||ma...@laravelista.com

--- Comment #3 from Mario Bašić  ---
I see here
https://invent.kde.org/plasma/plasma-browser-integration/-/merge_requests/75/diffs
that there is a fix for this issue, but it seems like the new version of the
extension which includes this fix has not been published. 

When will it be published it has been 4 months since this was fixed?

On the same topic, why not implement it like this
https://github.com/philc/vimium/commit/c5f232c75ee5fafd95eda456c1db88363902814a
?

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

[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument

[Mario Ray Mahardhika]

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

Mario Ray Mahardhika  changed:

   What|Removed |Added

 CC||leledumbo_c...@yahoo.co.id

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

[kdelibs] [Bug 297003] Newly created text files are not empty

[Mario Aichinger]

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

--- Comment #16 from Mario Aichinger  ---
Thanks for the hint with the Templates directory!

> The default template should cater to the typical use case, i.e. a user who 
> wants to create a simple text file.

I tend to disagree with the premise that the typical use case is creating a
"simple text file". But I wouldn't have any data to disprove it. From all the
files which are created with this action I don't know how many will have a .txt
suffix as opposed to a .py, .xml, .ini or what ever else suffix... It just
seams improbable to me that in most cases the extension will be .txt. And than
again how often will a user on purpose create a file with no extension and
expect it to be a "text file", I don't know. Still you might be right!

That all said, would you oppose a MR which adds a "File" .desktop file and
template to KIO which always creates an empty file regardless of the suffix?
The "Text File" entry would stay and there just would be an extra entry which
would just be called "File" since it would not create a new "text file" but a
file in the most generic sense of the word, just an empty file with a extension
chosen by the user. Could this be a compromise which would not change the
existing option but improve the current situation to seemingly at least some
users?

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

[kio-extras] [Bug 453497] Dolphin doesn't show folder preview on local file system until you enter that folder

[Mario Awad]

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

--- Comment #13 from Mario Awad  ---
Thanks again for all the info!

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

[kio-extras] [Bug 453497] Dolphin doesn't show folder preview on local file system until you enter that folder

[Mario Awad]

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

--- Comment #11 from Mario Awad  ---
Glad to hear that the fix is coming and thanks for the quick reply. Sorry I'm
new and couldn't find any more info on kio-extras. Would appreciate any links
to releases or schedule or code bases for it. Thanks again.

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

[kio-extras] [Bug 453497] Dolphin doesn't show folder preview on local file system until you enter that folder

[Mario Awad]

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

Mario Awad  changed:

   What|Removed |Added

 CC||mario.a...@gmail.com

--- Comment #9 from Mario Awad  ---
Thanks for all the hard work on this annoying bug.

I was hoping it would be resolved after today's updates to KDE Plasma 5.25 and
KDE Frameworks 5.95 but it's unfortunately not.

On my machine Dolphin behaves just like on Nick's machine with photos. However
with videos Dolphin will successfully generate thumbs for them in all
subfolders. If you enter a subfolder and then go up again then Dolphin will
start displaying thumbs for photos as well only for that folder you have
entered.

I tried to reset Dolphin settings to defaults and that didn't work too.

Anything else to be done? Thanks again!

SOFTWARE/OS VERSIONS:
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Filesystem: EXT4

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

[kdelibs] [Bug 297003] Newly created text files are not empty

[Mario Aichinger]

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

Mario Aichinger  changed:

   What|Removed |Added

 CC||aichi...@gmail.com

--- Comment #13 from Mario Aichinger  ---
Oh I see, my quirky brain always assumed "Text File" in this context meant
something like "Generic File". Turns out I'm just using it wrong :'D

So to sum up:

Suffix '.txt' + content ' \n' is a text file
Suffix '.txt' + content 'Some Content' is a text file
Suffix '.txt' + content '' is a text file

Suffix '' + content ' \n' is a text file
Suffix '' + content 'Some Content' is a text file
Suffix '' + content '' is NOT a text file

Suffix '.py' + content ' \n' is a python script
Suffix '.py' + content 'Some Content' is a python script
Suffix '.py' + content '' is a python script

The only combination between suffix and content which falls out of line seams
to be the empty-empty one. 

I think there are a few options to improve the situation:
- Turn the existing "Text file" option in to something more generic which only
copies the template if file name does not contain a '.' (probably not a good
idea since it would require a lot of changes in KNewFileMenu)
- Ignore the special case since the UI already proposes a '.txt' suffix in the
dialog (if someone removes the suffix they might know what they are doing)
- Add a "File" .desktop file and template to KIO which creates always an empty
file regardless of the suffix. 
- Make the mime hint more visible to reduce the feeling that the user is
experiencing a bug (e.g. "Text File Content"). This might also educate the user
that this is really a feature to create "text files" and not generic files (the
opposite of directories).

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

[yakuake] [Bug 222538] Allow hiding yakuake's title bar

[Mario Aichinger]

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

Mario Aichinger  changed:

   What|Removed |Added

 CC||aichi...@gmail.com

--- Comment #5 from Mario Aichinger  ---
I think this issue can be closed as it is implemented in
https://invent.kde.org/utilities/yakuake/-/commit/27d05a1ddbfa6c13711be0cd7b0e6763fc54fe4c

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

[KScreen] [Bug 453930] Scaling is off with dual displays when the vertical resolution is different

[Mario]

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

--- Comment #2 from Mario  ---
OK, here's the deal. I found this issue while verifying that
https://bugs.kde.org/show_bug.cgi?id=452397 was solved. However, at that time I
didn't realize that the Manjaro Plasma Daily live CD was booting to X11, not
Wayland.

I found this error using the Manjaro Plasma Daily 202205150340 Live CD.
However, it is not occurring on my normal session (Kubuntu 21.10) which is ALSO
using X11.

Trying Wayland on Kubuntu, I run against
https://bugs.kde.org/show_bug.cgi?id=452397, which precludes testing for this
specific bug. And I haven't found a live CD with daily builds that will allow
me to boot into Wayland using the proprietary Nvidia drivers. I also tried
compiling my own KDE but ran into dependency Hell even using `kdesrc-build`.

If you have a suggestion for how to do that I would really appreciate it, so
that I can both validate https://bugs.kde.org/show_bug.cgi?id=452397 and verify
this one.

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #16 from Mario  ---
I might have jumped the gun on giving it my OK. While submitting the new bug
report (https://bugs.kde.org/show_bug.cgi?id=453930) I realized that:

* Manjaro Plasm Daily (on which I tested) starts up with X11 (not Wayland)
* The KDE Neon live CD does not include the proprietary Nvidia drivers, and I
can't seem to activate my external monitor with Nouveau

So the test I did was with X11. It's weird, because the scaling issue does not
occur on my main Kubuntu install on X11. I haven't found a reasonably simple
way of booting KDE on Wayland with proprietary Nvidia drivers from a live CD.

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

[KScreen] [Bug 453930] New: Scaling is off with dual displays when the vertical resolution is different

[Mario]

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

Bug ID: 453930
   Summary: Scaling is off with dual displays when the vertical
resolution is different
   Product: KScreen
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: mca...@tecnoguru.com
  Target Milestone: ---

SUMMARY

Scaling is messed up on dual displays when the vertical resolution is
different. I am using the proprietary  drivers (this is the scenario I tested,
I'm not sure if it happens on other configurations). See the videos at
https://drive.google.com/drive/folders/10OBUr5NXY7KI1olIfcxr93bRQAGpJcR- 

First video: The external monitor starts up at 3840x1080 (which matches the
vertical resolution of the laptop monitor). Setting it to the proper 5120x1440
results in scaling being completely off (contents of the laptop screen spill
over to the external monitor, and the bottom panel is off of the screen).
Dragging the mouse shows that the pointer coordinates are shifted down/right
from where the pointer is.

Second video: Same thing, but also setting the external monitor to be Primary.
In this case the scaling works correctly.

Third video: I did not press Keep after setting the external monitor as
Primary, so the configuration reverted. Now we have the opposite scaling
problem: the bottom of the screen is black and pointer coordinates are shifted
up/left.

OBSERVED RESULT

Scaling is completely off when the primary monitor has a lower vertical
resolution than the secondary monitor

EXPECTED RESULT

Scaling should work correctly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Manjaro Plasma Daily 202205150340

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #14 from Mario  ---
Hello,

Thank you for the suggestions. Sorry for taking so long to reply, it's been a
bit of a challenge to find enough free time to test this.

I tried with Manjaro Plasma Daily 202205150340. The monitor changes the
resolutions correctly but there are a couple of problems. I've placed a video
at
https://drive.google.com/file/d/1ObjYEPyLyjzFsv5I59Hp6ozzOD0xIBjn/view?usp=sharing:

* The window size changes on both monitors
* The pointer position does not match where it should be (see video)
* It looks like Wayland has problems with screens of different vertical sizes.
At the beginning of the video, when I show both screens, you can see that the
bottom panel is not showing up at all in the laptop monitor, only a piece of it
shows on the external monitor. I would expect the bottom panel to show up only
on the laptop monitor (not overflow into the external one) and that it's at the
actual bottom of the laptop screen and not somewhere below it.

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #13 from Mario  ---
Hello,

Thank you for the suggestions. Sorry for taking so long to reply, it's been a
bit of a challenge to find enough free time to test this.

I tried with Manjaro Plasma Daily 202205150340. The monitor changes the
resolutions correctly but there are a couple of problems:

* The window size changes on both monitors
* The pointer position does not match where it should be (video attached)
* It looks like Wayland has problems with screens of different vertical sizes.
At the beginning of the video, when I show both screens, you can see that the
bottom panel is not showing up at all in the laptop monitor, only a piece of it
shows on the external monitor. I would expect the bottom panel to show up only
on the laptop monitor (not overflow into the external one) and that it's at the
actual bottom of the laptop screen and not somewhere below it.

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #12 from Mario  ---
Created attachment 148857
  --> https://bugs.kde.org/attachment.cgi?id=148857=edit
video - running on Manjaro Daily

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #8 from Mario  ---
(In reply to Zamundaaa from comment #6)
> You can test https://invent.kde.org/plasma/kwin/-/merge_requests/2249. If
> you compile it with Mesa 21.1 or newer there's a decent chance that it'll
> help

Thanks @Zamundaaa. Is there a way to get a binary or some easier way of testing
it that doesn't involve building all of the packages? This is my first time
trying to build anything KDE-related from source, and I'm bumping into
dependency hell.Also,  once I get a binary, will it be just a drop-in
replacement for my installed kwin? The only laptop I have is my daily driver
and it would really suck to break it.

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #5 from Mario  ---
(In reply to Zamundaaa from comment #4)
> I think your BAR is full / KWin is allocating too much CPU-visible memory in
> VRAM. I can make KWin release some ~16MiB of VRAM earlier in your case, but
> it carries a risk of things breaking worse if that fails.
> As a better solution, I'll try to make KWin use hardware accelerated copy
> more often, which doesn't require filling up CPU-visible memory.

Thank you. Is there anything I can do to help/test/get more information?

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #3 from Mario  ---
(In reply to Zamundaaa from comment #1)
> Please attach the output of "grep kwin_wayland_drm
> ~/.local/share/sddm/wayland-session.log". It'll be more useful if you have
> debug logging enabled (put QT_LOGGING_RULES="kwin_*.debug=true" into
> /etc/environment and reboot for that)
> 
> When you close display settings and open it again, is the resolution still
> not matching what your monitor is actually running at?

When reopening display settings I see the resolution that the monitor is
running at, not what I set. As an additional data point, when changing the
resolution and pressing Apply, I don't get the "Keep/Restore" dialog. It's as
if Display Settings doesn't detect that I changed the resolution.

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

[KScreen] [Bug 452397] [Wayland] Cannot change resolution in external monitor

[Mario]

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

--- Comment #2 from Mario  ---
Created attachment 148095
  --> https://bugs.kde.org/attachment.cgi?id=148095=edit
grep kwin_wayland_drm ~/.local/share/sddm/wayland-session.log

Here is the output of `grep kwin_wayland_drm
~/.local/share/sddm/wayland-session.log`, together with `env | sort` in case
there is something weird in my environment.

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

[lokalize] [Bug 452424] New: Crash on an attempt to save a file

[Mario Blättermann]

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

Bug ID: 452424
   Summary: Crash on an attempt to save a file
   Product: lokalize
   Version: 21.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sdepi...@gmail.com
  Reporter: mario.blaetterm...@gmail.com
CC: sha...@ukr.net
  Target Milestone: ---

Application: lokalize (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.17.1-arch1-1 x86_64
Windowing System: X11
Distribution: EndeavourOS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
Immediately after completing the translation of a gettext message, I tried to
save the .po file, but Lokalize crashed. After restarting it, it obviously
shows the recently changed gettext messages from an internal backup, and I'm
able to save my work.

I'm unsure if this crash is really reproducible. Well, such crashes happen very
often, but I don't know whether for the same reason. But especially with very
big files (> 1000 gettext messages), Lokalize is very sensitive. Then it is
almost impossible to work without saving the file after each translated
message.

-- Backtrace:
Application: Lokalize (lokalize), signal: Segmentation fault

[KCrash Handler]
#4  0x7f713f5dee6a in QSortFilterProxyModel::parent(QModelIndex const&)
const () from /usr/lib/libQt5Core.so.5
#5  0x561d097a1aa0 in ?? ()
#6  0x7f713f6297d6 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7f71401631c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#8  0x7f713f6055aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#9  0x7f713f6060a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#10 0x7f713f64d678 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x7f713da03163 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#12 0x7f713da599e9 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x7f713da006c5 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#14 0x7f713f65157a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#15 0x7f713f5fd88b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#16 0x7f713f608fd7 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#17 0x561d096f8ca6 in ?? ()
#18 0x7f713ee16310 in __libc_start_call_main () from /usr/lib/libc.so.6
#19 0x7f713ee163c1 in __libc_start_main_impl () from /usr/lib/libc.so.6
#20 0x561d096f9a45 in _start ()
[Inferior 1 (process 4602) detached]

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

[kwin] [Bug 452397] New: [Wayland] Cannot change resolution in external monitor

[Mario]

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

Bug ID: 452397
   Summary: [Wayland] Cannot change resolution in external monitor
   Product: kwin
   Version: 5.24.4
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mca...@tecnoguru.com
  Target Milestone: ---

SUMMARY
I have a Lenovo X1 Extreme Gen2 with an Nvidia GTX 1650 video card. When I log
in with an X11 session, my external monitor's resolution is correctly set to
5120x1440. However, when I log in with a Wayland session the monitor is set to
3840x1080. If I open the Display Configuration I see the 5120x1440 resolution
is available. However, when I try to set it there is no change (the monitor
stays at 3840x1080 even though the Display Configuration screen says
5120x1440).

As an additional data point, the laptop's internal LCD is 1920x1080.


STEPS TO REPRODUCE
1. Plug in external monitor with a different vertical resolution than the
laptop one(in my case the resolutions are as noted above)
2. Open Display Configuration and change the external monitor's resolution to
its native resolution. Apply changes.

OBSERVED RESULT

The Display Configuration shows the new resolution, but the monitor's
resolution is not changed.

EXPECTED RESULT

The monitor's resolution should change to what is selected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 21.10 / Plasma 5.24.4
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 451884] New: kde connect plasma scroll

[Mario Fetka]

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

Bug ID: 451884
   Summary: kde connect plasma scroll
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: mario.fe...@gmail.com
  Target Milestone: ---

Created attachment 147718
  --> https://bugs.kde.org/attachment.cgi?id=147718=edit
Screenshot

if you have more than one phime connected to your kde system then the scrolling
if the dropdown is really of as seen int screenshot.
 as i would see it it will just extend the list bunt on delete the notifys it
woukd not short the list.
so th secont phone ist way down in the dropdown as you can see ion the
scrollbar.


STEPS TO REPRODUCE
1. have 2 phones
2. get on both phones some notifikations
3. delete the notifikatiosn wiht the cleanup button


OBSERVED RESULT

biig scrollist

EXPECTED RESULT

scrolllist gets reduced so both phnes appera after the cleanup

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.15.29-gentoo-dist (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i9-11950H @ 2.60GHz
Memory: 31.0 GiB of RAM
Graphics Processor: NVIDIA RTX A4000 Laptop GPU/PCIe/SSE2

ADDITIONAL INFORMATION

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

[digikam] [Bug 416462] fuzzy search doesn't find photo which is rotated

[Mario Frank]

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

--- Comment #10 from Mario Frank  ---
(In reply to Daniel from comment #8)
> Hi all,
> 
> so I think they are 2 different cases here (both could theoretically be
> solved by the same solution, but probably shouldn't), and I don't think the
> solution (at least for similar pictures, as written at the end) needs to be
> complicated (maybe I'm naive).
> 
> 
> A) The image is already correctly oriented before importing, using a set
> exif orientation flag.
> 
> If the image is imported (and autorotate is enabled), this flag gets removed
> and the images is fully rotated (that's my understanding).
> 
> The solution to this would be to read the orientation flag when doing the
> fuzzy search. Before running the hash algorith on it, the pictures need to
> be rotated according the flag. This should be almost trivial.
> 
> B) The image is rotated after it has been imported, different to the
> original orientation.
> 
> The solution to this could be to search the hashes for all 4 (let's ignore
> mirrors for now) orientations of the search query picture. I don't think
> this would be difficult or slow (as to my experience the search algorithm is
> very fast/instant). This could be extended to only search for additional
> orientations, if no result is found. If it is technically not possible,
> maybe someone can explain to me why :)
> 
> 
> Ok, this would have one major drawback: It could only find similar pictures,
> not duplicate entries. But if you assume all images are correctly rotated in
> the digikam collection, finding duplicates wouldn't be a problem anymore…
> 
> 
> Daniel

Hi Daniel,

first of all, the similarity search is only quite fast since the fingerprints
are computed
before searching and excessive caching is used. The computation of the
fingerprints
is quite slow. Especially for users with >100k images which is not much.
We should never forget that.

But I think you have a point. The orientation flag could help. I see two
possible ways:

1) For every image, two fingerprints are generated - one with current
orientation and
one with original orientation. And the user can select for the search whether
he wants
to search by original or current orientation.
This has drawbacks, although in most cases not grave ones. First, in many
cases, both
fingerprints of the image will be identical which is a waste of memory (but
this could be optimised).
And second, the database scheme needs to be adopted (not really a problem).
And not to forget, the fingerprint generation will be slower - it is hard to
estimate how much,
since the degree of rotated images differs from user to user.
But the user can decide depending on the situation, which is good.
This could be a solution.

2) The user decides in the fingerprint generation configuration whether
fingerprints shall
be generated for the current orientation or the original one.
In this case, there is no additional memory consumption and rotated images
should be
recognised as similars. One drawback is that if the user changes the
configuration, the
fingerprints partially need to be regenerated. But this drawback can be
reduced. Here, we
also have a possible solution. If the fingerprint entry in the DB gets an
additional orientation flag,
we can compare the orientation flag with the current configuration when
refreshing fingerprints.
So only the fingerprints of the changed and rotated images would be updated.

But I must admit that I do not know what information the orientation flag
provides.
Does it state whether or not the image was rotated or does it give the angle
(90/19/270°)?

Regards,
Mario

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

[digikam] [Bug 416462] fuzzy search doesn't find photo which is rotated

[Mario Frank]

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

--- Comment #9 from Mario Frank  ---
(In reply to caulier.gilles from comment #7)
> Hi Mario and happy new year,
> 
> Well, i don't have a best idea, excepted the fact to use a deep learning
> method. Typically, We have a bug entry to detect and recognize monuments,
> places, animals, flower, tree, and more. This can be certainly extended to
> detect similar image based on shape.
> 
> I don't want mean to use DNN for similarity, but to check how rotation
> problem is treated with the DNN method, and to see if the algorithm is
> applicable to the current similarity code. 
> 
> For me the DNN performance is poor, especially if video cards acceleration
> is not used. Similarity algorithm has acceptable performances as well.
> 
> So yes, a GoSC 2022 project can be proposed around this topic.
> 
> Gilles

Hi Gilles, and I wish you a happy year, too.

I already had the same idea concerning DNN some time ago.
And I agree that DNN may not be our friend concerning performance in this case.
There seem to be concepts for detecting rotated objects. But an image may have
a huge amount of objects. And I did not find a description of recognising
whether
the complete image is rotated. In principle, this should be possible.
But again, the performance could be a big problem.
Nevertheless, it could be worth a try.

Regards,
Mario

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

[digikam] [Bug 416462] fuzzy search doesn't find photo which is rotated

[Mario Frank]

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

Mario Frank  changed:

   What|Removed |Added

 CC||mario.fr...@uni-potsdam.de

--- Comment #6 from Mario Frank  ---
(In reply to Daniel from comment #5)
> (In reply to caulier.gilles from comment #4)
> Hi Gilles, 
> 
> a happy new year too :)
> > Can you check if problem remain with digiKam 7.5.0 pre-release bundle
> 
> I just checked and the problem still persists.
> 
> To be a more verbose:
> 
> If a image A.jpeg is imported which has exif orientation set (for example
> Orientation : Rotate 90 CW), digikam will rotate it and adapt the file (and
> lets say save it to B.jpeg).
> 
> If you search with the original image A.jpeg (not touched by digikam) in the
> fuzzy search, the imported image (B.jpeg) is not found. So I think the main
> issue is that the orientation flag isn't adhered to when searching using
> fuzzy search. (Supported by the fact that the orientation of the image
> preview in the fuzzy search box of A.jpeg is wrong (just horizontal))

Hi Daniel,

I am experiencing this flaw for a long time. Solving this is technically
difficult.
For every image, a HAAR fingerprint is calculated. This is comparable to a 
heatmap concerning brightness. So every brightness point gets a coordinate
which is calculated on the "current" orientation of the image. If the image was
rotated in digiKam, the rotation flag is set. In this case, it could with some
effort
be possible to compute the heatmap "unoriented". But in some cases the
information
about rotation is missing as the image was imported in this orientation but
without
orientation info.

The HAAR concept is not orientation-agnostic. In order to support rotated
images,
every image would need at least 4 heatmaps (for rotation) and even much more
as the image cold have been mirrored. And even then, it would be necessary to
compare every heatmap of the one image with every respective one of the other
image for similarity. It is possible to implement this. But the similarity
search would
have an unacceptable performance - I already tried that.

So I conclude that I do not think that this issue can be solved with the
current similarity
comparison concept without grave effect on the performance - at least not with 
combinatorial comparison. At least, I think this is a bigger project, e.g.
something
for GSoC. There are concepts that may be more appropriate (point distance
comparison
or even machine learning based) and the digiKam database and fuzzy/similarity
search
module in principle support using multiple comparison concepts since after
GSoC2017.

Perhaps Gilles has another idea.

Regards,
Mario

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

[plasma-nm] [Bug 443946] New: Cannot see netplan bond configuration nor bons monitoring

[Mario Lener]

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

Bug ID: 443946
   Summary: Cannot see netplan bond configuration nor bons
monitoring
   Product: plasma-nm
   Version: git-stable-Plasma/5.22
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: mario.le...@gmail.com
  Target Milestone: ---

SUMMARY
When a create a bond via CLI with two or more NIC, i cannot see anithing in
plasma SYSTEM SETTINGS -> NETWORK (no ETH1/ETH2 or BOND0). And no one monitor
on Plasma is working. 
Instead in CLI mode the monitor on bond 0 work flawlessy.


STEPS TO REPRODUCE
1. Install at least two NIC bond via NETPLAN CLI;
2. Try to see config in Plasma System Settings -> Network;
3. Try a network monitor widget in Plasma GUI.

OBSERVED RESULT
Cannot see any result in GUI Plasma network monitor;


EXPECTED RESULT
Some result about traffic on Bond NIC in Graphic widget


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

ADDITIONAL INFORMATION
This is my Netplan file:

# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: networkd
  ethernets:
enp1s0:
  dhcp4: false
enp8s0:
  dhcp4: false
  bonds:
bond0:
  interfaces:
  - enp1s0
  - enp8s0
  addresses:
  - 192.168.10.10/24
  routes:
  - to: default
via: 192.168.10.254
  dhcp4: false
  parameters:
mode: balance-alb
mii-monitor-interval: 100
  nameservers:
addresses: 
- 192.168.10.253

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

[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten

[Mario Splivalo]

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

--- Comment #56 from Mario Splivalo  ---
(In reply to Ahmad Samir from comment #55)
> (In reply to Mario Splivalo from comment #54)
> > (In reply to Ahmad Samir from comment #50)
> > > Fixes were cherry-pick'ed to release/21.08 branch.
> > 
> > It seems this broke konsole again:
> > 
> > https://bugs.kde.org/show_bug.cgi?id=441244
> 
> The fix is in the release/21.08 git branch, it was added there after 21.08
> was released, so distro maintainer will need to backport the commit(s) to
> their respective distros.

Aaa, thnx for the explanation!

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

[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten

[Mario Splivalo]

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

Mario Splivalo  changed:

   What|Removed |Added

 CC||mario+bugs.kde.org@splivalo
   ||.hr

--- Comment #54 from Mario Splivalo  ---
(In reply to Ahmad Samir from comment #50)
> Fixes were cherry-pick'ed to release/21.08 branch.

It seems this broke konsole again:

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

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

[konsole] [Bug 441244] New: Unable to turn-off toolbar (non-existing setting in 'settings' menu)

[Mario Splivalo]

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

Bug ID: 441244
   Summary: Unable to turn-off toolbar (non-existing setting in
'settings' menu)
   Product: konsole
   Version: 21.08.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Install KDE Neon
2. Once installed upgrade all packages
3. Start Konsole
4. Try to turn off toolbars - not possible

OBSERVED RESULT
There is no menu option under 'settings' which will allow turning off the
toolbars.

EXPECTED RESULT
There should be a menu option under 'settings' which would allow turning off
the toolbars.


SOFTWARE/OS VERSIONS
KDE Neon 5.22 
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

I installed KDE Neon from this .iso image: neon-user-20210729-0944.iso

Upon installation the version of Konsole is:
4:21.04.3-0xneon+20.04+focal+release+build20
That version of Konsole does not suffer from the bug being reported here.

However, after upgrading Konsole to the latest version
(4:21.08.0-0xneon+20.04+focal+release+build21), the bug manifests itself.

This looks like a regression and might be a duplicate of
https://bugs.kde.org/show_bug.cgi?id=430036, but I was not sure if re-opening
old bug would be appropriate.

I observed described behavior upon fresh-installing KDE Neon on my workstation
laptop and then verified it with fresh install in KVM virtual machine.

Regards, 

Mario

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

[plasmashell] [Bug 436835] Closing session and relogging causes black screen

[Mario Liguori]

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

--- Comment #2 from Mario Liguori  ---
Yes, I'll check 
Thank you

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

[plasmashell] [Bug 436835] New: Closing session and relogging causes black screen

[Mario Liguori]

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

Bug ID: 436835
   Summary: Closing session and relogging causes black screen
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mariogt2...@live.it
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Sometimes, after closing a session in Plasma, login again causes black screen.
I have to restart SDDM from another TTY and reboot.

STEPS TO REPRODUCE
1. Close the session when some apps are opened;
2. After that, try to login.

OBSERVED RESULT
Black screen with only cursor.

EXPECTED RESULT
Working environment.

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION (could be useful)
CPU: AMD Ryzen 5 5600X
GPU: AMD RX 6700 XT

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

[kate] [Bug 426375] Kate does not set color scheme properly

[Mario Blunk]

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

Mario Blunk  changed:

   What|Removed |Added

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

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

[kate] [Bug 426375] Kate does not set color scheme properly

[Mario Blunk]

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

--- Comment #8 from Mario Blunk  ---
(In reply to Christoph Cullmann from comment #7)
> If you go to the Kate configuration dialog, what is there set on
> 
> "Color themes" (there at the bottom) -> "Default theme for kate:"...
> 
> It should be "Automatic Selection".

No, there is not "Automatic Selection" selected. There is my customized color
theme selected. If I change the setting to "Automatic Selection" then a
different theme gets active. If I select my theme then it is applied properly.
Setting the kate specific theme seems to be fine. 

It seems that the kate specific theme colors have nothing to do with the colors
used for the document, project and file names (see left side of screenshot in
https://bugsfiles.kde.org/attachment.cgi?id=131542)
The problem are the desktop wide color settings. Kate does not apply them to
the document names (on the left) when kate starts. The effect can also be
provoked when clicking Settings/Color Theme/default. By the way: in
Settings/Color Theme there is only "default", nothing else.

Thanks for your great work !

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

[kate] [Bug 426375] Kate does not set color scheme properly

[Mario Blunk]

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

--- Comment #6 from Mario Blunk  ---
It seems the issue has not been solved completely. I can't see any change on my
system. About Kate says:

Kate version 20.12.3
KDE Frameworks 5.81.0
Qt 5.15.2 (built against 5.15.2)
The xcb windowing system

Any ideas ?

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

[cantor] [Bug 431657] New: Al seleccionar el motor el programa se cierra

[Mario Almeida]

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

Bug ID: 431657
   Summary: Al seleccionar el motor el programa se cierra
   Product: cantor
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: cantor-b...@kde.org
  Reporter: mrter...@gmail.com
  Target Milestone: ---

Application: cantor (20.12.1)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.4.0-62-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.20

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

AL iniciar el programa no hay problema, el incoveniente es cuando se selecciona
el motor (Qalculate) el programa se cierra y muestra error

The crash can be reproduced every time.

-- Backtrace:
Application: Cantor (cantor), signal: Segmentation fault

[New LWP 8746]
[New LWP 8747]
[New LWP 8748]
[New LWP 8749]
[New LWP 8750]
[New LWP 8751]
[New LWP 8756]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f31c789eaff in __GI___poll (fds=0x7ffd970d9c68, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f31c13d4ac0 (LWP 8745))]

Thread 8 (Thread 0x7f31abfff700 (LWP 8756)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560f44880574) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560f44880520,
cond=0x560f44880548) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560f44880548, mutex=0x560f44880520) at
pthread_cond_wait.c:638
#3  0x7f31c7c4cd1b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f31c8b3cdca in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7f31c7c46bac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f31c65d2609 in start_thread (arg=) at
pthread_create.c:477
#7  0x7f31c78ab293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f31b2ffd700 (LWP 8751)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560f44711518) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560f447114c8,
cond=0x560f447114f0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560f447114f0, mutex=0x560f447114c8) at
pthread_cond_wait.c:638
#3  0x7f31b8de2e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f31b8de2a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f31c65d2609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f31c78ab293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f31aaffd700 (LWP 8750)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560f44711518) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560f447114c8,
cond=0x560f447114f0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560f447114f0, mutex=0x560f447114c8) at
pthread_cond_wait.c:638
#3  0x7f31b8de2e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f31b8de2a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f31c65d2609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f31c78ab293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f31b37fe700 (LWP 8749)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560f44711518) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560f447114c8,
cond=0x560f447114f0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560f447114f0, mutex=0x560f447114c8) at
pthread_cond_wait.c:638
#3  0x7f31b8de2e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f31b8de2a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f31c65d2609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f31c78ab293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f31b3fff700 (LWP 8748)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560f44711518) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560f447114c8,
cond=0x560f447114f0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560f447114f0, mutex=0x560f447114c8) at
pthread_cond_wait.c:638
#3  0x7f31b8de2e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f31b8de2a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f31c65d2609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f31c78ab293 in clone () at

[kwin] [Bug 430525] New: Magic Lamp is stuttering when another window is open

[Mario Ray Mahardhika]

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

Bug ID: 430525
   Summary: Magic Lamp is stuttering when another window is open
   Product: kwin
   Version: 5.20.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: leledumbo_c...@yahoo.co.id
  Target Milestone: ---

SUMMARY
I think this is better described as a video: https://youtu.be/bDFsksynmKk
tl;dr:
* standalone window -> effect is smooth
* another window behind -> effect is stuttering

STEPS TO REPRODUCE
1. Enable Magic Lamp effect, optionally Show FPS as well
2. Open two apps, preferably KDE apps (shouldn't matter, but just in case)
3. Minimize both
4. Start maximizing/minimizing one with the other stay minimized
5. Maximize the other
6. Start maximizing/minimizing again with the same window from step 4

OBSERVED RESULT
With Show FPS, at step 4 the fps only goes down by 10 or so and only at the
first or second minimize. The subsequent application is stable at highest
reachable fps. Visually, the animation is very smooth like there's no frame
skipping.
At step 6, the fps goes down by up to 30 with 20-ish average and it stays so
subsequently. Visually, the animation is like there are skipped frames so the
smoothness is much less.

EXPECTED RESULT
Step 6 should have the same performance as step 4.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro with 5.9.11-3 kernel
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
* CPU/GPU: i7-7700HQ/Intel UHD 620
* KWin MaxFPS: 144

Compositor:
* Scale method: Crisp
* Rendering backend: OpenGL 3.1
* Vsync: auto
* Allow application to block compositing: ✓

Other enabled desktop effects:
* Accessibility: Zoom
* Appearance: Background contrast, Blur, Desaturate Unresponsive Applications,
Fading Popups, Full Screen, Login, Logout, Maximize, Morphing popups, Screen
Edge, Sheet, Sliding popups, Translucency, Wobbly Windows
* Focus: Dialog Parent, Dim Inactive, Dim Screen for Administrator Mode, Slide
Back
* Show Desktop Animation: Window Aperture
* Virtual Desktop Switching Animation: Desktop Cube Animation
* Window Management: Desktop Cube, Present Windows, Resize Window
* Window Open/Close Animation: Glide

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

[neon] [Bug 428438] Installer creates sambashare with gid 1000

[Mario Splivalo]

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

--- Comment #7 from Mario Splivalo  ---
This is, indeed, fixed now.

I'm just a bit confused that sambashare has guid of 999 now, not 131 (or
whatever it was) with previous version of Neon.

mario@neja:~$ id
uid=1000(mario) gid=1000(mario)
groups=1000(mario),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),999(sambashare)

Thank you :)

Mario

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

[neon] [Bug 428438] Installer creates sambashare with gid 1000

[Mario Splivalo]

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

--- Comment #5 from Mario Splivalo  ---
Thnx, Harald. Is there a place I can see the progress/process for QAing this
change, and all of that?

Mario

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

[neon] [Bug 428438] Installer creates sambashare with gid 1000

[Mario Splivalo]

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

Mario Splivalo  changed:

   What|Removed |Added

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

--- Comment #3 from Mario Splivalo  ---
I just downloaded latest Neon install iso: neon-user-20201119-0945.iso

The issue is still present there. When system is installed, after I log in, my
user has gid 1001 and sambashare has gid of 1000.

Is this supposed to be fixed in the latest version available for download?

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

[kate] [Bug 426377] code folding with "null record" in Ada folds the rest of the file completely

[Mario Blunk]

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

--- Comment #3 from Mario Blunk  ---
(In reply to Justin Zobel from comment #2)
> Can you please supply the relevant code for testing purposes?

Hi Justin,
thanks for your work. Please find some examples on null-records here:
https://github.com/Blunk-electronic/ada_training/blob/master/src/records_3/records_3.adb

Best,
Mario

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

[muon] [Bug 428982] New Linux kernel packages not listed on Muon Package Manager

[Mario]

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

Mario  changed:

   What|Removed |Added

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

--- Comment #1 from Mario  ---
Resolved on Plasma 5.20.3

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

[muon] [Bug 428982] New Linux kernel packages not listed on Muon Package Manager

[Mario]

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

Mario  changed:

   What|Removed |Added

 CC||mario.bugs.rep...@gmail.com

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

[muon] [Bug 428982] New: New Linux kernel packages not listed on Muon Package Manager

[Mario]

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

Bug ID: 428982
   Summary: New Linux kernel packages not listed on Muon Package
Manager
   Product: muon
   Version: 5.8.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: mario.bugs.rep...@gmail.com
CC: silh...@gmail.com
  Target Milestone: ---

SUMMARY

yesterday I updated the system to kernel 5.4.0-53


STEPS TO REPRODUCE

Opened Muon Package Manager and searching for new kernel modules recently
installed.

OBSERVED RESULT

Packages not listed on Muon Package Manager
1 linux-headers-5.4.0-53
2 linux-modules-5.4.0-53-generic 
3 linux-headers-5.4.0-53-generic
4 linux-modules-extra-5.4.0-53-generic
5 linux-image-5.4.0-53-generic

EXPECTED RESULT

I was expecting to find and see these above packages.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux mario-optiplex790 5.4.0-53-generic #59-Ubuntu SMP Wed
Oct 21 09:38:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

(available in About System)
KDE Plasma Version: 5.20.02
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

I can see the following packages
1 linux-headers-5.4.0-52
2 linux-modules-5.4.0-52-generic 
3 linux-headers-5.4.0-52-generic
4 linux-modules-extra-5.4.0-52-generic
5 linux-image-5.4.0-52-generic

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

[neon] [Bug 428438] New: Installer creates sambashare with gid 1000

[Mario Splivalo]

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

Bug ID: 428438
   Summary: Installer creates sambashare with gid 1000
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

User related gids and uids start at 1000. With KDE Neon 20.04 this is not the
case, the user created trough installer has gid 1001.

This is not in-line with all other distros, where 1st created user has uid/gid
of 1000/1000. Even previous versions of Neon (16.04, 18.04) followed this rule.

For some reason sambashare group has gid 1000, although on liveCD it has gid
131. On my Neon 18.04 sambashare had gid 121.


STEPS TO REPRODUCE
1. Download lates Neon iso
2. Install it in KVM/Virtualbox
3. Log in as user, type 'id'

OBSERVED RESULT
marios@neonka:~$ id
uid=1000(marios) gid=1001(marios)
groups=1001(marios),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),1000(sambashare)


EXPECTED RESULT
marios@neonka:~$ id
uid=1000(marios) gid=1000(marios)
groups=1001(marios),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),120(lpadmin),131(sambashare)




This is not a problem so much, merely an annoyance. I reinstalled my system and
all of my NFS shares are now broken because of wrong UIDs :) 

I think that installer, when creating sambashare group, for some reason uses
the wrong gid, but I haven't been able to pinpoint it.

Regards, 

Mario

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

[kwin] [Bug 427111] Once logged out can not log in back again

[Mario Splivalo]

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

Mario Splivalo  changed:

   What|Removed |Added

 CC||mario+bugs.kde.org@splivalo
   ||.hr

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

[kwin] [Bug 427111] New: Once logged out can not log in back again

[Mario Splivalo]

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

Bug ID: 427111
   Summary: Once logged out can not log in back again
   Product: kwin
   Version: 5.19.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mario+bugs.kde@splivalo.hr
  Target Milestone: ---

When I log out (no restart, no shut down, plain log out) from my session, I can
not log in again. I need to restart my machine to be able to log in again.


STEPS TO REPRODUCE
1. Log in.
2. Do whatever (open browser, check local news, close browser, read email, play
a game)
3. Log out.
4. Log in again. It will fail in a manner that sddm will let you in, but it
looks like Xsession closes before it starts (like kwin never fires up), and
you're back at sddm.


OBSERVED RESULT
Not able to log in.


EXPECTED RESULT
To be able to log in.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon 20.04
(available in About System)
KDE Plasma Version: 5.19.5

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

[kdeplasma-addons] [Bug 426864] New: does not execute the line command

[Mario Moles]

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

Bug ID: 426864
   Summary: does not execute the line command
   Product: kdeplasma-addons
   Version: 5.19.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: timer
  Assignee: plasma-b...@kde.org
  Reporter: mario.mole...@gmail.com
  Target Milestone: ---

SUMMARY

does not execute the command: "mplayer
/usr/share/sounds/Oxygen-Sys-Log-In-Long.ogg"

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.8.6-1-Manjaro
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

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