[krita] [Bug 493830] Krita freezes when trying to save a removed layer in a folder

[Bogdan Costisor]

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

--- Comment #2 from Bogdan Costisor  ---
Thank you for the workaround. If I disable passthrough temporarily I can save
:)

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

[krita] [Bug 493830] New: Krita freezes when trying to save a removed layer in a folder

[Bogdan Costisor]

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

Bug ID: 493830
   Summary: Krita freezes when trying to save a removed layer in a
folder
Classification: Applications
   Product: krita
   Version: 5.2.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: bogdancosti...@gmail.com
  Target Milestone: ---

Created attachment 174202
  --> https://bugs.kde.org/attachment.cgi?id=174202&action=edit
File with problem

SUMMARY
It looks like Krita has some issues with trying to remove or move a layer
inside a folder. After removing a layer and trying to save I get a "Remove
Node" message that seems to never end.
I've attached a file for testing where I reproduce 100% all the time.

STEPS TO REPRODUCE
1. Open the attached file
2. Try to remove layer "Ivy Angles" (the one that is hidden)
3. Save 

OBSERVED RESULT
Krita displays a message "Waiting for operation to complete..." and in the
middle of the message box "Remove Nodes" is displayed. At this stage, nothing
can be done.

EXPECTED RESULT
Save The file

SOFTWARE/OS VERSIONS
Windows: Windows 11

ADDITIONAL INFORMATION
I'm using the following plugins: Shortcut composer v1.5.4

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

[plasmashell] [Bug 493675] Disks & Devices applet doesn't show LUKS-encrypted disks as mountable devices anymore

[Bogdan Onofriuchuk]

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

--- Comment #8 from Bogdan Onofriuchuk  ---
I'll take a look today after work.

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

[kde-cli-tools] [Bug 460878] System Color Selection Crash

[Bogdan]

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

--- Comment #4 from Bogdan  ---
Created attachment 172391
  --> https://bugs.kde.org/attachment.cgi?id=172391&action=edit
New crash information added by DrKonqi

kcmshell5 (5.27.9) using Qt 5.15.11

Hi,
Attempted to change Animation settings

Cheers

-- Backtrace (Reduced):
#6  0x7f23d8d5ee07 in KCModuleProxy::save() () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
[...]
#9  0x7f23d85c2a06 in QAbstractButton::clicked(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
[...]
#12 0x7f23d85c4ad7 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f23d850f95e in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f23d84cc763 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

[kde-cli-tools] [Bug 460878] System Color Selection Crash

[Bogdan]

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

Bogdan  changed:

   What|Removed |Added

 CC||bogdanste...@hotmail.com

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

[ark] [Bug 490640] New: Crash when performing drag and drop a folder from the ZIP

[Bogdan Bivolaru]

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

Bug ID: 490640
   Summary: Crash when performing drag and drop a folder from the
ZIP
Classification: Applications
   Product: ark
   Version: 24.05.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: bogdan.bivol...@gmail.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Application: ark (24.05.2)

Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.9-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Forty)"
DrKonqi: 6.1.2 [CoredumpBackend]

-- Information about the crash:
Crash when performing drag and drop a folder from the ZIP archive to a local
folder in Dolphin

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/ark...
Downloading separate debug info for
/home/bogdanbiv/.cache/debuginfod_client/4e9d7f99d31b7a2ef994d93d9d7309367c827710/debuginfo...
[New LWP 46717]
[New LWP 46721]
[New LWP 46720]
[New LWP 46722]
[New LWP 46723]
[New LWP 46750]
[New LWP 46737]
[New LWP 46725]
[New LWP 46736]
[New LWP 46748]
[New LWP 46747]
[New LWP 46726]
[New LWP 46727]
[New LWP 46739]
[New LWP 46738]
[New LWP 46735]
[New LWP 46724]
[New LWP 46740]
[New LWP 46751]
[New LWP 46728]
Downloading separate debug info for /lib64/libkerfuffle.so.24...
Downloading separate debug info for /lib64/libKF6Parts.so.6...
Downloading separate debug info for /lib64/libQt6Widgets.so.6...
Downloading separate debug info for
/home/bogdanbiv/.cache/debuginfod_client/9c67000fb781501ff77ba165bb521e4e3f35eebb/debuginfo...
Downloading separate debug info for /lib64/libQt6Gui.so.6...
Downloading separate debug info for /lib64/libQt6Core.so.6...
Downloading separate debug info for /lib64/libKF6FileMetaData.so.3...
Downloading separate debug info for
/home/bogdanbiv/.cache/debuginfod_client/a0b53203525b3e951ec67744dc7b2195327945d8/debuginfo...
Downloading separate debug info for /lib64/libKF6Pty.so.6...
Downloading separate debug info for /lib64/libQt6DBus.so.6...
Downloading separate debug info for /lib64/libQt6Network.so.6...
Downloading separate debug info for /lib64/libQt6Xml.so.6...
Downloading separate debug info for /lib64/libQt6PrintSupport.so.6...
Downloading separate debug info for /lib64/libQt6QuickControls2.so.6...
Downloading separate debug info for
/home/bogdanbiv/.cache/debuginfod_client/4ccd9b5fb34cd23c83bc25390a7c8a9f394191d3/debuginfo...
Downloading separate debug info for /lib64/libQt6Quick.so.6...
Downloading separate debug info for /lib64/libQt6QuickTemplates2.so.6...
Downloading separate debug info for /lib64/libQt6Qml.so.6...
Downloading separate debug info for /lib64/libQt6QmlModels.so.6...
Downloading separate debug info for /lib64/libQt6OpenGL.so.6...
Downloading separate debug info for /lib64/libEGL_mesa.so.0...
Downloading separate debug info for
/home/bogdanbiv/.cache/debuginfod_client/57b25dcbe756ba2733298697fb3e8fd81d9187ec/debuginfo...
Downloading separate debug info for /lib64/libgbm.so.1...
Downloading separate debug info for /lib64/libglapi.so.0...
Downloading separate debug info for /usr/lib64/dri/radeonsi_dri.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/iconengines/libqsvgicon.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/parts/arkpart.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/imageformats/libqjpeg.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/imageformats/libqgif.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/imageformats/libqico.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kerfuffle/kerfuffle_libzip.so...
Downloading separate debug info for /lib64/libzip.so.5...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/ark
/home/bogdanbiv/Downloads/ANNIVERSARY_ARTBOOK.zip'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f7451683b00 (LWP 46717))]

Cannot QML trace cores :(
Downloading source file
/usr/src/debug/mesa-24.1.4-2.fc40.x86_64/redhat-linux-build/../src/c11/impl/threads_posix.c...
Downloading source file
/usr/src/debug/mesa-24.1.4-2.fc40.x86_64/redhat-linux-build/../src/util/u_queue.c...
Downloading source file
/usr/src/debug/qt6-qtbase-6.7.2-4.fc40.x86_64/src/corelib/thread/qthread_unix.cpp...
Downloading source file
/usr/src

[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle

[Bogdan Dragoiu]

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

--- Comment #5 from Bogdan Dragoiu  ---
Here's a recording: https://imgur.com/a/f09s7Cg
It seems even initially it starts at over 1.5 core, then ramps up to over 3
cores and I hear the fan increasing speed.

I am on 12c/24t 128GB DDR4 so the overall system is not starved for resources.

Spectacle is likely impacted by changes upstream as I got spectacle-24.05.0-2
from Fedora repos on 2024-06-08, but my update to Plasma 6.1 was almost 2 weeks
later on 2024-06-20.

I use Spectacle almost daily to record small clips of devlogs to share with
friends, that is why I noticed instantly.

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

[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle

[Bogdan Dragoiu]

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

Bogdan Dragoiu  changed:

   What|Removed |Added

 CC||dragoiu.bog...@gmail.com

--- Comment #2 from Bogdan Dragoiu  ---
Same exact problem with the same log messages after the Plasma 6.1 update.
Work for a couple of seconds then a lot of the filter queue messages show up:
```
kpipewire_record_logging: Filter queue is full, dropping frame 
```

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

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

[konsole] [Bug 339783] Wishlist: Tab bar on the left/right side of UI

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REPORTED

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
There is no extra info to provide on this bug, and should not have been in the
NEEDSINFO status in the first place. But automation is automation.

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

[kdenlive] [Bug 483281] No microphone detected on kdenlive

[Bogdan]

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

Bogdan  changed:

   What|Removed |Added

 CC||dmtr...@gmail.com

--- Comment #2 from Bogdan  ---
Same situation on Linux Mint and Windows 11.

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

[plasmashell] [Bug 484255] Show only tasks "From current screen" ignores after woke up

[bogdan]

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

--- Comment #4 from bogdan  ---
(In reply to Nick from comment #3)
> Hi
> 
> I've tried to duplicate this on my Neon (Plasma 6.0.2) system but failed.
> Here's what I've tried:
> 
> Laptop with monitor plugged into my HDMI port.
> Extend the desktop to both screens
> Add a new panel to the external monitor so I have a panel on each
> Configure the Icons-only Taskbar -> Behavior -> Show only tasks -> Tick only
> "From current session
> 
> Now I open Firefox and move it between the screens. I only see the Firefox
> icon on the screen it is on (it dissapears from the other screen when it
> moves off).
> 
> I then put my laptop to sleep and re-awake it.
> 
> I then see the same functionality (i.e. the Firefox icon is only showed on
> the screen with the Firefox window.
> 
> Could you please double-check if I am testing this correctly? Thanks, Nick

Hi, all correct except one thing - From current *screen*, not session
ps: on last 5th kde version all was normal

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

[plasmashell] [Bug 484255] Show only tasks "From current screen" ignores after woke up

[bogdan]

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

--- Comment #2 from bogdan  ---
Created attachment 167615
  --> https://bugs.kde.org/attachment.cgi?id=167615&action=edit
expected screenshot

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

[plasmashell] [Bug 484255] Show only tasks "From current screen" ignores after woke up

[bogdan]

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

--- Comment #1 from bogdan  ---
Created attachment 167614
  --> https://bugs.kde.org/attachment.cgi?id=167614&action=edit
observed screenshot

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

[plasmashell] [Bug 484255] New: Show only tasks "From current screen" ignores after woke up

[bogdan]

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

Bug ID: 484255
   Summary: Show only tasks "From current screen" ignores after
woke up
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: bogdan2...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

SUMMARY
When pc woke up after sleep, icons ignores "From current screen" option & shows
on each displays

STEPS TO REPRODUCE
1.  In icons only taskmanager widget i have checked the one option
Show only tasks:
 - From current screen
2. Wait until displays turns off
3. Wake up any way (mouse, keyboard)

OBSERVED RESULT
Icons on icons only widget shows on each displays

EXPECTED RESULT
Icons on icons only widget shows on their display

SOFTWARE/OS VERSIONS
Linux: 6.8.1-arch1-1 (64-bit)
Graphics Platform: Wayland
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Dual monitor setup

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

[plasmashell] [Bug 483929] There is no smooth scrolling to the value of 6.

[bogdan]

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

bogdan  changed:

   What|Removed |Added

 CC||bogdan2...@gmail.com

--- Comment #6 from bogdan  ---
same problem

Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz
Memory: 31.3 ГиБ of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B24
System Version: 2.0

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

[kate] [Bug 482227] Kate crashes when saving file

[Bogdan]

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

--- Comment #4 from Bogdan  ---
Output: https://pastebin.com/Ypkw3BA9

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

[kate] [Bug 482227] Kate crashes when saving file

[Bogdan]

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

--- Comment #2 from Bogdan  ---
Here is the output: https://pastebin.com/S9kezGjh
It might be the rust LSP that's crashing Kate, but I'm not sure. I opened
different source files and I don't get any crashes.

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

[kate] [Bug 482227] New: Kate crashes when saving file

[Bogdan]

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

Bug ID: 482227
   Summary: Kate crashes when saving file
Classification: Applications
   Product: kate
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: moonfire.bog...@gmail.com
  Target Milestone: ---

Application: kate (24.02.0)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.6-arch1-2 x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 6.0.0 [CoredumpBackend]

-- Information about the crash:
Kate crashes everytime when saving the file I'm editing

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), 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 6660]
[New LWP 6661]
[New LWP 6665]
[New LWP 6662]
[New LWP 6675]
[New LWP 6685]
[New LWP 6678]
[New LWP 6679]
[New LWP 6686]
[New LWP 6664]
[New LWP 6683]
[New LWP 6663]
[New LWP 6674]
[New LWP 6677]
[New LWP 6684]
[New LWP 6676]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `kate'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x713a150ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x713a0f80ee80 (LWP 6660))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x713a0f80ee80 (LWP 6660))]

Thread 16 (Thread 0x7139ed6006c0 (LWP 6676)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x713a158a3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x713a158a64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#6  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7139db4006c0 (LWP 6684)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x713a158a3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x713a158a64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#6  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7139ecc006c0 (LWP 6677)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x713a158a3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x713a158a64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#6  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7139eea006c0 (LWP 6674)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x713a158a3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x713a158a64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#6  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 12 (Thread 0x713a0d0006c0 (LWP 6663)):
#0  0x713a151190bf in poll () at /usr/lib/libc.so.6
#1  0x713a103f3b18 in ??? () at /usr/lib/libQt6WaylandClient.so.6
#2  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#3  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#4  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7139dbe006c0 (LWP 6683)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x713a158a3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x713a158a64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x713a158a0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x713a150a955a in ??? () at /usr/lib/libc.so.6
#6  0x713a15126a3c in ??? () at /usr/lib/libc.so.6

Thread 10 (Thread 0x713a05a006c0 (LWP 6664)):
#0  0x713a150a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x713a150a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7139f708681c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x7139f

[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot

[Ovidiu-Florin BOGDAN]

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

--- Comment #13 from Ovidiu-Florin BOGDAN  ---
I'm not closing it myself since there were more people reporting this besides
me. I'll leave this to the devs to decide.

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

[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot

[Ovidiu-Florin BOGDAN]

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

--- Comment #12 from Ovidiu-Florin BOGDAN  ---
I have not experienced this for quite some time now. I have changed laptops and
reinstalled Fedora several times since, with newer versions. IMHO we can close
this.

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

[okular] [Bug 469705] okular does not find any certificate for digital signing

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||kde.kf...@simplelogin.com

--- Comment #8 from Ovidiu-Florin BOGDAN  ---
I had this issue as well. My solution for this was to go in the Okular PDF
platforms settings and ensure that the Firefox profile that Okular looks in is
the same one that Firefox is using.

In my case Okular was looking in a non-existing directory by default. As soon
as I changed it to the proper path the certificate appeared and was usable.

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

[kdeconnect] [Bug 471283] Messaging app does not show contact names, only phone numbers

[Ovidiu-Florin BOGDAN]

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

--- Comment #3 from Ovidiu-Florin BOGDAN  ---
Yes, that solved it for me. Thank you.

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||kde.kf...@simplelogin.com

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

[kdeconnect] [Bug 471283] Messaging app does not show contact names, only phone numbers

[Ovidiu-Florin BOGDAN]

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

--- Comment #1 from Ovidiu-Florin BOGDAN  ---
Created attachment 159803
  --> https://bugs.kde.org/attachment.cgi?id=159803&action=edit
Screenshot of messaging application

Screenshot of messaging application

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

[kdeconnect] [Bug 471283] New: Messaging app does not show contact names, only phone numbers

[Ovidiu-Florin BOGDAN]

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

Bug ID: 471283
   Summary: Messaging app does not show contact names, only phone
numbers
Classification: Applications
   Product: kdeconnect
   Version: 23.04.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: kde.kf...@simplelogin.com
  Target Milestone: ---

SUMMARY
When using the Messaging app (SMS) from the desktop, all the message recipients
are shown as phone number only. The contact name is not shown at all, even
though the KDE Connect app on the Android phone has Contacts permission.

A name is shown only for the recipients that have names from the network (phone
numbers I don't have in my agenda).

See attached screenshot.

STEPS TO REPRODUCE
1. Connect Android phone to KDE desktop via KDE Connect
2. Open SMS/messaging application

OBSERVED RESULT
SMS conversations are shown, but all recipients are shown as phone numbers.

EXPECTED RESULT
Recipients to be shown as names as they are in the address book.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6820HQ CPU @ 2.70GHz
Memory: 31.2 GiO of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Manufacturer: Dell Inc.
Product Name: Precision 3510

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

[systemsettings] [Bug 465484] System Settings Crashes While Importing A OpenVPN Config

[Bogdan Ilchyshyn]

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

Bogdan Ilchyshyn  changed:

   What|Removed |Added

 CC||bogdan.ilchys...@gmail.com

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

[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input

[Bogdan Bivolaru]

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

--- Comment #21 from Bogdan Bivolaru  ---
(In reply to Bogdan Bivolaru from comment #20)
> (In reply to Buovjaga from comment #19)
> > (In reply to Paul Chaffey from comment #18)

I made a donkey of myself, version fixed is actually 23.04 - sometime in April
there is a new release scheduled. Schedules could change, but that's the plan
at the moment.

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

[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input

[Bogdan Bivolaru]

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

--- Comment #20 from Bogdan Bivolaru  ---
(In reply to Buovjaga from comment #19)
> (In reply to Paul Chaffey from comment #18)
> > Somehow this was closed - sorry everyone I want to reopen this. I have tried
> > this out on
> >  version 5.26.5 and its still not working for me - am I missing something
> > obvious ?
> 
> Yes, you missed that the fix is not yet in any release:
> https://invent.kde.org/network/krfb/-/merge_requests/44
> 
> See also the "Version Fixed In" field.

I think it was merged into the master branch on 2023-02-07 (Feb 2nd). In my
opinion that means it hasn't been included even in the Plasma 5.27.0 release.
For any other release than 6.0.0 or 5.27.x this needs backporting. Even I'm not
sure it will be included in 5.27.x. I'm not sure if the 5.27 branch was cut
from master already or not.

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

[kwin] [Bug 462996] Windows do not stay on the virtual desktop they are on

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

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

[korganizer] [Bug 402417] Accepting invitations strips event notifications

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Ovidiu-Florin BOGDAN  ---
I no longer use KOrganizer for my events, so I can't test this anymore to
confirm this bug. If/when I return to try KOrganizer again, and I run into this
issue again, I'll reopen.

Since there are no votes on it, and nobody is subscribed to it, I assume nobody
else is interested or has encountered this bug, so I'm closing with WORKSFORME.

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

[kamoso] [Bug 463469] New: Effects selector overlaps half of a Video

[Bogdan Mart]

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

Bug ID: 463469
   Summary: Effects selector overlaps half of a Video
Classification: Applications
   Product: kamoso
   Version: 22.12.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: mart.bog...@gmail.com
  Target Milestone: ---

Created attachment 154822
  --> https://bugs.kde.org/attachment.cgi?id=154822&action=edit
Effects menu selected overlaps with video

SUMMARY
When you are selecting effect to apply to video, it overlaps huge portion of a
video. Especialy noticable if all is not in maximized window.

STEPS TO REPRODUCE
1. Open Kamoso
2. Click Effects selector

OBSERVED RESULT
Menu with grid of possible effects appears, but if covers video.

EXPECTED RESULT

Video frame should become smaller to free space for effects selector.

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux
KDE Plasma Version: 5.26.4
Qt Version: 5.15.7
KDE Frameworks Version: 5.15.84-1-MANJARO
ADDITIONAL INFORMATION

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

[kamoso] [Bug 447112] Very low framerate (fps) in kamoso

[Bogdan Mart]

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

--- Comment #4 from Bogdan Mart  ---
I would say to increase importance, as it makes this app unusable on some(?)
systems.

On my experience it was 2 of 2 laptops I have in my possession. And competitors
-- Gnome app works flawlesly.

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

[kamoso] [Bug 447112] Very low framerate (fps) in kamoso

[Bogdan Mart]

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

Bogdan Mart  changed:

   What|Removed |Added

 CC||mart.bog...@gmail.com

--- Comment #3 from Bogdan Mart  ---
Same problem on Manjaro.

Operating System: Manjaro Linux
KDE Plasma Version: 5.26.4
Qt Version: 5.15.7
KDE Frameworks Version: 5.15.84-1-MANJARO

Hardware: Acer Nitro 17 laptop

And I can confirm Patrick's observation, that Cheese works fast. Sad, because
this is app from competitor -- Gnome.


I've also noticed same problem few year ago on my old DELL laptop and Kubuntu.

And Skype/Slack/Zoom didn't produce same slowness effect. (on old system and
new system)
(and OBS as well, as I just checked today)

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

[krita] [Bug 462138] Text Tool Kerning Issue for any font size under 5

[Bogdan Costisor]

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

--- Comment #2 from Bogdan Costisor  ---
Hello. Thank you.

I'm a fellow developer working exactly with text rendering, but with DirectX,
no idea exactly what QT is... 

I tested this on a 4k monitor (200% scalling) and a Full HD one (100%-150%
scalling) and reproduced it so I rulled out any DPI scalling issue.

I also see everyday issues with floating point precision so my initial rough
testing might be off. 

Thank you again and I'll let you know after the 5.2 release if it still
reproducing.

Thank you for making this amazing app :)

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

[plasma-integration] [Bug 462293] KDE theming breaks drop-down menus in some applications

[Bogdan Mart]

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

Bogdan Mart  changed:

   What|Removed |Added

 CC||mart.bog...@gmail.com

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

[krita] [Bug 462138] New: Text Tool Kerning Issue for any font size under 5

[Bogdan Costisor]

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

Bug ID: 462138
   Summary: Text Tool Kerning Issue for any font size under 5
Classification: Applications
   Product: krita
   Version: 5.1.3
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: bogdancosti...@gmail.com
  Target Milestone: ---

Created attachment 153947
  --> https://bugs.kde.org/attachment.cgi?id=153947&action=edit
Example of text that doesn't render properly

SUMMARY
***
Any Text Rendered with font size under 5 is not applying correct letter spacing
/ kerning

***


STEPS TO REPRODUCE
1. Create a Vector layer 
2. Add text with text tool
3. Apply a small font size

OBSERVED RESULT
Some letters have no spacing, or too much spacing

EXPECTED RESULT
Font should be scalable and letter spacing & kerning should be applied
uniformly


SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro, version 21H2


ADDITIONAL INFORMATION
Using latest Krita 5.1.3, however I saw this bug back when the new Text tool
changes were applied.

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

[kdevelop] [Bug 376546] Focus given to view not search field

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[okular] [Bug 458723] PDF document isn't shown - "Please wait ..." message is shown instead

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

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

[kde] [Bug 460234] New: Desktop display crashed

[Bogdan]

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

Bug ID: 460234
   Summary: Desktop display crashed
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.21.1 (22.08.1))

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
Hi,
I awnated to configure the panel and then everything went black and a message
window appeared saying that akinadi_index has crashed.
Very anoying!!! :(

The crash can be reproduced every time.

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

[New LWP 8702]
[New LWP 8703]
[New LWP 8704]
[New LWP 8705]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f583b7a299f in __GI___poll (fds=0x7fff6ce553f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f5836ee6e80 (LWP 8701))]

Thread 5 (Thread 0x7f582f7fe700 (LWP 8705)):
#0  0x7f583b7a299f in __GI___poll (fds=0x7f5824004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f583a07036e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f583a0704a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f583bd90b9b in QEventDispatcherGlib::processEvents
(this=0x7f5824000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f583bd34b3b in QEventLoop::exec (this=this@entry=0x7f582f7fdbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f583bb4e342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f583bb4f543 in QThreadPrivate::start (arg=0x5627fc618160) at
thread/qthread_unix.cpp:330
#7  0x7f583aa62609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f583b7af133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f582700 (LWP 8704)):
#0  0x7f583b7a299f in __GI___poll (fds=0x7f582fffebe0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5837624d66 in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#2  0x7f583bb4f543 in QThreadPrivate::start (arg=0x5627fc5f4680) at
thread/qthread_unix.cpp:330
#3  0x7f583aa62609 in start_thread (arg=) at
pthread_create.c:477
#4  0x7f583b7af133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f5834bfa700 (LWP 8703)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5627fc5fcde0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5627fc5fcd90,
cond=0x5627fc5fcdb8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5627fc5fcdb8, mutex=0x5627fc5fcd90) at
pthread_cond_wait.c:647
#3  0x7f583bb555eb in QWaitConditionPrivate::wait (deadline=...,
this=0x5627fc5fcd90) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x5627fc5e18f8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f5837624d0d in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#6  0x7f583bb4f543 in QThreadPrivate::start (arg=0x5627fc5e18c0) at
thread/qthread_unix.cpp:330
#7  0x7f583aa62609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f583b7af133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f5836931700 (LWP 8702)):
#0  0x7f583a0bd508 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f583a06fd99 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f583a070312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f583a0704a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f583bd90b9b in QEventDispatcherGlib::processEvents
(this=0x7f583b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f583bd34b3b in QEventLoop::exec (this=this@entry=0x7f5836930bb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f583bb4e342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f583bff2f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f583bb4f543 in QThreadPrivate::start (arg=0x7f583c076d80) at
thread/qthread_unix.cpp:330
#9  0x7f583aa62609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f583b7af133 in clone () at
../sysdep

[kde] [Bug 459815] New: Akonadi index crushes and closes kmail

[Bogdan]

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

Bug ID: 459815
   Summary: Akonadi index crushes and closes kmail
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.21.1 (22.08.1))

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
Just started the system and opened kmail. the maximum time that kmail stais
open is 5 minutes. I can't work like that :(
Everytime I open kmail akonadi index crushes the same way.
Plese help me solve that, because I will be forced to use a mail software that
works and I like kmail
.

The crash can be reproduced every time.

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

[New LWP 8629]
[New LWP 8630]
[New LWP 8631]
[New LWP 8632]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fbe8af2899f in __GI___poll (fds=0x7ffc29d1be38, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7fbe8666ce80 (LWP 8628))]

Thread 5 (Thread 0x7fbe7effd700 (LWP 8632)):
#0  0x7fbe8af2899f in __GI___poll (fds=0x7fbe68004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbe897f636e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbe897f64a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbe8b516b9b in QEventDispatcherGlib::processEvents
(this=0x7fbe68000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fbe8b4bab3b in QEventLoop::exec (this=this@entry=0x7fbe7effcbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7fbe8b2d4342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7fbe8b2d5543 in QThreadPrivate::start (arg=0x556bce49dd30) at
thread/qthread_unix.cpp:330
#7  0x7fbe8a1e8609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fbe8af35133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fbe7f7fe700 (LWP 8631)):
#0  0x7fbe8af2899f in __GI___poll (fds=0x7fbe7f7fdbe0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbe86daad66 in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#2  0x7fbe8b2d5543 in QThreadPrivate::start (arg=0x556bce46f680) at
thread/qthread_unix.cpp:330
#3  0x7fbe8a1e8609 in start_thread (arg=) at
pthread_create.c:477
#4  0x7fbe8af35133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fbe7700 (LWP 8630)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x556bce452420) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556bce4523d0,
cond=0x556bce4523f8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x556bce4523f8, mutex=0x556bce4523d0) at
pthread_cond_wait.c:647
#3  0x7fbe8b2db5eb in QWaitConditionPrivate::wait (deadline=...,
this=0x556bce4523d0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x556bce45c8f8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fbe86daad0d in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#6  0x7fbe8b2d5543 in QThreadPrivate::start (arg=0x556bce45c8c0) at
thread/qthread_unix.cpp:330
#7  0x7fbe8a1e8609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fbe8af35133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fbe860b7700 (LWP 8629)):
#0  __GI___libc_read (nbytes=16, buf=0x7fbe860b69a0, fd=4) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=4, buf=0x7fbe860b69a0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fbe8983eb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbe897f5ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbe897f6312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbe897f64a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fbe8b516b9b in QEventDispatcherGlib::processEvents
(this=0x7fbe8b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fbe8b4bab3b in QEventLoop::exec (this=this@entry=0x7fbe860b6bb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7fbe8b2d4342 in QThread::exec (this=) at
../../include/QtCore/.

[kde] [Bug 459691] New: Akonady crashes all the time

[Bogdan]

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

Bug ID: 459691
   Summary: Akonady crashes all the time
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.21.1 (22.08.1))

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
When I login akonady send a crash message. If I want to restart the
application, it crashes. That is very frustrating. Please help me to solve
this. I have undestood that akonady is related to kmail. Thank you.

The crash can be reproduced every time.

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

[New LWP 5503]
[New LWP 5533]
[New LWP 5534]
[New LWP 5552]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb2204bd99f in __GI___poll (fds=0x7fffacd503f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7fb21bc01e80 (LWP 5490))]

Thread 5 (Thread 0x7fb21881d700 (LWP 5552)):
#0  __GI___libc_read (nbytes=16, buf=0x7fb21881c9d0, fd=13) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=13, buf=0x7fb21881c9d0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fb21edd3b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb21ed8aebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb21ed8b312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb21ed8b4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb220aabb9b in QEventDispatcherGlib::processEvents
(this=0x7fb204000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fb220a4fb3b in QEventLoop::exec (this=this@entry=0x7fb21881cbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7fb220869342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7fb22086a543 in QThreadPrivate::start (arg=0x5599c8c87240) at
thread/qthread_unix.cpp:330
#10 0x7fb21f77d609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7fb2204ca133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fb219114700 (LWP 5534)):
#0  __GI___pthread_mutex_lock (mutex=) at
../nptl/pthread_mutex_lock.c:164
#1  0x7fb21c2b644c in wl_display_cancel_read () from
/lib/x86_64-linux-gnu/libwayland-client.so.0
#2  0x7fb21c33fe55 in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#3  0x7fb22086a543 in QThreadPrivate::start (arg=0x5599c8c54680) at
thread/qthread_unix.cpp:330
#4  0x7fb21f77d609 in start_thread (arg=) at
pthread_create.c:477
#5  0x7fb2204ca133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fb219915700 (LWP 5533)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5599c8c5cde4) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5599c8c5cd90,
cond=0x5599c8c5cdb8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5599c8c5cdb8, mutex=0x5599c8c5cd90) at
pthread_cond_wait.c:647
#3  0x7fb2208705eb in QWaitConditionPrivate::wait (deadline=...,
this=0x5599c8c5cd90) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x5599c8c418f8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fb21c33fd0d in ?? () from
/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#6  0x7fb22086a543 in QThreadPrivate::start (arg=0x5599c8c418c0) at
thread/qthread_unix.cpp:330
#7  0x7fb21f77d609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb2204ca133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fb21b64c700 (LWP 5503)):
#0  __GI___libc_read (nbytes=16, buf=0x7fb21b64b9a0, fd=4) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=4, buf=0x7fb21b64b9a0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fb21edd3b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb21ed8aebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb21ed8b312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb21ed8b4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb220aabb9b in QEventDispatcherGlib::processEvents
(this=0x7fb214000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x

[systemsettings] [Bug 459599] New: System settings crash

[Bogdan]

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

Bug ID: 459599
   Summary: System settings crash
Classification: Applications
   Product: systemsettings
   Version: 5.25.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.25.5)

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

-- Information about the crash:
I just open the system and wanted to open system settings. I could not. Ițve
tried several times with the same result

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Aborted

[New LWP 10696]
[New LWP 10703]
[New LWP 10708]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f852fe1499f in __GI___poll (fds=0x7ffd69be50f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f852b4f1ec0 (LWP 10693))]

Thread 4 (Thread 0x7f84fdf61700 (LWP 10708)):
#0  __GI___libc_read (nbytes=16, buf=0x7f84fdf609b0, fd=23) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=23, buf=0x7f84fdf609b0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f852e913b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f852e8caebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f852e8cb312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f852e8cb4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f85303e7b9b in QEventDispatcherGlib::processEvents
(this=0x7f84f8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f853038bb3b in QEventLoop::exec (this=this@entry=0x7f84fdf60bc0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7f85301a5342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7f852e14f919 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f85301a6543 in QThreadPrivate::start (arg=0x564fdffc8d00) at
thread/qthread_unix.cpp:330
#11 0x7f852f288609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7f852fe21133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f8522333700 (LWP 10703)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x564fdf665098) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564fdf665048,
cond=0x564fdf665070) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x564fdf665070, mutex=0x564fdf665048) at
pthread_cond_wait.c:647
#3  0x7f852263a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f852263a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f852f288609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f852fe21133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f852a6b0700 (LWP 10696)):
#0  0x7f852fe1499f in __GI___poll (fds=0x7f85240053c0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f852e8cb36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f852e8cb4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f85303e7b9b in QEventDispatcherGlib::processEvents
(this=0x7f8524000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f853038bb3b in QEventLoop::exec (this=this@entry=0x7f852a6afbb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f85301a5342 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f852f4f0f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f85301a6543 in QThreadPrivate::start (arg=0x7f852f574d80) at
thread/qthread_unix.cpp:330
#8  0x7f852f288609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f852fe21133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f852b4f1ec0 (LWP 10693)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7f852fd24859 in __GI_abort () at abort.c:79
#6  0x7f853016abd9 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7ffd69be6180,
msg=msg@entry=0x7f853055e448 "Cannot mix incompatible Qt library (%d.%d.%d)
with this library (%d.%d.%d)") at global/qlogging.cpp:893
#8  0x7f853017fd71 in QObjectPrivate::checkForIncompatibleLib

[kde] [Bug 457678] New: Akonadi indenxing agent craches all the time

[Bogdan]

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

Bug ID: 457678
   Summary: Akonadi indenxing agent craches all the time
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.20.3 (22.04.3))

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.25
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
I just opened the computer and performed an update form the terminal

The crash can be reproduced every time.

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

[New LWP 7389]
[New LWP 7390]
[New LWP 7391]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f2e91fec99f in __GI___poll (fds=0x7fff5892ac78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f2e8d7369c0 (LWP 7388))]

Thread 4 (Thread 0x7f2e864dd700 (LWP 7391)):
#0  __GI___libc_read (nbytes=16, buf=0x7f2e864dc9d0, fd=8) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=8, buf=0x7f2e864dc9d0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f2e90907b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2e908beebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2e908bf312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2e908bf4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f2e925da5bb in QEventDispatcherGlib::processEvents
(this=0x7f2e78000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f2e9257e76b in QEventLoop::exec (this=this@entry=0x7f2e864dcbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7f2e92398372 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7f2e92399553 in QThreadPrivate::start (arg=0x56218aa0be00) at
thread/qthread_unix.cpp:331
#10 0x7f2e912a0609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7f2e91ff9133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f2e86cde700 (LWP 7390)):
#0  0x7f2e91fec99f in __GI___poll (fds=0x7f2e80004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f2e908bf36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2e908bf4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2e925da5bb in QEventDispatcherGlib::processEvents
(this=0x7f2e8b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f2e9257e76b in QEventLoop::exec (this=this@entry=0x7f2e86cddbb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f2e92398372 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f2e9283cf4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f2e92399553 in QThreadPrivate::start (arg=0x7f2e928c0d80) at
thread/qthread_unix.cpp:331
#8  0x7f2e912a0609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f2e91ff9133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f2e8c8fb700 (LWP 7389)):
#0  0x7f2e91fec99f in __GI___poll (fds=0x7f2e8c8faae8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f2e8df83c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f2e8df8590a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f2e8d0453c8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f2e92399553 in QThreadPrivate::start (arg=0x56218a911700) at
thread/qthread_unix.cpp:331
#5  0x7f2e912a0609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f2e91ff9133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f2e8d7369c0 (LWP 7388)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7f2e91efc859 in __GI_abort () at abort.c:79
#6  0x7f2e92187911 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7f2e9219338c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x7f2e921933f7 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7f2e921936a9 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7f2e93ab5478 in GlassTable::set_overwritten
(this=this@entry=0x56218ac19820) at /usr/include/c++/9/ext/new_allocator.h:89
#11 0x7f2e93ab56de in GlassTable::block_to_cu

[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input

[Bogdan Bivolaru]

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

--- Comment #11 from Bogdan Bivolaru  ---
Here https://wayland.app/protocols/virtual-keyboard-unstable-v1 is a more
authoritative source on the Wayland virtual keyboard protocol (there is a
similar one for pointers, I do not know about virtual touch). 
I also find such a protocol useful for software testing.

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

[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input

[Bogdan Bivolaru]

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

--- Comment #10 from Bogdan Bivolaru  ---
(In reply to Bogdan Bivolaru from comment #9)
> (In reply to Josh from comment #8)
> > Issue is only when connecting to a wayland session, not from. Sorely
> > affected by this as well and have been for some time. Is there a wl-roots
> > standard that would assist us in resolving this problem?
> 
> I _guess_ this is relevant here:
> Wayvnc is a VNC server for WL-roots based compositor
> https://github.com/any1/wayvnc/tree/master/protocols:
> at minimum I guess we would need virtual-keyboard-unstable-v1.xml and
> wlr-virtual-pointer-unstable-v1.xml
> 
> Gnome VNC source code confuses me a lot, I do not understand if this feature
> is implemented or not:
> https://gitlab.gnome.org/
> search?search=keyboard&group_id=&project_id=12409&scope=&search_code=true&sni
> ppets=false&repository_ref=master&nav_source=navbar
> 
> I would have hoped that all the remote desktop streams would be handled via
> pipewire eventually. My logic is that all stream types need buffering and to
> be routed from a producer node to a consumer. Since some are more latency
> dependent than others it would be great if there was a panel where mixing
> and matching streams could be made... say like WirePlumber session manager.
> I don't see why video, audio streams need to be managed separately from
> keyboard, mouse, clipboard, other data event streams.

UPDATE: comment from the  Elsie Hupp, author of
(any1)[https://github.com/any1/wayvnc/discussions/93#discussioncomment-741946]
I wouldn't be opposed to a PR implementing Gnome support, but I'd much rather
that the Gnome people implement proper wayland protocols for screen capturing
instead of putting everything on dbus

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

[kde] [Bug 453457] New: akonadi_indexing service crashed

[Bogdan]

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

Bug ID: 453457
   Summary: akonadi_indexing service crashed
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.20.0 (22.04.0))

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
I just booted the system and it crashed without opening any application.

The crash can be reproduced every time.

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

[New LWP 2378]
[New LWP 2382]
[New LWP 2383]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ff5237359cf in __GI___poll (fds=0x7ffeba3f1238, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7ff51ee989c0 (LWP 2335))]

Thread 4 (Thread 0x7ff5177fe700 (LWP 2383)):
#0  0x7ff5237359cf in __GI___poll (fds=0x7ff508004a60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff52201936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff5220194a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff523d2365b in QEventDispatcherGlib::processEvents
(this=0x7ff508000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff523cc787b in QEventLoop::exec (this=this@entry=0x7ff5177fdbe0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7ff523ae1442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7ff523ae2623 in QThreadPrivate::start (arg=0x55904528f110) at
thread/qthread_unix.cpp:331
#7  0x7ff5229fb609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7ff523742163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7ff517fff700 (LWP 2382)):
#0  0x7ff5237359cf in __GI___poll (fds=0x7ff510004e60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff52201936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff5220194a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff523d2365b in QEventDispatcherGlib::processEvents
(this=0x7ff51b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff523cc787b in QEventLoop::exec (this=this@entry=0x7ff517ffebb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7ff523ae1442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7ff523f84f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7ff523ae2623 in QThreadPrivate::start (arg=0x7ff524008d80) at
thread/qthread_unix.cpp:331
#8  0x7ff5229fb609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7ff523742163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7ff51e05f700 (LWP 2378)):
#0  0x7ff5237359cf in __GI___poll (fds=0x7ff51e05eae8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff51f6e3c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ff51f6e590a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ff51e7a91a8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7ff523ae2623 in QThreadPrivate::start (arg=0x559045192700) at
thread/qthread_unix.cpp:331
#5  0x7ff5229fb609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7ff523742163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7ff51ee989c0 (LWP 2335)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7ff523645859 in __GI_abort () at abort.c:79
#6  0x7ff5238d0911 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7ff5238dc38c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x7ff5238dc3f7 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7ff5238dc6a9 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7ff5251e7478 in GlassTable::set_overwritten
(this=this@entry=0x559045d46620) at /usr/include/c++/9/ext/new_allocator.h:89
#11 0x7ff5251e76de in GlassTable::block_to_cursor (this=0x559045d46620,
C_=0x559045d466e8, j=, n=10874) at
../backends/glass/glass_table.cc:335
#12 0x7ff5252a481d in GlassTable::find (this=this@entry=0x559045d46620,
C_=C_@entry=0x559045d466e8) at ../common/wordaccess.h:57
#13 0x7ff5252a6be3 in

[kmail2] [Bug 453376] New: KMail crash

[Bogdan]

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

Bug ID: 453376
   Summary: KMail crash
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: kmail (5.20.0 (22.04.0))

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Just checking mail and reading messages. When I have deleted a messahe, KMail
closed.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted

[New LWP 3975]
[New LWP 3976]
[New LWP 3977]
[New LWP 3978]
[New LWP 3979]
[New LWP 3980]
[New LWP 3981]
[New LWP 4031]
[New LWP 4033]
[New LWP 4039]
[New LWP 4040]
[New LWP 4041]
[New LWP 4042]
[New LWP 4045]
[New LWP 4046]
[New LWP 4047]
[New LWP 4053]
[New LWP 4068]
[New LWP 4083]
[New LWP 4090]
[New LWP 4176]
[New LWP 4318]
[New LWP 4319]
[New LWP 4320]
[New LWP 4321]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fcea570f9cf in __GI___poll (fds=0x7ffddbc0c778, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7fce965f9200 (LWP 3973))]

Thread 26 (Thread 0x7fcdf39ff700 (LWP 4321)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fcdf39fe310, clockid=, expected=0,
futex_word=0x5557cb7503f4) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fcdf39fe310, clockid=, mutex=0x5557cb7503a0, cond=0x5557cb7503c8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x5557cb7503c8, mutex=0x5557cb7503a0,
abstime=0x7fcdf39fe310) at pthread_cond_wait.c:656
#3  0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative
(this=0x5557cb7503a0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7503a0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x5557cb74b580,
mutex=mutex@entry=0x5557cb7aec98, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7fcea5abfb21 in QThreadPoolThread::run (this=0x5557cb74b570) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:275
#7  0x7fcea5abc623 in QThreadPrivate::start (arg=0x5557cb74b570) at
thread/qthread_unix.cpp:331
#8  0x7fcea2483609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7fcea571c163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7fce12ffd700 (LWP 4320)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fce12ffc310, clockid=, expected=0,
futex_word=0x5557cb7f8ea4) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fce12ffc310, clockid=, mutex=0x5557cb7f8e50, cond=0x5557cb7f8e78) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x5557cb7f8e78, mutex=0x5557cb7f8e50,
abstime=0x7fce12ffc310) at pthread_cond_wait.c:656
#3  0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative
(this=0x5557cb7f8e50, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7f8e50) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x5557cb8e2b20,
mutex=mutex@entry=0x5557cb7aec98, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7fcea5abfb21 in QThreadPoolThread::run (this=0x5557cb8e2b10) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:275
#7  0x7fcea5abc623 in QThreadPrivate::start (arg=0x5557cb8e2b10) at
thread/qthread_unix.cpp:331
#8  0x7fcea2483609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7fcea571c163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7fce11ffb700 (LWP 4319)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fce11ffa310, clockid=, expected=0,
futex_word=0x5557cb7f9114) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fce11ffa310, clockid=, mutex=0x5557cb7f90c0, cond=0x5557cb7f90e8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x5557cb7f90e8, mutex=0x5557cb7f90c0,
abstime=0x7fce11ffa310) at pthread_cond_wait.c:656
#3  0x7fcea5ac2618 in QWaitConditionPrivate::wait_relative
(this=0x5557cb7f90c0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x5557cb7f90c0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x5557cb7a3cc0,
mutex=mutex@entry=0x5557cb7aec98, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7fcea5abfb21 in QThrea

[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input

[Bogdan Bivolaru]

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

Bogdan Bivolaru  changed:

   What|Removed |Added

 CC||bogdan.bivol...@gmail.com

--- Comment #9 from Bogdan Bivolaru  ---
(In reply to Josh from comment #8)
> Issue is only when connecting to a wayland session, not from. Sorely
> affected by this as well and have been for some time. Is there a wl-roots
> standard that would assist us in resolving this problem?

I _guess_ this is relevant here:
Wayvnc is a VNC server for WL-roots based compositor
https://github.com/any1/wayvnc/tree/master/protocols:
at minimum I guess we would need virtual-keyboard-unstable-v1.xml and
wlr-virtual-pointer-unstable-v1.xml

Gnome VNC source code confuses me a lot, I do not understand if this feature is
implemented or not:
https://gitlab.gnome.org/search?search=keyboard&group_id=&project_id=12409&scope=&search_code=true&snippets=false&repository_ref=master&nav_source=navbar

I would have hoped that all the remote desktop streams would be handled via
pipewire eventually. My logic is that all stream types need buffering and to be
routed from a producer node to a consumer. Since some are more latency
dependent than others it would be great if there was a panel where mixing and
matching streams could be made... say like WirePlumber session manager. I don't
see why video, audio streams need to be managed separately from keyboard,
mouse, clipboard, other data event streams.

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

[kde] [Bug 452259] New: Kmail and akonadi are keep crashing at 3 min interval

[Bogdan]

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

Bug ID: 452259
   Summary: Kmail and akonadi are keep crashing at 3 min interval
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sima...@gmail.com
  Target Milestone: ---

Application: akonadi_indexing_agent (5.19.3 (21.12.3))

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.13.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I wanted to open KMail and the system reported taht akonadi indexing agent has
crashed. After I have restarted the application it continues the cicle of crash
and restart


- Unusual behavior I noticed:
Kmail and akonadi are keep crashing at 3 min interval

- Custom settings of the application: 
none

The reporter is unsure if this crash is reproducible.

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

[New LWP 10175]
[New LWP 10176]
[New LWP 10177]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fc0da5159cf in __GI___poll (fds=0x7ffca04121f8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7fc0d5c809c0 (LWP 10174))]

Thread 4 (Thread 0x7fc0ce994700 (LWP 10177)):
#0  0x7fc0da5159cf in __GI___poll (fds=0x7fc0c0004a60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc0d8e0436e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc0d8e044a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc0dab0365b in QEventDispatcherGlib::processEvents
(this=0x7fc0cb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc0daaa787b in QEventLoop::exec (this=this@entry=0x7fc0ce993be0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7fc0da8c1442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7fc0da8c2623 in QThreadPrivate::start (arg=0x5636b719dcb0) at
thread/qthread_unix.cpp:331
#7  0x7fc0d97e6609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fc0da522163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fc0cf195700 (LWP 10176)):
#0  __GI___libc_read (nbytes=16, buf=0x7fc0cf1949a0, fd=6) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=6, buf=0x7fc0cf1949a0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fc0d8e4cb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc0d8e03ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc0d8e04312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc0d8e044a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fc0dab0365b in QEventDispatcherGlib::processEvents
(this=0x7fc0c8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fc0daaa787b in QEventLoop::exec (this=this@entry=0x7fc0cf194bb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#8  0x7fc0da8c1442 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9  0x7fc0dad64f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7fc0da8c2623 in QThreadPrivate::start (arg=0x7fc0dade8d80) at
thread/qthread_unix.cpp:331
#11 0x7fc0d97e6609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7fc0da522163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fc0d4e48700 (LWP 10175)):
#0  0x7fc0da5159cf in __GI___poll (fds=0x7fc0d4e47ae8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc0d64cbc1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fc0d64cd90a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fc0d55921a8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fc0da8c2623 in QThreadPrivate::start (arg=0x5636b70a3700) at
thread/qthread_unix.cpp:331
#5  0x7fc0d97e6609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7fc0da522163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fc0d5c809c0 (LWP 10174)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7fc0da425859 in __GI_abort () at abort.c:79
#6  0x7fc0da6b0911 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7fc0da6bc38c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x7fc0da6bc3f7 in std::terminat

[kaddressbook] [Bug 451621] New: No synchronization between Google contacts and Contacts, Google address book not added

[Bogdan]

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

Bug ID: 451621
   Summary: No synchronization between Google contacts and
Contacts, Google address book not added
   Product: kaddressbook
   Version: 5.19.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sima...@gmail.com
CC: to...@kde.org
  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. Open Kontact
2. Open ”Contacts” from the tool bar
3. Add a new address book and choose ”Google groupware - Google calendar,
contacts and task from KDE”
4. Give the required permissions to the Google account for Akonadi services

OBSERVED RESULT
Nothing happened

EXPECTED RESULT
To see Google contacts address book synchronized with Contacts in Kontact
application

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Neon 5.24
(available in About System)
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.3
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #8 from Bogdan  ---
Problem is that Dolphin opens file as directory.
Directory path in path widget is [/home/miki/UserDirs/Music/Goran Vejvoda -
Beautiful Dayus.mp3/].
But this path does not exists really.

Expected Results:
- Dolphin must open the file catalog where the file is stored, and then set the
cursor to the specified file in the file list.
- If Dolphin has received a list of many files, then it must choose all these
files in the file list widget.
- If files from the list received are stored in different directories, then
Dolphin must open new tab for each of touched directories and select all the
received files in those directories.

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #7 from Bogdan  ---
Created attachment 144529
  --> https://bugs.kde.org/attachment.cgi?id=144529&action=edit
log open file from cli

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #6 from Bogdan  ---
Steps:
1) Create new playlist in Strawberry.
2) Close all Dolphin windows.
3) Close all Strawberry windows.
4) Start command in terminal:
dolphin "/home/miki/UserDirs/Music/Goran Vejvoda - Beautiful Dayus.mp3"
2>&1 | tee > /tmp/dolphin.log
5) Dolphin opens window with path:
[/home/miki/UserDirs/Music/Goran Vejvoda - Beautiful Dayus.mp3/]
6) Dolphin starts Strawberry (whic configured as default program for *.mp3
files);
7) Strawberry has 2 identical items in playlist.
8) Strawberry must start play opened file, but it did not play.

Dolphin log attached below.

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #5 from Bogdan  ---
Dolphin 21.08.3
Dolphin correctly opens file from Strawberry.

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

[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot

[Ovidiu-Florin BOGDAN]

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

--- Comment #8 from Ovidiu-Florin BOGDAN  ---
* deleted the /var/lib/PackageKit/offline-update-action file as instructed
* rebooted
* installed all updates via Discover -> got asked for reboot
* rebooted
* Discover reported updates -> the same updates that previously "we're
installed"
* Installed the updates -> got asked for reboot
* checked for updates with `dnf upgrade` -> all the updates "installed" by
Discover were not installed.

The `/var/lib/PackageKit/offline-update-action` is back containing `reboot`
again.

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

[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot

[Ovidiu-Florin BOGDAN]

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

--- Comment #7 from Ovidiu-Florin BOGDAN  ---
Thank you. It's back to normal now.

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

[Discover] [Bug 445652] Plasma keeps asking for reboot since upgrading to Fedora 34

[Ovidiu-Florin BOGDAN]

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

--- Comment #5 from Ovidiu-Florin BOGDAN  ---
Is there anything I can do to resolve this?

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

[Discover] [Bug 445652] Plasma keeps asking for reboot since upgrading to Fedora 34

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

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

--- Comment #3 from Ovidiu-Florin BOGDAN  ---
$ cat /var/lib/PackageKit/offline-update-competed
cat: /var/lib/PackageKit/offline-update-competed: No such file or directory

$ ls /var/lib/PackageKit/ 
offline-update-action  transactions.db

$ cat /var/lib/PackageKit/offline-update-action 
reboot

It seems that file does not exist. But I do have this file with these contents.

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

[plasmashell] [Bug 445652] New: Plasma keeps asking for reboot since upgrading to Fedora 34

[Ovidiu-Florin BOGDAN]

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

Bug ID: 445652
   Summary: Plasma keeps asking for reboot since upgrading to
Fedora 34
   Product: plasmashell
   Version: 5.22.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: ovidiu@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
I'm been using the plasma applet to get notified of updates and install them
since this thing existed.
A few months ago I've upgraded my system to Fedora 34. Since then this applet
keeps asking me for a reboot. No matter how much I reboot the system, this is
the first notification I get when the system turns on.

OBSERVED RESULT
Reboot/Restart request is always active.

EXPECTED RESULT
Just like before, only ask for a restart after installing updates that require
a restart. Otherwise only show a notification and the updates icon when there
are updates available.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 34 KDE
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

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

[kwin] [Bug 443410] Please restore the Desktop Cube switching effect

[Bogdan]

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

--- Comment #4 from Bogdan  ---
Hello,

Came by just in support for those that already mentioned, either here or in
other community platforms, that removing Desktop Cube doesn't quite seem
justified, and in fact will be like cutting the pinky of a pianist. Might sound
harsh, but all the features of KDE Plasma made me and others recommend it and
use it for the versatility and the choices to improve workflow.

Please kindly reconsider your decision.

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

[kde] [Bug 441336] [KDE Neon] When changing the Regular font from Noto sans arabic to Noto sans, the outline of the font names disappears

[Bogdan]

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

--- Comment #4 from Bogdan  ---
Created attachment 141555
  --> https://bugs.kde.org/attachment.cgi?id=141555&action=edit
The outline around the font names disappears

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

[kde] [Bug 441336] [KDE Neon] When changing the Regular font from Noto sans arabic to Noto sans, the outline of the font names disappears

[Bogdan]

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

--- Comment #3 from Bogdan  ---
Created attachment 141554
  --> https://bugs.kde.org/attachment.cgi?id=141554&action=edit
In the screenshot, the "appearance"section

Dear programmers, I am sending you screenshots of the problem. The first
screenshot shows the appearance tab. The problem is located in its fonts
section. In the second screenshot, I highlighted the problem itself with a red
rectangle. The outline around the font names disappears. Which is a visual
error

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

[plasmashell] [Bug 441338] [KDE Neon] When you right-click on a text file, the system crashes

[Bogdan]

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

--- Comment #11 from Bogdan  ---
After turning off the ballo, the same thing happens.

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

[plasmashell] [Bug 441338] [KDE Neon] When you right-click on a text file, the system crashes

[Bogdan]

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

--- Comment #10 from Bogdan  ---
PLAYBACK ACTIONS
1. Create a text file named abc on the desktop

2. Right-click this text file.

3. Scroll down the menu items with the mouse.
After disabling the baloo, the same bug occurs.
THE OBSERVED RESULT: the system crashes to a black screen, blocking further use
of KDE Neon.

Expected result: a menu for selecting actions for a text file will appear.

Environment:
KDE Plasma Version: 5.22.3
2. KDE Frameworks Version: 5.85.0
3. Qt Version: 5.15.3

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

[plasmashell] [Bug 441338] [KDE Neon] When you right-click on a text file, the system crashes

[Bogdan]

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

--- Comment #6 from Bogdan  ---
Created attachment 141034
  --> https://bugs.kde.org/attachment.cgi?id=141034&action=edit
The system crashes into a black screen when creating a text file in English

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

[plasmashell] [Bug 441338] [KDE Neon] When you right-click on a text file, the system crashes

[Bogdan]

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

--- Comment #5 from Bogdan  ---
When creating a new file in English new.txt, the error is repeated. Added a
video of a bug with an English name

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

[kde] [Bug 441342] When you click on a text file, it crashes.

[Bogdan]

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

--- Comment #1 from Bogdan  ---
Created attachment 140931
  --> https://bugs.kde.org/attachment.cgi?id=140931&action=edit
When you click on a text file, it crashes.

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

[kde] [Bug 441342] New: When you click on a text file, it crashes.

[Bogdan]

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

Bug ID: 441342
   Summary: When you click on a text file, it crashes.
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

Created attachment 140930
  --> https://bugs.kde.org/attachment.cgi?id=140930&action=edit
When you click on a text file, it crashes.

SUMMARY: When you click on a text file, it crashes.


STEPS TO REPRODUCE
1. Open the File Manager on the toolbar.

2. Go to the documents folder.

3. Create a text file with any name.

4. Right-click on this text file.

OBSERVED RESULT: the program crashes and the file manager closes spontaneously.


EXPECTED RESULT: a menu will appear with the option to select options for the
file. 


SOFTWARE/OS VERSIONS
1.KDE Plasma Version: 5.22.3
2.KDE Frameworks Version:5.85.0 
3.Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kde] [Bug 441341] New: [KDE Neon] When you right-click on an html file, the system crashes

[Bogdan]

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

Bug ID: 441341
   Summary: [KDE Neon] When you right-click on an html file, the
system crashes
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

Created attachment 140929
  --> https://bugs.kde.org/attachment.cgi?id=140929&action=edit
When you right-click on an html file, the system crashes

SUMMARY: When you right-click on an html file, the system crashes.


STEPS TO REPRODUCE
1. Create an html file with any name on the desktop.
2. Right-click on this file.
3. Scroll through the menu items that appear.

OBSERVED RESULT: The system crashes into a black screen.


EXPECTED RESULT: A menu for selecting actions for the text file will appear.


1.KDE Plasma Version: 5.22.3
2.KDE Frameworks Version:5.85.0 
3.Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kde] [Bug 441338] New: [KDE Neon] When you right-click on a text file, the system crashes

[Bogdan]

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

Bug ID: 441338
   Summary: [KDE Neon] When you right-click on a text file, the
system crashes
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

Created attachment 140928
  --> https://bugs.kde.org/attachment.cgi?id=140928&action=edit
When you right-click on a text file, the system crashes

SUMMARY: When you right-click on a text file, the system crashes


STEPS TO REPRODUCE
1. Create a text file with any name on the desktop.

2. Right-click on this text file.

3. Scroll through the menu items with the mouse down.

OBSERVED RESULT: The system crashes into a black screen, blocking further use
of KDE Neon.

Expected result: A menu for selecting actions for the text file will appear.

Environment:
1.KDE Plasma Version: 5.22.3
2.KDE Frameworks Version:5.85.0 
3.Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kde] [Bug 441336] New: [KDE Neon] When changing the Regular font from Noto sans arabic to Noto sans, the outline of the font names disappears

[Bogdan]

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

Bug ID: 441336
   Summary: [KDE Neon] When changing the Regular font from Noto
sans arabic to Noto sans, the outline of the font
names disappears
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

SUMMARY: [KDE Neon] When changing the Regular font from Noto sans arabic to
Noto sans, the outline of the font names disappears

STEPS TO REPRODUCE
1. Open the system settings and go to the appearance section.
2. Click the appearance button.
3. Change the regular font from Noto sans to Noto sans arabic
4. Close the System Settings window.
5. Open the System Settings window.
6. Select the external section.
7. Change the normal font from Noto sans arabic to Noto sans.Expected result:
The font names will be located in the icons with an outline.Actual result: the
stroke around the font names disappears.

OBSERVED RESULT: the outline around the font names disappears.


EXPECTED RESULT: the font names will be located in the icons with an outline.


1.KDE Plasma Version: 5.22.3
2.KDE Frameworks Version:5.85.0 
3.Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kde] [Bug 441323] When changing the font to Noto nastaliq Udru, the OK and Cancel buttons pop out of the screen

[Bogdan]

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

--- Comment #1 from Bogdan  ---
Created attachment 140926
  --> https://bugs.kde.org/attachment.cgi?id=140926&action=edit
When changing the font to Noto nastaliq Udru, the OK and Cancel buttons pop out
of the screen

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

[kde] [Bug 441334] [KDE Neon] When changing the font, the names of localization options are not displayed correctly.

[Bogdan]

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

--- Comment #1 from Bogdan  ---
Created attachment 140925
  --> https://bugs.kde.org/attachment.cgi?id=140925&action=edit
When changing the font, the names of localization options are not displayed
correctly.

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

[kde] [Bug 441334] New: [KDE Neon] When changing the font, the names of localization options are not displayed correctly.

[Bogdan]

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

Bug ID: 441334
   Summary: [KDE Neon] When changing the font, the names of
localization options are not displayed correctly.
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

Created attachment 140924
  --> https://bugs.kde.org/attachment.cgi?id=140924&action=edit
When changing the font, the names of localization options are not displayed
correctly.

SUMMARY:
When changing the font, the names of localization options are not displayed
correctly.

STEPS TO REPRODUCE
1. Select the system parameters and go to the appearance section.
2. Select the fonts option.
3. Change the plain text to Noto Nastaliq Urdu and click Apply.
4. Click back and go to the localization section.

OBSERVED RESULT: in the localization menu options, half of the text disappears.


EXPECTED RESULT: the options will open correctly in the localization menu.


1.KDE Plasma Version: 5.22.3
2.KDE Frameworks Version:5.85.0 
3.Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[kde] [Bug 441323] New: When changing the font to Noto nastaliq Udru, the OK and Cancel buttons pop out of the screen

[Bogdan]

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

Bug ID: 441323
   Summary: When changing the font to Noto nastaliq Udru, the OK
and Cancel buttons pop out of the screen
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tipoks...@mail.ru
  Target Milestone: ---

Created attachment 140922
  --> https://bugs.kde.org/attachment.cgi?id=140922&action=edit
the Ok and cancel buttons pop out of the screen

SUMMARY
When changing the font to Noto nastaliq Udru, the OK and Cancel buttons pop out
of the screen

STEPS TO REPRODUCE
1. Open the system parameters in the KDE Neon 5.22.3.
2. Click the appearance button and go to the fonts section.
3. Change the normal font from Noto sans to Noto nastaliq Udru, click apply.
4. Select change plain text again.


EXPECTED RESULT: A window opens with a selection of the OK and Cancel buttons.

Actual result: The Ok and Cancel buttons pop out of the screen and become
unusable.

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

ADDITIONAL INFORMATION

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #3 from Bogdan  ---
I think, that Dolphin has 2 bugs:
1) low support of files path in URI form;
2) don't checks existing of received file/folder path, before opening directory
listing.

Nemo correctly opens file path, sended from Strawberry.
If Strawberry use the same algoritm with Dolphin and Nemo, then Nemo check
existing of file path and, if received path is file - opens folder and select
file inside it. And thats all - expected behavior even without dbus supporting.

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

--- Comment #1 from Bogdan  ---
To reproduce error, Dolphin must be configured as default File Explorer
program.

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

[dolphin] [Bug 439007] Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

Bogdan  changed:

   What|Removed |Added

   Platform|Other   |Gentoo Packages

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

[dolphin] [Bug 439007] New: Dolphin crashes when open fully qualified file path from external program (Strawberry)

[Bogdan]

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

Bug ID: 439007
   Summary: Dolphin crashes when open fully qualified file path
from external program (Strawberry)
   Product: dolphin
   Version: 20.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bogdan.pylypenko...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Dolphin has incorrect behaviour when external program call Dolphin to open
fully qualified file path (not a directory path).


STEPS TO REPRODUCE (from Strawberry):
1. Open Strawberry (https://www.strawberrymusicplayer.org/);
2. Select any audio file in playlist;
3. Select "Open file in File Manager" from right-click menu of audio file.
4. Dolphin crashed and "Dolphin crashed" message shown in system tray.

STEPS TO REPRODUCE (from CLI):
1. Run command "dolphin ~/Music/test.mp3" ;
2. "Dolphin crashed" message shown in system tray;
3. Dolphin started and open clean tab with name "test.mp3/";
4. System media player (VLC) play ~/Music/test.mp3 file (may be media player
called from dolphin by xdg-open system).

OBSERVED RESULT
Dolphin opens clean tab with name "test.mp3/".

EXPECTED RESULT
Dolphin must:
1) opens tab with name of directory name, where "test.mp3" file placed;
2) show content of directory, where "test.mp3" file placed;
3) select "test.mp3" file in directory listing.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo 2.7
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Nemo 4.8.4-r1 correctly opens fully qualified file paths.

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

[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

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

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

[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update

[Ovidiu-Florin BOGDAN]

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

--- Comment #10 from Ovidiu-Florin BOGDAN  ---
Considering that now there is a message when the updating fails, the initial
scope of this ticket has been fixed. But the fact that after the failure we are
not taken back to the "Choose what updates to install" view and we are still
stuck in the "Installing updates" view, I consider this partially fixed.

Please let me know if you think otherwise.

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

[konsole] [Bug 403324] Cannot drag tab from one window into another

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com

--- Comment #8 from Ovidiu-Florin BOGDAN  ---
*** Bug 396891 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 396891] Regression: Cannot drop tab into existing window

[Ovidiu-Florin BOGDAN]

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

--- Comment #3 from Ovidiu-Florin BOGDAN  ---


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

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

[konsole] [Bug 403324] Cannot drag tab from one window into another

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

--- Comment #7 from Ovidiu-Florin BOGDAN  ---
As of Konsole 20.12.2 if you have "Run all Konsole windows in a single process"
enabled, the tab dragging  from one window to another works just fine.

However, if you start Konsole from the terminal by just using the "konsole"
command with no arguments, that window cannot share tabs with any other window.

Starting Konsole from the Kickstart or Krunner opens a window with shareable
tabs. Even if from KRunner we start the "konsole" command and not the Konsole
app, tabs are still shareable.

My system:
Linux/KDE Plasma: Fedora 33 KDE
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

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

[konsole] [Bug 395294] no intuitive/obvious way to return detached tab to window with other tabs

[Ovidiu-Florin BOGDAN]

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

--- Comment #7 from Ovidiu-Florin BOGDAN  ---
This is a possible duplicate of Bug 403324.

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

[konsole] [Bug 395294] no intuitive/obvious way to return detached tab to window with other tabs

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
Under the Konsole settings you can set the tab bar to be shown always. This way
you always see the tab bar on any Konsole window and will always be available
to drag the tab into another window.

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

[konsole] [Bug 403324] Cannot drag tab from one window into another

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||erben...@comcast.net

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
*** Bug 389897 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 389897] Tabs can not be moved to other Konsole window's which have different process ids

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE
 CC||ovidiu@gmail.com

--- Comment #7 from Ovidiu-Florin BOGDAN  ---


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

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

[konsole] [Bug 389897] Tabs can not be moved to other Konsole window's which have different process ids

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
*** Bug 396891 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 396891] Regression: Cannot drop tab into existing window

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Ovidiu-Florin BOGDAN  ---


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

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

[plasmashell] [Bug 435681] Changing themes from Light to Dark leaves white text on white background

[Ovidiu-Florin BOGDAN]

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

--- Comment #3 from Ovidiu-Florin BOGDAN  ---
Thank you for the heads-up Nate. How can get this information ahead of time so
I don't waste our time reporting fixed bugs?

I am subscribed to the weekly blog post, but I think I missed this, if it was
in there.

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

[konsole] [Bug 407180] Feature Request: allow vertical tabbar (on left/right side).

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com
 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Ovidiu-Florin BOGDAN  ---


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

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

[konsole] [Bug 339783] Wishlist: Tab bar on the left/right side of UI

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||gonzalo.ar...@gmail.com

--- Comment #2 from Ovidiu-Florin BOGDAN  ---
*** Bug 407180 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 339783] Wishlist: Tab bar on the left/right side of UI

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

--- Comment #1 from Ovidiu-Florin BOGDAN  ---
Possible Duplicate of Bug 74137.

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

[plasmashell] [Bug 435681] Changing themes from Light to Dark leaves white text on white background

[Ovidiu-Florin BOGDAN]

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

--- Comment #1 from Ovidiu-Florin BOGDAN  ---
There is a similar issue when I switch from Dark Breeze to Light Breeze: Icons
in the system tray don't switch colors and remain white for the following apps:
Nextcloud, Slack and others. Please note that this does not happen when
switching from Light to Dark.

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

[plasmashell] [Bug 435681] New: Changing themes from Light to Dark leaves white text on white background

[Ovidiu-Florin BOGDAN]

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

Bug ID: 435681
   Summary: Changing themes from Light to Dark leaves white text
on white background
   Product: plasmashell
   Version: 5.20.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Theme packages
  Assignee: plasma-b...@kde.org
  Reporter: ovidiu@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 137554
  --> https://bugs.kde.org/attachment.cgi?id=137554&action=edit
White text on white background

SUMMARY
Changing themes from Light Breeze to Dark Breeze leaves white text on light
colored background in KRunner (see screenshot) and the Login screen when
resuming from stand-by (Sleep).

A reboot solves the issue.


STEPS TO REPRODUCE
1. Start computer (boot up) using the Breeze Light theme.
2. Change the theme to Breeze Dark

OBSERVED RESULT
KRunner keeps the background color from the Light theme
The Login Password field (when resuming from stand-by) keeps the background
color from the Light theme. The selection background is also white, so I can't
tell if anything is selected or not.

EXPECTED RESULT
The background colors to be updated to the dark theme.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33 KDE
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

See attached screenshot with partially selected text to emphasize that text is
there.

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

[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update

[Ovidiu-Florin BOGDAN]

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

--- Comment #7 from Ovidiu-Florin BOGDAN  ---
It seems this part was lost:

* Dismissing that error message shows the same "Install in progress" view. It
does not reset back to the "These are the available updates to be installed"
view I saw when I opened Discover.

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

[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update

[Ovidiu-Florin BOGDAN]

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

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
Created attachment 137545
  --> https://bugs.kde.org/attachment.cgi?id=137545&action=edit
Second Abort button

This button only is revealed if you come with the cursor from the bottom of the
main button.

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

[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update

[Ovidiu-Florin BOGDAN]

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

--- Comment #5 from Ovidiu-Florin BOGDAN  ---
I haven't installed my updates for a few days to collect some for this test.

After I've started `pkcon update` it presented me with all the packages to be
updated and as soon as I confirmed the cursor jumped up about 20 lines and
started overwriting what was already on the screen. I was using Konsole
maximised.


$ pkcon update
Se obțin actualizări[=] 
Încheiat [=] 
Se pornește  [=] 
Se testează modificările[=] 
Încheiat [ ] (0%)  
Următoarele pachete trebuiesc actualizate:
 authselect-1.2.3-1.fc33.x86_64 Configures authentication and identity sources
from supported profiles
 ...
 perl-I18N-Langinfo-0.19-469.fc33.x86_64Query locale information
 perl-IO-1.43-469.fc33.x86_64   Perl input/output modules
 perl-IPC-Open3-1.21-469.fc33[=] g, writing,
and error handling
Se actualizează pachete  [=] nometric
functions
Se interoghează  [=] nctions by
caching return values
Se descarcă pachete  [=] 
Încheiat [=] n network
resolver
Eroare fatală: Cannot download vscodium-1.55.1-x86_64.rpm: All mirrors were
tried; Last error: Curl error (28): Timeout was reached for
https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/rpms/vscodium-1.55.1-x86_64.rpm
[Operation too slow. Less than 1000 bytes/sec transferred the last 30
seconds]003.1


Since this bug was reported I've updated my system and I now have the following
setup:
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33 KDE
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

Retrying in Discover to replicate the bug, I've noticed the following:

* When opening Discover after was already notified that there are updates does
not immediately trigger a check for updates.
* After starting the updates install and disconnecting from the internet, was
quickly presented with a banner at the bottom that there was a failure (could
not copy the text from there
* After about the same amount of time I waited for `pkcon update` to fail
Discover stopped the update process with a message stating that there was a
problem with updating. The details were the same error message as pkcon
* Dismissing that error message
* Hovering from the app list to the "Renunță" (Cancel/Abort) button reveals
another hidden button, that disappears immediately if I move my mouse again. It
does not appear if I come from the sides. (see screenshot)
* Clicking the Abort button resets the view.

I would have expected the view to reset after I acknowledged the network error.

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

[plasma-pa] [Bug 435199] Offer a choice whether mute actions mute all relevant devices, or just the default one

[Ovidiu-Florin BOGDAN]

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

--- Comment #1 from Ovidiu-Florin BOGDAN  ---
I like the idea presented in bug 434217 about having 2 sets of shortcuts: one
for mute all and one for mute the default device. That way we don't need a
setting to have one or the other and everyone can have both. Key combination
with shift is a good idea.

Which one is the default (without shift) is irrelevant to me as I expect we
will be able to edit these shortcuts like all the others and choose what's most
comfortable for each one of us.

Thank you Nate for doing an awesome job aggregating these issues.

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