[i18n] [Bug 362024] A few strange translations in Apper/pkupdates
https://bugs.kde.org/show_bug.cgi?id=362024 Lasse Liehu changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 362024] New: A few strange translations in Apper/pkupdates
https://bugs.kde.org/show_bug.cgi?id=362024 Bug ID: 362024 Summary: A few strange translations in Apper/pkupdates Product: i18n Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: fi Assignee: lasse.li...@gmail.com Reporter: lasse.li...@gmail.com CC: kim.enkova...@iki.fi Note: The following is in Finnish and meant for Finnish translators. Viestit: "Turvaluottamussuhdetta ei ole Turvaluottamussuhdetta ei voitu luoda ohjelmiston alkuperään." ja "Tarkista ohjelmiston allekirjoitusasetukset." "kontekstina tuo tulee kun packages.gz:n hash ei täsmää (täällä on joku todella ilmiselvä liikenteenurkintajärjestelmä)" Alustavalla haulla viestit löytyi apper.po:sta ja pkupdates.po:sta, mutta katso vielä uudelleen korjattaessa. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362023] Extremely slow metadata writing via maintenance
https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #1 from Simon --- Created attachment 98490 --> https://bugs.kde.org/attachment.cgi?id=98490&action=edit Command line output of writing metadata to files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362023] New: Extremely slow metadata writing via maintenance
https://bugs.kde.org/show_bug.cgi?id=362023 Bug ID: 362023 Summary: Extremely slow metadata writing via maintenance Product: digikam Version: 5.0.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com I am writing tags that previously only existed in (sqlite) database to image metadata via the maintenance tool. This takes an enormous amount of time, I am currently at 10% after 3 days continuously running. The bottleneck is (obviously) disk io. Still this should take much less time (exiftool took about 3h to delete old tags of the same collection). The collection contains 100'000 items and probably about half of them are to be tagged. What looks odd to me is, that throughout the process digikam.general reports that QFileSystemWatcher detected change in the folder that is currently written to by the metadata write. The occurrence of this is also not regular and at a fixed position within the log entries from writing metadata to tags, which suggest to me that the two things are separate. As it is digikam that is writing to these folders and not an external programs, are these scans really necessary? And if they are, can they be delayed till the maintenance tool finished writing to a directory. I do not see an option to attach something. I will get a partial log into this bug report as soon as I found out how (or use a pastebin). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 362008] Taking too long to open, "I Forgot my Password" link.
https://bugs.kde.org/show_bug.cgi?id=362008 Ben Cooksley changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED CC||bcooks...@kde.org Ever confirmed|0 |1 --- Comment #2 from Ben Cooksley --- As far as I can tell, Identity is performing perfectly fine. If you are using IPv6 please disable it, it is likely your IPv6 provider is faulty in regards to working with Incapsula - who currently frontend cdn.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361325] shortcut schemes broken again
https://bugs.kde.org/show_bug.cgi?id=361325 Raghavendra kamath changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Raghavendra kamath --- All my problems stated in thsi bug report are fixed commit solving file extension for shortcuts-> https://quickgit.kde.org/?p=krita.git&a=commit&h=5bd8323f83f14d2e1e5db8c770b37558392ad52d shortcuts can now be loaded and the shortcut are retained on restart. I am closing this bug , if anything crops up we can open a new one as for now all problems seem fixed thanks Boud and Michael for fixing things :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360595] Krita crashes when we cancel the save custom shortcut dialog box
https://bugs.kde.org/show_bug.cgi?id=360595 Raghavendra kamath changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Raghavendra kamath --- This bug is gone for me now , michael fixed it by this commit -> https://quickgit.kde.org/?p=krita.git&a=commit&h=bf2f2092b648b15f9ffccb0fc7cb68a8900a5d80 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362022] New: Krita 3.0 don't render this *.kra file from 2.9 correctly: vector-layer scaling is wrong
https://bugs.kde.org/show_bug.cgi?id=362022 Bug ID: 362022 Summary: Krita 3.0 don't render this *.kra file from 2.9 correctly: vector-layer scaling is wrong Product: krita Version: 3.0 Alpha Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Vector Objects and Tools Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Hi, I found a *.kra file with different rendering between 2.9 and 3.0, 100% reproductible. It's mainly about my comic frame, done with basic square shapes on a vector layer. The scaling is wrong when I open the file in 3.0. I attach screenshot and the culprit file under: ✩ https://share.kde.org/index.php/s/0iFENaRtXEAzO7K [ PNG screenshot image : rendering in 2.9 ] ✩ https://share.kde.org/index.php/s/jQ9txcwIA4foHXO [ PNG screenshot image : rendering in 3.0 ] ✩ https://share.kde.org/index.php/s/1LUoIHw7tMu9UeT [ ZIP, *.kra file inside : to reproduce the bug. ] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 362021] New: screenlocker dispaying current desktop
https://bugs.kde.org/show_bug.cgi?id=362021 Bug ID: 362021 Summary: screenlocker dispaying current desktop Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: haar...@gmail.com A locker that only shows the active desktop but disable mouse input except but temporarily displaying an unlock window when input is detected. This can be used if no input is required or allowed but the display needs to be shown (example show case laptop etc) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #56 from wolfyrion --- some more investigation... 1. ALL opengl games/applications disable compositor but actually some of them break kwin compositor. 2. if I use the org.kde.oxygen decoration it doesnt give me any artifacts 3. After opening a game or application that it will break the compositor even when the compositor is enabled. When the compositor/kwin is breaks what ever I open after it creates black squares all over the screen Image http://i.imgur.com/5gH0ZAv.png ( I cant find any attachment button when I post any bug so I am using imgur) 4. I have noticed that when a game breaks KWIN compositor it seems that VSYNC is messed up because I can see a lot of tearing issues in the game when the compositor is messed up. Dont know if that is because NVIDIA or KWIN but it seems like they have a conflict somewhere 5. In order to fix this problem I had to install another compositor like for example compiz. So whenever a game or an application breaks the compositor I just enable compiz for a sec and then activate again KWIN compositor and I am back to normal. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 --- Comment #10 from Martin Gräßlin --- sorry kscreenlocker is not yet in a quality from library point of view that we can ensure it's properly so-bumped. It doesn't follow any library guidelines, no d-ptr, etc. etc. kscreenlocker is part of Plasma and used in plasma-workspace and KWin. Those products release together and need to be updated in lock-step anyway. If distributions cannot ensure that those get updated together, please so-bump kscreenlocker manually. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #5 from Laurent Montel --- could you try to add birthday resource ? I tried to make it crash but not success yet -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday
https://bugs.kde.org/show_bug.cgi?id=358106 --- Comment #6 from sparhawk --- Huh, very strange. I wonder if those locale files are distro specific. Seems unlikely, but possible. FWIW I wouldn't hold my breath for a quick fix. I think my hit-rate is something like 5% for even getting a dev to respond here, let alone fix it! -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 362020] Login session changes upon installing Kodi
https://bugs.kde.org/show_bug.cgi?id=362020 --- Comment #1 from hagen@gmail.com --- Some additional system information: KDE Plasma Version: 5.5.5 QT Version: 5.5.1 Kernal Version 4.4.0-21-generic -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 362020] Login session changes upon installing Kodi
https://bugs.kde.org/show_bug.cgi?id=362020 hagen@gmail.com changed: What|Removed |Added Platform|Other |Kubuntu Packages CC||hagen@gmail.com Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 362020] New: Login session changes upon installing Kodi
https://bugs.kde.org/show_bug.cgi?id=362020 Bug ID: 362020 Summary: Login session changes upon installing Kodi Product: plasma4 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hagen@gmail.com I'm running Kubuntu 16.04 AMD64 and am running into an interesting situation when I install Kodi. Upon installation, the Auto Login session changes from "Plasma" to "Kodi." It's easy enough to change it back but I assume this shouldn't be the case. This change can lead the operating system to hang on the next startup. Reproducible: Always Steps to Reproduce: 1. Activate Auto Login 2. sudo apt-get install kodi 3. Check Auto Login details under System Settings > Startup and Shutdown > Login Screen > Advanced Actual Results: Autologin Session switched from "Plasma" to "Kodi" Expected Results: I would have expected the installation of Kodi not to alter the auto login session. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.
https://bugs.kde.org/show_bug.cgi?id=303877 --- Comment #38 from Ivo Raisr --- Dilyan Palauzov reports duplicate line in configure.ac: AC_CHECK_TYPES([Elf32_Chdr, Elf64_Chdr], [], [], [[#include ]]) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 --- Comment #4 from Ivo Raisr --- You are right, Philippe, that's very good remark. I have attached new patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added Attachment #98481|0 |1 is obsolete|| --- Comment #3 from Ivo Raisr --- Created attachment 98489 --> https://bugs.kde.org/attachment.cgi?id=98489&action=edit proposed patch v2 Addresses Philippe's comment. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354848] file association loophole: application automatically as default, even if i delete it from the list
https://bugs.kde.org/show_bug.cgi?id=354848 150...@mail.ru changed: What|Removed |Added CC||150...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362019] New: Freeze when click 'show uses' of functions or macros
https://bugs.kde.org/show_bug.cgi?id=362019 Bug ID: 362019 Summary: Freeze when click 'show uses' of functions or macros Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: huangkai950...@gmail.com The whole UI would freeze when I click 'show uses' of functions or macros in the editor, until I switch to another application window and wait for a few seconds. Reproducible: Sometimes Steps to Reproduce: 1. Write an arbitrary function or macro 2. Move cursor over it, and click 'show uses' 3. It freezes Actual Results: The UI freezes for a few seconds and then comes back normal. Expected Results: No freezing. It happens when I click 'show uses' of a GLEW macros glClearColor(), glClear(), functions glewInit(), glViewport() and some other macros or functions. printf() has no bugs. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 362018] New: Saving playlist feature extremely rough...
https://bugs.kde.org/show_bug.cgi?id=362018 Bug ID: 362018 Summary: Saving playlist feature extremely rough... Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playlist Assignee: amarok-bugs-d...@kde.org Reporter: evert.vors...@yandex.com A little background information I was migrating from internal database to external one, and I have a sizable collection, with 80,000 songs. With this collection I also have quite a few playlists stored in the database. First thing I tried was to try and drag my from the database to files on disk. This appeared to work, and I could load the playlists into the main playlist. However, when I switched to the new database, I was no longer able to open the playlists that were saved to disk, as they appeared corrupted. I then tried the export playlist function in the context menu of the database of saved playlists. However the exported file was not loadable by amarok. The next thing I tried was to switch back to the previous database, load a saved playlist, then save it to disk by clicking on the "save" button. This very helpfully saved the playlist back to the database. There is a little down arrow next to the save icon, which would normally mean that there are some options, like where to save the playlist. However, this little down arrow does nothing, and the playlist just gets saved to the database. Selecting all songs in the playlist and dragging the songs to a new playlist on disk worked. It was a bit tedious doing every saved playlist I have like this. Reproducible: Always Expected Results: Consistent and solid saved playlist handling, Icons to actually do what they suggest to be doing -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 362017] Yakuake icon is sometimes shown in task manager
https://bugs.kde.org/show_bug.cgi?id=362017 --- Comment #2 from bogdan --- I continue to notice it on 5.6.3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 362017] Yakuake icon is sometimes shown in task manager
https://bugs.kde.org/show_bug.cgi?id=362017 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- I'd noticed this a few times in the past too, but not (yet) since updating to plasma-5.6.2. -- You are receiving this mail because: You are watching all bug changes.
[klettres] [Bug 355091] Klettres dont show words
https://bugs.kde.org/show_bug.cgi?id=355091 Burkhard Lueck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Burkhard Lueck --- https://docs.kde.org/stable5/en/kdeedu/klettres/using-klettres.html#levels1-and2 ...brings you to level 2. In that level, the user only hears the sound of the letter and has to type in the letter... https://docs.kde.org/stable5/en/kdeedu/klettres/levels3-and4.html ...brings you to level 4. In that level, the user only hears the sound of the syllable and has to type in the letters https://docs.kde.org/stable5/en/kdeedu/klettres/commands.html Level → Level 2 Choose the level 2 (no letter displayed, sound only) Level → Level 4 Choose the level 4 (no syllable displayed, sound only) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 362017] New: Yakuake icon is sometimes shown in task manager
https://bugs.kde.org/show_bug.cgi?id=362017 Bug ID: 362017 Summary: Yakuake icon is sometimes shown in task manager Product: yakuake Version: 3.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: bogdan.sinit...@gmail.com When I bring the Yakuake window, its icon sometimes appears in taskbar. Reproducible: Sometimes Steps to Reproduce: 1. Press hotkey to toggle Yakuake(maybe several times) Actual Results: Yakuake icon is shown in taskbar Expected Results: Yakuake icon shouldn't be shown in taskbar -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 362016] New: Replay Gain buttons greyed out
https://bugs.kde.org/show_bug.cgi?id=362016 Bug ID: 362016 Summary: Replay Gain buttons greyed out Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playback/Replay Gain Assignee: amarok-bugs-d...@kde.org Reporter: evert.vors...@yandex.com The only option that is selectable is "Disabled" I had a look around, and this seems related to bug 325862. However, I am using phonon- gstreamer as a backend, so replay gain and the analyzer is supposed to work. Reproducible: Always Steps to Reproduce: Click on "Settings", then click on "Replay Gain mode" Actual Results: The bottom two options are greyed out Expected Results: All options to be available. At the very least, if this is a common error some sort of indication of what is wrong so that one can fix it. If there is a simple fix for this, I have not found it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 --- Comment #5 from Martin Klapetek --- This is because the notification text item was changed to allow copy-pasting from it. The new text item however does not support eliding long text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 Martin Klapetek changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361995] no maximum size in notification dialog
https://bugs.kde.org/show_bug.cgi?id=361995 Martin Klapetek changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 361389 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361389] Huge Notification Size By Showing Entire EMail Content
https://bugs.kde.org/show_bug.cgi?id=361389 Martin Klapetek changed: What|Removed |Added CC||kain...@gmail.com --- Comment #4 from Martin Klapetek --- *** Bug 361995 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 303025] Refactoring after renaming class uses wrong class name
https://bugs.kde.org/show_bug.cgi?id=303025 --- Comment #2 from Priyanka Bandaru --- Created attachment 98488 --> https://bugs.kde.org/attachment.cgi?id=98488&action=edit Renamed the class name for the second time which updated the constructor name I followed all the steps provided above and didnt find any issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 303025] Refactoring after renaming class uses wrong class name
https://bugs.kde.org/show_bug.cgi?id=303025 Priyanka Bandaru changed: What|Removed |Added CC||pband...@mail.csuchico.edu --- Comment #1 from Priyanka Bandaru --- Created attachment 98487 --> https://bugs.kde.org/attachment.cgi?id=98487&action=edit Renamed the class name for the first time which updated the constructor name -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 --- Comment #5 from Christoph Feck --- Would it be possible to check if a "-style" argument was passed? In this case, the supplied argument would override Krita's internal choice. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361885] Kalarm crashes when closing main woindow
https://bugs.kde.org/show_bug.cgi?id=361885 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||aleix...@kde.org --- Comment #2 from Aleix Pol --- That's the bug, it's fixed in Qt, just need to wait for Qt 5.6.1. https://bugreports.qt.io/browse/QTBUG-51648 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341963] After full HDD home/.cache gets corrupted, plasmashell stuck on file locking
https://bugs.kde.org/show_bug.cgi?id=341963 Jan Chren (rindeal) changed: What|Removed |Added CC||dev.rindeal+bugs.kde.org@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Jan Chren (rindeal) changed: What|Removed |Added CC||dev.rindeal+bugs.kde.org@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 347524] Qt Creator Options crashed in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=347524 --- Comment #36 from Jan Chren (rindeal) --- Some more info on this bug: - does occur only when QtCreator theme is set to default and KDE theme is set to Breeze - this means that one possible workaround is to set QtCreator theme to "dark" - does occur only after "Environment" tab in "Options" menu was visited at least once, some settings were changed and "Apply" button was clicked (doesn't occur after hitting "Ok") -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 362015] New: Amarok Repeatedly Crashes When Playing Audio
https://bugs.kde.org/show_bug.cgi?id=362015 Bug ID: 362015 Summary: Amarok Repeatedly Crashes When Playing Audio Product: amarok Version: 2.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: hagen@gmail.com Application: amarok (2.8.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was chatting on IRC, put on a song and Amarok Crashed. THis has happened every time I play anything either locally, or if I stream content through amarok. Always within 2 minutes. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4a988e5940 (LWP 16198))] Thread 47 (Thread 0x7f4a7a1f8700 (LWP 16228)): #0 0x7f4a9545fb16 in __GI___sigwaitinfo (set=, info=0x7f4a7a1f7c60) at ../sysdeps/unix/sysv/linux/sigwaitinfo.c:56 #1 0x7f4a7118f7ab in ?? () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #2 0x7f4a940a86fa in start_thread (arg=0x7f4a7a1f8700) at pthread_create.c:333 #3 0x7f4a9552fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 46 (Thread 0x7f4a63164700 (LWP 16229)): #0 0x7f4a7047964a in ?? () from /lib/x86_64-linux-gnu/libaio.so.1 #1 0x7f4a71756078 in LinuxAIOHandler::collect() () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #2 0x7f4a7175cd0c in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #3 0x7f4a7176048d in os_aio_handler(unsigned long, fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #4 0x7f4a7194f0df in fil_aio_wait(unsigned long) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #5 0x7f4a71a81830 in io_handler_thread () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #6 0x7f4a940a86fa in start_thread (arg=0x7f4a63164700) at pthread_create.c:333 #7 0x7f4a9552fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 45 (Thread 0x7f4a62963700 (LWP 16230)): #0 0x7f4a7047964a in ?? () from /lib/x86_64-linux-gnu/libaio.so.1 #1 0x7f4a71756078 in LinuxAIOHandler::collect() () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #2 0x7f4a7175cd0c in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #3 0x7f4a7176048d in os_aio_handler(unsigned long, fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #4 0x7f4a7194f0df in fil_aio_wait(unsigned long) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #5 0x7f4a71a81830 in io_handler_thread () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #6 0x7f4a940a86fa in start_thread (arg=0x7f4a62963700) at pthread_create.c:333 #7 0x7f4a9552fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 44 (Thread 0x7f4a62162700 (LWP 16231)): #0 0x7f4a7047964a in ?? () from /lib/x86_64-linux-gnu/libaio.so.1 #1 0x7f4a71756078 in LinuxAIOHandler::collect() () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #2 0x7f4a7175cd0c in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #3 0x7f4a7176048d in os_aio_handler(unsigned long, fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #4 0x7f4a7194f0df in fil_aio_wait(unsigned long) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #5 0x7f4a71a81830 in io_handler_thread () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #6 0x7f4a940a86fa in start_thread (arg=0x7f4a62162700) at pthread_create.c:333 #7 0x7f4a9552fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 43 (Thread 0x7f4a61961700 (LWP 16232)): #0 0x7f4a7047964a in ?? () from /lib/x86_64-linux-gnu/libaio.so.1 #1 0x7f4a71756078 in LinuxAIOHandler::collect() () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #2 0x7f4a7175cd0c in LinuxAIOHandler::poll(fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #3 0x7f4a7176048d in os_aio_handler(unsigned long, fil_node_t**, void**, IORequest*) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #4 0x7f4a7194f0df in fil_aio_wait(unsigned long) () from /usr/lib/kde4/amarok_collection-mysqlecollection.so #5 0x7f4a71a81830 in io_handler_thread () from /usr/lib/kde4/amarok_
[plasmashell] [Bug 354731] Black or incorrect textures in different places of UI
https://bugs.kde.org/show_bug.cgi?id=354731 Chris changed: What|Removed |Added CC||emailofch...@gmail.com --- Comment #15 from Chris --- Created attachment 98486 --> https://bugs.kde.org/attachment.cgi?id=98486&action=edit Filenames of desktop items are replaced with colorful noise. I have nvidia 364.16 installed for my GTX 980 and my desktop files look like this when I return from suspend. Using Plasma 5.6.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347237] Progress Indicator Spinner in notifications causes 100% CPU usage
https://bugs.kde.org/show_bug.cgi?id=347237 Tim Landscheidt changed: What|Removed |Added CC||t...@tim-landscheidt.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360008] Contents of Power vr registers contents is not printed correctly when the --vgdb-shadow-registers=yes option is used.
https://bugs.kde.org/show_bug.cgi?id=360008 --- Comment #10 from Carl Love --- Yes, there are typos in that comment which is causing confusion. > The comment tells there are 64 VSR registers of 64 bits. Should say 128-bits not 64 bits. > that 'however, these are not "real" floating point registers': is that > speaking about fp[0..31] Should say fp[32..63] > Finally, the last paragraph tells 'the 32 floating point registers (AKA > VSR[0] to VSR[31])' yea, the AKA confuses things. I removed "(AKA VSR[0] to VSR[31])" I also added a diagram that shows the register layout. Basically copied from the ISA document. That should help the reader to visualize the layout. > In the code that initialises low_offset and high_offset : for VG_BIGENDIAN, > the comment tells > that the 64-bits are stored as Little Endian. Are the values really stored as > little endian, even > on a big endian platform ? I think the comment confused things more then it should have. I was trying to describe where the 64-bit values were but I see how you interpreted it. The four 32-bit values are stored in little endian or big endian format no mixed/partial format. So, I changed the comment to state where the four 32-bit values map to the array indicies to remove the confusion. I will re-spin the patch, update it in this bugzilla and retest everything on the various platforms before committing the patch. Thanks for the help. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 347524] Qt Creator Options crashed in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=347524 Jan Chren (rindeal) changed: What|Removed |Added CC||dev.rindeal+bugs.kde.org@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360023] kalarm crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360023 --- Comment #5 from David Jarvie --- It turns out that kalarm 15.12 requires the KDE Frameworks 5 version of ktimezoned, which is provided by the plasma-workspace package (in Debian/Ubuntu - I'm not sure about Archlinux). If this isn't working on your system, it seems likely that it's some kind of packaging problem, since it works fine on a self-compiled system. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361885] Kalarm crashes when closing main woindow
https://bugs.kde.org/show_bug.cgi?id=361885 David Jarvie changed: What|Removed |Added Product|kalarm |Breeze Component|general |general Assignee|djar...@kde.org |plasma-de...@kde.org --- Comment #1 from David Jarvie --- The crash is in the Breeze style code. Reassigning to Breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #18 from Friedrich W. H. Kossebau --- Possibly related: https://bugs.kde.org/show_bug.cgi?id=347237 (and not only nvidia, also an intel problem, like for me). "export QSG_RENDER_LOOP=basic" has been reported there and elsewhere to work-around the issue for now. So perhaps this bug can be solved as duplicate then? Sadly the other bug is resolved as "upstream", and https://bugreports.qt.io/browse/QTBUG-45959 is still "Open" :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361730] (HDMI) Plasma crashes after logging out and turning montior off.
https://bugs.kde.org/show_bug.cgi?id=361730 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361936] Kalarm startup warning: Time zones are not accessible
https://bugs.kde.org/show_bug.cgi?id=361936 David Jarvie changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from David Jarvie --- On Ubuntu or Debian, you need to install plasma-workspace package to fix this. The relevant file which is missing is /usr/lib/x86_64-linux-gnu/qt5/plugins/kded_ktimezoned.so (substitute your computer's architecture for 'x86_64-linux-gnu' if it doesn't have an AMD64 type processor). Clearly, there should be a package dependency for the KF5 version of kalarm on plasma-workspace (or alternatively the kded_ktimezoned.so file may need to be split out into another package). This is something that needs to be fixed by the Ubuntu packagers (and probably the Debian experimental packagers also). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361933] Screen is corrupted on the fading-out
https://bugs.kde.org/show_bug.cgi?id=361933 --- Comment #7 from Laurent Carlier --- Created attachment 98485 --> https://bugs.kde.org/attachment.cgi?id=98485&action=edit logging out with kwrite in the background -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window
https://bugs.kde.org/show_bug.cgi?id=361619 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krit ||a/31195a85a054e50af2d61ae76 ||4f341db12190f1e Resolution|--- |FIXED --- Comment #35 from Dmitry Kazakov --- Git commit 31195a85a054e50af2d61ae764f341db12190f1e by Dmitry Kazakov. Committed on 20/04/2016 at 20:03. Pushed by dkazakov into branch 'master'. Fix a "bended lines"+AMD+Qt5.6 bug The bug is actually in Qt 5.6. They decided to implement a motion event compression without *any* way to disable it. So we have a lot of events dropped resulting in "bended lines" on canvas. For some reason the bug is reproducible on AMD GPUs only, with openGL activated. It seems like either Qt asks for some synchronization, or rendering on AMD is just too slow. I don't know the exact reason, but being busy with rendering makes Qt drop a lot of events. Since this event compression cannot be disabled in any official way, we should start patching Qt on Linux as well. Yes, it means that Krita 3.0 cannot be distributed through official distribution repositories. Which means that Krita Lime will have to be shut down as soon as Ubuntu 16.04 will upgrade to Qt 5.6. CC:kimages...@kde.org CC:shawn.rutle...@theqtcompany.com Fixes T2224 M +1-03rdparty/ext_qt/CMakeLists.txt A +20 -03rdparty/ext_qt/qt-no-motion-compression.diff http://commits.kde.org/krita/31195a85a054e50af2d61ae764f341db12190f1e -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 353767] Support for a supression file
https://bugs.kde.org/show_bug.cgi?id=353767 --- Comment #4 from Sergio Martins --- Pragmas seem too crude, they act on the whole file unless you do a lot of push/pop. I'm thinking about a special comment which if present will tell clazy to shut up, just like we have for krazy -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361933] Screen is corrupted on the fading-out
https://bugs.kde.org/show_bug.cgi?id=361933 --- Comment #6 from Laurent Carlier --- > The trigger though is most likely the full scene blur filter in the logout > effect - add > > [Effect-Logout] > UseBlur=false > > > somewhere in ~/.config/kwinrc (resp. alter a present entry, if any) That's fix the issue -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361838] Colour picker for Colour Clip can't work due to darkened background
https://bugs.kde.org/show_bug.cgi?id=361838 Jean-Baptiste Mardelle changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Jean-Baptiste Mardelle --- The color clip creation dialog in clipcreationdialog.cpp void ClipCreationDialog::createColorClip(KdenliveDoc *doc, QStringList groupInfo, Bin *bin) { } needs to be made non modal so that it does not obscure the main window -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357541] akonadi_baloo_indexer crashes on akonadi start
https://bugs.kde.org/show_bug.cgi?id=357541 --- Comment #4 from Amos --- Created attachment 98484 --> https://bugs.kde.org/attachment.cgi?id=98484&action=edit New crash information added by DrKonqi akonadi_baloo_indexer (4.14) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Starting akonadi with akonadictl. Also happens if I run kontact. Happens essentially every time. -- Backtrace (Reduced): #6 0x7f7554a1a418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f7554a1c01a in __GI_abort () at abort.c:89 [...] #11 0x7f7558722db1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7f7555c70fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f7555c77f16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357541] akonadi_baloo_indexer crashes on akonadi start
https://bugs.kde.org/show_bug.cgi?id=357541 Amos changed: What|Removed |Added CC||amos.elb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360008] Contents of Power vr registers contents is not printed correctly when the --vgdb-shadow-registers=yes option is used.
https://bugs.kde.org/show_bug.cgi?id=360008 --- Comment #9 from Philippe Waroquiers --- Re-reading the comment at the beginning of valgrind-low-ppc64.c, the register maps is still not clear to me. The comment tells there are 64 VSR registers of 64 bits. But afterwards; the same commen tells that "The 32 vr[0] to vr[31] registers of size 128-bits map to VSR[31] to VSR[63].". Probably a VSR register is 128 bits. The second not very clear thing is for the fp registers: when the comment tells that 'however, these are not "real" floating point registers': is that speaking about fp[0..31] or rather about upper 64 bits of vsr[32] to vsr[63] ? I guess the later, so maybe tells something like floating point instructions are referencing the fp registers, and not the vsr registers. Finally, the last paragraph tells 'the 32 floating point registers (AKA VSR[0] to VSR[31])' which contradicts the previous paragraph that told the fp register sare in vsr[32..63] upper bits. In the code that initialises low_offset and high_offset : for VG_BIGENDIAN, the comment tells that the 64-bits are stored as Little Endian. Are the values really stored as little endian, even on a big endian platform ? The little endian comment says everything is little endian (so sounds logical); but the big endian case seems half big/half little. If this is really the case, then maybe add a sentence such as: "In the big endian case, a little endian convention is still partially used." For the xml core2 file: after re-reading the comment and playing with gdb on gcc110, I finally understood :). GDB is somewhat bizarre: it prints the general registers, then the fp register 0 .. 31, then pc etc, even if the xml file defines them in the order general registers followed by pc etc followed by fp 0 .. 31. Thanks for clarifying this. Otherwise, patch looks good to me. Up to you to see which additional updates you do for the comments above, but feel free to commit. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window
https://bugs.kde.org/show_bug.cgi?id=361619 --- Comment #34 from Dmitry Kazakov --- Hi, Tyson! Did you compile Qt yourself or you use the system's one? Qt 5.4.2, right? The point is that the real cause of bended lines was introduced in Qt 5.6. But if you say that Qt 5.4.2 is also affected, then it starts looking a bit too weird :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361933] Screen is corrupted on the fading-out
https://bugs.kde.org/show_bug.cgi?id=361933 --- Comment #5 from Thomas Lübking --- This somehow looks like a corruption in the plasmashell context (gkrellm looks translucent but w/o impact on the artifact structure) Can you please leave some opaque window (empty kwrite will do) open when logging out and take a screenshot of that? The trigger though is most likely the full scene blur filter in the logout effect - add [Effect-Logout] UseBlur=false somewhere in ~/.config/kwinrc (resp. alter a present entry, if any) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362014] New: Audio Volume Widget Crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=362014 Bug ID: 362014 Summary: Audio Volume Widget Crashes Plasma Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jontillma...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Sound card 9 Series Chipset Family HD Audio Controller Configured as sound card number 0 Driver snd-hda-intel Test sound works in YaST. Opening the sound widget either displays "Dummy Output" or nothing. Clicking inside the widget causes Plasma to crash. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff45e8c6800 (LWP 27124))] Thread 13 (Thread 0x7ff447853700 (LWP 27126)): #0 0x7ff457dbebbd in poll () from /lib64/libc.so.6 #1 0x7ff45cd10422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7ff45cd1200f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7ff449fd63c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7ff4584b932f in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7ff4575c80a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff457dc6fed in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7ff444803700 (LWP 27128)): #0 0x7ff457dbebbd in poll () from /lib64/libc.so.6 #1 0x7ff45449ce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff45449cf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff4586ebd8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7ff458692d53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7ff4584b461a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7ff45b7c6e18 in QQmlThreadPrivate::run (this=0xa94c20) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7ff4584b932f in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7ff4575c80a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff457dc6fed in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7ff433d03700 (LWP 27135)): #0 0x7ff457dbac8d in read () from /lib64/libc.so.6 #1 0x7ff44ff63073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.361.42 #2 0x7ff4544ddb60 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff45449c999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff45449cdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7ff45449cf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7ff4586ebd8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7ff458692d53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7ff4584b461a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7ff45b7c6e18 in QQmlThreadPrivate::run (this=0xc63300) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #10 0x7ff4584b932f in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7ff4575c80a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7ff457dc6fed in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7ff4324dc700 (LWP 27136)): #0 0x7ff4544decf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff45449c4b9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff45449cd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff45449cf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff4586ebd8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7ff458692d53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7ff4584b461a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7ff45b7c6e18 in QQmlThreadPrivate::run (this=0xccfdf0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7ff4584b932f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7ff4575c80a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7ff457dc6fed in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7ff430b6e700 (LWP 27137)): #0 0x7ff4575cc03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff45df9586b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7ff45df95899 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7ff4575c80a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7ff457dc6fed in clone
[dolphin] [Bug 362013] New: Remove emblem icons at <=22px view size
https://bugs.kde.org/show_bug.cgi?id=362013 Bug ID: 362013 Summary: Remove emblem icons at <=22px view size Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: uri_herr...@nitrux.in Emblems are literally indistinguishable at this size in any icon theme including Breeze and Oxygen and the size it's so small that it makes it nearly impossible to create a meaningful icon in the size it's probably requiring them, I'm estimating that it's 8px or less. Reproducible: Always Steps to Reproduce: 1. Open Dolphin 2. Change to Icon view 3. Move slider to 22px Actual Results: Indistinguishable emblem icons. Expected Results: No emblem icons. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #55 from Thomas Lübking --- (In reply to Artur O. from comment #54) > Toggling composting with ctrl+shift+F12 the panel switches betwen these two > states. One when effects are on (updated) and effects off (frozen). More like bug #347829 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361933] Screen is corrupted on the fading-out
https://bugs.kde.org/show_bug.cgi?id=361933 --- Comment #4 from Laurent Carlier --- Created attachment 98483 --> https://bugs.kde.org/attachment.cgi?id=98483&action=edit glxinfo output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361933] Screen is corrupted on the fading-out
https://bugs.kde.org/show_bug.cgi?id=361933 --- Comment #3 from Laurent Carlier --- Created attachment 98482 --> https://bugs.kde.org/attachment.cgi?id=98482&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #2 from Philippe Waroquiers --- If show sched status is called before the threads are implemented, then nothing will be visible. Maybe it would be better to do something like: if (VG_(threads) == NULL) { VG_(printf) ("cannot show sched status : scheduler not yet initialised\"); return; } ... here the old code ... rather than report nothing ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361753] Activities marked “stopped” without reason
https://bugs.kde.org/show_bug.cgi?id=361753 Denis Kuplyakov changed: What|Removed |Added CC||dener@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 362012] New: akonadi crashes whenever I try to start it from the command line
https://bugs.kde.org/show_bug.cgi?id=362012 Bug ID: 362012 Summary: akonadi crashes whenever I try to start it from the command line Product: korgac Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: amos.elb...@gmail.com Application: korgac (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-18-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: akonadictl start - Custom settings of the application: When I had stopped akonadi earlier, it was because I noticed it had not downloaded from gmail in 2 days, but had continued to download from other email accounts. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff69d6ab940 (LWP 9684))] Thread 5 (Thread 0x7ff691d3f700 (LWP 9818)): #0 0x7ff6aa8538b9 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff6aa85424b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6aa85442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff6b1f54a9b in QEventDispatcherGlib::processEvents (this=0x7ff68c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff6b1efbdea in QEventLoop::exec (this=this@entry=0x7ff691d3ec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff6b1d188a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff6b1d1d84e in QThreadPrivate::start (arg=0xff3d60) at thread/qthread_unix.cpp:331 #7 0x7ff6aad756fa in start_thread (arg=0x7ff691d3f700) at pthread_create.c:333 #8 0x7ff6b141db5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7ff69153e700 (LWP 9819)): #0 0x7ff6b1411e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff6aa85431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6aa85442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff6b1f54a9b in QEventDispatcherGlib::processEvents (this=0x7ff6880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff6b1efbdea in QEventLoop::exec (this=this@entry=0x7ff69153dc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff6b1d188a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff6b1d1d84e in QThreadPrivate::start (arg=0x10c3170) at thread/qthread_unix.cpp:331 #7 0x7ff6aad756fa in start_thread (arg=0x7ff69153e700) at pthread_create.c:333 #8 0x7ff6b141db5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7ff690d3d700 (LWP 7446)): #0 0x7ff6aa8538a0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff6aa85424b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6aa85442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff6b1f54a9b in QEventDispatcherGlib::processEvents (this=0x7ff684003f10, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff6b1efbdea in QEventLoop::exec (this=this@entry=0x7ff690d3cc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff6b1d188a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff6b1d1d84e in QThreadPrivate::start (arg=0xf98820) at thread/qthread_unix.cpp:331 #7 0x7ff6aad756fa in start_thread (arg=0x7ff690d3d700) at pthread_create.c:333 #8 0x7ff6b141db5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7ff683bdd700 (LWP 7465)): #0 0x7ff6b1411e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff6aa85431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff6aa85442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff6b1f54a9b in QEventDispatcherGlib::processEvents (this=0x7ff67c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff6b1efbdea in QEventLoop::exec (this=this@entry=0x7ff683bdcc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff6b1d188a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff6b1d1d84e in QThreadPrivate::start (arg=0x292ade0) at thread/qthread_unix.cpp:331 #7 0x7ff6aad756fa in start_thread (arg=0x7ff683bdd700) at pthread_create.c:333 #8 0x7ff6b141db5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ff69d6ab940 (LWP 9684)): [KCrash Handler] #6 QVector >::reserve (this=, asize=asize@entry=0) at /usr/include/x86_64-linux-g
[ktorrent] [Bug 362011] New: Drag and drop of URLs from Chromium does not work
https://bugs.kde.org/show_bug.cgi?id=362011 Bug ID: 362011 Summary: Drag and drop of URLs from Chromium does not work Product: ktorrent Version: 5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: luke-jr+kdeb...@utopios.org Drag & drop of links from Chromium seems to get corrupted at some point. Also tested: - Drag and drop Chromium links to other Qt5 application (pcmanfm-qt): works fine - Drag and drop directory from pcmanfm-qt: works as expected (error that it's not a torrent file, with the full correct path name) - Drag and drop Chromium links to other KF5 application (Konversation): works fine It seems only the specific combination of Chromium to KTorrent fails. Reproducible: Always Steps to Reproduce: 1. Open http://www.kubuntu.org/getkubuntu/ in Chromium. 2. Drag "14.04 image, 64bit" BitTorrent link to KTorrent. Actual Results: Got errors: "Malformed URL %001%004%00.%000%004%00 %00i%00m%00a%00g%00e%00,%00 %006%004%00b%00i%00t." and "Malformed URL ." Expected Results: Prompt to start download of torrent file. This worked fine in 4.3.1. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361954] Make kwayland backend optional
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #10 from Luke-Jr --- In my case, I still run KDE 4, with a few KF5-based applications. If KWin/Plasma 5 will require KWayland, I will probably switch to LXQt when KDE 4 ceases to be viable. LXQt, however, still requires libkscreen. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 352896] Doesn't build on OSX
https://bugs.kde.org/show_bug.cgi?id=352896 Antonio Forgione changed: What|Removed |Added CC||emi...@gmail.com --- Comment #9 from Antonio Forgione --- @RJVB: how did you succeed in practice? I tried compiling the clazy plugin on Mac OS X after installing cmake and llvm with brew: brew install cmake brew install brew install llvm —with-clang —with-clang-extra-tools And using cmake this way: cmake -DCMAKE_INSTALL_PREFIX=/usr/local/bin -DCMAKE_BUILD_TYPE=Release -DLLVM_ROOT=/usr/local/opt/llvm But I found very similar (if not exatly the same) linking issues. Any help is appreciated. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 177778] make it possible to resize resizable annotations
https://bugs.kde.org/show_bug.cgi?id=18 Alessander Botti Benevides changed: What|Removed |Added CC||alessanderbo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361973] File open/save/export dialogs broken
https://bugs.kde.org/show_bug.cgi?id=361973 --- Comment #10 from Ilya V. Portnov --- "Suspected" part of that commit is +#ifdef Q_OS_LINUX +qputenv("XDG_DATA_DIRS", QFile::encodeName(KoResourcePaths::getApplicationRoot() + "/share") + ":" + qgetenv("XDG_DATA_DIRS")); +#else +qputenv("XDG_DATA_DIRS", QFile::encodeName(KoResourcePaths::getApplicationRoot() + "/share")); +#endif +//qDebug() << "Setting XDG_DATA_DIRS" << qgetenv("XDG_DATA_DIRS"); In my environment, I have XDG_DATA_DIRS not set. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361973] File open/save/export dialogs broken
https://bugs.kde.org/show_bug.cgi?id=361973 --- Comment #9 from Ilya V. Portnov --- So, I finally run git bisect, and the result is: 5ef533050cd4206353b44fecd4f06edd6e94e729 is the first bad commit commit 5ef533050cd4206353b44fecd4f06edd6e94e729 Author: Boudewijn Rempt Date: Wed Apr 6 20:57:52 2016 +0200 Find all the languages so the language chooser is shown Make sure that on all platforms the local xdg_data_dirs is part of the environment variable, the one that is bin'../share or MacOS/../share. And remove the kauthorized stuff as well. Nobody is going to disable anything in the help menu in krita in any kind of kiosk situation. :04 04 1daab4b1c7328743631461c0f7dc61e61905 b89d6b0304263dda7fc9a7ccb4fc14c3f248b00e M libs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361985] Plasmashell crashes when MPRIS dbus app stops
https://bugs.kde.org/show_bug.cgi?id=361985 Mike changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Mike --- Sort of. It's a proxy app that wraps the web service from JRiver MediaCenter into a MPRIS "player" so that you can control JRiver MC with any MPRIS applet. In addition, it provides an alternative GUI to simultaneously manage playback on multiple JRiver MC servers on your net. Each JRiver server can provide any number of playback zones (roughly related to sound/video output devices), so it can get complex and MPRIS using the dbus object-path per process creates a bit of a problem. It currently only works if JRiver is running somewhere on your net. Yes, I've converted everything applicable to QVariantMap and I am no longer using qDBusRegister, but it is still crashing occasionally. For some reason, DrKonqi isn't picking up the crash and PlasmaSHell is just restarting itself... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360578] Desktop folder view icons not movable if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360578 Eike Hein changed: What|Removed |Added Resolution|DUPLICATE |FIXED Latest Commit||http://commits.kde.org/plas ||ma-desktop/bca9fc813e4dfe6f ||af59d5945ac19c96c49b1e6f --- Comment #8 from Eike Hein --- Git commit bca9fc813e4dfe6faf59d5945ac19c96c49b1e6f by Eike Hein. Committed on 20/04/2016 at 18:50. Pushed by hein into branch 'Plasma/5.6'. Fix DND on Folder View containments with locked widgets. This is a regression from 92665578, which nerfed DND on the locked containment, not taking file DND in folder mode into account. The goal was actually to ignore dropped tabs from Mozilla Firefox -- this preserves that accomplishment by only letting through things Folder View would actually care about. Reviewed-by: David Rosca M +7-0containments/desktop/package/contents/code/FolderTools.js M +4-9containments/desktop/package/contents/ui/main.qml http://commits.kde.org/plasma-desktop/bca9fc813e4dfe6faf59d5945ac19c96c49b1e6f -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 362010] New: Kontact crashes on changing dictionary or autocorrection language
https://bugs.kde.org/show_bug.cgi?id=362010 Bug ID: 362010 Summary: Kontact crashes on changing dictionary or autocorrection language Product: korgac Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: koffeinfried...@gmail.com Application: korgac (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I've changed Dictionary (Autocorrection language is the same) to another language; in the "Edit Identity" setting in Kontact. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1356189940 (LWP 3971))] Thread 4 (Thread 0x7f1351fcc700 (LWP 3983)): #0 0x7f13648cda49 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1364b9 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f136488924b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f136488942c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f136bf89a9b in QEventDispatcherGlib::processEvents (this=0x7f13440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f136bf30dea in QEventLoop::exec (this=this@entry=0x7f1351fcbc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f136bd4d8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f136bd5284e in QThreadPrivate::start (arg=0x187a1a0) at thread/qthread_unix.cpp:331 #8 0x7f1364daa6fa in start_thread (arg=0x7f1351fcc700) at pthread_create.c:333 #9 0x7f136b452b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f13517cb700 (LWP 3984)): #0 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:213 #1 0x7f136bf88ffa in postEventSourcePrepare (s=0x7f13480012d0, timeout=0x7f13517caac4) at kernel/qeventdispatcher_glib.cpp:247 #2 0x7f1364ad in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f136488924b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f136488942c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f136bf89a9b in QEventDispatcherGlib::processEvents (this=0x7f13480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f136bf30dea in QEventLoop::exec (this=this@entry=0x7f13517cac80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f136bd4d8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f136bd5284e in QThreadPrivate::start (arg=0x18759c0) at thread/qthread_unix.cpp:331 #9 0x7f1364daa6fa in start_thread (arg=0x7f13517cb700) at pthread_create.c:333 #10 0x7f136b452b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f1350fca700 (LWP 3987)): #0 0x7f136b446e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f136488931c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f136488942c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f136bf89a9b in QEventDispatcherGlib::processEvents (this=0x7f133c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f136bf30dea in QEventLoop::exec (this=this@entry=0x7f1350fc9c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f136bd4d8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f136bd5284e in QThreadPrivate::start (arg=0x1870710) at thread/qthread_unix.cpp:331 #7 0x7f1364daa6fa in start_thread (arg=0x7f1350fca700) at pthread_create.c:333 #8 0x7f136b452b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f1356189940 (LWP 3971)): [KCrash Handler] #6 0x7f136fadcc90 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #7 0x7f136fad8894 in KCalCore::Calendar::setupRelations(QSharedPointer const&) () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #8 0x7f136fb16bac in KCalCore::MemoryCalendar::addIncidence(QSharedPointer const&) () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #9 0x7f13704b0e9e in ?? () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5 #10 0x7f13704be6f8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5 #11 0x7f13704bf959 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5 #12 0x7f136bf61e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffcde598e70, r=0x1826b00, this=)
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 --- Comment #1 from Ivo Raisr --- Created attachment 98481 --> https://bugs.kde.org/attachment.cgi?id=98481&action=edit proposed patch The patch consists mainly of whitespace changes due to different indentation. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 361976] 16.07.70 git master - rendering from .mp4 h.264 footage produces large distortion artifacts (video example & sample footage included)
https://bugs.kde.org/show_bug.cgi?id=361976 --- Comment #3 from Jesse --- Hey Evert, Thanks for the feedback. Yessir, the Processing threads is set to 1, and has been since the fresh installation. When you get a chance, would you be willing to try to render the sample clip I provided in the description with the settings I'd specified? I'm also trying a few different export options in Blender to see if that changes anything. More info' to come! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net Assignee|jsew...@acm.org |iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362009] New: Valgrind dumps core on unimplemented functionality before threads are created
https://bugs.kde.org/show_bug.cgi?id=362009 Bug ID: 362009 Summary: Valgrind dumps core on unimplemented functionality before threads are created Product: valgrind Version: 3.12 SVN Platform: Compiled Sources OS: Solaris Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: iv...@ivosh.net If VG_(unimplemented)() is called early during the main initialization, before the threads are created, Valgrind dumps core in show_sched_status_wrk(). That's because VG_(threads) is still NULL and it is dereferenced via VG_(threads)[i].os_state... This happens for example on Solaris when VG_(unimplemented)() is called from VG_(load_ELF)() which is used during client image initialization. Fix attached, regression testing went fine. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 362008] Taking too long to open, "I Forgot my Password" link.
https://bugs.kde.org/show_bug.cgi?id=362008 --- Comment #1 from Looserof7 --- It seems the whole identity.kde.org is too slow -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 362008] New: Taking too long to open, "I Forgot my Password" link.
https://bugs.kde.org/show_bug.cgi?id=362008 Bug ID: 362008 Summary: Taking too long to open, "I Forgot my Password" link. Product: forum.kde.org Version: unspecified Platform: Other URL: https://forum.kde.org/ucp.php?mode=login OS: All Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: forum-ad...@kde.org Reporter: looser...@gmail.com As I have forgotten my password, I clicked on the link "Forgot my password", But for my surprise it took to long load, immediately I opened another tab too check that out if Internet speed is slow, but the result is negative. I managed to get that page quite after some time , when I filled the appropriate options in text-boxes, then I clicked on "Reset My Password" option and this took longer than the other. But once the same is loaded in second. I was able to open all other web-pages without any problem, I mean it is fast enough. Please check out this problem. I think I was clear enough. Need any further information, happy to respond. Reproducible: Always Expected Results: Web-Pages would have been loaded faster. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 362007] New: On-demand modus & always enabling bluetooth-using integration (e.g. file sending)
https://bugs.kde.org/show_bug.cgi?id=362007 Bug ID: 362007 Summary: On-demand modus & always enabling bluetooth-using integration (e.g. file sending) Product: Bluedevil Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kosse...@kde.org I usually have bluetooth turned off via the Plasma bluetooth control on my laptop (for power & security/privacy reasons). Still I use it now and then, e.g. to send a file to another device. Problems: * needs me to explicitely enable & disable bluetooth every time I want to use it * the options where bluetooth integration is available sometimes are hidden (e.g. the send-file action in the filemanager integration), so I do not learn about them in my normal working modus Requested features: It would be nice to have the possibility of on-demand enabling of bluetooth: when bluetooth integration is enabled, the options are always shown (using static data where needed, like known other devices). if an option then is selected it result in bluetooth being enabled on-demand. if the action has a defined time scope, like file sending, bluetooth would be disabled afterwards again (unless other services requested on-demand mode and are still running, or the user actively set it to "always on"). Nice-to-have: perhaps the user could be optionally also queried if they really want to turn on bluetooth for that action (perhaps they are in an environment where this needs consideration every time). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[klettres] [Bug 355091] Klettres dont show words
https://bugs.kde.org/show_bug.cgi?id=355091 --- Comment #3 from orti1...@gmail.com --- german -- You are receiving this mail because: You are watching all bug changes.
[klettres] [Bug 355091] Klettres dont show words
https://bugs.kde.org/show_bug.cgi?id=355091 --- Comment #2 from orti1...@gmail.com --- german 2016-04-20 16:09 GMT+02:00 Burkhard Lueck via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=355091 > > Burkhard Lueck changed: > >What|Removed |Added > > > CC||lu...@hube-lueck.de > > --- Comment #1 from Burkhard Lueck --- > Which language are you using? > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361674] X11 damage events not generated when the desktop is exposed
https://bugs.kde.org/show_bug.cgi?id=361674 --- Comment #12 from Thomas Lübking --- I don't maintain plasmashell. If it's a bug, it's likely upstream (and driven by the GL overlay window nature) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.
https://bugs.kde.org/show_bug.cgi?id=361987 --- Comment #7 from Thomas Lübking --- (In reply to Artur O. from comment #6) > Transform/Morph the container but not the contents. That's not possible. The window is opaque to the compositor. (ie. there is no "content" - the window is one block of random pixels) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 --- Comment #9 from Germano Massullo --- Ok -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #4 from eric --- Created attachment 98479 --> https://bugs.kde.org/attachment.cgi?id=98479&action=edit Backtrace of kaddressbook crash This crash still happen with: - KDE Framework 5.21.0 - KDE Applications 15.12.3 - KDE Plasma 5.6.3 - Qt 5.6.0 - Linux 4.5.1 32bit (is 32bit the problem? Maybe the devs are using 64bit computers) There is some improvement: In the past, adding a contact with a birthday in kaddressbook used to crash kaddressbook and korganizer's to-do and even view, but now korganizer's event view does not crash anymore. This is the last thing I see in the console when kaddressbook/korganizer crash: ASSERT failure in QVector::at: "index out of range", file /usr/include/qt/QtCore/qvector.h, line 419 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 Rex Dieter changed: What|Removed |Added Product|plasmashell |kscreenlocker Component|general |library Target Milestone|1.0 |--- Version|5.6.2 |unspecified --- Comment #8 from Rex Dieter --- triaging to kscreenlocker component -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 Rex Dieter changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #7 from Rex Dieter --- It's not resolved (re-opening), I'd still argue upstream should consider bumping libKScreenLocker soname -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] New: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected"
https://bugs.kde.org/show_bug.cgi?id=362006 Bug ID: 362006 Summary: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected" Product: wacomtablet Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: joerg.ehri...@gmx.de Reporter: dilfri...@gentoo.org Have an Intuos 4, worked fine until the upgrade from KDE4. I packaged wacomtablet-3.0.0_beta1 (I'm in the gentoo kde team), the tabletfinder recognizes the tablet OK, but the KCM always shows "no tablet connected". Please advise how to debug further. Feel free to ping me on IRC (dilfridge). TIA! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 Germano Massullo changed: What|Removed |Added Resolution|--- |INVALID Status|CONFIRMED |RESOLVED Component|library |general Product|kscreenlocker |plasmashell Version|unspecified |5.6.2 Target Milestone|--- |1.0 --- Comment #6 from Germano Massullo --- The problem was that entering # dnf update kf* plasm* --enablerepo=updates-testing the system did not update kscreenlocker package -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 362005] Hidden windows namebar, panel's taskbar entries and whole Plasma unusable
https://bugs.kde.org/show_bug.cgi?id=362005 Rex Dieter changed: What|Removed |Added Ever confirmed|0 |1 Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Status|UNCONFIRMED |CONFIRMED Target Milestone|1.0 |--- Version|5.6.2 |unspecified Product|plasmashell |kscreenlocker CC||mgraess...@kde.org, ||rdie...@math.unl.edu Component|general |library --- Comment #5 from Rex Dieter --- Appears user updated to kwin-5.6.x , but (probably) missed upgrading kscreenlocker-5.6.x along with it (and tried using kscreenlocker-5.5.x), resulting in missing symbols: kwin_x11: symbol lookup error: /lib64/libkwin.so.5: undefined symbol: _ZN12ScreenLocker7KSldApp16lockStateChangedEv Shouldn't libKScreenLocker soname get bumped for the new symbol? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361651] kaddressbook crashes continuously after importing a vcf card
https://bugs.kde.org/show_bug.cgi?id=361651 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- This looks like https://bugs.kde.org/show_bug.cgi?id=358696 Kaddressbook crashes immediately after adding or importing a contact that has a birthday or anniversary date. If you remove the "BDAY" or "ANNIVERSARY" line in a vcf card, importing it will not result in a crash. After this crash, kaddressbook will always crash the next time it is executed. Korganizer will also always crash when it is in the "To-do View" (View > To-do List) or when adding a new to-do (Actions > New To-do...). Korganizer will not crash when in the calendar view (View > Month). Korganizer's "Event View" and create new event also used to crash, but is not doing that anymore... so there is some improvement. These crashes only happen when the "Birthday and Anniversaries" calendar is enabled in korganizer. Kaddressbook is almost useless without the possibility to have contacts that have a birthday or anniversary date. The frustrating part is that it is unconfirmed and not many other people complain about the same problem. I've tried everything I can think of, but so far without a success: - switching between MySQL (MariaDB) and SQLite; - creating a complete new user; - creating the homedir in /tmp (maybe it has issues with BtrFS); - raising the stacksize (ulimit -s); - changing locales (LC_*) to en_US, C or leave them empty I'm currently using: - KDE Framework 5.21.0 - KDE Applications 15.12.3 - KDE Plasma 5.6.3 - Qt 5.6.0 - Linux 4.5.1 32bit (is 32bit the problem? Maybe the devs are using 64bit computers) Other bugreport that may have the same issue as this one: https://bugs.kde.org/show_bug.cgi?id=360746 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=359610 https://bugs.kde.org/show_bug.cgi?id=358696 (crash after adding contact with birthday) https://bugs.kde.org/show_bug.cgi?id=357361 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=357228 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=353482 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360578] Desktop folder view icons not movable if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360578 Eike Hein changed: What|Removed |Added CC||painless.roas...@gmail.com --- Comment #7 from Eike Hein --- *** Bug 361996 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361996] impossible change position of file (or folder) in desktop with state 'lock widgets'
https://bugs.kde.org/show_bug.cgi?id=361996 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Eike Hein --- *** This bug has been marked as a duplicate of bug 360578 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #12 from matejcik --- At the moment i can very reliably reproduce between firefox and thunderbird, and much less reliably between firefox and something else. Between firefox and thunderbird, it is possible to get into a state where with relatively calm mouse pointer movement between the windows, the focus "sticks" on one of them for several transitions in a row. But I verified that it can happen with kwrite as well. I didn't manage to reproduce between two non-gtk apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.
https://bugs.kde.org/show_bug.cgi?id=361987 --- Comment #6 from Artur O. --- (In reply to Thomas Lübking from comment #5) > > Well i would say morph only the tooltip window and keep the size or > > constrain the resize to some % of the contents > > That does obviously not work - I guess what you mean is to not transform the > size (and not crossfade the content) but switch to new tooltip size & > content directly and transform only the position. > > There're already some filters to prevent "small™" and "large™" translations > - matter of taste and values I guess. > > I can't try your demo because I don't use KWin anymore. Transform/Morph the container but not the contents. The demo would be jquery / webb since i dont have any knoledge in qml/qt/kde dev. Or since you don't use kwin anymore maybe try to record the situation when it happens. -- You are receiving this mail because: You are watching all bug changes.
Re:Tennis Enthusiasts
Hi, Would you be interested in reaching out to "Tennis Enthusiasts"from the USA ? We maintain contacts with complete information. We also have data for Golfers List, Boxing Enthusiasts, Running Enthusiasts, Basketball Enthusiasts, Soccer Enthusiasts, Golfers List,Baseball Enthusiasts, Health and Fitness Enthusiasts, Outdoor Enthusiasts, Students List, Apparel Buyers , Skiers Enthusiasts, Spa and Resort Visitors and many more. Each record in the list contains Contact Name (First, Middle and Last Name), Mailing Address, List type and Opt-in email address. Please let me know your targeted criteria, so that I can help you out the driver your sales effort in the right direction. Thanks & Regards, Maria Rebello --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus