[plasmashell] [Bug 375844] Accessing config fails if not initially done by the plasmoid, but rather a config dialogue
https://bugs.kde.org/show_bug.cgi?id=375844 --- Comment #2 from Fuchs--- (In reply to David Edmundson from comment #1) > Can you define: > "subsequent access to plasma.configuration will fail?" > > > as in the object is null? Or it gets unexpected values, or it crashes? It doesn't crash (as in: plasma), however, when I tried to use trim on the variable later on (see the code) it was undefined, when I tried to print plasmoid.configuration to get some debug info it basically did nothing / stopped there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375845] New: Unrecognised instruction using std::random_device
https://bugs.kde.org/show_bug.cgi?id=375845 Bug ID: 375845 Summary: Unrecognised instruction using std::random_device Product: valgrind Version: 3.11.0 Platform: Other OS: unspecified Status: UNCONFIRMED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: cochamb...@tycoint.com Target Milestone: --- Full text of program is: #include using std::cout; #include using std::random_device; int main() { random_device random_seeder; cout << "number is " << random_seeder() << "\n"; return 0; } uname -a Linux colin-Precision-Tower-3620 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Valgrind command line: valgrind --read-inline-info=yes --log-file=valgrind.out -v ./random Contents of valgrind.out: ==30058== Memcheck, a memory error detector ==30058== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==30058== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==30058== Command: ./random ==30058== Parent PID: 28615 ==30058== --30058-- --30058-- Valgrind options: --30058----read-inline-info=yes --30058----log-file=valgrind.out --30058---v --30058-- Contents of /proc/version: --30058-- Linux version 4.4.0-42-generic (buildd@lgw01-13) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 --30058-- --30058-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-avx-avx2-bmi --30058-- Page sizes: currently 4096, max supported 4096 --30058-- Valgrind library directory: /usr/lib/valgrind --30058-- Reading syms from /media/big/colin/projects/c++-play/random-device/random --30058-- Reading syms from /lib/x86_64-linux-gnu/ld-2.23.so --30058-- Considering /lib/x86_64-linux-gnu/ld-2.23.so .. --30058-- .. CRC mismatch (computed d3da0723 wanted a1c29704) --30058-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so .. --30058-- .. CRC is valid --30058-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux --30058-- Considering /usr/lib/valgrind/memcheck-amd64-linux .. --30058-- .. CRC mismatch (computed 5529a2c7 wanted 5bd23904) --30058--object doesn't have a symbol table --30058--object doesn't have a dynamic symbol table --30058-- Scheduler: using generic scheduler lock implementation. --30058-- Reading suppressions file: /usr/lib/valgrind/default.supp ==30058== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-30058-by-colin-on-??? ==30058== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-30058-by-colin-on-??? ==30058== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-30058-by-colin-on-??? ==30058== ==30058== TO CONTROL THIS PROCESS USING vgdb (which you probably ==30058== don't want to do, unless you know exactly what you're doing, ==30058== or are doing some strange experiment): ==30058== /usr/lib/valgrind/../../bin/vgdb --pid=30058 ...command... ==30058== ==30058== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==30058== /path/to/gdb ./random ==30058== and then give GDB the following command ==30058== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=30058 ==30058== --pid is optional if only one valgrind process is running ==30058== --30058-- REDIR: 0x401cdc0 (ld-linux-x86-64.so.2:strlen) redirected to 0x3809e181 (???) --30058-- Reading syms from /usr/lib/valgrind/vgpreload_core-amd64-linux.so --30058-- Considering /usr/lib/valgrind/vgpreload_core-amd64-linux.so .. --30058-- .. CRC mismatch (computed a30c8eaa wanted 7ae2fed4) --30058--object doesn't have a symbol table --30058-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so --30058-- Considering /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so .. --30058-- .. CRC mismatch (computed 402c2ab5 wanted 745f25ae) --30058--object doesn't have a symbol table ==30058== WARNING: new redirection conflicts with existing -- ignoring it --30058-- old: 0x0401cdc0 (strlen ) R-> (.0) 0x3809e181 ??? --30058-- new: 0x0401cdc0 (strlen ) R-> (2007.0) 0x04c31020 strlen --30058-- REDIR: 0x401b710 (ld-linux-x86-64.so.2:index) redirected to 0x4c30bc0 (index) --30058-- REDIR: 0x401b930 (ld-linux-x86-64.so.2:strcmp) redirected to 0x4c320d0 (strcmp) --30058-- REDIR: 0x401db20 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x4c35270 (mempcpy) --30058-- Reading syms from /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 --30058-- Considering /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21 .. --30058-- .. CRC mismatch (computed 834c912e wanted c67ab13d) --30058--object doesn't have a symbol table --30058-- Reading syms from /lib/x86_64-linux-gnu/libgcc_s.so.1 --30058-- Considering /lib/x86_64-linux-gnu/libgcc_s.so.1 .. --30058-- .. CRC mismatch (computed b9a68419 wanted 29d51b00) --30058--
[plasmashell] [Bug 375844] Accessing config fails if not initially done by the plasmoid, but rather a config dialogue
https://bugs.kde.org/show_bug.cgi?id=375844 --- Comment #1 from David Edmundson--- Can you define: "subsequent access to plasma.configuration will fail?" as in the object is null? Or it gets unexpected values, or it crashes? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374133] Okular no longer opens comic book format
https://bugs.kde.org/show_bug.cgi?id=374133 --- Comment #13 from Wolfgang Bauer--- (In reply to Albert Astals Cid from comment #12) > Wolfgang which Qt and KArchive are you using? Qt 5.7.1 and karchive 5.30. Also tried with Qt 5.8.0, the same problem. I also tried other distributions last week using LiveCDs: - openSUSE Tumbleweed (20170123) with Qt 5.7.1 and karchive 5.29 - KDE Neon user edition (20170119-0019) - KDE Neon developer edition (20170125-0806) This was reproducible everywhere. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374957] Krita select another brush preset than the one selected after start-up
https://bugs.kde.org/show_bug.cgi?id=374957 jdre...@web.de changed: What|Removed |Added CC||jdre...@web.de --- Comment #8 from jdre...@web.de --- It seems to me because of this changes in 3.1.2 the brushes do not switch anymore to the previously selected stylus brush / eraser choice. When I try to use the wacom eraser it switches back to a startup brush, when I turn the stylus to draw it chooses the same startup brush again. No matter what brushes I have chosen before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 375813] DrKonqi can't report error because address is missing
https://bugs.kde.org/show_bug.cgi?id=375813 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Dolphin does not set a specific address, which means it should use the default one. Do you have the "Report Bug..." button in the Help menu? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian
https://bugs.kde.org/show_bug.cgi?id=322935 Tom Hugheschanged: What|Removed |Added CC||alexander.ress...@gmail.com --- Comment #36 from Tom Hughes --- *** Bug 358620 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375844] New: Accessing config fails if not initially done by the plasmoid, but rather a config dialogue
https://bugs.kde.org/show_bug.cgi?id=375844 Bug ID: 375844 Summary: Accessing config fails if not initially done by the plasmoid, but rather a config dialogue Product: plasmashell Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: deve...@fuchsnet.ch CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Hi, in my custom plasmoid, when I access a plasmoid.config value from the config dialogue without having used it from the plasmoid before, the plasmoid subsequently fails to access plasmoid.configuration. See https://github.com/Fuchs/hoppla-sa/commit/0bc8ca22e966f438453d2a34f34cce7836502425#diff-52c7b097dabe3c69cef049acf7f74fdb which fixes it in my case. Before that commit, one could 1) reload plasma 2) right click the plasmoid and open the configuration dialogue 3) save config, close config dialogue 4) open the plasmoid by clicking on it 5) subsequent access to plasma.configuration will fail, leading to the plasmoid not being able to read out the URL and thus contact the Hue bridge -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 Tom Hugheschanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #13 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 322935 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian
https://bugs.kde.org/show_bug.cgi?id=322935 --- Comment #35 from Jeffrey Walton--- (In reply to Julian Seward from comment #27) > This keeps cropping up, for example most recently in bug 366464. Maybe > I should explain more why this isn't supported > > Truth be told, I don't believe this is really even necessary, either... Here' another alternative that was not available in 2013: run a different distro on the RPI, like openSUSE or CentOS. Here's a compelling reason to do so for some RPI devices, like the Raspberry Pi 3 (if the incompatibilities were not enough): performance. The RPI3 uses an ARM-32 armhf image and its under-performing on the ARMv8/Cortex-A53 processor it has. Also see https://stackoverflow.com/questions/41956400/thread-performance-issues-for-java-on-raspberry-pi?noredirect=1#comment71101862_41956400 . -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375834] Missing shared libray for akregator
https://bugs.kde.org/show_bug.cgi?id=375834 --- Comment #2 from Clay Weber--- (In reply to Clay Weber from comment #1) > This also affects Kontact and Kmail I also just noted my system affected uses the testing repo for User edition for 5.9, which is known to have problems with QtWebEngine, so nevermind -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 Cade Robinsonchanged: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from Cade Robinson --- I just noticed today that enabling "Run all Konsole windows in a single process" and trying to run a "konsole --new-tab -e ssh HOST" doesn't work but it does work without that setting but it pops in a new window. Is this related to this bug? Will the change fix that? Should it be a new bug? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375834] Missing shared libray for akregator
https://bugs.kde.org/show_bug.cgi?id=375834 Clay Weberchanged: What|Removed |Added CC||c...@claydoh.com --- Comment #1 from Clay Weber --- This also affects Kontact and Kmail -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375083] Discover crashes on opening
https://bugs.kde.org/show_bug.cgi?id=375083 Aleix Polchanged: What|Removed |Added CC||ad...@rcstar.net --- Comment #9 from Aleix Pol --- *** Bug 375463 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net --- Comment #11 from Ivo Raisr --- I've done some googling for you as regards "unhandled instruction: 0xF1010200" and found this bug: https://bugs.kde.org/show_bug.cgi?id=322935 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #12 from Julian Seward--- See https://bugs.kde.org/show_bug.cgi?id=322935#c27 and the comments that follow. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375825] Please include 1920x1200 size wallpaper
https://bugs.kde.org/show_bug.cgi?id=375825 Kai Uwe Broulikchanged: What|Removed |Added Assignee|plasma-de...@kde.org|verme...@gmail.com CC||k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 375838] Crash when copying large data to clipboard
https://bugs.kde.org/show_bug.cgi?id=375838 Kai Uwe Broulikchanged: What|Removed |Added Component|general |plasma-widget Ever confirmed|0 |1 Product|plasmashell |klipper Status|UNCONFIRMED |CONFIRMED Version|5.5.5 |5.9.0 Target Milestone|1.0 |--- Assignee|k...@davidedmundson.co.uk|mgraess...@kde.org CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- I can confirm. Probably Klipper's delegate which shows the text getting overloaded. I think Klipper's model should limit the amount of text exposed through the model to some sensible amount. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366264] Was doing upgrade in Plasma DIscover
https://bugs.kde.org/show_bug.cgi?id=366264 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 370906 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375843] New: names of akonadi resources in kwallet makes sharing wallets difficult
https://bugs.kde.org/show_bug.cgi?id=375843 Bug ID: 375843 Summary: names of akonadi resources in kwallet makes sharing wallets difficult Product: kmail2 Version: 5.2.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@reaktanz.de Target Milestone: --- as soon as you configure an IMAP resource, it ends up in kwallet named "akonadi_imap_resource_Xrc", where "X" is a number and numbers increase for each additional account. now, i'm trying to use a shared (k)wallet on two machines running kmail2. the problem is that mail accounts were configured in a different order, so the numbers don't match and re-entering passwords effectively overwrites the entries of the other machine. there doesn't seem to be an easy way of renaming the akonadi resources, is there? actually, it would be really helpful if you could just rename those resources to your liking, that would solve the problem. but that would probably involve delicate changes to akonadi (similar requests date back to 2009 at least, e.g. #208188). this gets even more problematic when some, but not all accounts are being used on both machines (e.g., using A and B one machine 1, but C and A on machine 2). then it's not even possible to solve the issue by deleting all IMAP accounts and reconfiguring them in the correct order again (and then reconfiguring folder settings, identities and filter targets...). in effect, this makes sharing wallets between machines extremely difficult, if not impossible, as soon as you're trying to use kmail with a slighly different IMAP configuration. for the time being, it would be a good-enough workaround if you could define a designated wallet for kmail. that is, kmail wouldn't necessarily store its passwords in the default wallet, but a configurable one. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370906] Discover crash immediately after system update
https://bugs.kde.org/show_bug.cgi?id=370906 Aleix Polchanged: What|Removed |Added CC||411skit...@gmail.com --- Comment #3 from Aleix Pol --- *** Bug 366264 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373297] Discover Package Manager Crashes while updating/installing
https://bugs.kde.org/show_bug.cgi?id=373297 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 370906 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370906] Discover crash immediately after system update
https://bugs.kde.org/show_bug.cgi?id=370906 Aleix Polchanged: What|Removed |Added CC||nickmer...@gmail.com --- Comment #2 from Aleix Pol --- *** Bug 373297 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375463] Plasma Discover crashed at launch
https://bugs.kde.org/show_bug.cgi?id=375463 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 375083 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #10 from WernerF--- Hi, I have a very similar problem (though not wite the same). I am using Valgrind 3.12.0 on a Raspberry. According Julian's comment, many of these things should have been fixed. My program does have memory leaks but runs ok for a few days. With Valgrind it exits immediately (see attachment valgrind.log). Any idea? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 WernerFchanged: What|Removed |Added CC||werner.fr...@web.de --- Comment #9 from WernerF --- Created attachment 103750 --> https://bugs.kde.org/attachment.cgi?id=103750=edit valgrind.log -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 375837] mistyped word
https://bugs.kde.org/show_bug.cgi?id=375837 Vladimir Amelyanovichchanged: What|Removed |Added Summary|misstyped word |mistyped word -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #14 from caulier.gil...@gmail.com --- Git commit 9594cb3f9a334768aa21f827892b180ebb8c4050 by Gilles Caulier. Committed on 01/02/2017 at 14:10. Pushed by cgilles into branch 'master'. With new Exiv2 0.26, MPF Exif tags group have been introduced and generate an exception if we try to handle it M +6-1libs/dmetadata/metaengine_exif.cpp https://commits.kde.org/digikam/9594cb3f9a334768aa21f827892b180ebb8c4050 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375842] New: Invert inside levels
https://bugs.kde.org/show_bug.cgi?id=375842 Bug ID: 375842 Summary: Invert inside levels Product: krita Version: 3.1.1 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: adjustment layers Assignee: krita-bugs-n...@kde.org Reporter: ene...@gmail.com Target Milestone: --- It is feature from PS: When using levels there is possibility to invert sliders, move left controller to right and vice versa, both for input and output. It would be nice to have it in Krita. It would also eliminate need for "invert" filter. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #13 from caulier.gil...@gmail.com --- WildCowboy, The problem is in Exiv2 ExifTags class. We must be able to handle MPF tags with Exiv2::ExifKey as with other Exif tag groups... I wil fix digiKam to not handle MPF section for the moment, until Exiv2 is fixed. Please report this problem to Exiv2 bugzilla, as UPSTREAM. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #12 from caulier.gil...@gmail.com --- MPF doc : http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/MPF.html Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #11 from caulier.gil...@gmail.com --- The problem come from MPF Tags declared from group at Exiv2::tags.cpp::line 2166. Typically, if i try to resume: Exiv2::ExifKey(Exiv2::ExifData::Internal::mpfTagsList()) Generate the exception... Gilles -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373030] KConsole will get frozen if the CWD of one of its opened tab gets deleted
https://bugs.kde.org/show_bug.cgi?id=373030 --- Comment #9 from Eloi Gaudry--- I could reproduce the issue using what Edgmont said. Just create a new terminal then `mkdir test && cd test`, create a second tab then `cd test && rmdir test`, navigate back to first tab then create a new tab using keyboard shortcut : freeze. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373030] KConsole will get frozen if the CWD of one of its opened tab gets deleted
https://bugs.kde.org/show_bug.cgi?id=373030 --- Comment #8 from Kurt Hindenburg--- yes I've tried a lot of things - nothing crashes here - not sure if it shell I'm using or OS or distro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369413] Make it possible to have brushes bigger then 1000 pixels
https://bugs.kde.org/show_bug.cgi?id=369413 --- Comment #4 from Boudewijn Rempt--- I've added an option in the settings -- that's the easiest for now. It's now 10,000 hard max, but if you edit the kritarc file, you can add as many zeros as you want as long as you don't go beyond 2,147,483,647 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373030] KConsole will get frozen if the CWD of one of its opened tab gets deleted
https://bugs.kde.org/show_bug.cgi?id=373030 --- Comment #7 from Eloi Gaudry--- Version 16.08.2 I haven't been able to reproduce it again. I'm missing something in the initial conditions for this bug to happen. Have you checked what Edmont said ( (rmdir the working directory of a given tab, and then press Ctrl+Alt+T to open a new tab in this no longer existing directory.) )? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373030] KConsole will get frozen if the CWD of one of its opened tab gets deleted
https://bugs.kde.org/show_bug.cgi?id=373030 --- Comment #6 from Kurt Hindenburg--- What version is that? and I need more info about steps to reproduce or even a gif/video -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375841] New: Force close al seleccionar GTK2 ENGINE en KDE
https://bugs.kde.org/show_bug.cgi?id=375841 Bug ID: 375841 Summary: Force close al seleccionar GTK2 ENGINE en KDE Product: systemsettings Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sdanie...@gmail.com Target Milestone: --- Application: systemsettings5 (5.9.0) Qt Version: 5.8.0 Frameworks Version: 5.30.0 Operating System: Linux 4.9.6-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Por lo general antes no daba ningun fallo, pero fué instalar un complemento de Plasma, concretamente un plasmoid y dejar de funcionar. ¿Hay algun método para forzarlo? The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff8dbe6e5c0 (LWP 1092))] Thread 3 (Thread 0x7ff8bfdf5700 (LWP 1095)): #0 0x7ff8d1ca17bd in () at /usr/lib/libglib-2.0.so.0 #1 0x7ff8d1ca3c2b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d1ca46ab in () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d1ca489c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7ff8d849d46b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d8446c9a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d8268a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d8db7125 in () at /usr/lib/libQt5DBus.so.5 #8 0x7ff8d826d6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7ff8d3bc5454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7ff8d7b827df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7ff8c8274700 (LWP 1094)): #0 0x7ff8d7b7948d in poll () at /usr/lib/libc.so.6 #1 0x7ff8d44488e0 in () at /usr/lib/libxcb.so.1 #2 0x7ff8d444a679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7ff8ca7d8239 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7ff8d826d6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d3bc5454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff8d7b827df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7ff8dbe6e5c0 (LWP 1092)): [KCrash Handler] #6 0x7ff8d7acd04f in raise () at /usr/lib/libc.so.6 #7 0x7ff8d7ace47a in abort () at /usr/lib/libc.so.6 #8 0x7ff8d8253e21 in () at /usr/lib/libQt5Core.so.5 #9 0x7ff8d84720c5 in QObjectPrivate::QObjectPrivate(int) () at /usr/lib/libQt5Core.so.5 #10 0x7ff8a72f576e in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #11 0x7ff8a72e381e in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #12 0x7ff8a72f802d in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #13 0x7ff8da04b33b in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 #14 0x7ff8b6a49018 in () at /usr/lib/qt/plugins/kcm_style.so #15 0x7ff8b6a4bb11 in () at /usr/lib/qt/plugins/kcm_style.so #16 0x7ff8d8474149 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #17 0x7ff8da0da3b1 in QComboBox::activated(int) () at /usr/lib/libQt5Widgets.so.5 #18 0x7ff8da0dc80b in () at /usr/lib/libQt5Widgets.so.5 #19 0x7ff8da0df199 in () at /usr/lib/libQt5Widgets.so.5 #20 0x7ff8da0e41dd in () at /usr/lib/libQt5Widgets.so.5 #21 0x7ff8d8474149 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #22 0x7ff8da0dabb8 in () at /usr/lib/libQt5Widgets.so.5 #23 0x7ff8d84485a1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7ff8d9fdc325 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7ff8d9fe48c5 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7ff8d8448840 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x7ff8d9fe30cd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/libQt5Widgets.so.5 #28 0x7ff8da03e7f6 in () at /usr/lib/libQt5Widgets.so.5 #29 0x7ff8da040e03 in () at /usr/lib/libQt5Widgets.so.5 #30 0x7ff8d9fdc34c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #31 0x7ff8d9fe3b61 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #32 0x7ff8d8448840 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #33 0x7ff8d9847d53 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #34 0x7ff8d98498c5 in
[krita] [Bug 334123] Increase maximum brush size to 3k size
https://bugs.kde.org/show_bug.cgi?id=334123 Boudewijn Remptchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/85ec5a10916f4b5eefe36c14 ||272957154b49e4fb --- Comment #5 from Boudewijn Rempt --- Git commit 85ec5a10916f4b5eefe36c14272957154b49e4fb by Boudewijn Rempt. Committed on 01/02/2017 at 13:42. Pushed by rempt into branch 'master'. Related: bug 10, bug 000 Now users can set the maximum brush size to 10,000. The default is still 1,000 -- and trust me, a 10,000 pixel diameter brush is slow and takes a huge amount of memory. CCMAIL:kimages...@kde.org M +6-4 libs/image/brushengine/kis_standard_uniform_properties_factory.cpp M +5-0libs/ui/dialogs/kis_dlg_preferences.cc M +68 -38 libs/ui/forms/wdggeneralsettings.ui M +1-1libs/ui/kis_paintop_box.cc M +2-1plugins/paintops/dynadraw/kis_dyna_paintop_settings.cpp M +2-2plugins/paintops/dynadraw/kis_dynaop_option.cpp M +5-1plugins/paintops/libpaintop/kis_auto_brush_widget.cpp M +5-1plugins/paintops/libpaintop/kis_brush_chooser.cpp https://commits.kde.org/krita/85ec5a10916f4b5eefe36c14272957154b49e4fb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #10 from caulier.gil...@gmail.com --- Maik, I printed the tag name where the exception is generated : digikam.metaengine: Exif tag name: RelatedImageFileFormat digikam.metaengine: Exif tag name: RelatedImageWidth digikam.metaengine: Exif tag name: RelatedImageLength digikam.metaengine: Exif tag name: RelatedImageFileFormat digikam.metaengine: Exif tag name: RelatedImageWidth digikam.metaengine: Exif tag name: RelatedImageLength digikam.metaengine: Exif tag name: RelatedImageWidth digikam.metaengine: Exif tag name: RelatedImageLength digikam.metaengine: Exif tag name: RelatedImageLength digikam.metaengine: Exif tag name: MPFVersion digikam.metaengine: Cannot get Exif Tags list using Exiv2 (Error # 23 : Invalid ifdId 8 -- Makernote Tags - "MPFVersion" ... Gilles -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375840] MTP connection crashes after few minutes on several phones
https://bugs.kde.org/show_bug.cgi?id=375840 jmasponschanged: What|Removed |Added CC||joanmasp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375796] Barel Effect Apperaing on Images RAW RW2 Panasonic Format
https://bugs.kde.org/show_bug.cgi?id=375796 --- Comment #2 from Stephen Nixey--- Settings for Setup of Application was to Show the actual RAW Images and not a preview, looking at the images between different applications, it looks like the camera lense housing and the image is further back than the other applications show. The images is being shown from a different focal rectangle/region... If this makes sense? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #9 from caulier.gil...@gmail.com --- Arf... The error appear well with CLI tool. It's just too much verbose : -- Standard Exif Tags - digikam.metaengine: Cannot get Exif Tags list using Exiv2 (Error # 23 : Invalid ifdId 8 -- Makernote Tags - Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #8 from caulier.gil...@gmail.com --- I found the problem why Exif viewer list is empty. Exiv2 generate a C++ exception : Thread 1 "digikam" hit Breakpoint 7, Digikam::MetaEngine::getStdExifTagsList (this=0x7fffaa00) at /mnt/data/5.x/core/libs/dmetadata/metaengine_exif.cpp:1106 1106d->printExiv2ExceptionError(QString::fromLatin1("Cannot get Exif Tags list using Exiv2 "), e); (gdb) print e $51 = (Exiv2::Error &) @0x558fb50: { = {}, code_ = 23, count_ = 1, arg1_ = "8", arg2_ = "", arg3_ = "", msg_ = "Invalid ifdId 8"} ==> Invalid ifdId 8 This is strange because the code is exactly the same with CLI tool to print all Exiv2 know tags and the error do not appear. Gilles -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373269] Software Update notification incorrect
https://bugs.kde.org/show_bug.cgi?id=373269 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 372616 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 372616] Discover slow at showing available upgrades
https://bugs.kde.org/show_bug.cgi?id=372616 Aleix Polchanged: What|Removed |Added CC||xravengodgami...@gmail.com --- Comment #2 from Aleix Pol --- *** Bug 373269 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373269] Software Update notification incorrect
https://bugs.kde.org/show_bug.cgi?id=373269 Aleix Polchanged: What|Removed |Added CC||prote...@hotmail.it --- Comment #1 from Aleix Pol --- *** Bug 375311 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375311] unable to detect updates
https://bugs.kde.org/show_bug.cgi?id=375311 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 373269 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 364422] Resource size should include its dependencies
https://bugs.kde.org/show_bug.cgi?id=364422 Aleix Polchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Summary|size estimate off |Resource size should ||include its dependencies -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375830] Sending SIGINT to terminal breaks copying file name into a command
https://bugs.kde.org/show_bug.cgi?id=375830 --- Comment #1 from Wladimir Palant--- Created attachment 103749 --> https://bugs.kde.org/attachment.cgi?id=103749=edit Proposed patch This leaves clearing current command line as default behavior which is sane. However, this patch adds a parameter clearCommand to the sendInput() method to override this behavior. Inserting the file name and pasting are the scenarios where it is actually undesirable to clear the current command. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 372404] plasma-discover crashes on Kubuntu 16.10
https://bugs.kde.org/show_bug.cgi?id=372404 Aleix Polchanged: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #8 from Aleix Pol --- Seems like it's a problem with the graphics driver, not much we can do here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370362] Default user icon after installation differs from the one shown in user manager
https://bugs.kde.org/show_bug.cgi?id=370362 David Edmundsonchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit|http://commits.kde.org/kcor |https://commits.kde.org/pla |eaddons/70c745d6147e465ce1e |sma-desktop/52ba0122ebeb6aa |34b6037eb7dedb8e77f27 |21d23936d0fbef20f7d9f208f Status|REOPENED|RESOLVED --- Comment #3 from David Edmundson --- Git commit 52ba0122ebeb6aa21d23936d0fbef20f7d9f208f by David Edmundson. Committed on 01/02/2017 at 12:45. Pushed by davidedmundson into branch 'Plasma/5.9'. Use consistent default icon in UserManager and Kicker Summary: Both Kicker and UserManager when there is no icon set fallback to the icon "user-identity". However because we basically maintain two distinct icon themes for Plasma and not Plasma they ended up looking completely different as in the bug report. Reviewers: #plasma, hein Reviewed By: #plasma, hein Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D4249 M +1-0applets/kickoff/package/contents/ui/Header.qml https://commits.kde.org/plasma-desktop/52ba0122ebeb6aa21d23936d0fbef20f7d9f208f -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373123] Search won't produce any results
https://bugs.kde.org/show_bug.cgi?id=373123 Aleix Polchanged: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Aleix Pol --- Ask your distribution to provide good AppStream data. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373293] Make it possible to close the rightmost page
https://bugs.kde.org/show_bug.cgi?id=373293 Aleix Polchanged: What|Removed |Added CC||subd...@gmail.com --- Comment #6 from Aleix Pol --- *** Bug 370349 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370349] No way to go back from full Application description
https://bugs.kde.org/show_bug.cgi?id=370349 Aleix Polchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 373293 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375664] Cannot close preview pane
https://bugs.kde.org/show_bug.cgi?id=375664 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 373293 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373293] Make it possible to close the rightmost page
https://bugs.kde.org/show_bug.cgi?id=373293 Aleix Polchanged: What|Removed |Added CC||rula...@wp.pl --- Comment #5 from Aleix Pol --- *** Bug 375664 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375840] MTP connection crashes after few minutes on several phones
https://bugs.kde.org/show_bug.cgi?id=375840 Aleix Polchanged: What|Removed |Added CC||aleix...@kde.org --- Comment #1 from Aleix Pol --- How do you know it is crashing? Do you have a backtrace? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 314258] File sort order is not copied for duplicated tab
https://bugs.kde.org/show_bug.cgi?id=314258 --- Comment #2 from Wladimir Palant--- Created attachment 103748 --> https://bugs.kde.org/attachment.cgi?id=103748=edit Proposed patch Attached working patch, this will make sure to duplicate tab settings when a tab is duplicated. I'm not really familiar with the code but this seems to be the right way to do it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375840] New: MTP connection crashes after few minutes on several phones
https://bugs.kde.org/show_bug.cgi?id=375840 Bug ID: 375840 Summary: MTP connection crashes after few minutes on several phones Product: kio-extras Version: 5.9.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: default Assignee: plasma-de...@kde.org Reporter: t.ki...@gmail.com Target Milestone: --- MTP connection works only for few seconds, then gone crazy and still asks for allowe MTP connection in phone. Every time I connect phone with new Android (5,6,7), no matter what phone (LG G4, G5, Samsung Galaxy S7 EDGE...), the KDE connects it using MTP, then I allow the MTP connection in phone and everything seems OK BUT, after few minutes, the phone starts to call for allowing the MTP like crazy. This occurs mainly when I want to copy/write something using Dolphin from phone to computer. The same bug occurs in KDE NEON, Ubuntu 16.04 etc. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #7 from caulier.gil...@gmail.com --- Maik, I cleanup Exiv2 from trunk and recompiled all. Now the CLI test tool work as expected, but not the Setup/Metadata/View/Exif section... I continue to investiguate Gilles -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Stefan Lchanged: What|Removed |Added CC||stefan.loe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed
https://bugs.kde.org/show_bug.cgi?id=375839 Jacek Czajachanged: What|Removed |Added CC||jacek.cz...@intel.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375839] New: Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed
https://bugs.kde.org/show_bug.cgi?id=375839 Bug ID: 375839 Summary: Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed Product: valgrind Version: 3.12.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: jacek.cz...@intel.com Target Milestone: --- Created attachment 103747 --> https://bugs.kde.org/attachment.cgi?id=103747=edit output from GDB showing faulty instruction sequence + log from run valgrind I noticed a valgrind crash with error: "Temporary storage exhusted" in a case when there is long sequence(50+) of instructions: .. vfmadd231ps ymm0,ymm1,ymm2 vfmadd231ps ymm0,ymm1,ymm2 vfmadd231ps ymm0,ymm1,ymm2 vfmadd231ps ymm0,ymm1,ymm2 In attachment there is full crash message and sequence of instructions as seen in GDB (intel syntax) that made this crash happen. This sequence of instructions was created using JIt assembler xbyak (https://github.com/herumi/xbyak). I can attach linux project if needed. Notes: - valgrind was build from source (3.12) - commandline use: /bin/valgrind --tool=memcheck - Operating System: Fedora 21, uname -a: Linux linux-brix 3.14.5 #1 SMP Fri Mar 13 16:27:51 CET 2015 x86_64 x86_64 x86_64 GNU/Linux - without valgrind program works fine ,( does nothing as it was modified for exploiting this problem) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375838] New: Crash when copying large data to clipboard
https://bugs.kde.org/show_bug.cgi?id=375838 Bug ID: 375838 Summary: Crash when copying large data to clipboard Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde@netpage.dk CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-59-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: When using the IntelliJ IDE, opening a large XML file (~16MB) with syntax highlighting enabled and then copying it to the clipboard (Ctrl+C), Plasma crashes. After restarting Plasma, when opening the menu/history of the Clipboard widget it crashes again. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6878e6c8c0 (LWP 27020))] Thread 13 (Thread 0x7f67909ad700 (LWP 28934)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6873c7ba5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x18ae6a0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0x2c4a568, mutex=mutex@entry=0x2c4a560, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f6876f1992e in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x2c4a558) at scenegraph/qsgthreadedrenderloop.cpp:224 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2c4a4e0) at scenegraph/qsgthreadedrenderloop.cpp:657 #5 0x7f6876f1a1b3 in QSGRenderThread::run (this=0x2c4a4e0) at scenegraph/qsgthreadedrenderloop.cpp:686 #6 0x7f6873c7a7be in QThreadPrivate::start (arg=0x2c4a4e0) at thread/qthread_unix.cpp:331 #7 0x7f6872d676ba in start_thread (arg=0x7f67909ad700) at pthread_create.c:333 #8 0x7f687359082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f677fffe700 (LWP 27154)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6873c7ba5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2a91a60) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0x2a3cb08, mutex=mutex@entry=0x2a3cb00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f6876f1992e in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x2a3caf8) at scenegraph/qsgthreadedrenderloop.cpp:224 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2a3ca80) at scenegraph/qsgthreadedrenderloop.cpp:657 #5 0x7f6876f1a1b3 in QSGRenderThread::run (this=0x2a3ca80) at scenegraph/qsgthreadedrenderloop.cpp:686 #6 0x7f6873c7a7be in QThreadPrivate::start (arg=0x2a3ca80) at thread/qthread_unix.cpp:331 #7 0x7f6872d676ba in start_thread (arg=0x7f677fffe700) at pthread_create.c:333 #8 0x7f687359082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f67969ce700 (LWP 27060)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6873c7ba5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2286230) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0x1b87c38, mutex=mutex@entry=0x1b87c30, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f6876f1992e in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x1b87c28) at scenegraph/qsgthreadedrenderloop.cpp:224 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x1b87bb0) at scenegraph/qsgthreadedrenderloop.cpp:657 #5 0x7f6876f1a1b3 in QSGRenderThread::run (this=0x1b87bb0) at scenegraph/qsgthreadedrenderloop.cpp:686 #6 0x7f6873c7a7be in QThreadPrivate::start (arg=0x1b87bb0) at thread/qthread_unix.cpp:331 #7 0x7f6872d676ba in start_thread (arg=0x7f67969ce700) at pthread_create.c:333 #8 0x7f687359082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f6797dcf700 (LWP 27059)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6873c7ba5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1b719b0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0xaac918, mutex=mutex@entry=0xaac910, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f6876f1992e in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0xaac908) at
[kdesvn] [Bug 375837] New: misstyped word
https://bugs.kde.org/show_bug.cgi?id=375837 Bug ID: 375837 Summary: misstyped word Product: kdesvn Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: General Assignee: kdesvn-bugs-n...@kde.org Reporter: amelyanovich.vladi...@gmail.com Target Milestone: --- Created attachment 103746 --> https://bugs.kde.org/attachment.cgi?id=103746=edit misstyped word В настройках. Настройки -> Configure Kdesvn -> Сравнение и слияние В пунктах меню вместо "Сравнение" написано "Сревнение" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375836] New: Plasma crashed during idle time
https://bugs.kde.org/show_bug.cgi?id=375836 Bug ID: 375836 Summary: Plasma crashed during idle time Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andreus...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Just nothing. Computer was idle. Computer wasn't locked. I have a laptop connected with additional monitor. When bug happened, Laptop monitor was blacked out and didn't turn on -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f77461f5900 (LWP 2202))] Thread 18 (Thread 0x7f36477ff700 (LWP 4772)): #0 0x7f773f91c49d in poll () at /lib64/libc.so.6 #1 0x7f77355b00a1 in () at /usr/lib64/libpulse.so.0 #2 0x7f77355a176c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f77355a1dde in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f77355a1e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f77355b0006 in () at /usr/lib64/libpulse.so.0 #6 0x7f7734f47408 in () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7f773f125734 in start_thread () at /lib64/libpthread.so.0 #8 0x7f773f924d3d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f7664e83700 (LWP 4771)): #0 0x7f773bfe177b in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f773bfe3d43 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f773bfe42a8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f773bfe442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f774022332b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f77401d0fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f774000bf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f77433179c8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f77400109e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f773f125734 in start_thread () at /lib64/libpthread.so.0 #10 0x7f773f924d3d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f76657fa700 (LWP 2897)): #0 0x7f773f12a0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f774001165b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7685eb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7685eb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7685eaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7685eb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7685eaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7685eb2a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f77400109e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f773f125734 in start_thread () at /lib64/libpthread.so.0 #10 0x7f773f924d3d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f7665ffb700 (LWP 2896)): #0 0x7f773f12a0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f774001165b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7685eb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7685eb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7685eaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7685eb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7685eaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7685eb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f7685eaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f7685eb2a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f77400109e9 in () at /usr/lib64/libQt5Core.so.5 #11 0x7f773f125734 in start_thread () at /lib64/libpthread.so.0 #12 0x7f773f924d3d in clone () at
[kmail2] [Bug 368963] Freeze on send confirmation after spell check dialog.
https://bugs.kde.org/show_bug.cgi?id=368963 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- (In reply to L33tCh from comment #2) > Same problem my side. I jsut tested a spell check before sending it even > happens then. It's not an every time event though... Once or twice it has > done a spell check and completed and sent successfully so I will try to keep > track of what I do each time and hopefully narrow down the exact replication > steps. Which version ? I fixed in 5.4.0 Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 Fredrik Höglundchanged: What|Removed |Added CC|fred...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375835] New: Gets very confused with "⌛" and probably other unicode symbols
https://bugs.kde.org/show_bug.cgi?id=375835 Bug ID: 375835 Summary: Gets very confused with "⌛" and probably other unicode symbols Product: konsole Version: 16.12.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: tipos...@tiscali.it Target Milestone: --- If I paste the symbol "⌛" in a terminal, it gets very confused. For example, if I then pres "home" and hit space several times, the spaces will not appear and that symbol will not move. However after running the command, the command in the bash history will actually contain the spaces. Deleting the spaces will duplicate the symbol in their stead. Also, after pasting, selecting it, it looks like it's selected but normally something else is actually selected and goes in the selection buffer. I suppose other unicode symbols create the same issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 375610] Dolphin doesn't correctly show directories on a ftp server
https://bugs.kde.org/show_bug.cgi?id=375610 David Faurechanged: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kio ||/b158255bd590eb333e22526614 ||b1a72611402b6a Version Fixed In||5.31 Resolution|--- |FIXED --- Comment #4 from David Faure --- Git commit b158255bd590eb333e22526614b1a72611402b6a by David Faure, on behalf of Marco Scarpetta. Committed on 01/02/2017 at 11:25. Pushed by dfaure into branch 'master'. Fix parsing of directories listing on a specific ftp server Directories listing on ftp servers like ftp://ftp-dee.poliba.it/ are now parsed correctly. REVIEW: 129905 FIXED-IN: 5.31 M +13 -2src/ioslaves/ftp/ftp.cpp https://commits.kde.org/kio/b158255bd590eb333e22526614b1a72611402b6a -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 195749] Ctrl+Tab don't switch over edited files
https://bugs.kde.org/show_bug.cgi?id=195749 --- Comment #2 from Wladimir Palant--- This issue is still reproducible with my build from Git master (Krusader 2.5.1-beta, revision 5056272). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375834] Missing shared libray for akregator
https://bugs.kde.org/show_bug.cgi?id=375834 Laurent Bonnaudchanged: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 195749] Ctrl+Tab don't switch over edited files
https://bugs.kde.org/show_bug.cgi?id=195749 Wladimir Palantchanged: What|Removed |Added CC||ppk...@palant.de --- Comment #1 from Wladimir Palant --- *** Bug 375797 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375834] New: Missing shared libray for akregator
https://bugs.kde.org/show_bug.cgi?id=375834 Bug ID: 375834 Summary: Missing shared libray for akregator Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: l.bonn...@laposte.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Hi, I updated my system with latest neon packages and akregator non longer starts: $ akregator akregator: error while loading shared libraries: libQt5WebEngineWidgets.so.5: cannot open shared object file: No such file or directory Here are version details: Package: akregator Version: 4:16.12.1+p16.04+git20170131.0101-0 Versions of packages akregator depends on: ii kinit5.30.0+p16.04+git20170117.0646-0 ii kio 5.30.0+p16.04+git20170124.2027-0 ii libc62.24-3ubuntu2 ii libgcc1 1:6.2.0-5ubuntu12 ii libkf5codecs55.30.0+p16.04+git20170124.1611-0 ii libkf5completion55.30.0+p16.04+git20170124.1718-0 ii libkf5configcore55.30.0+p16.04+git20170124.1622-0 ii libkf5configgui5 5.30.0+p16.04+git20170124.1622-0 ii libkf5configwidgets5 5.30.0+p16.04+git20170130.0235-0 ii libkf5coreaddons55.30.1+p16.04+git20170131.0605-0 ii libkf5crash5 5.30.0+p16.04+git20170124.1737-0 ii libkf5grantleetheme5 16.12.1+p16.04+git20170118.0618-0 ii libkf5i18n5 5.30.0+p16.04+git20170116.2337-0 ii libkf5iconthemes55.30.0+p16.04+git20170118.0540-0 ii libkf5jobwidgets55.30.0+p16.04+git20170118.0541-0 ii libkf5kcmutils5 5.30.0+p16.04+git20170124.2228-0 ii libkf5kiocore5 5.30.0+p16.04+git20170124.2027-0 ii libkf5kiogui55.30.0+p16.04+git20170124.2027-0 ii libkf5kiowidgets55.30.0+p16.04+git20170124.2027-0 ii libkf5kontactinterface5 16.12.1+p16.04+git20170127.0227-0 ii libkf5libkdepim5 4:16.12.1+p16.04+git20170125.0238-0 ii libkf5messageviewer5 4:16.12.1+p16.04+git20170131.0921-0 ii libkf5mimetreeparser54:16.12.1+p16.04+git20170131.0921-0 ii libkf5notifications5 5.30.0+p16.04+git20170123.0229-0 ii libkf5notifyconfig5 5.30.0+p16.04+git20170124.2206-0 ii libkf5parts5 5.30.0+p16.04+git20170130.1313-0 ii libkf5pimcommon5 4:16.12.1+p16.04+git20170131.0845-0 ii libkf5pimtextedit5 16.12.1+p16.04+git20170125.0204-0 ii libkf5service5 5.30.0+p16.04+git20170118.0554-0 ii libkf5syndication5 16.12.1+p16.04+git20170118.0652-0 ii libkf5textwidgets5 5.30.0+p16.04+git20170124.1754-0 ii libkf5webengineviewer5 4:16.12.1+p16.04+git20170131.0921-0 ii libkf5widgetsaddons5 5.30.0+p16.04+git20170131.0616-0 ii libkf5xmlgui55.30.0+p16.04+git20170124.1810-0 ii libqt5core5a 5.7.1+dfsg-3+16.04+build5 ii libqt5dbus5 5.7.1+dfsg-3+16.04+build5 ii libqt5gui5 5.7.1+dfsg-3+16.04+build5 ii libqt5network5 5.7.1+dfsg-3+16.04+build5 ii libqt5webengine5 5.7.1+dfsg-2+16.04+build14 ii libqt5widgets5 5.7.1+dfsg-3+16.04+build5 ii libqt5xml5 5.7.1+dfsg-3+16.04+build5 ii libstdc++6 6.2.0-5ubuntu12 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375797] Pressing Ctrl+Tab in editor inserts a tab instead of switching tabs
https://bugs.kde.org/show_bug.cgi?id=375797 Wladimir Palantchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Wladimir Palant --- *** This bug has been marked as a duplicate of bug 195749 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375831] Sorting by file extension should put empty extensions first
https://bugs.kde.org/show_bug.cgi?id=375831 --- Comment #1 from Wladimir Palant--- Created attachment 103745 --> https://bugs.kde.org/attachment.cgi?id=103745=edit Proposed patch Here is a fix for this issue. Note that it is treating the case where both strings are equal specially, this is for consistency with the logic at the bottom of compareTextsAlphabetical() and compareTextsCharacterCode(). I don't see a difference if I leave out this case but if it is important then personally I would have written this differently: > if (aS2.length() == 0) { > return false; > } else if (aS1.length() == 0) { > return true; > } The checks in compareTextsAlphabetical() can be simplified similarly: > if (lPositionS2 == aS2.length()) return false; > else if (lPositionS1 == aS1.length()) return true; These two comparisons produce the same result as the six comparisons currently there. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!
https://bugs.kde.org/show_bug.cgi?id=358392 k...@douglasmcmillan.com changed: What|Removed |Added CC||k...@douglasmcmillan.com --- Comment #17 from k...@douglasmcmillan.com --- I'm still getting this behaviour in Kubuntu 16.04. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 375833] New: Flickr export converts all images to JPEG
https://bugs.kde.org/show_bug.cgi?id=375833 Bug ID: 375833 Summary: Flickr export converts all images to JPEG Product: kipiplugins Version: 5.5.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- The Flickr exporter converts all images to JPEG before uploading even when [Resize photos before uploading] is unchecked. For every export the Digikam console reports 'resized and saved to a temp file'. This is a problem for Animated GIF which is uploaded as a static JPG. For JPG this is also not ideal because the exported file is no longer bitwise identical to the source file, the checksums and filesizes of the uploaded files will not match the source files. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375540] Seg fault on startup
https://bugs.kde.org/show_bug.cgi?id=375540 --- Comment #2 from Norman--- On Saturday, 28 January 2017 19:10:00 GMT you wrote: > https://bugs.kde.org/show_bug.cgi?id=375540 > > Martin Sandsmark changed: > >What|Removed |Added > > CC||martin.sandsm...@kde.org > > --- Comment #1 from Martin Sandsmark --- > Can you run it in gdb and get a stacktrace? > > https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces gdb run typescript attached -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375832] New: System Settings crash after entering in Application Style
https://bugs.kde.org/show_bug.cgi?id=375832 Bug ID: 375832 Summary: System Settings crash after entering in Application Style Product: systemsettings Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: antonio.cas...@pernambucanas.com.br Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.6-200.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: I accessed Sytem Settings > Application Style and tried to go back to all settings The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4970628900 (LWP 6402))] Thread 6 (Thread 0x7f491a7fc700 (LWP 6460)): #0 0x7f497505c719 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #1 0x7f497505d07b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f497505d26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f497cfd173b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f497cf8273a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f497cddf5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f497b9a34e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f497cde39da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f49792a16ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f497c1d6f7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f495149b700 (LWP 6417)): #0 0x7f497cde2911 in QThreadData::current(bool) () at /lib64/libQt5Core.so.5 #1 0x7f497cfd15da in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f497505c699 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7f497505d07b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f497505d26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f497cfd173b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f497cf8273a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f497cddf5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f497cde39da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f49792a16ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f497c1d6f7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4953427700 (LWP 6412)): #0 0x7f497505d0e2 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #1 0x7f497505d26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #2 0x7f497cfd173b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f497cf8273a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f497cddf5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f497cde39da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7f49792a16ca in start_thread () at /lib64/libpthread.so.0 #7 0x7f497c1d6f7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f495d490700 (LWP 6405)): #0 0x7f497c1cb01d in poll () at /lib64/libc.so.6 #1 0x7f497505d156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f497505d26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f497cfd173b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f497cf8273a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f497cddf5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f497d6ce739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f497cde39da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f49792a16ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f497c1d6f7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f49652db700 (LWP 6404)): #0 0x7f497c1cb01d in poll () at /lib64/libc.so.6 #1 0x7f49798e0d10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f49798e2aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f49699a5d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f497cde39da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f49792a16ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f497c1d6f7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4970628900 (LWP 6402)): [KCrash Handler] #6 0x7f497b875b95 in QV4::WeakValue::free() () at /lib64/libQt5Qml.so.5 #7 0x7f497b8e6912 in
[krusader] [Bug 375831] New: Sorting by file extension should put empty extensions first
https://bugs.kde.org/show_bug.cgi?id=375831 Bug ID: 375831 Summary: Sorting by file extension should put empty extensions first Product: krusader Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: ppk...@palant.de Target Milestone: --- I'm using Krusader built from Git master (2.5.1-beta, revision 5056272) on Ubuntu 16.04. When files are sorted by file extension, files with empty file extension are placed last - this is unexpected and doesn't seem to be the intended behavior. Steps to reproduce: 1. Create files with names "foo" and "bar.txt" in the same directory. 2. Click Ext column header to sort by file extension in ascending order. Expected results: The file "foo" is listed before "bar.txt" because "" is smaller than "txt". Actual results: The file "foo" is listed after "bar.txt", function compareTexts() in krsort.cpp treats empty strings as larger than non-empty strings. This is independent of sort method chosen, and also inconsistent given that "foo.tx" is correctly listed before "bar.txt" (shorter is generally smaller). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375769] Mouse wheel over activity pager does not switch activity
https://bugs.kde.org/show_bug.cgi?id=375769 Eike Heinchanged: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/fff65ad696f4dc3 ||4391a0e9eb4b9ef0ed09a9c42 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Eike Hein --- Git commit fff65ad696f4dc34391a0e9eb4b9ef0ed09a9c42 by Eike Hein. Committed on 01/02/2017 at 10:47. Pushed by hein into branch 'Plasma/5.8'. Revamp (Activity) Pager wheel handling Summary: Fixes the mouse wheel not working to switch activities by refactoring the code so currentPage() always behaves the same and accounting for virt desktops starting at 1 only where it actually counts, then fixing an off-by-one along the way. Also introduces the wheel event handling logic used in Task Manager and many other UIs to avoid reacting overly sensitively to gesture scroll events from trackpads. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D4360 M +28 -6applets/pager/package/contents/ui/main.qml M +8-9applets/pager/plugin/pagermodel.cpp M +1-1applets/pager/plugin/pagermodel.h https://commits.kde.org/plasma-desktop/fff65ad696f4dc34391a0e9eb4b9ef0ed09a9c42 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #6 from caulier.gil...@gmail.com --- Maik, We have a test code in digiKam core named "printtagslist" which print all Exif, Iptc, and XMP tags know by Exiv2 with description on the console. I can reproduce the dysfunction with 0.26, but not with 0.25. 2 solutions : 1/ the bug is in Exiv2 ==> UPSTREAM 2/ the code must be adapted in dmetadata to work fine with 0.26 due to API changes (perhaps). If it's the case, why old Exiv2 API is not annotated as deprecated ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373030] KConsole will get frozen if the CWD of one of its opened tab gets deleted
https://bugs.kde.org/show_bug.cgi?id=373030 --- Comment #5 from Eloi Gaudry--- Sorry to say so, but I have been able to reproduce it now and up-to-date Leap-42.2 OS. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374296] late-16.12.0 - with plasma-5.8.5 "Ctrl-O" doesn't open the folder of the current opened file
https://bugs.kde.org/show_bug.cgi?id=374296 boo...@center-erm.net changed: What|Removed |Added CC||boo...@center-erm.net --- Comment #1 from boo...@center-erm.net --- I have this BUG too and it is really annoying - open command on any file opened remotely via sftp://, fish://, ... did previously open the same location and now it opens home folder. Open on local files works ok. OpenSuse Tumbleweed + Plasma 5.8.5 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 314258] File sort order is not copied for duplicated tab
https://bugs.kde.org/show_bug.cgi?id=314258 --- Comment #1 from Wladimir Palant--- This is still an issue with the current Git master (2.5.1-beta, revision 5056272). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 375610] Dolphin doesn't correctly show directories on a ftp server
https://bugs.kde.org/show_bug.cgi?id=375610 --- Comment #3 from David Faure--- For reference: https://git.reviewboard.kde.org/r/129905/ (thanks!) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 314258] File sort order is not copied for duplicated tab
https://bugs.kde.org/show_bug.cgi?id=314258 Wladimir Palantchanged: What|Removed |Added CC||ppk...@palant.de -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 328068] Automatic sending chdir to embedded terminal may lead to tragic consequences if some command is already typed.
https://bugs.kde.org/show_bug.cgi?id=328068 Wladimir Palantchanged: What|Removed |Added CC||ppk...@palant.de --- Comment #3 from Wladimir Palant --- I filed bug 375830 on a regression that this caused. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375830] New: Sending SIGINT to terminal breaks copying file name into a command
https://bugs.kde.org/show_bug.cgi?id=375830 Bug ID: 375830 Summary: Sending SIGINT to terminal breaks copying file name into a command Product: krusader Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: ppk...@palant.de Target Milestone: --- I am using Krusader compiled from master (revision 5056272) on Ubuntu 16.04 - so the fix for bug 328068 is included. This has a side-effect that copying file name to the embedded terminal is essentially broken: 1. Make sure that embedded terminal enabled but not the command line. 2. Select some file. 3. Switch to the embedded terminal and start typing a command: "ls -l" 4. Now press Ctrl+Enter to copy the file name. Expected results: The file name is added to the command and you get something like "ls -l 'foo'" Actual results: The command line is cleared by SIGINT and you get only the file name on a new line. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 373119] QFileDialog sends messages to standard out
https://bugs.kde.org/show_bug.cgi?id=373119 Elvis Stansvikchanged: What|Removed |Added CC||elvst...@gmail.com --- Comment #4 from Elvis Stansvik --- I'm running into this issue with our product on Ubuntu 16.04 as well (KF5 5.18.0 and Qt 5.5.1), though we're only getting the "Invalid URL: QUrl("blahblah")" messages. Our QFileDialog is configured and shown as follows: QFileDialog *dialog = new QFileDialog(this, "Select CSV File Name"); dialog->setModal(true); dialog->setNameFilter("CSV Files (*.csv)"); dialog->setDirectory(QFileInfo(outputFileEdit->text()).dir()); dialog->setLabelText(QFileDialog::Accept, "OK"); dialog->setAttribute(Qt::WA_DeleteOnClose); dialog->setFileMode(QFileDialog::AnyFile); dialog->setAcceptMode(QFileDialog::AcceptSave); dialog->selectFile(outputFileEdit->text()); connect(dialog, ::fileSelected, outputFileEdit, ::setText); dialog->show(); Since we're initially targeting Ubuntu 16.04 exclusively with this product (and using the packaged versions of KF5 and Qt), does anyone know if there's a workaround to quench the messages? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375797] Pressing Ctrl+Tab in editor inserts a tab instead of switching tabs
https://bugs.kde.org/show_bug.cgi?id=375797 Wladimir Palantchanged: What|Removed |Added Version|2.5.0 |Git --- Comment #4 from Wladimir Palant --- In fact, I just built from master (revision 5056272) and I can still reproduce. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375761] [Wacom] Pressure Sensitivity Not Working (only for Krita) 3.1.1
https://bugs.kde.org/show_bug.cgi?id=375761 --- Comment #5 from Boudewijn Rempt--- Nope. Krita Gemini also uses the wintab api. The big difference is that Gemini doesn't ask for the tablet name. There are some other changes. BUT: Krita works with wacom tablets for hundreds of thousands of people, including the developers. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375633] Two buttons in Map tab on the Right Sidebar are not working
https://bugs.kde.org/show_bug.cgi?id=375633 --- Comment #12 from caulier.gil...@gmail.com --- Git commit 8b19ee7daf20c1e8c28d433bec6d013986e108f4 by Gilles Caulier. Committed on 01/02/2017 at 09:12. Pushed by cgilles into branch 'master'. fix wrong path in AppImage run bash script to handle Qt5 plugins. This must fix the XCB integration error when an url request is passed to QDesktopService. Related: bug 375808 M +1-1project/bundles/appimage/data/AppRun https://commits.kde.org/digikam-software-compilation/8b19ee7daf20c1e8c28d433bec6d013986e108f4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375808] Submit bug report is not working
https://bugs.kde.org/show_bug.cgi?id=375808 --- Comment #1 from caulier.gil...@gmail.com --- Git commit 8b19ee7daf20c1e8c28d433bec6d013986e108f4 by Gilles Caulier. Committed on 01/02/2017 at 09:12. Pushed by cgilles into branch 'master'. fix wrong path in AppImage run bash script to handle Qt5 plugins. This must fix the XCB integration error when an url request is passed to QDesktopService. Related: bug 375633 M +1-1project/bundles/appimage/data/AppRun https://commits.kde.org/digikam-software-compilation/8b19ee7daf20c1e8c28d433bec6d013986e108f4 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375797] Pressing Ctrl+Tab in editor inserts a tab instead of switching tabs
https://bugs.kde.org/show_bug.cgi?id=375797 Toni Asensi Estevechanged: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #3 from Toni Asensi Esteve --- As strange as it may seem: the bug is seen if, for example, Kubuntu 16.04 is used. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375829] New: "Custom Makefiles" not availble if import existing makefile project
https://bugs.kde.org/show_bug.cgi?id=375829 Bug ID: 375829 Summary: "Custom Makefiles" not availble if import existing makefile project Product: kdevelop Version: 5.0.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: Custom Makefiles Assignee: kdevelop-bugs-n...@kde.org Reporter: charles.gorand@gmail.com Target Milestone: --- My projects have the following file tree : myproject/make/ : contains custom makefiles myproject/src/ : contains source code If I import this kind of project, "Custom Makefiles" in Project manager is not available. It looks this option is only available if I select a folder where there is a makefile. In kdevelop 4, this issue does not exists. I workaround this issue by editing .kdev4 project file and change "Manager=KDevCustomMakeManager" Step to reproduce : - "Open/Import project" - Select a project where makefile is not at the root of the project - In Manager : "Custom Makefiles" is not available. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 375577] Kontact crashed after opening a contact
https://bugs.kde.org/show_bug.cgi?id=375577 Robby Engelmannchanged: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #2 from Robby Engelmann --- Done: https://bugreports.qt.io/browse/QTBUG-58565 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #16 from Marco Martin--- (In reply to Thomas Weissel from comment #15) > unfortunately nothing changed ! It didn't make into 5.9.0, should be in 5.9.1 -- You are receiving this mail because: You are watching all bug changes.