[kwin] [Bug 451825] The window is translucent and frozen, not responding to any events, and no crash message.

[A weak little orange cat]

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

--- Comment #5 from A weak little orange cat  ---
(In reply to Nate Graham from comment #4)
> Thanks for the info.
> 
> Are you on Wayland, or X11.

I am using X11 on plasma

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

[plasmashell] [Bug 452015] Fresh Boot long wait for menu search

[bugzilla_noreply]

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

wiser.nat...@gmail.com changed:

   What|Removed |Added

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

--- Comment #3 from wiser.nat...@gmail.com ---
(In reply to Nate Graham from comment #1)
> Does the same thing happen in KRunner itself, invoked with the Alt+Space
> shortcut?

Haven't noticed this happening in krunner or any other menu only the new
kickoff menu.

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

[krita] [Bug 452655] When you resize the canvas, the canvas becomes a mosaic

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #6 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[plasmashell] [Bug 452015] Fresh Boot long wait for menu search

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 452031] QR code option is shown for screenshots, but fails

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[korganizer] [Bug 328655] Exception on recurring event on CalDAV calendar makes whole event series disappear

[Bug Janitor Service]

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

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kmix] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

[Koshika]

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

Koshika  changed:

   What|Removed |Added

 CC||koshi...@gmail.com

--- Comment #1 from Koshika  ---
About System;
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Graphics Platform: X11
wm: kwin_x11 vt: 1 dm: SDDM
Distro: Manjaro Linux base: Arch Linux

Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915
v: kernel ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0166 class-ID: 0300
  Device-2: AMD Thames [Radeon HD 7500M/7600M Series] vendor: Dell
driver: radeon v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max:
gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 1002:6840
class-ID: 0300
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
loaded: modesetting,radeon alternate: fbdev,vesa gpu: i915 display-ID: :0
screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
  Monitor-1: LVDS-1 model: LG Display 0x033a built: 2012 res: 1366x768
hz: 60 dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm
(15.5")
ratio: 16:9 modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 22.0.1
compat-v: 3.1 direct render: Yes

SUMMARY
after the upgrade to kde-frameworks-5.93 the all(system, brightness, volume)
OSD indicators are displayed in the top left corner of the screen instead of
being displayed in the center of the screen

STEPS TO REPRODUCE
invoke any changes through Fn keys  brightness, volume, Wifi, etc.

OBSERVED RESULT
the OSD indicator is displayed in the top left corner of the screen

EXPECTED RESULT
the OSD indicator should be displayed in the center of the screen

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

[kwin] [Bug 452435] [Wayland] SDL Applications crash with error "wl_registry@2: error 0: invalid global wp_drm_lease_device_v1 (50)" when external display is unplugged

[Weng Xuetian]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com
 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #10 from Weng Xuetian  ---
KWIN_XWAYLAND_DEBUG=1

Some relevant log from Xwayland, it seems there's some race. 

[1937782.511] wl_registry@15.global_remove(52)
[1937782.581] wl_registry@2.global_remove(52)
[1937782.734]  -> zxdg_output_v1@31.destroy()
[1937782.754] wl_registry@15.global_remove(51)
[1937782.761] wl_registry@2.global_remove(51)
[1937782.768] wl_registry@15.global_remove(50)
[1937782.776] wl_registry@2.global_remove(50)
[1937782.785]  -> wp_drm_lease_device_v1@29.release()
[1937782.792] wl_registry@15.global(53, "wp_drm_lease_device_v1", 1)
[1937782.810] wl_registry@2.global(53, "wp_drm_lease_device_v1", 1)
[1937782.834]  -> wl_regis...@2.bind(53, "wp_drm_lease_device_v1", 1, new id
[unknown]@32)
[1937782.861] wl_registry@15.global_remove(53)
[1937782.868] wl_registry@2.global_remove(53)
[1937782.876]  -> wp_drm_lease_device_v1@32.release()
error in client communication (pid 43035)
[1937783.583] wl_display@1.delete_id(31)
[1937783.603] wl_display@1.delete_id(29)
[1937783.611] wl_display@1.error(wl_registry@2, 0, "invalid global
wp_drm_lease_device_v1 (53)")

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

[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor

[Henrique Sant'Anna]

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

--- Comment #17 from Henrique Sant'Anna  ---
I'm using kwin 5.24.4 and can reproduce this problem ALWAYS, every time I
unplug HDMI cable without deactivating the external monitor first.

But now the screen completely freezes, even the mouse pointer, and after that
it will not unfreeze anymore. 

I'm on Arch and I don't know how to collect useful information about this
freeze, since I don't have debug symbols installed, maybe I have to compile it
myself.

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

[krita] [Bug 452667] New: Open krita, it's work fine, go to any software and back krita, the brushes no pressure.

[Will Song]

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

Bug ID: 452667
   Summary: Open krita, it's work fine, go to any software and
back krita, the brushes no pressure.
   Product: krita
   Version: 5.0.5
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: s.s...@outlook.com
  Target Milestone: ---

Open krita, it's work fine, go to any software and back krita, the brushes no
pressure. Open krita, cycle like this.
This can be reproduced in version prior to 5.x for a year.(In any software it's
fine, only krita, tablet is Wacom)
Thank you.


Krita

 Version: 5.0.5
 Languages: en_US, en, en_US, en, en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information

  Build ABI: arm64-little_endian-lp64
  Build CPU: arm64
  CPU: arm64
  Kernel Type: darwin
  Kernel Version: 21.4.0
  Pretty Productname: macOS 12.3
  Product Type: osx
  Product Version: 12.3

OpenGL Info

  Vendor:  "Apple" 
  Renderer:  "Apple M1 Pro" 
  Version:  "4.1 Metal - 76.3" 
  Shading language:  "4.10" 
  Requested format:  QSurfaceFormat(version 3.2, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CoreProfile) 
  Current format:  QSurfaceFormat(version 4.1, options
QFlags(), depthBufferSize 32, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CoreProfile) 
 Version: 4.1
 Supports deprecated functions false 
 is OpenGL ES: false 
  supportsBufferMapping: true 
  supportsBufferInvalidation: false 
  Extensions: 
 "GL_ARB_ES2_compatibility" 
 "GL_ARB_texture_rgb10_a2ui" 
 "GL_ARB_texture_storage" 
 "GL_ARB_tessellation_shader" 
 "GL_ARB_timer_query" 
 "GL_ARB_shading_language_include" 
 "GL_ARB_vertex_attrib_64bit" 
 "GL_APPLE_client_storage" 
 "GL_APPLE_flush_render" 
 "GL_ARB_texture_gather" 
 "GL_EXT_texture_filter_anisotropic" 
 "GL_ARB_vertex_type_2_10_10_10_rev" 
 "GL_ARB_sampler_objects" 
 "GL_APPLE_container_object_shareable" 
 "GL_ARB_texture_query_lod" 
 "GL_ARB_internalformat_query" 
 "GL_EXT_texture_compression_s3tc" 
 "GL_APPLE_rgb_422" 
 "GL_ARB_explicit_attrib_location" 
 "GL_ARB_gpu_shader5" 
 "GL_ARB_instanced_arrays" 
 "GL_APPLE_texture_range" 
 "GL_EXT_framebuffer_multisample_blit_scaled" 
 "GL_ARB_shader_subroutine" 
 "GL_EXT_texture_sRGB_decode" 
 "GL_ARB_shader_bit_encoding" 
 "GL_ARB_blend_func_extended" 
 "GL_ARB_texture_cube_map_array" 
 "GL_EXT_debug_label" 
 "GL_ARB_draw_indirect" 
 "GL_ARB_viewport_array" 
 "GL_EXT_debug_marker" 
 "GL_ARB_separate_shader_objects" 
 "GL_APPLE_row_bytes" 
 "GL_ARB_occlusion_query2" 
 "GL_ARB_texture_buffer_object_rgb32" 
 "GL_ARB_transform_feedback2" 
 "GL_ARB_transform_feedback3" 
 "GL_ARB_gpu_shader_fp64" 
 "GL_NV_texture_barrier" 
 "GL_ARB_draw_buffers_blend" 
 "GL_ARB_sample_shading" 
 "GL_ARB_texture_swizzle" 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: false 
  isQtPreferOpenGLES: true 

useBufferInvalidation (config option): false


Hardware Information

  GPU Acceleration: desktop
  Memory: 16384 Mb
  Number of Cores: 10
  Swap Location: /private/var/folders/jn/4cmmr8313vqbxhk78ynnxdw8gn/T

Current Settings

  Current Swap Location:
/private/var/folders/jn/4cmmr8313vqbxhk78ynnxdw8gn/T
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 200
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Disable Vector Optimizations: false
  Disable AVX Optimizations: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 420
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: false


Display Information
Number of screens: 2
Screen: 0
Name: 
Depth: 24
Scale: 2
Resolution in pixels: 1512x982
Manufacturer: 
Model: 
Refresh Rate: 120
Screen: 1
Name: 
Depth: 24
Scale: 2
Resolution in pixels: 2560x1440
Manufacturer: 
Model: 
   

[frameworks-kservice] [Bug 452566] KDE offers to open mimetype with application twice when it inherits the association twice

[Adam Fontenot]

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

--- Comment #3 from Adam Fontenot  ---
(In reply to Ahmad Samir from comment #1)
> First things first, could you verify you only have one okular .desktop file
> in /usr/share/applications/ and ~/.local/share/applications/ ?

Yes, I only have /usr/share/applications/org.kde.okular.desktop

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

[systemsettings] [Bug 391905] No way to delete Look & Feel themes from the KCM

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|wishlist|normal
   Priority|NOR |HI

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

[kwin] [Bug 452062] Xwayland app doesn't launch in Wayland KDE 5.24.4

[McCak]

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

McCak  changed:

   What|Removed |Added

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

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

[krita] [Bug 452655] When you resize the canvas, the canvas becomes a mosaic

[Will Song]

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

--- Comment #2 from Will Song  ---
Resize canvas.

For example,  photos.

Yes, i mean this can be reproduced in version prior to 5.x.

Thank you.









> 2022年4月15日 19:38，David REVOY  写道：
> 
> https://bugs.kde.org/show_bug.cgi?id=452655
> 
> David REVOY  changed:
> 
>   What|Removed |Added
> 
> CC||i...@davidrevoy.com
> Resolution|--- |WAITINGFORINFO
> Status|REPORTED|NEEDSINFO
> 
> --- Comment #1 from David REVOY  ---
> Your bug report needs more information:
> 
>> "When the canvas size is adjusted"
> 
> How? Crop tool with "grow" option? Resizing canvas dialog via the top menu?
> Using the arrow appearing on the edge when moving the canvas far away? You 
> see,
> there is multiple way to adjust the canvas size. (even GMIC filters can do it
> too).
> 
>> "the canvas will become mosaic"
> 
> A mosaic like what? Do you mean a lot of glitch that form a pattern that
> doesn't look like your artwork anymore? Or do you have your artwork repeated
> all around the canvas as a repetitive wallpaper pattern? Please post a
> screenshot, or a photo of your screen if you can't describe it more 
> accurately;
> it might help.
> 
>> "It has been about a year."
> 
> You use a Krita superior to 5.x; a year ago, Krita 5 wasn't released. With 
> this
> sentence, do you try to communicate this bug was also something you could
> reproduce in version prior to 5.x ? Can you mention this versions?
> 
> Thank you for the future information.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 452655] When you resize the canvas, the canvas becomes a mosaic

[Will Song]

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

--- Comment #3 from Will Song  ---
Created attachment 148180
  --> https://bugs.kde.org/attachment.cgi?id=148180=edit
001.jpeg

--- Comment #4 from Will Song  ---
Created attachment 148181
  --> https://bugs.kde.org/attachment.cgi?id=148181=edit
002.jpeg

--- Comment #5 from Will Song  ---
Created attachment 148182
  --> https://bugs.kde.org/attachment.cgi?id=148182=edit
003.jpeg

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

[kstars] [Bug 452666] New: Kstars mosaic tool zooms to minimum

[bugzilla_noreply]

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

Bug ID: 452666
   Summary: Kstars mosaic tool zooms to minimum
   Product: kstars
   Version: 3.5.8
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: leedpeter...@mac.com
  Target Milestone: ---

SUMMARY

Mosaic tool does not automatically zoom out to size of the mosaic. It always
shows a minimum (high) zoom of the target

STEPS TO REPRODUCE
1. Create a sequence
2. Select a target
3. Click on the mosaic tool

OBSERVED RESULT

Tool only shows the target and does not automatically zoom out to the size of
the mosaic FOV

EXPECTED RESULT

Tool should zoom out to the size of the mosaic FOV

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Stellarmate 1.7.0
(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.

[systemsettings] [Bug 452561] The "Change Wallpaper..." button does nothing when the current activity is not the default one

[Fushan Wen]

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

Fushan Wen  changed:

   What|Removed |Added

Summary|The "Change Wallpaper..."   |The "Change Wallpaper..."
   |button does nothing |button does nothing when
   ||the current activity is not
   ||the default one

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

[systemsettings] [Bug 452561] The "Change Wallpaper..." button does nothing

[Fushan Wen]

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

Fushan Wen  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED

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

[kwin] [Bug 442846] Blocking calls to Xwayland can make kwin freeze

[Weng Xuetian]

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

--- Comment #26 from Weng Xuetian  ---
Also another observation is that, if Xwayland is killed or crashed, all new X
client will just blocking on X. I don't think this should happen.

I'm thinking that kwin might not release the socket fd or sth properly, so x
client are still indefinitely waiting for X socket, including kwin itself.

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

[krita] [Bug 452626] Freehand shortcut not working as expected

[CaFeine]

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

--- Comment #2 from CaFeine  ---
Hello, tomorrow I will check for viruses (I use a computer not alone) 
and in the evening I will record a video with a keyboard. 
Maybe it's something I don't understand. (°-°)

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

[kwin] [Bug 442846] Blocking calls to Xwayland can make kwin freeze

[Weng Xuetian]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #25 from Weng Xuetian  ---
It seems that I'm also affected by this.
For some other probably unrelated reason, unplug external monitor would cause
SIGSEGV on Xwayland on my setup,  but I observed that kwin freeze due to this
in this case. 

I gdb attached to Xwayland and noticed Xwayland received a sigsegv, after
detach from gdb, noticed Xwayland become a zombie process.

Relevant stack trace in kwin, looks similar to the existing ones.
It seems that kwin is blocked on some X event request and never returns.

I'd say we should try to manage Xwayland process in a separate thread,
otherwise we may fail to collect xwayland process when making a blocking call.
#0  0x7f18b7bd32af in poll () at /usr/lib/libc.so.6
#1  0x7f18b8d8963b in  () at /usr/lib/libxcb.so.1
#2  0x7f18b8d8b08f in  () at /usr/lib/libxcb.so.1
#3  0x7f18b8d8b1a2 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1
#4  0x7f18ba58339a in KWin::Workspace::updateXStackingOrder() () at
/usr/lib/libkwin.so.5
#5  0x7f18ba583479 in KWin::Workspace::xStackingOrder() const () at
/usr/lib/libkwin.so.5
#6  0x7f18ba512243 in KWin::Compositor::windowsToRender() const () at
/usr/lib/libkwin.so.5
#7  0x7f18ba5127be in KWin::Compositor::composite(KWin::RenderLoop*) () at
/usr/lib/libkwin.so.5
#8  0x7f18b84af463 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f18ba4d07a7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
() at /usr/lib/libkwin.so.5
#10 0x7f18ba5a1c18 in KWin::RenderLoopPrivate::dispatch() () at
/usr/lib/libkwin.so.5
#11 0x7f18b84af463 in  () at /usr/lib/libQt5Core.so.5
#12 0x7f18b84b169f in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#13 0x7f18b84a2766 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#14 0x7f18b8f3c1c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#15 0x7f18b847e5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#16 0x7f18b84c9dd5 in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#17 0x7f18b84ca272 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#18 0x557e3c5a97e2 in  ()
#19 0x7f18b847688b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#20 0x7f18b8481fd7 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#21 0x557e3c4b832a in  ()
#22 0x7f18b7afa310 in __libc_start_call_main () at /usr/lib/libc.so.6
#23 0x7f18b7afa3c1 in __libc_start_main_impl () at /usr/lib/libc.so.6
#24 0x557e3c4b9ab5 in  ()

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

[ksysguard] [Bug 433804] zfs support in ksysguard / system monitor widgets?

[Eridani Rodríguez]

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

Eridani Rodríguez  changed:

   What|Removed |Added

 CC||eridanired...@yahoo.com.mx

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

[kontact] [Bug 452665] New: Kmail/Kontact bug

[Valentin]

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

Bug ID: 452665
   Summary: Kmail/Kontact bug
   Product: kontact
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: vako...@mail.ru
  Target Milestone: ---

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


STEPS TO REPRODUCE
1.  Launch Kontact
2.  Setup Exchange (EWS) account
3.  Setup outgoing servers based on Exchange/EWS account

OBSERVED RESULT
No mailbox folders are displayed. No E-mail in folder are available. Icoming
E-mails are visible in Kmail, but it's impssible to send anything through the
Kmail due to it doesn't recognize EWS account set up. 

EXPECTED RESULT
Account set up. In Kontact window, mailbox and its folders are visible with
E-mails in folders. Calendar  and Contacts sre available.

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

ADDITIONAL INFORMATION

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

[frameworks-kxmlgui] [Bug 450184] Application-specific action "start_new_session" does not appear in menu in a Plasma session

[Alexander Potashev]

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

--- Comment #2 from Alexander Potashev  ---
Git commit f8ed5ac856934ef8008680bdf97bfa0e6d316cfc by Alexander Potashev.
Committed on 15/04/2022 at 23:09.
Pushed by aspotashev into branch 'master'.

Fix action "Start New Session".

Looks like the problem was caused by the following section in
/usr/share/kde-settings/kde-profile/default/xdg/kdeglobals on Fedora:

```
[KDE Action Restrictions]
action/start_new_session=false
action/switch_user=false
```

M  +1-1src/ktimetrackerui.rc
M  +2-2src/timetrackerwidget.cpp

https://invent.kde.org/pim/ktimetracker/commit/f8ed5ac856934ef8008680bdf97bfa0e6d316cfc

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

[frameworks-kxmlgui] [Bug 450184] Application-specific action "start_new_session" does not appear in menu in a Plasma session

[Alexander Potashev]

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

--- Comment #1 from Alexander Potashev  ---
Looks like it's caused by the following section in
/usr/share/kde-settings/kde-profile/default/xdg/kdeglobals on Fedora:

```
# HOW: https://develop.kde.org/deploy/kiosk/introduction/
# WHY: https://bugzilla.redhat.com/show_bug.cgi?id=1929643
[KDE Action Restrictions]
action/start_new_session=false
action/switch_user=false
```

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

[Elisa] [Bug 452664] Elisa doesn't play song opened via context menu but sticks to earlier played song

[postix]

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

--- Comment #1 from postix  ---
You can actually skip step 2. from above.

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

[Elisa] [Bug 452664] Elisa doesn't play song opened via context menu but sticks to earlier played song

[postix]

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

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[Elisa] [Bug 452664] New: Elisa doesn't play song opened via context menu but sticks to earlier played song

[postix]

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

Bug ID: 452664
   Summary: Elisa doesn't play song opened via context menu but
sticks to earlier played song
   Product: Elisa
   Version: 21.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: pos...@posteo.eu
  Target Milestone: ---

STEPS TO REPRODUCE
1. Play some song in Elisa
2. Close Elisa
3.  Open Dolphin, choose a song, right click on it and choose "Open with Elisa"

OBSERVED RESULT
Elisa opens and the song is added to the playlist, though the last played song
is still selected and nothing is played automatically.
One needs to choose the last added item in the playlist first manually.

EXPECTED RESULT
Elisa starts and plays the selected song.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220413
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.2-1-default (64-bit)
Graphics Platform: Wayland

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

[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0

[bugzilla_noreply]

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

--- Comment #14 from caulier.gil...@gmail.com ---
Maik,

One Q : What's the gain of capi concept ?

https://invent.kde.org/graphics/digikam/-/tree/master/core/libs/video/qtav/src/capi

Typically, this allow to load dynamically a dependency at run time, instead to
link with dependency. 
so, it replace the OS loader which load in memory the dependencies on demand. 
Why to duplicates this job ? It a specific use cases under phone where QtAv can
be compiled ?
I think it's a non sense with desktop uses.

Gilles

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

[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0

[Maik Qualmann]

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

--- Comment #13 from Maik Qualmann  ---
Hi Gilles,
I'll get an overview of the QtAV code over the weekend.

Best

Maik

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

[digikam] [Bug 452577] Export to pinterest function does not work and shows a message status:failure,code:11

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
I have uploaded the required video showing the digiKam Pinterest Export tool in
action. The video is required to upgrade trial access to standard access. We'll
see if we get accepted.

Maik

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

[digikam] [Bug 452577] Export to pinterest function does not work and shows a message status:failure,code:11

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Git commit c5404cd23a83f5147702486e8fda54ea66e63926 by Maik Qualmann.
Committed on 15/04/2022 at 20:12.
Pushed by mqualmann into branch 'qt5-maintenance'.

ported Pinterest export tool to the new V5 API
The digiKam client key is currently still in trial
mode and therefore cannot be used publicly by other users.

M  +45   -80   core/dplugins/generic/webservices/pinterest/ptalker.cpp
M  +3-1core/dplugins/generic/webservices/pinterest/ptalker.h
M  +6-7core/dplugins/generic/webservices/pinterest/pwindow.cpp

https://invent.kde.org/graphics/digikam/commit/c5404cd23a83f5147702486e8fda54ea66e63926

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

[umbrello] [Bug 87537] DataTypes should be scoped just as other UML elements

[Oliver Kellogg]

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

Oliver Kellogg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit||https://invent.kde.org/sdk/
   ||umbrello/commit/d46954b97ec
   ||d6d2af7900cb9864ddf93a9f543
   ||1e
   Version Fixed In||2.34.70 (KDE releases
   ||22.07.70)

--- Comment #3 from Oliver Kellogg  ---
Git commit d46954b97ecd6d2af7900cb9864ddf93a9f5431e by Oliver Kellogg.
Committed on 15/04/2022 at 20:09.
Pushed by okellogg into branch 'master'.

Fix "DataTypes should be scoped just as other UML elements"

umbrello/umllistview.cpp
- In function addNewItem do not force parentItem of lvt_Datatype to
  m_datatypeFolder.
FIXED-IN: 2.34.70 (KDE releases 22.07.70)

M  +0-4umbrello/umllistview.cpp

https://invent.kde.org/sdk/umbrello/commit/d46954b97ecd6d2af7900cb9864ddf93a9f5431e

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

[frameworks-kservice] [Bug 452566] KDE offers to open mimetype with application twice when it inherits the association twice

[Ahmad Samir]

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

--- Comment #2 from Ahmad Samir  ---
To be more exact (because okular installs many .desktop files),
org.kde.okular.desktop is the main one.

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

[frameworks-kservice] [Bug 452566] KDE offers to open mimetype with application twice when it inherits the association twice

[Ahmad Samir]

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

--- Comment #1 from Ahmad Samir  ---
First things first, could you verify you only have one okular .desktop file in
/usr/share/applications/ and ~/.local/share/applications/ ?

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

[systemsettings] [Bug 417615] Option to disable kdeconnect

[Forest]

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

--- Comment #12 from Forest  ---
I found some (ugly) workarounds for the unwanted kdeconnectd autostart.

The process seems to be launched at session startup time from two distinct
places:

1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop

This can be disabled for individual users by copying the file to each user's
~/.config/autostart/ directory and adding Hidden=true to the [Desktop Entry]
section of the copies.

Alternatively, it can be disabled by default by adding a line like this to the
file's [Desktop Entry] section:
  X-KDE-autostart-condition=kdeconnectd-autostartrc:General:Autostart:false
Then, to re-enable it for a particular user, create a
~/.config/kdeconnectd-autostartrc file with Autostart=true in its [General]
section. (The file name "kdeconnectd-autostartrc" is arbitrary; I chose it in
hopes of avoiding conflicts with any standard files.)

2. /usr/share/dbus-1/services/org.kde.kdeconnect.service

According to KDE docs*, this file tells every user's dbus session to launch
kdeconnectd if something tries to contact it over d-bus. With this file in
place, kdeconnectd is launched by systemd at session start even if a user
disables the autostart .desktop file. The file can be moved to a backup
directory to avoid this. However, I think a better fix would be to identify
whatever is making org.kde.kdeconnect d-bus requests at session startup, and
prevent that instead.
* https://develop.kde.org/docs/use/d-bus/dbus_autostart_services/

Of course, these workarounds are hackish, and will probably revert to the
normal (unwanted) behavior whenever KDE Connect package updates are installed.
What we really need is for it to be configurable in the first place. Seems like
a good fit for the Background Services panel.

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

[kdeconnect] [Bug 452663] New: after reconnect the taskbar icon doesn't come back and notifications are muted

[Michael]

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

Bug ID: 452663
   Summary: after reconnect the taskbar icon doesn't come back and
notifications are muted
   Product: kdeconnect
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: michael.hm...@gmail.com
  Target Milestone: ---

after reconnect, the taskbar icon doesn't come back and notifications from
smartphone are cut off until you manually select the device in Kde Connect
settings

other capabilities like network Manager sees the active connection and starts
working immediately

this effect is the same on Linux Mint, Kde Neon, Arch
kde connect version installed is 21.12.3-1

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[Graham Perrin]

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

--- Comment #43 from Graham Perrin  ---
Created attachment 148178
  --> https://bugs.kde.org/attachment.cgi?id=148178=edit
Screen recording

(In reply to Graham Perrin from comment #41)

> … For me, the problem: 
> 
> * began a few weeks ago – almost certainly before Friday 4th March
> * is reproducible on campus, with a wired network connection
> * is _not_ reproducible at home, with a wired network connection. 
> 
> ### Environment
> 
> … 

I'm not yet certain, but from a few test results I suspect that I can avoid the
issue (on campus) by using the JavaEmbeddedFrame in my system tray to quit
LanguageTool before starting Remmina. 

This screen recording (at home, without attempting to start Remmina) shows use
of the context menu for the JavaEmbeddedFrame icon for LanguageTool. 



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

[kwin] [Bug 443723] "Display geometry when moving or resizing" does not work under wayland

[Michael Tunnell]

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

Michael Tunnell  changed:

   What|Removed |Added

 CC||m...@michaeltunnell.com

--- Comment #12 from Michael Tunnell  ---
I am disappointed to see this removed intentionally. I used this feature all
the time to resize windows for different usecases. I'll provide one of the
critical examples I use it for. I'm a podcaster on Destination Linux and during
preparation we have individual windows for each camera. I resize the windows to
1080p so that I can capture them via OBS. This feature made it very easy and
simple to make sure I always had it at the right sizing and positioning for
capture. The first episode we recorded after I updated to 5.24 actually sent me
into a panic because I didnt have time to figure out what happened. Luckily I
already knew how to workaround this with wmctrl so I did that and have been
doing so ever since.

I decided to see if there was a bug report to add my need to today and see that
it was intentionally removed without warning. I don't know how I would be able
to be warned as I am not sure there is a change advisory thing but that would
be very helpful as a side note.

I now see that wmctrl does not work on Wayland so this feature being removed in
KWin and my workaround only works in X means this will eventually create a
bigger problem for me later.

Note: this is not the only reason I use this feature, this was also great for a
lot of other reasons and was a great way to show people why KWin was awesome
because everyone has different reasons to find this helpful.

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

[plasmashell] [Bug 452632] plasmashell crash after activating compositor

[Bart]

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

Bart  changed:

   What|Removed |Added

 CC||b...@schelstraete.org

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

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

[Russell]

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

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

kwin_x11 (5.24.4) using Qt 5.15.3

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

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

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

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

[Russell]

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

Russell  changed:

   What|Removed |Added

 CC||russ...@obets.net

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

[systemsettings] [Bug 452561] The "Change Wallpaper..." button does nothing

[nicos]

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

--- Comment #4 from nicos  ---
(In reply to Nate Graham from comment #1)
> I can't reproduce this on Wayland. Didn't you say you could reproduce it
> somewhere/somehow, Fushan?

I'm on X11, I thought KDE had issues on Wayland. Can I switch to Wayland ?

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

[systemsettings] [Bug 452561] The "Change Wallpaper..." button does nothing

[nicos]

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

--- Comment #3 from nicos  ---
Yes, I didn't include it at first because I was doubtful about it, but when I
remove all activities and reboot, the popup does show, so it clearly looks like
it's linked to having more than one activities.

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

[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor

[phrxmd]

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

--- Comment #16 from phrxmd  ---
I'm on a trip at the moment and will test again as soon as I have access to the
dock, this will be in about 10 days.

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

[plasmashell] [Bug 452613] device notifier stops working

[davidblunkett]

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

--- Comment #3 from davidblunkett  ---
Thanks,  let's park until I can check with a newer version!

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

[kmail2] [Bug 426012] drag-n-drop to konsole seems to have stopped working

[davidblunkett]

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

davidblunkett  changed:

   What|Removed |Added

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

--- Comment #4 from davidblunkett  ---
Not sure what version I'm on now but it's working as of 2022 - I think an
option was restart during some update and this lead to the problem.  If it
helps anyone else it can be set in kmail:settings:configure:misc

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

[kig] [Bug 422665] kig crash on SVG export

[Axel Schwank]

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

Axel Schwank  changed:

   What|Removed |Added

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

--- Comment #9 from Axel Schwank  ---
Could a fix (at least the temporary fix mentioned in comment #3) please be
ported back to versions in which the error occurs? This is at least the case
down to 20.04. This version is still used in current versions of released
distros (e.g. openSuSE 15.3) and an update to 21 or above requires updating Qt
libraries or even more which causes a lot of effort.
Is there an easy alternative that I don't see? Should I ask the distributor for
an update to 20.12?
Thank you very much.

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

[krita] [Bug 452662] Two-finger pan/rotate gesture glitch with changing touch points

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |sh...@sdf.org

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

[frameworks-kirigami] [Bug 449031] ActionToolBar Overflow button not visible when created while already overflowing

[Alexander Stippich]

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

Alexander Stippich  changed:

   What|Removed |Added

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

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

[krita] [Bug 452131] kinetic scrolling/touch pan not working on cintiq

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 CC||sh...@sdf.org

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

[krita] [Bug 414431] Freehand Path Tool Stopped Working With Touch Screen Of Laptop & Stylus

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 CC||al...@alvinhc.com

--- Comment #2 from Alvin Wong  ---
Is this issue still valid on latest release (5.0.5)?

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

[kwin] [Bug 422938] Coordinated resize for adjacent tiled windows

[Neal Gompa]

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

Neal Gompa  changed:

   What|Removed |Added

 CC||ngomp...@gmail.com

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

[krita] [Bug 452131] kinetic scrolling/touch pan not working on cintiq

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 CC||al...@alvinhc.com
  Component|OpenGL Canvas   |Shortcuts and Canvas Input
   ||Settings

--- Comment #7 from Alvin Wong  ---
Uh, there seems to be a lot of things mixed in this report... Anyway,
considering only the issue of panning the canvas, first I shall clarify that
"kinetic scrolling" only applies to the dockers and certain lists, for example
the layers docker and the brush preset chooser. The touch gestures for
manipulating the canvas are configured separately from the "Canvas Input
Settings" section.

Krita's touch gesture support has been somewhat revamped in
https://invent.kde.org/graphics/krita/-/merge_requests/1341, which consequently
means the canvas input settings needs to be reset in order to get the new
default gestures, or the user can add the gestures themself. This also makes
the input profile somewhat incompatible between old and new versions.

We are in the process of changing some stuff regarding touch gestures in
https://invent.kde.org/graphics/krita/-/merge_requests/1395. For the time
being, when moving to nightly you may have to reassign some of the gestures
yourself.

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

[frameworks-kirigami] [Bug 449031] ActionToolBar Overflow button not visible when created while already overflowing

[Alexander Stippich]

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

Alexander Stippich  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kirigami/commit/5e97
   ||0d112f8479056b73e0463a9cfd0
   ||72be2f6a9

--- Comment #2 from Alexander Stippich  ---
Git commit 5e970d112f8479056b73e0463a9cfd072be2f6a9 by Alexander Stippich.
Committed on 15/04/2022 at 16:42.
Pushed by astippich into branch 'fixActionToolbar'.

fix moreButton visibility for ActionToolBar

when the button should be visible for construction

M  +1-1src/toolbarlayout.cpp

https://invent.kde.org/frameworks/kirigami/commit/5e970d112f8479056b73e0463a9cfd072be2f6a9

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

[frameworks-plasma] [Bug 452512] Many panel applets' Full Representations are too small in frameworks 5.93

[Cristóbal Veas]

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

Cristóbal Veas  changed:

   What|Removed |Added

 CC||cristobal.v...@pm.me

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

[krita] [Bug 426694] Pen touch breaks drag shortcuts

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 CC||al...@alvinhc.com
 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #2 from Alvin Wong  ---
I wonder if this is referring to the same issue as bug 438784? Please check if
this still happens on the latest version (5.0.5).

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

[knights] [Bug 445063] Unable to run application from krunner or the application launcher

[physkets]

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

--- Comment #2 from physkets  ---
It still occurs. Only one entry of 'Knights' shows up when I type that into
Krunner, and it is an "Application", so I think that isn't the issue.

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

[okular] [Bug 421206] okular presentation mode does not allow for WebRTC screensharing in Firefox/Chromium

[physkets]

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

--- Comment #7 from physkets  ---
It now works for me was well.

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

[kmymoney] [Bug 274130] Adding an extra Category/Account column in the ledger view

[bugzilla_noreply]

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

--- Comment #13 from adi@gmail.com ---
*** Bug 445604 has been marked as a duplicate of this bug. ***

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

[kmymoney] [Bug 445604] Ledger rows are too narrow in Windows

[bugzilla_noreply]

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

adi@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from adi@gmail.com ---


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

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

[kmymoney] [Bug 274130] Adding an extra Category/Account column in the ledger view

[bugzilla_noreply]

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

--- Comment #12 from adi@gmail.com ---
*** Bug 452617 has been marked as a duplicate of this bug. ***

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

[kmymoney] [Bug 452617] Legder row is not large enough

[bugzilla_noreply]

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

--- Comment #4 from adi@gmail.com ---


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

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

[kmymoney] [Bug 274130] Adding an extra Category/Account column in the ledger view

[bugzilla_noreply]

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

--- Comment #11 from adi@gmail.com ---
Created attachment 148176
  --> https://bugs.kde.org/attachment.cgi?id=148176=edit
Detail field cannot hold all information

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

[kmymoney] [Bug 274130] Adding an extra Category/Account column in the ledger view

[bugzilla_noreply]

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

adi@gmail.com changed:

   What|Removed |Added

 CC||adi@gmail.com
   Platform|Debian unstable |unspecified
 OS|Linux   |Microsoft Windows
Version|4.5.3   |git (master)

--- Comment #10 from adi@gmail.com ---
After 11 years since this bug has been reported...

I fully agree to what it has been said above.
Using KMyMoney 5.1.80-6b0d9509e in Windows 11.
When checking "Show all register entries in full detail", the Detail field in
ledger shows two rows of text: category and memo. And it cuts into memo a
little. It's not ok with two rows crammed in one row.

Instead of making the row wider, why not put category and memo in different
fields in the ledger, like it is in the entry form? Every information in it's
field, isn't that as it should be?

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

[kwin] [Bug 452522] Display changes to low resolution when HDMI was disconnected

[Zamundaaa]

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

--- Comment #1 from Zamundaaa  ---
Please check with "coredumpctl list" if KWin was the only thing that crashed

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

[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login

[Julius R.]

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

Julius R.  changed:

   What|Removed |Added

 CC||c3i8zv...@mozmail.com

--- Comment #95 from Julius R.  ---
Isecond the bug. In my case, the login sound is completely gone on two
different systems (running latest plasma).

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

[krita] [Bug 452662] New: Two-finger pan/rotate gesture glitch with changing touch points

[Alvin Wong]

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

Bug ID: 452662
   Summary: Two-finger pan/rotate gesture glitch with changing
touch points
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Shortcuts and Canvas Input Settings
  Assignee: krita-bugs-n...@kde.org
  Reporter: al...@alvinhc.com
  Target Milestone: ---

Created attachment 148175
  --> https://bugs.kde.org/attachment.cgi?id=148175=edit
tablet log, the gesture has been performed multiple times

Hold one finger down completely still, then flick (press, move, release) using
another finger repeatedly. Sometimes you can see the canvas jump as if you have
never released the second finger. Sometimes the canvas rotates 180 degrees.

IRC conversation:

 windragon: the problem seems here: 
 [2528] krita.tabletlog: "[   ] TouchUpdate  TouchScreen id:
100663306 hires:  930,   557.5 prs: 0.5 rot: 0; id: 100663297 hires: 
294, 288 prs: 0.5 rot: 0; "
 [2528] krita.tabletlog: "[   ] TouchUpdate  TouchScreen id:
100663297 hires:  294, 288 prs: 0.5 rot: 0; id: 100663307 hires: 
948,   342.5 prs: 0.5 rot: 0; "
 the touchpoints are flipped by the driver apparently. 
 sh_zam: the id values are mapped correctly though
 this doesn't seem like a regression caused by the gesture handling
code. Because we don't do anything which will require us to use IDs. Where as
for rotation code because angle is computed with the finger placement, it seems
that this *is* the source. 
 windragon: yes, but we calculate delta between fingers and assume them
to be in order always:
https://invent.kde.org/szaman/krita/blob/6c46fcbc1324b50756ff2e36b748c49c301ebec1/libs/ui/input/kis_rotate_canvas_action.cpp#L155-156
 which is an incorrect assumption
 windragon: yes 
 sh_zam: but more importantly, there is no sign in the latter half
of the tablet log that it even acknowledged that the second finger has ever
been lifted from the touchscreen
 the touch point id changed, but the gesture handling probably
didn't pick that up

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

[systemsettings] [Bug 34362] Support for configuring additional mouse buttons

[Carbug]

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

Carbug  changed:

   What|Removed |Added

 CC||b...@caralluin.de

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

[kmymoney] [Bug 452617] Legder row is not large enough

[bugzilla_noreply]

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

adi@gmail.com changed:

   What|Removed |Added

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

--- Comment #3 from adi@gmail.com ---


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

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

[kmymoney] [Bug 445604] Ledger rows are too narrow in Windows

[bugzilla_noreply]

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

--- Comment #3 from adi@gmail.com ---
*** Bug 452617 has been marked as a duplicate of this bug. ***

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

[kmymoney] [Bug 445604] Ledger rows are too narrow in Windows

[bugzilla_noreply]

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

adi@gmail.com changed:

   What|Removed |Added

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

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

[kdeplasma-addons] [Bug 452596] Comics widget does not show image

[Alexander Lohnau]

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

--- Comment #3 from Alexander Lohnau  ---
The "Unable to find service type for service" parts can be safely ignored,
because the conversion still works file (fixed in master for some time now).
Please install kdebugsettings, enable full debug for ork.kde.plasma.comic. Then
you should get more detailed logs.

>noticed after update last night.

What version did you update from?

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

[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor

[Zamundaaa]

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

Zamundaaa  changed:

   What|Removed |Added

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

--- Comment #15 from Zamundaaa  ---
We had a few fixes for output changes in the bugfix releases for 5.24, can you
still reproduce this with a newer release?

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

[kdevelop] [Bug 434670] Kdevelop fails to authenticate on Github

[Ikari]

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

Ikari  changed:

   What|Removed |Added

 CC||zach...@zachary-miller.com

--- Comment #2 from Ikari  ---
Nearly a year later, but I also have this problem. 
I am not on a VPN.
I do not have MFA enabled.

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

[kdeplasma-addons] [Bug 452596] Comics widget does not show image

[Alexander Lohnau]

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

Alexander Lohnau  changed:

   What|Removed |Added

   Assignee|notm...@gmail.com   |alexander.loh...@gmx.de

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

[kwin] [Bug 439577] kwin_wayland: no mouse cursor is captured in webrtc screen share through pipewire in Firefox or Chrome

[Chang Liu]

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

--- Comment #3 from Chang Liu  ---
I later found that this bug only occurred in Firefox. For Chrome everything
works fine.

I opened a bug report at Mozilla to push them to update the webrtc library.

https://bugzilla.mozilla.org/show_bug.cgi?id=1745610

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

[kwin] [Bug 439577] kwin_wayland: no mouse cursor is captured in webrtc screen share through pipewire in Firefox or Chrome

[postix]

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

--- Comment #2 from postix  ---
See also "Better mouse cursor support" [1]

[1]
https://jgrulich.cz/2022/02/16/webrtc-journey-to-make-wayland-screen-sharing-enabled-by-default/

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

[xdg-desktop-portal-kde] [Bug 452612] WebRTC in Chromium: Selecting screen / window fails and portal dialog opens a second time, where it then works

[postix]

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

postix  changed:

   What|Removed |Added

Summary|WebRTC in Chromium: Screen  |WebRTC in Chromium:
   |/ window picker dialog  |Selecting screen / window
   |opens a second time after   |fails and portal dialog
   |failing to select a source  |opens a second time, where
   |to share|it then works

--- Comment #1 from postix  ---
Side remark: Jan Grulich is currently working on getting rid of the second
portal dialog:

> this will allow us to skip the second portal dialog and I already have plan 
> in my head how to do this in WebRTC. This is currently only supported by 
> xdg-desktop-portal-gnome and xdg-desktop-portal-kde lacks this functionality.

[1]
https://jgrulich.cz/2022/02/16/webrtc-journey-to-make-wayland-screen-sharing-enabled-by-default/

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

[kwin] [Bug 452610] WebRTC in Chromium: Failed to query DMA-BUF modifiers

[postix]

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

postix  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from postix  ---
As of [1] it looks more like a PipeWire/Chromium issue than a KWin issue. If
I'm wrong, please feel to free to reopen of course! :-)

[1]
https://jgrulich.cz/2022/02/16/webrtc-journey-to-make-wayland-screen-sharing-enabled-by-default/

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

[dolphin] [Bug 451876] Dolphin slow start takes almost 5-6 seconds

[clyde]

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

clyde  changed:

   What|Removed |Added

 CC||ra...@globe.lu

--- Comment #1 from clyde  ---
same here, start is significantly delayed

Operating System: EndeavourOS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.3-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 630/PCIe/SSE2

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

[kwin] [Bug 450250] Game window looks ugly, mouse behaves incorrect

[Lach Sławomir]

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

Lach Sławomir  changed:

   What|Removed |Added

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

--- Comment #11 from Lach Sławomir  ---
Hi.
I provided info long time ago. I hope I do not mess up by setting it to
reopened. I think nobody look here, because of status. Thanks.

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

[systemsettings] [Bug 451367] Light and Dark theme settings put GTK apps in the opposite color mode from what's expected

[Marcel]

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

Marcel  changed:

   What|Removed |Added

 CC||marcmatias...@gmail.com

--- Comment #2 from Marcel  ---
Hello! About this problem I notice that when we change the theme in Settings >
Quick Settings menu to Light, ~/.kde4/share/config/kdeglobals update 
"[General]  ColorScheme" as "BreezeDark"  and vice versa. Maybe GTK is getting
this value as a reference to change theme color?

After logout and login, "[General]  ColorScheme" in
~/.kde4/share/config/kdeglobals shows the actual theme selected correctly and
GTK apps getting the right theme.

I hope this helps in some way, Thanks!

Operating System that i tested: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

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

[kaffeine] [Bug 452484] linux kernel upgrade to 5.17.1 Kaffeine 2.0.18 fails to read DVB device

[Avid]

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

--- Comment #6 from Avid  ---
I confirm the bugfix in linux kernel 5.17.3-arch1-1 #1 SMP PREEMPT Thu, 14 Apr
2022 01:18:36 + x86_64 GNU/Linux
works with Kaffeine 2.0.18 with my device.

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

[Falkon] [Bug 452661] New: Falkon frozen while autosaving the running session

[Theo]

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

Bug ID: 452661
   Summary: Falkon frozen while autosaving the running session
   Product: Falkon
   Version: 22.03.80
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: alpha0...@yahoo.de
  Target Milestone: ---

STEPS TO REPRODUCE
1. Use Falkon with many tabs.
2. Open new tab.

OBSERVED RESULT
After a few seconds Falkon autosaves the running session into the file
session.dat under the profile directory. Falkon freezes until the saving has
finished.

EXPECTED RESULT
The application should stay usable when doing background tasks the user cannot
control.

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

[plasmashell] [Bug 452660] New: Random Plasma crashes

[Stefan Schmidt]

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

Bug ID: 452660
   Summary: Random Plasma crashes
   Product: plasmashell
   Version: 5.24.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: thrimbor+kdeb...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.3-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
I'm experiencing Plasma crashes, but so far couldn't narrow it down to some
specific action or situation.
Today it crashed when I clicked on the icon of an open dolphin instance in the
task bar, two days ago it crashed when I opened Firefox (which opens a lot of
windows).
These actions do not reliably reproduce the crash, and I've had crashes where I
didn't even actively do anything.

I've tried to install all debug symbols, but the debug dialog mentioned that
the symbols for /usr/bin/plasmashell are still not there. I will try to have
debuginfod ready the next time.

The crash can be reproduced sometimes.

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

[KCrash Handler]
#4  std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=0x70006f006f0070, this=,
__m=) at /usr/include/c++/11.2.0/bits/atomic_base.h:479
#5  QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=...,
_q_value=) at /usr/include/qt/QtCore/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed() const (this=0x70006f006f0070,
this=) at /usr/include/qt/QtCore/qbasicatomic.h:107
#7  QWeakPointer::internalData() const (this=0x5630186a0e48) at
/usr/include/qt/QtCore/qsharedpointer_impl.h:698
#8  QPointer::data() const (this=0x5630186a0e48, this=)
at /usr/include/qt/QtCore/qpointer.h:77
#9  QPointer::operator QObject*() const (this=0x5630186a0e48,
this=) at /usr/include/qt/QtCore/qpointer.h:83
#10 QQmlDelegateModelPrivate::destroyCacheItem(QQmlDelegateModelItem*)
(this=0x563014e01b10, cacheItem=0x5630186a0e20) at
/usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:643
#11 0x7f86f5be1bb2 in std::function::operator()(QQmlDelegateModelItem*) const
(__args#0=0x5630186a0e20, this=0x7ffefb8e8220) at
/usr/include/c++/11.2.0/bits/std_function.h:560
#12 QQmlReusableDelegateModelItemsPool::drain(int, std::function) (this=0x563014e01d08, maxPoolTime=0,
releaseItem=...) at
/usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:3821
#13 0x7f86f5bd1c6b in QQmlDelegateModelPrivate::drainReusableItemsPool(int)
(maxPoolTime=, this=) at
/usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1118
#14 QQmlDelegateModel::drainReusableItemsPool(int) (this=,
maxPoolTime=) at
/usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1123
#15 0x7f86f86d0f15 in QQuickListView::geometryChanged(QRectF const&, QRectF
const&) (this=0x5630172220b0, newGeometry=..., oldGeometry=...) at
/usr/src/debug/qtdeclarative/src/quick/items/qquicklistview.cpp:3418
#16 0x7f86f85fd530 in QQuickItem::setSize(QSizeF const&)
(this=this@entry=0x5630172220b0, size=...) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickitem.cpp:7045
#17 0x7f86f0efd2fb in QQuickControlPrivate::resizeContent()
(this=) at
/usr/src/debug/qtquickcontrols2/src/quicktemplates2/qquickcontrol.cpp:402
#18 0x7f86f0efff6b in QQuickControl::geometryChanged(QRectF const&, QRectF
const&) (this=0x56301619e5c0, newGeometry=..., oldGeometry=...) at
/usr/src/debug/qtquickcontrols2/src/quicktemplates2/qquickcontrol.cpp:
#19 0x7f86f85fd3ec in QQuickItem::setImplicitHeight(double)
(this=0x56301619e5c0, h=) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickitem.cpp:6944
#20 0x7f86f8149b11 in QQmlPropertyData::writeProperty(QObject*, void*,
QFlags) const (this=,
target=, value=, flags=...) at
../../include/QtQml/5.15.3/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:375
#21 0x7f86f819f73b in GenericBinding<6>::doStore(double,
QQmlPropertyData const*, QFlags) const (flags=...,
pd=, value=, this=0x563014c4e090) at
/usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:342
#22 GenericBinding<6>::write(QV4::Value const&, bool,
QFlags) (this=0x563014c4e090, result=...,
isUndefined=, flags=...) at
/usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:315
#23 0x7f86f81a82e6 in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) (this=0x563014c4e090,
watcher=..., flags=..., scope=) at
/usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:258
#24 0x7f86f81a91cc in
QQmlBinding::update(QFlags) (this=0x563014c4e090,
flags=...) at 

[Falkon] [Bug 451782] Falkon crashes on startup

[steen . meyer]

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

steen.me...@gmail.com  changed:

   What|Removed |Added

 CC||steen.me...@gmail.com

--- Comment #1 from steen.me...@gmail.com  ---
I have the same, since the last few weeks, probably since the upgrade, Falkon
cannot start. Sometimes a window shows up for a fraction of a second. Error
message in console:
WebEngineContext used before QtWebEngine::initialize() or OpenGL context
creation failed.
QGLXContext: Failed to create dummy context
Failed to load python support plugin "Cannot load library
/usr/lib/qt/plugins/falkon/PyFalkon.so:
(libpyside2.cpython-310-x86_64-linux-gnu.so.5.15: cannot open shared object
file: No such file or directory)"
Falkon: 1 extensions loaded
Fatal: Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
options QFlags(), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples 0, swapBehavior
QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
zsh: IOT instruction (core dumped)  

There is no 'libpyside2' on the system and no
'cpython-310-x86_64-linux-gnu.so.5' but lots of
'cpython-310-x86_64-linux-gnu.so'

After pyside2 is installed the same behaviour produces this error:
WebEngineContext used before QtWebEngine::initialize() or OpenGL context
creation failed.  
QGLXContext: Failed to create dummy context
Failed to load python support plugin "Cannot load library
/usr/lib/qt/plugins/falkon/PyFalkon.so:
(/usr/lib/qt/plugins/falkon/PyFalkon.so: undefined symbol:
_ZN6PySide16fillQtPropertiesEP7_objectPK11QMetaObjectS1_PPKcj)"
Falkon: 1 extensions loaded
Fatal: Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
options QFlags(), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples 0, swapBehavior
QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace
QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 

Note: /usr/lib/qt/plugins/falkon/PyFalkon.so exists.

Linux 5.15.28-1-MANJARO

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

[Discover] [Bug 375877] Fetching Updates takes incredibly long time

[Jonathan Wakely]

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

--- Comment #12 from Jonathan Wakely  ---
Time to run the command and then quit the app as soon as it finishes
"Loading..." the updates.

$ time plasma-discover --backends flatpak
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.


real4m46.710s
user0m22.899s
sys 0m8.797s

Running the same command again right away:

$ time plasma-discover --backends flatpak
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.


real0m10.474s
user0m4.988s
sys 0m2.028s

That's still pretty slow even with a fresh cache.

And for PK:

$ time plasma-discover --backends packagekit
adding empty sources model QStandardItemModel(0x56366b77b160)
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.


** (process:795073): WARNING **: 14:40:20.266: System cache issue: The
AppStream system cache was updated, but some errors were detected, which might
lead to missing metadata. Refer to the verbose log for more information.

real0m3.491s
user0m2.518s
sys 0m0.452s


So it seems that flatpak is the slow part, even when the cache is up to date.
If I just run "plasma-discover" and click on the "Fetching updates..." (which
quickly turns into "Update (32)") menu item at the bottom left, the progress
bar is still going, at about 95% or so, until at least 10 seconds after
starting the app. That matches what I see when I click on the systray popup: it
shows a progress bar at about 95% and stays like that for a subjectively long
time (sometimes over 30 seconds).

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

[Discover] [Bug 375877] Fetching Updates takes incredibly long time

[Jonathan Wakely]

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

--- Comment #11 from Jonathan Wakely  ---
(In reply to Aleix Pol from comment #9)
> I am sorry but this is simply not true. In PackageKitBackend.cpp:107 you can
> see that we only refresh the cache if it's over 1 hour old.

And yet when I've JUST booted up and got the systray popup as soon as I login,
it takes 30+ seconds to show the available updates. Is the systray popup using
stale data straight after boot, so then when I open the GUI it refreshes?


> It would be useful if you can provide feedback if you have the same problem
> when running with:
> 
> * plasma-discover --backends flatpak
> * plasma-discover --backends packagekit


I'll try this and report back.

> Also could you state which distros are you on respectively?

See above, Fedora 34

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

[kate] [Bug 452659] New: Markdown Preview Uses Wrong Encoding

[Peter Shkenev]

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

Bug ID: 452659
   Summary: Markdown Preview Uses Wrong Encoding
   Product: kate
   Version: 22.03.80
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plugin-preview
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: santury...@gmail.com
  Target Milestone: ---

Created attachment 148174
  --> https://bugs.kde.org/attachment.cgi?id=148174=edit
Screenshot which shows the bug

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

STEPS TO REPRODUCE
1. Open Markdown document with non-ASCII charaters
2. Load Preview plugin
3. Open Preview tab

OBSERVED RESULT
Wrong encoding is used, thus text is unreadable. See attached screenshot

EXPECTED RESULT
Preview uses correct encoding to render the document

SOFTWARE/OS VERSIONS
Windows: 10 21H2 
KDE Frameworks Version: 5.92.0
Qt Version: 5.12.2

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

[Discover] [Bug 445761] Discover offers me to remove code

[Christopher Yeleighton]

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

Christopher Yeleighton  changed:

   What|Removed |Added

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

--- Comment #16 from Christopher Yeleighton  ---
I have a package that contains a file .  [!] Discover offers to remove the package even though it is not installed. 
Removing the package results in an internal error toast.  This behaviour
repeats.

Notes: 
1. the file  exists on my system but
it does not belong to any package.
2. pkcon install-local --allow-untrusted mysteriously fails with a critical
error (after an attempt to install the package).
3. zypp history does not mention anything except for PK_TMP_DIR manipulations.
4. pkcon install-local
/var/tmp/build-root/home/abuild/rpmbuild/RPMS/noarch/http-dell-site-0-0.noarch.rpm
5. zypper in fails with Signature verification failed [6-File is unsigned].  I
ignored the warning and the package installed all right.

I understand that all this background has nothing to do with Discover.  The
problem with Discover is marked [!].

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

[dolphin] [Bug 452658] New: dolphin segmentation fault on refresh in cifs mounted git repository after git rebase was performed externally

[Andreas Sturmlechner]

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

Bug ID: 452658
   Summary: dolphin segmentation fault on refresh in cifs mounted
git repository after git rebase was performed
externally
   Product: dolphin
   Version: 21.12.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ast...@gentoo.org
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (21.12.3)
 (Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.10.109-gentoo x86_64
Windowing System: X11
Distribution: Gentoo/Linux
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
dolphin crashed in the background (without manually triggering a refresh) after
git rebase was performed in yakuake on the repository currently viewed in
dolphin. This has happened the second time in two weeks now.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6  QSharedDataPointer::~QSharedDataPointer
(this=0x55dd803d2380, __in_chrg=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/include/g++-v11/bits/atomic_base.h:385
#7  KFileItem::~KFileItem (this=0x55dd803d2380, __in_chrg=) at
/var/tmp/portage/kde-frameworks/kio-5.92.0/work/kio-5.92.0/src/core/kfileitem.cpp:604
#8  0x7f2e2a87daed in QList::node_destruct (n=0x55dd803d2380,
this=0x55dd7f8a9160) at /usr/include/qt5/QtCore/qlist.h:479
#9  QList::erase (it=..., this=0x55dd7f8a9160) at
/usr/include/qt5/QtCore/qlist.h:566
#10 KCoreDirListerCache::reinsert (this=this@entry=0x7f2e2a8ec4a0 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, item=...,
oldUrl=...) at
/var/tmp/portage/kde-frameworks/kio-5.92.0/work/kio-5.92.0/src/core/kcoredirlister_p.h:287
#11 0x7f2e2a86e22e in KCoreDirListerCache::processPendingUpdates
(this=0x7f2e2a8ec4a0 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at
/var/tmp/portage/kde-frameworks/kio-5.92.0/work/kio-5.92.0/src/core/kcoredirlister.cpp:2023
#12 0x7f2e28f2918e in QtPrivate::QSlotObjectBase::call (a=0x7ffeab1bc560,
r=0x7f2e2a8ec4a0 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>,
this=0x55dd7f4c9710) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x7f2e2a8ec570 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder+208>,
signal_index=3, argv=0x7ffeab1bc560) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:3886
#14 0x7f2e28f231af in QMetaObject::activate (sender=,
m=m@entry=0x7f2e291c6300 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeab1bc560)
at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:3946
#15 0x7f2e28f2d14a in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#16 0x7f2e28f2130f in QObject::event (this=0x7f2e2a8ec570 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder+208>,
e=0x7ffeab1bc6b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:1336
#17 0x7f2e298ae63f in QApplicationPrivate::notify_helper (this=, receiver=0x7f2e2a8ec570 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder+208>,
e=0x7ffeab1bc6b0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qapplication.cpp:3637
#18 0x7f2e28ef6c18 in QCoreApplication::notifyInternal2
(receiver=0x7f2e2a8ec570 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder+208>,
event=0x7ffeab1bc6b0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1064
#19 0x7f2e28f45fcb in QTimerInfoList::activateTimers (this=0x55dd7f415520)
at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qtimerinfo_unix.cpp:643
#20 0x7f2e28f46894 in timerSourceDispatch (source=) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:183
#21 0x7f2e26d359eb in g_main_dispatch (context=0x7f2e1c005000) at
../glib-2.70.4/glib/gmain.c:3381
#22 g_main_context_dispatch (context=0x7f2e1c005000) at
../glib-2.70.4/glib/gmain.c:4099
#23 0x7f2e26d35c98 in g_main_context_iterate
(context=context@entry=0x7f2e1c005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.70.4/glib/gmain.c:4175
#24 

[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)

[Ruben Kelevra]

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

Ruben Kelevra  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||cyr...@gmail.com
 Ever confirmed|0   |1

--- Comment #14 from Ruben Kelevra  ---
S ... is this going to be fixed or does your users have to change to
another DE?

I mean it's 3 years now and I still get memory leaks on a daily basis (with a
sliding desktop wallpaper - not sure why this memory leak issue isn't fixed
after 8 years...)

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

[plasmashell] [Bug 448853] When removing the cable of the connected phone, KDE hangs

[bugzilla_noreply]

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

--- Comment #13 from devakan...@gmail.com ---
The problem is no longer reproducible. The task can be closed. Thx

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

[kde-cli-tools] [Bug 446199] kstart5 ignores --desktop option

[witchhunter]

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

witchhunter  changed:

   What|Removed |Added

 CC||witchhunterpro@protonmail.c
   ||om

--- Comment #3 from witchhunter  ---
The command is also ignoring '--alldesktops' argument.

KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Graphics Platform: X11

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

[Powerdevil] [Bug 304696] Display is dimmed in half the time you configure to dim

[Tim Siegel]

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

Tim Siegel  changed:

   What|Removed |Added

Version|5.2.0   |5.24.4
 CC||siege...@gmail.com

--- Comment #18 from Tim Siegel  ---
This bug is still present, KDE 5.24.4.

There are 5 proposed solutions, ranked from worst to best.

1. Do nothing, it works as intended.
2. Keep the same behavior, except dim less (90%, 75%). This will cause just as
much end-user confusion, while also upsetting people who are used to the
current behavior.
3. Keep the same behavior, but document it in the settings interface. This is
the least we could do, should ruffle no feathers, and won't even unbalance the
UI since that page already contains several long textual explanations.
4. Keep the behavior as is, except change the dimming times to be 1, ⁵⁄₄, ³⁄₂
(instead of ½, ¾, 1), so the screen stays full brightness until the requested
dimming time.
5. Remove this unnecessary feature. Dim 50% at the requested time, and let
"Screen Energy Saving: Switch off" do the rest.

"Do nothing" has been the KDE response for a decade at this point, and yet it
is clearly the wrong answer. There is no way to read "Dim screen: After 3
minutes" to mean "50% at 1:30".

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

[krita] [Bug 451859] Glitchy transparent areas appear on canvas while painting

[bugzilla_noreply]

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

--- Comment #19 from acc4commissi...@gmail.com ---
Yes, it is fixed as far as I tested. I don't see any glitches anymore. I'll
post if it happens again.

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

[kwin] [Bug 452657] New: [kwin_wayland] 100% cpu usage after user switching

[bugzilla_noreply]

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

Bug ID: 452657
   Summary: [kwin_wayland] 100% cpu usage after user switching
   Product: kwin
   Version: 5.24.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kt47uo5u...@protonmail.com
  Target Milestone: ---

SUMMARY
After user switching kwin_wayland on 100% cpu usage

STEPS TO REPRODUCE
1. kwin_wayland session in user A
2. switch to user B

OBSERVED RESULT
Often 1 cpu core is on 100% from process of user A:
/usr/bin/kwin_wayland --wayland-fd 5 --socket wayland-0 --xwayland-fd 6
--xwayland-fd 7 --xwayland-display :1 --xwayland-xauthority
/run/user/1001/xauth_zJPcnB --xwayland

If I switch back to user A the cpu usage is back to normal, but sometimes
kwin_wayland from user B is up to 100% again and vice verca.

EXPECTED RESULT
Normal cpu usage

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.3
Graphics Platform: Wayland

ADDITIONAL INFORMATION

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

[kalendar] [Bug 452656] Unable to upload events to radicale

[aunderscored]

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

--- Comment #2 from aunderscored  ---
Interestingly, it seems that using `Europe/Berlin` works? I'd assume this is
due to that having DST info being included, thus causing it to be populated.

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

[krita] [Bug 451859] Glitchy transparent areas appear on canvas while painting

[Alvin Wong]

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

--- Comment #18 from Alvin Wong  ---
Please let me know if this is fixed on the latest nightly.

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