[neon] [Bug 476789] New: Kernel 6.2.0-36 - L3 Cache Ext. Error Code: 4, L3M Data ECC Error
https://bugs.kde.org/show_bug.cgi?id=476789 Bug ID: 476789 Summary: Kernel 6.2.0-36 - L3 Cache Ext. Error Code: 4, L3M Data ECC Error Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: francogpellegr...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Latest default kernel starts to spam L3 cache errors since latest KDE neon updates. STEPS TO REPRODUCE 1. Use the system OBSERVED RESULT the system terminal starts to spam randomly this logs: nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Corrected error, no action required. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: CPU:0 (19:50:0) MC7_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc204404010b nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Error Addr: 0x0001002fe620 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: IPID: 0x000700b02035, Syndrome: 0xdfea1a470607 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: L3 Cache Ext. Error Code: 4, L3M Data ECC Error. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: GEN nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Corrected error, no action required. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: CPU:0 (19:50:0) MC8_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc204404010b nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Error Addr: 0x000375bbac50 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: IPID: 0x000700b020350100, Syndrome: 0x71e71a470707 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: L3 Cache Ext. Error Code: 4, L3M Data ECC Error. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: GEN nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Corrected error, no action required. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: CPU:0 (19:50:0) MC9_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc204404010b nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: Error Addr: 0x0006e4db9aa0 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: IPID: 0x000700b020350200, Syndrome: 0x000135151a470700 nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: L3 Cache Ext. Error Code: 4, L3M Data ECC Error. nov 09 07:56:54 developer.cevt.ar kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: GEN EXPECTED RESULT I rolled back to Kernel 6.2.0-35, and there's no log spam there SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-35-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H V2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474840] New: Baloo File Extractor crashes when logging in
https://bugs.kde.org/show_bug.cgi?id=474840 Bug ID: 474840 Summary: Baloo File Extractor crashes when logging in Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.110.0 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: frap...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.110.0) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 5.17.0-1035-oem x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: I have recently installed the NVIDIA propietary drivers, and after logging in, I am getting this error. Nothing else has changed. Now every time I log in, I get this error. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139740267264320) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139740267264320) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139740267264320, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f17d4574476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f17d455a7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f17d42c1418 in mdb_assert_fail.constprop.0 (env=0x564ac9a11190, expr_txt=, func=, line=, file=0x7f17d42c2967 "mdb.c") at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:1542 #10 0x7f17d42b3a45 in mdb_page_dirty (txn=, txn=, mp=) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:2114 #11 mdb_page_dirty (txn=0x564ac9a11610, mp=) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:2114 #12 0x7f17d42be756 in mdb_page_alloc.isra.0 (num=, mp=0x7ffd43e83708, mc=, mc=) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:2308 #13 0x7f17d42b5b13 in mdb_page_touch (mc=mc@entry=0x7ffd43e83c50) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:2428 #14 0x7f17d42b790c in mdb_cursor_touch (mc=mc@entry=0x7ffd43e83c50) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:6523 #15 0x7f17d42ba1f8 in mdb_cursor_put (mc=mc@entry=0x7ffd43e83c50, key=key@entry=0x7ffd43e84060, data=data@entry=0x7ffd43e84050, flags=flags@entry=0) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:6657 #16 0x7f17d42bb377 in mdb_put (txn=0x564ac9a11610, dbi=3, key=0x7ffd43e84060, data=0x7ffd43e84050, flags=0) at /build/lmdb-nWcbxF/lmdb-0.9.24/libraries/liblmdb/mdb.c:9022 #17 0x7f17d5709304 in Baloo::PositionDB::put(QByteArray const&, QVector const&) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #18 0x7f17d5717c40 in Baloo::WriteTransaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #19 0x7f17d570cf5f in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #20 0x564ac948af14 in Baloo::App::processNextFile (this=0x7ffd43e84710) at ./src/file/extractor/app.cpp:109 #21 0x7f17d4c7ea46 in QtPrivate::QSlotObjectBase::call (a=0x7ffd43e842a0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 QSingleShotTimer::timerEvent (this=0x564ac9b50e50) at kernel/qtimer.cpp:322 #23 0x7f17d4c702ef in QObject::event (this=0x564ac9b50e50, e=0x7ffd43e843e0) at kernel/qobject.cpp:1369 #24 0x7f17d4c42e7a in QCoreApplication::notifyInternal2 (receiver=0x564ac9b50e50, event=0x7ffd43e843e0) at kernel/qcoreapplication.cpp:1064 #25 0x7f17d4c9b69b in QTimerInfoList::activateTimers (this=0x564ac99d6100) at kernel/qtimerinfo_unix.cpp:643 #26 0x7f17d4c9bf9c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #27 0x7f17d3735d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f17d378b258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f17d37333e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f17d4c9c368 in QEventDispatcherGlib::processEvents (this=0x564ac99c8200, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #31 0x7f17d4c4179b in QEventLoop::exec (this=this@entry=0x7ffd43e84620, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #32 0x7f17d4c49d44 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #33 0x564ac9480f63 in main (argc=, argv=) at ./src/file/extractor/main.cpp:43 [Inferior 1 (process 3013) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #15 from Franco Pellegrini --- I cannot reproduce it in a lot of months. Seems to be fixed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428335] Widget shows unnecessary animations when first becoming visible on a thick vertical auto-hiding panel
https://bugs.kde.org/show_bug.cgi?id=428335 --- Comment #8 from Franco Pellegrini --- seems to be fixed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] Segmentation fault (11) on plasmashell when returning from screen locking
https://bugs.kde.org/show_bug.cgi?id=467444 --- Comment #7 from Franco Pellegrini --- the desktop crash every day, when screensaver turn off both monitors, and I wake up the session. But cannot catch any error report like in previous crashes.. I'm forced to kill all plasma and restart it again every time to work again. I also tried to remove calendar, but the problem continues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?)
https://bugs.kde.org/show_bug.cgi?id=467444 --- Comment #5 from Franco Pellegrini --- (In reply to Nate Graham from comment #3) > What is "light locker?" You mean the lock screen? > > Looks like a calendar plugin is crashing: > > > #5 0x7f5d557bae1e in ?? () from > > /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so > > #6 0x7f5d557bb1cd in ?? () from > > /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so > > Could you please install debug symbols for Plasma, reproduce the crash, and > attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports for details about how to do this. > > Thanks! I attached an image about the "light locker" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?)
https://bugs.kde.org/show_bug.cgi?id=467444 --- Comment #4 from Franco Pellegrini --- Created attachment 157867 --> https://bugs.kde.org/attachment.cgi?id=157867=edit Light Locker -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?)
https://bugs.kde.org/show_bug.cgi?id=467444 --- Comment #2 from Franco Pellegrini --- maybe its related to https://bugs.kde.org/show_bug.cgi?id=451322 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?)
https://bugs.kde.org/show_bug.cgi?id=467444 --- Comment #1 from Franco Pellegrini --- I think that I captured the crash: -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x0018 in ?? () #5 0x7f5d557bae1e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so #6 0x7f5d557bb1cd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so #7 0x7f5df86822b7 in QQmlEngine::~QQmlEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f5df924c527 in KDeclarative::QmlObject::~QmlObject() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #9 0x7f5df924d22d in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #10 0x7f5df6ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5df6ef21a6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5de3fbcdaa in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #13 0x7f5df6ee711e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f5df6ef21a6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f5de3fa5e0d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #16 0x7f5df92f91c8 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #17 0x7f5df92f93cd in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #18 0x7f5df92e2da6 in Plasma::Applet::~Applet() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #19 0x7f5df92e88fd in Plasma::Containment::~Containment() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #20 0x5573fdc949e0 in ?? () #21 0x5573fdc94c9d in ?? () #22 0x7f5df6ee9883 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f5df7d6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f5df6ebc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f5df6ebf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f5df6ec2f4c in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x5573fdc62a8b in ?? () #28 0x7f5df6429d90 in __libc_start_call_main (main=main@entry=0x5573fdc61b70, argc=argc@entry=1, argv=argv@entry=0x7ffcc934d008) at ../sysdeps/nptl/libc_start_call_main.h:58 #29 0x7f5df6429e40 in __libc_start_main_impl (main=0x5573fdc61b70, argc=1, argv=0x7ffcc934d008, init=, fini=, rtld_fini=, stack_end=0x7ffcc934cff8) at ../csu/libc-start.c:392 #30 0x5573fdc62bb5 in ?? () [Inferior 1 (process 28655) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467444] New: Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?)
https://bugs.kde.org/show_bug.cgi?id=467444 Bug ID: 467444 Summary: Segmentation fault (11) on plasmashell when screen turn off and on again (light locker?) Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: francogpellegr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Every time the monitor turn on again after light locker kicks in (turning off the monitors), plasmashell crash and all panels and widgets disappear. I can reproduce it on 2 different hardware PC, every time, since more than 2 years. STEPS TO REPRODUCE 1. wait until light locker kicks in, and monitors (dual) turn off 2. type some key to turn on again the monitors. 3. the monitors turn on 4. enter again to the session (unlock) 5. desktop crash OBSERVED RESULT plasmashell always crash when monitors wake up EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H V2 ADDITIONAL INFORMATION can also reproduce on this PC: Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430530] CPU Widget garbage
https://bugs.kde.org/show_bug.cgi?id=430530 --- Comment #2 from Franco Pellegrini --- It does not appear since 1-2 month, maybe its fixed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430530] CPU Widget garbage
https://bugs.kde.org/show_bug.cgi?id=430530 --- Comment #2 from Franco Pellegrini --- It does not appear since 1-2 month, maybe its fixed --- Comment #3 from Franco Pellegrini --- It does not appear since 1-2 month, maybe its fixed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] With AMD or NVIDIA GPU, Lock screen wallpaper is sometimes all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #40 from Franco Pellegrini --- *** Bug 464445 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464445] wallpaper black after monitor resume from sleep
https://bugs.kde.org/show_bug.cgi?id=464445 Franco Pellegrini changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Franco Pellegrini --- *** This bug has been marked as a duplicate of bug 457284 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] With AMD or NVIDIA GPU, Lock screen wallpaper is sometimes all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 Franco Pellegrini changed: What|Removed |Added CC||francogpellegr...@gmail.com --- Comment #39 from Franco Pellegrini --- (In reply to Nate Graham from comment #37) > Oh fabulous, maybe > https://invent.kde.org/plasma/kscreenlocker/-/commit/ > 50fc20dc940c87ffd62be0650b935324e164b59d was the fix. > > Can other people upgrade to Plasma 5.26.5 and see if the issue is solved for > them too? I'm using AMD, and the problem continues. Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H V2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464445] New: wallpaper black after monitor resume from sleep
https://bugs.kde.org/show_bug.cgi?id=464445 Bug ID: 464445 Summary: wallpaper black after monitor resume from sleep Classification: Plasma Product: kwin Version: 5.26.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com Target Milestone: --- SUMMARY Every time the screensaver (shut down monitors) kick in, when I move the mouse to continue working, some screens/monitors wallpapers change their background to black, and some windows change sizes or crashes STEPS TO REPRODUCE 1. wait until screensaver turn off all monitors 2. resume working turning on monitors and sesion 3. some wallpapers from some monitors become black OBSERVED RESULT some desktops from certain monitors become black desktops (but panels work just fine) EXPECTED RESULT all desktop must show wallpapers after resume from monitor sleep SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H V2 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 462405] New: subtitlecomposer crashes when choosing a different audio stream
https://bugs.kde.org/show_bug.cgi?id=462405 Bug ID: 462405 Summary: subtitlecomposer crashes when choosing a different audio stream Classification: Miscellaneous Product: unknown Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: frap...@gmail.com Target Milestone: --- Application: subtitlecomposer (0.7.1) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 5.15.0-53-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: I don't know which debug symbols I need to install in order to get better stack traces... for some reason the KDE Crash Handler fails to do so automatically. In any case, the way to reproduce it is super easy: 1) open a subtitle file for a MKV video with multiple audio streams 2) Right-click the video 3) Under the "Audio Streams" menu, choose the second stream After this, the program just crashes The crash can be reproduced every time. -- Backtrace: Application: Subtitle Composer (subtitlecomposer), signal: Segmentation fault [KCrash Handler] #4 0x55ac053473ae in SubtitleComposer::FFPlayer::activeAudioStream (streamIndex=1, this=0x55ac076b1810) at ./src/videoplayer/backend/ffplayer.cpp:291 #5 SubtitleComposer::VideoPlayer::selectAudioStream (streamIndex=1, this=0x55ac071f5b90) at ./src/videoplayer/videoplayer.cpp:204 #6 SubtitleComposer::VideoPlayer::selectAudioStream (this=0x55ac071f5b90, streamIndex=1) at ./src/videoplayer/videoplayer.cpp:197 #7 0x7f6bbe4330f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6bbf716735 in KSelectAction::indexTriggered(int) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #9 0x7f6bbe4330f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6bbf716795 in KSelectAction::triggered(int) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #11 0x7f6bbf71ae6a in KSelectAction::actionTriggered(QAction*) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #12 0x7f6bbe4330f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6bbeff6b53 in QActionGroup::triggered(QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f6bbe433128 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f6bbeff2c56 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f6bbeff594c in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f6bbf181902 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f6bbf1894d9 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f6bbf03c87e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f6bbeff9763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f6bbf0013a4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f6bbe3fb09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f6bbefffe87 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f6bbf056c13 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f6bbf0593a5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f6bbeff9763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f6bbe3fb09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f6bbe8eea87 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7f6bbe8c2a6c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f6bb24e6c8e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #31 0x7f6bbaed5d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f6bbaf2a6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f6bbaed33c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f6bbe454af8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f6bbe3f99bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f6bbe401f54 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x55ac052b9af7 in main (argc=, argv=) at ./src/main.cpp:239 [Inferior
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 Franco Pellegrini changed: What|Removed |Added Version|5.22.4 |5.26.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #27 from Franco Pellegrini --- the problem is 100% reproduced every day using x11 Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 23.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H310M H -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added Version|5.22.3 |5.26.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #12 from Franco Pellegrini --- the problem is 100% reproduced every day using x11 Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 23.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H310M H -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347437] Alt + Tab should bring all instances of application to the front
https://bugs.kde.org/show_bug.cgi?id=347437 --- Comment #9 from Franco Pellegrini --- (In reply to kde.org from comment #8) > I did exactly what you wrote and not touch the mouse and can confirm that I > am back at dolphin. But to be honest, that's what I would have expected, as > that is the window that was active before tabbing to Konsole 2. Your wish is > that this behavior should be changed to move the focus to the most recent > active window of the same application, when "Only one window per > application" is chosen for the tabbox. Well, I'll leave that for someone > else to decide if the behavior should be changed or if we need a new config > option to enable your desired behavior. Correct, there are 2 ways you can look at this, either you Alt + Tab between applications or windows... If you switch between windows, then yeah the current behavior is expected, I am proposing to provide a way to really Alt + Tab between applications (Which is the intention, I believe of the "Only one window per application). When I created this proposal, I was coming from MacOS, and I am pretty sure the behavior was like what I am proposing here (I don't remember, this report is turning 7 years in a few days :P, and I don't have a Mac near me to test), which does make a lot of sense when you work with tons of windows/tabs/etc... At least it does for me :) I am fine with it being either the default behavior or having a separate setting, it would be great either way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347437] Alt + Tab should bring all instances of application to the front
https://bugs.kde.org/show_bug.cgi?id=347437 --- Comment #7 from Franco Pellegrini --- (In reply to kde.org from comment #6) > Thank you for the quick response. I still can't reproduce the issue. What > focus policy are you using. I use "focus follows mouse (mouse precedence), > focus stealing prevention medium. Same settings on both... Are you using your mouse to change focus? Try this, without touching your mouse at all: 1) Alt + Space, type Konsole and open it 2) In konsole Type some random character, say "1", doesn't matter, and hit Enter. 3) Ctrl + Shift + N to open a new Konsole Window 4) Type a different character, say "2" and hit Enter. 5) Alt + Space, type Dolphin and open it 6) Alt + Tab to switch to Konsole (You should be seeing the one you typed 2) 7) Ctrl + D to close it At this point, you are back at dolphin, and not at the Konsole with "1" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347437] Alt + Tab should bring all instances of application to the front
https://bugs.kde.org/show_bug.cgi?id=347437 --- Comment #5 from Franco Pellegrini --- (In reply to kde.org from comment #4) > Thank you for reporting this issue. I tried to reproduce the steps but the > described behavior works for me. Is this still an issue for you in 5.24.5? I haven't yet upgraded to 5.24.5, I am on 5.24.4 and this is still happening by following my second example: 1) Open Chromium 2) Ctrl + N to get a new window 3) Open Konsole 4) Alt + Tab to Chromium 5) Ctrl + W to close this window It no longer happens though, with the Kate example with the "Open" dialog -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #11 from Franco Pellegrini --- problem continues Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #25 from Franco Pellegrini --- (In reply to Nate Graham from comment #24) > Yeah could you check again with Plasma 5.24.3 when it's released in three > days? problem continues with 5.24.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 --- Comment #10 from Franco Pellegrini --- (In reply to Gabriel from comment #9) > For KDE Neon it should be: > /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing I get: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet: symbol lookup error: /lib/x86_64-linux-gnu/libLayerShellQtInterface.so.5: undefined symbol: wl_proxy_marshal_flags -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 --- Comment #8 from Franco Pellegrini --- (In reply to David Edmundson from comment #7) > Some distros change it. It might be lib64 instead of lib. > > You can try finding the file, failing that lets hope someone else hits the > same bug cannot find either -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 --- Comment #6 from Franco Pellegrini --- (In reply to David Edmundson from comment #5) > /usr/lib/libexec/kscreenlocker_greet --testing it say: command not found -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 --- Comment #4 from Franco Pellegrini --- (In reply to David Edmundson from comment #1) > Crashes need a backtrace to be actionable. > > You may find it easier to run kscreenlocker_greet --testing manually Can you list the commands to log this error? I tried that command without success -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 --- Comment #3 from Franco Pellegrini --- Created attachment 147418 --> https://bugs.kde.org/attachment.cgi?id=147418=edit error reported by kde This is the error reported when I woke up my pc after session lock down -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451322] New: screen locker does not work anymore after upgrading to 5.24.3
https://bugs.kde.org/show_bug.cgi?id=451322 Bug ID: 451322 Summary: screen locker does not work anymore after upgrading to 5.24.3 Product: kscreenlocker Version: 5.24.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: francogpellegr...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY I get a message that state that I need to use loginctl unlock-session 5 to restore my locked session, in a black screen. STEPS TO REPRODUCE 1. set screen lock to 5 minutes 2. wait until lock 3. try to login again OBSERVED RESULT a black screen with instructions to unlock the session using commands EXPECTED RESULT unlock my session using the gui login manager SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #10 from Franco Pellegrini --- Problems continues. When boot, the main monitor background becomes black (but with panels), and all windows get minimized into the second monitor Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #21 from Franco Pellegrini --- Problems continues. When boot, the main monitor background becomes black (but with panels), and all windows get minimized into the second monitor Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Franco Pellegrini changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #397 from Franco Pellegrini --- Problems continues. When boot, the main monitor background becomes black (but with panels), and all windows get minimized into the second monitor Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 449998] Kde 5.24 takes more than 5 minutes to boot
https://bugs.kde.org/show_bug.cgi?id=449998 Franco Pellegrini changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 449998] Kde 5.24 takes more than 5 minutes to boot
https://bugs.kde.org/show_bug.cgi?id=449998 Franco Pellegrini changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 449998] Kde 5.24 takes more than 5 minutes to boot
https://bugs.kde.org/show_bug.cgi?id=449998 --- Comment #1 from Franco Pellegrini --- Note that it seems to fail to mount my HOME dir? but it work just fine after boot -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 449998] New: Kde 5.24 takes more than 5 minutes to boot
https://bugs.kde.org/show_bug.cgi?id=449998 Bug ID: 449998 Summary: Kde 5.24 takes more than 5 minutes to boot Product: kcm_grub2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: konstantinos.sma...@gmail.com Reporter: francogpellegr...@gmail.com Target Milestone: --- SUMMARY Since KDE 5.24 the boot time goes from 10-20 seconds to 5 minutes STEPS TO REPRODUCE 1. boot and wait to login 2. it takes 5 minutes OBSERVED RESULT 11 06:23:23 developer.cevt.ar systemd[1]: Starting File System Check on /dev/disk/by-uuid/999ea169-c56e-4457-a02f-6fbb467390d3... feb 11 06:23:23 developer.cevt.ar systemd[1]: Found device KINGSTON_SA400S37480G 4. feb 11 06:23:23 developer.cevt.ar systemd[1]: Found device KINGSTON_SA400S37480G NO_LABEL. feb 11 06:23:23 developer.cevt.ar systemd[1]: Activating swap /dev/disk/by-uuid/6464c210-2a67-4b81-a8f5-34bc4382c2ed... feb 11 06:23:23 developer.cevt.ar systemd[1]: Starting File System Check on /dev/disk/by-uuid/88D2-A2E5... feb 11 06:23:23 developer.cevt.ar systemd[1]: Started File System Check Daemon to report status. feb 11 06:23:23 developer.cevt.ar systemd[1]: Activated swap /dev/disk/by-uuid/6464c210-2a67-4b81-a8f5-34bc4382c2ed. feb 11 06:23:23 developer.cevt.ar systemd[1]: Reached target Swap. feb 11 06:23:23 developer.cevt.ar systemd[1]: Finished File System Check on /dev/disk/by-uuid/88D2-A2E5. feb 11 06:23:23 developer.cevt.ar systemd[1]: Mounting /boot/efi... feb 11 06:23:23 developer.cevt.ar systemd[1]: Mounted /boot/efi. feb 11 06:23:23 developer.cevt.ar systemd[1]: Finished File System Check on /dev/disk/by-uuid/999ea169-c56e-4457-a02f-6fbb467390d3. feb 11 06:23:23 developer.cevt.ar systemd[1]: Mounting /home... feb 11 06:23:23 developer.cevt.ar systemd[1]: Mounted /home. feb 11 06:23:23 developer.cevt.ar systemd[1]: Finished Flush Journal to Persistent Storage. feb 11 06:23:53 developer.cevt.ar systemd[1]: systemd-fsckd.service: Succeeded. feb 11 06:24:09 developer.cevt.ar kernel: fbcon: Taking over console feb 11 06:24:09 developer.cevt.ar kernel: Console: switching to colour frame buffer device 240x67 feb 11 06:24:51 developer.cevt.ar systemd[1]: dev-sdd1.device: Job dev-sdd1.device/start timed out. feb 11 06:24:51 developer.cevt.ar systemd[1]: Timed out waiting for device /dev/sdd1. > it seems to wait here feb 11 06:24:51 developer.cevt.ar systemd[1]: Dependency failed for /media/franco. feb 11 06:24:51 developer.cevt.ar systemd[1]: Dependency failed for Local File Systems. feb 11 06:24:51 developer.cevt.ar systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. feb 11 06:24:51 developer.cevt.ar systemd[1]: media-franco.mount: Job media-franco.mount/start failed with result 'dependency'. feb 11 06:24:51 developer.cevt.ar systemd[1]: dev-sdd1.device: Job dev-sdd1.device/start failed with result 'timeout'. feb 11 06:24:51 developer.cevt.ar systemd[1]: Starting Load AppArmor profiles... feb 11 06:24:51 developer.cevt.ar systemd[1]: Starting Set console font and keymap... EXPECTED RESULT boot like before SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #391 from Franco Pellegrini --- when I fresh start KDE Neon, sometimes the wallpaper is black on one screen, and all windows get minimized on the other screen instead of the current one. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #27 from Franco Pellegrini --- (In reply to Harald Sitter from comment #26) > zsh counts as garbage login shell > https://bugs.kde.org/show_bug.cgi?id=441227#c14 > > https://realjenius.com/2020/01/12/kde-neon-snap-apps-missing/ I can confirm that https://realjenius.com/2020/01/12/kde-neon-snap-apps-missing/ solves the issue -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #25 from Franco Pellegrini --- (In reply to Harald Sitter from comment #24) > Are you using zsh there? If so it is configured as your login shell (in > /etc/passwd)? I set zsh as the default shell using chsh -s "$(which zsh)" -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 Franco Pellegrini changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #23 from Franco Pellegrini --- Created attachment 142717 --> https://bugs.kde.org/attachment.cgi?id=142717=edit /var/lib/snapd/desktop/applications content (In reply to Nate Graham from comment #22) > Do the expected .desktop files appear in /var/lib/snapd/desktop/? yes, all snap app appears there as the attached screenshot (in my test example, code and gimp). But they does not appear as an installed app on KDE neon menu, or in KRunner (it only shows a folder named gimp) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 Franco Pellegrini changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #21 from Franco Pellegrini --- I can reproduce this problem on my 3 different PC. All of them are updated, but from old KDE versions to the latest one. Its seems an old problem carried up today. What should I do to workaround the problem? I test a NEW kde neon on a virtual machine, and the problem cannot be reproduced. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #20 from Franco Pellegrini --- Just as a comment, I did not edit such files, they are all untouched since I first installed KDE neon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227
--- Comment #19 from Franco Pellegrini ---
(In reply to Nate Graham from comment #18)
> (In reply to Franco Pellegrini from comment #16)
> > If I type in a terminal
> > echo $XDG_DATA_DIRS
> > I get:
> > /usr/share/plasma:/home/franco/.local/share/flatpak/exports/share:/var/lib/
> > flatpak/exports/share:/usr/local/share:/usr/share
> Looks to me like the snap path isn't in there. Can you print the contents of
> /etc/profile.d/apps-bin-path.sh?
# shellcheck shell=sh
# Expand $PATH to include the directory where snappy applications go.
snap_bin_path="/snap/bin"
if [ -n "${PATH##*${snap_bin_path}}" ] && [ -n "${PATH##*${snap_bin_path}:*}"
]; then
export PATH="$PATH:${snap_bin_path}"
fi
# Ensure base distro defaults xdg path are set if nothing filed up some
# defaults yet.
if [ -z "$XDG_DATA_DIRS" ]; then
export XDG_DATA_DIRS="/usr/local/share:/usr/share"
fi
# Desktop files (used by desktop environments within both X11 and Wayland) are
# looked for in XDG_DATA_DIRS; make sure it includes the relevant directory for
# snappy applications' desktop files.
snap_xdg_path="/var/lib/snapd/desktop"
if [ -n "${XDG_DATA_DIRS##*${snap_xdg_path}}" ] && [ -n
"${XDG_DATA_DIRS##*${snap_xdg_path}:*}" ]; then
export XDG_DATA_DIRS="${XDG_DATA_DIRS}:${snap_xdg_path}"
fi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #16 from Franco Pellegrini --- (In reply to Harald Sitter from comment #14) > (snapd itself installs a file - /etc/profile.d/apps-bin-path.sh - that > injects the relevant XDG_DATA_DIRS path, which is a non-standard location > managed by snapd. if that is not working then chances are that file is > broken/missing, or a garbage login shell is being used that doesn't source > /etc/profile, or /etc/profile is broken, or something overwrites > XDG_DATA_DIRS without appending the original entries) If I type in a terminal echo $XDG_DATA_DIRS I get: /usr/share/plasma:/home/franco/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #15 from Franco Pellegrini --- (In reply to Nate Graham from comment #13) > Franco, how did you install the Snap app in question? Using Discover? > > Can you try installing it on the command line to see if a relevant .desktop > file appears in the applications folder of any of the directories in > $XDG_DATA_DIRS? I tried both ways, same results. For example installing gimp from command line or from discover. No icons, no folders. The only way to run it is via terminal typing "gimp" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #11 from Franco Pellegrini --- (In reply to David Edmundson from comment #10) > >it does not exists > > Then plasma is not at fault but i'm using kde default program installer to add programs, it's KDE NEON fault? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 443676] New: infinite written files to usb disk
https://bugs.kde.org/show_bug.cgi?id=443676 Bug ID: 443676 Summary: infinite written files to usb disk Product: frameworks-plasma Version: 5.86.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: francogpellegr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 142406 --> https://bugs.kde.org/attachment.cgi?id=142406=edit infinite storage? SUMMARY It seems that I write infinite data to my external usb storage STEPS TO REPRODUCE 1. plug usb external disk 2. copy some data OBSERVED RESULT This time, it seems to show infinite written data (see image attached) EXPECTED RESULT correct graphs SOFTWARE/OS VERSIONS It seems that I wrote infinite data, but only copy some files to an usd disk. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 Franco Pellegrini changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Franco Pellegrini --- ups, I wrongly attached another image report to this thread. Sorry -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #8 from Franco Pellegrini --- Created attachment 142399 --> https://bugs.kde.org/attachment.cgi?id=142399=edit insane data written? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #7 from Franco Pellegrini --- (In reply to David Edmundson from comment #6) > >but I can run them via terminal just fine. > > Please confirm desktop files can be found at $XDG_DATA_DIRS /applications it does not exists -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #9 from Franco Pellegrini --- Problem continues... and I have to reboot 3 or 4 times everyday until the screens decide to select the correct monitor. Very frustrating. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 Franco Pellegrini changed: What|Removed |Added Version|5.20.2 |5.22.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #18 from Franco Pellegrini --- Problem continues... and I have to reboot 3 or 4 times everyday until the screens decide to select the correct monitor. Very frustrating. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #4 from Franco Pellegrini --- tried both ways, discover, and then via terminal. No success. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 --- Comment #2 from Franco Pellegrini --- No, I cannot find them anywhere, but I can run them via terminal just fine. Tested on a fresh install KDE neon, and my workstation (old, but updated over time up today) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441227] New: Cannot find snap installed applications
https://bugs.kde.org/show_bug.cgi?id=441227 Bug ID: 441227 Summary: Cannot find snap installed applications Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: francogpellegr...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Cannot find application installed via snap STEPS TO REPRODUCE 1. install visual studio code via snap 2. install gimp via snap 3. press "super" or click on "application launcher" 4. Try to find them... they are not there OBSERVED RESULT There's no indexation of any snap installed program EXPECTED RESULT find and launch snap applications SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added Version|5.21.0 |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #7 from Franco Pellegrini --- It getting worst. I can almost always reproduce the problem with a fresh boot. All windows animate and minimize to the other monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439282] New: White piles around tooltips and windows
https://bugs.kde.org/show_bug.cgi?id=439282 Bug ID: 439282 Summary: White piles around tooltips and windows Product: kwin Version: 5.22.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com Target Milestone: --- Created attachment 139728 --> https://bugs.kde.org/attachment.cgi?id=139728=edit white pixels bug SUMMARY Since 5.22+ the rounded borders has 2 white pixels. This can be observed on tooltips and windows borders. Its present using default KDE neon drivers, and privative NVIDIA drivers OBSERVED RESULT screenshot EXPECTED RESULT transparent border instead of white SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: NV134 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438507] No search results returned.
https://bugs.kde.org/show_bug.cgi?id=438507 Franco Pellegrini changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438603] cannot find lots of snap and flatpack installed programs using aplication menu
https://bugs.kde.org/show_bug.cgi?id=438603 --- Comment #1 from Franco Pellegrini --- I'm using Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438603] New: cannot find lots of snap and flatpack installed programs using aplication menu
https://bugs.kde.org/show_bug.cgi?id=438603 Bug ID: 438603 Summary: cannot find lots of snap and flatpack installed programs using aplication menu Product: frameworks-plasma Version: 5.82.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: francogpellegr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. open the application menu 2. try to find thunderbird, or visual code (one installed from snap and the other from flatpack) OBSERVED RESULT cannot be find (but it can using alt+space search menu) EXPECTED RESULT find the program SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #14 from Franco Pellegrini --- Created attachment 137587 --> https://bugs.kde.org/attachment.cgi?id=137587=edit notifications also affected this problem appear almost 100% If I don't use the pc form more than 2 or 3 days, but if I reboot or grub to windows and back, I cannot reproduce it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431263] Notifications start to appear on the second monitor instead of main one
https://bugs.kde.org/show_bug.cgi?id=431263 --- Comment #6 from Franco Pellegrini --- Created attachment 137586 --> https://bugs.kde.org/attachment.cgi?id=137586=edit example of notifications appearing on the WRONG monitor example of notifications appearing on the WRONG monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433074] Notifications and panels appear on wrong screen
https://bugs.kde.org/show_bug.cgi?id=433074 --- Comment #14 from Franco Pellegrini --- yes, if there's one, it appear correctly, but all my panels are on the wrong monitor after switching to wayland. Thats the OP report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433074] Notifications and panels appear on wrong screen
https://bugs.kde.org/show_bug.cgi?id=433074 --- Comment #12 from Franco Pellegrini --- I'm using notificaton applet on both monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433074] Notifications and panels appear on wrong screen
https://bugs.kde.org/show_bug.cgi?id=433074 Franco Pellegrini changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434018] New: Cannot see Andorid files when mounted
https://bugs.kde.org/show_bug.cgi?id=434018 Bug ID: 434018 Summary: Cannot see Andorid files when mounted Product: dolphin Version: 20.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Cannot see files from Andorid 9 phones when mounted STEPS TO REPRODUCE 1. Plug in a Phone with Andorid 9 2. Choose "Transfer Files" or "Photo Transfer PTP" on the phone 3. Whait KDE notification to popup 4. Click on Mount and Open 5. Dolphin appear 6. nothing else happens OBSERVED RESULT Dolphin appears EXPECTED RESULT Dolphin appear and show JUST MOUNTED android phone SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433074] Notifications and panels appear on wrong screen
https://bugs.kde.org/show_bug.cgi?id=433074 Franco Pellegrini changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Franco Pellegrini --- (In reply to Nate Graham from comment #3) > When does this happen? When you plug in a new screen while Plasma is already > running? When the screen was already plugged in when the computer was turned > on? The monitor was already plugged in. It happens when I logout and login using Wayland. Also trying to reboot and login using Wayland. Also, as a second related bug, If I change again from Wayland to X11, it delete my second monitor panels and widgets, and I have to configure create all again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428059] Icon sometimes shows zero notifications
https://bugs.kde.org/show_bug.cgi?id=428059 Franco Pellegrini changed: What|Removed |Added Version|5.20.2 |5.21.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added Version|master |5.21.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433074] Wayland does not support "primary" monitor setup
https://bugs.kde.org/show_bug.cgi?id=433074 --- Comment #2 from Franco Pellegrini --- (In reply to Nicolas Fella from comment #1) > Wayland has no concept of a "primary screen". > > What is it that you want to achieve? All my notifications appear on the wrong monitor, and all my panels too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433074] New: Wayland does not support "primary" monitor setup
https://bugs.kde.org/show_bug.cgi?id=433074 Bug ID: 433074 Summary: Wayland does not support "primary" monitor setup Product: kwin Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com Target Milestone: --- SUMMARY Cannot set primary monitor using wayland. There's no such option, like in X11 STEPS TO REPRODUCE 1. switch to wailand 2. try to setup the main monitor OBSERVED RESULT No configuration to change EXPECTED RESULT "primary" checkbox, like with X11 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #73 from Franco Pellegrini --- (In reply to David Redondo from comment #71) > (In reply to Nicola Mori from comment #70) > > @DavidRedondo as I already explained in comment 61 I have several > > NetworkManager packages installed in my Archlinux system, yet the network > > widget doesn't work. This makes me think that the issue might not be 100% > > connected to NetworkManager, but I got no reply to my comment asking for > > clarifications. > > Do you use NetworkManager for managing your connections (not just having the > packages)? With Plasma 5.21 it should now work in both cases. But maybe > there is a case where with some combination it doesn't work and then we can > look further? I use the default KDE Neon installation, and the problem appear in all my PCs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #68 from Franco Pellegrini --- This was never fixed. Don't know why is tagged as fixed... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #6 from Franco Pellegrini --- This problem is getting worst... EVERY time I fresh boot, I get this problem. Every day. I have to relogin to sometimes (75% chance) fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #63 from Franco Pellegrini --- On my end, If I type sudo ksystemstats --replace I get: Unable to start backend, network information not available. Could not determine Plasma version, got: "The name org.kde.plasmashell was not provided by any .service files" Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[knemo] [Bug 432409] New: Switching between netwoks profiles hang ALL PANELS
https://bugs.kde.org/show_bug.cgi?id=432409 Bug ID: 432409 Summary: Switching between netwoks profiles hang ALL PANELS Product: knemo Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jst...@mehercule.net Reporter: francogpellegr...@gmail.com Target Milestone: --- Created attachment 135363 --> https://bugs.kde.org/attachment.cgi?id=135363=edit this menu hang all if click connect SUMMARY Every time I switch from one network profile to another, it hangs for 20 seconds ALL KDE PANELS STEPS TO REPRODUCE 1. create several network profiles, and attach them to specific mac address (I have 2 network cards) 2. switch (connect) between them OBSERVED RESULT All KDE panels hang for 15-20 seconds EXPECTED RESULT Connect in the background without hang all the interactive panels SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #5 from Franco Pellegrini --- Created attachment 135278 --> https://bugs.kde.org/attachment.cgi?id=135278=edit display configuration (In reply to Thiago Sueto from comment #4) > Can you please show a screenshot of your Display Configuration in System > Settings? Image attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #3 from Franco Pellegrini --- In this example, one desktop goes black and cannot right click on it, but I can on the second monitor. The notifications start to appear on the second monitor instead of the first. If I reboot the sesion, "sometimes" it fix the problem. I can reproduce this with 50% chance at boot. https://youtu.be/qQVW5gFHGuw So, there's 2 cases of the same bug: 1) or the 2 screens get merged in the second monitor 2) or the 2 screens get swapped completely Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-64-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added Version|5.20.3 |master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] 2 desktops mergen into one (using multi monitor)
https://bugs.kde.org/show_bug.cgi?id=429917 Franco Pellegrini changed: What|Removed |Added CC||plasma-b...@kde.org Component|Panel |Multi-screen support Assignee|plasma-b...@kde.org |aleix...@kde.org Summary|panels get swapped between |2 desktops mergen into one |screens |(using multi monitor) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431263] Notifications start to appear on the second monitor instead of main one
https://bugs.kde.org/show_bug.cgi?id=431263 --- Comment #5 from Franco Pellegrini --- I also tested placing notification applet on both monitor, and they keep randomly appearing on second monitor sometimes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431263] Notifications start to appear on the second monitor instead of main one
https://bugs.kde.org/show_bug.cgi?id=431263 --- Comment #4 from Franco Pellegrini --- I don't have notification applet on the second monitor, and they ayer appearing on that monitor. Also sometimes the background images get swapped. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431263] Notifications start to appear on the second monitor instead of main one
https://bugs.kde.org/show_bug.cgi?id=431263 --- Comment #2 from Franco Pellegrini --- in the screen configuration options , you can select what monitor is considered as "primary". That monitor should display the incoming notification popups. My primary monitor also should display the panels I specifically add, and widgets to that panel. This bug mix everything between prinary and secondary monitor every 3 or 4 days, at login. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431263] New: Notifications start to appear on the second monitor instead of main one
https://bugs.kde.org/show_bug.cgi?id=431263 Bug ID: 431263 Summary: Notifications start to appear on the second monitor instead of main one Product: kwin Version: 5.20.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. login 2. screen get panels swapped between screens or notifications appear on the wrong monitor OBSERVED RESULT notifications or panels appear on the wrong monitor (sometimes it login ok, sometimes swapped) EXPECTED RESULT notifications and panels to appear in the intended monitor SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-59-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #58 from Franco Pellegrini --- (In reply to jonzn4suse from comment #57) > Created attachment 134594 [details] > Widget working lately In my 3 different pc, it does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430530] New: CPU Widget garbage
https://bugs.kde.org/show_bug.cgi?id=430530 Bug ID: 430530 Summary: CPU Widget garbage Product: plasmashell Version: 5.20.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: francogpellegr...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 134174 --> https://bugs.kde.org/attachment.cgi?id=134174=edit graph garbage SUMMARY Since 5.20.3 and 5.20.4, sometimes the CPU widget show garbage STEPS TO REPRODUCE 1. wait until garbage appear OBSERVED RESULT attached as screenshot EXPECTED RESULT Correct graph SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 366380] Kontact crashed when doing a search
https://bugs.kde.org/show_bug.cgi?id=366380 Franco Pellegrini changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Franco Pellegrini --- Heh, yeah, 4 years later... it works :P -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 430443] Cannot install using encrypted LVM
https://bugs.kde.org/show_bug.cgi?id=430443 --- Comment #2 from Franco Pellegrini --- Created attachment 134104 --> https://bugs.kde.org/attachment.cgi?id=134104=edit Error in the UI after trying to install -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 430443] Cannot install using encrypted LVM
https://bugs.kde.org/show_bug.cgi?id=430443 --- Comment #1 from Franco Pellegrini --- Created attachment 134103 --> https://bugs.kde.org/attachment.cgi?id=134103=edit Partitioning before installing -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 430443] New: Cannot install using encrypted LVM
https://bugs.kde.org/show_bug.cgi?id=430443 Bug ID: 430443 Summary: Cannot install using encrypted LVM Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: frap...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Unable to install KDE Neon when having an encrypted LVM structure. I am using the testing image, downloaded on 20201215 (yesterday) I currently have Windows 10 already installed, and I am trying to install KDE Neon alongside. Disk partitioned as follows: Device StartEndSectors Size Type /dev/nvme0n1p1 2048 206847 204800 100M EFI System /dev/nvme0n1p2206848 239615 3276816M Microsoft reserved /dev/nvme0n1p3239616 928459045 928219430 442.6G Microsoft basic data /dev/nvme0n1p4 928460800 9295216631060864 518M Windows recovery environment /dev/nvme0n1p5 929521664 9305456631024000 500M Linux filesystem /dev/nvme0n1p6 930545664 1953523711 1022978048 487.8G Linux filesystem Partition /dev/nvme0n1p6 is a luks encrypted partition, and inside of it, I have an LVM set up with a root and home partitions (Will eventually have more, but it is irrelevant for this bug) The first issue I encountered with the installation using the stable release, is that apparently the only way to have the filesystem encrypted, is to use the "Install alongside" option, and mark the "Encrypt system" checkbox. This does not provide any flexibility on how to partition or anything... Plus, apparently calamares didn't consider a scenario like mine, in which /boot wouldn't be encrypted... This was solved in https://github.com/calamares/calamares/pull/1566 So, what I do is: 1. As soon as the live USB boots, I open a konsole, and decrypt my partition, which loads the LVM structure. 2. Open calamares, so the disk structure is loaded properly 3. Choose the LVM partition to use for root and home 4. Choose /dev/nvme0n1p1 as /boot/efi 5. Choose /dev/nvme0n1p5 as /boot 6. All partitions that needed it were already formatted as ext4, so no need to do so now. Will attach screenshot on how it looks right before going ahead... Once you click on "Install" the installation fails. Will also attach screenshot with the error shown in the UI This is the terminal output: root@neon:/home/neon# cryptsetup luksOpen /dev/nvme0n1p6 nvme-system Enter passphrase for /dev/nvme0n1p6: root@neon:/home/neon# calamares QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' 19:03:45 [0]: unknown file system type "" on "/dev/nvme0n1p2" 19:03:47 [0]: unknown file system type "dos" on "/dev/sdb3" 16:18:46 [0]: QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout 16:18:46 [0]: QObject::setParent: Cannot set parent, new parent is in a different thread 16:18:46 [0]: QObject::setParent: Cannot set parent, new parent is in a different thread 16:25:35 [0]: Cannot get luksUUID for device "/dev/system/private" cryptsetup exit code 4 output: "Device /dev/system/private doesn't exist or access denied." chcon: failed to get security context of '/': No data available chcon: failed to get security context of '/boot': No data available chcon: failed to get security context of '/boot/efi': No such file or directory chcon: failed to get security context of '/dev': No data available chcon: failed to get security context of '/home': No data available chcon: failed to get security context of '/proc': Operation not supported chcon: failed to get security context of '/run': No data available chcon: failed to get security context of '/run/udev': No data available chcon: failed to get security context of '/sys': No data available chcon: failed to get security context of '/sys/firmware/efi/efivars': Operation not supported 16:25:36 [1]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&) ERROR: Installation failed: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429917] panels get swapped between screens
https://bugs.kde.org/show_bug.cgi?id=429917 --- Comment #2 from Franco Pellegrini --- Today, the 2 screen get partially merged, and one background screen can sometimes appear on the second one. Also, all notifications and program appear on the wrong screen. A quick fix is to reboot session 1 or 2 times, and then it work for a week or so. I managed to capture a video (notice that one screen is black because the background merged on the second screen): https://youtu.be/xMm27C9m8b0 Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428052] Windows selects the wrong panel to minimize, on multiscreen
https://bugs.kde.org/show_bug.cgi?id=428052 --- Comment #13 from Franco Pellegrini --- Today, the 2 screen get partially merged, and one background screen can sometimes appear on the second one. Also, all notifications and program appear on the wrong screen. A quick fix is to reboot session 1 or 2 times, and then it work for a week or so. I managed to capture a video (notice that one screen is black because the background merged on the second screen): https://youtu.be/xMm27C9m8b0 Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358920] Kontact crashed when opening an entry from akregator
https://bugs.kde.org/show_bug.cgi?id=358920 --- Comment #8 from Franco Pellegrini --- Yeah, I am no longer able to reproduce this -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358920] Kontact crashed when opening an entry from akregator
https://bugs.kde.org/show_bug.cgi?id=358920 Franco Pellegrini changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
