[plasma-browser-integration] [Bug 397138] Reading manifest: Error processing background.persistent: Event pages
https://bugs.kde.org/show_bug.cgi?id=397138 --- Comment #1 from Kai Uwe Broulik --- Cannot reproduce the breakage. The key is documented as "should be set to false" explicitly. The extension does work in Firefox and Chrome here, despite the aforementioned warnings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397203] New: Gradients don't save or update
https://bugs.kde.org/show_bug.cgi?id=397203 Bug ID: 397203 Summary: Gradients don't save or update Product: krita Version: 4.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: chris.we...@googlemail.com Target Milestone: --- Any changes made to a gradient aren't saved. To reproduce: Create a new gradient - this will automatically save in the gradients folder Make any change to that gradient Check the gradient file - it will remain unchanged Saving the current document or closing Krita makes no difference. When you re-open Krita the gradient will have reverted to the default yellow-red. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397203] Gradients don't save or update
https://bugs.kde.org/show_bug.cgi?id=397203 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #31 from Julian Seward --- (In reply to Florian Weimer from comment #29) > Created attachment 114302 [details] > Use guarded loads in the guest > > This patch changes the guest code to use guarded loads. > > However, this insufficient because the isel implementation does not handle > Ist_LoadG. I don't know how to fix this. Look at how the amd64 back end does it. It basically is going to be a completely normal unconditional load that has a conditional branch in front of it. > s390_insn_cond_move does not perform the U8 → U32 zero extension, so it is > not a good fit here (and even Ist_LoadG with ILGop_8Uto32 is a bit off in > this context, we would need ILGop_Ident8). This doesn't matter very much. Presumably s390 has an instruction that loads 8 bits from memory and zero extends the loaded value out to 64 bits. Then you can use the ILGop_8Uto64 descriptor in your conditional load. The narrowing operations that you will have to use afterwards (64to8, or 32to8) become no-ops in the generated code, so there's no performance disadvantage to using an 8bits-to-64bits-and-back-to-8bits scheme. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #32 from Julian Seward --- (In reply to Florian Weimer from comment #30) > Created attachment 114305 [details] > Implement early exit in s390_vr_loadWithLength > > Updated patch. This seems to fix the VLL issue. Limited testing only. It would be better to implement guarded loads and use that scheme, so that we don't have to end the superblock every time we see VLL. > However, these VLL instructions are typically part of the GCC inline > expansion of strlen, and the result is used with VFENEZBS. Since VLL is > used to over-load bytes until the next boundary, the vector result is > partially undefined. VFENEZBS is implemented with a host assist only, > though, so we get tons of warnings from inline copies of strlen: What does VFENEZBS do? I imagine this will need to be fixed by making a translation of it that is more Memcheck-friendly, and/or adjusting Memcheck to deal with the underlying IROps better. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #33 from Julian Seward --- (In reply to Andreas Arnez from comment #23) > Julian, is this OK now? Considering comment 30, alas, no. Let's try and get the Memcheck problems with this fixed first. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388174] valgrind with Wine quits with "Assertion 'cfsi_fits' failed"
https://bugs.kde.org/show_bug.cgi?id=388174 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #3 from Julian Seward --- There have been a number of fixes to debuginfo reading in the git trunk version recently. Can you try again with that, and see if this still happens? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388706] warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0xf2 (DW_OP_GNU_implicit_pointer)
https://bugs.kde.org/show_bug.cgi?id=388706 --- Comment #2 from Julian Seward --- (In reply to Mark Wielaard from comment #1) > This is DW_OP_GNU_implicit_pointer. Mark, do we need to be concerned about this, still? I note it is reported against 3.11.0. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397202] Show more info about current update process in Discover Updater Tasks
https://bugs.kde.org/show_bug.cgi?id=397202 --- Comment #1 from Murz --- Now there are more than 1,5 hours gone, but update process still at 0%, and I even can't close the Discover window with error "Could not close the application, there are tasks that need to be done."! And there are no ways to review the source of current update process problem! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #3 from jeromec...@laposte.net --- Thanks! I will try to ask them. However, "incorrectly framed headers" in the bug case you linked makes me believe Amarok actually corrupts the headers of those ogg files after the first playback, doesn't it? This fix on GStreamer is aimed to play corrupted files… -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 388740] Ordering by timestamp instead of core number
https://bugs.kde.org/show_bug.cgi?id=388740
Julian Seward changed:
What|Removed |Added
CC||jsew...@acm.org
--- Comment #1 from Julian Seward ---
You can embed the contents of arbitrary environment variables in the filename
by putting "%q{VARNAME}" as part of the --callgrind-out-file= option. That
might be helpful.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 397105] "plasmawindowed org.kde.plasma.networkmanagement" can't be closed correctly
https://bugs.kde.org/show_bug.cgi?id=397105 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- Please attach backtrace from the crash and don't forget to install debug symbols for plasma-nm and networkmanager-qt. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397105] "plasmawindowed org.kde.plasma.networkmanagement" can't be closed correctly
https://bugs.kde.org/show_bug.cgi?id=397105 --- Comment #2 from Lucas Willems --- (In reply to Jan Grulich from comment #1) > Please attach backtrace from the crash and don't forget to install debug > symbols for plasma-nm and networkmanager-qt. How do I attach backtrace? What is it? And what is debug symbols for plasma-nm? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #34 from Vadim Barkov --- (In reply to Julian Seward from comment #32) > What does VFENEZBS do? VFENE V1, V2, V3 -- vector find element not equal It elementwise compares V2 and V3. If an unequal element is found, its index is stored in byte 7th (counting from 0th byte) of V1. If not, the value 16 is stored in 7th byte (counting from 0th byte) of V1. All other bytes of V1 are zeroed. VFENEZBS: B -- element size is 1 byte Z -- also compares elements of V2 with zero S -- set condition code with result of comparation So, "VFENEZBS %%v0, %%v0, %%v0" just searchs the first zero byte in %%v0, stores its index (or 16 if not found) and indicates if it was found in Conditional Code (CC). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388847] WARNING: unhandled arm64-linux syscall: 168 (getcpu)
https://bugs.kde.org/show_bug.cgi?id=388847 Julian Seward changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397105] "plasmawindowed org.kde.plasma.networkmanagement" can't be closed correctly
https://bugs.kde.org/show_bug.cgi?id=397105 --- Comment #3 from Jan Grulich --- Depends on your distribution, usually you can install them as package_name-debug or package_name-debuginfo or similarly, e.g. plasma-nm-debuginfo. You should get the backtrace from the "Developer information" tab in drkonqi, which is the dialog you get opened once this happens. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 397200] Crash when kstars window is not in front when starting
https://bugs.kde.org/show_bug.cgi?id=397200 Jasem Mutlaq changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Jasem Mutlaq --- I've seen this issue occasionally but I don't think it's related to alt-tabbing per se. We're using (or abusing) QtConcurrent in order to speed the start up time. Not sure if you recall earlier version of KStars where it would take anywhere from 10-15 seconds for startup. I think what's happening is that occasionally, some threads finish earlier and start looking for data that does not _yet_ exist. So better control of the concurrency is required at this stage. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388895] LibVEX_FrontEnd assertion failure: `0 == sizeof(VexGuestX86State) % LibVEX_GUEST_STATE_ALIGN'
https://bugs.kde.org/show_bug.cgi?id=388895 Julian Seward changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #5 from Julian Seward --- (In reply to bob from comment #0) > Upon calling LibVEX_FrontEnd (with the args configured for an AMD64 host and > an x86 guest), libvex bails out with the following message: We gave up on supporting cross-target Vex some years back, so I am not surprised this doesn't work. It seems unlikely to me that it'll get fixed any time soon. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397204] New: Latte-Dock does not always respect Opacity Settings
https://bugs.kde.org/show_bug.cgi?id=397204 Bug ID: 397204 Summary: Latte-Dock does not always respect Opacity Settings Product: latte-dock Version: 0.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: ch...@magentium.com Target Milestone: --- Latte-Dock does not always respect the Opacity Settings. At the moment I have Latte Dock as a "Dock" at the bottom of my screen, with Opacity set to 25%. Regardless of if Shadows are enabled or it is set to Solid. I'm unsure what information you require, so please let me know an I will attach it as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397204] Latte-Dock does not always respect Opacity Settings
https://bugs.kde.org/show_bug.cgi?id=397204 ch...@magentium.com changed: What|Removed |Added Platform|Other |Archlinux Packages CC||ch...@magentium.com --- Comment #1 from ch...@magentium.com --- After some additional testing, It seems that this only occurs if Latte-Dock is set to "Panel". Setting it to "Dock" allows transparency to work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 389412] Failed assertion in readelf.c, line 697 for clang binaries with coverage information
https://bugs.kde.org/show_bug.cgi?id=389412 --- Comment #1 from Julian Seward --- This may well have been fixed by recent commits to the debuginfo reader (within the past month). Can you try again? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390175] Valgrind internal assertion failure on program that runs normally
https://bugs.kde.org/show_bug.cgi?id=390175 Julian Seward changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julian Seward --- I've never seen the system fail at this point before now. One possibility is a bug in your program, which causes valgrind's internal data structures to get overwritten, leading to this failure. I'm going to close this as invalid. If you can still reproduce this, please feel free to reopen. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 397055] Extern import can't read from stdout
https://bugs.kde.org/show_bug.cgi?id=397055 --- Comment #9 from Gerry Agbobada --- I just tested it (sorry for the delay), it works perfectly. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64
https://bugs.kde.org/show_bug.cgi?id=390498 --- Comment #6 from Julian Seward --- (In reply to rrt from comment #5) > I've filed https://github.com/termux/termux-packages/issues/2148 Hi! I fixed some debuginfo reading stuff for arm64-linux recently (within the past month) so it might be worth you trying the git trunk, to see if this still happens. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396930] Option to lock the order of preferred applications for all mimetypes
https://bugs.kde.org/show_bug.cgi?id=396930 --- Comment #1 from David Faure --- Which applications auto-edit ~/.local/share/applications/mimeapps.list ?? That should be forbidden. The intent of the spec was for the user to edit this file, and only the user. In any case we can't do anything at the KDE level, to prevent an application from editing a file. But since this is a violation of the mimeapps spec, let's get those apps fixed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390866] "at" is doubled in "Block was alloc'd at"
https://bugs.kde.org/show_bug.cgi?id=390866 --- Comment #2 from Julian Seward --- You're right, it is ungrammatical. I wonder how many output-parsing GUIs will break if we change this, though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #5 from Julian Seward --- Is this still valid, considering there's been at least one related fix to the debuginfo reader recently? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397199] ballo crashes on login
https://bugs.kde.org/show_bug.cgi?id=397199 --- Comment #1 from Mathias Homann --- Created attachment 114316 --> https://bugs.kde.org/attachment.cgi?id=114316&action=edit New crash information added by DrKonqi baloo_file (5.48.0) using Qt 5.11.1 same as before: crash at login, after that it seems to be ok. -- Backtrace (Reduced): #7 0x7fb05d5f2df2 in mdb_cursor_put () from /usr/lib64/liblmdb-0.9.14.so #8 0x7fb05d5f40e0 in mdb_txn_commit () from /usr/lib64/liblmdb-0.9.14.so #9 0x7fb061164f2e in Baloo::Transaction::commit (this=this@entry=0x7fb0560ceb40) at /usr/src/debug/baloo-5.48.0/src/engine/transaction.cpp:273 #10 0x00413958 in Baloo::ModifiedFileIndexer::run (this=0x26abdb0) at /usr/src/debug/baloo-5.48.0/src/file/modifiedfileindexer.cpp:103 #11 0x7fb06062b9b2 in QThreadPoolThread::run (this=0x220e9a0) at thread/qthreadpool.cpp:101 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397199] ballo crashes on login
https://bugs.kde.org/show_bug.cgi?id=397199 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391164] constraint bug in tests/ppc64/test_isa_2_07_part1.c for mtfprwa
https://bugs.kde.org/show_bug.cgi?id=391164 --- Comment #7 from Julian Seward --- Carl, is this OK to close now? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 397200] Crash when kstars window is not in front when starting
https://bugs.kde.org/show_bug.cgi?id=397200 --- Comment #2 from TallFurryMan --- Agreed. I think alt-tabbing, at least in my dev VM, has an impact on the preparation of the UI frame. I note I enabled HIPS rendering (because it's awesome), so maybe that's a hint. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397205] New: Lambda capture with initializers and structured binding declaration not parsed
https://bugs.kde.org/show_bug.cgi?id=397205
Bug ID: 397205
Summary: Lambda capture with initializers and structured
binding declaration not parsed
Product: kdevelop
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: dvra...@kde.org
Target Milestone: ---
Variables declared with lambda captures with initializers are not
syntax-highlighted and are not part of code completion inside of the lambda.
[socket = std::weak_ptr(socketptr)]() {
// "socket" is not available for code completion and when used the entire
expression is not syntax-highlighted
};
Same applies to variables defined by structured binding.
I have the C++ profile set to C++1z in project settings and other C++14/17
constructs are highlighted correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 391845] Unrecognised instruction: __svml_irem8_l9
https://bugs.kde.org/show_bug.cgi?id=391845 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #1 from Julian Seward --- 3.11.0 is pretty old. Can you re-test with 3.13.0 or better with the latest git trunk sources? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397116] Text in permanently visible notes from the tools is shown too small, difficult to read
https://bugs.kde.org/show_bug.cgi?id=397116 --- Comment #4 from k...@mail.orbitel.bg --- Dear Tobias, Thank you very much for your information and to all team who are creating and supporting Okular. Okular is a very good tool and I believe it will get much better in future. I am thankful for the chance to have and use it. So after all this discussion I understood that missing Cyrillic letters is known problem and it will be solved in the future. Other problem - the size of letters may be managed. So I believe this my bug report can be closed now. At least some one like me if has same problems can later read in and get informed why in PDFs notes Cyrillic text is missing for now. With best regards, -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397168] Discover ignores application-specific window position settings
https://bugs.kde.org/show_bug.cgi?id=397168 --- Comment #2 from Elkasir --- Thank you for the suggestion. I hadn't before, but by setting "Ignore requested geometry" to "Force" + Yes in Application-Specific Settings, it resolved the issue. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 george changed: What|Removed |Added CC||stu...@anchev.net --- Comment #3 from george --- The only reason I am not using Falkon is because I cannot install uMatrix, uBlock Origin and HTTPS everywhere. (sorry but Adblock Plus is not a replacement for the above) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 tr...@yandex.com changed: What|Removed |Added Ever confirmed|0 |1 CC||tr...@yandex.com Status|UNCONFIRMED |CONFIRMED --- Comment #4 from tr...@yandex.com --- Yes, supporting the lots of existing webextensions is much better than waiting for someone to create new Falkon extensions. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390498] Valgrind reports errors without full backtrace on arm64
https://bugs.kde.org/show_bug.cgi?id=390498 --- Comment #7 from r...@sc3d.org --- Sorry, I didn't say that a rebuild fixed it; a Termux script (termux-elf-cleaner) used to remove some supposedly unneeded stuff from ELF binaries was found to be the culprit. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 397104] isbndb search broken
https://bugs.kde.org/show_bug.cgi?id=397104 Thomas Fischer changed: What|Removed |Added Resolution|UNMAINTAINED|WONTFIX Status|RESOLVED|CLOSED Latest Commit||a0971a1bb3bdd0405745609ea88 ||b282a45109cc7 --- Comment #3 from Thomas Fischer --- (In reply to Volker Fröhlich from comment #2) > Could you simply remove it then? It has been removed as of commit a0971a1bb3bdd0405745609ea88b282a45109cc7 The essential change is the removal of the addEngine(..) invocation for OnlineSearchIsbnDB. As I do no longer maintain version 0.4.1, you would have to edit the source code yourself and recompile/package KBibTeX. Please contact the Debian folks on how to do that for Debian. Still, I would recommend to upgrade to a newer version of KBibTeX. Even if you are still using KDE4, the 0.7.x series was the last to be release for this KDE version. I may be open to fix bugs there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396930] Option to lock the order of preferred applications for all mimetypes
https://bugs.kde.org/show_bug.cgi?id=396930 --- Comment #2 from Øystein Steffensen-Alværvik --- I don't know about that file, but KMPlayer from Neon adds itself to the top of the list for audio and video files in File Associations. I see now that the program messes with default options only; if you've changed anything for a mimetype in File Associations it respects that. But on a new user account, installing KMPlayer sets it as the default audio and video player. So if you're happy with the defaults, you msut change each association manually. :-( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397190] kwin_killer_helper hangs trying to kill window
https://bugs.kde.org/show_bug.cgi?id=397190 David Edmundson changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from David Edmundson --- Oh you have. sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397190] kwin_killer_helper hangs trying to kill window
https://bugs.kde.org/show_bug.cgi?id=397190 --- Comment #6 from David Edmundson --- So the bug is in frameworks integration adding notification with sound support to KMessageBox. There's a port on frameworks that should fix that soon. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396719] Falkon crashes and closes when trying to write fast inside address bar
https://bugs.kde.org/show_bug.cgi?id=396719 --- Comment #2 from medin --- Created attachment 114317 --> https://bugs.kde.org/attachment.cgi?id=114317&action=edit log gdb -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396719] Falkon crashes and closes when trying to write fast inside address bar
https://bugs.kde.org/show_bug.cgi?id=396719 --- Comment #3 from medin --- I'm new to gdb, I tried whole two weeks to catch crash using gdb but the browser freezes only and the crash never happened when using gdb, what happens is that the pop up address bar with suggestions persists always on top and the browser is frozen and I'm forced to kill it using ctrl+d inide gdb, but without gdb the crash is always present, I don't know how should I proceed ? I attached the log of gdb, but I think it's incomplete. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396719] Falkon crashes and closes when trying to write fast inside address bar
https://bugs.kde.org/show_bug.cgi?id=396719 --- Comment #4 from medin --- Comment on attachment 114317 --> https://bugs.kde.org/attachment.cgi?id=114317 log gdb >Starting program: /usr/bin/falkon >[Thread debugging using libthread_db enabled] >Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". >[New Thread 0x7fffd2829700 (LWP 4355)] >[New Thread 0x7fffca9ed700 (LWP 4356)] >[New Thread 0x7fffc1eac700 (LWP 4357)] >[New Thread 0x7fffc16ab700 (LWP 4358)] >[New Thread 0x7fffc0eaa700 (LWP 4359)] >[New Thread 0x7fffb3fff700 (LWP 4360)] >[New Thread 0x7fffb2883700 (LWP 4361)] >[New Thread 0x7fffb2082700 (LWP 4366)] >[New Thread 0x7fffb1881700 (LWP 4367)] >[New Thread 0x7fffb1080700 (LWP 4368)] >[New Thread 0x7fffb087f700 (LWP 4369)] >[New Thread 0x7fff9bfff700 (LWP 4370)] >[New Thread 0x7fff9b7fe700 (LWP 4371)] >[New Thread 0x7fff9affd700 (LWP 4372)] >[New Thread 0x7fff9a7fc700 (LWP 4373)] >[New Thread 0x7fff99ffb700 (LWP 4374)] >[New Thread 0x7fff997fa700 (LWP 4375)] >[New Thread 0x7fff98ff9700 (LWP 4376)] >[New Thread 0x7fff87fff700 (LWP 4378)] >[New Thread 0x7fff877fe700 (LWP 4377)] >[New Thread 0x7fff86ffd700 (LWP 4379)] >[New Thread 0x7fff867fc700 (LWP 4380)] >[New Thread 0x7fff85ffb700 (LWP 4381)] >[New Thread 0x7fff857fa700 (LWP 4382)] >[New Thread 0x7fff84903700 (LWP 4383)] >[New Thread 0x7fff6fde1700 (LWP 4384)] >[New Thread 0x7fff6f39f700 (LWP 4385)] >[New Thread 0x7fff6dcde700 (LWP 4396)] >[New Thread 0x7fff6c6e6700 (LWP 4403)] >[New Thread 0x7fff6bcc5700 (LWP 4404)] >[Thread 0x7fff6bcc5700 (LWP 4404) exited] >[Thread 0x7fffb3fff700 (LWP 4360) exited] >[New Thread 0x7fffb3fff700 (LWP 15515)] >[New Thread 0x7fff6bcc5700 (LWP 15516)] >[New Thread 0x7fff6b21d700 (LWP 15517)] >[New Thread 0x7fff6aa1c700 (LWP 15518)] >[New Thread 0x7fff69cd7700 (LWP 15523)] >[New Thread 0x7fff694d6700 (LWP 15524)] >[New Thread 0x7fff67479700 (LWP 15538)] >[New Thread 0x7fff66c78700 (LWP 15539)] >[New Thread 0x7fff66477700 (LWP 15540)] >[Thread 0x7fff6aa1c700 (LWP 15518) exited] >[Thread 0x7fffb3fff700 (LWP 15515) exited] >[Thread 0x7fff6bcc5700 (LWP 15516) exited] >[New Thread 0x7fff6bcc5700 (LWP 1)] >[New Thread 0x7fffb3fff700 (LWP 15556)] >[New Thread 0x7fff6aa1c700 (LWP 15596)] >[New Thread 0x7fff5d318700 (LWP 15652)] >[Thread 0x7fff66c78700 (LWP 15539) exited] >[New Thread 0x7fff66c78700 (LWP 15672)] >[New Thread 0x7fff57fff700 (LWP 15679)] >[Thread 0x7fff6aa1c700 (LWP 15596) exited] >[Thread 0x7fff6bcc5700 (LWP 1) exited] >[Thread 0x7fffb3fff700 (LWP 15556) exited] >[New Thread 0x7fffb3fff700 (LWP 15699)] >[New Thread 0x7fff6bcc5700 (LWP 15700)] >[New Thread 0x7fff6aa1c700 (LWP 15701)] >[Thread 0x7fff6bcc5700 (LWP 15700) exited] >[Thread 0x7fffb3fff700 (LWP 15699) exited] >[New Thread 0x7fffb3fff700 (LWP 15725)] >[New Thread 0x7fff6bcc5700 (LWP 15726)] >[New Thread 0x7fff5700 (LWP 15749)] >[New Thread 0x7fff5f7fe700 (LWP 15755)] >[New Thread 0x7fff5effd700 (LWP 15757)] >[New Thread 0x7fff5e071700 (LWP 15766)] >[Thread 0x7fffb3fff700 (LWP 15725) exited] >[Thread 0x7fff6bcc5700 (LWP 15726) exited] >[Thread 0x7fff6aa1c700 (LWP 15701) exited] >[New Thread 0x7fff6aa1c700 (LWP 15794)] >[New Thread 0x7fff6bcc5700 (LWP 15795)] >[New Thread 0x7fffb3fff700 (LWP 15796)] >[Thread 0x7fffb3fff700 (LWP 15796) exited] >[New Thread 0x7fffb3fff700 (LWP 15895)] >[Thread 0x7fffb3fff700 (LWP 15895) exited] >[Thread 0x7fff6aa1c700 (LWP 15794) exited] >[Thread 0x7fff6bcc5700 (LWP 15795) exited] >[New Thread 0x7fff6bcc5700 (LWP 16159)] >[New Thread 0x7fff6aa1c700 (LWP 16160)] >[New Thread 0x7fffb3fff700 (LWP 16161)] >[Thread 0x7fff6aa1c700 (LWP 16160) exited] >[Thread 0x7fffb3fff700 (LWP 16161) exited] >[Thread 0x7fff6bcc5700 (LWP 16159) exited] >[New Thread 0x7fff6bcc5700 (LWP 16450)] >[New Thread 0x7fffb3fff700 (LWP 16451)] >[New Thread 0x7fff6aa1c700 (LWP 16452)] > >Thread 65 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. >[Switching to Thread 0x7fff6aa1c700 (LWP 16452)] >0x769a0136 in qHash(QByteArray const&, unsigned int) () > from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 >Quit >quit -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396719] Falkon crashes and closes when trying to write fast inside address bar
https://bugs.kde.org/show_bug.cgi?id=396719 --- Comment #5 from David Rosca --- You need to type "bt" and press enter after it crashes. Also you need to have debugging symbols at least for Falkon, otherwise the backtrace won't be much useful. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397194] Face tags are not well rendered when coming from Portrait DNG files
https://bugs.kde.org/show_bug.cgi?id=397194 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Can you confirm that it depends on the type of image preview (from embedded JPEG, full view or RAW half size)? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397105] "plasmawindowed org.kde.plasma.networkmanagement" can't be closed correctly
https://bugs.kde.org/show_bug.cgi?id=397105 --- Comment #4 from Jan Grulich --- I managed to reproduce this myself so you don't need to provide any additional data. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397206] New: Kicker: submenus are too wide after opening Recent Documents containing long filename
https://bugs.kde.org/show_bug.cgi?id=397206 Bug ID: 397206 Summary: Kicker: submenus are too wide after opening Recent Documents containing long filename Product: plasmashell Version: 5.13.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: rantow...@yandex.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 114318 --> https://bugs.kde.org/attachment.cgi?id=114318&action=edit Bug behaviour Kicker's submenus are too wide when I hover mouse over Recent Documents first and there is long filename in Recent Documents. When I hover mouse over categories first or let submenus disappear and then hover mouse over them, then submenus are reasonably small. Expecting that submenus will dynamically change their size. Looks like submenus somehow inherit width of Recent Documents. Steps to reproduce: 1. Open any file with long filename (over 50 characters in my case). 2. Open Application Menu and go to Recent Documents. There will be this filename. 3. Move mouse down to app categories. Submenus will be too wide. See attachment for this behaviour. OS: Fedora 28 Plasma: 5.13.3 Qt: 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381442] SVG starter icons not displayed in application menus/launchers
https://bugs.kde.org/show_bug.cgi?id=381442 Dr. Chapatin changed: What|Removed |Added CC||el...@seznam.cz --- Comment #17 from Dr. Chapatin --- *** Bug 396084 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 396084] Icons changed via kmenuedit are not visible in start menu
https://bugs.kde.org/show_bug.cgi?id=396084 Dr. Chapatin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 381442 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #35 from Vadim Barkov --- (In reply to Florian Weimer from comment #30) Are you sure that VLL is the reason of the bug with strlen? If so, I believe that the conditional load implementation is the most natural. I'll add support for conditional load (and store) in the host part of s390x VEX. It shouldn't be hard (I've already implemented conditional dirty helpers in "vector basic" patch) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #36 from Julian Seward --- (In reply to Vadim Barkov from comment #35) > (In reply to Florian Weimer from comment #30) > > Are you sure that VLL is the reason of the bug with strlen? Exactly which bug are you referring to? If you mean the problem that Florian describes in comment 25 to comment 28, then I agree with his analysis -- I think it is correct. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397207] New: Too many open files, when reverse geocoding many images
https://bugs.kde.org/show_bug.cgi?id=397207 Bug ID: 397207 Summary: Too many open files, when reverse geocoding many images Product: digikam Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-ReverseGeoCoding Assignee: digikam-bugs-n...@kde.org Reporter: kristian.hermann.k...@gmail.com Target Milestone: --- Created attachment 114319 --> https://bugs.kde.org/attachment.cgi?id=114319&action=edit Proposed patch Running reverse geocoding on a large set of images, generates error: GLib-ERROR **: Creating pipes for GWakeup: Too many open files Actions === 1) In the Geolocation Editor, select the Reverse Geocoding tab. 2) Select a large set of images. I used 5,000 images. 3) Select Open Street Map as the service 4) Click on Apply reverse geocding button Expected result === All images with coordinates are reversed geocoded. Actual result = After around 1, requests, digikam crashes. First I got a SSL Handshake failed, error message dialog. Then when I exit the Editor, digikam crashes with: GLib-ERROR **: Creating pipes for GWakeup: Too many open files Additional info === Running the same scenario again, and tracking number of open files using: watch -n1 "ls -la /proc/$(pidof digikam)/fd | wc -l" I could see that the number was increasing, until I ran into the same problem. A similar issue (https://github.com/albertlauncher/albert/issues/634) was fixed by https://github.com/albertlauncher/albert/commit/70e3662a8e3a08137073b5932dbd7ddee136ff65 When I tested their approach on digikam, digigam did not crash running the same scenario. Given the above I propose the attached fix. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 393074] Checkbox to enable/disable the wi-fi adapter available in the network applet is not working correctly
https://bugs.kde.org/show_bug.cgi?id=393074 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #3 from Jan Grulich --- I still cannot reproduce this. Can you run "dbus-monitor --system" in a terminal and reproduce the issue and then attach here output from there? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 394360] kded5 hangs in QProcess::waitForFinished and does not reap setxkbmap
https://bugs.kde.org/show_bug.cgi?id=394360
Jiri Slaby changed:
What|Removed |Added
Attachment #112709|0 |1
is obsolete||
--- Comment #5 from Jiri Slaby ---
Created attachment 114320
--> https://bugs.kde.org/attachment.cgi?id=114320&action=edit
strace -f of kded5 (packed by xz due to size)
Now I reproduced even with strace capturing the process. (It still recurs and
is painful.)
13987 is kdeinit.
16233 is the pid of the setxkbmap process which became a zombie.
16213 is the last process which kdeinit called wait4 for. It is another
instance of setxkbmap:
> 16213 exit_group(0) = ?
> 16213 +++ exited with 0 +++
> 13987 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=16213,
> si_uid=500, si_status=0, si_utime=0, si_stime=1} ---
> 13987 waitid(P_ALL, 0, {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=16213,
> si_uid=500, si_status=0, si_utime=0, si_stime=0}, WNOHANG|WEXITED|WNOWAIT,
> NULL) = 0
> 13987 wait4(16213,
> 13987 <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG,
> {ru_utime={tv_sec=0, tv_usec=2524}, ru_stime={tv_sec=0, tv_usec=10098}, ...})
> = 16213
setxkbmap is not the only unreaped process. I also saw zombie of xterm pinned
to kdeinit (opened via ctrl-alt-t which is a custom shortcut to run xterm).
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 397207] Too many open files, when reverse geocoding many images
https://bugs.kde.org/show_bug.cgi?id=397207 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Thanks for the error report and patch, yes that is a wrong use of QNetworkAccessManager in our code. Thousands of QNetworkAccessManager are created. I'll fix it tonight, but different. Maik -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 396577] No User Templates after update from Kile 2.0
https://bugs.kde.org/show_bug.cgi?id=396577 --- Comment #2 from Markus Rudolf Domula --- Grea! It workes. Just another problem: The spell check is not recognized although I installed aspell and ispell. How can I fix this? And another thing: the autocompletition. whe I type \par \paragraph appears and when I just press enter as I am used to, \paragraph appears. Can you help me with this too? Over all the new kile seems quite nice to me:-) Thanks markus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397190] kwin_killer_helper hangs trying to kill window
https://bugs.kde.org/show_bug.cgi?id=397190 --- Comment #7 from undyin...@gmail.com --- Btw, I've meet the same problem with org_kde_powerdevile (sorry for posting it here) but here the backtrace of thread which use 100% CPU: Thread 7 (Thread 0x7f022c143700 (LWP 14031)): #0 0x7f0251f01483 in __GI___poll (fds=0x7f022c142c80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f022f55d10f in ?? () from /usr/lib64/libasound.so.2 #2 0x7f022f59ea14 in ?? () from /usr/lib64/libasound.so.2 #3 0x7f022f7f2d05 in ?? () from /usr/lib64/vlc/plugins/audio_output/libalsa_plugin.so #4 0x7f02387831c2 in ?? () from /usr/lib64/libvlccore.so.9 #5 0x7f0238765f9c in ?? () from /usr/lib64/libvlccore.so.9 #6 0x7f024f16f96a in start_thread (arg=0x7f022c143700) at pthread_create.c:463 #7 0x7f0251f0d05f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397190] kwin_killer_helper hangs trying to kill window
https://bugs.kde.org/show_bug.cgi?id=397190 --- Comment #8 from undyin...@gmail.com --- Created attachment 114321 --> https://bugs.kde.org/attachment.cgi?id=114321&action=edit powerdevil backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397208] New: Reference tool not updating correctly when tabbing to full screen. Bad dirty rectangle update.
https://bugs.kde.org/show_bug.cgi?id=397208 Bug ID: 397208 Summary: Reference tool not updating correctly when tabbing to full screen. Bad dirty rectangle update. Product: krita Version: 4.1.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: magick.c...@gmail.com Target Milestone: --- Created attachment 114322 --> https://bugs.kde.org/attachment.cgi?id=114322&action=edit Before tab Mind KDE fully updated with Nvidia gtx 580 GPU Krita 4.1.1 When I tab to full window mode a lange chunk of the reference image stays in the wrong place, covering the image I need to work on. Like the dirty rectangle has a one off programming error on its update. Reproducible. Happens every time (I think). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397208] Reference tool not updating correctly when tabbing to full screen. Bad dirty rectangle update.
https://bugs.kde.org/show_bug.cgi?id=397208 --- Comment #1 from Douglas --- I wanted to add an after picture but can't add a second attachment. So here is a link. http://pasteall.org/pic/f393754a9599c17f3d1047260582f9cc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397208] Reference tool not updating correctly when tabbing to full screen. Bad dirty rectangle update.
https://bugs.kde.org/show_bug.cgi?id=397208 Douglas changed: What|Removed |Added CC||magick.c...@gmail.com --- Comment #2 from Douglas --- Created attachment 114323 --> https://bugs.kde.org/attachment.cgi?id=114323&action=edit Tab error two With bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 397070] "Add to desktop" feature of the apps launcher does not work correctly with KCMs
https://bugs.kde.org/show_bug.cgi?id=397070 --- Comment #2 from Kai Uwe Broulik --- Git commit cf7381d7fbff0c966b93b7c2df4cd748011689e2 by Kai Uwe Broulik. Committed on 06/08/2018 at 12:33. Pushed by broulik into branch 'Plasma/5.12'. [Service Runner] Look up relative entryPaths For KCMs we get a relative entryPath() for our KService resulting in an invalid URL being created. Differential Revision: https://phabricator.kde.org/D14546 M +17 -9runners/services/servicerunner.cpp https://commits.kde.org/plasma-workspace/cf7381d7fbff0c966b93b7c2df4cd748011689e2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 393074] Checkbox to enable/disable the wi-fi adapter available in the network applet is not working correctly
https://bugs.kde.org/show_bug.cgi?id=393074 --- Comment #4 from Dr. Chapatin --- Created attachment 114324 --> https://bugs.kde.org/attachment.cgi?id=114324&action=edit dbus-monitor -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 393074] Checkbox to enable/disable the wi-fi adapter available in the network applet is not working correctly
https://bugs.kde.org/show_bug.cgi?id=393074 --- Comment #5 from Jan Grulich --- Did you enable wireless after you disabled it? In the log I see twice it has been disabled, but not enabled. Either you didn't enable it or NM doesn't correctly propagate this change which would explain your problem. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 397209] New: 'about kpmcore' has no icon
https://bugs.kde.org/show_bug.cgi?id=397209 Bug ID: 397209 Summary: 'about kpmcore' has no icon Product: partitionmanager Version: Git Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: sit...@kde.org Target Milestone: --- Created attachment 114325 --> https://bugs.kde.org/attachment.cgi?id=114325&action=edit screenshot about kpmcore dialog in partitionmanager has no icon in the dialog. probably should simply use the partitionmanager icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396923] [regression] Plasma crashes repeatedly after login
https://bugs.kde.org/show_bug.cgi?id=396923 korg...@yandex.com changed: What|Removed |Added CC||korg...@yandex.com Status|UNCONFIRMED |CONFIRMED Keywords||regression Ever confirmed|0 |1 --- Comment #1 from korg...@yandex.com --- I'm also facing this problem. In my case I'm using the latest Kubuntu 18.04.1 with all updates to date (it didn't happen in Kubuntu 18.04). I have no applets, other than the standard panel on the bottom. Plasma crashes repeatedly until it just stops to be respawned. This happens with every user. What I've already tried: * I've deleted the printer and I've reconfigured it (someone on the Internet forums suggested it); * Remove discover (other people had suggested it); * Deleted the cache; * Deleted ~/.local/share/kactivitymanagerd/ None of this has worked. Is there anything I can do to get more information to post here? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 393074] Checkbox to enable/disable the wi-fi adapter available in the network applet is not working correctly
https://bugs.kde.org/show_bug.cgi?id=393074 --- Comment #6 from Dr. Chapatin --- I followed exactly the same steps shown in my screencast. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #4 from Nate Graham --- Clementine (a fork of an older version of Amarok) has the same issue, BTW: https://github.com/clementine-player/Clementine/issues/5524 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 397210] New: Touchpad indicator is missing from the system tray under Wayland
https://bugs.kde.org/show_bug.cgi?id=397210 Bug ID: 397210 Summary: Touchpad indicator is missing from the system tray under Wayland Product: Touchpad-KCM Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-applet Assignee: rajeeshknamb...@gmail.com Reporter: bugsefor...@gmx.com Target Milestone: --- "Touchpad" is checked in the system tray settings under "Extra items" but its icon only appears in the system tray under X11. I use neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397012] glibc ld.so uses arch_prctl on i386
https://bugs.kde.org/show_bug.cgi?id=397012 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- commit 2eb2df759f51b15702934dee108f4c20c3db5fef Author: Mark Wielaard Date: Tue Jul 31 15:32:43 2018 +0200 Bug 397012 - glibc ld.so uses arch_prctl on i386. arch_prctl used to be amd64 only. But since linux 4.12 it is also implemented for i386. And since glibc 2.28 ld.so will use it to see if the cpu/kernel provides CET support. To prevent seeing: WARNING: unhandled x86-linux syscall: 384 You may be able to write your own handler. Read the file README_MISSING_SYSCALL_OR_IOCTL. Nevertheless we consider this a bug. Please report it at http://valgrind.org/support/bug_reports.html. on every program run under valgrind just make it explicitly not implemented (ENOSYS). This is fine for the glibc usage. It just indicates there is no CET support. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397211] New: Discover doesn't properly show flatpak appdata (missing images, description flatpak name)
https://bugs.kde.org/show_bug.cgi?id=397211 Bug ID: 397211 Summary: Discover doesn't properly show flatpak appdata (missing images, description flatpak name) Product: Discover Version: 5.13.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: autinfranco...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- Created attachment 114326 --> https://bugs.kde.org/attachment.cgi?id=114326&action=edit No pictures displayed, no description on krita flatpak When viewing flatpaks through discover, no images previews are being displayed and some keep their flatpak names (e.g. org.gnome.Lollypop.desktop). Steps to reproduce: - Open discover - Click on a flatpak Additional information: At startup, Discovers asks to check whether Appstream is properly set up. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397213] New: Using the default animation caching settings causes playback issue with small resolution frames
https://bugs.kde.org/show_bug.cgi?id=397213 Bug ID: 397213 Summary: Using the default animation caching settings causes playback issue with small resolution frames Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: frabb...@gmail.com Target Milestone: --- With the "cache storage->on disk" option enabled, the animation preview miss all the frames that contains less to more or less 40x40 pixels. Try to make a new animation with a small resolution (i.e. for pixelart), for example 16x16 pixels: the preview doesn't work! Also, if you make a new project with a bigger resolution (i.e. 1000x1000) it still not work if you don't paint at least a 40x40 (more or less) area... frames with less of a certain number of pixels are reads as "empty" from the preview. This issue is only present with the "cache storage->on disk" option enabled, setting it to "In-memory" there are no problems and ALL the frames are displayed in the preview, also if there is only one pixel in the image! Sorry for my bad explanation! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397212] New: Add create vector to pull down layers in menu at top of Krita.
https://bugs.kde.org/show_bug.cgi?id=397212 Bug ID: 397212 Summary: Add create vector to pull down layers in menu at top of Krita. Product: krita Version: 4.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: magick.c...@gmail.com Target Milestone: --- "add vector layer", should be added to the layers pull down layers menu at the top. +1 for having an option to create types of layers in the layer menu. Can you please make a wish bug for this? Raghavendra Kamath Illustrator and a Krita User. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 394360] kded5 hangs in QProcess::waitForFinished and does not reap setxkbmap
https://bugs.kde.org/show_bug.cgi?id=394360
--- Comment #6 from Fabian Vogt ---
That strace output is very useful:
16233 exit_group(0) = ?
16233 +++ exited with 0 +++
13987 <... ppoll resumed> ) = ? ERESTARTNOHAND (To be restarted if
no handler)
13987 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=16233,
si_uid=500, si_status=0, si_utime=0, si_stime=0} ---
13987 ppoll([{fd=-1}, {fd=-1}, {fd=-1}, {fd=46, events=POLLIN}], 4, NULL, NULL,
8
13990 <... poll resumed> ) = 1 ([{fd=3, revents=POLLIN}])
If I interpret this correctly, kdeinit was currently doing a ppoll (no sigmask,
so == poll) and it had no handler, as otherwise it would've done one of the
calls in the handler and not continue with ppoll.
This seems to explain it:
13987 rt_sigaction(SIGCHLD, {sa_handler=SIG_DFL, sa_mask=[],
sa_flags=SA_RESTORER, sa_restorer=0x7f0242406110}, NULL, 8) = 0
It's the last call to rt_sigaction in that process, so it removed its signal
handler, so it's no surprise it stays a zombie...
Now the question is where the rt_sigaction call comes from. It might be
somewhere in forkfd.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 Vadim Barkov changed: What|Removed |Added Attachment #114305|0 |1 is obsolete|| --- Comment #37 from Vadim Barkov --- Created attachment 114327 --> https://bugs.kde.org/attachment.cgi?id=114327&action=edit New VLL implementation Based on Florian's patch with guarded loads (attachment 114302) I've just added host part to his code and replaced Iop_SetElem8x16 to direct write. This patch passes tests but additional testing is needed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396412] Improve the new sidebar concept for desktop mode
https://bugs.kde.org/show_bug.cgi?id=396412 --- Comment #2 from Marco Martin --- the current expanding sidebar in master should behave like that. can you check if it's suited to your needs? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 394360] kded5 hangs in QProcess::waitForFinished and does not reap setxkbmap
https://bugs.kde.org/show_bug.cgi?id=394360 Fabian Vogt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #7 from Fabian Vogt --- Please try to run kded5 without the glib event loop: kquitapp5 kded5; QT_NO_GLIB=1 kded5 If that works fine, it's probably a bug in either glib itself or in its integration. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #6 from John Reiser --- I believe that this bug and revised patch still are valid. The intervening https://bugs.kde.org/show_bug.cgi?id=395682#c9 is a distinct issue regarding .rodata for multiple segments. That bug does not address the handling of multiple adjacent (after alignment) .rodata* sections within the same segment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 --- Comment #2 from Marco Martin --- (In reply to Nate Graham from comment #1) > Showing an overlay that displays a vertical list of actions with both icons > and text seems like it would be the most humane. We already have a UI for > this; maybe we just need to use it and abandon the "swipe to show inline hmm, what it is? could you elaborate what this should do? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #38 from Vadim Barkov --- (In reply to Florian Weimer from comment #30) Floarian, I can't reproduce the problem that you describe. Could you take my patch (attachment 114327) and test against your executable? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396412] Improve the new sidebar concept for desktop mode
https://bugs.kde.org/show_bug.cgi?id=396412 --- Comment #3 from Emmanuel Lepage Vallée --- I will take a look, I am back from vacation today. For the next week I will work on integrating the changes. Thanks for fixing these issues. If you can also take a look at the header one, hopefully I will be able to release 3.0.1 during Akademy with less custom code. See ya at Akademy (I am already in VIE) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 --- Comment #3 from Emmanuel Lepage Vallée --- > hmm, what it is? could you elaborate what this should do? This can wait for next week with VDG people? Right now that was one of the issue raised when I a/b tested Ring-KDE at my local hackerspace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 --- Comment #4 from Nate Graham --- (In reply to Marco Martin from comment #2) > (In reply to Nate Graham from comment #1) > > Showing an overlay that displays a vertical list of actions with both icons > > and text seems like it would be the most humane. We already have a UI for > > this; maybe we just need to use it and abandon the "swipe to show inline > > hmm, what it is? could you elaborate what this should do? My idea is basically that when you swipe on an item, instead of having icon-only action buttons appear inline, they would appear along with text on an overlaysheet, the way Discover used to do for apps that could be downloaded from multiple sources: https://cgit.kde.org/discover.git/tree/discover/qml/ApplicationPage.qml?h=Plasma/5.12#n48 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 395156] kirigami-5.47 fails to build on rhel7 (using gcc-4.8.5)
https://bugs.kde.org/show_bug.cgi?id=395156 Marco Martin changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kir ||igami/fc5bb5fd892acc6938e0a ||ef3709dbf00d0219050 --- Comment #2 from Marco Martin --- Git commit fc5bb5fd892acc6938e0aef3709dbf00d0219050 by Marco Martin. Committed on 06/08/2018 at 14:02. Pushed by mart into branch 'master'. ld on old gcc M +1-1src/delegaterecycler.cpp https://commits.kde.org/kirigami/fc5bb5fd892acc6938e0aef3709dbf00d0219050 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 Nate Graham changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #8 from Nate Graham --- Ah, I see what you mean now. However, there is no possible way to fix that with the current approach of putting the content (which includes the tab view) inside a scroll view. It seems that Christoph is right, and the real solution is to redesign the KCMs to never have a minimum height that's taller than about 700 px, so they'll never get cut off on anyone's screen. At that point, we can remove the scrollview. Kishore, do you think you could collect a list of KCMs that are too tall to fit without a scrollview? Then we can focus our efforts there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397153] [wayland] - Support PresentWindows for grouped tasks
https://bugs.kde.org/show_bug.cgi?id=397153 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Present Windows effect isn't triggered after clicking grouped windows in Task Manager in X11 and Wayland. How to enable it - Present Windows effect is enabled in Desktop Effects Distribution: KDE neon Developer Edition Kernel: 4.15.0-29-generic Plasma: 5.13.80 Apps: 18.11.70 Qt: 5.11.1 Frameworks: 5.48.0 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 397214] New: Context info vanishes after a second if drawn above location
https://bugs.kde.org/show_bug.cgi?id=397214 Bug ID: 397214 Summary: Context info vanishes after a second if drawn above location Product: kstars Version: 2.9.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: p.suetter...@royac.iac.es Target Milestone: --- right clicking in the star map normally opens a context info window right and below the current position. If the menue is too high to fully display that way, it is instead placed 'above' (window base is level with position). Those 'above' painted windows for me only pop up for a second and directly vanish again (also if I move the mouse cursor in and try to select an item). Windows drawn 'below' stay until I select something or right-click again somewhere else. This is openSUSE Tumbleweed (20180803) running Plasma DE 5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396930] Option to lock the order of preferred applications for all mimetypes
https://bugs.kde.org/show_bug.cgi?id=396930 --- Comment #3 from Christoph Feck --- I guess this is expected behaviour, probably caused by respecting a 'priority' in the desktop file. If you only have 'Ark' installed, then Office Open XML files would open in 'Ark', because they are .zip archives. If you then install 'Okular', it must have a higher priority to show .odt files in 'Okular'. Finally, if you now install 'LibreOffice', all files should open there by default. You probably want bug 254560 instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397215] New: Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 Bug ID: 397215 Summary: Visual bug around the maximize/unmaximize button Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 114328 --> https://bugs.kde.org/attachment.cgi?id=114328&action=edit when display scaling factor is 1.2 See the screenshots. I can reproduce easily maximizing/unmaximizing the desktop settings window some times in sequence. Arch Linux Plasma 5.13.4 frameworks 5.48 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 --- Comment #1 from Dr. Chapatin --- Created attachment 114329 --> https://bugs.kde.org/attachment.cgi?id=114329&action=edit no change in display scaling factor -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented
https://bugs.kde.org/show_bug.cgi?id=385409 --- Comment #39 from Florian Weimer --- (In reply to Vadim Barkov from comment #38) > (In reply to Florian Weimer from comment #30) > > Floarian, > > I can't reproduce the problem that you describe. Could you take my patch > (attachment 114327 [details]) and test against your executable? Do you have GCC 7 installed? Then you can build glibc like this: git clone --depth 1 git://sourceware.org/git/glibc.git cd glibc mkdir build cd build ../configure --prefix=/usr CFLAGS="-O2 -g -march=z13 -mtune=z13" make (Parallel make is supported.) After that, if valgrind is on PATH, you can run /bin/true like this: ./testrun.sh --tool=valgrind /bin/true This should report no issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396923] [regression] Plasma crashes repeatedly after login
https://bugs.kde.org/show_bug.cgi?id=396923 Christoph Feck changed: What|Removed |Added Resolution|--- |BACKTRACE Status|CONFIRMED |NEEDSINFO --- Comment #2 from Christoph Feck --- To investigate the crash, please add a backtrace, ideally with Qt and Plasma debug symbol packages installed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #9 from Kishore Gopalakrishnan --- Created attachment 114330 --> https://bugs.kde.org/attachment.cgi?id=114330&action=edit Touchpad KCM, which shows the ideal behaviour While looking through the various KCMs, I noticed that input devices > touchpad (image attached) has what I would consider the ideal behaviour (there is a scroll area inside each tab). The following KCMs did not fit without a scrollbar on a 768 px tall screen, of which maybe 20 pixels were taken up by the panel. The available height would probably be even smaller for people who don't hide titlebars and borders for maximised windows. Desktop behaviour > virtual desktops (I have 16 virtual desktops, so that might be the reason. I think the default is 9, which would *just* fit there) Display and monitor > displays (There are no tabs here, so there is no problem) Multimedia > audio volume (Not on my setup, but it could become too tall if there are 4–5 applications playing audio. I'm not sure what would happen then) Power management > Energy saving Input devices > touchpad (this behaves properly, as seen in the attached image) I'm not sure about the 'printers' KCM, since I don't have any print service installed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 395607] Use alternating background colors for list views
https://bugs.kde.org/show_bug.cgi?id=395607 --- Comment #2 from Marco Martin --- I think that in a discussion on telegram the idea was ultimately abandoned? (as look too .. old) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363860] Slideshow does not cycle if only one image in set directory
https://bugs.kde.org/show_bug.cgi?id=363860 --- Comment #6 from Pit --- One year and many versions (5.13.4) later, and still no change. Is it that difficult to validate cached info before using it? :( -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397123] Plasma Discover 5.13.4; KNSRC3 error; "Config group not found! Check your KNS3 installation."
https://bugs.kde.org/show_bug.cgi?id=397123 --- Comment #4 from Aleix Pol --- Can you try running with "G_DEBUG=fatal-criticals" environment variable? This way maybe we'll get to know what's offending glib. It should crash, that backtrace will be more useful. Thanks for your patience! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394960] Kirigami.Theme.highlightColor changes depending on whether the window is selected
https://bugs.kde.org/show_bug.cgi?id=394960 --- Comment #4 from Marco Martin --- this is simply following global color settings on systemsettings colors, "edit scheme" "inactive selection changes color" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397152] [wayland] - Support Window Previews
https://bugs.kde.org/show_bug.cgi?id=397152 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Tooltips with previews not working at all in Wayland? Distribution: KDE neon Developer Edition Kernel: 4.15.0-29-generic Plasma: 5.13.80 Apps: 18.11.70 Qt: 5.11.1 Frameworks: 5.48.0 -- You are receiving this mail because: You are watching all bug changes.
