[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #9 from Sergey --- If I create file "Образец.txt" in some path in Krusader then it correctly displayed in KrViewer but on the right panel of Krusader I have "��.txt" instead of "Образец.txt". Also, no problems with filenames in konsole-16.04.3 or in dolphin-16.04.3. The only problem is inside panels of krusader-2.5.0. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #11 from Sergey --- # locale-gen * Generating locale-archive: forcing # of jobs to 1 * Generating 6 locales (this might take a while) with 1 jobs * (1/6) Generating en_US.ISO-8859-1 ... [ ok ] * (2/6) Generating en_US.UTF-8 ... [ ok ] * (3/6) Generating ru_RU.CP1251 ... [ ok ] * (4/6) Generating ru_RU.KOI8-R ... [ ok ] * (5/6) Generating ru_RU.UTF-8 ... [ ok ] * (6/6) Generating ru_RU.UTF-8 ... [ ok ] * Generation complete # locale -a C en_US en_US.iso88591 en_US.utf8 POSIX ru_RU ru_RU.cp1251 ru_RU.koi8r ru_RU.utf8 # eselect locale list Available targets for the LANG variable: [1] C [2] en_US [3] en_US.iso88591 [4] en_US.utf8 [5] POSIX [6] ru_RU [7] ru_RU.cp1251 [8] ru_RU.koi8r [9] ru_RU.utf8 [10] ru_RU.UTF-8 * [ ] (free form) # env-update && source /etc/profile >>> Regenerating /etc/ld.so.cache... # emerge -1 kde-misc/krusader * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news read to view new items. These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild R ~] kde-misc/krusader-2.5.0:5::gentoo USE="handbook -debug" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Emerging (1 of 1) kde-misc/krusader-2.5.0::gentoo >>> Installing (1 of 1) kde-misc/krusader-2.5.0::gentoo >>> Jobs: 1 of 1 complete Load avg: 2.79, 1.54, 1.10 >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. non-English files are still buggy after restart of Krusader. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #12 from Sergey --- Created attachment 101839 --> https://bugs.kde.org/attachment.cgi?id=101839&action=edit Log of emerge -1 kde-misc/krusader-2.5.0 from Portage -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #13 from Sergey --- I will try manual install later. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372301] New: Plasmashell crash on suspend/resume
https://bugs.kde.org/show_bug.cgi?id=372301 Bug ID: 372301 Summary: Plasmashell crash on suspend/resume Product: plasmashell Version: 5.8.3 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rion...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) (Compiled from sources) Qt Version: 5.6.2 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-ck-r1 x86_64 Distribution: "Gentoo Base System release 2.3" -- Information about the crash: - What I was doing when the application crashed: I closed lid of my laptop for few hours, opened again later. Plasmashell was not running on open. The last time it restarted automatically but I usually I have to alt+f2+plasmashell to restart it. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f872f2c87c0 (LWP 12602))] Thread 8 (Thread 0x7f866acc2700 (LWP 12610)): #0 0x7f872a545c30 in timerSourceCheckHelper(GTimerSource*) () from /usr/lib64/libQt5Core.so.5 #1 0x7f8725a6ca11 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8725a6cf80 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8725a6d0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f872a545d9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f872a4f5aaa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f866bb7fa57 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #8 0x7f872a35903c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8729c09ded in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f867c798700 (LWP 12608)): #0 0x7f872a351ff9 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5 #1 0x7f872a545b1f in postEventSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f8725a6c56d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8725a6cf0b in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8725a6d0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f872a545d9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f872a4f5aaa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f872d4c8626 in QQuickPixmapReader::run() () from /usr/lib64/libQt5Quick.so.5 #9 0x7f872a35903c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0 #11 0x7f8729c09ded in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f8707bde700 (LWP 12607)): #0 0x7f8729412fef in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f872ed212f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQt5Script.so.5 #2 0x7f872ed21339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQt5Script.so.5 #3 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8729c09ded in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f8711a43700 (LWP 12606)): #0 0x7f8729bfcd5d in read () from /lib64/libc.so.6 #1 0x7f8725ab02e0 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8725a6cac4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8725a6cf80 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8725a6d0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f872a545d9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f872a4f5aaa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f872cb462c5 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #9 0x7f872a35903c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0 #11 0x7f8729c09ded in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8713fff700 (LWP 12605)): #0 0x7f8725ab1694 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8725a6c560 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x
[plasmashell] [Bug 372301] Plasmashell crash on suspend/resume
https://bugs.kde.org/show_bug.cgi?id=372301 Sergey changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages --- Comment #1 from Sergey --- It happens for few days probably. So quite recent bug somewhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 --- Comment #5 from Sergey --- It's not fixed. It crashes almost every time with 5.8.3. Maybe problem is in my second monitor. Usually it turns on not immediately on resume. Probably plasmashell thinks it's disconnected at all and moves panels to laptop's monitor. Can show right on resume a small hint window with "yes" button and countdown counter suggesting to move all panels to the primary monitor? So if second monitor is not detected after few seconds, all panels will be moved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372301] Plasmashell crash on suspend/resume
https://bugs.kde.org/show_bug.cgi?id=372301 --- Comment #3 from Sergey --- not fixed. see comment in #366707 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372666] New: Selection in konsole is slow
https://bugs.kde.org/show_bug.cgi?id=372666 Bug ID: 372666 Summary: Selection in konsole is slow Product: konsole Version: 16.08.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: rion...@gmail.com Target Milestone: --- There were no problem with selection 16.04.3 version. But starting from 16.08.2 or maybe even earlier selection by mouse is really sluggish. Often mouse scroll suffers too but if I scroll with slider, it works fine. I'm not sure but probably long lines are most affected. It does not depend on any other package in my system. Just emerging 16.04.3 is enough to fix this problem on my Gentoo system. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372666] Selection in konsole is slow
https://bugs.kde.org/show_bug.cgi?id=372666 --- Comment #2 from Sergey --- I don't know. links underlining is disabled for me already but it's still sluggish. For example xfce4-terminal is very fast on the me output -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #14 from Sergey --- I tried to execute krusader with changed language variables. If I run it with the following command: LC_ALL=ru_RU.UTF-8 krusader then all path/file names back no normal behaviour. But LC_ALL changes all language settings to Russian, not only file names, but also menu, descriptions, etc. which I don't want to change. It's better sometimes to get messages and other things in English. That's why I have the following set: $ locale LANG=ru_RU.UTF-8 LC_CTYPE="ru_RU.UTF-8" LC_NUMERIC=C LC_TIME="ru_RU.UTF-8" LC_COLLATE="ru_RU.UTF-8" LC_MONETARY="ru_RU.UTF-8" LC_MESSAGES=C LC_PAPER="ru_RU.UTF-8" LC_NAME="ru_RU.UTF-8" LC_ADDRESS="ru_RU.UTF-8" LC_TELEPHONE="ru_RU.UTF-8" LC_MEASUREMENT="ru_RU.UTF-8" LC_IDENTIFICATION="ru_RU.UTF-8" LC_ALL= Executing krusader with LC_MESSAGES or LC_NUMERIC set to "ru_RU.UTF-8" doesn't help to solve strange symbols in names. It looks like krusader only knows LC_ALL and ignores other language variables. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371582] [2.5.0] Wrong representation of files and paths with Russian names (ru_RU.UTF-8)
https://bugs.kde.org/show_bug.cgi?id=371582 --- Comment #16 from Sergey --- I have never been in this menu. According to my experience it's bad practice to interfere there. I set everything long time ago inside /etc/ and other configs. Also time zone is set in config files long time ago using console. Once I tried to change in KDE4 settings my time zone or other thing and it was bad experience. It broke my "console" settings. Also I don't change things which work well. Well, in your example I see that "en_US.UTF-8" != "C". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 --- Comment #7 from Sergey --- 5.8.4 crashes th same way. on each resume from sleep. Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x73df49fb in KConfigGroupPrivate::fullName() const () from /usr/lib64/libKF5ConfigCore.so.5 (gdb) bt full #0 0x73df49fb in KConfigGroupPrivate::fullName() const () from /usr/lib64/libKF5ConfigCore.so.5 No symbol table info available. #1 0x73df3d79 in KConfigGroup::readEntry(char const*, QVariant const&) const () from /usr/lib64/libKF5ConfigCore.so.5 No symbol table info available. #2 0x0043209a in int KConfigGroup::readEntry(char const*, int const&) const () No symbol table info available. #3 0x0042fca5 in PanelView::restore() () No symbol table info available. #4 0x0042ff45 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () No symbol table info available. #5 0x7306680e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 No symbol table info available. #6 0x73072a48 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5 I don't know if it's still matches with my original report in Bug 372301 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 450136] New: No load tasks from google calendar
https://bugs.kde.org/show_bug.cgi?id=450136 Bug ID: 450136 Summary: No load tasks from google calendar Product: kalendar Version: 0.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: kostr...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- STEPS TO REPRODUCE 1. Load Kalendar 2. Add google account 3. See on Kalendar OBSERVED RESULT View tasks from google calendar EXPECTED RESULT Google calendar items not available. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION none. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466217] System monitor crashed when opening the Processes page
https://bugs.kde.org/show_bug.cgi?id=466217 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #1 from Sergey --- I just had a crash with very similar trace in kwin_x11 and before that plasmashell also crashed on QGuiApplication::topLevelWindows() -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467165] New: Wrong widgets positions after sleep on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=467165 Bug ID: 467165 Summary: Wrong widgets positions after sleep on dual screen setup Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kolo...@gmail.com Target Milestone: --- Created attachment 157176 --> https://bugs.kde.org/attachment.cgi?id=157176&action=edit Video STEPS TO REPRODUCE 1. Wait while the PC goes sleep and both screens goes off 2. Then wake it up, and see the widgets in the middle of two screens (but still on the main screen) Tooltips notifications about any widgets in tray goes to the second screen turn off and then trun on the first monitor fix positioning SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-12400 Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Product Name: B660M-ITX/ac ADDITIONAL INFORMATION Main screen is connected to DP Second screen to HDMI -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467738] New: input fields not working in Unreal Engine 5, but works in Gnome
https://bugs.kde.org/show_bug.cgi?id=467738 Bug ID: 467738 Summary: input fields not working in Unreal Engine 5, but works in Gnome Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kolo...@gmail.com Target Milestone: --- Created attachment 157543 --> https://bugs.kde.org/attachment.cgi?id=157543&action=edit UE5.1 input in some fields in the engine does not work, I tried to reinstall the system I can also say that the fields work in gnome wayland STEPS TO REPRODUCE 1. Just open UE5.1 and try to use the fields like in video SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch, last updates, 5.27.3, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467738] input fields not working in Unreal Engine 5, but works in Gnome
https://bugs.kde.org/show_bug.cgi?id=467738 --- Comment #4 from Sergey --- According to internet information, UE5 supports Wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477550] enable launch feedback make slower app startup or closing time
https://bugs.kde.org/show_bug.cgi?id=477550 Sergey changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #3 from Sergey --- Nate Graham, i have the same experience with every app almost, It would be easier to report applications in which this works correctly -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478196] New: Photo tags(labels) are not shown in the main viewing window.
https://bugs.kde.org/show_bug.cgi?id=478196 Bug ID: 478196 Summary: Photo tags(labels) are not shown in the main viewing window. Classification: Applications Product: digikam Version: 8.1.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: laryo...@mail.tomsknet.ru Target Milestone: --- Created attachment 163969 --> https://bugs.kde.org/attachment.cgi?id=163969&action=edit Here you can see that there are no photo tags. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch the program. 2. Go to any album. OBSERVED RESULT 3. There are no photo tags. EXPECTED RESULT 3. I want to see photo tags. SOFTWARE/OS VERSIONS Fedora Linux 39 (Workstation Edition) (GNOME 4) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478196] Add a note in online documentation about the items icon-view information not visible if thumbnails size is small.
https://bugs.kde.org/show_bug.cgi?id=478196 --- Comment #6 from Sergey --- 07.12.2023 15:29, bugzilla_nore...@kde.org пишет: > Note: if you wan to see tags under the thumbnails, go to digiKam / setup / > View > and turn on right options: I made this setup a long time ago. See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478196] Add a note in online documentation about the items icon-view information not visible if thumbnails size is small.
https://bugs.kde.org/show_bug.cgi?id=478196 --- Comment #7 from Sergey --- Hi Mike, 07.12.2023 15:54, Maik Qualmann пишет: > You have set the thumbnail size (slider) to the absolute minimum size (100). I didn't find a slider that sets this size on the viewing settings tab. However, I found commands in the menu to increase/decrease the size of thumbnails. After increasing the size of the thumbnails, the signatures appeared. I thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478196] Add a note in online documentation about the items icon-view information not visible if thumbnails size is small.
https://bugs.kde.org/show_bug.cgi?id=478196 --- Comment #9 from Sergey --- Hi, 07.12.2023 21:12, bugzilla_nore...@kde.org пишет: > The slider is on the bottom/right side, in the status bar. Thanks for the tip! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481850] New: plasmashell crash on drag'n'drop
https://bugs.kde.org/show_bug.cgi?id=481850 Bug ID: 481850 Summary: plasmashell crash on drag'n'drop Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: rion...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY *** If Qt compiled with asserts enabled then plasmashell crashes almost every time on drag'n'drop any icon on desktop. *** STEPS TO REPRODUCE 1. start dragging any *.desktop file on desktop OBSERVED RESULT get a crash on drop EXPECTED RESULT icon moved SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: Qt Version: 5.15.12 ADDITIONAL INFORMATION #0 0x7f0e6e6b1b1c in ??? () at /usr/lib64/libc.so.6 #1 0x7f0e6e663512 in raise () at /usr/lib64/libc.so.6 #2 0x7f0e70fe782d in KCrash::defaultCrashHandler(int) () at /usr/lib64/libKF5Crash.so.5 #3 0x7f0e6e6635b0 in () at /usr/lib64/libc.so.6 #4 0x7f0e6e6b1b1c in ??? () at /usr/lib64/libc.so.6 #5 0x7f0e6e663512 in raise () at /usr/lib64/libc.so.6 #6 0x7f0e6e64c4ed in abort () at /usr/lib64/libc.so.6 #7 0x7f0e6ec92d6d in QMessageLogger::fatal(char const*, ...) const () at /usr/lib64/libQt5Core.so.5 #8 0x7f0e6ec918d2 in qt_assert(char const*, char const*, int) () at /usr/lib64/libQt5Core.so.5 #9 0x7f0e6ecb24e8 in ??? () at /usr/lib64/libQt5Core.so.5 #10 0x7f0e600b8451 in Positioner::move(QList const&) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so #11 0x7f0e600946bf in Positioner::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so #12 0x7f0e600951f3 in Positioner::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so #13 0x7f0e704cb233 in ??? () at /usr/lib64/libQt5Qml.so.5 #14 0x7f0e703a55f9 in ??? () at /usr/lib64/libQt5Qml.so.5 #15 0x7f0e703a750b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib64/libQt5Qml.so.5 #16 0x7f0e703c3e92 in ??? () at /usr/lib64/libQt5Qml.so.5 #17 0x7f0e703c758f in ??? () at /usr/lib64/libQt5Qml.so.5 #18 0x7f0e703595ed in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib64/libQt5Qml.so.5 #19 0x7f0e704e60ad in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib64/libQt5Qml.so.5 #20 0x7f0e7049657f in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib64/libQt5Qml.so.5 #21 0x7f0e70497cd0 in ??? () at /usr/lib64/libQt5Qml.so.5 #22 0x7f0e704cad15 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib64/libQt5Qml.so.5 #23 0x7f0e659d in ??? () at /usr/lib64/libQt5Core.so.5 #24 0x7f0e600908fd in FolderModel::move(int, int, QList) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so #25 0x7f0e600a4588 in FolderModel::drop(QQuickItem*, QObject*, int, bool) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so #26 0x7f0e60094df3 in FolderModel::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so sometimes it also show this in the logs фев 26 11:45:42 rionpc plasmashell[83588]: ASSERT: "last < rowCount(parent)" in file /var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp, l> фев 26 11:45:42 rionpc plasmashell[83588]: 25 -- exe=/usr/bin/plasmashell фев 26 11:45:42 rionpc plasmashell[83588]: 13 -- platform=xcb фев 26 11:45:42 rionpc plasmashell[83588]: 11 -- display=:0 фев 26 11:45:42 rionpc plasmashell[83588]: 20 -- appname=plasmashell фев 26 11:45:42 rionpc plasmashell[83588]: 17 -- apppath=/usr/bin фев 26 11:45:42 rionpc plasmashell[83588]: 9 -- signal=6 фев 26 11:45:42 rionpc plasmashell[83588]: 10 -- pid=83588 фев 26 11:45:42 rionpc plasmashell[83588]: 19 -- appversion=5.27.10 фев 26 11:45:42 rionpc plasmashell[83588]: 19 -- programname=Plasma фев 26 11:45:42 rionpc plasmashell[83588]: 31 -- bugaddress=sub...@bugs.kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 484799] New: System Monitor crash after open app
https://bugs.kde.org/show_bug.cgi?id=484799 Bug ID: 484799 Summary: System Monitor crash after open app Classification: Applications Product: plasma-systemmonitor Version: 5.27.11 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: yesin...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 167976 --> https://bugs.kde.org/attachment.cgi?id=167976&action=edit bugreport Hello, system monitor not correct show font in application, several times i have crash after open app, help only reboot ADDITIONAL INFORMATION software version and about system attached to request https://ibb.co/9n3KQ3H https://ibb.co/L1dM88L https://ibb.co/HqvWv8c -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 484799] System Monitor crash after open app
https://bugs.kde.org/show_bug.cgi?id=484799 --- Comment #2 from Sergey --- Hello, vcard NVIDIA GeForce 315M integrated in laptop, the same problem also seen on radeon x1600 pro and several integrated intel hd. I'm Everyday use kde on pc with amd 5700xt vcard, sysmonitor show all correct. I think problem only for old vcards -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Sergey changed: What|Removed |Added CC||blese...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Sergey changed: What|Removed |Added Version|24.02.0 |24.02.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #57 from Sergey --- Is there similar report for X11? plasma panel crashes for all the time on hdmi connect plasmashell[1522]: ASSERT: "last < rowCount(parent)" in file /storage/gentoo/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-c2ea67ecefe049f6e9bb8f910d7f9c60319d8619/src/corelib/itemmodels/qabstractitemmodel.cpp, line 2815 #5 0x7f5659a71ac2 raise (libc.so.6 + 0x3dac2) #6 0x7f5659a5c449 abort (libc.so.6 + 0x28449) #7 0x7f5659ef7584 qt_message_fatal (libQt5Core.so.5 + 0xb8584) #8 0x7f5659ef38a6 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xb48a6) #9 0x7f5659eea244 _Z9qt_assertPKcS0_i (libQt5Core.so.5 + 0xab244) #10 0x7f565a1130cb _ZN18QAbstractItemModel15beginRemoveRowsERK11QModelIndexii (libQt5Core.so.5 + 0x2d40cb) #11 0x7f56442687db n/a (libfolderplugin.so + 0x417db) #12 0x7f565a192529 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x353529) #13 0x7f565a1d5ee2 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x396ee2) #14 0x7f565a1cf1e5 _ZN11QMetaObject8activateEP7QObjectPKS_iPPv (libQt5Core.so.5 + 0x3901e5) #15 0x7f565a11 _ZN18QAbstractItemModel20rowsAboutToBeRemovedERK11QModelIndexiiNS_14QPrivateSignalE (libQt5Core.so.5 + 0x2d9888) #16 0x7f565a11311e _ZN18QAbstractItemModel15beginRemoveRowsERK11QModelIndexii (libQt5Core.so.5 + 0x2d411e) #17 0x7f565a14382b _ZN28QSortFilterProxyModelPrivate21remove_proxy_intervalER7QVectorIiES2_iiRK11QModelIndexN2Qt11OrientationEb (libQt5Core.so.> #18 0x7f565a14376a _ZN28QSortFilterProxyModelPrivate19remove_source_itemsER7QVectorIiES2_RKS1_RK11QModelIndexN2Qt11OrientationEb (libQt5Core.so> #19 0x7f565a145c64 _ZN28QSortFilterProxyModelPrivate21handle_filter_changedER7QVectorIiES2_RK11QModelIndexN2Qt11OrientationE (libQt5Core.so.5 +> #20 0x7f565a145851 _ZN28QSortFilterProxyModelPrivate14filter_changedERK11QModelIndex (libQt5Core.so.5 + 0x306851) #21 0x7f565a14bc20 _ZN21QSortFilterProxyModel16invalidateFilterEv (libQt5Core.so.5 + 0x30cc20) #22 0x7f565a192529 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x353529) #23 0x7f565a1d5ee2 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x396ee2) #24 0x7f565a1cf1e5 _ZN11QMetaObject8activateEP7QObjectPKS_iPPv (libQt5Core.so.5 + 0x3901e5) #25 0x7f5644273c90 n/a (libfolderplugin.so + 0x4cc90) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455892] plasmashell crashes every 5-10 minutes
https://bugs.kde.org/show_bug.cgi?id=455892 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #1 from Sergey --- I believe I have the same crash. But for me it's every couple of seconds right after login. crashes on Q_ASSERT(from.isValid()); in QConcatenateTablesProxyModelPrivate::_q_slotDataChanged in qtbase-everywhere-src-5.15.5/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp I had to recompile qtcore without debug to disable asserts and now it's somewhat stable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449600] kf.kio.slaves.file copy() QUrl mode= 420 Cannot copy file (Errno: 38)
https://bugs.kde.org/show_bug.cgi?id=449600 Sergey changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #4 from Sergey --- (In reply to Ahmad Samir from comment #1) > Is this still an issue? Yes. It's still "Errno: 38" on files copying in both krusader and dolphin. SOFTWARE/OS VERSIONS kde-plasma/plasma-desktop-5.24.6-r2 kde-plasma/plasma-workspace-5.24.6 kde-frameworks/plasma-5.96.0-r1 dev-qt/qtcore-5.15.5-r2 ADDITIONAL INFORMATION kde-misc/krusader-2.7.2, kde-apps/dolphin-22.04.3. kde-frameworks/kio-5.96.0-r3, kde-apps/kio-extras-22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442229] New: KDEvelop crashes at attemt to create a new Qt project
https://bugs.kde.org/show_bug.cgi?id=442229 Bug ID: 442229 Summary: KDEvelop crashes at attemt to create a new Qt project Product: kdevelop Version: 5.6.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: cy6erg...@gmail.com Target Milestone: --- Application: kdevelop (5.6.1) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-59.19-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.3" -- Information about the crash: A project wizard gives me a chance to enter all the fields but crashes once I click Finish -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f7d0b7a74d0 in QQmlData::signalHasEndpoint(int) const (this=0x55c2f69069c0, index=7) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-4.2.1.x86_64/include/QtQml/5.12.7/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:370 #5 QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) (d=0x55c2f69069c0, index=7) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-4.2.1.x86_64/src/qml/qml/qqmlengine.cpp:900 #6 0x7f7d124536ea in QObjectPrivate::isDeclarativeSignalConnected(unsigned int) const (signal_index=7, this=) at kernel/qobject_p.h:267 #7 QMetaObject::activate(QObject*, int, int, void**) (sender=0x55c2f69001f0, signalOffset=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3672 #8 0x7f7d12453fcf in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff8f373dd0, r=0x55c2f69001f0, this=0x55c2f6910290) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #9 QMetaObject::activate(QObject*, int, int, void**) (sender=0x55c2f69069c0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3784 #10 0x7f7d124545c7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f7d1437e2e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3657 #11 0x7f7d13e52700 in QTextEdit::textChanged() (this=) at .moc/moc_qtextedit.cpp:543 #12 0x7f7d13e5853d in QTextEdit::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x55c2f69069c0, _c=, _id=, _a=0x7fff8f373f40) at .moc/moc_qtextedit.cpp:325 #13 0x7f7d12453eb5 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x55c2f690aeb0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3804 #14 0x7f7d124545c7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f7d14380040 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3657 #15 0x7f7d13e717b0 in QWidgetTextControl::textChanged() (this=) at .moc/moc_qwidgettextcontrol_p.cpp:501 #16 0x7f7d13e7dd55 in QWidgetTextControl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x55c2f690aeb0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=0, _a=_a@entry=0x7fff8f3740d0) at .moc/moc_qwidgettextcontrol_p.cpp:256 #17 0x7f7d13e7e245 in QWidgetTextControl::qt_metacall(QMetaObject::Call, int, void**) (this=0x55c2f690aeb0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff8f3740d0) at .moc/moc_qwidgettextcontrol_p.cpp:471 #18 0x7f7d12453f79 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x55c2f690af00, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3822 #19 0x7f7d124545c7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f7d135eac60 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3657 #20 0x7f7d13304ed3 in QTextDocument::contentsChanged() (this=) at .moc/moc_qtextdocument.cpp:393 #21 0x7f7d130493dc in QTextDocumentPrivate::finishEdit() (this=0x55c2f690b0c0) at text/qtextdocument_p.cpp:1245 #22 0x7f7d1304978c in QTextDocumentPrivate::endEditBlock() (this=) at text/qtextdocument_p.cpp:1200 #23 0x7f7d13078be4 in QTextCursor::endEditBlock() (this=this@entry=0x7fff8f374198) at text/qtextcursor.cpp:2534 #24 0x7f7d1308d8c1 in QSyntaxHighlighter::setDocument(QTextDocument*) (this=this@entry=0x55c2f6949250, doc=doc@entry=0x0) at text/qsyntaxhighlighter.cpp:341 #25 0x7f7d1308d9f9 in QSyntaxHighlighter::~QSyntaxHighlighter() (this=0x55c2f6949250, __in_chrg=) at text/qsyntaxhighlighter.cpp:323 #26 0x7f7cfd16a489 in Sonnet::Highlighter::~Highlighter() () at /usr/lib64/libKF5SonnetUi.so.5 #27 0x7f7d12451acb in QObjectPrivate::deleteChildren() (this=this@entry=0x55c2f69a91e0) at kernel/qobject.cpp:2017 #28 0x7f7d1245b66b in QObject::~QObject() (this=, __in_chrg=) at kern
[Skanlite] [Bug 444987] silent crash while searching for scanners
https://bugs.kde.org/show_bug.cgi?id=444987 Sergey changed: What|Removed |Added CC||svs1...@gmail.com --- Comment #3 from Sergey --- Try to remove .config/skanliterc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX
https://bugs.kde.org/show_bug.cgi?id=360033 --- Comment #52 from Sergey --- (In reply to kde.org from comment #51) > This issue report is quite old. Can you please confirm, that it still > persists with KDE 5.23? nVidia has stopped supporting such old generation of GPUs in the kernel. So, I decided to upgrade GPU and I no longer have such problem and I also don't have to use suggested patch above. But I didn't try to use old GPU with opensource video driver. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414834] Plasma crashes in QWaylandClientExtensionPrivate::handleRegistryGlobal() on Wayland when I change global theme
https://bugs.kde.org/show_bug.cgi?id=414834 --- Comment #96 from Sergey --- Unsubscribe On Mon, Nov 8, 2021 at 5:36 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=414834 > > Nate Graham changed: > >What|Removed |Added > > > CC| > |danailgeorgiev@protonmail.c >||om > > --- Comment #95 from Nate Graham --- > *** Bug 445122 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 416765] Cannout continue a multisession blu-ray disc
https://bugs.kde.org/show_bug.cgi?id=416765 Sergey changed: What|Removed |Added CC||progser...@gmail.com --- Comment #3 from Sergey --- Such problrm on ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 416765] Cannout continue a multisession blu-ray disc
https://bugs.kde.org/show_bug.cgi?id=416765 --- Comment #4 from Sergey --- Created attachment 151044 --> https://bugs.kde.org/attachment.cgi?id=151044&action=edit error continue multisession -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 443983] New: khelpcenter man:btrfs-replace(8)
https://bugs.kde.org/show_bug.cgi?id=443983 Bug ID: 443983 Summary: khelpcenter man:btrfs-replace(8) Product: khelpcenter Version: 5.7.6.21082 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: driv...@gmail.com Target Milestone: --- SUMMARY error in opening man page STEPS TO REPRODUCE 1. open Help 2. type "btrfs-replace" in search field and press enter 3. go to page "man:btrfs-replace(8)" OBSERVED RESULT Error dialog box EXPECTED RESULT man page SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440386] High CPU use of kwin_wayland when video playing in firefox
https://bugs.kde.org/show_bug.cgi?id=440386 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #9 from Sergey --- Google Chrome now suffers more from this problem consuming almost twice as much of Firefox. 14 (FF) and 26% (GC) on my MSI GL75 9SDK laptop. But if I monitor the CPU on semi-transparent Konsole with htop then it goes beyond 200% -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444226] New: Wayland: Some windows don't show up on the taskbar
https://bugs.kde.org/show_bug.cgi?id=444226 Bug ID: 444226 Summary: Wayland: Some windows don't show up on the taskbar Product: plasmashell Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: rion...@gmail.com Target Milestone: 1.0 While X11 Plasma session is terribly buggy and unusable starting from 5.23 I decided to switch to Wayland which is also not perfect but at least doesn't have graphical artifacts on the screen and doesn't crash all the Qt apps. So with Wayland one thing annoys me a lot: Not every application appears on the task bar. I tried to add another panel and tried to play with all the checkboxes in settings but those apps just do no appear. Even so their windows are visible and usable and also available by alt+tab and via "Windows list" widget. Also with X11 Plasma session I never had this issue (even so I had others like taskbar is always empty till next restart). So essentially only the problem seems to in some incompatibility of Wayland session and the taskbar. Examples of applications: Qt Creator, gvim STEPS TO REPRODUCE 1. Start Qt Creator OBSERVED RESULT Qt Creator works properly but absent on the taskbar EXPECTED RESULT All GUI apps are definitely visible on the taskbar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 ADDITIONAL INFORMATION Wrt my X11 problems, in my MSI GL75 9SDK laptop I have Nvidia video card and proprietary driver 495.29.05-r1. I also tried 470.74 just to check if X11 Plasma session would become stable but it didn't. It reports "qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found." for every Qt app but somehow starts plasmashell anyway even being Qt based. I would be happy to return to X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444226] Wayland: Some windows don't show up on the taskbar
https://bugs.kde.org/show_bug.cgi?id=444226 --- Comment #1 from Sergey --- And yes being a programmer I could fix it myself if one can just point me to the right direction. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 441665] New: Button "Setup a NAP network" in bluetooth connection settings does nothing.
https://bugs.kde.org/show_bug.cgi?id=441665 Bug ID: 441665 Summary: Button "Setup a NAP network" in bluetooth connection settings does nothing. Product: Bluedevil Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rion...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I was trying to figure out how to share my PC internet to a mobile device via bluetooth when I found how it's done with Blueman. I guess Setup a NAP (in my Russian ui I see it like: Настроить сеть NAP..) button does exactly the same in KDE/bluedevil but unfortunaely when I click it nothings happens (not even in logs). I guess bluedevil silently drops my attempts because of some problems and it's hard to say which ones. Also my paired Android device (where I want to reach the internet via bluetooth) doesn't habe "Use for internet" checkbox on the bluetooth connection to my pc. Some other connections have the option (for exmaple between two my android phones) It's on Gentoo system net-wireless/bluez compiled with next USE flag: cups, experimental, mesh, obex, readline, systemd, udev, user-session In NM applet settings has some auto-created NAP network, but I can't do anything with it. It's jus marked as never used. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 441665] Button "Setup a NAP network" in bluetooth connection settings does nothing.
https://bugs.kde.org/show_bug.cgi?id=441665 --- Comment #2 from Sergey --- Created attachment 141131 --> https://bugs.kde.org/attachment.cgi?id=141131&action=edit screenshot of bluetooth connection settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440276] New: I am setting the brightness in the power saving settings for battery operation. After a reboot, this setting does not work. Those. this setting only works until reboot
https://bugs.kde.org/show_bug.cgi?id=440276 Bug ID: 440276 Summary: I am setting the brightness in the power saving settings for battery operation. After a reboot, this setting does not work. Those. this setting only works until reboot Product: Powerdevil Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: svs1...@gmail.com Target Milestone: --- SUMMARY I am setting the brightness in the power saving settings for battery operation. After a reboot, this setting does not work. Those. this setting only works until reboot STEPS TO REPRODUCE 1. set brightness for work on battery 2. reboot 3. disconnect power OBSERVED RESULT brightness become minimum EXPECTED RESULT brightness should be as you set in point 1 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE NEON 5.22 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438707] New: System Settings Crashes after changing task switcher visualisation to anything. Wayland
https://bugs.kde.org/show_bug.cgi?id=438707 Bug ID: 438707 Summary: System Settings Crashes after changing task switcher visualisation to anything. Wayland Product: systemsettings Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sergeymokhovm...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.0) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.10-arch1-1 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: I had 4 windows open, one og them is "System Settings". I go to Window Management > Task Switcher > Main > Change Visualisation to anything else in dropdown (I tried most of them, for example "Compact") This is freshly installed system, I have not installed much packages yet. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7fbd100f0260 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /usr/lib/libQt5WaylandClient.so.5 #5 0x7fbd100d4f39 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /usr/lib/libQt5WaylandClient.so.5 #6 0x7fbd100fab26 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /usr/lib/libQt5WaylandClient.so.5 #7 0x7fbd0db26acd in ?? () from /usr/lib/libffi.so.7 #8 0x7fbd0db2603a in ?? () from /usr/lib/libffi.so.7 #9 0x7fbd10059fe4 in ?? () from /usr/lib/libwayland-client.so.0 #10 0x7fbd10056563 in ?? () from /usr/lib/libwayland-client.so.0 #11 0x7fbd10057cac in wl_display_dispatch_queue_pending () from /usr/lib/libwayland-client.so.0 #12 0x7fbd100d448d in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/libQt5WaylandClient.so.5 #13 0x7fbd129153f0 in ?? () from /usr/lib/libQt5Core.so.5 #14 0x7fbd12918880 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #15 0x7fbd1291908d in QSocketNotifier::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7fbd134c4d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7fbd128de00a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x7fbd1293784e in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7fbd104ae10c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x7fbd10501b99 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x7fbd104ab871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x7fbd12936c36 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7fbd128dc97c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #24 0x7fbd128e4ee4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #25 0x556bbf454954 in ?? () #26 0x7fbd1226ab25 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x556bbf4556be in ?? () [Inferior 1 (process 8540) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438810] New: Fault in design
https://bugs.kde.org/show_bug.cgi?id=438810 Bug ID: 438810 Summary: Fault in design Product: plasmashell Version: 5.22.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: skoval...@ukr.net Target Milestone: 1.0 Created attachment 139440 --> https://bugs.kde.org/attachment.cgi?id=139440&action=edit You can see how the bug looks like SUMMARY STEPS TO REPRODUCE 1. Select and copy reasonably large text 2. Go to Klipper 3. Select the clip you've just copied OBSERVED RESULT Icons on the clip are not aligned EXPECTED RESULT The icons don't go beyond borders SOFTWARE/OS VERSIONS Windows: macOS: OpenSuse Tumbleweed Linux/KDE Plasma: kernel 5.12.9-1/5.22.0 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437140] New: Start new game always start game # 0. Should start random.
https://bugs.kde.org/show_bug.cgi?id=437140 Bug ID: 437140 Summary: Start new game always start game # 0. Should start random. Product: kmahjongg Version: 0.9.21040 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: svs1...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. launch kmahjongg 2. start new game 3. start new game again OBSERVED RESULT should start random number instead of the same #0 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kde neon 5.21.5 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 437140] Start new game always start game # 0. Should start random.
https://bugs.kde.org/show_bug.cgi?id=437140 --- Comment #1 from Sergey --- Created attachment 138447 --> https://bugs.kde.org/attachment.cgi?id=138447&action=edit screenshot of bug -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427821] Crashed while updating "Themes" addons in Discover
https://bugs.kde.org/show_bug.cgi?id=427821 Sergey changed: What|Removed |Added CC||skoval...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430423] Missing (custom?) data meet.google.com data field when receiving calendar invites from Google Calendar
https://bugs.kde.org/show_bug.cgi?id=430423 Sergey changed: What|Removed |Added CC||svs1...@gmail.com --- Comment #1 from Sergey --- plasma 5.21.4 nothing changed - can't use korganizer without link to meet -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424592] Sidebarview does not render after suspend
https://bugs.kde.org/show_bug.cgi?id=424592 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #6 from Sergey --- Exactly the same problem for me nvidia-driver 450.57 in PRIME mode. So basically nvidia is always enabled and renders everything. (Intel can't render on second monitor, so I don't use it). Even being black the sidebar is still clickable, but it's totally black all the time. 100% reproducible. always after resume but never after reboot. parameters passed to nvidia kernel module: options nvidia \ NVreg_DeviceFileGID=27 \ NVreg_DeviceFileMode=432 \ NVreg_DeviceFileUID=0 \ NVreg_ModifyDeviceFiles=1 \ NVreg_PreserveVideoMemoryAllocations=1 \ NVreg_TemporaryFilePath=/tmp nvidia suspend/resume systemd services are enabled and according to the logs are properly executed. restarting plasma settings has no any effect on this problem. disabling dekstop effects support has no any effect on this problem. playing with effects renderer selection has no any effect on this problem. changing different windows decorations/widgets style etc has no any effect on this problem. I often update my gentoo system and probably the problem was first time noticed not more than a month ago. plasma 5.19.4 qt 5.15.0 kernel 5.7.11 nvidia GeForce GTX 1660 Ti Mobile btw Google Chrome usually also has problems with resume. But restarting it helps. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424592] Sidebarview does not render after suspend
https://bugs.kde.org/show_bug.cgi?id=424592 --- Comment #7 from Sergey --- I confirm the relevance to https://bugs.kde.org/show_bug.cgi?id=424311 After downgrading nvdia-driver to 440.100 I don't see the black sidebar after resume anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 Sergey changed: What|Removed |Added CC||rion...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474836] plasma crash
https://bugs.kde.org/show_bug.cgi?id=474836 --- Comment #2 from Sergey --- Created attachment 162178 --> https://bugs.kde.org/attachment.cgi?id=162178&action=edit New crash information added by DrKonqi plasmashell (5.27.6) using Qt 5.15.8 Since the first version of Plasma5 FreeBSD plasmashell5 has always crashed unexpectedly after about 5 minutes of use for about 9 years. I always start it manually again. I didn't notice any pattern leading to crash of the plasma shell, only one thing - active use of the interface. -- Backtrace (Reduced): -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474836] plasma crash
https://bugs.kde.org/show_bug.cgi?id=474836 Sergey changed: What|Removed |Added CC||sa...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477550] New: enable launch feedback make slower app startup or closing time
https://bugs.kde.org/show_bug.cgi?id=477550 Bug ID: 477550 Summary: enable launch feedback make slower app startup or closing time Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kolo...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Try to enable - disable it , to see the difference Operating System: openSUSE Tumbleweed 20231124 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-12400 Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 730 Product Name: B660M-ITX/ac -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477550] enable launch feedback make slower app startup or closing time
https://bugs.kde.org/show_bug.cgi?id=477550 --- Comment #1 from Sergey --- Created attachment 163497 --> https://bugs.kde.org/attachment.cgi?id=163497&action=edit Video how it works now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448844] [NVIDIA Wayland] Panel stops visually updating after some time, but remains functional and interactive
https://bugs.kde.org/show_bug.cgi?id=448844 Sergey changed: What|Removed |Added CC||kolo...@gmail.com --- Comment #14 from Sergey --- same here, 545 driver, they said it should fix wayland but its not Operating System: openSUSE Tumbleweed 20231102 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-12400 Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Manufacturer: ASRock Product Name: B660M-ITX/ac -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 463191] New: Elisa wakes up the screen.
https://bugs.kde.org/show_bug.cgi?id=463191 Bug ID: 463191 Summary: Elisa wakes up the screen. Classification: Applications Product: Elisa Version: 22.12.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: sch...@sche91.ru Target Milestone: --- SUMMARY *** Elisa wakes up the screen from either fading (decrease brightness) or power saving (zero brightness) upon switching to a next track when one track is finished. *** STEPS TO REPRODUCE 1. Install Elisa, start any song, set up screen power saving for a time shorter than the song's duration. 2. Wait for a screen to decrease backlight or turn it off due to power saving settings. 3. Watch as Elisa wakes it up, when a song ends and it switches to a next one. EXPECTED RESULT Music player shouldn't wake up a screen. ADDITIONAL INFORMATION I run Debian 11 Sid + Plasma (X11) on my Dell M4800. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #31 from Sergey --- I don't remember when last time it was reproducible for me on Gentoo Linux (always fresh). But I noticed another problem. I have dualboot with Windows and sometimes after rebooting from Windows to Gentoo my laptop display is disabled. I have to press Fn key to change display configuration. And I'm lucky enough if the second monitor is connected when it happens (at least I see where I switch to). Otherwise just black screen and seems nothing can change it (I tried backlight Fn keys and Ctrl+Alt+N). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #51 from Sergey --- I don't know if it's related or not. but with recent updates (kscreen/locker 5.19.3, nvidia drivers 450.57) ctrl+alt+L does not show lock screen anymore, instead it makes everything untouchable but still visible. But as always killing kscreenlocker_greet helps (after entering password everything works well). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449600] New: kf.kio.slaves.file copy() QUrl mode= 420 Cannot copy file (Errno: 38)
https://bugs.kde.org/show_bug.cgi?id=449600
Bug ID: 449600
Summary: kf.kio.slaves.file copy() QUrl mode= 420 Cannot copy
file (Errno: 38)
Product: frameworks-kio
Version: 5.88.0
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Overwrite dialog
Assignee: kio-bugs-n...@kde.org
Reporter: energumenos...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
***
I can't neither copy nor move files in neither Krusader nor Dolphin because of
new bug introduction somewhere inside kf.kio.slaves.file.
***
STEPS TO REPRODUCE
1. Run Krusader or Dolphin in Konsole.
2. Try to Copy or Move file from one path to another.
3. It gives me in console:
kf.kio.slaves.file: copy() QUrl("file:///home/incoming/1/111/filename.webm") to
QUrl("file:///mnt/f/inc2/ExamplePath/filename.webm") mode= 420.
OBSERVED RESULT
I also see popup window: Cannot copy file from
/home/incoming/1/111/filename.webm to /mnt/f/inc2/ExamplePath/filename.webm
(Errno: 38)
EXPECTED RESULT
I wanna Copy and Move files without any problems in Krusader and Dolphin. Usual
cp, mv in Konsole under Plasma works fine ATM.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kde-plasma/plasma-desktop-5.23.5
(available in About System)
KDE Plasma Version: kde-plasma/plasma-workspace-5.23.5
KDE Frameworks Version: kde-frameworks/plasma-5.88.0-r3
Qt Version: dev-qt/qtcore-5.15.2-r14
ADDITIONAL INFORMATION
kde-misc/krusader-2.7.2, kde-apps/dolphin-21.08.3.
kde-frameworks/kio-5.88.0-r2, kde-apps/kio-extras-21.08.3-r1.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 449600] kf.kio.slaves.file copy() QUrl mode= 420 Cannot copy file (Errno: 38)
https://bugs.kde.org/show_bug.cgi?id=449600 Sergey changed: What|Removed |Added CC||energumenos...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 408137] QCA::TLS handshaken is emitted with a broken certificate instance leading to a crash
https://bugs.kde.org/show_bug.cgi?id=408137 Sergey changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Sergey --- Well since I took maintainership of QCA fork, I tried to review it myself. But all the code looks pretty valid for me. Moreover original the reporter told me it didn't crash for him for awhile. And same for me. So likely it's neither QCA or Psi problem. It's something else. I'm closing this issue since there is nothing more to investigate and it's better to have a coredump from debug version next time. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 392054] qca fails to compile against openssl-1.1 without deprecated features
https://bugs.kde.org/show_bug.cgi?id=392054 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #3 from Sergey --- I fixed this in my fork. Not sure when it will be merged back to upstream. But if interesting https://github.com/psi-im/qca -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 425178] Docker is spewing UdevQt: unhandled device action "move"
https://bugs.kde.org/show_bug.cgi?id=425178 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #2 from Sergey --- I see the same in a regular Qt GUI application without docker. But docker works on the same machine for other tasks. wrt USB I have only USB wireless mouse and whatever built-in into my MSI GL75 9SDK laptop. Last time I saw it, my dmesg was populated with next entries approximately the same time: [234633.368717] docker0: port 1(veth3446d1d) entered disabled state [234633.368939] vethbed7499: renamed from eth0 [234633.395120] docker0: port 1(veth3446d1d) entered disabled state [234633.398863] device veth3446d1d left promiscuous mode [234633.398867] docker0: port 1(veth3446d1d) entered disabled state -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 429639] Strongswan connection editor adds an empty certificate parameter
https://bugs.kde.org/show_bug.cgi?id=429639 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #1 from Sergey --- same problem for me and same workaround. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434400] New: program crash !
https://bugs.kde.org/show_bug.cgi?id=434400 Bug ID: 434400 Summary: program crash ! Product: kdenlive Version: 20.12.3 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: youwi...@mail.ru Target Milestone: --- SUMMARY program crash ! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434429] New: Manage Cashe Data
https://bugs.kde.org/show_bug.cgi?id=434429 Bug ID: 434429 Summary: Manage Cashe Data Product: kdenlive Version: 20.12.3 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: youwi...@mail.ru Target Milestone: --- SUMMARY Manage Cashe Data not workin. Nothing is removed, including "qmlcache" This problem in all versions, including 20.12.3A SOFTWARE/OS VERSIONS Linux Mint 18.3 Sylvia x86_64 Kernel: 4.15.0-39-generic DE: XFCE KDE Frameworks 5 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419945] Crash on drag'n'drop random executable on applications starter menu widget
https://bugs.kde.org/show_bug.cgi?id=419945 --- Comment #3 from Sergey --- I tried to reproduce a few times with recent software. seems to be not reprodusible -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #16 from Sergey --- it happended again. so no miracles. it's still broken. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #24 from Sergey --- agreed with Holger -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #17 from Sergey --- I just compared ~/.local/share/kscreen/56e40e2cebeace281ad87eb77d19cacd with and without the bug. The only difference is in the offset of my second monitor. It's set to 0 when has to be 1920. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #18 from Sergey --- any developers here? any idea what code can I check to try to fix? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #19 from Sergey --- same problem with openSUSE Tumbleweed kscreen-5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372666] Selection in konsole is slow
https://bugs.kde.org/show_bug.cgi?id=372666 Sergey changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Sergey --- Just tried print a bunch of huge links and then select them. Works fast enough with 17.12.3. I guess it was fixed. PS do you know if kscreen developers are still alive? it's terribly broken on resume from sleep with some monitors. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 408137] New: QCA::TLS handshaken is emitted with a broken certificate instance leading to a crash
https://bugs.kde.org/show_bug.cgi?id=408137 Bug ID: 408137 Summary: QCA::TLS handshaken is emitted with a broken certificate instance leading to a crash Product: qca Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: rion...@gmail.com CC: br...@frogmouth.net, jus...@karneges.com Target Milestone: --- The above was noticed with Psi instant messenger on wakeup from sleep. On handshaken() it tries to tls->peerCertificateChain().primary(); Crashes in copy constructor of QCA::Certificate #6 0x7f29cb340af9 in QCA::Algorithm::operator=(QCA::Algorithm const&) () from /usr/lib/libqca-qt5.so.2 #7 0x7f29cb341d35 in QCA::Algorithm::Algorithm(QCA::Algorithm const&) () from /usr/lib/libqca-qt5.so.2 #8 0x7f29cb32f502 in QCA::Certificate::Certificate(QCA::Certificate const&) () from /usr/lib/libqca-qt5.so.2 #9 0x5630b910b153 in CertificateHelpers::checkCertificate(QCA::TLS*, XMPP::QCATLSHandler*, QString&, QByteArray&, QObject*, QString const&, QString const&) () #10 0x5630b8d42f62 in PsiAccount::tls_handshaken() () #11 0x5630b8c8ca07 in ?? () #12 0x7f29c33981d7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0x7f29c33981d7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #14 0x7f29cb372522 in QCA::TLS::Private::processNextAction() () from /usr/lib/libqca-qt5.so.2 #15 0x7f29cb36c776 in ?? () from /usr/lib/libqca-qt5.so.2 #16 0x7f29c33981d7 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x7f29c3398a3b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x7f29c3898da4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7f29c38a03c1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #20 0x7f29c336d849 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #21 0x7f29c33c1d15 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 Assuming certicate chain can't be empty in this case it's likely the chain has a certificate with some dangling pointers. Note Psi handles this in the same thread and there is no any Qt::QueuedConnection (it's visible from the stack above). I currently can't provide more details except it happened on Manjaro Linux 18.0.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] New: digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 Bug ID: 412417 Summary: digikam fails to start - update fails Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Sqlite Assignee: digikam-bugs-n...@kde.org Reporter: laryo...@mail.tomsknet.ru Target Milestone: --- SUMMARY After updating the OS to OpenSUSE 15.1, digikam stopped working: it tries to update its database from version 8 to 10, but after updating to 9 update to 10 fails. STEPS TO REPRODUCE 1. Have digikam installed on OpenSUSE 41.2 2. Update OS to OpenSUSE 15.1 3. Try to run digikam OBSERVED RESULT After launching it in command prompt: > digikam digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QSQLITE" DB Core Name: "/mnt/nas4free/Album/digikam4.db" DB Thumbs Name: "/mnt/nas4free/Album/thumbnails-digikam.db" DB Face Name: "/mnt/nas4free/Album/recognition.db" DB Similarity Name: "/mnt/nas4free/Album/similarity.db" Connect Options: "" Host Name:"" Host port:-1 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 8 digikam.coredb: Core database: makeUpdates 8 to 10 digikam.coredb: Core database: success updating to version 9 digikam.coredb: Core database: success updating to version 9 digikam.dbengine: Failure executing query: "" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV9ToV10" ] Statement [ "DROP TABLE IF EXISTS ImageHaarMatrix;" ] digikam.coredb: Core database: schema update to V 10 failed! digikam.dbengine: Failure executing query: "REPLACE INTO Settings VALUES (?,?);" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: (QVariant(QString, "DBVersion"), QVariant(QString, "9")) digikam.dbengine: Failure executing query: "REPLACE INTO Settings VALUES (?,?);" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: (QVariant(QString, "DBVersionRequired"), QVariant(QString, "5")) digikam.coredb: Core database: cannot process schema initialization KMemoryInfo: Platform identified : "LINUX" KMemoryInfo: TotalRam: 8387072000 digikam.general: Allowing a cache size of 200 MB QThreadStorage: Thread 0x7f8a64baec40 exited after QThreadStorage 12 destroyed EXPECTED RESULT digikam runs SOFTWARE/OS VERSIONS OpenSUSE 15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 --- Comment #4 from Sergey --- > You have no write permission to the database file. I did on the server: nas4free: Album# ls -l digikam4.db -rwxrw-r-- 1 lary admin 42672128 Sep 11 21:24 digikam4.db nas4free: Album# chmod 0666 digikam4.db nas4free: Album# chown lary:users digikam4.db And: nas4free: Album# chmod 0666 thumbnails-digikam.db nas4free: Album# chmod 0666 recognition.db nas4free: Album# chmod 0666 Thumbs.db nas4free: Album# chown lary:users thumbnails-digikam.db recognition.db Thumbs.db Digikam program behavior has changed, but it still did not work: digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV9ToV10" ] Statement [ "DROP TABLE IF EXISTS ImageHaarMatrix;" ] digikam.coredb: Core database: schema update to V 10 failed! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 --- Comment #5 from Sergey --- > the SQLite databases should reside on a fast local drive. How can I specify a new database location before (!) Launching the program? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410315] New: reviews: show preview of review, outline selected review as Adobe Acrobat reader does
https://bugs.kde.org/show_bug.cgi?id=410315 Bug ID: 410315 Summary: reviews: show preview of review, outline selected review as Adobe Acrobat reader does Product: okular Version: 1.6.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: srg...@gmail.com Target Milestone: --- current - https://imgur.com/HJyorWm expected (how Acrobat reader shows reviews/highlightments) - https://imgur.com/fT25xys Summary: 1. current - the review content is not previewed in sidebar widget, but only "Highlight" or "Highlight with comment" expected - for hightlight without comment - dont preview anything (or maybe preview first words of highlighted text), for hightlight with comment - preview comment content and make it editable (or maybe preview comment AND first words of hightlighted text) 2. current - when highlightment is selected (from sidebar widget) the highlightment is not outlined expected - when highlightment is selected (from sidebar widget) the highlightment is outlined -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 411245] New: Unable to create io-slave
https://bugs.kde.org/show_bug.cgi?id=411245 Bug ID: 411245 Summary: Unable to create io-slave Product: okular Version: 1.7.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: pisnicser...@gmail.com Target Milestone: --- OVERVIEW Sad experience - i lost my annotations for two chapters from a book. STEPS TO REPRODUCE i opened a book in okular and was adding annotations without intermediate save during several hours. When i wanted to close book and save it, got error message and empty file listing in directory about to save (this should be the hint) OBSERVED RESULT Error while trying to save document with added annotations to ".okular" archive. Error message: "Unable to create io-slave. Can not create socket for launching io-slave for protocol 'file'..." EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/Ubuntu 18.04.2 LTS ADDITIONAL INFORMATION i understand this may be related to system side bug, when app is not able to list files in directory, but the app itself may resist in this scenario by knowing destination file path only -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Sergey changed: What|Removed |Added CC||rion...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 --- Comment #20 from Sergey --- I found it easier to have a small script with xrandr --output LVDS-1 --primary --auto --left-of HDMI-2 so after resume I can press alt+f2 and start it. In other words this bug is not that critical for me anymore. Probably I'll just update my script to start this script once per 10 secs. So it won't require any manual actions. It will solve the problem completely. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #21 from Sergey ---
xrandr shell script seems to work good.
Bug I just rewrote it based on this
https://askubuntu.com/questions/183516/how-do-i-detect-when-my-system-wakes-up-from-suspend-via-dbus-or-similar-in-a-py
def handle_sleep_callback(sleeping):
if not sleeping:
os.system("sleep 5; xrandr --output LVDS-1 --primary --auto --left-of
HDMI-2")
If I notice any issues I'll report back.
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 Sergey changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #22 from Sergey --- seems to be the same https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1573345 wrt my scripts no issues so far. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 400598] New: Akregator crashes when closing tab
https://bugs.kde.org/show_bug.cgi?id=400598 Bug ID: 400598 Summary: Akregator crashes when closing tab Product: akregator Version: 5.9.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: skoval...@ukr.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open an article in internal browser 2. Close the tab with the article 3. Click anywhere in the program OBSERVED RESULT Akregator crashes EXPECTED RESULT Akregator is still working SOFTWARE VERSIONS 5.9.1 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50 Qt Version: 5.11.1 ADDITIONAL INFORMATION Fedora 29 In Fedora 28 Akregator worked fine. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 400800] New: screenlock's password field doesn't receive focus
https://bugs.kde.org/show_bug.cgi?id=400800 Bug ID: 400800 Summary: screenlock's password field doesn't receive focus Product: ksmserver Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ui Assignee: unassigned-b...@kde.org Reporter: rion...@gmail.com Target Milestone: --- SUMMARY After resume from sleep password field is not focused and it's impossible to set focus on it neither with keyboard nor mouse. Though I can click on other elements. For example "eye" button or unlock button. STEPS TO REPRODUCE 1. put computer to sleep (with lid close for example) 2. resume and see lock screen 3. try to enter password or at least focus password field OBSERVED RESULT Impossible to set focus on password field under no circumstances. EXPECTED RESULT Possible to focus password and enter it. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: Qt Version: 5.11.2 ksmserver: 0.4 OS: openSUSE Tumbleweed with latest updates ADDITIONAL INFORMATION I have a script in autostart settings which does "sleep 5; xrandr --output LVDS-1 --primary --auto --left-of HDMI-2" on resume. It's a workaround for some X11 or KScreen bug which are unable to properly restore my displays configuration. I don't know if it can have some impact related to this problem. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 400800] screenlock's password field doesn't receive focus
https://bugs.kde.org/show_bug.cgi?id=400800 --- Comment #1 from Sergey --- also sometimes I can enter password even w/o password dialog which is drawn only on my right screen (depending on mouse position). It looks like nothing on the screen but I anyway can unlock it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400914] New: Plasma crashed after moving the Network Monitor widget.
https://bugs.kde.org/show_bug.cgi?id=400914 Bug ID: 400914 Summary: Plasma crashed after moving the Network Monitor widget. Product: plasmashell Version: 5.8.7 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sergb...@yandex.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.159-73-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I was moving the Network Monitor widget. Screen freezed when it overlapped with system tray widget, then crash happened. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffae3058900 (LWP 1536))] Thread 10 (Thread 0x7ff9d9ffa700 (LWP 32422)): #0 0x7ffadc55f33d in read () at /lib64/libc.so.6 #1 0x7ffad8c53750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffad8c12e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffad8c132a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ffad8c1342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ffadce7016b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ffadce1dbbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ffadcc58f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ffadff523d8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7ffadcc5d9e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7ffadbd69724 in start_thread () at /lib64/libpthread.so.0 #11 0x7ffadc56be8d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff9fa413700 (LWP 13525)): #0 0x7ffadc578280 in pthread_mutex_lock () at /lib64/libc.so.6 #1 0x7ffad1b6650e in pa_mutex_lock () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7ffad21cf08b in () at /usr/lib64/libpulse.so.0 #3 0x7ffad21c074c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #4 0x7ffad21c0dbe in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #5 0x7ffad21c0e70 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #6 0x7ffad21cefe6 in () at /usr/lib64/libpulse.so.0 #7 0x7ffad1b673f8 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #8 0x7ffadbd69724 in start_thread () at /lib64/libpthread.so.0 #9 0x7ffadc56be8d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ffa0bfff700 (LWP 13524)): #0 0x7ffadc56330d in poll () at /lib64/libc.so.6 #1 0x7ffad8c13314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffad8c1342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffadce7016b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ffadce1dbbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffadcc58f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ffadff523d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7ffadcc5d9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ffadbd69724 in start_thread () at /lib64/libpthread.so.0 #9 0x7ffadc56be8d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7ffa11132700 (LWP 1829)): #0 0x7ffadc56330d in poll () at /lib64/libc.so.6 #1 0x7ffad8c13314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffad8c1342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffadce7016b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ffadce1dbbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffadcc58f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ffa125598f7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7ffadcc5d9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ffadbd69724 in start_thread () at /lib64/libpthread.so.0 #9 0x7ffadc56be8d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7ffa23cc6700 (LWP 1729)): #0 0x7ffad8c548b0 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ffad8c12950 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffad8c13230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffad8c1342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ffadce7016b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ffadce1dbbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ffadcc58f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ffae0ad6822 in () at /usr/lib64/libQt5Qui
[plasmashell] [Bug 386035] SDDM Loginscreen is black
https://bugs.kde.org/show_bug.cgi?id=386035 Sergey changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||rion...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Sergey --- This looks similar to what I experience Also an laptop with Intel and nvidia. sddm shows black screen but I still can type my password and login. After I logged in everything works fine. If I connect additional monitor, then usually I see the login prompt just on it while laptop display is black. I guess sddm uses X configuration and probably there is something wrong it, while after login some xrandr magic fixes displays configuration. In any case, showing the black screen is hardly a good option something is wrong with X config unless something is really terribly wrong. KDE 5.18.5, Gentoo Linux. $ cat /etc/X11/xorg.conf # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 440.82 # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 440.82 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 Inactive "InactiveDevice1" Inactive "InactiveDevice1" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" Option "Xinerama" "0" EndSection Section "Files" EndSection Section "InputDevice" # generated from data in "/etc/conf.d/gpm" Identifier "Mouse0" Driver "mouse" Option "Protocol" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection #Section "Monitor" #Identifier "Monitor0" #VendorName "Unknown" #ModelName "LG Electronics LG ULTRAWIDE" #HorizSync 30.0 - 90.0 #VertRefresh 56.0 - 75.0 #Option "DPMS" #EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1660 Ti" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "InactiveDevice1" Driver "modesetting" VendorName "Unknown" EndSection Section "Device" Identifier "InactiveDevice1" Driver "modesetting" VendorName "Unknown" EndSection Section "Screen" Identifier "Screen0" Device "Device0" #Monitor"Monitor0" DefaultDepth24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-0" Option "metamodes" "nvidia-auto-select +1920+0" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" Option "AllowEmptyInitialConfiguration" "True" SubSection "Display" Depth 24 EndSubSection EndSection $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x1b8 cap: 0x1, Source Output crtcs: 4 outputs: 3 associated providers: 1 name:NVIDIA-0 Provider 1: id: 0x1e3 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 1 associated providers: 1 name:modesetting -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #45 from Sergey --- 5.18.4.1 is still broken As far as I know kscreenlocker auto restarts when killed and after that starts working properly (the screen will still be locked but at least it's possible to login). Does anyone have a systemd system resume hook auto-kill kscreenlocker? Maybe something like this (not tested) [Unit] Description=KScreenLocker resume killer After=systemd-suspend.service After=systemd-hibernate.service [Service] Type=oneshot ExecStart=/bin/killall -9 "kscreenlocker_greet" [Install] RequiredBy=systemd-suspend.service RequiredBy=systemd-hibernate.service -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #46 from Sergey --- Created attachment 127682 --> https://bugs.kde.org/attachment.cgi?id=127682&action=edit qdbus org.kde.KWin /KWin supportInformation For me the problem is not about CPU but black screen after system resume from stand-by. Happens randomly. I tried to type my password blindly but the screen wasn't unlocked so I believe the thread accepting input got stuck. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #47 from Sergey --- after some testing QSG_RENDER_LOOP=basic seems to be the perfect workaround. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 375455] Processes usage doesn't sum up to total CPU usage.
https://bugs.kde.org/show_bug.cgi?id=375455 Sergey changed: What|Removed |Added CC||skoval...@ukr.net --- Comment #11 from Sergey --- I can confirm that for Fedora 28-31, OpenSUSE 15-15.1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418393] New: gwenview doesn't rotate video if metadata contains rotation
https://bugs.kde.org/show_bug.cgi?id=418393 Bug ID: 418393 Summary: gwenview doesn't rotate video if metadata contains rotation Product: gwenview Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: svs1...@gmail.com Target Milestone: --- SUMMARY gwenview doesn't rotate video if metadata contains rotation STEPS TO REPRODUCE 1. make any video using portrait orientation 2. display the video using gwenview 3. metadata contains rotation 90 but gwenview doesn't use it and play video in landscape orientation rotated 90 degree. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418489] New: Dolphin xdg folder paths do not match with ones in plasma settings
https://bugs.kde.org/show_bug.cgi?id=418489 Bug ID: 418489 Summary: Dolphin xdg folder paths do not match with ones in plasma settings Product: dolphin Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: rion...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin xdg folder paths (on the side panel) do not match with ones in plasma settings->applications->paths STEPS TO REPRODUCE 1. change some paths with xdg-user-dirs-update / create new directories if required 2. relogin / reboot 3. check plasma settings/ new directories will be there. 4. try to click to folder on dolphin's side panel. It still tries to open old paths. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418489] Dolphin xdg folder paths do not match with ones in plasma settings
https://bugs.kde.org/show_bug.cgi?id=418489 Sergey changed: What|Removed |Added Platform|Other |Ubuntu Packages --- Comment #1 from Sergey --- It's on Ubuntu 19.10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418489] Dolphin xdg folder paths do not match with ones in plasma settings
https://bugs.kde.org/show_bug.cgi?id=418489 --- Comment #3 from Sergey --- I see. I have fixed every single path manually. So it's kind of double work. First to fix standard way and second to fix Dolphin way. Weird. But I have no choice :-( -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 404192] kscreenlocker_greet 100% cpu and BSOD with cursor on wakeup from suspend with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=404192 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #9 from Sergey --- reproducible with nvidia drivers 440.82 A workaround is to make a wrapper for kscreenlocker_greet with env QSG_RENDER_LOOP=basic But the trace goes deep to nvidia libraries for me. So maybe different. -- You are receiving this mail because: You are watching all bug changes.
