[krusader] [Bug 485225] Krusader issue with mime types after P6 update
https://bugs.kde.org/show_bug.cgi?id=485225 Marek Samec changed: What|Removed |Added CC||samec.ma...@gmail.com --- Comment #3 from Marek Samec --- Same issue on Arch linux. I don't see kf5html or similar package on AUR at the moment. KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 --- Comment #5 from Marek --- BTW, clipboard doesn't work in KDE 6.x under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 486659] Multiple routes added through different gateways for same Remote Gateway IP - fortisslvpn
https://bugs.kde.org/show_bug.cgi?id=486659 --- Comment #1 from Marek --- Bug still present in plasma-nm-fortisslvpn 6.0.5-1.fc40. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486160] All akonadi network resources are offline
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #7 from Marek Greško --- Same here also with latest updates (akonadi-1.13.0-126.fc40.x86_64). -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 --- Comment #4 from Marek --- (In reply to Marek from comment #3) > In my case, installing package wl-clipboard solved issue. > Now it works from/to VM from wayland native and non-native apps. Not true, after reboot it logged me into X11. Clipboard still not working, even after installing wl-clipboard package. -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 --- Comment #3 from Marek --- In my case, installing package wl-clipboard solved issue. Now it works from/to VM from wayland native and non-native apps. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 487254] Not possible to surf .dn42 domains
https://bugs.kde.org/show_bug.cgi?id=487254 --- Comment #2 from Marek Küthe --- Created attachment 169633 --> https://bugs.kde.org/attachment.cgi?id=169633=edit Here I click on Enter at the address bar and it searches for the address instead of calling it up. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 487254] Not possible to surf .dn42 domains
https://bugs.kde.org/show_bug.cgi?id=487254 --- Comment #1 from Marek Küthe --- Created attachment 169632 --> https://bugs.kde.org/attachment.cgi?id=169632=edit The link in the address bar. Here I have called `myip.dn42` by a link and the address is displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 487254] New: Not possible to surf .dn42 domains
https://bugs.kde.org/show_bug.cgi?id=487254 Bug ID: 487254 Summary: Not possible to surf .dn42 domains Classification: Applications Product: angelfish Version: 24.02.2 Platform: postmarketOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: m...@mk16.de Target Milestone: --- Created attachment 169631 --> https://bugs.kde.org/attachment.cgi?id=169631=edit Page accessed via a link SUMMARY Hello, I would like to surf with Angelfish in dn42. The dn42 is a decentralized overlay network which uses internet technologies like BGP. Unfortunately Angelfish does not seem to accept dn42 domains. However, I can access a .dn42 page if I click on a corresponding link. Numbers are allowed in domain names - even if rather uncommon. STEPS TO REPRODUCE 1. Establish a VPN connection to the dn42. 2. Try to go to a `.dn42` domain like `myip.dn42`. OBSERVED RESULT The address is searched for. EXPECTED RESULT The address is browsed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.6.3 Kernel version: 6.9.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 470057] Shared Clipboard of Wayland applications is not working for VMs
https://bugs.kde.org/show_bug.cgi?id=470057 Marek changed: What|Removed |Added CC||enc...@vivaldi.net --- Comment #2 from Marek --- Fresh install of Debian 12 with KDE in VMware, fully updated, Windows 11 host. Clipboard doesn't work in wayland native apps. It works when copy/paste from Windows to KDE VM to lets say Firefox, Chrome, but doesn't work to Konsole, LibreOffice, Dolphin, etc. KDE Plasma: 5.27.5 KDE Frameworks: 5.103.0 QT: 5.15.8 Kernel: 6.1.0-18 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 486659] New: Multiple routes added through different gateways for same Remote Gateway IP - fortisslvpn
https://bugs.kde.org/show_bug.cgi?id=486659 Bug ID: 486659 Summary: Multiple routes added through different gateways for same Remote Gateway IP - fortisslvpn Classification: Plasma Product: plasma-nm Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: enc...@vivaldi.net Target Milestone: --- SUMMARY Connection itslef to Fortigate Remote Gateway works using openfortivpn and plasma-nm-fortisslvpn. However nothing can be reached inside tunnel. Route list while disconnected: mbabinca@fedora:~$ ip r default via 192.168.1.1 dev wls192u4u1 proto dhcp src 192.168.1.123 metric 600 192.168.1.0/24 dev wls192u4u1 proto kernel scope link src 192.168.1.123 metric 600 Route list while connected from cli - everything works fine: mbabinca@fedora:~$ sudo openfortivpn -u user -p password 80.156.225.162 mbabinca@fedora:~$ ip r default via 192.168.1.1 dev wls192u4u1 proto dhcp src 192.168.1.123 metric 600 10.40.33.33 dev ppp0 scope link 10.40.33.44 dev ppp0 scope link 10.40.51.0/24 dev ppp0 scope link 80.156.225.162 via 192.168.1.1 dev wls192u4u1 192.168.1.0/24 dev wls192u4u1 proto kernel scope link src 192.168.1.123 metric 600 Route list while connected from plasma-nm-fortisslvpn - traffic into tunnel doesn't work: mbabinca@fedora:~$ ip r default via 192.168.1.1 dev wls192u4u1 proto dhcp src 192.168.1.123 metric 600 10.19.83.1 dev ppp0 proto static scope link metric 50 10.40.33.33 via 10.19.83.1 dev ppp0 proto static metric 50 10.40.33.44 via 10.19.83.1 dev ppp0 proto static metric 50 10.40.51.0/24 via 10.19.83.1 dev ppp0 proto static metric 50 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 80.156.225.162 via 192.168.1.1 dev wls192u4u1 proto static metric 50 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 metric 50 192.168.1.0/24 dev wls192u4u1 proto kernel scope link src 192.168.1.123 metric 600 192.168.1.1 dev wls192u4u1 proto static scope link metric 50 Notice, that for remote gateway 80.156.225.162 three routes are added instead of one while using cli. 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 80.156.225.162 via 192.168.1.1 dev wls192u4u1 proto static metric 50 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 metric 50 If I manually delete at least 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 traffic to tunnel start working. If I remove second route 80.156.225.162 dev ppp0 proto kernel scope link src 10.19.83.1 metric 50, then dnf list installed command makes output again. While those routes are present, dnf list installed hangs for a while and won't produce any output. Why is plasma-applet making routes to Remote Gateway through tunnel? That doesn't make sense. In KDE 5.x, applet works fine and only one route for Remote Gateway is created. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Installed packages: mbabinca@fedora:~$ dnf list installed | grep forti NetworkManager-fortisslvpn.x86_64 1.4.1-5.20231021gite201da5.fc40 @fedora openfortivpn.x86_64 1.21.0-4.fc40 @fedora plasma-nm-fortisslvpn.x86_64 6.0.4-1.fc40 @updates -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMWare and VirtualBox VMs
https://bugs.kde.org/show_bug.cgi?id=427060 Marek changed: What|Removed |Added CC||enc...@vivaldi.net Platform|openSUSE|Ubuntu --- Comment #56 from Marek --- Bug is not fixed! Host: Intel i7 11850H OS: Win 11 22H2 VMware Player: 17.5.0 GPU: NVIDIA T1200 (anyways, happens with hardware acceleration enabled/disabled) Fresh install: Guest: Kubuntu 23.10 KDE: 5.27.8 KDE Framework: 5.11.0 QT Version: 5.15.10 Kernel: 6.5.0-28 Is there any other workaround/fix other than using environment variable KWIN_FORCE_SW_CURSOR=1? That will fix it, but also disables automatic realease/grab mouse into VM. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486160] All akonadi network resources are offline
https://bugs.kde.org/show_bug.cgi?id=486160 Marek Greško changed: What|Removed |Added Summary|Cannot switch imap account |All akonadi network |to online |resources are offline -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 Marek Greško changed: What|Removed |Added Version|unspecified |6.0.2 Product|kmail2 |Akonadi CC||c...@carlschwan.eu Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #6 from Marek Greško --- Hmm, also korganizer is offline. so it is definitely akonadi bug, not kmail. Marek -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484706] IMAP-folders stay offline
https://bugs.kde.org/show_bug.cgi?id=484706 Marek Greško changed: What|Removed |Added CC||marek.gre...@protonmail.com --- Comment #1 from Marek Greško --- Hello, I confirm the behavior. I created another bug 486160 for this and found this report thereafter. Marek -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #5 from Marek Greško --- I just found bug 484706. It seems to be the same. Quite a long time nobody looked at it. Is it worth to use such software? Marek -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #4 from Marek Greško --- It seems to be an akonadi problem. When running akonadiconsole I see many resources offline. I am not able to make them back online. Maybe akonadi thinks there is no network connection or something like that? How does it detect such things? Thanks Marek -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #3 from Marek Greško --- Hello, is there some debug possible. I cannot imagine where I can start. Why the resource is offline and how to make it try to connect? Thanks Marek -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #2 from Marek Greško --- Some interesting parts from Akonadi.error file: 2024-04-26T16:24:24 [INFO ] org.kde.pim.akonadiserv2024-04-26T16:24:25 [INFO ] org.kde.pim.akonadicontrol: Akonadi server is now operational. 2024-04-26T16:24:25 [CRITICAL] org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_imap_resource_8', error message: '' 2024-04-26T16:26:51 [WARN ] org.kde.pim.akonadiserver: ItemRetrievalJob for request 17 finished with error: "Unable to retrieve item from resource: Nemôžete vybrať položku v offline móde." 2024-04-26T16:26:51 [WARN ] org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection MessageViewer-94821059623520 (0x558219bb0170) : Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Nemôžete vybraÅ¥ položku v offline móde. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 --- Comment #1 from Marek Greško --- I just tried to clear akonadi cache from kmail2 menu. I received notofication that IMAP resource and local folders resource are corrupt. What could be the problem? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486160] New: Cannot switch imap account to online
https://bugs.kde.org/show_bug.cgi?id=486160 Bug ID: 486160 Summary: Cannot switch imap account to online Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: marek.gre...@protonmail.com Target Milestone: --- SUMMARY I just upgraded Fedora 39 to Fedora 40. When I lggen in to the kde plasma 6 session after upgrade and run the kmail 2 application, my IMAP account is offline and cannot be switched online. There is no reaction on clicking "Click here to switch to online" (sorry if not properly translated, I see it in Slovak). STEPS TO REPRODUCE 1. Upgrade Fedora 39 to Fedora 40. 2. Login to plasma 6 session and run kmail2. 3. Try to switch IMAP resource online. OBSERVED RESULT IMAP resource is not switched to online after clicking. No change after click. EXPECTED RESULT The IMAP resource should be online without needing to click anything. SOFTWARE/OS VERSIONS Fedora 40 with latest updates. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485633] plasmasheel crash when running with Vulkan renderer on Nvidia
https://bugs.kde.org/show_bug.cgi?id=485633 --- Comment #1 from Marek Pikuła --- Created attachment 168581 --> https://bugs.kde.org/attachment.cgi?id=168581=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485633] New: plasmasheel crash when running with Vulkan renderer on Nvidia
https://bugs.kde.org/show_bug.cgi?id=485633 Bug ID: 485633 Summary: plasmasheel crash when running with Vulkan renderer on Nvidia Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: marek+...@pikula.co Target Milestone: 1.0 Application: plasmashell (6.0.3) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.8.5-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.3 [CoredumpBackend] -- Information about the crash: I tried different Plasma renderers and after selecting Vulkan renderer plasmashell was functional, but once a while it crashed and restarted. After going with OpenGL renderer everything goes back to normal. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x7bbd4e2ab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #7 0x7bbd4e25a6c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7bbd4e2424b8 in __GI_abort () at abort.c:79 #9 0x7bbd5126d4f2 in wl_abort (fmt=fmt@entry=0x7bbd512726d8 "Tried to add event to destroyed queue\n") at ../wayland-1.22.0/src/wayland-util.c:462 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Marek Pikuła changed: What|Removed |Added CC||marek+...@pikula.co -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476967] Plasma Integration Firefox extension does not work on LibreWolf
https://bugs.kde.org/show_bug.cgi?id=476967 Marek changed: What|Removed |Added CC||stargat...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=476161 --- Comment #4 from Marek Brunda --- Honestly, without the ability to use the effect for virtual desktops switching it is just no more than an useless toy. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=476161 Marek Brunda changed: What|Removed |Added CC||ma...@brunda.name -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 Marek Pikuła changed: What|Removed |Added CC||marek+...@pikula.co -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461350] Krita Freezes and crashes without a crash log - no matter what - after a few minutes of usage.
https://bugs.kde.org/show_bug.cgi?id=461350 Marek Piskule changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Marek Piskule --- (In reply to Dmitry Kazakov from comment #3) > Hi, Marek! > > Could you please check the nightly version of the upcoming Krita 5.2? We > have fixed a lot of animation-related issues, including the ones happening > when applying transformation or move operations to the animated layer. There > were multiple issues caused by the new implementation of the 'auto-keyframe' > option: > > https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/ > > If you still experience a crash in this build, please try disabling > "Auto-create keyframe" option and check if the crash goes away. Checking for > 'kritacrash.log' again would also help. Hi, Dmitry! Firstly, I tried the nightly-x64-5.3.0-prealpha-bc09a52527 build, and Krita no longer crashes! The issue is resolved. Secondly, thank you for replying to such an old and cryptic assignment ^^" I appreciate it and you made me respect the Krita team a lot more. :-) If it crashes, I'll disable "Auto-create keyframe". But currently I'm happy with the performance. Best wishes, and thank you a lot for the help once again! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469937] Akonadi crashed at startup after Fedora 37 upgrade to 38
https://bugs.kde.org/show_bug.cgi?id=469937 --- Comment #1 from Marek --- I restrarted the machine, akonadi seems to be stable: $ pgrep -fl akonadi 3040 akonadi_control 3225 akonadiserver 3265 mysqld 3599 akonadi_akonote 3600 akonadi_archive 3601 akonadi_birthda 3602 akonadi_contact 3603 akonadi_followu 3604 akonadi_google_ 3605 akonadi_ical_re 3606 akonadi_indexin 3608 akonadi_maildir 3610 akonadi_maildis 3611 akonadi_mailfil 3614 akonadi_mailmer 3616 akonadi_migrati 3617 akonadi_newmail 3620 akonadi_sendlat 3622 akonadi_unified So maybe it was just a transient upgrade problem. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469937] New: Akonadi crashed at startup after Fedora 37 upgrade to 38
https://bugs.kde.org/show_bug.cgi?id=469937 Bug ID: 469937 Summary: Akonadi crashed at startup after Fedora 37 upgrade to 38 Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: marek.schim...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.23.0 (23.04.0)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.1.18-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 38 (Thirty Eight)" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I wasn't doing anything, the system rebooted after upgrade and KDE started (I have autologin set up). I'm not sure if this is reproductible. I'll reboot and see. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 0x7fabc62b0844 in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fabc625fabe in raise () from /lib64/libc.so.6 #6 0x7fabc624887f in abort () from /lib64/libc.so.6 #7 0x7fabc64df1c0 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) () from /lib64/libstdc++.so.6 #8 0x55daf5f6815f in Akonadi::Server::DataStore::debugLastDbError(char const*) const () #9 0x55daf5f5e152 in Akonadi::Server::DataStore::open() () #10 0x55daf5f5ec40 in Akonadi::Server::DataStore::database() () #11 0x55daf5ee74ca in Akonadi::Server::AkonadiServer::setupDatabase() () #12 0x55daf5ee95d7 in Akonadi::Server::AkonadiServer::init() () #13 0x7fabc6adf73b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7fabc6ab3d2b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fabc6ab71f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #16 0x7fabc6b06e2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #17 0x7fabc4b1339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7fabc4b71438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #19 0x7fabc4b10a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7fabc6b06919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7fabc6ab270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fabc6aba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #23 0x55daf5ee2f2b in main () [Inferior 1 (process 3179) detached] The reporter indicates this bug may be a duplicate of or related to bug 439305, bug 468985, bug 469033. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 469444] New: Ability to set the counting of paragraphs in the margins via Preferences
https://bugs.kde.org/show_bug.cgi?id=469444 Bug ID: 469444 Summary: Ability to set the counting of paragraphs in the margins via Preferences Classification: Applications Product: ghostwriter Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: mareklac...@tutanota.com Target Milestone: --- It would be nice to have the ability for setting for paragraphs to be numerically counted in the margins, alongside as you type text, and every time a new paragraph is started, new number (depending on the paragraph number against the whole written text) would get assigned to it in the margins. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469093] New: Crash after configuring Google Groupware source
https://bugs.kde.org/show_bug.cgi?id=469093
Bug ID: 469093
Summary: Crash after configuring Google Groupware source
Classification: Frameworks and Libraries
Product: Akonadi
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Google Resource
Assignee: kdepim-b...@kde.org
Reporter: marek.sil...@gmail.com
CC: c...@carlschwan.eu, dvra...@kde.org
Target Milestone: ---
Application: akonadi_google_resource (5.23.0 (23.04.0))
Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.2.12-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.4 [KCrashBackend]
-- Information about the crash:
Everytime I try to configure Google Groupware Akonadi plugin / agent, it
crashes. Worked with previous version of KDE / Kontact / Akonadi.
The crash can be reproduced every time.
-- Backtrace:
Application: Google Groupware (not configured) (akonadi_google_resource),
signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f1d210a0953 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f1d21051ea8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f1d2103b53d in __GI_abort () at abort.c:79
#10 0x7f1d2169fede in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffd2f925138, msg=msg@entry=0x7f1d21977380 "ASSERT failure
in %s: \"%s\", file %s, line %d") at global/qlogging.cpp:893
#12 0x7f1d2169ff9d in qt_assert_x(char const*, char const*, char const*,
int) (where=where@entry=0x7f1d2336a830 "Akonadi::ResourceBase::retrieveItem()",
what=what@entry=0x7f1d2336a760 "The base implementation of retrieveItem() must
never be reached. You must implement either retrieveItem() or
retrieveItems(Akonadi::Item::List, QSet) overload to handle item
retrieval requ"..., file=file@entry=0x7f1d2336a718
"/usr/src/debug/akonadi/akonadi-23.04.0/src/agentbase/resourcebase.cpp",
line=line@entry=1465) at global/qglobal.cpp:3399
#13 0x7f1d23335695 in Akonadi::ResourceBase::retrieveItem(Akonadi::Item
const&, QSet const&) (this=this@entry=0x7ffd2f9258a0,
item=, parts=...) at
/usr/src/debug/akonadi/akonadi-23.04.0/src/agentbase/resourcebase.cpp:1460
#14 0x7f1d233505ad in
Akonadi::ResourceBasePrivate::slotPrepareItemRetrievalResult(KJob*)
(this=, job=) at
/usr/src/debug/akonadi/akonadi-23.04.0/src/agentbase/resourcebase.cpp:1043
#15 0x7f1d218beb41 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd2f9252b0, r=, this=0x5636ef57b4b0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x5636eef71ca0,
signal_index=6, argv=0x7ffd2f9252b0) at kernel/qobject.cpp:3923
#17 0x7f1d22d617da in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x5636eef71ca0, _t1=, _t1@entry=0x5636eef71ca0,
_t2=...) at
/usr/src/debug/kcoreaddons/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#18 0x7f1d22d6752c in KJob::finishJob(bool) (this=0x5636eef71ca0,
emitResult=) at
/usr/src/debug/kcoreaddons/kcoreaddons-5.105.0/src/lib/jobs/kjob.cpp:98
#19 0x7f1d218b1c80 in QObject::event(QEvent*) (this=0x5636eef71ca0,
e=0x5636ef42d920) at kernel/qobject.cpp:1347
#20 0x7f1d22578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5636eef71ca0, e=0x5636ef42d920) at
kernel/qapplication.cpp:3640
#21 0x7f1d2188e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5636eef71ca0, event=0x5636ef42d920) at
kernel/qcoreapplication.cpp:1064
#22 0x7f1d2188e093 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#23 0x7f1d2188eb33 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5636ee697290) at
kernel/qcoreapplication.cpp:1821
#24 0x7f1d218d4f58 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x5636ee76f510) at kernel/qeventdispatcher_glib.cpp:277
#25 0x7f1d1f90f53b in g_main_dispatch (context=0x7f1d14000ee0) at
../glib/glib/gmain.c:3460
#26 g_main_context_dispatch (context=0x7f1d14000ee0) at
../glib/glib/gmain.c:4200
#27 0x7f1d1f96c219 in g_main_context_iterate.constprop.0
(context=0x7f1d14000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#28 0x7f1d1f90e1a2 in g_main_context_iteration (context=0x7f1d14000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#29 0x7f1d218d8d3c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5636ee774600, flags=...) at
[kdevelop] [Bug 467980] Kdevelop hanged afer run using CLI
https://bugs.kde.org/show_bug.cgi?id=467980
--- Comment #3 from Marek Witkowski ---
(In reply to Igor Kushnir from comment #1)
> Try opening another session or a new session: `kdevelop -n test-session`.
>
> The backtrace is too short. Have you tried attaching to the hanging kdevelop
> process with GDB and printing the backtrace of all threads?
> gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 >
> /some/path/hanging-kdevelop.bt
> ("12345" in the command stands for the hanging kdevelop process ID)
> If you get the `ptrace: Operation not permitted.` error, run the following
> command before repeating the gdb command:
> echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
> (you can revert the configuration change with `echo 1 | sudo tee
> /proc/sys/kernel/yama/ptrace_scope`)
After `kdevelop -n test-session` works fine.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 467980] Kdevelop hanged afer run using CLI
https://bugs.kde.org/show_bug.cgi?id=467980 --- Comment #2 from Marek Witkowski --- Created attachment 157744 --> https://bugs.kde.org/attachment.cgi?id=157744=edit kdevelop process with GDB and printing the backtrace of all threads kdevelop process with GDB and printing the backtrace of all threads after: gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 > /some/path/hanging-kdevelop.bt -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 467980] New: Kdevelop hanged afer run using CLI
https://bugs.kde.org/show_bug.cgi?id=467980
Bug ID: 467980
Summary: Kdevelop hanged afer run using CLI
Classification: Applications
Product: kdevelop
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: marek.witkowski.p...@gmail.com
Target Milestone: ---
Application: kdevelop (5.10.221203 (22.12.3))
Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.8-1-default x86_64
Windowing System: Wayland
Distribution: openSUSE Tumbleweed
DrKonqi: 5.27.3 [KCrashBackend]
-- Information about the crash:
After run kdevelop using CLI:
: kdevelop .
application started but has stoped and hanged.
info from terminal:
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number of the
ExtraNames fields should match the number of ExtraTypes fields
kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number of the
ExtraNames fields should match the number of ExtraTypes fields
kf.kio.workers.file: copy() QUrl("file:///home/marekwu/Pobrane/Pobrane.kdev4")
to QUrl("file:///tmp/kdevelop.NmZZKK") mode= -1
kf.kio.workers.file: the file doesn't have any xattr
QAbstractItemModel::endInsertRows: Invalid index ( 2 , 0 ) in model
QSortFilterProxyModel(0x55a1f1f2aa60)
QAbstractItemModel::endInsertRows: Invalid index ( 3 , 0 ) in model
QSortFilterProxyModel(0x55a1f1f2aa60)
QAbstractItemModel::endInsertRows: Invalid index ( 2 , 0 ) in model
QSortFilterProxyModel(0x55a1f1f2aa60)
QAbstractItemModel::endInsertRows: Invalid index ( 2 , 0 ) in model
QSortFilterProxyModel(0x55a1f1f2aa60)
The crash can be reproduced every time.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
[KCrash Handler]
#4 0x7f65dc733dda in KDevelop::ProjectController::openProjectForUrl
(this=0x5596c462b4c0, sourceUrl=...) at
/usr/src/debug/kdevelop-22.12.3/kdevplatform/shell/projectcontroller.cpp:795
#5 0x5596c2c1b5eb in main (argc=, argv=) at
/usr/src/debug/kdevelop-22.12.3/app/main.cpp:830
[Inferior 1 (process 2516) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 467461] New: Digikam crashes on album creation
https://bugs.kde.org/show_bug.cgi?id=467461 Bug ID: 467461 Summary: Digikam crashes on album creation Classification: Applications Product: digikam Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: mail...@zalfresso.com Target Milestone: --- Application: digikam (8.0.0-beta1) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 5.19.0-26-generic x86_64 Windowing System: X11 Distribution: Ubuntu Lunar Lobster (development branch) DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: When I try to create new album, digikam is crashing. I was running it on Kubuntu 22.10 and after upgrade to 23.04 beta, hoping that the issue may be solved. Unfortunately, it is not - still crashes... The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7f279d4f093e in QObject::removeEventFilter(QObject*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f279b0f229a in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () at /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #6 0x7f279b0f22cd in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () at /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #7 0x7f279d4e58ae in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f279e1aa586 in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f279f0c92cd in Digikam::DTextEdit::~DTextEdit() () at /usr/lib/digikam/libdigikamcore.so.8.0.0 #10 0x7f279d4e58ae in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f279e1aa586 in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f279e1aa8cd in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f279d4e58ae in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f279e1aa586 in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f279ff62979 in () at /usr/lib/digikam/libdigikamgui.so.8.0.0 #16 0x7f279ff56403 in () at /usr/lib/digikam/libdigikamgui.so.8.0.0 #17 0x7f279ff4aa15 in () at /usr/lib/digikam/libdigikamgui.so.8.0.0 #18 0x7f279d4f39dc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f279e165546 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f279e168203 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f279e2f1342 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f279e2f924c in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f279e1aec28 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f279e16bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f279e174612 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f279d4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f279e172712 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f279e1c8625 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f279e1cb590 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f279e16bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f279d4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f279d94240d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #33 0x7f279d9164bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #34 0x7f271b67e54e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #35 0x7f278e264afd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f278e2bf468 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7f278e2623f0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7f279d514e7a in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7f279d4b97cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f279e2f6b93 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #41 0x7f279e2f6cb3 in QMenu::exec(QPoint const&, QAction*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #42
[kruler] [Bug 36100] alternate units of measurement for kruler (inches)
https://bugs.kde.org/show_bug.cgi?id=36100 Ph. Marek changed: What|Removed |Added CC||phil...@marek.priv.at --- Comment #13 from Ph. Marek --- Yeah, please add real-world units as well (I know that this depends on the DPI being correct!); similarly, angles (against the horizontal or vertical resp, against another kruler) and/or areas would be quite nice. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Marek changed: What|Removed |Added CC||skro...@skrobul.com --- Comment #6 from Marek --- Could this be related to https://bugs.kde.org/show_bug.cgi?id=443155 ? -- You are receiving this mail because: You are watching all bug changes.
[AudioCD-KIO] [Bug 124514] audiocd encoding to a renamed folder errors out
https://bugs.kde.org/show_bug.cgi?id=124514 Ph. Marek changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Ph. Marek --- Still happens -- renaming the copy destination breaks the copy process. And the whole behaviour hasn't improved in the 17 years. Simply opening a konqueror window with an audio cd in the drive hurts -- it spins up, it spins down, it spins up, seeks, spins down, spins up, ... When copying from the Ogg Vorbis folder on the CD to a local SSD I'd expect the whole 60x speed that the drive is capable of -- after all, the simple transcode to MP3 or OGG isn't the bottleneck any more, and even if it was, a modern machine can cache quite a few audio CDs in RAM (simply in the Linux buffers) before breaking a sweat. But instead of having a full copy of the CD in a minute or so, the window for _a single file_ is open for 15 seconds (with a 100% progress bar!) while the drive is clicking on and off before the progress bar resets and then starts to move. The seeking sounds continue ISTR that the number of parallel KIO threads was configurable with KDE 3.5 or so, is that still possible somewhere? Sorry (a bit) about the rant. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 464227] New: Search results incomplete
https://bugs.kde.org/show_bug.cgi?id=464227 Bug ID: 464227 Summary: Search results incomplete Classification: Applications Product: kcharselect Version: 22.12.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: cf...@kde.org Reporter: phil...@marek.priv.at Target Milestone: --- SUMMARY Searching for characters gives incomplete results. STEPS TO REPRODUCE 1. Open kcharselect 2. Enter "c" (without quotes) in search bar 3. Press to search OBSERVED RESULT I get about 14 results - all lowercase. EXPECTED RESULT The uppercase results should also be shown; eg. when using "caron" as search phrase, both upper- and lowercase variants get displayed. ADDITIONAL INFORMATION Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413956] Night color location values doesn’t use regional settings for decimal separator
https://bugs.kde.org/show_bug.cgi?id=413956 Marek changed: What|Removed |Added CC||stargat...@seznam.cz --- Comment #1 from Marek --- Happens to me as well. I have regional settings with ',' as a decimal separator. Few other points: - when I'm changing the values, it only allows me to enter them with respecting the regional settings (I can enter '47,3245', but not '47.3245') - after changing the values I can't save them (the Apply button is greyed out) - when I go to other tab, there is no dialog that the 'settings have changed' - afer going back to the Night Color settings, the values I entered are clipped from the decimal separator to the end (so '47,3245' becomes '47') I tested this with Czech regional settings for numbers. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.2-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461350] Krita Freezes and crashes without a crash log - no matter what - after a few minutes of usage.
https://bugs.kde.org/show_bug.cgi?id=461350 --- Comment #2 from Marek Piskule --- (In reply to Dmitry Kazakov from comment #1) > Hi, Marek! > > Do you have a crash log in %localappdata%\kritacrash.log? It seems to be not > in the package Hi, Dmitry! There is no crash log in %localappdata% either. That is the problem that made me report the bug. How can I record the reason of freezing after Krita freezes? It dumps nothing. Neither to the console, or the crash log. Krita freezes without a reason given. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461350] New: Krita Freezes and crashes without a crash log - no matter what - after a few minutes of usage.
https://bugs.kde.org/show_bug.cgi?id=461350 Bug ID: 461350 Summary: Krita Freezes and crashes without a crash log - no matter what - after a few minutes of usage. Classification: Applications Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: piskul...@gmail.com Target Milestone: --- Created attachment 153432 --> https://bugs.kde.org/attachment.cgi?id=153432=edit Packaged crash logs, plus some screenshots SUMMARY *** On my system, Krita crashes for no reason. I tried disabling autosave, reducing and increasing Cache, memory... I got 16GB of RAM and 40GB of free storage SSD space. I am trying to animate on a 720x720 canvas at 15FPS. I even erased the Resource Folder. No dice. Tried the 5.0.2 version installed on my PC, updated to stable 5.1.1, updated that to the plus variant of 5.1.1 (3b6b341425 build). Haven't tried the nightly build, not willing to introduce other quirks. Closed down all aplications (except for Firefox and Classic-Shell which I use HEAVILY). Using built-in Windows protection as the antivirus, it shouldn't conflict. No dice. Other animation apps (Pencil2D, Flash CS6) work fine. I hope you'll be able to identify the problem, this is insane. I love Krita too much, but this is infuriating. I don't know what to do. *** STEPS TO REPRODUCE 1. Use a factory-reset Krita of any 5.1.1 build (Stable, Plus) for an exteded amount of time 2. Use a brush and draw 3. It freezes and doesn't produce a crash log. Not even in the Krita com console. OBSERVED RESULT It crashes. EXPECTED RESULT It shouldn't crash. SOFTWARE/OS VERSIONS Windows: Windows 10 (10.0) 10.0.19044 KDE Plasma Version: Can't find KDE Frameworks Version: Can't find Qt Version: 5.12.12 ADDITIONAL INFORMATION Using Wacom CTL-480 as the tablet, with Windows Ink enabled. Driver version: 6.3.46-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 --- Comment #41 from Marek Brunda --- "they are not used widely based on support information from various bug reports" - this is extremely wrong. If it didn't show up in bug reports, it means it was working very well." - You're right, I've used it on several computers for a number of years even with various Linux distributions and never had a problem, even when using it with Wine or OpenGL full screen applications and games. Everything worked as expected. On Mon, Jun 20, 2022 at 3:55 AM aditsu wrote: > https://bugs.kde.org/show_bug.cgi?id=438883 > > aditsu changed: > >What|Removed |Added > > > CC||adi...@yahoo.com > > --- Comment #40 from aditsu --- > I've just been hit by this catastrophe too. > "they are not used widely based on support information from various bug > reports" - this is extremely wrong. If it didn't show up in bug reports, it > means it was working very well. > This is a SEVERE degradation of user experience. I would consider > volunteering > to help fix this disaster, if it didn't involve learning an entirely new > framework (or multiple frameworks?) from scratch. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You voted for the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 --- Comment #11 from Marek --- I created a new user, logged into Plasma and systemsettings worked. Then I fixed my installation with rm .config/systemsettingsrc .config/kde.org/systemsettings.conf Logged out & in again, systemsettings now open. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 --- Comment #3 from Marek --- Created attachment 147252 --> https://bugs.kde.org/attachment.cgi?id=147252=edit QT_DEBUG_PLUGINS=1 systemsettings > /tmp/debug.txt 2>&1 The output looks OK to me. Still no indication why the plugins are not loaded. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 --- Comment #1 from Marek --- I found this post with the same problem (one of their problems..): https://forum.artixlinux.org/index.php/topic,3747.msg0.html A "solution" proposed there is to install amd-ucode package, which doesn't exist for Fedora (at least not with "amd" in the name). I'm doubtful as why processor microcode package should affect systemsettings5... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451054] New: Systemsettings don't open after latest update
https://bugs.kde.org/show_bug.cgi?id=451054 Bug ID: 451054 Summary: Systemsettings don't open after latest update Product: systemsettings Version: 5.24.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: marek.schim...@gmail.com Target Milestone: --- SUMMARY Systemsettings doesn't work. When I tried to execute it from the terminal, I got: $ systemsettings5 org.kde.systemsettings.app: System Settings was unable to load any views, and hence has nothing to display. qt.qpa.wayland: Wayland does not support QWindow::requestActivate() $ echo $? 0 $ systemsettings5 --list The following modules are available: kcm_about-distro - Information About This System kcm_access - Configure Accessibility Options kcm_activities - Activities help you to focus on a specific task kcm_autostart - Automatically Started Applications kcm_baloofile - Configure File Search kcm_bluetooth - Manage Bluetooth devices kcm_cddb - Configure the CDDB Retrieval kcm_clock - Date and Time kcm_colord - Manage color correction of devices kcm_colors - Choose colour scheme kcm_componentchooser - Choose default Applications kcm_cookies- Configure the way cookies work kcm_cursortheme- Choose mouse cursor theme kcm_desktoppaths - Location for Personal Files kcm_desktoptheme - Choose Plasma style kcm_device_automounter - Configure automatic handling of removable storage media kcm_energyinfo - Energy Consumption Statistics kcm_feedback - Configure user feedback settings kcm_filetypes - Configure file associations kcm_fontinst - Install, manage and preview fonts kcm_fonts - Configure user interface fonts kcm_formats- Numeric, Currency and Time Formats kcm_hotkeys- Configure Input Actions settings kcm_icons - Choose icon theme kcm_joystick - Calibrate Game Controller kcm_kaccounts - Configure your internet accounts such as Google, Live, Owncloud kcm_kamera - Configure Kamera kcm_kdeconnect - Connect and sync your devices kcm_kded - Configure background services kcm_keyboard - Keyboard Hardware and Layout kcm_keys - Configure Keyboard Shortcuts kcm_kscreen- Manage and configure monitors and displays kcm_kwallet5 - KDE Wallet Configuration kcm_kwin_effects - Configure compositor settings for desktop effects kcm_kwin_scripts - Manage KWin scripts kcm_kwin_virtualdesktops - Configure navigation, number and layout of virtual desktops kcm_kwindecoration - Configure window titlebars and borders kcm_kwinoptions- Configure window actions and behaviour kcm_kwinrules - Individual Window Behaviour kcm_kwinscreenedges- Configure active screen corners and edges kcm_kwintabbox - Navigation Through Windows kcm_kwintouchscreen- Configure touch screen swipe gestures kcm_landingpage- Landing page with some basic settings kcm_launchfeedback - Application Launch Feedback kcm_lookandfeel- Choose global look and feel kcm_mouse - Mouse Controls kcm_netpref- Configure generic network preferences, like timeout values kcm_networkmanagement - Edit your Network Connections kcm_nightcolor - Adjust colour temperature at night to reduce eye strain kcm_notifications - Event Notifications and Actions kcm_plasmasearch - Configure search settings kcm_powerdevilactivitiesconfig - Per-Activity Power Management kcm_powerdevilglobalconfig - Advanced Power Management Settings kcm_powerdevilprofilesconfig - Energy Saving kcm_printer_manager- Configure your printers kcm_proxy - Configure the proxy servers used kcm_pulseaudio - Configure audio devices and volume kcm_qtquicksettings- No description available kcm_screenlocker - Configure screen locking kcm_sddm - Configure Login Manager kcm_smb- Credentials used to access SMB shares kcm_smserver - Desktop Session Login and Logout kcm_solid_actions - Manage actions available to the user when connecting new devices kcm_splashscreen -
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Marek Brunda changed: What|Removed |Added CC||ma...@brunda.name --- Comment #38 from Marek Brunda --- Maybe it's time to move to another desktop after 10 years... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Marek Brunda changed: What|Removed |Added CC||ma...@brunda.name --- Comment #18 from Marek Brunda --- Please return this feature. I have been using it for many years and I have never had a single problem with it. So far, I have downgraded and will not upgrade as long as possible. Then I will have to look for alternative solutions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445421] New: Exporting animation with audio - Clip Start chops the audio at the beginning, but doesn't move it (resulting in no or wrongly put audio)... and also moves chopped audio to fr
ffer_blit" "GL_ANGLE_framebuffer_multisample" "GL_ANGLE_texture_usage" "GL_CHROMIUM_bind_uniform_location" "GL_OES_texture_float" "GL_CHROMIUM_copy_texture" "GL_NV_pixel_buffer_object" "GL_OES_texture_half_float" "GL_EXT_robustness" "GL_EXT_texture_format_BGRA" "GL_OES_EGL_image_external_essl3" "GL_OES_rgb8_rgba8" "GL_OES_EGL_image_external" "GL_ANGLE_instanced_arrays" "GL_EXT_read_format_bgra" "GL_NV_EGL_stream_consumer_external" "GL_EXT_color_buffer_half_float" "GL_EXT_texture_compression_dxt1" "GL_ANGLE_texture_compression_dxt5" "GL_OES_texture_npot" "GL_CHROMIUM_bind_generates_resource" "GL_OES_get_program_binary" "GL_OES_texture_half_float_linear" "GL_EXT_debug_marker" "GL_EXT_texture_compression_s3tc_srgb" "GL_EXT_disjoint_timer_query" "GL_ANGLE_pack_reverse_row_order" "GL_CHROMIUM_copy_compressed_texture" "GL_EXT_frag_depth" "GL_KHR_debug" "GL_OES_element_index_uint" "GL_EXT_color_buffer_float" "GL_OES_surfaceless_context" "GL_OES_EGL_image" "" "GL_ANGLE_program_cache_control" "GL_EXT_draw_buffers" "GL_OES_compressed_ETC1_RGB8_texture" "GL_EXT_blend_minmax" "GL_OES_depth32" QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true useBufferInvalidation (config option): false Hardware Information GPU Acceleration: angle Memory: 8128 Mb Number of Cores: 4 Swap Location: C:/Users/Marek/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/Marek/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 60 Screen: 1 Name: \\.\DISPLAY2 Depth: 32 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444026] LO Presentation mode broken after update to Plasma 5.23.0
https://bugs.kde.org/show_bug.cgi?id=444026 Jan-Marek Glogowski changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #5 from Jan-Marek Glogowski --- FYI: the xrandr output suggests the layout is - from left to right: external HDMI (width: 1920) + 236 pixel nothing (the 2156) + laptop screen (width: 1920). In the LO bug report, Axel provided additional input from a little QScreen debug program for 5.22.5 and 5.23.0. The working setup with 5.22.5 doesn't have this gap, but since it's on a different machine, it's not yet clear it's related to the update. Still one idea is, that the LO window / screen positioning code might somehow mix up width and offset; Axel's monitor setup is uncommon. FWIW gtk and direct xlib show the same behavior for him. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436956] Multiple images copy paste issues
https://bugs.kde.org/show_bug.cgi?id=436956 --- Comment #17 from Jan-Marek Glogowski --- (In reply to Nate Graham from comment #16) > Jan-Marek, that specific issue appears to be caused by a Qt bug, which KDE > developer Jan Pontaoski has helpfully fixed already in > https://codereview.qt-project.org/c/qt/qtwayland/+/366769. The fix will be > backported into the KDE patch collection for Qt 5.15. Thanks for the quick reply. Very much looks like my LO bug. Now I just need to tell Debian to fix a non-security bug in QtWayland; it is really nasty... (I could use a QImage to catch the "application/x-qt-image" type and use convertToFormat to get the right stuff, but this feels like a horrible workaround :-( ... still tempting, but then other non-qt apps will still fail. So guess I'll just wait for a fixed Qt5) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436956] Multiple images copy paste issues
https://bugs.kde.org/show_bug.cgi?id=436956 Jan-Marek Glogowski changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #15 from Jan-Marek Glogowski --- I might be hijacking this report and it might be a different problem, but it looks the same. I just analyzed a LibreOffice image pasting bug on Wayland in https://bugs.documentfoundation.org/show_bug.cgi?id=142889 Repo: 1. spectacle -> copy to clipboard 2. "wl-paste -l" lists "image/png" 3. "wl-paste -t image/png >/tmp/unknown.data" 4. "hexdump -C /tmp/unknown.data | head -n 1" 42 4d 36 ec 5e 00 00 00 00 00 36 00 00 00 28 00 |BM6.^.6...(.| So instead of ~375k PNG, which I get from spectacle on save, I got a 6.2m BMP from the clipboard, which LO's PNG reader doesn't like :-( That's for my freshly updated Debian Bullseye, which has some KDE 5.20.5 variant. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436391] New: Printing only pages with annotations
https://bugs.kde.org/show_bug.cgi?id=436391 Bug ID: 436391 Summary: Printing only pages with annotations Product: okular Version: 21.04.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: phil...@marek.priv.at Target Milestone: --- When annotating PDFs, simply saving the PDF and passing it on doesn't always work - some people are stuck with software that doesn't display annotations. A workaround is to print the document to a new PDF - then the annotations are included as normal elements and can be seen in any PDF viewer. It would be great if okular had another page selector for "annotated pages only", so that a long PDF could be restricted to the necessary pages - associating with the original can typically be done easily via the page numbers in the footer anyway. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436214] New: Measure distances (and areas?)
https://bugs.kde.org/show_bug.cgi?id=436214 Bug ID: 436214 Summary: Measure distances (and areas?) Product: okular Version: 21.04.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: phil...@marek.priv.at Target Milestone: --- It would be great if there was some tool to measure distances (in points, mm, cm, dpi) and perhaps areas in an PDF. I'd imagine zooming in as much as necessary, then choosing the measurement tool, and dragging a line (resp. a rectangle) on the screen; either the status bar or a hovering popup could show the distance in some choosable units (one or multiple). Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433247] Folder expanded incorrectly when sorted by ascending size
https://bugs.kde.org/show_bug.cgi?id=433247 marek changed: What|Removed |Added CC||kordikma...@gmail.com --- Comment #1 from marek --- I can also reproduce it but I can reproduce the same behaviour both for ascending and descending ordering according to size. The number of folders/files does not need to be high. It can be reproduced with three folders with three files in each. Furthermore sometimes (when are folders ordered by size) it happens that seemingly random folders swap their places - for example: . ├── a ├── b ├── c ├── d └── e after expanding of "c": . ├── b ├── a ├── c │ ├── c1 │ ├── c2 │ ├── c3 │ └── c4 ├── d └── e System info: Operating System: Manjaro Linux KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.18-1-MANJARO OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #16 from Marek Paśnikowski --- Thank you. I will put it on a back burner for a while. There are other things that I need to get done. Maybe someone else will be able to provide better insight in the meantime. All I could do is some blind package installations in hopes of finding a missing link. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #14 from Marek Paśnikowski --- Created attachment 135428 --> https://bugs.kde.org/attachment.cgi?id=135428=edit Terminal Output of QML apps Here is the terminal output of the Settings app and the Elisa app. There are some warnings which may or may not be relevant. With regards to the theming, I have no clue what to do. Am I supposed to find a system package with the correct theme or something? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #12 from Marek Paśnikowski --- I have confirmed now, that there are actually two bugs related to Fontconfig. I used to have the following option be unset - meaning it was in the default state, "radeon". https://search.nixos.org/options?channel=20.09=services.xserver.videoDrivers=0=50=relevance=videoDrivers I had tried "modesetting" first, it resulted in no change. But when I set it to "amdgpu", only the Settings application is broken. All the other applications like Konsole or Kmail render fonts correctly. When you were writing about the theming, did you have the Settings application specifically in mind? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #10 from Marek Paśnikowski --- Declaration of kdeFrameworks.qqc2-desktop-style did not change anything, it seems it is already part of the dependency chain for KDE. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #8 from Marek Paśnikowski --- I am "dumb" user of NixOS. I had installed the KDE "service" which pulled in the Plasma Desktop. QT5CT was not installed. When running the program, it warns about QT_QPA_PLATFORMTHEME being not set. The installation of this program did not change font rendering even after a reboot. I am not touching any of the settings in qt5ct because I do not know what I am doing with those changes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #6 from Marek Paśnikowski --- Created attachment 135425 --> https://bugs.kde.org/attachment.cgi?id=135425=edit fc-match output -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432431] New: File -> Open: wrong file type as default ("XPS" instead of "*" or "PDF")
https://bugs.kde.org/show_bug.cgi?id=432431
Bug ID: 432431
Summary: File -> Open: wrong file type as default ("XPS"
instead of "*" or "PDF")
Product: okular
Version: 20.12.1
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: phil...@marek.priv.at
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. start okular
2. Use File => Open menu
OBSERVED RESULT
3. you can't see any PDFs unless you change the file type selector
EXPECTED RESULT
3. either all supported files are listed or at least a more common file format
is used as default
Thanks a lot!
--
You are receiving this mail because:
You are watching all bug changes.
[qca] [Bug 432142] Can't run OpenPGP on Android
https://bugs.kde.org/show_bug.cgi?id=432142
--- Comment #1 from Marek ---
Looking at another project I have renamed libqca-gnupg.so into:
file lib/armeabi-v7a/libplugins_crypto_libqca-gnupg.so
lib/armeabi-v7a/libplugins_crypto_libqca-gnupg.so: ELF 32-bit LSB shared
object, ARM, EABI5 version 1 (SYSV), dynamically linked,
BuildID[sha1]=140485303f05c8975f71f17a186f1265341a7b73, stripped
And it is included in APK now, but still
QCA::isSupported("openpgp") = false
Is this because gnuPG is not available on Android ?
Best Regards
Marek
--
You are receiving this mail because:
You are watching all bug changes.
[qca] [Bug 432142] New: Can't run OpenPGP on Android
https://bugs.kde.org/show_bug.cgi?id=432142
Bug ID: 432142
Summary: Can't run OpenPGP on Android
Product: qca
Version: 2.3.1
Platform: Android
OS: Android 9.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dr...@land.ru
Reporter: marek.florianc...@gmail.com
CC: aa...@kde.org, br...@frogmouth.net,
jus...@karneges.com
Target Milestone: ---
SUMMARY
Can't run OpenPGP on Android. QCA lib is searching for a plugin libqca-gnupg.so
in crypto directory but Android does not copy subfolders from armeabi-v7a
directory. Here is some issue discussed
https://github.com/gradle/gradle/issues/2394
Can there be some settings that will tell library to look for a plugin in the
directory where libqca-qt5 is located?
And also main question is: Can OpenPGP work at all on Android, maybe it relies
on some OS specific commands like gpg gpg2 and packages gnupg and no matter
what it will not work on Android ?
STEPS TO REPRODUCE
1. Cross compile QCA with command:
cmake . -DCMAKE_SYSTEM_NAME=Android
-DCMAKE_TOOLCHAIN_FILE=/opt/Android/Ndk/android-ndk-r20/build/cmake/android.toolchain.cmake
-DQt5_DIR=/opt/Felgo/Felgo/android_armv7/lib/cmake/Qt5/
-DQt5Core_DIR=/opt/Felgo/Felgo/android_armv7/lib/cmake/Qt5Core/
-DQt5Test_DIR=/opt/Felgo/Felgo/android_armv7/lib/cmake/Qt5Test/
-DQt5Network_DIR=/opt/Felgo/Felgo/android_armv7/lib/cmake/Qt5Network/
-DANDROID_PLATFORM=android-29 -DCMAKE_INSTALL_PREFIX=/usr/local/android
-DUSE_RELATIVE_PATHS=ON
I'm using Felgo, but pure Qt should have the same result
2. Copy libraries into android/libs/armeabi-v7a within Qt project
ls -la armeabi-v7a/
drwxr-xr-x 2 franki franki 4096 sty 25 18:18 crypto
-rw-r--r-- 1 franki franki 3812452 sty 25 19:01 libqca-gnupg.so
-rw-r--r-- 1 franki franki 674004 sty 25 19:01 libqca-logger.so
-rw-r--r-- 1 franki franki 12997264 sty 25 18:18 libqca-qt5.so
-rw-r--r-- 1 franki franki 1025504 sty 25 19:01 libqca-softstore.so
drwxr-xr-x 3 franki franki 4096 sty 25 18:55 plugins
drwxr-xr-x 3 franki franki 4096 sty 25 18:18 qca-qt5
3. Build Android APK, only files from armeabi-v7a will be included in package,
no subdirectories
OBSERVED RESULT
QCA::isSupported("openpgp") = false
EXPECTED RESULT
QCA::isSupported("openpgp") = true
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Debian Buster, KDE 5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.13.2
ADDITIONAL INFORMATION
Please Help ;)
Best Regards
Marek
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #4 from Marek Paśnikowski --- Created attachment 135159 --> https://bugs.kde.org/attachment.cgi?id=135159=edit There is a difference on an Intel GPU. When I deployed a new system to an old laptop, with Intel hardware platform, I discovered the bug is not as severe on that hardware. So far, it appears only in the Settings applications. The rest of the few applications that are installed there are properly rendering the text. It is a production computer, so I did not have a chance to test it yet. What tests could I do anyway? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #3 from Paśnikowski Marek --- (In reply to Nate Graham from comment #2) > I doubt this is related to Kirigami. It's more likely to be an issue with > the way the distro's fontconfig interacts with the settings in the Fonts > KCM. Moving there. To test the interaction, I suggest to implement an option which clears the current KCM font configuration and keeps the options undeclared, which would let the inherited system configuration do its job. This would show in which direction the bug is hidden. If the issue persists, it would indicate a problem with Fontconfig parsing or rendering by a library or a framework. If the issue disappears, it would indicate an actual KCM interaction problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #1 from Paśnikowski Marek --- I started to doubt if this bug is actually in Kirigami. Today I installed Libreoffice-QT and it also has this problem, but only in the menus and tooltips. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 431649] New: Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 Bug ID: 431649 Summary: Most KDE Applications Do Not Respect Fontconfig Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: m...@marekpasnikowski.name Target Milestone: Not decided Created attachment 134907 --> https://bugs.kde.org/attachment.cgi?id=134907=edit Presentation of Fontconfig Resistance I have seen this problem for a couple of version now. Regardless of distribution or configuration, many of the KDE applications enforce their own fontconfig. In my previous, already discarded installation, even the system wide Fontconfig was ignored. The attached screenshot shows it all. The AA is in the disabled position, my GTK based browser, KWin and the Plasma Shell are properly aliased, but the Settings Manager is still smoothed. My desire is to have no font antialiasing, because my eyes can't focus properly on the blurry curves. The reproduction is as easy as unchecking the antialiasing button and applying the change. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 268341] Complete Konqueror crash on phoronix.com
https://bugs.kde.org/show_bug.cgi?id=268341 --- Comment #29 from Paśnikowski Marek --- It's been months since I last used KDE and even longer since I last used konqueror. I am not able to test. > 14 grudnia 2020 02:38 Justin Zobel napisał(a): > > > https://bugs.kde.org/show_bug.cgi?id=268341 > > Justin Zobel changed: > >What|Removed |Added > > CC||justin.zo...@gmail.com > Resolution|--- |WAITINGFORINFO > Status|CONFIRMED |NEEDSINFO > > --- Comment #28 from Justin Zobel --- > Thank you for the crash reports. > > As it has been a while since this was reported, can you please test and > confirm > if this issue is still occurring or if this bug report can be marked as > resolved. > > I have set the bug status to "needsinfo" pending your response, please change > back to "reported" or "resolved/worksforme" when you respond, thank you. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 --- Comment #8 from Paśnikowski Marek --- Yes. I forgot I had an OwnCloud server. This says something. Email z Środa, 29 stycznia 2020 od bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=330472 > > --- Comment #7 from y...@jacky.wtf --- > On Wednesday, January 29, 2020 7:43:17 AM PST bugzilla_nore...@kde.org wrote: > > https://bugs.kde.org/show_bug.cgi?id=330472 > > > > kde.sebac...@simplelogin.co changed: > > > >What|Removed |Added > > > > CC||kde.sebac...@simplelogin.co > > > > --- Comment #6 from kde.sebac...@simplelogin.co --- > > any news about this? > > I think it's dead, tbh. The project and this ticket. > > > Bet, > *Jacky Alcine* > > -- > You are receiving this mail because: > You are on the CC list for the bug -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409646] No case for 1Uto32 - arm64
https://bugs.kde.org/show_bug.cgi?id=409646
--- Comment #3 from Marek Zmysłowski ---
So I created following fix:
---
diff --git a/VEX/priv/host_arm64_isel.c b/VEX/priv/host_arm64_isel.c
index b2ab7422b..724633737 100644
--- a/VEX/priv/host_arm64_isel.c
+++ b/VEX/priv/host_arm64_isel.c
@@ -1946,7 +1946,9 @@ static HReg iselIntExpr_R_wrk ( ISelEnv* env, IRExpr* e )
addInstr(env, ARM64Instr_VXfromQ(dst, tmp, 0/*laneNo*/));
return dst;
}
- case Iop_1Uto64: {
+ case Iop_1Uto64:
+ case Iop_1Uto32:
+ {
/* 1Uto64(tmp). */
HReg dst = newVRegI(env);
if (e->Iex.Unop.arg->tag == Iex_RdTmp) {
---
Currently I have a following issue:
==2953== Taintgrind, the taint analysis tool
==2953== Copyright (C) 2010-2018, and GNU GPL'd, by Wei Ming Khoo.
==2953== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==2953== Command: /bin/ls
==2953==
t111 = 64HLto128(CmpwNEZ64(t109),t109)
vex: the `impossible' happened:
iselStmt
vex storage: T total 32492776 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==2953==at 0x5802E0DC: show_sched_status_wrk (m_libcassert.c:388)
==2953==by 0x5802E20B: report_and_quit (m_libcassert.c:459)
==2953==by 0x5802E443: vgPlain_core_panic_at (m_libcassert.c:535)
==2953==by 0x5802E467: vgPlain_core_panic (m_libcassert.c:545)
==2953==by 0x580B415F: failure_exit (m_translate.c:751)
==2953==by 0x58130E8F: vpanic (main_util.c:255)
==2953==by 0x5819A263: iselSB_ARM64 (host_arm64_isel.c:4015)
==2953==by 0x5812D75F: LibVEX_Translate (main_main.c:1049)
==2953==by 0x580B6D77: vgPlain_translate (m_translate.c:1813)
==2953==by 0x58084EE7: handle_chain_me (scheduler.c:1167)
==2953==by 0x58087FDB: vgPlain_scheduler (scheduler.c:1516)
==2953==by 0x580E8937: run_a_thread_NORETURN (syswrap-linux.c:103)
==2953==by 0x: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2953)
==2953==at 0x4007764: ??? (in /lib/aarch64-linux-gnu/ld-2.27.so)
client stack range: [0x1FFEFFF000 0x1FFF000FFF] client SP: 0x1FFEFFFBA0
valgrind stack range: [0x100486E000 0x100496DFFF] top usage: 6400 of 1048576
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 413708] New: Akonadi Crash During Deduplication
https://bugs.kde.org/show_bug.cgi?id=413708 Bug ID: 413708 Summary: Akonadi Crash During Deduplication Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I am removing duplicates in my e-mail archives and this particular folder (one of the big ones) causes Akonadi to crash every time. It seems to do so on the "deleting" phase, according to the status bar. The crash can be reproduced every time. -- Backtrace (Reduced): #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #8 0x7f427255655d in __GI_abort () at abort.c:79 [...] #10 0x7f42725b78fc in malloc_printerr (str=str@entry=0x7f42726bd0f1 "free(): invalid pointer") at malloc.c:5332 #11 0x7f42725b92dc in _int_free (av=, p=, have_lock=0) at malloc.c:4173 #12 0x7f4272a4cafb in QTypedArrayData::deallocate (data=) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:236 Possible duplicates by query: bug 412300, bug 412218, bug 411993, bug 411687, bug 411347. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413706] Akonadi Crash During Removal of Duplicates in a Folder
https://bugs.kde.org/show_bug.cgi?id=413706 Paśnikowski Marek changed: What|Removed |Added CC||m...@marekpasnikowski.name -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413706] New: Akonadi Crash During Removal of Duplicates in a Folder
https://bugs.kde.org/show_bug.cgi?id=413706 Bug ID: 413706 Summary: Akonadi Crash During Removal of Duplicates in a Folder Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I am removing duplicates in my e-mail archives and this particular folder (one of the big ones) causes Akonadi to crash every time. It seems to do so on the "deleting" phase, according to the status bar. The crash can be reproduced every time. -- Backtrace (Reduced): #7 0x7fcab32ccabe in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x6e0061006a0024) at /usr/include/c++/9/bits/atomic_base.h:413 #8 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #9 QBasicAtomicInteger::load (this=0x6e0061006a0024) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #11 QString::operator= (this=this@entry=0x7fca4406d828, other=...) at tools/qstring.cpp:2434 #12 0x558bfe64af01 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x558bfee3a6c0, request=0x7fca4406d810, errorMsg=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:224 Possible duplicates by query: bug 413301, bug 411886, bug 410782, bug 410345, bug 410267. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 413355] New: Random Crash of Kontact
https://bugs.kde.org/show_bug.cgi?id=413355 Bug ID: 413355 Summary: Random Crash of Kontact Product: kontact Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: kontact (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I pressed the button to delete a journal entry. After restarting Kontact the same action resulted in no crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fa47cf5af80 (LWP 3162))] Thread 30 (Thread 0x7fa3e7853700 (LWP 7048)): #0 __GI___libc_read (nbytes=10, buf=0x7fa3e785295e, fd=112) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=fd@entry=112, buf=buf@entry=0x7fa3e785295e, nbytes=nbytes@entry=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fa4700f60f1 in read (__nbytes=10, __buf=0x7fa3e785295e, __fd=112) at /usr/include/bits/unistd.h:44 #3 pa_read (fd=112, buf=buf@entry=0x7fa3e785295e, count=count@entry=10, type=type@entry=0x55d721acc458) at pulsecore/core-util.c:422 #4 0x7fa471c4aa0e in clear_wakeup (m=) at pulse/mainloop.c:782 #5 pa_mainloop_prepare (m=m@entry=0x55d721acc380, timeout=-1) at pulse/mainloop.c:789 #6 0x7fa471c4b4b0 in pa_mainloop_iterate (m=0x55d721acc380, block=, retval=0x0) at pulse/mainloop.c:923 #7 0x7fa471c4b570 in pa_mainloop_run (m=0x55d721acc380, retval=retval@entry=0x0) at pulse/mainloop.c:945 #8 0x7fa471c59439 in thread (userdata=0x55d721a1f6f0) at pulse/thread-mainloop.c:101 #9 0x7fa470123c78 in internal_thread_func (userdata=0x55d720c38860) at pulsecore/thread-posix.c:81 #10 0x7fa47c79cf2a in start_thread (arg=) at pthread_create.c:479 #11 0x7fa47d8034af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fa3454d2700 (LWP 7047)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fa3454d18e0, clockid=, expected=0, futex_word=0x7fa3454d1a08) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fa3454d18e0, clockid=, mutex=0x7fa3454d19b8, cond=0x7fa3454d19e0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fa3454d19e0, mutex=0x7fa3454d19b8, abstime=0x7fa3454d18e0) at pthread_cond_wait.c:656 #3 0x7fa475c4c486 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7fa475c4ce53 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230 #5 0x7fa475c4cfd1 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162 #6 0x7fa475c05141 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37 #7 0x7fa475c07fdd in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303 #8 0x7fa475c086d4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229 #9 0x7fa475c4f2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fa47c79cf2a in start_thread (arg=) at pthread_create.c:479 #11 0x7fa47d8034af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fa344cd1700 (LWP 6715)): #0 0x7fa47d7f8bdf in __GI___poll (fds=0x7fa3f8002fe0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa47bd3e2ae in g_main_context_poll (priority=, n_fds=1, fds=0x7fa3f8002fe0, timeout=, context=0x7fa3f8000bf0) at ../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7fa3f8000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:3912 #3 0x7fa47bd3e3cf in g_main_context_iteration (context=0x7fa3f8000bf0, may_block=may_block@entry=1) at ../glib/gmain.c:3978 #4 0x7fa47ddbf99b in QEventDispatcherGlib::processEvents (this=0x7fa3f8002000, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fa47dd680db in QEventLoop::exec (this=this@entry=0x7fa344cd0b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fa47dba0021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fa47dba11a2 in
[k3b] [Bug 404787] In K3b - The ISRC Field in the Audio Track Properties Dialog Box only allows for 2 Characters - ISRC's are 12 Characters Long eg: "CAS9S1900101" so this field need to be increased
https://bugs.kde.org/show_bug.cgi?id=404787 Marek Klein changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Marek Klein --- Sorry - it is indeed possible to enter the ISRC codes with letters too - but capital letters must be used. For example - US-HM9-19-85865 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 404787] In K3b - The ISRC Field in the Audio Track Properties Dialog Box only allows for 2 Characters - ISRC's are 12 Characters Long eg: "CAS9S1900101" so this field need to be increased
https://bugs.kde.org/show_bug.cgi?id=404787 Marek Klein changed: What|Removed |Added Status|RESOLVED|REOPENED CC||ma...@gregoriana.sk Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #3 from Marek Klein --- Hello, my ISRC codes do not have dashes and contain letters too - it is simply 12 character string - for example ushm91985865. The original poster example was CAS9S1900101 - how would you put it in the field using dashes? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412591] New unwanted window opens with map tab
https://bugs.kde.org/show_bug.cgi?id=412591 --- Comment #5 from Marek Potocki --- Thanks :) Marble as application works fine. There is no problem with map in DigiKam. I can move, scale and change map. Only this mysterious window opens… -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412591] New unwanted window opens with map tab
https://bugs.kde.org/show_bug.cgi?id=412591 --- Comment #2 from Marek Potocki --- Well… I open DK 6.3.0 from AppImage, and there isn't problem. With delivered with manjaro version, window opens. There is any content. I can move and resize this window, but i can't close it. Window closes with main program. PS. I found one method to close this window without closing DK – open "Edit geolocation", and close it. "Geolocation edition" opens new instance of this window. When I close this tool, and I change tab from map to other, both inactive windows (from map tab, and geolocation edition) are closed. In map tab still active, only one window is closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412591] New: New unwanted window opens with map tab
https://bugs.kde.org/show_bug.cgi?id=412591 Bug ID: 412591 Summary: New unwanted window opens with map tab Product: digikam Version: 6.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: qrczak...@gmail.com Target Milestone: --- Created attachment 123006 --> https://bugs.kde.org/attachment.cgi?id=123006=edit New unwanted window SUMMARY When I open map tab in album, opens new not responsible Digikam window STEPS TO REPRODUCE 1. Open Album 2. Switch to Map tab OBSERVED RESULT New little window opens. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro XFCE (available in About System) KDE Plasma Version: Framework 5.61 with other comonents 5.16 KDE Frameworks Version: Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412590] New: New files are not showing in album
https://bugs.kde.org/show_bug.cgi?id=412590 Bug ID: 412590 Summary: New files are not showing in album Product: digikam Version: 6.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: qrczak...@gmail.com Target Milestone: --- SUMMARY In case of add new files to with external application, album file list not refreshing. STEPS TO REPRODUCE 1. Open Digikam and any album 2. Add new image to this album (like export from RAW) OBSERVED RESULT No changes. To show new file required full album refresh (F5). EXPECTED RESULT New file added to album without refresh. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro with XFCE (available in About System) KDE Plasma Version: Framework 5.61, and another components: 5.16 Qt Version: 5.13 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 412439] New: Kontact Crash When Moving Moving Email Folders
https://bugs.kde.org/show_bug.cgi?id=412439 Bug ID: 412439 Summary: Kontact Crash When Moving Moving Email Folders Product: kontact Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: kontact (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.2.14-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Moving folders in my email structure. Kontact has a tendency to crash after some move operations. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fe486fd0a80 (LWP 2818))] Thread 32 (Thread 0x7fe41a7fc700 (LWP 3479)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fe41a7fb840, expected=0, futex_word=0x7fe41a7fba08) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fe41a7fb8e0, mutex=0x7fe41a7fb9b8, cond=0x7fe41a7fb9e0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fe41a7fb9e0, mutex=0x7fe41a7fb9b8, abstime=0x7fe41a7fb8e0) at pthread_cond_wait.c:667 #3 0x7fe48002b486 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7fe48002be53 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230 #5 0x7fe48002bfd1 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162 #6 0x7fe47ffe4141 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37 #7 0x7fe47ffe732b in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331 #8 0x7fe47ffe76d4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229 #9 0x7fe48002e2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fe486a43faa in start_thread (arg=) at pthread_create.c:486 #11 0x7fe48903873f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fe34fd9a700 (LWP 3361)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fe34fd99a18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fe34fd999c8, cond=0x7fe34fd999f0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fe34fd999f0, mutex=0x7fe34fd999c8) at pthread_cond_wait.c:655 #3 0x7fe48002b38c in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #4 0x7fe48002be60 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232 #5 0x7fe48002bf8f in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #6 0x7fe47ffe4116 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35 #7 0x7fe47ffe6fdd in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303 #8 0x7fe47ffe7714 in base::internal::SchedulerWorker::RunSharedWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:241 #9 0x7fe48002e2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fe486a43faa in start_thread (arg=) at pthread_create.c:486 #11 0x7fe48903873f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fe350921700 (LWP 3144)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56457878c2c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56457878c278, cond=0x56457878c2a0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56457878c2a0, mutex=0x56457878c278) at pthread_cond_wait.c:655 #3 0x7fe46f36bb8b in cnd_wait (mtx=0x56457878c278, cond=0x56457878c2a0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=) at ../src/util/u_queue.c:272 #5 0x7fe46f36ba37 in impl_thrd_routine.lto_priv.4.lto_priv () at ../src/util/u_cpu_detect.c:508 #6 0x7fe486a43faa in start_thread (arg=) at
[valgrind] [Bug 409646] No case for 1Uto32 - arm64
https://bugs.kde.org/show_bug.cgi?id=409646 Marek Zmysłowski changed: What|Removed |Added Summary|1Uto32 can be identified|No case for 1Uto32 - arm64 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409646] New: 1Uto32 can be identified
https://bugs.kde.org/show_bug.cgi?id=409646 Bug ID: 409646 Summary: 1Uto32 can be identified Product: valgrind Version: 3.15 SVN Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: marekzmyslow...@poczta.onet.pl Target Milestone: --- SUMMARY While running the taintgrind plugin, the following error occurs: 1Uto32(t60) vex: the `impossible' happened: iselIntExpr_R: cannot reduce tree This happens becuse the 1Uto32 case is not found inside host_arm64_isel.c (missing the case for Iop_1Uto32) STEPS TO REPRODUCE 1. Install taintgrind according to the instruction https://github.com/wmkhoo/taintgrind/ 2. Run the simple command 3. /work/temp/valgrind/build/bin/valgrind --tool=taintgrind --file-filter=/work --taint-start=0 --taint-len=1 ls OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS ARMBIAN 5.83 stable Ubuntu 18.04.2 LTS 4.19.38-sunxi64 Linux pine64so 4.19.38-sunxi64 #5.83 SMP Fri May 3 21:02:31 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux ADDITIONAL INFORMATION /work/temp/valgrind/build/bin/valgrind --tool=taintgrind --file-filter=/work --taint-start=0 --taint-len=1 ls ==18427== Taintgrind, the taint analysis tool ==18427== Copyright (C) 2010-2018, and GNU GPL'd, by Wei Ming Khoo. ==18427== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright info ==18427== Command: ls ==18427== 1Uto32(t60) vex: the `impossible' happened: iselIntExpr_R: cannot reduce tree vex storage: T total 12936 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==18427==at 0x5802CE1C: show_sched_status_wrk (m_libcassert.c:386) ==18427==by 0x5802CF4B: report_and_quit (m_libcassert.c:457) ==18427==by 0x5802D183: vgPlain_core_panic_at (m_libcassert.c:533) ==18427==by 0x5802D1A7: vgPlain_core_panic (m_libcassert.c:543) ==18427==by 0x580B30D7: failure_exit (m_translate.c:749) ==18427==by 0x5813025F: vpanic (main_util.c:253) ==18427==by 0x58191F4F: iselIntExpr_R_wrk (host_arm64_isel.c:2082) ==18427==by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458) ==18427==by 0x58192C4B: iselIntExpr_R_wrk (host_arm64_isel.c:1766) ==18427==by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458) ==18427==by 0x58198D53: doHelperCall.isra.28.constprop.29 (host_arm64_isel.c:685) ==18427==by 0x58199FFB: iselSB_ARM64 (host_arm64_isel.c:3761) ==18427==by 0x5812CB2F: LibVEX_Translate (main_main.c:1047) ==18427==by 0x580B5CEF: vgPlain_translate (m_translate.c:1811) ==18427==by 0x58083CBF: handle_chain_me (scheduler.c:1165) ==18427==by 0x58086DB3: vgPlain_scheduler (scheduler.c:1514) ==18427==by 0x580E68AF: run_a_thread_NORETURN (syswrap-linux.c:101) ==18427==by 0x: ??? sched status: running_tid=1 --18427-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --18427-- si_code=1; Faulting address: 0x140; sp: 0x1004b6d300 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==18427==at 0x580880D8: vgPlain_is_in_syscall (syswrap-main.c:1640) ==18427==by 0x5802C9CF: print_thread_state (m_libcassert.c:324) ==18427==by 0x5802CC0F: show_sched_status_wrk (m_libcassert.c:420) ==18427==by 0x5802CF4B: report_and_quit (m_libcassert.c:457) ==18427==by 0x5802D183: vgPlain_core_panic_at (m_libcassert.c:533) ==18427==by 0x5802D1A7: vgPlain_core_panic (m_libcassert.c:543) ==18427==by 0x580B30D7: failure_exit (m_translate.c:749) ==18427==by 0x5813025F: vpanic (main_util.c:253) ==18427==by 0x58191F4F: iselIntExpr_R_wrk (host_arm64_isel.c:2082) ==18427==by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458) ==18427==by 0x58192C4B: iselIntExpr_R_wrk (host_arm64_isel.c:1766) ==18427==by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458) ==18427==by 0x58198D53: doHelperCall.isra.28.constprop.29 (host_arm64_isel.c:685) ==18427==by 0x58199FFB: iselSB_ARM64 (host_arm64_isel.c:3761) ==18427==by 0x5812CB2F: LibVEX_Translate (main_main.c:1047) ==18427==by 0x580B5CEF: vgPlain_translate (m_translate.c:1811) ==18427==by 0x58083CBF: handle_chain_me (scheduler.c:1165) ==18427==by 0x58086DB3: vgPlain_scheduler (scheduler.c:1514) ==18427==by 0x580E68AF: run_a_thread_NORETURN (syswrap-linux.c:101) ==18427==by 0x: ??? sched status: running_tid=1 Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 --- Comment #2 from Jan-Marek Glogowski --- Patch: https://phabricator.kde.org/D21249 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 --- Comment #1 from Jan-Marek Glogowski --- Created attachment 120136 --> https://bugs.kde.org/attachment.cgi?id=120136=edit qmake file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] New: KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 Bug ID: 407642 Summary: KFileWidget selects the the wrong filter on filter change with enabled automatic extensions Product: frameworks-kio Version: 5.54.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: glo...@fbihome.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 120135 --> https://bugs.kde.org/attachment.cgi?id=120135=edit Simple test file picker program If your filter list has two matching filters for an extension, KFileWidget will always select the first filter, even if the current filter already matches the file name. The result is that a user selects a filter and it's not honored by the UI. This resulted in two bugs in LibreOffice with the KDE backend: * https://bugs.documentfoundation.org/show_bug.cgi?id=125267 * https://bugs.documentfoundation.org/show_bug.cgi?id=120950 Our workaround is now to ignore the returned filter string. This bug doesn't happen with the non-native QFileDialog. STEPS TO REPRODUCE 1. Compile and run the attached program 2. Make sure that "auto extension" checkbox is enable 2. Select the last file filter (DocBook (.xml)) via dropdown list OBSERVED RESULT Filter is "Word 2003 XML (.xml)" EXPECTED RESULT Filter is "DocBook (.xml)" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Buster with KIO 5.54 I already have a patch for this. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 406876] Allow to keep "black on white forced" enabled for all messages
https://bugs.kde.org/show_bug.cgi?id=406876 --- Comment #2 from Marek Malevič --- For review https://gerrit.vesnicky.cesnet.cz/r/#/c/1025/ -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358680] sort order not saved when not threaded
https://bugs.kde.org/show_bug.cgi?id=358680 --- Comment #8 from Marek Malevič --- Hi Jan, learning Gerrit I created https://gerrit.vesnicky.cesnet.cz/r/#/c/1024/ . Hopefully it is as it should... -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 406876] Allow to keep "black on white forced" enabled for all messages
https://bugs.kde.org/show_bug.cgi?id=406876 --- Comment #1 from Marek Malevič --- Created attachment 119814 --> https://bugs.kde.org/attachment.cgi?id=119814=edit Patch for fixing bug 406876 Configuration of default color schema in settings dialog -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358680] sort order not saved when not threaded
https://bugs.kde.org/show_bug.cgi?id=358680 Marek Malevic changed: What|Removed |Added CC||ma...@malevicovi.net --- Comment #6 from Marek Malevic --- Created attachment 119802 --> https://bugs.kde.org/attachment.cgi?id=119802=edit Patch for fixing bug 358680 I have created a patch that stores selected sorting order in profile config and uses it when messages are updated. This solves sorting issues (at least in my case). The patch may not be perfect, I am not a C++ guy. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 406876] New: Allow to keep "black on white forced" enabled for all messages
https://bugs.kde.org/show_bug.cgi?id=406876 Bug ID: 406876 Summary: Allow to keep "black on white forced" enabled for all messages Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: ma...@malevicovi.net Target Milestone: --- SUMMARY Very bad readability of some messages when breeze-dark used, because many sending apps expect the readers to have white background and black text. "Black on white forced" is not remembered which significantly complicates usability. STEPS TO REPRODUCE 1. Set dark theme 2. Open various types of HTML/plaintext messages 3. Some of the texts are very hard to read. Use "black on white forced" to make them readable. 4. Click on another message, again hardly readable. OBSERVED RESULT Color scheme must be changed for every message. EXPECTED RESULT Color scheme should be configurable for the whole Trojita profile. SOFTWARE/OS VERSIONS Operating System: Devuan GNU/Linux KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 4.19.0-4-amd64 OS Type: 64-bit Processors: 4 × AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G Memory: 14.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404638] Add VG_(replaceIndexXA)
https://bugs.kde.org/show_bug.cgi?id=404638 --- Comment #4 from Łukasz Marek --- Just one remark. Your method doesn't mark array sorted=false. I can live with that anyway. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404638] Add VG_(replaceIndexXA)
https://bugs.kde.org/show_bug.cgi?id=404638 --- Comment #3 from Łukasz Marek --- (In reply to Julian Seward from comment #1) > Is this actually necessary? I've always done this: > > T* p = (T*)VG_(indexXA)(arr, index); > *p = new_value; You are right, this new function is not necessary. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404638] New: Add VG_(replaceIndexXA)
https://bugs.kde.org/show_bug.cgi?id=404638 Bug ID: 404638 Summary: Add VG_(replaceIndexXA) Product: valgrind Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: lukasz.m.lu...@gmail.com Target Milestone: --- Created attachment 118247 --> https://bugs.kde.org/attachment.cgi?id=118247=edit patch VG_(replaceIndexXA) I found useful for myself manipulating huge array that has around 100k elements and I have to replace some part of them periodically. This allows avoiding elements shifting each time old element is removed when there is a possibility to just replace it with a new one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366471] Plasma desktop becomes unresponsive with a .desktop file using a .svgz icon
https://bugs.kde.org/show_bug.cgi?id=366471 Marek changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #7 from Marek --- I provided the information two years ago. -- You are receiving this mail because: You are watching all bug changes.
