[plasmashell] [Bug 484546] Plasma crashes when drag'n'dropping file from notifications menu

[Petrov Egor]

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

Petrov Egor  changed:

   What|Removed |Added

 CC||dikey0fic...@disroot.org

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

[plasmashell] [Bug 484546] New: Plasma crashes when drag'n'dropping file from notifications menu

[Petrov Egor]

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

Bug ID: 484546
   Summary: Plasma crashes when drag'n'dropping file from
notifications menu
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: plasma-b...@kde.org
  Reporter: dikey0fic...@disroot.org
CC: k...@privat.broulik.de
  Target Milestone: 1.0

SUMMARY
Some applications, like Spectacle, Ark and Firefox, show notifications with
draggable files. For instance, if you take a screenshot using a hotkey, you
will get this type of notification. However, if you wait until the notification
disappears in the notifications applet and then try to drag'n'drop file, Plasma
crashes.

STEPS TO REPRODUCE
1. Get notification with draggable file attachment (make a screenshot or
download something in Firefox)
2. Wait until notification hides
3. Try to drag file from notifications applet

OBSERVED RESULT
Plasma crashes.

EXPECTED RESULT
Normal drag'n'drop

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240321
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.4.12-1-default (64-bit)
Graphics Platform: Wayland

Bug were also reproduced with this configuration (https://t.me/kde_ru/268085):
Operating System: Manjaro Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-2-MANJARO (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
Also seen this bug on Plasma 5 with Wayland session.
Also sorry for bad English, first paragraph was written with machine
translator.

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

[Bluedevil] [Bug 479868] The "On login" setting for the Bluetooth on/off state is not respected

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

 CC||egor.kuznetsov...@gmail.com

--- Comment #4 from Egor Kuznetsov  ---
Seems, it's back. Reproduced as Ilya writes. 

I don't know why, but after some reboots it write in .config/bluedevilglobalrc
string about my adapter like:
[Adapters]
MACAddressOfAdapter_powered=false

When I delete config and enable bluetooth on boot again, it works, but can
return and I need again delete config.

Operating System: openSUSE Tumbleweed 20240314
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: HP Laptop 15s-eq2xxx

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

[plasmashell] [Bug 477768] Sometimes Application menu out of border

[Egor Kuznetsov]

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

--- Comment #1 from Egor Kuznetsov  ---
Created attachment 163651
  --> https://bugs.kde.org/attachment.cgi?id=163651=edit
Breaking borders by list of apps

I don't know, does I need to create separate bug report, but this break borders
of list of apps too

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

[plasmashell] [Bug 477768] New: Sometimes Application menu out of border

[Egor Kuznetsov]

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

Bug ID: 477768
   Summary: Sometimes Application menu out of border
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: 1.0

Created attachment 163650
  --> https://bugs.kde.org/attachment.cgi?id=163650=edit
Screenshot of breaking borders

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
***
Sometimes when I type something in Search field (for example I write "gtk"),
Application menu break their own borders

STEPS TO REPRODUCE
1. Change Application Launcher to Applcation menu
2. Type something in Search field

OBSERVED RESULT
Application Menu break own borders

EXPECTED RESULT
Application Menu save borders

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7,7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION

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

[Merkuro] [Bug 477767] New: Merkuro-contact crash on contact creation

[Egor Kuznetsov]

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

Bug ID: 477767
   Summary: Merkuro-contact crash on contact creation
Classification: Applications
   Product: Merkuro
   Version: 24.01.80
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Created attachment 163646
  --> https://bugs.kde.org/attachment.cgi?id=163646=edit
Crash report of Merkuro-Contact

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
***
When I try to create contact throw contact creation menu and press "+Add"
Merkuro-Contact crash

STEPS TO REPRODUCE
1. Open Merkuro-Contact
2. Press "+ Create"
3. Add something about new contact (I add only name)
4. Press "+ Add"

OBSERVED RESULT
Merkuro-Contact crashes immediately

EXPECTED RESULT
Merkuro-Contact add new contact 

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7,7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION

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

[frameworks-baloo] [Bug 477754] Baloo_file crash immediately after login

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

   Keywords||qt6

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

[frameworks-baloo] [Bug 477754] New: Baloo_file crash immediately after login

[Egor Kuznetsov]

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

Bug ID: 477754
   Summary: Baloo_file crash immediately after login
Classification: Frameworks and Libraries
   Product: frameworks-baloo
   Version: 5.246.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

Created attachment 163640
  --> https://bugs.kde.org/attachment.cgi?id=163640=edit
Baloo_file crash file

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
***
Every time (2 boots as minimum) when I login into system, baloo generate crash
report with don't understandable error

STEPS TO REPRODUCE
1. Install KDE Neon Unstable
2. Login into system
3. Baloo_file generate crashreport

OBSERVED RESULT
Crash is happening

EXPECTED RESULT
Crash doesen't happening

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7,7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION

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

[neon] [Bug 477546] KDE Neon doesen't start to install due Calamares undefined symbol

[Egor Kuznetsov]

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

--- Comment #1 from Egor Kuznetsov  ---
Fixed in latest release, maybe can close it

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

[kate] [Bug 477746] New: Weird black rectangle in Search overlaps field

[Egor Kuznetsov]

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

Bug ID: 477746
   Summary: Weird black rectangle in Search overlaps field
Classification: Applications
   Product: kate
   Version: 24.01.80
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

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

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Weird black rectangle overlaps search field in Configure

STEPS TO REPRODUCE
1. Open Kate
2. Choose Configure option

OBSERVED RESULT
Search field closed by black rectangle

EXPECTED RESULT
Search field would clear

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)

ADDITIONAL INFORMATION

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

[neon] [Bug 477546] KDE Neon doesen't start to install due Calamares undefined symbol

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

Summary|KDE Neon doesen't start to  |KDE Neon doesen't start to
   |boot due Calamares  |install due Calamares
   |undefined symbol|undefined symbol

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

[neon] [Bug 477546] New: KDE Neon doesen't start to boot due Calamares undefined symbol

[Egor Kuznetsov]

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

Bug ID: 477546
   Summary: KDE Neon doesen't start to boot due Calamares
undefined symbol
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@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.  Download KDE Neon Unstable (neon-unstable-20231119-1118)
2.  Boot into it in virtual machine
3.  Try to click on "Install system" or start manually from terminal via

OBSERVED RESULT
Calamares doesen't start

EXPECTED RESULT
Calamares start, all gonna install

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.81.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-36-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.1

ADDITIONAL INFORMATION
Error message: /usr/bin/_neon.calamares: symbol lookup error:
/lib/x86_64-linux-gnu/libcalamares.so.3.3: undefined symbol:
_ZN10FileSystem11nameForTypeENS_4TypeERK11QstringList

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

[dolphin] [Bug 474258] Dolphin crashes on deleting file

[Egor]

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

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

dolphin (21.12.3) using Qt 5.15.2

- What I was doing when the application crashed:
While copying files to the flash drive, I deleted files that were supposed to
be copied to the media and then dolphin gave an error.

-- Backtrace (Reduced):
#4  0x7f482570c9c7 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f48266e2392 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#6  0x7f48266e91a0 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#7  0x7f482570cc53 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#8  0x7f482672404b in QWidget::setParent(QWidget*, QFlags)
() from /usr/lib64/libQt5Widgets.so.5

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

[dolphin] [Bug 474258] Dolphin crashes on deleting file

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||mars-romanov...@mail.ru

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

[NeoChat] [Bug 466330] NeoChat Crashes at launch

[Petrov Egor]

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

--- Comment #4 from Petrov Egor  ---
Created attachment 162130
  --> https://bugs.kde.org/attachment.cgi?id=162130=edit
New crash information added by DrKonqi

neochat (23.08.1) using Qt 5.15.10

Just installed NeoChat from main repo (openSUSE Tumbleweed), crashes just after
launching.

Is there enough data?

-- Backtrace (Reduced):
#4  Quotient::RoomStateView::RoomStateView(Quotient::RoomStateView const&)
(this=this@entry=0x7fff37ef1468) at
/usr/src/debug/libQuotient-0.8.1.2/Quotient/roomstateview.h:24
#5  Quotient::Room::currentState() const (this=this@entry=0x0) at
/usr/src/debug/libQuotient-0.8.1.2/Quotient/room.cpp:1574
#6  0x555b5af28939 in ImagePacksModel::reloadImages()
(this=this@entry=0x555b5d4300f0) at
/usr/src/debug/neochat-23.08.1/src/models/imagepacksmodel.cpp:105
#7  0x555b5af29b5d in ImagePacksModel::setRoom(NeoChatRoom*)
(room=, this=0x555b5d4300f0) at
/usr/src/debug/neochat-23.08.1/src/models/imagepacksmodel.cpp:73
#8  ImagePacksModel::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=_o@entry=0x555b5d4300f0, _c=_c@entry=QMetaObject::WriteProperty,
_id=_id@entry=0, _a=_a@entry=0x7fff37ef1690) at
/usr/src/debug/neochat-23.08.1/build/src/neochat_autogen/include/moc_imagepacksmodel.cpp:167

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

[NeoChat] [Bug 466330] NeoChat Crashes at launch

[Petrov Egor]

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

Petrov Egor  changed:

   What|Removed |Added

 CC||dikey0fic...@disroot.org

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

[kamoso] [Bug 475049] Kamoso crash on camera unplugging

[Egor Kuznetsov]

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

--- Comment #1 from Egor Kuznetsov  ---
Crash report with debugging symbols here. Looks like what needed?

[KCrash Handler]
#4  g_type_check_instance_is_fundamentally_a
(type_instance=type_instance@entry=0x563fd78178f0,
fundamental_type=fundamental_type@entry=80) at ../gobject/gtype.c:4184
#5  0x7f53ab4e6428 in g_object_notify (object=0x563fd78178f0,
property_name=0x7f53654608c9 "zoom") at ../gobject/gobject.c:1583
#6  0x7f53ab4df468 in g_closure_invoke (closure=0x563fd78d5010,
return_value=0x0, n_param_values=2, param_values=0x7ffebf06a440,
invocation_hint=0x7ffebf06a390) at ../gobject/gclosure.c:832
#7  0x7f53ab4f261c in signal_emit_unlocked_R
(node=node@entry=0x7ffebf06a510, detail=detail@entry=2562,
instance=instance@entry=0x563fd779dea0,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7ffebf06a440) at
../gobject/gsignal.c:3980
#8  0x7f53ab4f4031 in signal_emit_valist_unlocked
(instance=instance@entry=0x563fd779dea0, signal_id=signal_id@entry=1,
detail=detail@entry=2562, var_args=var_args@entry=0x7ffebf06a670) at
../gobject/gsignal.c:3612
#9  0x7f53ab4f9ce2 in g_signal_emit_valist (instance=0x563fd779dea0,
signal_id=1, detail=2562, var_args=0x7ffebf06a670) at ../gobject/gsignal.c:3355
#10 0x7f53ab4f9d8f in g_signal_emit
(instance=instance@entry=0x563fd779dea0, signal_id=,
detail=) at ../gobject/gsignal.c:3675
#11 0x7f53ab4e36e4 in g_object_dispatch_properties_changed
(object=0x563fd779dea0, n_pspecs=, pspecs=) at
../gobject/gobject.c:1427
#12 0x7f53a96ec1e4 in gst_object_dispatch_properties_changed
(object=0x563fd779dea0, n_pspecs=1, pspecs=0x7ffebf06a7e0) at
../gst/gstobject.c:455
#13 0x7f53ab4e4038 in g_object_notify_queue_thaw (object=0x563fd779dea0,
nqueue=) at ../gobject/gobject.c:358
#14 0x7f53ab4e7ee6 in g_object_set_valist (var_args=0x7ffebf06a970,
first_property_name=, object=) at
../gobject/gobject.c:2792
#15 g_object_set_valist (object=, first_property_name=, var_args=0x7ffebf06a970) at ../gobject/gobject.c:2741
#16 0x7f53ab4e8ac3 in g_object_set (_object=0x563fd779dea0,
first_property_name=first_property_name@entry=0x7f53654608c9 "zoom") at
../gobject/gobject.c:2956
#17 0x7f536545ccb1 in gst_camera_bin_create_elements
(camera=0x563fd7ae7b20) at ../gst/camerabin2/gstcamerabin2.c:1742
#18 gst_camera_bin_change_state (element=0x563fd7ae7b20,
trans=GST_STATE_CHANGE_NULL_TO_READY) at ../gst/camerabin2/gstcamerabin2.c:1891
#19 0x7f53a971a47b in gst_element_change_state
(element=element@entry=0x563fd7ae7b20,
transition=transition@entry=GST_STATE_CHANGE_NULL_TO_READY) at
../gst/gstelement.c:3093
#20 0x7f53a971ad0b in gst_element_set_state_func (element=0x563fd7ae7b20,
state=GST_STATE_READY) at ../gst/gstelement.c:3047
#21 0x563fd5874a30 in WebcamControl::playDevice (this=0x7ffebf06b060,
device=0x563fd732f050) at /usr/include/qt5/QtCore/qscopedpointer.h:138
#22 0x563fd5875d3d in WebcamControl::onBusMessage (message=,
this=) at
/usr/src/debug/kamoso-23.08.1/src/video/webcamcontrol.cpp:308
#23 webcamWatch (message=, user_data=0x7ffebf06b060) at
/usr/src/debug/kamoso-23.08.1/src/video/webcamcontrol.cpp:244
#24 0x7f53a9702131 in gst_bus_source_dispatch (source=0x563fd7058060,
callback=0x563fd5875ad0 ,
user_data=0x7ffebf06b060) at ../gst/gstbus.c:821
#25 0x7f53a95bcef0 in ?? () from /lib64/libglib-2.0.so.0
#26 0x7f53a95beb18 in ?? () from /lib64/libglib-2.0.so.0
#27 0x7f53a95bf1cc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f53a9b464a6 in QEventDispatcherGlib::processEvents
(this=0x563fd6e62e10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f53a9aebffb in QEventLoop::exec (this=this@entry=0x7ffebf06ae70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x7f53a9af4490 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x563fd587077d in main (argc=, argv=) at
/usr/src/debug/kamoso-23.08.1/src/main.cpp:47
[Inferior 1 (process 15274) detached]

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

[kamoso] [Bug 475049] New: Kamoso crash on camera unplugging

[Egor Kuznetsov]

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

Bug ID: 475049
   Summary: Kamoso crash on camera unplugging
Classification: Applications
   Product: kamoso
   Version: 23.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

SUMMARY
***
When I start Kamoso with plugged USB camera, it can show picture, but when I
unplug it with open Kamoso, it crashed with some logs in terminal
***


STEPS TO REPRODUCE
1. Open Kamoso
2. Plug USB webcam
3. Unplug USB webcam

OBSERVED RESULT
Kamoso crashed with next log:
(kamoso:14078): GLib-GObject-CRITICAL **: 16:07:58.798: g_object_notify:
assertion 'G_IS_OBJECT (object)' failed
Fatal glibc error: pthread_mutex_lock.c:130 (___pthread_mutex_lock): assertion
failed: mutex->__data.__owner == 0
20 -- exe=/usr/bin/kamoso
17 -- platform=wayland
15 -- appname=kamoso
17 -- apppath=/usr/bin
9 -- signal=6
10 -- pid=14078
19 -- appversion=23.08.1
19 -- programname=Kamoso
31 -- bugaddress=sub...@bugs.kde.org
KCrash: Application 'kamoso' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
[1]  + 14078 suspended (signal)  kamoso


EXPECTED RESULT
Nothing crashed, Kamoso black screen again

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230926
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: ASUS

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

[kdevelop] [Bug 474082] No support of fish shell in `kdevelop!` script

[Petrov Egor]

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

--- Comment #6 from Petrov Egor  ---
Okay, thanks for attention.

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

[kdevelop] [Bug 474082] No support of fish shell in `kdevelop!` script

[Petrov Egor]

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

--- Comment #4 from Petrov Egor  ---
> If the path where `kdevelop!` is installed is not the first entry in $PATH, 
> you
> can create a custom, possibly empty, `kdevelop!` script in a preceding path,
> e.g. ~/.local/bin/kdevelop!. This script should take precedence over the 
> script
> provided by KDevelop. So, in this sense, the option you ask for already 
> exists.

Just tried — that's works, thanks! But i believe that it should be only
workaround, not a recommended way ;)

By option i mean checkbox in KDevelop settings menu that sets should
konsole load kdevelop! script or something else.

> The ideal solution is obvious: translate KDevelop's scripts into fish. But
> apparently no one priorities this solution highly enough to implement it.

Okay.

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

[kdevelop] [Bug 474082] No support of fish shell in `kdevelop!` script

[Petrov Egor]

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

--- Comment #2 from Petrov Egor  ---
> --- Comment #1 from Igor Kushnir  ---
> > Support of fish shell
> https://commits.kde.org/kdevelop/f3bde6dcd4767396b5fce7572be565f345adf271 
> added
> support for zsh relatively recently. If fish is similar enough to bash, you
> could easily add support for it too and create a merge request.

However, it's not so similar; at least, fish isn't POSIX and has
own syntax.

> > or at least not run `kdevelop!` script in unsupported shells
> Not running the `kdevelop!` script in unsupported shells would make
> KDevelop-specific functions defined in kdevplatform_shell_environment.sh
> unavailable. So this doesn't look like a viable general solution for me.

I mean, adding an option to disable it in terminal pane would be
enough, although it's not an ideal solution ;)

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

[kdevelop] [Bug 474082] No support of fish shell in `kdevelop!` script

[Petrov Egor]

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

Petrov Egor  changed:

   What|Removed |Added

 CC||dikey0fic...@disroot.org

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

[kdevelop] [Bug 474082] New: No support of fish shell in `kdevelop!` script

[Petrov Egor]

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

Bug ID: 474082
   Summary: No support of fish shell in `kdevelop!` script
Classification: Applications
   Product: kdevelop
   Version: 5.11.230403
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: dikey0fic...@disroot.org
  Target Milestone: ---

SUMMARY
Currently, `kdevelop!` script, which autoruns in built-in terminal pane)
supports only bash and zsh. When I'm using terminal, it loads into fish, but
immediately runs `kdevelop!` script, which start interactive bash shell.


STEPS TO REPRODUCE
1. Set fish as your $SHELL;
2. Open terminal pane in kdevelop;

EXPECTED RESULT
Support of fish shell or at least not run `kdevelop!` script in unsupported
shells

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230828
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HUAWEI
Product Name: HLYL-WXX9
System Version: M1010

ADDITIONAL INFORMATION
$SHELL: /usr/bin/fish

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

[XWaylandVideoBridge] [Bug 471140] Xwayland Video Bridge stopped working on Arch

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

 CC||egor.kuznetsov...@gmail.com

--- Comment #6 from Egor Kuznetsov  ---
(In reply to David Edmundson from comment #4)
> My released flatpak still works as intended. 
> 
> Checking out xwaylandvideo bridge at the same commit as the released flatpak
> does not work.

Flatpak XWaylandBridge version worked in
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#8149214815066223
but not worked with Discord Flatpak and Discord RPM

Fedora 38 with KDE 5.27.5, KF 5.107 and Qt 5.15.10

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

[kate] [Bug 470559] New: [wish] Vim-like commands for folding/unfolding code

[Petrov Egor]

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

Bug ID: 470559
   Summary: [wish] Vim-like commands for folding/unfolding code
Classification: Applications
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Vi Input Mode
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: dikey0fic...@disroot.org
  Target Milestone: ---

SUMMARY:
In Vim there are special commands to fold/unfold code, like `za` (toggles
fold), `zo` (opens fold), `zc` (closes fold) and so on. It would be nice if
these combinations were also available in Kate's Vi Input mode.

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

[kwin] [Bug 468304] New: KWin lock frequency on 60 Hz

[Egor Kuznetsov]

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

Bug ID: 468304
   Summary: KWin lock frequency on 60 Hz
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

SUMMARY
I noticed that if I enable the AMD Freesync option in the monitor settings, and
then set the screen refresh rate in the monitor settings to be different from
165 Hz and possibly higher, the monitor and KDE continue to run at 60 Hz.
However, this behavior does not depend on the set option for Adaptive sync in
Display Configuration in System Settings (if I set Never, for example, Hz lock
still exists)


STEPS TO REPRODUCE
1. Turn on AdaptiveSync (maybe it will be called FreeSync in other model of
displays) in display settings
2. Choose any refresh rate up to 165 Hz
3. Accept new refresh rate

OBSERVED RESULT
Display says that refresh rate is 60 Hz and I visually noticed that desktop
compositing still runs at 60 FPS

EXPECTED RESULT
Display must operate at the frequency specified in the display settings

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230407
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: ASUS

ADDITIONAL INFORMATION
If it can be helpful, Display model is MSI G27CQ4 E2. I use DisplayPort for
connection

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

[kwin] [Bug 402857] Touchpad gestures are not configurable

[Petrov Egor]

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

Petrov Egor  changed:

   What|Removed |Added

 CC||m...@dikey0ficial.rf.gd

--- Comment #4 from Petrov Egor  ---
Sadly that in the most configurable DE touchpad gestures couldn'be customized;(

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

[kwin] [Bug 464169] Second monitor freezes with game launched on it. [NVIDIA HYBRID+WAYLAND]

[Egor]

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

--- Comment #5 from Egor  ---
Created attachment 155673
  --> https://bugs.kde.org/attachment.cgi?id=155673=edit
drm_info

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

[kwin] [Bug 464169] Second monitor freezes with game launched on it. [NVIDIA HYBRID+WAYLAND]

[Egor]

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

--- Comment #4 from Egor  ---
```
Jan 26 22:23:26 fedora systemd[1799]: Starting plasma-kwin_wayland.service -
KDE Window Manager...
Jan 26 22:23:26 fedora systemd[1799]: Started plasma-kwin_wayland.service - KDE
Window Manager.
Jan 26 22:23:26 fedora kwin_wayland[1866]: No backend specified, automatically
choosing drm
Jan 26 22:23:26 fedora kwin_wayland[1866]: OpenGL vendor string:   
   AMD
Jan 26 22:23:26 fedora kwin_wayland[1866]: OpenGL renderer string: 
   AMD Radeon Graphics (renoir, LLVM 15.0.6, DRM 3.49, 6.1.7-200.fc37.x86_64)
Jan 26 22:23:26 fedora kwin_wayland[1866]: OpenGL version string:  
   4.6 (Core Profile) Mesa 22.3.3
Jan 26 22:23:26 fedora kwin_wayland[1866]: OpenGL shading language version
string: 4.60
Jan 26 22:23:26 fedora kwin_wayland[1866]: Driver: 
   Unknown
Jan 26 22:23:26 fedora kwin_wayland[1866]: GPU class:  
   Unknown
Jan 26 22:23:26 fedora kwin_wayland[1866]: OpenGL version: 
   4.6
Jan 26 22:23:26 fedora kwin_wayland[1866]: GLSL version:   
   4.60
Jan 26 22:23:26 fedora kwin_wayland[1866]: Mesa version:   
   22.3.3
Jan 26 22:23:26 fedora kwin_wayland[1866]: Linux kernel version:   
   6.1.7
Jan 26 22:23:26 fedora kwin_wayland[1866]: Requires strict binding:
   no
Jan 26 22:23:26 fedora kwin_wayland[1866]: GLSL shaders:   
   yes
Jan 26 22:23:26 fedora kwin_wayland[1866]: Texture NPOT support:   
   yes
Jan 26 22:23:26 fedora kwin_wayland[1866]: Virtual Machine:
   no
Jan 26 22:23:27 fedora kwin_wayland[1866]: kwin_wayland_drm: Failed to create
framebuffer for multi-gpu: Invalid argument
Jan 26 22:23:27 fedora kwin_wayland[1866]: kwin_xkbcommon: XKB: inet:323:58:
unrecognized keysym "XF86EmojiPicker"
Jan 26 22:23:27 fedora kwin_wayland[1866]: kwin_xkbcommon: XKB: inet:324:58:
unrecognized keysym "XF86Dictate"
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1939]: (WW) Option "-listen" for
file descriptors is deprecated
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1939]: Please use "-listenfd"
instead.
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1939]: (WW) Option "-listen" for
file descriptors is deprecated
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1939]: Please use "-listenfd"
instead.
Jan 26 22:23:27 fedora kwin_wayland[1866]: kwin_wayland_drm: Failed to create
gamma blob! Invalid argument
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1971]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1971]: > Warning: 
Unsupported maximum keycode 708, clipping.
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1971]: >   X11
cannot support keycodes above 255.
Jan 26 22:23:27 fedora kwin_wayland_wrapper[1971]: Errors from xkbcomp are not
fatal to the X server
Jan 26 22:23:33 fedora kwin_wayland[1866]: QQmlEngine::setContextForObject():
Object already has a QQmlContext
Jan 26 22:23:33 fedora kwin_wayland[1866]:
file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
Jan 26 22:23:33 fedora kwin_wayland[1866]:
file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{0ba0e2e1-8636-4e9f-80c3-13340f917bb6}"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{0ba0e2e1-8636-4e9f-80c3-13340f917bb6}"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{4be79f5b-aef3-47cb-939e-861c292b94ac}"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{4be79f5b-aef3-47cb-939e-861c292b94ac}"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{4be79f5b-aef3-47cb-939e-861c292b94ac}"
Jan 26 22:28:13 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{4be79f5b-aef3-47cb-939e-861c292b94ac}"
Jan 26 22:31:51 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{a837d157-8931-4666-af5f-4d8acb859f9e}"
Jan 26 22:31:51 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{a837d157-8931-4666-af5f-4d8acb859f9e}"
Jan 26 22:31:51 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{a837d157-8931-4666-af5f-4d8acb859f9e}"
Jan 26 22:31:51 fedora kwin_wayland[1866]: kwin_core: Could not find window
with uuid "{a837d157-8931-4666-af5f-4d8acb859f9e}"
Jan 26 22:34:17 fedora kwin_wayland[1866]: kwin_core: Failed to focus 0x1400209
(error 8)
Ja

[Discover] [Bug 464849] New: Discover crashes when trying to view installed applications.

[Egor Stoyakin]

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

Bug ID: 464849
   Summary: Discover crashes when trying to view installed
applications.
Classification: Applications
   Product: Discover
   Version: 5.26.5
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: stoyakine...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.26.5)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 5.15.0-58-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.26
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
Discover crashes when trying to view installed applications.

The crash can be reproduced every time.

-- Backtrace:
Application: Центр программ Discover (plasma-discover), signal: Segmentation
fault

[KCrash Handler]
#4  0x7f2d88563859 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#5  0x7f2d88577bdb in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so
#6  0x7f2deddd7ade in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2deef73793 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f2deddaa07a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2deddad167 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f2dede04487 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f2dec43ad3b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f2dec48f6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f2dec4383e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7f2dede03ad8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f2dedda899b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f2deddb0f34 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x560510477b43 in ?? ()
#18 0x7f2ded6c5d90 in __libc_start_call_main
(main=main@entry=0x560510477220, argc=argc@entry=1,
argv=argv@entry=0x7ffc366dec48) at ../sysdeps/nptl/libc_start_call_main.h:58
#19 0x7f2ded6c5e40 in __libc_start_main_impl (main=0x560510477220, argc=1,
argv=0x7ffc366dec48, init=, fini=,
rtld_fini=, stack_end=0x7ffc366dec38) at ../csu/libc-start.c:392
#20 0x560510478585 in ?? ()
[Inferior 1 (process 31397) detached]

The reporter indicates this bug may be a duplicate of or related to bug 457059,
bug 457202, bug 457278, bug 457411, bug 457444, bug 458763, bug 458531, bug
458259, bug 457569, bug 459542, bug 459909, bug 460066, bug 460503, bug 460900,
bug 462011, bug 462630, bug 462998, bug 463070, bug 463446, bug 463704, bug
463736, bug 463768, bug 463864, bug 464357, bug 464517.

Reported using DrKonqi

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

[kwin] [Bug 464169] Second monitor freezes with game launched on it. [NVIDIA HYBRID+WAYLAND]

[Egor]

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

--- Comment #2 from Egor  ---
(In reply to Zamundaaa from comment #1)
> Does it still happen if you put KWIN_DRM_NO_DIRECT_SCANOUT=1 into
> /etc/environment and reboot?

No, games works good with it. Also I noticed games launched via gamescope are
not affected

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

[kwin] [Bug 464169] New: Second monitor freezes with game launched on it. [NVIDIA HYBRID+WAYLAND]

[Egor]

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

Bug ID: 464169
   Summary: Second monitor freezes with game launched on it.
[NVIDIA HYBRID+WAYLAND]
Classification: Plasma
   Product: kwin
   Version: 5.26.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ragusse...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Launch game using discrette nvidia gpu on second monitor with wayland

OBSERVED RESULT
second monitor totally freezes

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Nvidia: 525.60.11

ADDITIONAL INFORMATION
GPU: GTX 1650 in notebook
Fedora Kinoite 37
Wayland
Second monitor connected via HDMI

It works good on GNOME, but all freezes on Plasma. I tried to make second
monitor primary, set 60hz, disable notebook screen. Games works perfect on
notebook screen, but freezes when I drag it to second monitor.

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

[kalendar] [Bug 463145] Kalendar crash when changing completition status of tasks

[Petrov Egor]

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

Petrov Egor  changed:

   What|Removed |Added

 CC||m...@dikey0ficial.rf.gd

--- Comment #1 from Petrov Egor  ---
Have the same problem ad error in trace. Also have this on changing name after
double-clicking on task.
Maybe that's openSUSE-specific problem?

Operating System: openSUSE Tumbleweed 20221216
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.0.12-1-default (64-bit)
Graphics Platform: X11

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

[kde] [Bug 463040] New: Digital Clock widget doesn't show month on Wayland

[Egor Kuznetsov]

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

Bug ID: 463040
   Summary: Digital Clock widget doesn't show month on Wayland
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

SUMMARY
When you click to calendar on panel and try to click on Months tab, it doesn't
show months, but all is clickable.

STEPS TO REPRODUCE
1. Start KDE Wayland Session
2. Click on Calendar on panel
3. Click on Months tab

OBSERVED RESULT
Doesn't show names of months (https://imgur.com/a/ybBdNKj) 

EXPECTED RESULT
Like on X11, widget need to show names of months

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221213
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.0.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics

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

[QtCurve] [Bug 359209] pop-up menu opacity broken

[Egor Y. Egorov]

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

--- Comment #7 from Egor Y. Egorov  ---
Qt4 applications are not present in Gentoo now. Issue can be closed. Thanks

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

[QtCurve] [Bug 368672] kdialog hangs on popup menu when using qtcurve with menu opacity less then 100

[Egor Y. Egorov]

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

--- Comment #9 from Egor Y. Egorov  ---
This bug is not reproduced now. Issue can be closed. Thanks

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

[dolphin] [Bug 459545] Cannot delete from trash clicking "Delete" button: Changing the attributes of files is not supported with protocol trash

[Petrov Egor]

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

--- Comment #5 from Petrov Egor  ---
Updated to Plasma 5.26. Nothing changed, bug still reproduces

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

[kdeconnect] [Bug 415426] photo plugin, no item in plasmoid menu

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||ragusse...@gmail.com

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

[kscreenlocker] [Bug 454397] New: Excessive shortcut to lock screen

[Egor]

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

Bug ID: 454397
   Summary: Excessive shortcut to lock screen
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ragusse...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

Created attachment 149210
  --> https://bugs.kde.org/attachment.cgi?id=149210=edit
two shortcuts enabled by default

ctrl+alt+l is a global shortcut without using meta key. It can be used by some
software (for example ctrl+alt+l is a popular shortcut in a jetbrains software
kit).

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

[print-manager] [Bug 452029] Error with print-manager window on Panel

[Egor Kuznetsov]

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

--- Comment #1 from Egor Kuznetsov  ---
Screenshot with bug links here: https://imgur.com/a/SdZME7b

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

[print-manager] [Bug 452029] New: Error with print-manager window on Panel

[Egor Kuznetsov]

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

Bug ID: 452029
   Summary: Error with print-manager window on Panel
   Product: print-manager
   Version: 22.03.80
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: dantt...@gmail.com
  Reporter: egor.kuznetsov...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Update to version 22.03.80 (on latest version repo for SUSE it's
22.03.80-232.1)
2. Click to printer icon on Panel

OBSERVED RESULT
See error report about plasmoid:
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/printmanager.qml:56:34:
Type PopupDialog unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:61:24:
PlasmaExtras.Highlight is not a type

EXPECTED RESULT
See some printers or nothing when zero printers connected

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220324
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2
Kernel Version: 5.16.15-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION
I use repos with latest software for openSUSE (not unstable), maybe this can be
useful information.
Version: Tumbleweed
KDE Frameworks 5:
https://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory/
KDE Applications (optional):
https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Tumbleweed/
KDE Extra (optional):
https://download.opensuse.org/repositories/KDE:/Extra/KDE_Frameworks5_openSUSE_Tumbleweed

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

[plasmashell] [Bug 449083] New: Vertical color bar out of border

[Egor Kuznetsov]

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

Bug ID: 449083
   Summary: Vertical color bar out of border
   Product: plasmashell
   Version: 5.23.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: egor.kuznetsov...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

SUMMARY
Vertical color bar out of border on notification popups with rounded borderds


STEPS TO REPRODUCE
1. Wait for notification or manually call notification popup 

OBSERVED RESULT
Vertical bar out of border of popup

EXPECTED RESULT
Bar adjust to the popup borders

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220122 with KDE Beta (not unstable)
repos
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.1-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD RENOIR

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

[kate] [Bug 445128] Kate Window not raised automaticly on Wayland

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

Summary|Kate Window not change  |Kate Window not raised
   |active status automaticly   |automaticly on Wayland
   |on Wayland  |

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

[kate] [Bug 445128] Kate Window not change active status automaticly on Wayland

[Egor Kuznetsov]

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

Egor Kuznetsov  changed:

   What|Removed |Added

Summary|Kate Window not resize auto |Kate Window not change
   |on Wayland  |active status automaticly
   ||on Wayland

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

[kate] [Bug 445128] New: Kate Window not resize auto on Wayland

[Egor Kuznetsov]

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

Bug ID: 445128
   Summary: Kate Window not resize auto on Wayland
   Product: kate
   Version: 21.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: sessions
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: egor.kuznetsov...@gmail.com
  Target Milestone: ---

SUMMARY
When I open file on Kate, minimize window after it and open file from Dolphin
by Kate, Kate window not stays active automaticly, and I need to open Kate
manually

STEPS TO REPRODUCE
1. Open Kate
2. Press Ctrl+O or open file by other options
3. Minimize Kate window
4. Open Dolphin
5. Right click to File, choose Open by and choose Kate

OBSERVED RESULT
Kate window stays inactive and minimized 

EXPECTED RESULT
Kate open window again and stays active and not minimized

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20211105
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.12.2

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

[Spectacle] [Bug 445096] New: Can't paste screens on Wayland

[Egor Kuznetsov]

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

Bug ID: 445096
   Summary: Can't paste screens on Wayland
   Product: Spectacle
   Version: 21.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: egor.kuznetsov...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
I'm can't paste screens after making screenshot by Spectacle 21.08.2 on
Wayland, but it works well on X11.

STEPS TO REPRODUCE
1. Making screen by Spectacle
2. Push button "Copy to clipboard"
3. Try to Ctrl+V on any apps (Browser: tested on Firefox and Vivaldi, Telegram
Desktop)

OBSERVED RESULT
On KDE Wayland nothing happend
On KDE X11 picture pasted

EXPECTED RESULT
On KDE Wayland picture will pasted like on X11
On KDE X11 picture pasted

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20211104
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.12.5

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

[kdenlive] [Bug 414006] Spacer tool is prohibitively slow with many timeline clips

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 443433] Speed effect on image sequence doesn't works correctly

[Egor]

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

Egor  changed:

   What|Removed |Added

Version|21.08.1 |21.08.2

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

[kdenlive] [Bug 443433] Speed effect on image sequence doesn't works correctly

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 443433] New: Speed effect on image sequence doesn't works correctly

[Egor]

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

Bug ID: 443433
   Summary: Speed effect on image sequence doesn't works correctly
   Product: kdenlive
   Version: 21.08.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: e.vakhromt...@gmail.com
  Target Milestone: ---

Created attachment 142236
  --> https://bugs.kde.org/attachment.cgi?id=142236=edit
Example project with bug

Speed effect does not changes actual speed of image sequence clip (it changes
inly clip duration while play speed did not changed).


STEPS TO REPRODUCE
1. Add Image sequence to project (1 image per frame)
2. Append speed effect to clip and change speed to 300%

OBSERVED RESULT

Clip on timeline played at normal speed without any speedup

EXPECTED RESULT
Clip played 3x times faster than normal.

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

[systemsettings] [Bug 440429] New: crash system preferences

[Barinov Egor]

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

Bug ID: 440429
   Summary: crash system preferences
   Product: systemsettings
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: barinove...@outlook.com
  Target Milestone: ---

Application: systemsettings5 (5.22.4)

Qt Version: 5.15.3
Frameworks Version: 5.84.0
Operating System: Linux 5.8.0-63-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: KDE neon User Edition 5.22

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

Application: Параметры системы (systemsettings5), signal: Segmentation fault

[New LWP 4297]
[New LWP 4298]
[New LWP 4299]
[New LWP 4300]
[New LWP 4301]
[New LWP 4302]
[New LWP 4307]
[New LWP 4308]
[New LWP 4312]
[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".
0x7faef85daaff in __GI___poll (fds=0x7ffc81085078, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7faef3e1f9c0 (LWP 4295))]

Thread 12 (Thread 0x7faea5994700 (LWP 4321)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5593440e34f0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5593440e34a0,
cond=0x5593440e34c8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5593440e34c8, mutex=0x5593440e34a0) at
pthread_cond_wait.c:638
#3  0x7faef896cf2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7faef7d79b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7faef7d79fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7faef8966dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7faef7096609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7faef85e7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7faea71bf700 (LWP 4320)):
#0  0x7faef85daaff in __GI___poll (fds=0x7faea0004c70, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7faef66d736e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7faef66d74a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7faef8ba7fcb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7faef8b4c25b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7faef8965c22 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7faef79ff559 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7faef8966dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7faef7096609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7faef85e7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7faec21e8700 (LWP 4312)):
#0  __GI___libc_read (nbytes=16, buf=0x7faec21e79b0, fd=26) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=26, buf=0x7faec21e79b0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7faef671fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7faef66d6ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7faef66d7312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7faef66d74a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7faef8ba7fcb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7faef8b4c25b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7faef8965c22 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7faef79ff559 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7faef8966dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7faef7096609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7faef85e7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7faec35e5700 (LWP 4308)):
#0  __GI___libc_read (nbytes=16, buf=0x7faec35e49b0, fd=21) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=21, buf=0x7faec35e49b0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7faef671fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7faef66d6ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7faef66d7312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7faef66d74a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7faef8ba7fcb in

[plasma-browser-integration] [Bug 439637] New: Unnecessary control buttons under every preview window

[Egor]

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

Bug ID: 439637
   Summary: Unnecessary control buttons under every preview window
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Firefox
  Assignee: k...@privat.broulik.de
  Reporter: egoriv0...@gmail.com
  Target Milestone: ---

Created attachment 139943
  --> https://bugs.kde.org/attachment.cgi?id=139943=edit
picture of described bug

If you have multiple firefox (with plasma integration addon) windows, and one
of them is playing media (e.g. youtube) then playback control buttons (back;
play/pause; forward) will appear under every window in preview (when you hover
cursor on icon).

EXPECTED RESULT
only preview of window with media playing to have those buttons.

ADDITIONAL INFORMATION
Graphics platform: Wayland

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64 
(available in About System)
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

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

[kdenlive] [Bug 436879] VP8 Rendering has a low quality (quality settings do not work)

[Egor]

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

--- Comment #3 from Egor  ---
(In reply to Egor from comment #0)
> Hello!
> 
> Kdenlive 20.04
> 
> Linux (Ubuntu)
>  kdenlive in .APPIMAGE
> 
> vp8 rendering VERY LOW quality video. I cant render good video, because
> settings of quality (in render) in vp8 not work.
> 
> Please, fix,
> and thanks for this very good program (Kdenlive)!

in 20.04 quality settings os vp8 (render) is work. Settings doesn't work in
20.08 (and later).

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

[kdenlive] [Bug 436879] VP8 Rendering has a low quality (quality settings do not work)

[Egor]

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

Egor  changed:

   What|Removed |Added

Version|21.04.0 |21.04.1
   Platform|Other   |Appimage

--- Comment #1 from Egor  ---
Hello!

Kdenlive 21.04.1

Linux (Ubuntu)
 kdenlive in .APPIMAGE

vp8 rendering VERY LOW quality video. I cant render good video, because
settings of quality (in render) in vp8 not work.

Please, fix,
and thanks for this very good program (Kdenlive)!

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

[kdenlive] [Bug 436879] New: vp8

[Egor]

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

Bug ID: 436879
   Summary: vp8
   Product: kdenlive
   Version: 21.04.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: n119...@gmail.com
  Target Milestone: ---

Hello!

Kdenlive 20.04

Linux (Ubuntu)
 kdenlive in .APPIMAGE

vp8 rendering VERY LOW quality video. I cant render good video, because
settings of quality (in render) in vp8 not work.

Please, fix,
and thanks for this very good program (Kdenlive)!

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

[dolphin] [Bug 409179] Dolphin (and Konqueror) do not connect via BlueTooth

[Egor Ignatov]

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

--- Comment #3 from Egor Ignatov  ---
Thanks to Nicolas Fella(@nicolasfella) for his help in fixing this bug.

https://invent.kde.org/plasma/bluedevil/-/merge_requests/36

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

[dolphin] [Bug 409179] Dolphin (and Konqueror) do not connect via BlueTooth

[Egor Ignatov]

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

Egor Ignatov  changed:

   What|Removed |Added

 CC||eg...@basealt.ru

--- Comment #2 from Egor Ignatov  ---
Ping.

Have the same issue.

Dolphin: 19.12.3
Linux:  5.10.26
KDE Frameworks Version:  5.12.9
Qt Version: 5.12.9

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

--- Comment #7 from Egor Ignatov  ---
Additionally segfault occurs only when using png internal plot format.

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

[ktouch] [Bug 434632] New: layouts error in wayland session but without error in X11 session

[Egor]

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

Bug ID: 434632
   Summary: layouts error in wayland session but without error in
X11 session
   Product: ktouch
   Version: 20.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: sebastian.gottfr...@posteo.de
  Reporter: jagua...@mail.ru
  Target Milestone: ---

SUMMARY
in wayland session KTouch return error about layots/
but in X11 session all works OK

STEPS TO REPRODUCE
1. start KTouch in wayland session(in system 2  layouts RU & US(by default))
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

--- Comment #6 from Egor Ignatov  ---
Created attachment 136808
  --> https://bugs.kde.org/attachment.cgi?id=136808=edit
Cantor segfault backtrace

Cantor crashes with "(libspectre) ghostscript reports: syntaxerror -18"

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

--- Comment #5 from Egor Ignatov  ---
Yes, octave-cli 6.2 itself works on both of the systems above.

I tried to change octave executable from 'octave-cli' to just 'octave'
in cantor and it fixed plotting on arch linux.

But in Alt linux gnuplot and qt toolkits started to randomly crash on every
other plot (so plot works sometimes).

But in Alt linux, the gnuplot and qt toolkits started randomly crashing on
every other plot (plot sometimes works).

Is there a reason octave-cli used by default instead of octave?

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

--- Comment #3 from Egor Ignatov  ---
I have this problem on both of my VMs: 
- Alt Linux
Got octave from an rpm package
(http://geyser.altlinux.org/ru/sisyphus/srpms/octave)

- Latest Arch Linux
Got octave from the official repository
(https://archlinux.org/packages/community/x86_64/octave/)

What OS are you using?

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

Egor Ignatov  changed:

   What|Removed |Added

 CC||eg...@basealt.ru

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

Egor Ignatov  changed:

   What|Removed |Added

 CC||warqu...@gmail.com

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

[cantor] [Bug 434271] Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

Egor Ignatov  changed:

   What|Removed |Added

 Attachment #136578|text/x-log  |text/plain
  mime type||

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

[cantor] [Bug 434271] New: Plotting doesn't work with octave 6.2

[Egor Ignatov]

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

Bug ID: 434271
   Summary: Plotting doesn't work with octave 6.2
   Product: cantor
   Version: 20.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: octave-backend
  Assignee: cantor-b...@kde.org
  Reporter: eg...@basealt.ru
  Target Milestone: ---

Created attachment 136578
  --> https://bugs.kde.org/attachment.cgi?id=136578=edit
Execution log

SUMMARY
After updating octave to version 6.2.0, the plot function hangs when evaluating
the worksheet.

STEPS TO REPRODUCE
1. Install octave version 6.2.0
2. Open cantor with octave backend
3. Write 'plot(1:1)'
4. Click 'Evaluate Worksheet'

OBSERVED RESULT
Plotting hangs

EXPECTED RESULT
The plot result appears.

SOFTWARE/OS VERSIONS
Linux: Alt Linux Sisyphus
KDE Plasma Version: 20.12.3
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
--
Linux: Arch Linux
KDE Plasma Version: 20.12.3
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I use gnuplot graphics toolkit.

See also: https://bugs.kde.org/show_bug.cgi?id=433982

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

[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one

[Egor T]

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

Egor T  changed:

   What|Removed |Added

 CC||chem_tom...@mail.ru
 Status|RESOLVED|REOPENED
 Resolution|UPSTREAM|---

--- Comment #70 from Egor T  ---
Kubuntu 20.10, bug still exist. If I set Russian layout to Top in list,
shortcuts stops working (Ctrl+Atl+T, Win+E and other).

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

[kdenlive] [Bug 430227] Changing speed of image sequence does incorrect result (wrong images displayed in wrong time)

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 430227] New: Changing speed of image sequence does incorrect result (wrong images displayed in wrong time)

[Egor]

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

Bug ID: 430227
   Summary: Changing speed of image sequence does incorrect result
(wrong images displayed in wrong time)
   Product: kdenlive
   Version: 20.08.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: e.vakhromt...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Create image sequence with 1 image per frame (timelapse for example)
2. Put part of this image sequence into timeline
3. Change clip speed (on timeline) to 1600%

OBSERVED RESULT
Play the video or render project and you get wrong results - random laggy
images instead of smooth image sequence playback

EXPECTED RESULT
Image sequence played/rendered correctly with increased speed

ADDITIONAL INFORMATION
This short video show all the process and buggy result:
https://youtu.be/x9JtsHdpGCc

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

[kdenlive] [Bug 430225] Cannot add custom effect to clip in project bin

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 430225] New: Cannot add custom effect to clip in project bin

[Egor]

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

Bug ID: 430225
   Summary: Cannot add custom effect to clip in project bin
   Product: kdenlive
   Version: 20.08.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: e.vakhromt...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Add some effects to clip
2. Create custom effect via "Save Effect Stack" menu item
3. Try to drag and drop this new custom effect to clip in project bin.

OBSERVED RESULT
Got an error: "Cannot add effect to clip"

EXPECTED RESULT
Saved effect stack successfully applied to clip in project bin.

ADDITIONAL INFORMATION

New custom effect can be applied to clip in timeline but not on clip in project
bin.

Video with this bug: https://youtu.be/98H8so2lcts

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

[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4

[Egor]

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

Egor  changed:

   What|Removed |Added

 CC||glu...@gmail.com

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

[kdeconnect] [Bug 402683] New: kdeinit5 crashes after hibernation on laptop

[Egor Klenin]

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

Bug ID: 402683
   Summary: kdeinit5 crashes after hibernation on laptop
   Product: kdeconnect
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: e_g1...@mail.ru
  Target Milestone: ---

SUMMARY
After hibernating my laptop, i sometimes get kdeconnect crashed while trying to
 interact with it via SystemTray. 

STEPS TO REPRODUCE
1. Suspend/unsuspend device
2. Click on kdeconnect icon in SystemTray

OBSERVED RESULT
Crash message

EXPECTED RESULT
Everything is fine

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ab0154780 (LWP 16339))]

Thread 3 (Thread 0x7f0aa9de2700 (LWP 16341)):
#0  0x7f0ab3f56804 in __GI___libc_read (nbytes=16, buf=0x7f0aa9de1bd0,
fd=6) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f0ab3f56804 in __GI___libc_read (fd=6, buf=0x7f0aa9de1bd0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f0ab246b180 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0ab242591f in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0ab2425df0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f0ab2425f6c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f0ab42e9d2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0ab4296d0b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0ab40e60c6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0aaf714545 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f0ab40efc97 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f0ab2fc0fa3 in start_thread (arg=) at
pthread_create.c:486
#12 0x7f0ab3f6588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f0aab8dc700 (LWP 16340)):
#0  0x7f0ab3f5abd9 in __GI___poll (fds=0x7f0aab8dbd38, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f0ab4b0ccf7 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0ab4b0e91a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0aac225519 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f0ab40efc97 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0ab2fc0fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f0ab3f6588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f0ab0154780 (LWP 16339)):
[KCrash Handler]
#6  0x7f0aa391d4f4 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/ffmpegthumbs.so
#7  0x7f0aa391f20a in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/ffmpegthumbs.so
#8  0x7f0aa391f359 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/ffmpegthumbs.so
#9  0x7f0aa391c793 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/ffmpegthumbs.so
#10 0x7f0ab4cff9fe in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so
#11 0x7f0aafd62df6 in KIO::SlaveBase::dispatch(int, QByteArray const&) ()
at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#12 0x7f0aafd5e196 in KIO::SlaveBase::dispatchLoop() () at
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#13 0x7f0ab4cfd08d in kdemain () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so
#14 0x55c733c12e1c in  ()
#15 0x55c733c13eea in  ()
#16 0x55c733c148fb in  ()
#17 0x55c733c0f645 in  ()
#18 0x7f0ab3e9009b in __libc_start_main (main=0x55c733c0ec70, argc=5,
argv=0x7ffda1a96118, init=, fini=,
rtld_fini=, stack_end=0x7ffda1a96108) at ../csu/libc-start.c:308
#19 0x55c733c102ca in _start ()
[Inferior 1 (process 16339) detached]

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

[kdevelop] [Bug 321735] «internal error: cannot build a file item» — after opening a project

[Egor]

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

--- Comment #2 from Egor  ---
This bug does not hit me anymore. I beleive, it is fixed.

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

[krita] [Bug 393431] New: Some bugs found by PVS-Studio

[Egor]

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

Bug ID: 393431
   Summary: Some bugs found by PVS-Studio
   Product: krita
   Version: git master
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: bredik...@viva64.com
  Target Milestone: ---

Created attachment 112196
  --> https://bugs.kde.org/attachment.cgi?id=112196=edit
Full analyzer report

Hi! I've checked Krita 4.0 with PVS-Studio static analyzer and found some bugs.
Here are some interesting fragments: https://www.viva64.com/en/b/0569/.
Additionally, I attached full HTML-report for you.

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

[lokalize] [Bug 393081] New: PO-Revision-Date timezone offset doesn't account for DST

[Egor Vladimirovich]

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

Bug ID: 393081
   Summary: PO-Revision-Date timezone offset doesn't account for
DST
   Product: lokalize
   Version: 2.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sha...@ukr.net
  Reporter: e...@opensrc.club
  Target Milestone: ---

When saving a .po file, Lokalize writes current time into the PO-Revision-Date
header field. The time itself is correct, but the timezone is wrong for DST
timezones.

Steps to Reproduce:
1) make sure you're in a DST timezone (in my case it's EEST +0300)
2) save a .po file

Actual Results:
"PO-Revision-Date: 2018-04-13 05:01+0200\n"

Expected Results:
"PO-Revision-Date: 2018-04-13 05:01+0300\n"

Lokalize version: 2.0
Archlinux package version: lokalize 17.12.3-1

Additional Information:
This is not a system configuration problem. timedatectl displays EEST +0300.
git uses the correct timezone offset when saving commits.

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

[kde] [Bug 392779] Cursor doesn't disappear after deselecting QLabel

[Egor Vladimirovich]

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

--- Comment #2 from Egor Vladimirovich <e...@opensrc.club> ---
Created attachment 111865
  --> https://bugs.kde.org/attachment.cgi?id=111865=edit
List of Qt/KDE-related package versions on my laptop

Reproduced on my laptop. I haven't updated it for a few days, so it has older
frameworks (5.43.0), same version of qt, but older arch package release, and
older dolphin (17.12.2). I don't have plasma installed there.

Attached is the list of packaged on my laptop, made with the same command as
before.

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

[kde] [Bug 392779] Cursor doesn't disappear after deselecting QLabel

[Egor Vladimirovich]

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

--- Comment #1 from Egor Vladimirovich <e...@opensrc.club> ---
Created attachment 111862
  --> https://bugs.kde.org/attachment.cgi?id=111862=edit
List of Qt/KDE related package versions on my PC

Output of the following command as run on my PC
pacman -Q $(pacman -Qgq plasma) $(pacman -Qgq kf5) $(pacman -Qgq qt5) dolphin

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

[kde] [Bug 392779] New: Cursor doesn't disappear after deselecting QLabel

[Egor Vladimirovich]

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

Bug ID: 392779
   Summary: Cursor doesn't disappear after deselecting QLabel
   Product: kde
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: e...@opensrc.club
  Target Milestone: ---

Created attachment 111861
  --> https://bugs.kde.org/attachment.cgi?id=111861=edit
Screenshot of the bug, as it appears in Dolphin

When you change focus from a selectable QLabel (that is, a QLabel with
TextSelectableByKeyboard and TextSelectableByMouse interaction flags set), the
text cursor doesn't disappear. You can click back on the label, and it will
change the position of cursor as intended, but clicking on anything else won't
remove the cursor.

Steps to reproduce:
1) right click on any file in Dolphin
2) click Properties
3) on General tab, click anywhere inside Location field (make sure you don't
select any characters)
4) click the edit control on the top (the one with file name)

Actual Results:
The text cursor in Location field didn't disappear

Expected Results:
The cursor should disappear

Versions:
KDE Plasma Version: 5.12.4
KDE Frameworks Version: 5.44.0
Qt Version: 5.10.1
Kernel Version: 4.15.14-1-ARCH
Dolphin Version: 17.12.3

Additional Information:
This bug only occurs if nothing is selected. If at least one character is
selected, both the cursor and the highlight of the selected characters
disappear as intended.

This doesn't seem like a Dolphin bug. I made a Qt form with multiple QLabels,
and after clicking on each label, all of them had a text cursor.

This also doesn't look like a glitch, it's very consistent in how it works, and
it doesn't disappear on its own.

I should also note that the cursors (both the "real" one as well as the
"shadow" ones) don't blink. Not sure if they are supposed to blink or not, as I
don't remember how it's supposed to be. The cursor in the line edit widget
blinks correctly.

Things I tried:
- Changing window decorations and widget styles
- Disabling compositor (Shift+Alt+F12)
- Rebooting

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

[kdenlive] [Bug 387609] Icons, text and buttons are very small on 4k HiDPI monitors + non-KDE desktop environments

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 390496] HIDPI display, using KDE scaling factor 1.3x, can't move clips in the timeline

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 380044] speed effect - timeline and add clip bugs

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 388558] "Fade to/from Black" + "Speed" effects cause "Fade to/from Black" duplicates and change parameter values

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 388729] 17.12 - Duplicate clip with speed change not doing slowmotion

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 369585] Timeline corruption due to speed effect

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 385780] Speed Effect is not saved after editing

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[kdenlive] [Bug 385542] Clips with Speed effect reset when moved back with other clips

[Egor]

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

Egor <e.vakhromt...@gmail.com> changed:

   What|Removed |Added

 CC||e.vakhromt...@gmail.com

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

[plasmashell] [Bug 387128] Memory leak in plasmashell with persistent notifications

[Egor Y . Egorov]

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

Egor Y. Egorov <egorov_e...@bk.ru> changed:

   What|Removed |Added

 CC||egorov_e...@bk.ru

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

[kdialog] [Bug 382437] Regression in kdialog causes wrong file extension

[Egor Y . Egorov]

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

Egor Y. Egorov <egorov_e...@bk.ru> changed:

   What|Removed |Added

 CC||egorov_e...@bk.ru

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

[Discover] [Bug 384263] New: Crash to run plasma-discover

[Egor]

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

Bug ID: 384263
   Summary: Crash to run plasma-discover
   Product: Discover
   Version: 5.10.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: elfimov8...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Application: Центр приложений Discover (plasma-discover), signal: Segmentation
fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff0f3356e40 (LWP 2872))]

Thread 10 (Thread 0x7ff0b9d2f700 (LWP 2889)):
#0  0x7ff0eea41029 in syscall () at /usr/lib/libc.so.6
#1  0x7ff0eed8e0e7 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*)
(g=0x7ff0ed9fd168) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/guard.cc:302
#2  0x7ff0ed74f94d in  () at /usr/lib/libQt5Network.so.5
#3  0x7ff0ed74246c in  () at /usr/lib/libQt5Network.so.5
#4  0x7ff0ef12e341 in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff0ef13215b in  () at /usr/lib/libQt5Core.so.5
#6  0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff0e04cf700 (LWP 2888)):
#0  0x7ff0eea41029 in syscall () at /usr/lib/libc.so.6
#1  0x7ff0eed8e0e7 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*)
(g=0x7ff0ed9fd168) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/guard.cc:302
#2  0x7ff0ed74f94d in  () at /usr/lib/libQt5Network.so.5
#3  0x7ff0ed74246c in  () at /usr/lib/libQt5Network.so.5
#4  0x7ff0ef12e341 in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff0ef13215b in  () at /usr/lib/libQt5Core.so.5
#6  0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff0ba530700 (LWP 2882)):
[KCrash Handler]
#5  0x7ff0f318b8e8 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2
#6  0x7ff0f3193813 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#7  0x7ff0eea7fe44 in _dl_catch_error () at /usr/lib/libc.so.6
#8  0x7ff0f319315a in _dl_open () at /lib64/ld-linux-x86-64.so.2
#9  0x7ff0e936eea6 in  () at /usr/lib/libdl.so.2
#10 0x7ff0eea7fe44 in _dl_catch_error () at /usr/lib/libc.so.6
#11 0x7ff0e936f5a7 in  () at /usr/lib/libdl.so.2
#12 0x7ff0e936ef42 in dlopen () at /usr/lib/libdl.so.2
#13 0x7ff0ef31172e in  () at /usr/lib/libQt5Core.so.5
#14 0x7ff0ef30af89 in QLibrary::load() () at /usr/lib/libQt5Core.so.5
#15 0x7ff0ed74f349 in  () at /usr/lib/libQt5Network.so.5
#16 0x7ff0ed74f95a in  () at /usr/lib/libQt5Network.so.5
#17 0x7ff0ed74246c in  () at /usr/lib/libQt5Network.so.5
#18 0x7ff0ef12e341 in  () at /usr/lib/libQt5Core.so.5
#19 0x7ff0ef13215b in  () at /usr/lib/libQt5Core.so.5
#20 0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0
#21 0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff0bad31700 (LWP 2881)):
#0  0x7ff0e90eaa84 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7ff0e90a5d26 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7ff0ef370084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7ff0ef313ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7ff0ef12d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7ff0ef13215b in  () at /usr/lib/libQt5Core.so.5
#6  0x7ff0eb283049 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7ff0eea45f0f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7ff0bbbd2700 (LWP 2880)):
#0  0x7ffe68be4b52 in clock_gettime ()
#1  0x7ff0eea53546 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7ff0ef36f972 in  () at /usr/lib/libQt5Core.so.5
#3  0x7ff0ef36e10a in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7ff0ef36e6e6 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff0ef36fdcf in  () at /usr/lib/libQt5Core.so.5
#6  0x7ff0e90a5148 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#7  0x7ff0e90a5b3b in  () at /usr/lib/libglib-2.0.so.0
#8  0x7ff0e90a5d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#9  0x7ff0ef370084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#10 0x7ff0ef313ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#11 0x7ff0ef12d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#12 0x7ff0ef13215b in  () at /usr/lib/libQt5Core.so.5
#13 0x7ff0eb283049 in start_thread () at 

[plasmashell] [Bug 383251] New: Crash when scrolling holidays in digital clock widget settings

[Egor Malykh]

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

Bug ID: 383251
   Summary: Crash when scrolling holidays in digital clock widget
settings
   Product: plasmashell
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: f...@fea.st
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
- Opened digital clock widget settings
- Opened the holidays tab
- Scrolled to r letter
- Crash

The crash does not seem to be reproducible.

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

Thread 18 (Thread 0x7f970bfff700 (LWP 2379)):
#0  0x7f9810f4ca84 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9810f07bc6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9810f07d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9816f24084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9816ec7ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9816ce140e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9816ce615b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9815ead049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f98165f9f0f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f973a02d700 (LWP 2377)):
#0  0x7f98165efe9d in poll () at /usr/lib/libc.so.6
#1  0x7f9810f07c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9810f07d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9816f24084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9816ec7ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9816ce140e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9819e6a1d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f9816ce615b in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9815ead049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f98165f9f0f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f9717fff700 (LWP 1977)):
#0  0x7f9815eb31ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9816ce75ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97644723cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97644772b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f9764471913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f9764477312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9764471913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f9764474b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f9816ce615b in  () at /usr/lib/libQt5Core.so.5
#9  0x7f9815ead049 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f98165f9f0f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f9734a00700 (LWP 1976)):
#0  0x7f9815eb31ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9816ce75ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97644723cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97644772b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f9764471913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f9764477312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9764471913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f9764474b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f9816ce615b in  () at /usr/lib/libQt5Core.so.5
#9  0x7f9815ead049 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f98165f9f0f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f97364c3700 (LWP 1975)):
#0  0x7f9815eb31ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9816ce75ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  

[QtCurve] [Bug 359209] pop-up menu opacity broken

[Egor Y . Egorov]

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

--- Comment #5 from Egor Y. Egorov <egorov_e...@bk.ru> ---
reproduced on current master

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

[QtCurve] [Bug 382182] kdialog crached when called from google-chrome in qtcurve

[Egor Y . Egorov]

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

Egor Y. Egorov <egorov_e...@bk.ru> changed:

   What|Removed |Added

 CC||rjvber...@gmail.com

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

[QtCurve] [Bug 382182] kdialog crached when called from google-chrome in qtcurve

[Egor Y . Egorov]

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

--- Comment #1 from Egor Y. Egorov <egorov_e...@bk.ru> ---
This problem is subject to master and 1.9 branches

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

[QtCurve] [Bug 382182] New: kdialog crached when called from google-chrome in qtcurve

[Egor Y . Egorov]

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

Bug ID: 382182
   Summary: kdialog crached when called from google-chrome in
qtcurve
   Product: QtCurve
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: qt5
  Assignee: yyc1...@gmail.com
  Reporter: egorov_e...@bk.ru
CC: h...@kde.org
  Target Milestone: ---

bt:

pplication: kdialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a0bc4f880 (LWP 10918))]

Thread 2 (Thread 0x7f7a0b5c3700 (LWP 10923)):
#0  0x0035d16de72d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x0035d620c8f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x0035d620e6f7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f7a0b80fe87 in QXcbEventReader::run (this=0x20b96d0) at
qxcbconnection.cpp:1343
#4  0x003a5a8bda30 in QThreadPrivate::start (arg=0x20b96d0) at
thread/qthread_unix.cpp:368
#5  0x0035d1a073b4 in start_thread (arg=0x7f7a0b5c3700) at
pthread_create.c:333
#6  0x0035d16e776d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f7a0bc4f880 (LWP 10918)):
[KCrash Handler]
#6  0x003a5a8b1dc9 in
std::__atomic_base::compare_exchange_strong
(__m2=std::memory_order_acquire, __m1=std::memory_order_acquire, __p2=0x1,
__p1=@0x7ffdc847e540: 0x0, this=0x20) at
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/bits/atomic_base.h:752
#7  std::atomic::compare_exchange_strong (this=0x20,
__p1=@0x7ffdc847e540: 0x0, __p2=0x1, __m=std::memory_order_acquire) at
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/atomic:475
#8  0x003a5a8b1bcc in
QAtomicOps::testAndSetAcquire (_q_value=...,
expectedValue=0x0, newValue=0x1, currentValue=0x7ffdc847e5d0) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290
#9  0x003a5a8b1aa2 in QBasicAtomicPointer::testAndSetAcquire
(this=0x20, expectedValue=0x0, newValue=0x1, currentValue=@0x7ffdc847e5d0: 0x5)
at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:259
#10 0x003a5a8b178b in QBasicMutex::fastTryLock (this=0x20,
current=@0x7ffdc847e5d0: 0x5) at thread/qmutex.h:89
#11 0x003a5a8b1142 in QMutex::lock (this=0x20) at thread/qmutex.cpp:225
#12 0x003a5ae15aaf in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x003a5ae16b5a in QDBusConnection::sessionBus() () from
/usr/lib64/libQt5DBus.so.5
#14 0x7f7a0a6ad806 in QtCurve::Style::disconnectDBus (this=0x2114920) at
/var/tmp/portage/x11-themes/qtcurve--r1/work/qtcurve-/qt5/style/qtcurve.cpp:705
#15 0x7f7a0a6adddf in QtCurve::Style::~Style (this=0x2114920,
__in_chrg=) at
/var/tmp/portage/x11-themes/qtcurve--r1/work/qtcurve-/qt5/style/qtcurve.cpp:737
#16 0x7f7a0a6adfb6 in QtCurve::Style::~Style (this=0x2114920,
__in_chrg=) at
/var/tmp/portage/x11-themes/qtcurve--r1/work/qtcurve-/qt5/style/qtcurve.cpp:745
#17 0x7f7a0a70fa06 in QtCurve::StylePlugin::~StylePlugin (this=0x20f3940,
__in_chrg=) at
/var/tmp/portage/x11-themes/qtcurve--r1/work/qtcurve-/qt5/style/qtcurve_plugin.cpp:158
#18 0x7f7a0a70fa8e in QtCurve::StylePlugin::~StylePlugin (this=0x20f3940,
__in_chrg=) at
/var/tmp/portage/x11-themes/qtcurve--r1/work/qtcurve-/qt5/style/qtcurve_plugin.cpp:165
#19 0x003a5aadc4f2 in QLibraryPrivate::unload (this=0x20fa670,
flag=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:562
#20 0x003a5aad454b in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x20fa930, __in_chrg=) at plugin/qfactoryloader.cpp:86
#21 0x003a5aad4604 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x20fa930, __in_chrg=) at plugin/qfactoryloader.cpp:89
#22 0x003a5ab2e35a in QScopedPointerDeleter::cleanup
(pointer=0x20fa930) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#23 0x003a5ab2cc2d in QScopedPointer::~QScopedPointer (this=0x3a5ce19d08
<(anonymous namespace)::Q_QGS_loader::innerFunction()::holder+8>,
__in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#24 0x003a5ab22d8d in QObject::~QObject (this=0x3a5ce19d00 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder>, __in_chrg=)
at kernel/qobject.cpp:900
#25 0x003a5aad5519 in QFactoryLoader::~QFactoryLoader (this=0x3a5ce19d00
<(anonymous namespace)::Q_QGS_loader::innerFunction()::holder>,
__in_chrg=) at plugin/qfactoryloader.cpp:207
#26 0x003a5c804370 in (anonymous namespace)::Q_QGS_loader::Holder::~Holder
(this=0x3a5ce19d00 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder>, __in_chrg=)
at styles/qstylefactory.cpp:72
#27 0x0035d1635aa8 in __run_exit_handlers (status=0, listp=0x35d19935d8
<__exit_funcs>, 

[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style

[Egor Y . Egorov]

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

--- Comment #55 from Egor Y. Egorov <egorov_e...@bk.ru> ---
Yes, you are right. Current master without this patch crached too.
I'll open new issue...

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

[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style

[Egor Y . Egorov]

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

--- Comment #53 from Egor Y. Egorov <egorov_e...@bk.ru> ---
Hm. Now when I press CTRL+O in chome kdialog has craching with

Application: kdialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f82aa1b8840 (LWP 7786))]

Thread 2 (Thread 0x7f82a8097700 (LWP 7787)):
#0  0x7f82b6f6872d in poll () from /lib64/libc.so.6
#1  0x7f82b45c78f2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f82b45c96f7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f82a9dc9c69 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f82b76c0e3c in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f82b300f3b4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f82b6f7176d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f82aa1b8840 (LWP 7786)):
[KCrash Handler]
#6  0x7f82b76b9454 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#7  0x7f82baa39aaf in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7f82baa3ab5a in QDBusConnection::sessionBus() () from
/usr/lib64/libQt5DBus.so.5
#9  0x7f82a6d0fd60 in ?? () from /usr/lib64/qt5/plugins/styles/qtcurve.so
#10 0x7f82a6d15c70 in ?? () from /usr/lib64/qt5/plugins/styles/qtcurve.so
#11 0x7f82a6d15d49 in ?? () from /usr/lib64/qt5/plugins/styles/qtcurve.so
#12 0x7f82a6d478cb in ?? () from /usr/lib64/qt5/plugins/styles/qtcurve.so
#13 0x7f82a6d479e9 in ?? () from /usr/lib64/qt5/plugins/styles/qtcurve.so
#14 0x7f82b784c993 in ?? () from /usr/lib64/libQt5Core.so.5
#15 0x7f82b7843782 in ?? () from /usr/lib64/libQt5Core.so.5
#16 0x7f82b78438a9 in ?? () from /usr/lib64/libQt5Core.so.5
#17 0x7f82b7882221 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#18 0x7f82b7842cba in QFactoryLoader::~QFactoryLoader() () from
/usr/lib64/libQt5Core.so.5
#19 0x7f82b80f71a9 in ?? () from /usr/lib64/libQt5Widgets.so.5
#20 0x7f82b6ebfaa8 in ?? () from /lib64/libc.so.6
#21 0x7f82b6ebfaf5 in exit () from /lib64/libc.so.6
#22 0x7f82b76cc263 in QCommandLineParser::showVersion() () from
/usr/lib64/libQt5Core.so.5
#23 0x7f82b76ce97b in QCommandLineParser::process(QStringList const&) ()
from /usr/lib64/libQt5Core.so.5
#24 0x0040bcc4 in ?? ()
#25 0x7f82b6eaa670 in __libc_start_main () from /lib64/libc.so.6
#26 0x00410029 in _start ()

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

[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style

[Egor Y . Egorov]

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

Egor Y. Egorov <egorov_e...@bk.ru> changed:

   What|Removed |Added

 CC||egorov_e...@bk.ru

--- Comment #51 from Egor Y. Egorov <egorov_e...@bk.ru> ---
(In reply to RJVB from comment #39)
> (In reply to RJVB from comment #36)
> > Created attachment 103308 [details]
> > translucent/rounded menus patch MkII
> 
> Yichao, what do you think, can I commit this patch?

This patch solve the https://bugs.kde.org/show_bug.cgi?id=368672
Thanks for your job!

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

[QtCurve] [Bug 368672] kdialog hangs on popup menu when using qtcurve with menu opacity less then 100

[Egor Y . Egorov]

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

--- Comment #7 from Egor Y. Egorov <egorov_e...@bk.ru> ---
Oh, this patch works for me
https://bugs.kde.org/show_bug.cgi?id=374224#c39

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

[QtCurve] [Bug 368672] kdialog hangs on popup menu when using qtcurve with menu opacity less then 100

[Egor Y . Egorov]

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

--- Comment #6 from Egor Y. Egorov <egorov_e...@bk.ru> ---
Created attachment 106479
  --> https://bugs.kde.org/attachment.cgi?id=106479=edit
backtrace of kdialog when it hangs

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