[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com --- Comment #2 from Grzegorz --- Created attachment 149270 --> https://bugs.kde.org/attachment.cgi?id=149270&action=edit shrinked window After disconnect the external screens from my laptop, often all windows will be reduced in length. The linked screens are above the laptop (in display settings too) ArchLinux Plasma: 5.24.5 Framework: 5.94.0 Qt: 5.15.4 I guess this happened after updating framework version to 5.93.0 or qt to 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #3 from Grzegorz --- I'm using plasma on x11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #5 from Grzegorz --- Created attachment 149380 --> https://bugs.kde.org/attachment.cgi?id=149380&action=edit screen layout my screen layout -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #6 from Grzegorz --- main screen is laptop screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #8 from Grzegorz --- I have this problem sometimes :/ I am trying to find a rule so that I can always trigger it -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"
https://bugs.kde.org/show_bug.cgi?id=454948 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #10 from Grzegorz --- Peter, maybe you are able to reproduce this problem? recently this problem has occurred when docking laptop to station which have connected two external monitor (above in settings) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 Grzegorz changed: What|Removed |Added Version|5.24.4 |5.25.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 Grzegorz changed: What|Removed |Added Version|5.25.0 |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #11 from Grzegorz --- same here -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397132] Windows may get horizontally squashed when switching screens through kwin's context menu or when connecting a new screen
https://bugs.kde.org/show_bug.cgi?id=397132 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466467] Frameworks 5.103: wireless extensions that are deprecated for modern drivers; use nl80211
https://bugs.kde.org/show_bug.cgi?id=466467 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445746] New: IMAP Account crashing
https://bugs.kde.org/show_bug.cgi?id=445746
Bug ID: 445746
Summary: IMAP Account crashing
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: IMAP resource
Assignee: kdepim-b...@kde.org
Reporter: bibliotekar...@gmail.com
Target Milestone: ---
Application: akonadi_imap_resource (5.18.3 (21.08.3))
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.14.14-3-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- Custom settings of the application:
I think it might have crashed during applying filters to mail.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Służbowa (akonadi_imap_resource), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f680b7438e3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f680b6f66f6 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f680b6e07b3 in __GI_abort () at abort.c:79
#10 0x7f680b9819b6 in __gnu_cxx::__verbose_terminate_handler() () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x7f680b98d19c in __cxxabiv1::__terminate(void (*)())
(handler=) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#12 0x7f680b98d207 in std::terminate() () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
#13 0x7f680b98d4fd in __cxxabiv1::__cxa_rethrow() () at
../../../../libstdc++-v3/libsupc++/eh_throw.cc:133
#14 0x560a3309dedc in QVector::realloc(int,
QFlags) (this=0x7fff3cdb6dc0, aalloc=, options=...) at /usr/include/qt5/QtCore/qvector.h:734
#15 0x560a330bce38 in QVector::append(long long const&)
(this=0x7fff3cdb6dc0, t=) at
/usr/include/qt5/QtCore/qvector.h:784
#16 0x560a330f95b3 in QVector::operator<<(long long const&)
(t=@0x7fff3cdb6d60: 268435452, this=0x7fff3cdb6dc0) at
/usr/include/qt5/QtCore/qvector.h:293
#17 MoveItemsTask::imapSetToList(KIMAP::ImapSet const&) [clone .constprop.0]
(set=..., this=) at
/usr/src/debug/kdepim-runtime-21.08.3-1.1.x86_64/resources/imap/moveitemstask.cpp:348
#18 0x560a330d55a0 in MoveItemsTask::onMoveDone(KJob*)
(this=0x560a347238a0, job=0x560a347258d0) at
/usr/src/debug/kdepim-runtime-21.08.3-1.1.x86_64/resources/imap/moveitemstask.cpp:171
#19 0x7f680be02043 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff3cdb6f10, r=0x560a347238a0, this=0x560a34660ff0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x560a347258d0,
signal_index=6, argv=0x7fff3cdb6f10) at kernel/qobject.cpp:3886
#21 0x7f680bdfb50f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x560a347258d0, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff3cdb6f10)
at kernel/qobject.cpp:3946
#22 0x7f680d430c7c in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x560a347258d0, _t1=, _t1@entry=0x560a347258d0,
_t2=...) at
/usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#23 0x7f680d43501b in KJob::finishJob(bool) (this=0x560a347258d0,
emitResult=) at
/usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/src/lib/jobs/kjob.cpp:98
#24 0x7f680d435c6a in KJob::emitResult() (this=) at
/usr/src/debug/kcoreaddons-5.88.0-1.1.x86_64/src/lib/jobs/kjob.cpp:337
#25 0x7f680da363cb in KIMAP::Job::handleErrorReplies(KIMAP::Response
const&) (this=0x560a347258d0, response=...) at
/usr/src/debug/kimap-21.08.3-1.1.x86_64/src/job.cpp:72
#26 0x7f680da471b5 in
KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&)
(this=0x560a346ed100, response=...) at
/usr/src/debug/kimap-21.08.3-1.1.x86_64/src/session.cpp:288
#27 0x7f680bdf7fee in QObject::event(QEvent*) (this=0x560a346ed100,
e=0x7f67e8051720) at kernel/qobject.cpp:1314
#28 0x7f680ca6fa7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x560a346ed100, e=0x7f67e8051720) at
kernel/qapplication.cpp:3632
#29 0x7f680bdcb9fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x560a346ed100, event=0x7f67e8051720) at
kernel/qcoreapplication.cpp:1064
#30 0x7f680bdcea47 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x560a34537090) at
kernel/qcoreapplication.cpp:1821
#31 0x7f680be23853 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=s@entry=0x560a346294b0) at kernel/qeventdispatcher_glib.cpp:277
#32 0x7f680ad1bd4f in g_main_dispatch (context=0x7f685000) at
../glib/gmain.c:
[plasma-pa] [Bug 446162] New: bad ui on applets
https://bugs.kde.org/show_bug.cgi?id=446162 Bug ID: 446162 Summary: bad ui on applets Product: plasma-pa Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: grzegorz.alibo...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143997 --> https://bugs.kde.org/attachment.cgi?id=143997&action=edit volume applet SUMMARY Volume, network and many other applets has bad scroll ui, slider SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2+kde -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417523] "More options..." button of vertical Panel is hidden if I also have an always visible horizontal Panel on bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=417523 --- Comment #11 from Grzegorz --- I can confirm it fixed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 Grzegorz changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #13 from Grzegorz --- (In reply to Nate Graham from comment #7) > Thanks. > > 1. Can you make the top-left screen primary and try again? unchanged, problem persists > 2. Can you try the Wayland session and see if the same thing happens there? I was unable to reproduce the problem on wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454425] Windows are resized to a minimal height if I unplug external monitors
https://bugs.kde.org/show_bug.cgi?id=454425 --- Comment #14 from Grzegorz --- looks from duplicate to https://bugs.kde.org/show_bug.cgi?id=452118 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 440290] New: Bad status after resume in cellular network
https://bugs.kde.org/show_bug.cgi?id=440290 Bug ID: 440290 Summary: Bad status after resume in cellular network Product: plasma-nm Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 140337 --> https://bugs.kde.org/attachment.cgi?id=140337&action=edit status SUMMARY Applet show bad cellular network status after wakeup from suspend STEPS TO REPRODUCE 1. Enable mobile network 2. Suspend 3. Wakeup 4. Applet show bad status OBSERVED RESULT The applet shows the disabled status even though the lte modem is enabled and you can see the connection with T-Mobile EXPECTED RESULT The applet should show enabled status SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440379] New: Some config options are not accessible if panel is on right edge of screen
https://bugs.kde.org/show_bug.cgi?id=440379 Bug ID: 440379 Summary: Some config options are not accessible if panel is on right edge of screen Product: plasmashell Version: 5.22.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bibliotekar...@gmail.com Target Milestone: 1.0 Created attachment 140384 --> https://bugs.kde.org/attachment.cgi?id=140384&action=edit Cut settings SUMMARY I have set custom empty panel on right edge of screen. If I try to edit panel the last button is hidden under bottom panel STEPS TO REPRODUCE 1. Add adinational panel 2. Move it to left side of screen 3. try to edit its settings OBSERVED RESULT Last part of panel settings goes under bottom panel- see attachment EXPECTED RESULT It does stop at edge of panel, not the edge of screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20210726 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It can be mitigated by moving panel to top and changing setting there before moving it back. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438857] New: KDE Connect Crashing
https://bugs.kde.org/show_bug.cgi?id=438857 Bug ID: 438857 Summary: KDE Connect Crashing Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: bibliotekar...@gmail.com Target Milestone: --- Application: kdeconnectd (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.10-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Application was not connecting to phone despite firewall disabled (ping also were passing). I renamed ~/.config/kdeconnectd and tried with fresh config- resulting in this crash. It persist after reboots. The crash can be reproduced every time. -- Backtrace: Application: Usługa KDE Connect (kdeconnectd), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f764910d340 (LWP 1492))] [KCrash Handler] #6 QCA::Certificate::Certificate (this=, opts=..., key=..., provider=..., this=, opts=..., key=..., provider=...) at /usr/src/debug/qca-qt5-2.3.3-1.1.x86_64/src/qca_cert.cpp:1466 #7 0x7f764cebb681 in KdeConnectConfig::generateCertificate (this=this@entry=0x7f764ced9df0 , certPath=...) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:347 #8 0x7f764cebbbfc in KdeConnectConfig::loadCertificate (this=this@entry=0x7f764ced9df0 ) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:287 #9 0x7f764cebc01c in KdeConnectConfig::KdeConnectConfig (this=, this=) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:92 #10 0x7f764cebc1d5 in KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #11 KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #12 0x7f764cebf2b2 in Daemon::init (this=0x7fffc22cbc00) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/daemon.cpp:89 #13 0x7f764b94109e in QObject::event (this=0x7fffc22cbc00, e=0x55ab797bf130) at kernel/qobject.cpp:1314 #14 0x7f764c564a5f in QApplicationPrivate::notify_helper (this=, receiver=0x7fffc22cbc00, e=0x55ab797bf130) at kernel/qapplication.cpp:3632 #15 0x7f764b914aaa in QCoreApplication::notifyInternal2 (receiver=0x7fffc22cbc00, event=0x55ab797bf130) at kernel/qcoreapplication.cpp:1063 #16 0x7f764b917af7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55ab796b0380) at kernel/qcoreapplication.cpp:1817 #17 0x7f764b96ca73 in postEventSourceDispatch (s=s@entry=0x55ab79783350) at kernel/qeventdispatcher_glib.cpp:277 #18 0x7f7649eb880f in g_main_dispatch (context=0x7f7640005000) at ../glib/gmain.c:3337 #19 g_main_context_dispatch (context=0x7f7640005000) at ../glib/gmain.c:4055 #20 0x7f7649eb8b98 in g_main_context_iterate (context=context@entry=0x7f7640005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #21 0x7f7649eb8c4f in g_main_context_iteration (context=0x7f7640005000, may_block=1) at ../glib/gmain.c:4196 #22 0x7f764b96c0f4 in QEventDispatcherGlib::processEvents (this=0x55ab797868a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x7f764b9134bb in QEventLoop::exec (this=this@entry=0x7fffc22cbaf0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x7f764b91b790 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x7f764bd721fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #26 0x7f764c5649d5 in QApplication::exec () at kernel/qapplication.cpp:2824 #27 0x55ab78096a47 in main (argc=, argv=0x7fffc22cbba0) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/daemon/kdeconnectd.cpp:174 [Inferior 1 (process 1492) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427864] New: Dark breeze popup titile bar - bad color
https://bugs.kde.org/show_bug.cgi?id=427864 Bug ID: 427864 Summary: Dark breeze popup titile bar - bad color Product: Breeze Version: 5.20.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 132472 --> https://bugs.kde.org/attachment.cgi?id=132472&action=edit popup SUMMARY on breeze dark I have bad color in title bar in popup (attachment) after upgrade to 5.20.0 SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.0 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427864] Dark breeze popup titile bar - bad color
https://bugs.kde.org/show_bug.cgi?id=427864 --- Comment #1 from Grzegorz --- after upgrade from 5.19.5 to 5.20.0, this problem appears after second reboot. on new account problem doesent appears, but i try remove my all config files from ~/.config in main account and set everything manualy one more time, it was ok, but after reboot the problem again appeared -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427864] Dark breeze popup titile bar - bad color
https://bugs.kde.org/show_bug.cgi?id=427864 --- Comment #3 from Grzegorz --- Yes, for now I'm using framework 5.75 and plasma 5.20.1 and problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 427864] Dark breeze popup titile bar - bad color
https://bugs.kde.org/show_bug.cgi?id=427864 --- Comment #4 from Grzegorz --- Dark breeze + color scheme breeze -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435321] New: [openvpn] support for sha3 in auth
https://bugs.kde.org/show_bug.cgi?id=435321 Bug ID: 435321 Summary: [openvpn] support for sha3 in auth Product: plasma-nm Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: task Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- SUMMARY Please add support in openvpn for SHA3-384/SHA3-512 in auth to list vpn.data: auth = SHA3-384 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428655] New: Battery Monitor says the power source is not strong enough when ac-adapter is unplugged
https://bugs.kde.org/show_bug.cgi?id=428655 Bug ID: 428655 Summary: Battery Monitor says the power source is not strong enough when ac-adapter is unplugged Product: plasmashell Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: grzegorz.alibo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132998 --> https://bugs.kde.org/attachment.cgi?id=132998&action=edit battery-screenshot SUMMARY After unplug ac-adapter/undock from station battery widget says "the power source is not strong enough to charge the battery" STEPS TO REPRODUCE 1. plug ac-adapter 2. unplug ac-adapter EXPECTED RESULT battery widget show discharging state SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION % acpi -V Battery 0: Discharging, 97%, 06:00:54 remaining Battery 0: design capacity 4512 mAh, last full capacity 3671 mAh = 81% Adapter 0: off-line Thermal 0: ok, 39.0 degrees C Thermal 0: trip point 0 switches to mode critical at temperature 128.0 degrees C Cooling 0: Processor 0 of 10 Cooling 1: pch_skylake no state information available Cooling 2: Processor 0 of 10 Cooling 3: iwlwifi_1 no state information available Cooling 4: Processor 0 of 10 Cooling 5: Processor 0 of 10 Cooling 6: INT3400 Thermal no state information available Cooling 7: Processor 0 of 10 Cooling 8: B0D4 no state information available Cooling 9: Processor 0 of 10 Cooling 10: x86_pkg_temp no state information available Cooling 11: Processor 0 of 10 Cooling 12: intel_powerclamp no state information available Cooling 13: Processor 0 of 10 Cooling 14: SEN1 no state information available -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428655] Battery Monitor says the power source is not strong enough when ac-adapter is unplugged
https://bugs.kde.org/show_bug.cgi?id=428655 --- Comment #1 from Grzegorz --- After wake up from suspend with no connected ac-adapter battery monitor is fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428655] Battery Monitor says the power source is not strong enough when ac-adapter is unplugged
https://bugs.kde.org/show_bug.cgi?id=428655 --- Comment #2 from Grzegorz --- Sorry the propper STEPS TO REPRODUCE: 1. Plugged ac-adapter 2. Suspend laptop 3. Unplug ac-adapter 4. Wake-up from suspend when ac-adapter not connected -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 Grzegorz changed: What|Removed |Added CC||gjes...@gmail.com --- Comment #25 from Grzegorz --- Still not working. Empty window. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 473203] duplicate output device on bluetooth headset reconnect in applet with pipewire-pulse
https://bugs.kde.org/show_bug.cgi?id=473203 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463036] New: Akonadi server crashes on IMAP
https://bugs.kde.org/show_bug.cgi?id=463036 Bug ID: 463036 Summary: Akonadi server crashes on IMAP Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: bibliotekar...@gmail.com Target Milestone: --- Application: akonadi_imap_resource (5.22.0 (22.12.0)) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: All folders in account got red, like being offline, no new mails downloaded. Afrer restarting the IMAP accound using context menu in kmail, akonadi server crashed. Still no new mail. IMAP resiurrce is unable to start, chcking it in akonadiconsole its status is stuck on "move' part of first filter rule. Trying to start it again results in almost immediate crash. Deleting account and restoring its settings from backup resolves the issue temporalily, it breaks around onece or twice per day now. Have tried two different backup versions, in case one was corrupted, but there was no difference. The crash can be reproduced sometimes. -- Backtrace: Application: Służbowa (akonadi_imap_resource), signal: Aborted [KCrash Handler] #4 0x7fee43c957ec in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7fee43c42816 in raise () at /lib64/libc.so.6 #6 0x7fee43c2b81c in abort () at /lib64/libc.so.6 #7 0x7fee43ea9ab5 in () at /lib64/libstdc++.so.6 #8 0x7fee43eb4fcc in () at /lib64/libstdc++.so.6 #9 0x7fee43eb5037 in () at /lib64/libstdc++.so.6 #10 0x7fee43eb52eb in __cxa_rethrow () at /lib64/libstdc++.so.6 #11 0x55b215d415e4 in QVector::realloc(int, QFlags) (this=0x7ffd30b62820, aalloc=, options=...) at /usr/include/qt5/QtCore/qvector.h:734 #12 0x55b215d5d818 in QVector::append(long long const&) (this=0x7ffd30b62820, t=) at /usr/include/qt5/QtCore/qvector.h:784 #13 0x55b215d9c033 in QVector::operator<<(long long const&) (t=@0x7ffd30b627c0: 268435452, this=0x7ffd30b62820) at /usr/include/qt5/QtCore/qvector.h:293 #14 MoveItemsTask::imapSetToList(KIMAP::ImapSet const&) [clone .constprop.0] (set=..., this=) at /usr/src/debug/kdepim-runtime-22.12.0/resources/imap/moveitemstask.cpp:346 #15 0x55b215d76f08 in MoveItemsTask::onMoveDone(KJob*) (this=0x7fee20046210, job=0x55b217ebddd0) at /usr/src/debug/kdepim-runtime-22.12.0/resources/imap/moveitemstask.cpp:169 #16 0x7fee445132cd in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd30b62960, r=0x7fee20046210, this=0x55b217fb7210) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate(QObject*, int, void**) (sender=0x55b217ebddd0, signal_index=6, argv=0x7ffd30b62960) at kernel/qobject.cpp:3919 #18 0x7fee45d69bc5 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #19 0x7fee45d6de2b in KJob::finishJob(bool) () at /lib64/libKF5CoreAddons.so.5 #20 0x7fee463887d8 in KIMAP::Job::handleErrorReplies(KIMAP::Response const&) (this=0x55b217ebddd0, response=...) at /usr/src/debug/kimap-22.12.0/src/job.cpp:72 #21 0x7fee46399975 in KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&) (this=0x7fee380222c0, response=...) at /usr/src/debug/kimap-22.12.0/src/session.cpp:288 #22 0x7fee44507c40 in QObject::event(QEvent*) (this=0x7fee380222c0, e=0x7fee20046640) at kernel/qobject.cpp:1347 #23 0x7fee453a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7fee380222c0, e=0x7fee20046640) at kernel/qapplication.cpp:3637 #24 0x7fee444dc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fee380222c0, event=0x7fee20046640) at kernel/qcoreapplication.cpp:1064 #25 0x7fee444df0c1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55b217c3cf00) at kernel/qcoreapplication.cpp:1821 #26 0x7fee44534353 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55b217d44570) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7fee435d3a90 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #28 0x7fee435d3e48 in () at /lib64/libglib-2.0.so.0 #29 0x7fee435d3edc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #30 0x7fee44533b56 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55b217d45be0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x7fee444dab9b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd30b62eb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #32 0x7fee444e2d06 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/glob
[dolphin] [Bug 463779] New: Is it possible for Dolphin to integrate BTRFS functions in its properties?
https://bugs.kde.org/show_bug.cgi?id=463779 Bug ID: 463779 Summary: Is it possible for Dolphin to integrate BTRFS functions in its properties? Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bibliotekar...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- I'm wondering if BTRFS flags for compression (btrfs properties command) can be integrated into properties window in Dolphin. It would be very nice to see and set up compression for folders without opening console (like it is possible in Windows). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com --- Comment #2 from Grzegorz --- I have the same problem -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463779] Is it possible for Dolphin to integrate BTRFS functions in its properties?
https://bugs.kde.org/show_bug.cgi?id=463779 --- Comment #2 from Grzegorz --- (In reply to Nicolas Fella from comment #1) In my opinion compression is a good candidate. It is something that can be set per folder, so having UI for it makes sense. Most of the other options i know and use are either per filesystem or per subvolume. In my opinion that makes it better to have dedicated UI for them if someone is interested, not in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423332] New: Global menu on wayland in new window
https://bugs.kde.org/show_bug.cgi?id=423332 Bug ID: 423332 Summary: Global menu on wayland in new window Product: kwin Version: 5.19.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 129572 --> https://bugs.kde.org/attachment.cgi?id=129572&action=edit global menu on wayland SUMMARY Global menu appears in new window Linux/KDE Plasma: KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423332] Global menu on wayland in new window
https://bugs.kde.org/show_bug.cgi?id=423332 Grzegorz changed: What|Removed |Added Version|5.19.1 |5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 Grzegorz changed: What|Removed |Added CC||grzegorz.adam...@gmail.com --- Comment #30 from Grzegorz --- I started to experience exactly the same issue, hovewer, in my case I found a way to reproduce it. I commented on that already on Manjaro forum [1] so here's the copy of my findings: >>> I experienced the same issue today i.e. after a reboot my default panel has gone and I could not add it back nor any other panel via the context menu, the desktop wallpaper has reset to the default and my custom key bindings for the default panel have been gone equally. I think I identified it to be related to my dual screen setup. My Lenovo L570 has a UHD 4K display connected via a mini-DP to DP cable. As I used to dual boot with Windows 10 I had the laptop lid open during boot and closed it when the login screen came on. This resulted in a cloned display on both the laptop and the 4K screen with the same low resolution of the laptop screen. After logging in the resolution gets adjusted to 4K and scaling of 150% is applied. Today, however, I restarted from Windows 10 with the lid closed and the boot continued only on the 4K screen. When KDE login screen came up it was in the native 4K resolution without any scaling applied and after logging in my desktop was reset, the default panel gone etc. The same remained after logging out and in again, rebooting and even clearing cache, config files and applying other reset actions I was able to find. Resetting the theme to defaults helped bring the default panel back but it didn't persist the log out/in nor reboot cycle. Very frustrating. Finally, I booted up with the laptop lid open and… bang! my panel was there back again. I repeated the same procedure a few times with the same result: - **reboot with the lid open** and the laptop screen on during the boot and my **desktop and panels persist** - **reboot with the lid closed** and the laptop screen off during the boot and my **desktop panels and wallpaper are gone**. Looks like connected to screen setup detected by KDE. >>> [1]: https://forum.manjaro.org/t/manjaro-kde-taskbar-panel-missing-each-time-i-log-into-account-after-log-off-or-reboot-event/145960/7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423332] Global menu on wayland in new window
https://bugs.kde.org/show_bug.cgi?id=423332 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445746] IMAP Account crashing
https://bugs.kde.org/show_bug.cgi?id=445746 Grzegorz changed: What|Removed |Added CC||bibliotekar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445746] IMAP Account crashing
https://bugs.kde.org/show_bug.cgi?id=445746 --- Comment #1 from Grzegorz --- Created attachment 146261 --> https://bugs.kde.org/attachment.cgi?id=146261&action=edit New crash information added by DrKonqi akonadi_imap_resource (5.19.1 (21.12.1)) using Qt 5.15.2 - What I was doing when the application crashed: Restarting my PC,KMail is set to autostart - Custom settings of the application: Multiple rules for moving mails, In settings there is reference to one of rules (that it is currently moving messages according to rules), but the resource crashes (not always, sometimes restart will fix it, at other times you need to add account again (it works even if i restore a backup of settings made when kmail was broken) -- Backtrace (Reduced): #6 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #7 0x7fdc0f4a12d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #8 0x7fdc0f451356 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #9 0x7fdc0f43a7d3 in __GI_abort () at abort.c:79 #10 0x7fdc0f6ef976 in __gnu_cxx::__verbose_terminate_handler() () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 461831] New: bad radio and silder in sound applet
https://bugs.kde.org/show_bug.cgi?id=461831 Bug ID: 461831 Summary: bad radio and silder in sound applet Classification: Frameworks and Libraries Product: frameworks-kwidgetsaddons Version: 5.100.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: grzegorz.alibo...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 153741 --> https://bugs.kde.org/attachment.cgi?id=153741&action=edit sound applet 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. Upgrade frameworks to 5.100.0 from 5.99.0 OBSERVED RESULT oversized slider and radio button (screenshot) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7+kde -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 461831] oversized radio and slider in sound applet
https://bugs.kde.org/show_bug.cgi?id=461831 Grzegorz changed: What|Removed |Added Summary|bad radio and silder in |oversized radio and slider |sound applet|in sound applet -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 461831] oversized radio and slider in applets
https://bugs.kde.org/show_bug.cgi?id=461831 Grzegorz changed: What|Removed |Added Summary|oversized radio and slider |oversized radio and slider |in sound applet |in applets -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 461831] oversized radio and slider in applets
https://bugs.kde.org/show_bug.cgi?id=461831 --- Comment #1 from Grzegorz --- Created attachment 153746 --> https://bugs.kde.org/attachment.cgi?id=153746&action=edit battery applet other applets too -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 462566] New: Itinerary not running on android for few weeks (builds from binary-factory and F-droid)
https://bugs.kde.org/show_bug.cgi?id=462566 Bug ID: 462566 Summary: Itinerary not running on android for few weeks (builds from binary-factory and F-droid) Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: 92ett...@anonaddy.me Target Milestone: --- Created attachment 154243 --> https://bugs.kde.org/attachment.cgi?id=154243&action=edit Frozen app on logo SUMMARY I have upgraded recently Android version of KDE Itinerary throw f-droid nightly and it stopped loading, but very old version on Google play still works (but does not support Polish railways (PKP)) STEPS TO REPRODUCE 1. Download 22.08.03 (build #601 stable build from factory binary) or 23.03.70 (build #513 from nightly factory-binary) 2. Install app (clean install) 3. App freezez on logo OBSERVED RESULT App freezez on Itinerary logo EXPECTED RESULT App runs and show normal UI SOFTWARE/OS VERSIONS Device: Samsung S22 ultra (exynos version) Android 13 (One UI 5.0) ADDITIONAL INFORMATION I have installed it around 2 months ago and i was still using app with great success aroud 3 weeks ago but i dont rememebr if i had the newest version or not, unfortunatly after updating to the newest nightly version few days ago (i think around 25.11.2022, but im not sure) it broke. I have tried downloding all avaiable apk files from binary-factory (and stable and nighty) and non of them starts up. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411962] konsole crashes when ctrl+shift+w on a frozen ssh session
https://bugs.kde.org/show_bug.cgi?id=411962 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422181] kmail - bad render header
https://bugs.kde.org/show_bug.cgi?id=422181 --- Comment #1 from Grzegorz --- Created attachment 128863 --> https://bugs.kde.org/attachment.cgi?id=128863&action=edit good header -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422181] New: kmail - bad render header
https://bugs.kde.org/show_bug.cgi?id=422181 Bug ID: 422181 Summary: kmail - bad render header Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 128861 --> https://bugs.kde.org/attachment.cgi?id=128861&action=edit bad header After upgrade qt5-webengine to 5.15.0-1 kmail starts to bad rendering headers in message preview Additional info: * qt5-webengine 5.15.0 * kmail 20.04.1-1 STEPS TO REPRODUCE 1. install qt5-webengine 5.15.0 2. run kmail or akregator SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 422183] New: bad ui color in connection editor
https://bugs.kde.org/show_bug.cgi?id=422183 Bug ID: 422183 Summary: bad ui color in connection editor Product: plasma-nm Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 128866 --> https://bugs.kde.org/attachment.cgi?id=128866&action=edit bad color Panel from attachment have bad color in selected area OBSERVED RESULT black color EXPECTED RESULT white color SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422181] kmail - bad render header
https://bugs.kde.org/show_bug.cgi?id=422181 --- Comment #3 from Grzegorz --- (In reply to Laurent Montel from comment #2) > it's a problem against q5.15 > > Install 20.04.2 20.04.2 out at June 11, 2020 you'll provide a link to patch/commit that fix it -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422181] kmail - bad render header
https://bugs.kde.org/show_bug.cgi?id=422181 Grzegorz changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Grzegorz --- similar problem is in akregator on start page is a patch also available? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 422193] New: start page don't display properly with qt 5.15
https://bugs.kde.org/show_bug.cgi?id=422193 Bug ID: 422193 Summary: start page don't display properly with qt 5.15 Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: grzegorz.alibo...@gmail.com Target Milestone: --- Created attachment 128871 --> https://bugs.kde.org/attachment.cgi?id=128871&action=edit start page SUMMARY STEPS TO REPRODUCE 1. upgrade qt5-webengine to 5.15 2. run akregator SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 ADDITIONAL INFORMATION downgrade qt5-webengine version to 5.14.2 fixing problem -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 416184] New: Przeglądarka wyłącza się kiedy zmieniam wolumin dysku z C: na na przykład H: nie widzi potem żadnych woluminów
https://bugs.kde.org/show_bug.cgi?id=416184 Bug ID: 416184 Summary: Przeglądarka wyłącza się kiedy zmieniam wolumin dysku z C: na na przykład H: nie widzi potem żadnych woluminów Product: amarok Version: 2.9.0 Platform: MS Windows OS: MS Windows Status: REPORTED Keywords: investigated Severity: normal Priority: NOR Component: File Browser Assignee: amarok-bugs-d...@kde.org Reporter: mandrag...@gmail.com Target Milestone: kf5 Flags: Translation_missing+, Windows+, ReviewRequest+ SUMMARY Amarok shut sown file brownser STEPS TO REPRODUCE 1. bugzilla 2. learn 3. share OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5 ADDITIONAL INFORMATION : im new -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416549] New: IMAP crashing
https://bugs.kde.org/show_bug.cgi?id=416549 Bug ID: 416549 Summary: IMAP crashing Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: bibliotekar...@gmail.com Target Milestone: --- Application: akonadi_imap_resource (5.13.1 (19.12.1)) Qt Version: 5.13.1 Frameworks Version: 5.66.0 Operating System: Linux 5.4.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Kmail was open on diffrentvirtual desktop - Custom settings of the application: Crashes are irregular, but as far i didn't experienced them when there were no rules set to filter mail The crash can be reproduced sometimes. -- Backtrace: Application: Konto IMAP 13 (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f866d90ef80 (LWP 14410))] Thread 25 (Thread 0x7f86037fe700 (LWP 14436)): #0 0x7f867ee31bdf in poll () at /lib64/libc.so.6 #1 0x7f867b62c2ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f867b62c40f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f867d1e7a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f867d19015b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f867cfc8011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f867cfc9192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f8603fff700 (LWP 14435)): #0 0x7f867ee31bdf in poll () at /lib64/libc.so.6 #1 0x7f867b62c2ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f867b62c40f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f867d1e7a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f867d19015b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f867cfc8011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f867cfc9192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f861d7fa700 (LWP 14432)): #0 0x7f867ee31bdf in poll () at /lib64/libc.so.6 #1 0x7f867b62c2ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f867b62c40f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f867d1e7a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f867d19015b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f867cfc8011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f867cfc9192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f861dffb700 (LWP 14431)): #0 0x7f867c47bb90 in pthread_getspecific () at /lib64/libpthread.so.0 #1 0x7f867b655640 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7f867b62c3ff in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f867d1e7a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f867d19015b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f867cfc8011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f867e3124f6 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f867cfc9192 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #9 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f861e7fc700 (LWP 14430)): #0 0x7f867c47a6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8669a1a05b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f8669a19ec7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f861effd700 (LWP 14429)): #0 0x7f867c47a6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8669a1a05b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f8669a19ec7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f867c473f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f867ee3c4af in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f861f7fe700 (LWP 14428)): #0 0x7f867c47a6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8669a1a05b in () at /usr/lib64/dri/radeonsi_dri
[Akonadi] [Bug 416549] IMAP crashing
https://bugs.kde.org/show_bug.cgi?id=416549 --- Comment #1 from Grzegorz --- I forgot to mention: I have second mail setup in KMail (Gmail account) that hasn't seen single crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411962] konsole crashes when ctrl+shift+w on a frozen ssh session
https://bugs.kde.org/show_bug.cgi?id=411962 --- Comment #2 from Grzegorz --- Created attachment 123961 --> https://bugs.kde.org/attachment.cgi?id=123961&action=edit New crash information added by DrKonqi konsole (19.08.3) using Qt 5.13.2 - What I was doing when the application crashed: if you have a frozen ssh session and close the card with the shortcut ctrl + shift + w, crash occurs -- Backtrace (Reduced): #6 0x7fe7863a217e in QWidget::setFocus(Qt::FocusReason) () from /usr/lib/libQt5Widgets.so.5 [...] #8 0x7fe786f67163 in Konsole::TabbedViewContainer::activeViewChanged(Konsole::TerminalDisplay*) () from /usr/lib/libkonsoleprivate.so.19 #9 0x7fe7870179ed in Konsole::TabbedViewContainer::currentTabChanged(int) () from /usr/lib/libkonsoleprivate.so.19 [...] #11 0x7fe78654146f in QTabWidget::currentChanged(int) () from /usr/lib/libQt5Widgets.so.5 [...] #14 0x7fe78652135f in QTabBar::currentChanged(int) () from /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 304202] No option to re-read metadata from XMP sidecar file
https://bugs.kde.org/show_bug.cgi?id=304202 Grzegorz changed: What|Removed |Added CC||grzegorz.adam...@gmail.com --- Comment #8 from Grzegorz --- In 5.9 rereading metadata form sidecar file works correctly. It reads metadata from darktable for example. I use Item → Reread metadata from image. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] New: Metadata is wiped out from the sidecar file if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 Bug ID: 395914 Summary: Metadata is wiped out from the sidecar file if reading sidecar files is not enabled Product: digikam Version: 5.9.0 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Sidecar Assignee: digikam-bugs-n...@kde.org Reporter: grzegorz.adam...@gmail.com Target Milestone: --- digiKam replaces existing sidecar file (at least for CR2), resulting in loosing existing information, if "Read from sidecar files" option is not enabled (Configure→Metadata→Sidecars). This is unexpected given the option name. If that's a feature not a bug at least a warning should be displayed that existing sidecar will be replaced or wiped. The expected effect of the option would be to preserve existing sidecar file with all information on writing and skipping it on reading. At least that's what the option name implies. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 Grzegorz changed: What|Removed |Added Summary|Metadata is wiped out from |Sidecar files are replaced |the sidecar file if reading |if reading sidecar files is |sidecar files is not|not enabled |enabled | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395915] New: Option to set metadata namespaces to be written for caption (and others)
https://bugs.kde.org/show_bug.cgi?id=395915 Bug ID: 395915 Summary: Option to set metadata namespaces to be written for caption (and others) Product: digikam Version: 5.9.0 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Sidecar Assignee: digikam-bugs-n...@kde.org Reporter: grzegorz.adam...@gmail.com Target Milestone: --- There are already options for selectively write (and read) metadata in selected namespaces for comment (description), tags and rating. Such an option is missing for caption, which is written in all available namespaces. It should be possible to limit that one similarly. Specifically, I want to preserve the 'dc' namespace only. The same should be possible for image information metadata, which is written to sidecar files. digiKam writes a bunch of exif and tiff namespace parameters, which I find unnecessary as they can always be read from a raw file. An option to exclude those namespaces would be handy as well. Of course, excluding exif should not disable writing GPS coordinates if they are set. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 --- Comment #2 from Grzegorz --- Created attachment 113592 --> https://bugs.kde.org/attachment.cgi?id=113592&action=edit darktable XMP The source XMP coming from darktable containing processing history -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 --- Comment #3 from Grzegorz --- Created attachment 113593 --> https://bugs.kde.org/attachment.cgi?id=113593&action=edit digiKam XMP with Read from sidecar files enabled The darktable XMP after updating from digiKam with the "Read from sidecar files" option enabled -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 --- Comment #4 from Grzegorz --- Created attachment 113594 --> https://bugs.kde.org/attachment.cgi?id=113594&action=edit digiKam XMP with Read from sidecar files disabled The darktable XMP after updating from digiKam with the "Read from sidecar files" option disabled -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 --- Comment #6 from Grzegorz --- (In reply to Maik Qualmann from comment #5) > Ok, I think the correct solution is always to mix the sidecar metadata when > writing. That's what I'd expect. Always merge, never overwrite. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 495012] A black screen appears when changing user or randomly the system locks the screen and enters the password.
https://bugs.kde.org/show_bug.cgi?id=495012 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 494927] kscreen_locker does not unlock screen (error TypeError: Property 'respond' of object ... is not a function)
https://bugs.kde.org/show_bug.cgi?id=494927 Grzegorz changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 494927] With Qt 6.8 after monitor wake-up, can't unlock lock screen by pressing enter button on password field or clicking arrow button (error TypeError: Property 'respond' of ob
https://bugs.kde.org/show_bug.cgi?id=494927 --- Comment #33 from Grzegorz --- I have the same problem on Arch Linux (up to date), I also have this problem, it seems that when the lock screen has its own image set the problem is worse, when I changed the regular color it is a bit better -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363788] Fit to page printing does incorrect scaling and unwanted offsetting
https://bugs.kde.org/show_bug.cgi?id=363788 Grzegorz Wozniak changed: What|Removed |Added CC||wozni...@gmail.com --- Comment #10 from Grzegorz Wozniak --- Same behaviour on Debian 8: Okular version: Version 0.20.2 Using KDE Development Platform 4.14.2 Cups: 1.7.5-11+deb8u1 Ghostscript: 9.06~dfsg-2+deb8u4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 Grzegorz Kowzan changed: What|Removed |Added CC||grzegorz.kow...@gmail.com --- Comment #15 from Grzegorz Kowzan --- I have the same issue: wallpaper is incorrectly scaled, running `plasmashell --replace` and switching workspaces fixes iy, krunner also shows up in the wrong spot. Note that I am using a single external monitor, so this problem is not specific to multi-monitor setups. I can confirm that the issue is not new and occurred also with 5.23.X. Possibly also with 5.22.X, but back then Plasma on Wayland crashed too frequently for me to use, so I didn't use it regularly and can't be sure. The issue is summarized by the photo I just added. Desktop Folder Settings shows the wallpaper correctly scaled, but it's displayed wrongly. Spectacle screenshot also shows incorrectly placed krunner. Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.7-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #16 from Grzegorz Kowzan --- Created attachment 146612 --> https://bugs.kde.org/attachment.cgi?id=146612&action=edit Incorrectly scaled wallpaper with incorrectly scaled krunner, single external monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #17 from Grzegorz Kowzan --- (In reply to Grzegorz Kowzan from comment #15) > wrong spot. Note that I am using a single external monitor, so this problem > is not specific to multi-monitor setups. For clarity, this is also a laptop so there is an internal monitor connected but it is disabled. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 450796] New: KDE Crash handler, asks if you can provide additional info but does not let you do so.
https://bugs.kde.org/show_bug.cgi?id=450796 Bug ID: 450796 Summary: KDE Crash handler, asks if you can provide additional info but does not let you do so. Product: frameworks-kcrash Version: 5.88.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: sta...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Kde crash handler, asks if you can provide information, like what i was doing when the crash occurred. And then it does not let you actually provide that information in any way, it goes straight to the next screen. What is the point ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead store this data in extended attributes
https://bugs.kde.org/show_bug.cgi?id=322922 Grzegorz Szymaszek changed: What|Removed |Added CC||gszymas...@short.pl -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445941] valgrind 3.18.1 crashes on RHEL 6.7 debuginfo Assertion 'in_rx' failed in libmagic.so
https://bugs.kde.org/show_bug.cgi?id=445941 Grzegorz Roszak changed: What|Removed |Added CC||grzegorz.ros...@gmail.com --- Comment #2 from Grzegorz Roszak --- (In reply to Paul Floyd from comment #1) > Which compiler are you using? (In reply to Paul Floyd from comment #1) > Which compiler are you using? I can confirm the same issue on RHEL6.8 (Santiago) with both code under test and valgrind compiled with GCC 11.1.0. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453292] New: KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 Bug ID: 453292 Summary: KOrganizer shows wrong month form in headers Product: korganizer Version: 5.20.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: gregorykku...@gmail.com Target Milestone: --- Created attachment 148513 --> https://bugs.kde.org/attachment.cgi?id=148513&action=edit The header in question SUMMARY Korganizer uses CLDR's "format" month form instead of "standalone" as the header of its month view (see attachment). In Slavic languages it makes the month name show in genitive case, which is correct only as a part of a full date, not as a calendar header. STEPS TO REPRODUCE 1. Open KOrganizer 2. Click "Month" in the topbar. OBSERVED RESULT The month name in the calendar's header is in genitive. EXPECTED RESULT The month name should be in nominative. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453292] KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 --- Comment #2 from Grzegorz Kulik --- I went on a hunt and I hope I caught all instances where the date is shown wrong: - print day shows month name in the top left in "format" instead of "stand-alone", - print event shows American date format if the event repeats every year, - print month shows month names in "format" instead of "stand-alone" in all three instances, - print to-dos shows month name in the top left in "format" instead of "stand-alone", - print week shows name in the top left in "format" instead of "stand-alone", while single day dates show up in American format, - print month shows month names in "format" instead of "stand-alone" in all instances, - timeline header shows the date in American format. I made screenshots with the wrong dates and headers highlighted just in case: https://chmura.kulik.si/s/sSoJ8DrrXkiPby4 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453292] KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 --- Comment #3 from Grzegorz Kulik --- Actually I just switched KOrganizer to German and in the print event preview the date I mentioned showed up in German format, so I'm guessing it's a matter of an incomplete translation. I checked the other instances of the American format and they persist in the German version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 432372] FormLayout text gets elided too early when using a fractional font size
https://bugs.kde.org/show_bug.cgi?id=432372 Grzegorz Kowzan changed: What|Removed |Added CC|grzegorz.kow...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453292] KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 --- Comment #6 from Grzegorz Kulik --- (In reply to gjditchfield from comment #4) > (In reply to Grzegorz Kulik from comment #2) > > - timeline header shows the date in American format. > > Is the month name in the incorrect case — should the timeline > header display "czw. 5 moja 2022"? "czw. 5 moja 2022" is the right format. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 450796] KDE Crash handler, asks if you can provide additional info but does not let you do so.
https://bugs.kde.org/show_bug.cgi?id=450796 --- Comment #2 from Grzegorz Stawik --- So it happened again and i managed to get screenshots to prove it: https://imgur.com/a/FFBuA7x -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 450796] KDE Crash handler, asks if you can provide additional info but does not let you do so.
https://bugs.kde.org/show_bug.cgi?id=450796 --- Comment #3 from Grzegorz Stawik --- So it happened again and i managed to get screenshots to prove it: https://imgur.com/a/FFBuA7x -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442343] New: Unnecessary text ellipsis with non-integer general font size
https://bugs.kde.org/show_bug.cgi?id=442343 Bug ID: 442343 Summary: Unnecessary text ellipsis with non-integer general font size Product: systemsettings Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: grzegorz.kow...@gmail.com Target Milestone: --- Created attachment 141493 --> https://bugs.kde.org/attachment.cgi?id=141493&action=edit Systems settings fonts applet with ellided labels SUMMARY Text labels in System Settings are partially ellided when general font size is set to a fractional value. STEPS TO REPRODUCE 1. Set General font size to a non-integer value in system settings 2. Restart system settings app OBSERVED RESULT Some text labels are ellided EXPECTED RESULT No unnecessary ellision SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Verified that it occurs with a clean user account and a different font family. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432543] New: External display connected to laptop is not working on KDE Wayland session
https://bugs.kde.org/show_bug.cgi?id=432543 Bug ID: 432543 Summary: External display connected to laptop is not working on KDE Wayland session Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: gha...@redhat.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY An external display connected to laptop is not working on KDE Wayland session. STEPS TO REPRODUCE 1. Boot KDE Neon Live ISO OBSERVED RESULT External display is black(it is enabled in Display Configuration) and it is not usable. It is powered-on but applications are not being rendered, the only thing which is visible is the mouse cursor. EXPECTED RESULT The external display should work. SOFTWARE/OS VERSIONS KDE Neon Live ISO: neon unstable 20210131-03:38 ADDITIONAL INFORMATION The same problem can be reproduced also with Fedora Rawhide KDE Live: Fedora-KDE-Live-x86_64-Rawhide-20210203.n.0.iso I reported this bug also in Fedora BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1925326 Xorg session works fine. HARDWARE Laptop: Lenovo ThinkPad P50 GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Grzegorz Kowzan changed: What|Removed |Added CC||kan.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426630] New: plasmashell crashes on startup but runs fine
https://bugs.kde.org/show_bug.cgi?id=426630 Bug ID: 426630 Summary: plasmashell crashes on startup but runs fine Product: plasmashell Version: 5.19.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kan.n...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.5) Qt Version: 5.15.1 Frameworks Version: 5.73.0 Operating System: Linux 5.7.11-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Fresh login into Plasma (Wayland) session on OpenSUSE Tumbleweed (20200915-0). External monitor connected by USB-C/DisplayPort and laptop monitor disabled. The crash happens every time I login, i.e. there is a notification from DrKonqi in the tray, but the desktop actually runs normally. If not for DrKonqi notification, I wouldn't know the crash happened. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f4dc42f9a92 in QScreen::name (this=0x55fb94f115a0) at kernel/qscreen.cpp:189 #5 0x55fb94ad7b13 in ShellCorona::addOutput (this=this@entry=0x55fb94f239c0, screen=, screen@entry=0x55fb94f115a0) at /usr/src/debug/plasma5-workspace-5.19.5-2.1.x86_64/shell/shellcorona.cpp:1324 #6 0x55fb94ad87cb in ShellCorona::load (this=) at /usr/src/debug/plasma5-workspace-5.19.5-2.1.x86_64/shell/shellcorona.cpp:766 #7 0x7f4dc3ec5646 in QtPrivate::QSlotObjectBase::call (a=0x7ffcea1ddc90, r=0x55fb94f239c0, this=0x55fb9516cb20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x55fb94f91ab0, signal_index=4, argv=argv@entry=0x7ffcea1ddc90) at kernel/qobject.cpp:3886 #9 0x7f4dc3ebe9a0 in QMetaObject::activate (sender=, m=m@entry=0x7f4dc5f8c560, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcea1ddc90) at kernel/qobject.cpp:3946 #10 0x7f4dc5f68311 in KActivities::Consumer::serviceStatusChanged (this=, _t1=) at /usr/src/debug/kactivities5-5.73.0-1.2.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:253 #11 0x7f4dc3ec5680 in doActivate (sender=0x55fb94fcad80, signal_index=11, argv=argv@entry=0x7ffcea1dddf0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #12 0x7f4dc3ebe9a0 in QMetaObject::activate (sender=sender@entry=0x55fb94fcad80, m=, local_signal_index=local_signal_index@entry=8, argv=argv@entry=0x7ffcea1dddf0) at kernel/qobject.cpp:3946 #13 0x7f4dc5f7990e in KActivities::ActivitiesCache::serviceStatusChanged (_t1=KActivities::Consumer::Running, this=0x55fb94fcad80) at /usr/src/debug/kactivities5-5.73.0-1.2.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:412 #14 KActivities::ActivitiesCache::setAllActivities (this=0x55fb94fcad80, _activities=...) at /usr/src/debug/kactivities5-5.73.0-1.2.x86_64/src/lib/activitiescache_p.cpp:285 #15 0x7f4dc5f6c522 in KActivities::ActivitiesCache::passInfoFromReply, void (KActivities::ActivitiesCache::*)(QList const&)> (f=, watcher=, this=0x55fb94fcad80) at /usr/include/qt5/QtCore/qlist.h:164 #16 KActivities::ActivitiesCache::setAllActivitiesFromReply (watcher=, this=0x55fb94fcad80) at /usr/src/debug/kactivities5-5.73.0-1.2.x86_64/src/lib/activitiescache_p.cpp:211 #17 KActivities::ActivitiesCache::qt_static_metacall (_o=0x55fb94fcad80, _c=, _id=, _a=) at /usr/src/debug/kactivities5-5.73.0-1.2.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:201 #18 0x7f4dc3ec5680 in doActivate (sender=0x55fb94faca40, signal_index=3, argv=argv@entry=0x7ffcea1de060) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #19 0x7f4dc3ebe9a0 in QMetaObject::activate (sender=, m=m@entry=0x7f4dc50765e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcea1de060) at kernel/qobject.cpp:3946 #20 0x7f4dc5056baf in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #21 0x7f4dc3ebb091 in QObject::event (this=0x55fb94faca40, e=0x55fb94f25b90) at kernel/qobject.cpp:1314 #22 0x7f4dc4a3a14f in QApplicationPrivate::notify_helper (this=, receiver=0x55fb94faca40, e=0x55fb94f25b90) at kernel/qapplication.cpp:3630 #23 0x7f4dc3e8f05a in QCoreApplication::notifyInternal2 (receiver=0x55fb94faca40, event=0x55fb94f25b90) at ../../include/QtCore/5.15.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #24 0x7f4dc3e91a91 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55fb94ef1560) at kernel/qcoreapplication.cpp:1817 #25 0x7f4dc3ee6f23 in postEventSourceDispatch (s=0x55fb94f41520) at kernel
[konsole] [Bug 427681] New: Konsole behaves strangely when setting AllowKDEAppsToRememberWindowPositions=false
https://bugs.kde.org/show_bug.cgi?id=427681 Bug ID: 427681 Summary: Konsole behaves strangely when setting AllowKDEAppsToRememberWindowPositions=false Product: konsole Version: 20.08.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: antonone+kdeb...@gmail.com Target Milestone: --- SUMMARY Sorry for such general title, but because of unfamiliarity with KDE codebase, I'm unable to pinpoint the bug to the specific component. I can see however that it's visible in Konsole app. STEPS TO REPRODUCE Not really sure what's the exact sequence; I can reproduce it on one KDE installation (on openSUSE) without problems by following the steps described below, but the bug never happens on another KDE installation (on ArchLinux) and I can't force it to happen on this another KDE installation. 1. Set `AllowKDEAppsToRememberWindowPositions=false` in ~/.config/kdeglobals 2. Run Konsole 3. Change its size to very small or very large 4. Open 1 additional tab 5. Bug: Konsole should change the window size to some other size. 6. Resize the Konsole window again 7. Switch to another tab 8. Bug: There's a chance that the window will resize itself once again, by itself. Then, close the Konsole window. Update AllowKDEAppsToRememberWindowPositions to 'true' or remove this setting (it should be true by default). If done so, the Konsole window will behave normally without problems. OBSERVED RESULT You can see the behavior here: https://www.youtube.com/watch?v=QcS3hDgphNc On this video, the Konsole window resizes itself, it also confuses the "Show menu" option: when I turn menu on, switch tab, then menu can hide itself. But Konsole still will think the menu is shown, because it will hide 'show menu' option in the context menu! Also sometimes when switching tabs, the Konsole window is resized, and "Show menu" option is reverted to previous setting. EXPECTED RESULT Proper Konsole behavior! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20201011 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.8.14-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 427681] Konsole behaves strangely when setting AllowKDEAppsToRememberWindowPositions=false
https://bugs.kde.org/show_bug.cgi?id=427681 --- Comment #1 from Grzegorz Antoniak --- A little errata for the original bug report, in case my original report isn't clear. Step 5 in "STEPS TO REPRODUCE": 5. Bug: Konsole changes the window size to some other size, and it shouldn't do it. OBSERVED RESULT Konsole sometimes changes the size of the window, and changes the state of "menu visible" option, just after switching from one tab to another. EXPECTED RESULT Konsole shouldn't change the size of the window when switching tabs. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 427681] Konsole behaves strangely when setting AllowKDEAppsToRememberWindowPositions=false
https://bugs.kde.org/show_bug.cgi?id=427681 --- Comment #2 from Grzegorz Antoniak --- After updating to KDE Plasma 5.20, the resizing part of this problem is gone, but sometimes switching tabs reverts the last action of showing/hiding the menu. So it's not completely gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422637] [Wayland] Changing some settings in fonts KCM leads to a blank screen when "applied"
https://bugs.kde.org/show_bug.cgi?id=422637 Grzegorz Kowzan changed: What|Removed |Added CC||kan.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kgraphviewer] [Bug 462326] kgraphviewer crashes when loading file
https://bugs.kde.org/show_bug.cgi?id=462326 --- Comment #7 from Grzegorz Szymaszek --- I’ve checked a few build scripts of other CMake-based programs (kquickimageeditor, plasma-pass, qgis), and the build() and package() functions are written in a quite different way; but I’m not sure which one is better. Could you try to compare the contents of the Arch package and the one you’ve built? Perhaps the build environment, ie the libraries available and their versions make the difference, perhaps you should build it in a fresh chroot that has only those dependencies the Arch-package-building-software deems necessary. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422899] Kwin crashed when using present window option via hot corners.
https://bugs.kde.org/show_bug.cgi?id=422899 Grzegorz Kowzan changed: What|Removed |Added CC||kan.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422899] Kwin crashed when using present window option via hot corners.
https://bugs.kde.org/show_bug.cgi?id=422899 --- Comment #5 from Grzegorz Kowzan --- Created attachment 129947 --> https://bugs.kde.org/attachment.cgi?id=129947&action=edit New crash information added by DrKonqi kwin_x11 (5.19.2) using Qt 5.15.0 - What I was doing when the application crashed: Entered Present Windows by hot corners. Crash happens when I exit the effect. Happens quite reliably every few times I do this. - Custom settings of the application: OpenGL 3.1 compositor (doesn't happen for XRender). Intel Graphics UHD 620, modesetting driver. -- Backtrace (Reduced): #5 0x7efe2149bdcc in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=, e=0x7efe14007360) at /usr/include/qt5/QtCore/qvector.h:1041 #6 0x7efe20094057 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7efe14007360, result=result@entry=0x7ffec3be9758) at kernel/qabstracteventdispatcher.cpp:488 #7 0x7efe1a37b571 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x560c05868b60, event=event@entry=0x7efe14007360) at qxcbnativeinterface.h:101 #8 0x7efe1a37ca86 in QXcbConnection::processXcbEvents(QFlags) (this=0x560c05868b60, flags=...) at qxcbconnection.cpp:1003 #9 0x7efe1a39f2fc in QXcbUnixEventDispatcher::processEvents(QFlags) (this=0x560c0597bf00, flags=...) at qxcbeventdispatcher.cpp:61 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424340] New: PDF bookmarks not found when opening document by symbolic link
https://bugs.kde.org/show_bug.cgi?id=424340 Bug ID: 424340 Summary: PDF bookmarks not found when opening document by symbolic link Product: okular Version: 1.10.2 Platform: unspecified OS: All Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kan.n...@gmail.com Target Milestone: --- SUMMARY Bookmarks for a PDF document not found when the document is opened through a symbolic link. STEPS TO REPRODUCE 1. Create a folder ~/dir_x and a symbolic link to it at ~/dir_y. 2. Open file ~/dir_x/file.pdf and create a bookmark. 3. Open the same file through ~/dir_y/file.pdf path, bookmark is not found. POSSIBLE SOLUTION Resolve absolute path when opening a file or compare absolute paths when looking for bookmarks. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408142] Improve workflow when removing empty space in timeline
https://bugs.kde.org/show_bug.cgi?id=408142 --- Comment #2 from Grzegorz Nowakowski --- Wow, this was so long ago... the logic behind moving the playhead is to avoid skipping playback of a bit of material. Therefore I imagine that in your case the playhead should still move to the start of the following clip, just like in case of all tracks. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408142] New: Improve workflow when remove empty space
https://bugs.kde.org/show_bug.cgi?id=408142 Bug ID: 408142 Summary: Improve workflow when remove empty space Product: kdenlive Version: 19.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gres...@gmail.com Target Milestone: --- Created attachment 120427 --> https://bugs.kde.org/attachment.cgi?id=120427&action=edit step 2 and step 3 side by side SUMMARY When removing empty space in timeline the play head stays in the same place on screen. This effectively moves the play head forward on the next clip by some arbitrary amount. Clip editing workflow would be much more smooth and intuitive if the playhead could be placed at the beginning of the first clip located just after the empty space. STEPS TO REPRODUCE 1. Create empty space between two clips (called left and right) 2. Move playhead somewhere into the empty space 3. Remove empty space (i.e. by pressing shift+space) OBSERVED RESULT Playhead retains it's location on the screen and is now placed some seconds into the right clip. Pressing space at this moment plays the right clip not from the beginning but rather from a more or less random spot to the right. EXPECTED RESULT The playhead could move to the beginning of the right clip so one space is pressed the playback would start from there. SOFTWARE/OS VERSIONS I have experienced this on 19.04.0. I imagine it's quite OS agnostic. ADDITIONAL INFORMATION Originally I thought this might become a feature to turn on in the settings, but I don't see how current behavior would be useful. I recommend to change default behavior if it doesn't break anything else. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408142] Improve workflow when remove empty space in timeline
https://bugs.kde.org/show_bug.cgi?id=408142 Grzegorz Nowakowski changed: What|Removed |Added Summary|Improve workflow when |Improve workflow when |remove empty space |remove empty space in ||timeline -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408142] Improve workflow when removing empty space in timeline
https://bugs.kde.org/show_bug.cgi?id=408142 Grzegorz Nowakowski changed: What|Removed |Added Summary|Improve workflow when |Improve workflow when |remove empty space in |removing empty space in |timeline|timeline -- You are receiving this mail because: You are watching all bug changes.
