[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381266] Icontasks identifying Chrome apps as Chrome windows
https://bugs.kde.org/show_bug.cgi?id=381266 --- Comment #19 from Andrei --- I've updated my post on this above. TLDR: no scripts needed, just use separate class and --user-data-dir for separate apps. E.g.: `chromium --app=https://example.com --class=webapp-one --user-data-dir=/tmp/webapp-one` and `chromium --app=https://example.com --class=webapp-two --user-data-dir=/tmp/webapp-two` — these won't be grouped. At least this works for me for quite some time. Example .desktop file: ``` [Desktop Entry] Name=Gmail Exec=chromium --app=https://gmail.com --class=webapp-gmail --user-data-dir=/home/x/.local/share/webapps/gmail Icon=/home/x/Pictures/Icons/Gmail.png Type=Application ``` -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 465888] New: Wrong encoding in address label (ADR;LABEL=...)
https://bugs.kde.org/show_bug.cgi?id=465888 Bug ID: 465888 Summary: Wrong encoding in address label (ADR;LABEL=...) Classification: Applications Product: kaddressbook Version: 5.21.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tdhj744ra...@opayq.com CC: to...@kde.org Target Milestone: --- Created attachment 156343 --> https://bugs.kde.org/attachment.cgi?id=156343&action=edit Test contact STEPS TO REPRODUCE 1. Consider the following vcard: ``` BEGIN:VCARD VERSION:4.0 FN:Алиса N:Алиса ADR;TYPE=home;LABEL=тест:;;тест END:VCARD ``` 2. Import it 3. Open edit window 4. Go to Location tab 5. Notice OBSERVED RESULT Label for the address in address list is unreadable, has wrong encoding Screenshot: https://imgur.com/QA6uo5Y SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION If you export this contact, encoding is ok again. But when using some external sources for contacts (e.g. EteSync), it uploads contact with broken encoding. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459543] Feature request: Zoom to width
https://bugs.kde.org/show_bug.cgi?id=459543 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #3 from Andrei --- Hello! If it would be fit only by width the some parts of image will be not shown. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466452] New: Ability to copy image to clipboard
https://bugs.kde.org/show_bug.cgi?id=466452 Bug ID: 466452 Summary: Ability to copy image to clipboard Classification: Applications Product: digikam Version: 7.9.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** It is very needed possibility. Sometimes when I recognize faces and manage my albums I need to ask about it from my relatives and need to send the photo. So the usual way it would be by pressing Ctrl+C but it doesn't work. Even I open in pressing F4 I can't copy to clipboard (I mean the whole image). Please add this ability in Preview Image at least. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466455] New: "Open In File Manager" doesn't work
https://bugs.kde.org/show_bug.cgi?id=466455 Bug ID: 466455 Summary: "Open In File Manager" doesn't work Classification: Applications Product: digikam Version: 7.9.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- STEPS TO REPRODUCE 1. Open image in Preview. 2. Right click mouse and choose "Open In File Manager" by left click. OBSERVED RESULT Nothing happened. EXPECTED RESULT Opening in Files or Thunar or Dolphin or error message how to fix this error. May be it would be choosing the File manager to open directory with this file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.10 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466456] New: Ability to show filepath to image
https://bugs.kde.org/show_bug.cgi?id=466456 Bug ID: 466456 Summary: Ability to show filepath to image Classification: Applications Product: digikam Version: 7.9.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- STEPS TO REPRODUCE 1. Open in Preview 2. See at status bar or image tooltip (in image line) OBSERVED RESULT Only filename. EXPECTED RESULT Either filename with filepath either filename and filepath separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ununtu 22.10. (available in About System) KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466455] "Open In File Manager" doesn't work
https://bugs.kde.org/show_bug.cgi?id=466455 --- Comment #2 from Andrei --- (In reply to caulier.gilles from comment #1) > It work perfectly here under Kubuntu 22.04: > > https://i.imgur.com/0T36aB8.mp4 > > Gilles Caulier Ok. But what's the problem for my Ubuntu? digiKam doesn't show the problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409995] Scan for Faces in video files is not yet supported
https://bugs.kde.org/show_bug.cgi?id=409995 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #4 from Andrei --- About time. I don't see problem with it. I can run it at night. But I see another problem with shouldn't be done before: to see similar faces as one with some coefficient. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409995] Scan for Faces in video files is not yet supported
https://bugs.kde.org/show_bug.cgi?id=409995 Andrei changed: What|Removed |Added Version|6.1.0 |7.9.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409995] Scan for Faces in video files is not yet supported
https://bugs.kde.org/show_bug.cgi?id=409995 Andrei changed: What|Removed |Added Platform|Microsoft Windows |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363724] Request for Search By Face
https://bugs.kde.org/show_bug.cgi?id=363724 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #1 from Andrei --- I think it would be doing automatically as it is in Picasa. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363724] Request for Search By Face
https://bugs.kde.org/show_bug.cgi?id=363724 Andrei changed: What|Removed |Added Version|5.0.0 |7.9.0 OS|Linux |All Platform|Other |unspecified -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #2 from Andrei --- I agree it would be nice also for ex wifes and husbands and their relatives. It's our historym but it have to be in the past. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 Andrei changed: What|Removed |Added Platform|Kubuntu |unspecified Version|7.8.0 |7.9.0 OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401458] Rename file name with recognized faces-tags
https://bugs.kde.org/show_bug.cgi?id=401458 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru --- Comment #3 from Andrei --- I don't think so. Because there are many person on the photo. Better to find this photo with a filter. I don't know is it possible now in digiKam or not. If not the better the ability to do such a filter. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466456] Ability to show filepath to image
https://bugs.kde.org/show_bug.cgi?id=466456 Andrei changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #2 from Andrei --- (In reply to caulier.gilles from comment #1) > Information is visible in Right sidebar, Properties tab. > > https://i.imgur.com/Yptftby.png > > Gilles Caulier Thank you but it's hard to find out this info). BTW is it possible to copy full path to the image to clipboard? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored
https://bugs.kde.org/show_bug.cgi?id=415770 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Andrei --- Same issue: Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481399] New: license message NO_PUBKEY when starting discover
https://bugs.kde.org/show_bug.cgi?id=481399 Bug ID: 481399 Summary: license message NO_PUBKEY when starting discover Classification: Applications Product: Discover Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ans...@yandex.ru CC: aleix...@kde.org Target Milestone: --- SUMMARY *** STEPS TO REPRODUCE 1. each time I start discover OBSERVED RESULT modal message appears: W: Произошла ошибка при проверке подписи. Репозиторий не обновлён, и будут использованы предыдущие индексные файлы. Ошибка GPG: https://repo.waydro.id jammy InRelease: Следующие подписи не могут быть проверены, так как недоступен открытый ключ: NO_PUBKEY 0E406D181DCEE19C E: https://repo.waydro.id jammy InRelease is not (yet) available (Следующие подписи не могут быть проверены, так как недоступен открытый ключ: NO_PUBKEY 0E406D181DCEE19C) EXPECTED RESULT started without the message -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487374] Missing icons
https://bugs.kde.org/show_bug.cgi?id=487374 Andrei changed: What|Removed |Added CC||and...@amateescu.me -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Andrei changed: What|Removed |Added CC||ilikeorange...@gmail.com --- Comment #7 from Andrei --- The default shortcuts of Ten Brushes "ctrl+alt+number" work fine in Krita Beta 5 but changing to something like "E" used to enable eraser mode doesn't change back the preset. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=452532 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442571] New: kdeconnect-cli -a lists not paired devices
https://bugs.kde.org/show_bug.cgi?id=442571 Bug ID: 442571 Summary: kdeconnect-cli -a lists not paired devices Product: kdeconnect Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: tdhj744ra...@opayq.com Target Milestone: --- SUMMARY kdeconnect-cli --help says: -a, --list-available List available (paired and reachable) devices Instead, it also lists reachable not paired devices, see https://invent.kde.org/network/kdeconnect-kde/-/blob/master/cli/kdeconnect-cli.cpp#L91 STEPS TO REPRODUCE 1. Have 2 reachable devices, one paired and one not 2. kdeconnect-cli -a OBSERVED RESULT Both devices are shown EXPECTED RESULT Only reachable AND paired device should be shown SOFTWARE/OS VERSIONS Linux: Ubuntu 21.04, kernel 5.11.0-31-generic KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457407] New: Feature request
https://bugs.kde.org/show_bug.cgi?id=457407 Bug ID: 457407 Summary: Feature request Product: digikam Version: 7.7.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- SUMMARY *** I wish that digiKam could group similar faces and show amount of grouped faces like Picasa. Similarity of the photo could be an parameter like a 90%, so there is small probability for digiKam mistake. *** EXPECTED RESULT I see group photos and name this group and it could speed up the work with naming of photos. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436192] Feature Request: Sort Unknown Faces (ungrouped)
https://bugs.kde.org/show_bug.cgi?id=436192 --- Comment #3 from Andrei --- (In reply to Amin Husni from comment #0) > Wondering if it is possible to have a feature where you can sort the faces > in the unknown group in an incremental manner according to > similarity/alignments? > > This is possible with other program called FaceSwap by using openCV. > > (Note: Different program on the link to demonstrate example of such feature) > https://github.com/deepfakes/faceswap/issues/252 > https://forum.faceswap.dev/viewtopic.php?t=27#sort > > I believe this could further enhance the speed of managing faces where we > can just batch tag a row of faces that has been sorted. please, explain your feature... Do you mean that after you name photo digiKam have to find the similar photo or what? May be you mean that digiKam has to group similar photos? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457407] Feature request: Group similar faces
https://bugs.kde.org/show_bug.cgi?id=457407 Andrei changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #2 from Andrei --- I don't think this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=436192 . But I agree that feature request too. My idea is to group, but the idea of 436192 is to recognize face step by step. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444160] Facing matching is guess work at best
https://bugs.kde.org/show_bug.cgi?id=444160 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457407] Feature request: Group similar faces
https://bugs.kde.org/show_bug.cgi?id=457407 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457461] New: Ability to ignore all faces except tag marked
https://bugs.kde.org/show_bug.cgi?id=457461 Bug ID: 457461 Summary: Ability to ignore all faces except tag marked Product: digikam Version: 7.7.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: avmaksi...@yandex.ru Target Milestone: --- SUMMARY *** Better if I can open a photo as I can now but if this group photo with 20 people and I know only 1-2 I have to ignore all this faces one by one. But better if I could press button "Ignore unknown (unrecognized) faces" and other faces would be marked as ignored. *** OBSERVED RESULT Less hours with cleaning the face data) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457461] Ability to ignore all faces except tag marked
https://bugs.kde.org/show_bug.cgi?id=457461 Andrei changed: What|Removed |Added CC||avmaksi...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Brush outline (and also stroke) lags significantly on 4k displays
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #24 from andrei --- Sorry, Dmitry, I haven't noticed your questions in time. VSync/Tripple buffering give no noticeable effect. Reducing Krita FPS to 60 also does not change anything much, but when I set it to 30, the lag is almost completely gone (regardless of Nvidia/Intel gpu is used). Unfortunately, with 30 FPS artifacts start to appear. Probably I can live with those artifacts, since they don't affect resulting image... PS: tested on Krita 4.3.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401458] Rename file name with recognized faces-tags
https://bugs.kde.org/show_bug.cgi?id=401458 --- Comment #4 from Andrei --- (In reply to Andrei from comment #3) > I don't think so. Because there are many person on the photo. Better to find > this photo with a filter. I don't know is it possible now in digiKam or not. > If not the better the ability to do such a filter. I agree with you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466455] "Open In File Manager" doesn't work
https://bugs.kde.org/show_bug.cgi?id=466455 --- Comment #6 from Andrei --- (In reply to caulier.gilles from comment #5) > Andrei, > > What's about this file using current 8.2.0 AppImage Linux bundle ? It's > reproducible ? > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier Yes. It's work fine with it. It shows the folder with file but doen't select the file. If it's possible it will be nice (or may be it should - I don't know). And BTW. I checked in the fresh Ubuntu - I have the same problem with installed version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453159] Unable to set custom top-level icon in Service Menu
https://bugs.kde.org/show_bug.cgi?id=453159 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422140] Annoying and obtrusive notifications KDE connect
https://bugs.kde.org/show_bug.cgi?id=422140 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Delay and lag in painting stroke while drawing.
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #11 from andrei --- That would be interesting to try. I guess not only outline, but also brush drawing can be updated only in the area of brush. For now I just switched to Ubuntu, which does not have Nvidia Optimus. I read on some laptops it can be disabled in bios, but not on my MSI. I wonder how games for example work on Windows. If rendering is done only with opengl then intel gpu can be disabled...? hm... Maybe it's worth mentioning in some FAQ, that Laptop with Nvidia + 4K + Windows give noticeable lag. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Brush outline (and also stroke) lags significantly on 4k displays
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #14 from andrei --- Ok, thank you. I’ll try to test on this weekend. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Brush outline (and also stroke) lags significantly on 4k displays
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #16 from andrei --- Dear Dmitry, thanks for your work~ I tried to do some tests, and here's the result: For all tests I used "Basic 1" brush, size 100, without smoothing. Picture size 4096x4096, 8 bit. Laptop with Nvidia GPU as before. External monitor 4K, 60 FPS. For checking the lag I used video on my phone, also 60 FPS. At first I tried to check with screen recorder, but realized that it affects Krita performance. That's why phone camera. 1. Windows, Krita 4.3, Intel GPU Outline lag: ~4 frames (65ms), brush lag: ~5 frames (83ms). 2. Windows, Krita 4.3, Nvidia Optimus Outline lag: ~8 frames (130ms), brush lag: ~11 frames (180ms). 3. Windows, Krita DK11, Intel GPU Outline lag: ~3 frames (50ms), brush lag: ~3 frames (50ms). 4. Windows, Krita DK14, Intel GPU Outline lag: ~3 frames (50ms), brush lag: ~3 frames (50ms). 5. Windows, Krita DK14, Nvidia Optimus Outline lag: ~4 frames (65ms), brush lag: ~5 frames (83ms). 6. Ubuntu, Krita 4.2.9, Only Nivida Outline lag: ~1 frame (17ms), brush lag: ~1 frame (17ms). Maybe even less. 7. Ubuntu, Krita 4.2.9, Intel GPU Outline lag: ~4 frames (65ms), brush lag: ~5 frames (83ms). So few notes on this. * Your fix is working. It improves the performance 25~50% depending on GPU used. * Only Intel GPU is better than Nvidia + Intel GPU. * Performance on pure Nvidia is still ~3 times higher. (case 6) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Brush outline (and also stroke) lags significantly on 4k displays
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #18 from andrei --- Nonono. I use usual tablet (XP-Pen Deco Pro) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 437871] New: KDE Latte crash on startup
https://bugs.kde.org/show_bug.cgi?id=437871 Bug ID: 437871 Summary: KDE Latte crash on startup Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: vickarch...@yandex.com Target Milestone: --- Application: latte-dock (0.9.91) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.7-zen1-1-zen x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Garuda Linux -- Information about the crash: - What I was doing when the application crashed: [The system had a fresh start, I logged out of Windows on another drive and logged in to Garuda] -I selected my Garuda Linux from the grub menu -I waited for the loading -I did not enter any credentials as I have setting "don't ask password on login" enabled -I saw my desktop wallpaper appear -I saw "Garuda Welcome" application appear and at the same time - the dock appeared with Latte dock -Almost instantly both Latte dock and the dock panel dissappeared and the crash report form appeared The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fb2453d27c0 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7fb245403a9c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fb2453ea37a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fb2453efaf6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7fb2453f0505 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7fb2453d7582 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fb2454460a3 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #11 0x7fb2454466de in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #12 0x7fb2455b5b17 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #13 0x7fb2453d7d2d in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #14 0x7fb2453d7549 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #15 0x7fb2453d7a74 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #16 0x7fb24543dd53 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #17 0x7fb2454add01 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #18 0x7fb24544c9e7 in () at /usr/lib/libQt5Quick.so.5 #19 0x7fb24544d3c7 in () at /usr/lib/libQt5Quick.so.5 #20 0x7fb2433f7f7f in () at /usr/lib/libQt5Core.so.5 #21 0x7fb242721259 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fb242f005e3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fb1b31fe640 (LWP 4404) "latte-do:gdrv0"): #1 0x7fb242727270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fb22c621e8c in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fb22c61bf08 in () at /usr/lib/dri/radeonsi_dri.so #4 0x7fb242721259 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fb242f005e3 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fb1b3fff640 (LWP 4107) "latte-dock"): #1 0x7fb23de92524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7fb23de938a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7fb242721259 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb242f005e3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fb1e3fff640 (LWP 3847) "QQmlThread"): #1 0x7fb2419e145d in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7fb241a34a8b in () at /usr/lib/libglib-2.0.so.0 #3 0x7fb2419de781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fb24363bcaf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb2435e197c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb2433f6da2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fb2450eb509 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fb2433f7f7f in () at /usr/lib/libQt5Core.so.5 #9 0x7fb242721259 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb242f005e3 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fb2077fe640 (LWP 3496) "QQmlThread"): #1 0x7fb2419df4c6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb2419e0aeb in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fb241a34a06 in () at /usr/lib/libglib-2.0.so.0
[neon] [Bug 490010] New: Cannot login after system update
https://bugs.kde.org/show_bug.cgi?id=490010 Bug ID: 490010 Summary: Cannot login after system update Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: ans...@yandex.ru CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 171525 --> https://bugs.kde.org/attachment.cgi?id=171525&action=edit login screen STEPS TO REPRODUCE 1. start notebook 2. try to enter password at login screen OBSERVED RESULT accepts the password, black screen and then loops back to login screen again EXPECTED RESULT enter into desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.27 (6) KDE Plasma Version: ? KDE Frameworks Version: 5.116.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I can login in console when try ctrl+alt+f3 then enter login and password -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410737] New: Hashed display of pdf images created with gnuplot
https://bugs.kde.org/show_bug.cgi?id=410737 Bug ID: 410737 Summary: Hashed display of pdf images created with gnuplot Product: okular Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ao...@mail.ru Target Milestone: --- Created attachment 122019 --> https://bugs.kde.org/attachment.cgi?id=122019&action=edit pdf file which demonstrates the problem SUMMARY Slackware Linux, current, kde 4.14.38 When using okular to display pdf files created with gnuplot (pm3d map) hash appears over the plot areas (and colorbox). No hash (almost) when using xpdf, older version of okular (slackware 14.2, kde 4.14.32) pdftopng removes hashes... STEPS TO REPRODUCE 1. create pdf using gnuplot, cairolatex, pm3d map z.plt: set terminal cairolatex pdf standalone size 12cm,12cm set output "z.tex" A(x,y) = x**2+y**2 < 1 ? exp(-x**2-y**2) : NaN set xrange [-2:2] set yrange [-2:2] set isosamples 300 set pm3d map splot A(x,y) -- $ gnuplot z.plt $ pdflatex z $ okular z.pdf OBSERVED RESULT hash lines over the image and colorbox EXPECTED RESULT smooth color image SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware current (14.2+), kde 4.14.38 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 4.8.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410737] Hashed display of pdf images created with gnuplot
https://bugs.kde.org/show_bug.cgi?id=410737 --- Comment #2 from Andrei --- Okular setting "graphics smoothing" removes the effect ... still,looks like it's a bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Delay and lag in painting stroke while drawing.
https://bugs.kde.org/show_bug.cgi?id=413504 andrei changed: What|Removed |Added CC||akela1...@gmail.com --- Comment #7 from andrei --- I can confirm this performance issue. My system: windows 10, NVidia 1050Ti + IntelHD 630 (some core i7) Krita version: beta from Steam. (can confirm for stable version too) Krita settings (display/performance) do not influence much for me. Brush smoothing is disabled. It does not depend on whether I use mouse or tablet. Interesting note: it depends on canvas size. The bigger canvas window, the larger lag you can observe. For example, on 4k monitor it's really slow. Interesting note 2: moving cursor even without any drawing loads both GPU heavily (up to 80% on Intel and up to 25% on NVidia). Interesting note 3: Full Screen mode reduces this load a bit, but still it is pretty noticeable. I checked if it's the same for other drawing applications on my PC. For some yes, for some no. One of the working ones is GIMP - almost no lag between cursor and brush, and almost no load on GPU. Please, fix this or point me how to do it. : ) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Delay and lag in painting stroke while drawing.
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #8 from andrei --- Tested on other PCs today. * windows laptop, without Nvidia GPU - same lag. * ubuntu pc with Nvidia - no lag. * ubuntu laptop without Nvidia - no lag. * ubuntu in VirtualBox on windows - black canvas and freeze : ) So, apparently it works only on native ubuntu system, not related to discrete GPU presence. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Delay and lag in painting stroke while drawing.
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #9 from andrei --- I really doubt somebody is reading this thread, but anyway I'd like to keep my research results somewhere... At first, some more information about my setup. ANGLE is used, Nvidia vertical sync disabled - no difference. Also, I'm testing on 4K monitor. With smaller monitor the lag is less noticeable, but still present. Image size is not so relevant, you can take 256x256 with the same effect. The main factor is canvas widget size. To be sure it's software problem, I run application on the same PC under Ubuntu - no lag. So, I tried to build from source and check what's taking so much GPU resource when mouse is just moving. It happened to be KisToolPaint::requestUpdateOutline with funny commentaries like: // DIRTY HACK ALERT: we should fetch the assistant's dirty rect when requesting the update, instead of just dumbly update the entire canvas! So, I commented out all that block and tried to run again. This time there was no GPU load during mouse move, but I started to notice the same effect when drawing with freehand brush. Apparently it does full canvas refresh too. I think, even the canvas rendering is not 100% optimized, this problem is mainly due to Nvidia Optimus brokenness and it is not possible to disable integrated GPU for me now. On ubuntu, iGPU is not used, and everything is fine (some other stuff is not fine, but it's not related to krita). Maybe I'll try to fix this in future, but it seems much easier way is to buy normal PC with GPU directly connected to monitor. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 385202] KRunner crashes while typing in the name of an application
https://bugs.kde.org/show_bug.cgi?id=385202 Andrei changed: What|Removed |Added CC||andp...@gmail.com --- Comment #1 from Andrei --- Same thing happens to me: Application: krunner (5.12.1) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I was typing firefox in krunner. It crashed as soon as I have typed "fir". The same thing happens when I try to type it into the app launcher widget. This is not the only combination that makes it crash. The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390572] New: App launcher widget crashes when I type application name
https://bugs.kde.org/show_bug.cgi?id=390572 Bug ID: 390572 Summary: App launcher widget crashes when I type application name Product: plasmashell Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andp...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.1) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Typing application name - Unusual behavior I noticed: Only some letter combinations seem to cause the crash, such as "fir" and "ire". Krunner also has this bug. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe49d36a800 (LWP 684))] Thread 16 (Thread 0x7fe3b17fa700 (LWP 1071)): #0 0x7fe4960e43bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe496f2b02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe3e448142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe3e4486479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fe3e4483c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fe496f29b4d in () at /usr/lib/libQt5Core.so.5 #17 0x7fe4960de08c in start_thread () at /usr/lib/libpthread.so.0 #18 0x7fe496831e7f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fe3b1ffb700 (LWP 1070)): #0 0x7fe4960e43bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe496f2b02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe3e448142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe3e4486479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe3e44864d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe3e4480924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fe3e4483c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fe496f29b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7fe4960de08c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fe496831e7f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fe3b27fc700 (LWP 1069)): [KCrash Handler] #5 0x7fe49715ca60 in QVariant::QVariant(QVariant const&) () at /usr/lib/libQt5Core.so.5 #6 0x7fe3ba4562cc in () at /usr/lib/qt/plugins/sqldrivers/libqsqlite.so #7 0x7fe3ba453ae6 in () at /usr/lib/qt/plugins/sqldrivers/libqsqlite.so #8 0x7fe494edb938 in QSqlQuery::exec() () at /usr/lib/libQt5Sql.so.5 #9 0x7fe3b8f36761 in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so #10 0x7fe3b8f36f0a in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so #11 0x7fe3b8f31972 in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so #12 0x7fe3b8f2f1b5 in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so #13 0x7fe3b8f3a064 in () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so #14 0x7fe3e4f7f7f0 in Plasma::AbstractRunner::performMatch
[plasmashell] [Bug 398690] New: Window position after new monitor is added
https://bugs.kde.org/show_bug.cgi?id=398690 Bug ID: 398690 Summary: Window position after new monitor is added Product: plasmashell Version: 5.13.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: andrei.eich...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 114987 --> https://bugs.kde.org/attachment.cgi?id=114987&action=edit Configuration screen of the monitors I use KDE on my laptop with a external monitor, I got my laptop screen as a primary screen. Every time I attach the monitor to the laptop, the windows move to that new monitor instead of staying on the device screen. The same behavior happens when I minimize the windows before attaching the monitor to the laptop, when I de-minimize the windows, they show up on the external monitor, even if I let the cursor on the primary screen or click on the wallpaper to bring the focus to that screen. It acts like the shell is choosing the last monitor in the list of available monitors instead of the first, or the primary one -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 446920] [Feature Reequest] Open directory in yakuake from commandline
https://bugs.kde.org/show_bug.cgi?id=446920 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 Andrei changed: What|Removed |Added CC||andreisva2...@gmail.com --- Comment #24 from Andrei --- I second this. Please add some way to disable the service from running. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Andrei changed: What|Removed |Added CC||tdhj744ra...@opayq.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502078] New: Incorrect attachment of windows in portrait orientation
https://bugs.kde.org/show_bug.cgi?id=502078 Bug ID: 502078 Summary: Incorrect attachment of windows in portrait orientation Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: prockaand...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Grab the window and move it to the edge of the screen. The wrong windows grid appears OBSERVED RESULT Landscape orientation grid appears EXPECTED RESULT do it like in windows 11 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502078] Incorrect attachment of windows in portrait orientation
https://bugs.kde.org/show_bug.cgi?id=502078 --- Comment #4 from Andrei --- You can compare how the window mount works in portrait orientation, in plasma the window mount works the same regardless of the monitor orientation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502078] Incorrect attachment of windows in portrait orientation
https://bugs.kde.org/show_bug.cgi?id=502078 --- Comment #3 from Andrei --- Created attachment 180132 --> https://bugs.kde.org/attachment.cgi?id=180132&action=edit How works on Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502078] Incorrect attachment of windows in portrait orientation
https://bugs.kde.org/show_bug.cgi?id=502078 --- Comment #2 from Andrei --- Created attachment 180131 --> https://bugs.kde.org/attachment.cgi?id=180131&action=edit How works on Win 11 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368316] Kontact crashes often after minutes of running
https://bugs.kde.org/show_bug.cgi?id=368316 Andrei Slavoiu changed: What|Removed |Added CC||ansl...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368316] Kontact crashes often after minutes of running
https://bugs.kde.org/show_bug.cgi?id=368316 --- Comment #1 from Andrei Slavoiu --- Created attachment 102400 --> https://bugs.kde.org/attachment.cgi?id=102400&action=edit New crash information added by DrKonqi kontact (4.14.10) on KDE Platform 4.14.26 using Qt 4.8.7 - What I was doing when the application crashed: Just rebooted my computer and as soon as akregator refreshed the feeds it crashed -- Backtrace (Reduced): #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35 #7 0x7f097021648f in c4_Column::CopyData (this=this@entry=0x14f3f1b8, to_=to_@entry=15278080, from_=from_@entry=15282176, count_=190) at /usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/column.cpp:304 #8 0x7f0970216bd7 in c4_Column::Grow (this=0x14f3f1b8, off_=, diff_=diff_@entry=99) at /usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/column.cpp:555 #9 0x7f097021ddde in c4_FormatB::SetOne (this=0x14f3f1a0, index_=5654, xbuf_=..., ignoreMemos_=ignoreMemos_@entry=false) at /usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/format.cpp:607 #10 0x7f097021e7f9 in c4_FormatS::Set (this=, index_=, buf_=...) at /usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/format.cpp:862 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449856] Plasma crashes when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=449856 Andrei Coada changed: What|Removed |Added CC||andrei.raz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449856] Plasma crashes when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=449856 --- Comment #4 from Andrei Coada --- Created attachment 146959 --> https://bugs.kde.org/attachment.cgi?id=146959&action=edit New crash information added by DrKonqi plasmashell (5.24.1) using Qt 5.15.2 - What I was doing when the application crashed: Coming out of Screen energy saving (not sleep) -- Backtrace (Reduced): #6 0x7faa3995bcf1 in QScopedPointer >::operator-> (this=0x99) at /usr/include/qt5/QtCore/qscopedpointer.h:118 [...] #9 QQuickWindow::mouseGrabberItem (this=0x91) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickwindow.cpp:1732 #10 0x7faa3995e49b in QQuickWindowPrivate::removeGrabber (this=0x55ba041596b0, grabber=grabber@entry=0x55b9ff65d9e0, mouse=mouse@entry=true, touch=touch@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickwindow.cpp:1001 #11 0x7faa3993e002 in QQuickItemPrivate::setEffectiveVisibleRecur (this=0x55b9ff74a3f0, newEffectiveVisible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickitem.cpp:6067 #12 0x7faa3993e037 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x55b9ff408b90, newEffectiveVisible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.1.x86_64/src/quick/items/qquickitem.cpp:6072 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249
--- Comment #4 from Andrei Slavoiu ---
(In reply to Igor Kushnir from comment #3)
> Andrei Slavoiu, could you try the workaround that works for other reporters?
Hi, I assume the workaround was applying this patch:
--- kdevelop-22.04.1-orig/plugins/clang/duchain/builder.cpp 2022-06-01
21:11:28.907037431 +0300
+++ kdevelop-22.04.1/plugins/clang/duchain/builder.cpp 2022-06-01
21:12:48.177035132 +0300
@@ -1080,7 +1080,7 @@
#endif
#if CINDEX_VERSION_MINOR >= 16
-decl->setBitWidth(clang_getFieldDeclBitWidth(cursor));
+decl->setBitWidth(-1);
#endif
if (clang_isCursorDefinition(cursor)) {
In that case, I confirm that after rebuilding with it kdevelop was able to
complete the background parsing.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #11 from Andrei Slavoiu --- (In reply to Igor Kushnir from comment #5) > Arthur, Andrei, do your projects use wxWidgets? No > Also, when you write that the crash started occurring after an > update/rebuild of KDevelop, were your projects or some libraries > they use updated at the same time too? I don't remember any significant code changes around that time. But I could downgrade to the version built with clang-13 and see how it behaves with current code. (In reply to Igor Kushnir from comment #7) > Could someone try to get the backtrace of this crash with assertions > enabled? (NDEBUG not defined) I'll give it a try. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #14 from Andrei Slavoiu --- Here is the assert. For some reason DrKonqi does not handle it, so I got the stacktrace manually: kdevelop: /var/tmp/portage/sys-devel/clang-14.0.4/work/clang/lib/AST/ExprConstant.cpp:15103: llvm::APSInt clang::Expr::EvaluateKnownConstInt(const clang::ASTContext&, llvm::SmallVectorImpl >*) const: Assertion `!isValueDependent() && "Expression evaluator can't be called on a dependent expression."' failed. Thread 41 "Queue(0x58c" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff41560640 (LWP 24484)] __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x75f77d1f in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75f2aa62 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75f15469 in __GI_abort () at abort.c:79 #4 0x75f15395 in __assert_fail_base (fmt=0x760a3c80 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fff4f2c2c98 "!isValueDependent() && \"Expression evaluator can't be called on a dependent expression.\"", file=0x7fff4f2c53b0 "/var/tmp/portage/sys-devel/clang-14.0.4/work/clang/lib/AST/ExprConstant.cpp", line=15103, function=) at assert.c:92 #5 0x75f239d2 in __GI___assert_fail (assertion=0x7fff4f2c2c98 "!isValueDependent() && \"Expression evaluator can't be called on a dependent expression.\"", file=0x7fff4f2c53b0 "/var/tmp/portage/sys-devel/clang-14.0.4/work/clang/lib/AST/ExprConstant.cpp", line=15103, function=0x7fff4f2cf7f0 "llvm::APSInt clang::Expr::EvaluateKnownConstInt(const clang::ASTContext&, llvm::SmallVectorImpl >*) const") at assert.c:101 #6 0x7fff4de82d71 in clang::Expr::EvaluateKnownConstInt(clang::ASTContext const&, llvm::SmallVectorImpl >*) const (this=, Ctx=, Diag=Diag@entry=0x0) at /usr/src/debug/sys-devel/clang-14.0.4/clang/lib/AST/ExprConstant.cpp:15103 #7 0x7fff4ddc979b in clang::FieldDecl::getBitWidthValue(clang::ASTContext const&) const (this=, Ctx=) at /usr/src/debug/sys-devel/clang-14.0.4/clang/lib/AST/Decl.cpp:4206 #8 0x7fff4fcc1bff in (anonymous namespace)::Visitor::setDeclData<(CXCursorKind)6>(CXCursor, KDevelop::ClassMemberDeclaration*) (cursor=..., decl=decl@entry=0x7fff2a075a00, this=0x7fff4155efa0) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:1083 #9 0x7fff4fcd346a in (anonymous namespace)::Visitor::createDeclarationCommon<(CXCursorKind)6, KDevelop::ClassMemberDeclaration>(CXCursor, KDevelop::Identifier const&) (this=this@entry=0x7fff4155efa0, cursor=..., id=...) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:442 #10 0x7fff4fcd404b in (anonymous namespace)::Visitor::createDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration> (context=0x0, id=..., cursor=..., this=0x7fff4155efa0) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:451 #11 (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration, false>(CXCursor) (this=this@entry=0x7fff4155efa0, cursor=...) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:1217 #12 0x7fff4fcd5010 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)6> (parent=..., cursor=..., this=0x7fff4155efa0) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:965 #13 (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff4155efa0) at /usr/src/debug/dev-util/kdevelop-22.04.1/kdevelop-22.04.1/plugins/clang/duchain/builder.cpp:1554 #14 0x7fff4dccd9c5 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) (this=0x7fff4155e580, Cursor=..., CheckedRegionOfInterest=) at /usr/src/debug/sys-devel/clang-14.0.4/clang/tools/libclang/CIndex.cpp:220 #15 0x7fff4dcd3add in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) (this=0x7fff4155e580, D=0x7ffec0bfc4c0) at /usr/src/debug/sys-devel/clang-14.0.4/clang/tools/libclang/CIndex.cpp:682 #16 0x7fff4dcd3bd0 in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) (this=0x7fff4155e580, DC=0x7ffec0bfc088) at /usr/src/debug/sys-devel/clang-14.0.4/clang/tools/libclang/CIndex.cpp:643 #17 0x7fff4dccd2b2 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) (this=0x7fff4155e580, Cursor=...) at /usr/src/debug/sys-devel/clang
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #16 from Andrei Slavoiu --- Looks like it's parsing std::string when crashing?!?! [Thread 0x7ffec67fc640 (LWP 2174) exited] setDeclData "class basic_string_base< Allocator >" "" setDeclData " operator=" "" setDeclData " basic_string_base" "" setDeclData " allocator_type" "" setDeclData " allocator_traits_type" "" setDeclData " stored_allocator_type" "" setDeclData " pointer" "" setDeclData " value_type" "" setDeclData " size_type" "" setDeclData " difference_type" "" setDeclData " pointer_traits" "" setDeclData " basic_string_base" "" setDeclData " basic_string_base" "" setDeclData " basic_string_base" "" setDeclData " basic_string_base" "" setDeclData " basic_string_base" "" setDeclData " ~basic_string_base" "" setDeclData "class long_t" "" setDeclData " is_short" "" setDeclData " length" "" [New Thread 0x7ffec67fc640 (LWP 2208)] kdevelop: /var/tmp/portage/sys-devel/clang-14.0.4/work/clang/lib/AST/ExprConstant.cpp:15103: llvm::APSInt clang::Expr::EvaluateKnownConstInt(const clang::ASTContext&, llvm::SmallVectorImpl >*) const: Assertion `!isValueDependent() && "Expression evaluator can't be called on a dependent expression."' failed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249
--- Comment #17 from Andrei Slavoiu ---
No, not std::string. boost::string. Found the culprit:
//This is the structure controlling a long string
struct long_t
{
size_type is_short : 1;
size_type length: (sizeof(size_type)*CHAR_BIT - 1);
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #18 from Andrei Slavoiu --- And another correction, it's boost::container::string. Looks like boost has multiple string implementations. Also, I compiled kdevelop with clang-13 again, and no more crash. Weird. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #20 from Andrei Slavoiu --- (In reply to Igor Kushnir from comment #19) > If you can reproduce the crash consistently with Clang 14 > (I cannot with my system Clang 13), report the bug. Yes, it crashes consistently with clang 14, I'll look into reporting the bug upstream. > Does KDevelop compiled against Clang 13 call Clang 14 implementation at > runtime or does it keep using the Clang 13 version it was compiled against? Gentoo puts the libraries of each clang version in it's own dir, so it keeps using the one it was built with: # ldd /usr/lib64/qt5/plugins/kdevplatform/36/kdevclangsupport.so | grep llvm libclang.so.13 => /usr/lib/llvm/13/lib64/libclang.so.13 (0x7f3303933000) libLLVM-13.so => /usr/lib/llvm/13/lib64/../lib64/libLLVM-13.so (0x7f32fafd9000) After adjusting the symlinks from llvm/13 to point to the ones in llvm/14, kdevelop built with clang-13 and ran with clang-14 crashes the same way as the one built with clnag-14. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #22 from Andrei Slavoiu --- (In reply to Igor Kushnir from comment #21) > If you want to play with this some more, you could try building Clang 13 > with assertions enabled and see if the assertion is triggered. If yes, then > the absence of the crash is accidental. If the assertion does not fail, then > maybe it's a regression in Clang 14. Hah, good point. The assert fails on clang-13 as well when built with DEBUG. Probably on 13 it just happened to return some junk instead of crashing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project
https://bugs.kde.org/show_bug.cgi?id=438249 --- Comment #24 from Andrei Slavoiu --- Created attachment 149527 --> https://bugs.kde.org/attachment.cgi?id=149527&action=edit New crash information added by DrKonqi kdevelop (5.8.220401 (22.04.1)) using Qt 5.15.4 - What I was doing when the application crashed: Compiled clang-13 back without DEBUG and now I get the same crash with it as well. -- Backtrace (Reduced): #6 0x7fc50833d030 in __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:801 #7 0x7fc45184af1b in llvm::APInt::APInt(llvm::APInt const&) (that=..., this=0x7fc41e7f82c0) at /usr/lib/llvm/13/include/llvm/ADT/APInt.h:321 #8 llvm::APSInt::APSInt(llvm::APSInt const&) (this=0x7fc41e7f82c0) at /usr/lib/llvm/13/include/llvm/ADT/APSInt.h:22 #9 clang::Expr::EvaluateKnownConstInt(clang::ASTContext const&, llvm::SmallVectorImpl >*) const (this=0x7fc2d0226918, Ctx=..., Diag=Diag@entry=0x0) at /usr/src/debug/sys-devel/clang-13.0.1/clang/lib/AST/ExprConstant.cpp:15006 #10 0x7fc4517b449f in clang::FieldDecl::getBitWidthValue(clang::ASTContext const&) const (this=, Ctx=) at /usr/src/debug/sys-devel/clang-13.0.1/clang/lib/AST/Decl.cpp:4172 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465714] New: Assertion failure when attempting to open a PSD
https://bugs.kde.org/show_bug.cgi?id=465714 Bug ID: 465714 Summary: Assertion failure when attempting to open a PSD Classification: Applications Product: krita Version: 5.1.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ak...@taisei-project.org Target Milestone: --- Created attachment 156230 --> https://bugs.kde.org/attachment.cgi?id=156230&action=edit Full stack trace with locals SUMMARY Attempting to open a particular PSD file crashes Krita with an assertion failure. STEPS TO REPRODUCE Open the affected file with Krita and wait. Unfortunately, I am not permitted to distribute this file publicly, but I think I can send it to a verified active Krita developer privately. Please contact me on IRC (Akari @ libera.chat) or by email (ak...@taisei-project.org), with some way to verify your identity. OBSERVED RESULT ASSERT (krita): "embeddedResources.last().data()" in file /home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp, line 750 Stack trace from the relevant thread: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x75495503 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75442e16 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7542b89c in __GI_abort () at abort.c:79 #4 0x75abb0db in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #5 QMessageLogger::fatal (this=this@entry=0x7fffbe00, msg=msg@entry=0x77f7b0ab "%s") at global/qlogging.cpp:893 #6 0x77f76fb3 in kis_assert_common(char const*, char const*, int, bool, bool) [clone .constprop.0] (assertion=assertion@entry=0x77415970 "embeddedResources.last().data()", file=file@entry=0x77415850 "/home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp", line=line@entry=750, isIgnorable=isIgnorable@entry=false, throwException=) at /usr/src/debug/krita-5.1.5/libs/global/kis_assert.cpp:89 #7 0x77f3e7a7 in kis_assert_exception (assertion=assertion@entry=0x77415970 "embeddedResources.last().data()", file=file@entry=0x77415850 "/home/abuild/rpmbuild/BUILD/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp", line=line@entry=750) at /usr/src/debug/krita-5.1.5/libs/global/kis_assert.cpp:112 #8 0x7739fbe2 in KisAslLayerStyleSerializer::fetchEmbeddedResources (style=0x5bc5e890) at /usr/src/debug/krita-5.1.5/libs/image/kis_asl_layer_style_serializer.cpp:750 #9 0x773c0639 in KisPSDLayerStyle::embeddedResources (this=, globalResourcesInterface=...) at /usr/src/debug/krita-5.1.5/libs/image/kis_psd_layer_style.cpp:396 #10 0x775b4237 in KoResource::requiredResources (this=this@entry=0x5bc5e890, globalResourcesInterface=...) at /usr/src/debug/krita-5.1.5/libs/resources/KoResource.cpp:242 #11 0x773c0dd8 in KisRequiredResourcesOperators::createLocalResourcesSnapshot (globalResourcesInterface=..., object=0x5bc5e890) at /usr/src/debug/krita-5.1.5/libs/resources/KisRequiredResourcesOperators.h:60 #12 KisRequiredResourcesOperators::cloneWithResourcesSnapshot, KisPSDLayerStyle> (globalResourcesInterface=..., object=0x67689060) at /usr/src/debug/krita-5.1.5/libs/resources/KisRequiredResourcesOperators.h:91 #13 KisPSDLayerStyle::cloneWithResourcesSnapshot (this=this@entry=0x67689060, globalResourcesInterface=..., canvasResourcesInterface=...) at /usr/src/debug/krita-5.1.5/libs/image/kis_psd_layer_style.cpp:335 #14 0x7fffb40ec0d7 in PSDLoader::decode (this=, io=...) at /usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_loader.cpp:419 #15 0x7fffb40ee8c1 in PSDLoader::buildImage (io=..., this=0x7fffc6c0) at /usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_loader.cpp:432 #16 psdImport::convert (this=, document=0x5f2e1470, io=0x7fffc730) at /usr/src/debug/krita-5.1.5/plugins/impex/psd/psd_import.cc:29 #17 0x77c2201a in KisImportExportManager::doImport (this=0x5b9a7510, location=..., filter=...) at /usr/src/debug/krita-5.1.5/libs/ui/KisImportExportManager.cpp:667 #18 0x77c24000 in KisImportExportManager::convert (this=0x5b9a7510, direction=, location=..., realLocation=..., mimeType=..., showWarnings=, exportConfiguration=..., isAsync=, isAdvancedExporting=) at /usr/src/debug/krita-5.1.5/libs/ui/KisImportExportManager.cpp:376 #19 0x77c24f25 in KisImportExportManager::importDocument (this=, location=..., mimeType=...) at /usr/src/debug/krita-5.1.5/libs/global/kis_shared_ptr.h:206 #20 0x77c0b492 in KisDocument::openFile (this=0x5f2e1470) at /usr/src/debug/krita-5.1.5/libs/ui/KisDocument.cpp:1874 #21 0x77c19749 in KisDocument::openPathInternal (this=0x
[krita] [Bug 465714] Assertion failure when attempting to open a PSD
https://bugs.kde.org/show_bug.cgi?id=465714 Andrei Alexeyev changed: What|Removed |Added CC||ak...@taisei-project.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466256] New: It is hard to distinguish "KDE Connect" app from "KDE Connect" section in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=466256 Bug ID: 466256 Summary: It is hard to distinguish "KDE Connect" app from "KDE Connect" section in Application Launcher Classification: Applications Product: kdeconnect Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: rybak@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Created attachment 156613 --> https://bugs.kde.org/attachment.cgi?id=156613&action=edit State of the Application Launcher after the third step SUMMARY When typing "kde connect" in the Application Launcher, it is hard to distinguish the "KDE Connect" app proper from the section of System Settings which is also titled "KDE Connect". STEPS TO REPRODUCE 1. Open Application Launcher 2. Type "kde connect" into the search field 3. Read the top three results OBSERVED RESULT Top three search results: 1. The app proper with hint "Device Synchronization". 2. "KDE Connect SMS", easily distinguishable from the other two. 3. The section of System Settings with hint "Connect and sync your devices" EXPECTED RESULT Hints that help distinguish the app proper from the section of System Settings. For example, the System Settings hint could be "Change settings of KDE Connect". ADDITIONAL INFORMATION\ - It doesn't seem that the string "Connect and sync your devices" appears anywhere in the UI of the System Settings, but I could be missing some place where it is shown, like in a tooltip or something. - I've found the strings in code: - https://invent.kde.org/network/kdeconnect-kde/-/blob/master/app/org.kde.kdeconnect.app.desktop#L52 - https://invent.kde.org/network/kdeconnect-kde/-/blob/master/kcm/kcm_kdeconnect.json#L5 and don't mind creating a pull request myself. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] New: KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 Bug ID: 466416 Summary: KDE Connect keeps adding devices to Dolphin over and over and over and over and over Classification: Applications Product: kdeconnect Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: rybak@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Created attachment 156717 --> https://bugs.kde.org/attachment.cgi?id=156717&action=edit Unusable Dolphin due to overlong "Devices" section in the panel "Places" SUMMARY The section "Devices" in Dolphin becomes unusable, because KDE Connect keeps adding a new line to the section "Devices", it seems, every single time the phone is connected to the computer. STEPS TO REPRODUCE 1. Use KDE Connect for a prolonged period of time, make sure that the phone(s) connect and disconnect from the network that PC is on multiple times. 2. Open Dolphin. 3. Unhide the section "Devices" in the "Places" panel. OBSERVED RESULT Watch the screen recording please. EXPECTED RESULT Something sensible, that doesn't require you to scroll for how long the video is. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 5570 ADDITIONAL INFORMATION Right now there is no simple way to delete these phantom entries from Dolphin interface in a fast way. I will also create a Dolphin bug to add a feature to delete the devices from this panel faster. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #1 from Andrei Rybak --- > $ apt show kdeconnect 2>/dev/null | head -2 > Package: kdeconnect > Version: 22.12.2-0xneon+22.04+jammy+release+build21 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466420] New: Add ability to delete devices from Dolphin faster
https://bugs.kde.org/show_bug.cgi?id=466420 Bug ID: 466420 Summary: Add ability to delete devices from Dolphin faster Classification: Applications Product: dolphin Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rybak@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 156719 --> https://bugs.kde.org/attachment.cgi?id=156719&action=edit screen recording of steps to reproduce and observed result SUMMARY There is a bug – https://bugs.kde.org/show_bug.cgi?id=466416 – that causes too many entries being added to the Dolphin's panel "Places". If that bug is ever fixed, it would be nice to get rid of the wrong entries. It would be a good addition to the wonderful UI of Dolphin if it could allow its users to delete these incorrect entries in some _fast_ way. STEPS TO REPRODUCE 1. Open Dolphin on a computer affected by https://bugs.kde.org/show_bug.cgi?id=466416 2. Try selecting multiple devices at once. 3. Try removing a device using the Delete key 4. Remove a device using the context menu OBSERVED RESULT For step 2 — there is no way to select multiple devices at once. For step 3 — the "Selection mode" turns on For step 4 — Dolphin freezes. I don't actually know if a device gets removed or not — I don't know how to count them in an easy way. On the screen recording I'm trying to 1) resize the window - it doesn't work, 2) click on the "Cancel" button (it doesn't work) and 3) click on the close application button in the top right (it doesn't work). EXPECTED RESULT - There is a way to select multiple devices at once, similar to how it is possible to select multiple folders or files in the main panel of Dolphin - There is some kind of shortcut to delete devices while navigating the panel "Places" via keyboard, without having to open the context menu - Dolphin doesn't freeze SOFTWARE/OS VERSIONS > $ apt show dolphin 2>/dev/null | head -2 > Package: dolphin > Version: 4:22.12.2-0xneon+22.04+jammy+release+build16 Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 5570 ADDITIONAL INFORMATION Value "panels: places" is missing from the "Component:" field when creating a new bug on https://bugs.kde.org/enter_bug.cgi?product=dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster
https://bugs.kde.org/show_bug.cgi?id=466420 --- Comment #1 from Andrei Rybak --- Created attachment 156720 --> https://bugs.kde.org/attachment.cgi?id=156720&action=edit Four panels in Dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster
https://bugs.kde.org/show_bug.cgi?id=466420 --- Comment #2 from Andrei Rybak --- Created attachment 156721 --> https://bugs.kde.org/attachment.cgi?id=156721&action=edit Only three panels of Dolphin in Component field on bugs.kde.org Here are two screenshots showing the missing value for "Component" field for Dolphin on bugs.kde.org — the issue that I mentioned in the "ADDITIONAL INFORMATION" section. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #2 from Andrei Rybak --- > ADDITIONAL INFORMATION > Right now there is no simple way to delete these phantom entries > from Dolphin interface in a fast way. I will also create a Dolphin bug > to add a feature to delete the devices from this panel faster. Created new bug: https://bugs.kde.org/show_bug.cgi?id=466420 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #3 from Andrei Rybak --- In the video, one can see that the name of the phantom entries in the list is different for the last couple of dozen items — that's roughly the number of days that I've had a new phone that connects to the same computer via KDE Connect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461872] kdeconnect adds many duplicate devices in dolphin file manager
https://bugs.kde.org/show_bug.cgi?id=461872 --- Comment #4 from Andrei Rybak --- I have created two new tickets with more details: 1. https://bugs.kde.org/show_bug.cgi?id=466416 2. https://bugs.kde.org/show_bug.cgi?id=466420 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #5 from Andrei Rybak --- (In reply to zacharytalis from comment #4) > For the time being, you can prune these spam entries by editing > "~/.local/share/user-places.xbel" directly. (make sure to be careful and > take a backup, yada yada) It would have taken me a looong time to figure out where this is being stored. Thank you for saving my sanity when using Dolphin and my time! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466420] Add ability to delete devices from Dolphin faster
https://bugs.kde.org/show_bug.cgi?id=466420 --- Comment #3 from Andrei Rybak --- For those who don't mind editing Dolphin's data manually, zacharytalis proposed a hacky solution over at https://bugs.kde.org/show_bug.cgi?id=466416#c4: > For the time being, you can prune these spam entries by editing > "~/.local/share/user-places.xbel" directly. (make sure to be careful and > take a backup, yada yada) I looked at the structure of this XML file, which consisted mostly of tags. Each bookmark has a tag, which has the strings which I was interested in -- the names of the phones. I grepped the file for all tags. I noticed that all the erroneous entries are clumped together: > $ cd ~/.local/share > $ grep '' user-places.xbel | uniq > [...] > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A > Xiaomi > Pixel 6A So I did the following: 1. Found the first bookmark with the of an erroneous entry 2. Started selection 3. Found the last erroneous bookmark 4. Made sure the selection starts at an opening tag and ends at a closing tag 5. Deleted the whole selection -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #6 from Andrei Rybak --- (In reply to zacharytalis from comment #4) > you can prune these spam entries by editing "~/.local/share/user-places.xbel" > directly. More instructions for manually cleaning up "~/.local/share/user-places.xbel" in the Dolphin ticket: https://bugs.kde.org/show_bug.cgi?id=466420#c3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466834] New: KWin crashes after opening Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=466834 Bug ID: 466834 Summary: KWin crashes after opening Desktop Grid Classification: Plasma Product: kwin Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rybak@gmail.com Target Milestone: --- Application: kwin_x11 (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: This morning I noticed that desktop icons were missing (probably caused by multiple KWin and Plasma restarts yesterday). I pressed Meta+S – shortcut for "Show Desktop Grid" effect and then a KWin crash was reported. I am using a laptop in clamshell mode with external monitor. Laptop resolution is 1920x1080, the resolution of the external monitor is 2560x1440. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 KWin::OutputMode::size (this=0x3f80) at ./src/core/output.cpp:50 #5 0x7fa3f5fc3e52 in KWin::Output::modeSize (this=this@entry=0x7fa3e80091d0) at ./src/core/output.cpp:194 #6 0x7fa3f5fc4071 in KWin::Output::pixelSize (this=this@entry=0x7fa3e80091d0) at ./src/core/output.cpp:199 #7 0x7fa3f5fc40bf in KWin::Output::geometry (this=0x7fa3e80091d0) at ./src/core/output.cpp:174 #8 0x7fa3f60eb0a4 in KWin::Window::isOnOutput (this=0x561e02859e40, output=) at ./src/window.cpp:428 #9 0x7fa3f6090d7c in KWin::DesktopBackgroundItem::updateWindow (this=this@entry=0x561e02769740) at ./src/scripting/desktopbackgrounditem.cpp:112 #10 0x7fa3f6091126 in KWin::DesktopBackgroundItem::setDesktop (desktop=, this=0x561e02769740) at ./src/scripting/desktopbackgrounditem.cpp:66 #11 KWin::DesktopBackgroundItem::setDesktop (desktop=, this=0x561e02769740) at ./src/scripting/desktopbackgrounditem.cpp:62 #12 KWin::DesktopBackgroundItem::qt_static_metacall (_o=_o@entry=0x561e02769740, _c=_c@entry=QMetaObject::WriteProperty, _id=_id@entry=3, _a=_a@entry=0x7ffdb6383fb0) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:148 #13 0x7fa3f60913e3 in KWin::DesktopBackgroundItem::qt_metacall (this=0x561e02769740, _c=QMetaObject::WriteProperty, _id=3, _a=0x7ffdb6383fb0) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:197 #14 0x7fa3f54f430e in QQmlPropertyData::writeProperty (flags=..., value=0x7ffdb6383f68, target=, this=) at ../../include/QtQml/5.15.8/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:393 #15 QObjectPointerBinding::write (this=0x561e02662330, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:742 #16 0x7fa3f54f5b07 in QQmlNonbindingBinding::doUpdate (this=0x561e02662330, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:258 #17 0x7fa3f54f3664 in QQmlBinding::update (this=0x561e02662330, flags=...) at qml/qqmlbinding.cpp:194 #18 0x7fa3f54d0165 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #19 0x7fa3f46f3c5b in doActivate (sender=0x561e0255cec0, signal_index=27, argv=0x0) at kernel/qobject.cpp:3815 #20 0x7fa3f46f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7ffdb6385ba0, r=0x561e0255cec0, this=0x561e0254c0a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x561e0148acf0, signal_index=7, argv=0x7ffdb6385ba0) at kernel/qobject.cpp:3923 #22 0x7fa3f46ed177 in QMetaObject::activate (sender=, m=m@entry=0x7fa3f63cdc00 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffdb6385ba0) at kernel/qobject.cpp:3983 #23 0x7fa3f5f93963 in KWin::VirtualDesktopManager::currentChanged (this=, _t1=, _t2=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_virtualdesktops.cpp:622 #24 0x7fa3f60d7bf8 in KWin::VirtualDesktopManager::setCurrent (this=0x561e0148acf0, newDesktop=0x561e016123a0) at ./src/virtualdesktops.h:62 #25 0x7fa3f5fb4c8e in KWin::Workspace::activateWindow (this=0x561e0141a5c0, window=0x561e014e0eb0, force=) at ./src/activation.cpp:294 #26 0x7fa3f60b2743 in KWin::WorkspaceWrapper::qt_metacall (this=this@entry=0x561e025f6f50, _c=_c@entry=QMetaObject::WriteProperty, _id=2, _a=_a@entry=0x7ffdb6385d30) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_workspace_wrapper.cpp:1047 #27 0x7fa3f60b2895 in KWin::DeclarativeScriptWorkspaceWrapper::qt_metacall (this=0x561e025f6f50, _c=QMetaObject::WriteProperty, _id=, _a=0x7ffdb6385d30) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_workspace_wrapper.cpp:1423 #28 0x7fa3f548b46e in QQmlPropertyData::writeProperty (flags=..., value=, target=, this=) at ../../include/QtQml/5.15.8/QtQml/priva
[kdevelop] [Bug 388075] Kdevelop crashes after adding a new build dir
https://bugs.kde.org/show_bug.cgi?id=388075 Andrei Slavoiu changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Andrei Slavoiu --- I can no longer reproduce it with version 22.08.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467965] New: KWin crashes intermittently when switching to a window on a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=467965 Bug ID: 467965 Summary: KWin crashes intermittently when switching to a window on a different virtual desktop Classification: Plasma Product: kwin Version: 5.27.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rybak@gmail.com Target Milestone: --- Application: kwin_x11 (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: 1. Clicked on Chromium icon in Application launcher 2. While Chromium is still opening switched to a Firefox window on a different virtual desktop by pressing "Meta+1" - shortcut "Activate Task Manager Entry 1". 3. Once I was ready to use Chromium for what I opened it for, I clicked on its button in the Task Manager widget 4. KWin crashed and restarted itself. Notes: - This isn't the first time KWin crashes in this way. - I have a bunch of window rules for opening them on specific virtual desktops. There is one for Firefox, but none for Chromium. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 KWin::OutputMode::size (this=0x7) at ./src/core/output.cpp:50 #5 0x7ff3f7bc4122 in KWin::Output::modeSize (this=this@entry=0x55f5759eefa0) at ./src/core/output.cpp:194 #6 0x7ff3f7bc4341 in KWin::Output::pixelSize (this=this@entry=0x55f5759eefa0) at ./src/core/output.cpp:199 #7 0x7ff3f7bc438f in KWin::Output::geometry (this=0x55f5759eefa0) at ./src/core/output.cpp:174 #8 0x7ff3f7ced7d4 in KWin::Window::isOnOutput (this=0x55f576b26e20, output=) at ./src/window.cpp:428 #9 0x7ff3f7c8f72c in KWin::DesktopBackgroundItem::updateWindow (this=this@entry=0x55f576cd67d0) at ./src/scripting/desktopbackgrounditem.cpp:112 #10 0x7ff3f7c8fad6 in KWin::DesktopBackgroundItem::setDesktop (desktop=, this=0x55f576cd67d0) at ./src/scripting/desktopbackgrounditem.cpp:66 #11 KWin::DesktopBackgroundItem::setDesktop (desktop=, this=0x55f576cd67d0) at ./src/scripting/desktopbackgrounditem.cpp:62 #12 KWin::DesktopBackgroundItem::qt_static_metacall (_o=_o@entry=0x55f576cd67d0, _c=_c@entry=QMetaObject::WriteProperty, _id=_id@entry=3, _a=_a@entry=0x7ffe838ea7e0) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:148 #13 0x7ff3f7c8fd93 in KWin::DesktopBackgroundItem::qt_metacall (this=0x55f576cd67d0, _c=QMetaObject::WriteProperty, _id=3, _a=0x7ffe838ea7e0) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:197 #14 0x7ff3f70f430e in QQmlPropertyData::writeProperty (flags=..., value=0x7ffe838ea798, target=, this=) at ../../include/QtQml/5.15.8/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:393 #15 QObjectPointerBinding::write (this=0x55f576d8fdc0, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:742 #16 0x7ff3f70f5b07 in QQmlNonbindingBinding::doUpdate (this=0x55f576d8fdc0, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:258 #17 0x7ff3f70f3664 in QQmlBinding::update (this=0x55f576d8fdc0, flags=...) at qml/qqmlbinding.cpp:194 #18 0x7ff3f70d0165 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #19 0x7ff3f62f3c5b in doActivate (sender=0x55f576db9810, signal_index=27, argv=0x0) at kernel/qobject.cpp:3815 #20 0x7ff3f62f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7ffe838ec3d0, r=0x55f576db9810, this=0x55f576db9d40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x55f575c33c30, signal_index=7, argv=0x7ffe838ec3d0) at kernel/qobject.cpp:3923 #22 0x7ff3f62ed177 in QMetaObject::activate (sender=, m=m@entry=0x7ff3f7fcfbc0 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffe838ec3d0) at kernel/qobject.cpp:3983 #23 0x7ff3f7b93ad3 in KWin::VirtualDesktopManager::currentChanged (this=, _t1=, _t2=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_virtualdesktops.cpp:622 #24 0x7ff3f7cd8148 in KWin::VirtualDesktopManager::setCurrent (this=0x55f575c33c30, newDesktop=0x55f575d55620) at ./src/virtualdesktops.h:62 #25 0x7ff3f7bb4f0e in KWin::Workspace::activateWindow (this=0x55f575c0ca10, window=0x55f575cd8c00, force=) at ./src/activation.cpp:294 #26 0x7ff3f6d29bb4 in NETRootInfo::event(xcb_generic_event_t*, QFlags*, QFlags*) () from /lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 #27 0x7ff3f7c61528 in KWin::RootInfoFilter::event (this=, event=) at ./src/rootinfo_filter.cpp:26 #28 0x7ff3f7c49304 in KWin::Application::dispatchEvent (this=, event=0x7ff3e0031500) at ./src/main.cpp:483 #29 0x7ff3f62b9447 in QA
[kwin] [Bug 467965] KWin crashes intermittently when switching to a window on a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=467965 Andrei Rybak changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466834 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466834] KWin crashes in KWin::Window::isOnOutput() after opening Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=466834 Andrei Rybak changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=467965 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466416] KDE Connect keeps adding devices to Dolphin over and over and over and over and over
https://bugs.kde.org/show_bug.cgi?id=466416 --- Comment #8 from Andrei Rybak --- Jose, thank you for the insight. I will try disabling the MAC randomization on the phone and see if it helps. What is very surprising, however, if it is indeed the root cause, is that KDE Connect itself doesn't seem to be confused by the MAC address randomization. Regardless of the MAC address, KDE Connect seems to be able to keep track of the "trusted" status of the phone and of all the settings of plugins (e.g. the commands in "Run commands"). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470312] New: krunner crashed when typing in 4000000
https://bugs.kde.org/show_bug.cgi?id=470312 Bug ID: 470312 Summary: krunner crashed when typing in 400 Classification: Plasma Product: krunner Version: 5.27.5 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rybak@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Application: krunner (5.27.5) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 5.19.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I've tried to start a calculation that started with the number of 4 million. KRunner crashed several times roughly after typing 400 or 4000. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KRunner (krunner), signal: Segmentation fault [KCrash Handler] #4 0x7f553b83b024 in MathStructure::type() const () from /lib/x86_64-linux-gnu/libqalculate.so.22 #5 0x7f553b835134 in MathStructure::MathStructure(MathStructure const&) () from /lib/x86_64-linux-gnu/libqalculate.so.22 #6 0x7f553b7aa101 in CalculateThread::run() () from /lib/x86_64-linux-gnu/libqalculate.so.22 #7 0x7f553b843534 in Thread::doRun(void*) () from /lib/x86_64-linux-gnu/libqalculate.so.22 #8 0x7f5584694b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f5584726a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 29 (Thread 0x7f54df7fe640 (LWP 90937) "krunner:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f55349a6240) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f55349a6240, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f5584693ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f55349a61f0, cond=0x7f55349a6218) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f55349a6218, mutex=0x7f55349a61f0) at ./nptl/pthread_cond_wait.c:627 #5 0x7f557cd0aced in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f557ccbe35b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f557cd0ac1b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f5584694b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f5584726a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 28 (Thread 0x7f55167fc640 (LWP 37714) "GlobalQueue[16]"): #1 0x7f55846ea6e7 in __GI___nanosleep (req=, rem=) at ../sysdeps/unix/sysv/linux/nanosleep.c:25 #2 0x7f553b844264 in sleep_ms(int) () from /lib/x86_64-linux-gnu/libqalculate.so.22 #3 0x7f553b7b526e in Calculator::calculate(MathStructure*, std::__cxx11::basic_string, std::allocator >, int, EvaluationOptions const&, MathStructure*, MathStructure*, bool) () from /lib/x86_64-linux-gnu/libqalculate.so.22 #4 0x7f5541df392f in QalculateEngine::evaluate (this=0x561fb91c0a80, expression=..., isApproximate=isApproximate@entry=0x7f55167fb9eb, base=base@entry=10, customBase=...) at ./runners/calculator/qalculate_engine.cpp:155 #5 0x7f5541df4cee in CalculatorRunner::calculate (this=0x561fb932c4f0, term=..., isApproximate=0x7f55167fb9eb, base=10, customBase=...) at /usr/include/c++/11/bits/unique_ptr.h:173 #6 0x7f5541df597b in CalculatorRunner::match (this=0x561fb932c4f0, context=...) at ./runners/calculator/calculatorrunner.cpp:126 #7 0x7f55740b810f in ?? () from /lib/x86_64-linux-gnu/libKF5Runner.so.5 #8 0x7f557407abcd in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f557407bab4 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f5574080226 in ThreadWeaver::Thread::run() () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f5584ece733 in operator() (__closure=, __closure=) at thread/qthread_unix.cpp:350 #12 (anonymous namespace)::terminate_on_exception > (t=..., t=...) at thread/qthread_unix.cpp:287 #13 QThreadPrivate::start (arg=0x7f55100029e0) at thread/qthread_unix.cpp:310 #14 0x7f5584694b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #15 0x7f5584726a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 27 (Thread 0x7f5516ffd640 (LWP 37713) "GlobalQueue[15]"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x561fb9338700) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (
[kwin] [Bug 470329] New: Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 Bug ID: 470329 Summary: Monitor power on / off results in stolen input and broken xwayland clients Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: and...@posteo.net Target Milestone: --- SUMMARY *** CPU: AMD 5950x GPU: 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] [1002:744c] (rev c8) Sapphire Nitro+ System Memory: 32GB DDR4 Display(s): DELL 27" 2560x1440@144 DisplayPort and SAMSUNG 75" 3840x2160@120 HDMI Debian 12 Bookworm Kernel: 6.3.3-x64v3-xanmod1 #0~20230517.05b3a98 *** STEPS TO REPRODUCE 1. Have the HDMI display screen powered off while Displayport screen is Primary and active, powered on 2. Start Steam, start a game from library via Proton (Wine) 3. Play the game normally 4. Turn on the HDMI display from remote, the whole desktop flickers, the game client window moves and freezes (depending on game) and loses input. 5. Need to stop (terminate) the frozen game window client and restart OBSERVED RESULT First, desktop flickers and all windows (that maybe are on powered off screen) move to primary screen and then back to screen that was powered on. It seems some xwayland clients are broken, getting freezed and losing focus. Focus is lost from active window (screen). EXPECTED RESULT Screen powers on and displays the configured desktop for it No flickering or minimal flickering, no Window moving from active screen to the other and back. No changing focus from screen to screen. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.3.3-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS ADDITIONAL INFORMATION Testing on Windows I see a short flicker when trying the same operation of turning a screen on / off but the windows do not move. Testing on Linux, this happens, have observed this desktop flicker when turning a display on and the current windows getting moved from screen to screen also while trying Fedora 38 KDE Live 1.6.iso. Not sure if this strictly a KDE Kwin/Plasma issue, I think it's maybe amd/drm something, will raise another issue there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 --- Comment #1 from Andrei Amuraritei --- I have tested this further with: Sway wayland, the same game (ex, FFXIV with Wine via Lutris) does not die in that session when turning on the HDMI screen. Plasma X11, the same game (ex, FFXIV with Wine via Lutris), does not die but the window gets switched (moved?) from fullscreen , where the taskbar is visible at the top and focus on the game stays. Also tested with an older kernel from Debian, 6.1.0-3-amd64, so maybe not drm/amd related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 --- Comment #2 from Andrei Amuraritei --- Also tested with Gnome Wayland, shell version 43.4 and the same game (ex, FFXIV with Wine via Lutris), closes like on the KDE Wayland session. I have also tested running a native Linux version of a game, and it does not close however when the other screen is powered on, desktop flickers and the game window switches from borderless/fullscreen to where taskbar is visible (position top) and game loses focus (input). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 470428] New: Kdevelop crashes during background parsing with clang
https://bugs.kde.org/show_bug.cgi?id=470428
Bug ID: 470428
Summary: Kdevelop crashes during background parsing with clang
Classification: Applications
Product: kdevelop
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: ansl...@yahoo.com
Target Milestone: ---
Application: kdevelop (5.11.230401 (23.04.1))
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.3-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
Started crashing after I changed the active compiler for the project from GCC
to Clang.
The crash can be reproduced every time.
-- Backtrace (Reduced):
#6 __memset_avx2_unaligned_erms () at
../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:328
#7 0x7f28322a7daf in std::__fill_a1(unsigned short*,
unsigned short*, int const&) (__value=, __last=,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:930
#8 std::__fill_a(unsigned short*, unsigned short*, int
const&) (__value=, __last=, __first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:977
#9 std::__fill_n_a(unsigned short*, int, int
const&, std::random_access_iterator_tag) (__value=, __n=3277,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:1128
#10 std::fill_n::{unnamed type#3},
int>(KDevelop::Bucket::{unnamed type#3},
KDevelop::Bucket::{unnamed type#3}, int const&)
(__value=,
__n=KDevelop::Bucket::NextBucketHashSize,
__first=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13/bits/stl_algobase.h:1157
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 470428] Kdevelop crashes during background parsing with clang
https://bugs.kde.org/show_bug.cgi?id=470428
--- Comment #3 from Andrei Slavoiu ---
Hi, first of all, after clearing the cache it no longer crashes. But if it
helps to prevent this in the future:
The entire system is built with CFLAGS="-march=native -ggdb3 -O2 -pipe
-fdiagnostics-color". See attached compiler.info for what -march=native
translates to on my system.
This is the content of stl_algobase.h around that line.
template
_GLIBCXX20_CONSTEXPR
inline typename
__gnu_cxx::__enable_if<__is_scalar<_Tp>::__value, void>::__type
__fill_a1(_ForwardIterator __first, _ForwardIterator __last,
const _Tp& __value)
{
const _Tp __tmp = __value;
930: for (; __first != __last; ++__first)
*__first = __tmp;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 470428] Kdevelop crashes during background parsing with clang
https://bugs.kde.org/show_bug.cgi?id=470428 --- Comment #4 from Andrei Slavoiu --- Created attachment 159346 --> https://bugs.kde.org/attachment.cgi?id=159346&action=edit compiler.info -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 408821] "Allow Pepper Plugins (Flash Plugin)" checkbox has the opposite effect
https://bugs.kde.org/show_bug.cgi?id=408821 Andrei Slavoiu changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Andrei Slavoiu --- Turns out there was a problem with my flash plugin and when the checkbox was disabled it falled back to HTML5. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470312] krunner crashed when typing in 4000000
https://bugs.kde.org/show_bug.cgi?id=470312 --- Comment #2 from Andrei Rybak --- libqalculate22 installed version is 4.6.1-0xneon+22.04+jammy+release+build9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 Andrei Amuraritei changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
