[plasmashell] [Bug 382290] New: Kde crash
https://bugs.kde.org/show_bug.cgi?id=382290 Bug ID: 382290 Summary: Kde crash Product: plasmashell Version: 5.10.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sebastians...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.11.9-300.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I had a window of KRDC on one workspace open (and connected) and wanted to open firefox on the second workspace The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f736bba34c0 (LWP 1415))] Thread 16 (Thread 0x7f72857fa700 (LWP 1826)): #0 0x7f7376e4781b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f737871e93b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f72b99f1985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f72b99f58f8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f72b99f0b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f72b99f383b in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f737871e1ee in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f7376e4136d in start_thread () at /lib64/libpthread.so.0 #8 0x7f7377b05b8f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f7285ffb700 (LWP 1825)): #0 0x7f7376e4781b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f737871e93b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f72b99f1985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f72b99f58f8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f72b99f0b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f72b99f5952 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f72b99f0b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7f72b99f383b in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7f737871e1ee in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f7376e4136d in start_thread () at /lib64/libpthread.so.0 #10 0x7f7377b05b8f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f72867fc700 (LWP 1824)): #0 0x7f7376e4781b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f737871e93b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f72b99f1985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f72b99f58f8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f72b99f0b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f72b99f383b in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f737871e1ee in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f7376e4136d in start_thread () at /lib64/libpthread.so.0 #8 0x7f7377b05b8f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f7286ffd700 (LWP 1822)): #0 0x7f7376e4781b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f737871e93b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f72b99f1985 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f72b99f58f8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f72b99f0b4d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f72b99f5952 in
[kwin] [Bug 382285] KWin crash while installing Steam with Wine
https://bugs.kde.org/show_bug.cgi?id=382285 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Flöser --- Please upgrade to 5.10.3.1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 382280] KRunner cannot be opened after pressing Escape key on Wayland
https://bugs.kde.org/show_bug.cgi?id=382280 Martin Flöserchanged: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-61930 --- Comment #2 from Martin Flöser --- Upstream bug reported: https://bugreports.qt.io/browse/QTBUG-61930 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 349378] ctest unit tests run in the wrong working directory
https://bugs.kde.org/show_bug.cgi?id=349378 Rolf Eike Beerchanged: What|Removed |Added Version Fixed In||5.2.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||velop/5c65da19fc4451eb02f3e ||2354764fd272ce33949 --- Comment #1 from Rolf Eike Beer --- Git commit 5c65da19fc4451eb02f3e2354764fd272ce33949 by Rolf Eike Beer. Committed on 13/07/2017 at 04:58. Pushed by dakon into branch 'master'. pass all test properties to CTestSuite Summary: This way this and CTestRunJob can do any adaptions to the properties without needing more and more members. CTest: parse the test properties from CTestTestfile.cmake Otherwise e.g. the WILL_FAIL check in ctestutils.cpp will never match as the property hash is always empty. CTest: honor the WORKING_DIRECTORY property of tests FIXED-IN:5.2.0 CTest: use the test name as name instead of the executable name Now one only needs to get rid of the first argument that is sometimes appended. Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D6668 M +1-1projectmanagers/cmake/testing/ctestrunjob.cpp https://commits.kde.org/kdevelop/5c65da19fc4451eb02f3e2354764fd272ce33949 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 349378] ctest unit tests run in the wrong working directory
https://bugs.kde.org/show_bug.cgi?id=349378 Rolf Eike Beerchanged: What|Removed |Added Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde |velop/5c65da19fc4451eb02f3e |velop/569a9e03eca189d68db3f |2354764fd272ce33949 |9ef9b854d446c473afd --- Comment #2 from Rolf Eike Beer --- Git commit 569a9e03eca189d68db3f9ef9b854d446c473afd by Rolf Eike Beer. Committed on 13/07/2017 at 04:54. Pushed by dakon into branch 'master'. CTest: honor the WORKING_DIRECTORY property of tests FIXED-IN:5.2.0 M +6-2projectmanagers/cmake/testing/ctestrunjob.cpp https://commits.kde.org/kdevelop/569a9e03eca189d68db3f9ef9b854d446c473afd -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 382289] New: Long-standing bug: Bookmarks are often forgotten.
https://bugs.kde.org/show_bug.cgi?id=382289 Bug ID: 382289 Summary: Long-standing bug: Bookmarks are often forgotten. Product: kdevelop Version: 5.1.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bookmarks part Assignee: kdevelop-bugs-n...@kde.org Reporter: termt...@rogers.com Target Milestone: --- Hello. For a long time now, if I recall even back in Qt4 before the switch to Qt5, KDevelop keeps forgetting my bookmarks. It happens in all distros I've used, like KUbuntu or this current openSUSE Tumbleweed. As a seasoned tracker, all I have been able to do so far is watch, and try to observe when it happens. But it's elusive, hard to pin down. The only clue I can provide is that it seems to have something to do with large files in a large project and/or the number of files open in the editor. I can only point you in the direction of our CMake based C++ project: Project: https://github.com/muse-sequencer/muse Website: http://muse-sequencer.org/ To recreate the problem, open the MusE cmake project. Open say, ten or twenty of the large "juicy" project files in the editor. As a test, which I just tried, also open the >2000 line "midi.cpp" file. Add some bookmarks to "midi.cpp", close and reopen KDevelop and MusE. The bookmarks are gone in "midi.cpp". If not that file, try some of the other files, surely sooner or later you'll hit several files where all bookmarks are forgotten. Some of our files are over two thousand lines long. Hope I can assist further. Thanks. Tim. Coding MusE and other projects in KDevelop since its inception. KDevelop rocks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381732] (gmic-qt) Problems with layer dimension and position calculations
https://bugs.kde.org/show_bug.cgi?id=381732 Nicholas LaPointechanged: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/f80c0940d1e1bd94fa137f35 ||510fe4f877c2d227 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nicholas LaPointe --- Git commit f80c0940d1e1bd94fa137f35510fe4f877c2d227 by Nicholas LaPointe. Committed on 13/07/2017 at 01:12. Pushed by nicholasl into branch 'master'. Fix calculations of source rectangle and selection dimensions when sending data to G'MIC When there was no selection, the old plug-in would read and write pixels within the rectangle (0,0 canvasWidth x canvasHeight). The new plug-in was still set up to do this, except it would send the rectangle (0,0 layerWidth x layerHeight) to G'MIC. When there was a selection in the old plug-in, it would read and write within the selection rectangle. The new plug-in would read using (0,0 layerWidth x layerHeight), then write inside the selection rectangle. This commit should reinstate the old behavior. Differential Revision: https://phabricator.kde.org/D6431 M +28 -12 plugins/extensions/qmic/QMic.cpp https://commits.kde.org/krita/f80c0940d1e1bd94fa137f35510fe4f877c2d227 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Tim E. Realchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #28 from Tim E. Real --- This seems to be working now. I noticed a couple of situations after switching desktop styles where it was frozen if I clicked on the title bar, but I was able to continue simply by (I think) clicking once more, or by using the title bar icons to restore/minimize. Minor graphical artifact: The MDI shadow is not drawn on a 'normal' subwin sometimes after a style change, but IIRC maximizing/minimizing cures it soon after. Our project seems OK now. It uses MDI with styles/stylesheets. It's the good ol' MusE midi/audio sequencer project. Hope it's OK to change to this status. Thanks very much for your help! Tim. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379519] JJ: Improvement to the color adjustment curves
https://bugs.kde.org/show_bug.cgi?id=379519 Isabelle Delmaschanged: What|Removed |Added CC||anz...@gmail.com --- Comment #2 from Isabelle Delmas --- Hi, I am willing to get started on that job. However, I am new to KDE and have not used Qt in a while. Any indication where I should start? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 346194] option "Do not close when command exits" unchecks itself from Advanced Options for a link to application
https://bugs.kde.org/show_bug.cgi?id=346194 Jaggz H.changed: What|Removed |Added CC||jagg...@gmail.com --- Comment #1 from Jaggz H. --- In addition to this, I noticed the full Menu editor does not show that option at all. It has "Run in terminal", but not "Do not close when command exits". Neither option, including "Run in terminal", will not stay selected when I edit the application entry directly (Right-click -> Edit Application -> ... -> Advanced). I am in Debian Testing, using menu editor 5.8.4, on July 12, 2017. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382288] libQt5Core5 5.9.1 introduces memory leak and plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=382288 --- Comment #1 from Mircea Kitsune--- Created attachment 106586 --> https://bugs.kde.org/attachment.cgi?id=106586=edit Screenshot Attaching a screenshot of the desktop as it becomes broken. It shows both the Media Frame widget and slideshow wallpaper being replaced by a black color, whereas normally they should contain images... it's at this point that clicking on things causes Plasma to crash and restart. The only edits include me blurring the contents of a plasmoid, and adding the red text and arrows to better indicate what happens. -- You are receiving this mail because: You are watching all bug changes.
[kiten] [Bug 379679] Kiten crashes on startup
https://bugs.kde.org/show_bug.cgi?id=379679 Horacio Sansonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Horacio Sanson --- Problem has not manifested since latest update of KDE Neon. Now using Qt 5.9.1. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 371890] kded5 always crashes when running screenfetch
https://bugs.kde.org/show_bug.cgi?id=371890 Horacio Sansonchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Horacio Sanson --- Problem finally disappeared with latest KDE neon update as of yesterday. It comes with QT base 5.9.1 and KDE Frameworks 5.35.0: Package: qtbase5-dev Priority: optional Section: libdevel Installed-Size: 13081 Maintainer: Neon CI Architecture: amd64 Source: qtbase-opensource-src Version: 5.9.1+dfsg-2+16.04+xenial+build22 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Kevin Harperchanged: What|Removed |Added CC||kevinharp...@gmail.com --- Comment #20 from Kevin Harper --- Discover continues to crash for me even after installing flatpack [lex@localhost ~]$ sudo dnf history ID | Command line | Date and time| Action(s) | Altered --- 6 | install flatpack | 2017-07-12 15:51 | Install| 13 5 | install chromium | 2017-07-12 14:43 | Install|6 4 | install google-chrome-st | 2017-07-12 14:23 | Install| 123 EE 3 | update | 2017-07-12 13:49 | Update |1 2 | install gparted | 2017-07-12 11:01 | Install|1 < 1 | | 2017-07-05 15:00 | Install| 1655 >E This is a fresh install of Fedora 26 KDE and, as noted by 'dnf history', have only 3 packages (forced to do so via Konsole). [lex@localhost ~]$ uname -a Linux localhost.localdomain 4.11.9-300.fc26.x86_64 #1 SMP Wed Jul 5 16:21:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Software: KDE Plasma Version: 5.10.1 KDE Frameworks Version: 5.35.0 Qt Version: 5.7.1 Kernel Version: 4.11.9-300.fc26x86_64 OS Type: 64-bit Hardware: Processor: 8 x Intel Core i7-6700HQ CPU @ 2.60 GHz Memory: 15.5 GiB of RAM Please let me know if you need any more info from me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382288] libQt5Core5 5.9.1 introduces memory leak and plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=382288 Mircea Kitsunechanged: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382288] New: libQt5Core5 5.9.1 introduces memory leak and plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=382288 Bug ID: 382288 Summary: libQt5Core5 5.9.1 introduces memory leak and plasmashell crash Product: plasmashell Version: 5.10.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sonichedgehog_hyperblas...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Since upgrading from libQt5Core5 5.9.0 to 5.9.1, I experience two issues with plasmashell, which seem to be caused by the same core problem. The first is that the desktop causes massive memory usage. In over an hour, my system goes from using 2GB of memory (after booting and opening my applications) to approximately 8GB! However this memory is not attributed to any one process; It seems to be disk cache memory, which is further indicated by the fact that issuing the command "echo 3 > /proc/sys/vm/drop_caches" causes some of it to be freed up (not all). The second issue is that every few hours, plasmashell will crash and restart. I use an image slideshow wallpaper, and before the crash it always becomes black instead of an image... plasmashell then dies immediately after I attempt to click anything on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 328050] KMymoney does not support space as thousand separator
https://bugs.kde.org/show_bug.cgi?id=328050 --- Comment #8 from Ralf Habacker--- (In reply to Jack from comment #7) > (Candian French and Canadian English are two separate languages) > Does this only affect KMM, or is there anything at a higher level in KDE > which should be changed also? This does only affect KMM only. I kmm main function the KDE thousand separator system settings is copied into kmm, see below main.cpp 138: // setup the MyMoneyMoney locale settings according to the KDE settings 139: MyMoneyMoney::setThousandSeparator(KGlobal::locale()->monetaryThousandsSeparator()[0]); Because ' ' as thousand separator is ignored the whole application does not know anything about this value except the cases where KGlobal::locale()->monetaryThousandsSeparator() is used directly, which is 1. MyMoneyQifProfile::clear() 2. kMyMoneyMoneyValidator::validate() An interesting location is inside GncObject::hide() ... case MONEY2: in = MyMoneyMoney(data); if (data == "-1/0") in = MyMoneyMoney(); mresult = MyMoneyMoney(m_moneyHideFactor) * in; mresult.convert(1); MyMoneyMoney::setThousandSeparator(' '); result = mresult.formatMoney("", 2); break; Because ' ' is converted to '', which means no thousand separator this could be rewritten to result = mresult.formatMoney("", 2, false); The third parameter is a value for showThousandSeparator. I'm talking about code because the task is to inspect any call of formatMoney() if it falls into one of the following category: 1. used for debug output 2. used for gui output 3. used for further processing 4. used for file export Category 1. and 2. are uncritical (from my current knowledge) but the other need to be inspected and optional fixed like the mentioned example. Refactoring the above mentioned code fragment also fixes an additional bug: Because the original thousand separator is not saved and restored (as it is done in the qif reader), this piece of code kills the thousand separator in the whole application until kmymoney will be been restarted. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 328050] KMymoney does not support space as thousand separator
https://bugs.kde.org/show_bug.cgi?id=328050 Jackchanged: What|Removed |Added CC|ostroffjh@users.sourceforge | |.net| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382287] New: Places is missing in the Computer tab of the menu
https://bugs.kde.org/show_bug.cgi?id=382287 Bug ID: 382287 Summary: Places is missing in the Computer tab of the menu Product: plasmashell Version: 5.8.7 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mtm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 The Computer tab of the menu should contain an Applications and a Places list, but the latter is completely missing ever since I upgraded KDE from 4 to 5. I now tried a Fedora live CD, and that one didn't have this issue, so it's probably a configuration error. Does anyone have any idea how to fix this? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 328050] KMymoney does not support space as thousand separator
https://bugs.kde.org/show_bug.cgi?id=328050 Jackchanged: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #7 from Jack --- (Candian French and Canadian English are two separate languages) Does this only affect KMM, or is there anything at a higher level in KDE which should be changed also? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 328050] KMymoney does not support space as thousand separator
https://bugs.kde.org/show_bug.cgi?id=328050 --- Comment #6 from Ralf Habacker--- According to https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/index.html the affected languages are Canadian, German, Dansk, Finish, French and Swedish. Setting thousand separator is handled by MyMoneyMoney::setThousandSeparator() which simply ignores ' ' as separator. Changing is really simple by removing some lines inside the mentioned method. The much bigger task is to verify that removing the former "ignore" behavior does not introduce unwanted regressions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382259] Can't open picture database located at /home/egh/Pictures
https://bugs.kde.org/show_bug.cgi?id=382259 --- Comment #12 from Edward G. Howard--- where do I find the SDK setup dialog? If you let me know, I will forward the info to you. I believe this is the Microsoft Virus (EUFI) that is causing the problem. I thought I had overcome it. Digikam is working perfectly in one of my other computers with an Intel i7. I have booted with Mageia -6-rc-Live on a USB, this time, only to find the problem persists. Find the Dolphin does not show all the places (devices) as it did in previously in earlier versions. Kind regards, Edward G. Howard Registered Linux User #224802 On 12 July 2017 at 22:01, wrote: > https://bugs.kde.org/show_bug.cgi?id=382259 > > --- Comment #11 from caulier.gil...@gmail.com --- > >"mysql" is the default database used by Digikam and that is why I am using > >it. I would not mind using an alternative database if this was > recommended, > > No I want to know just if it's a local mysql database (files on hard drive > as > sqlite), or if it's a network database (as running on a NAS for ex). > > Can you go to SDK setup dialog, and give me all the settings from Database > and > Collections sections ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #266 from Leonardo Romor--- Same problem here, is not fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Leonardo Romorchanged: What|Removed |Added CC||leonardo.ro...@gmail.com --- Comment #265 from Leonardo Romor --- Same problem here, is not fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 328050] KMymoney does not support space as thousand separator
https://bugs.kde.org/show_bug.cgi?id=328050 Ralf Habackerchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||ralf.habac...@freenet.de Summary|KDE language, number and|KMymoney does not support |time option |space as thousand separator Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 --- Comment #67 from madc...@atlas.cz --- (In reply to tempel.julian from comment #64) > Thx for your efforts. > > Does this also fix the behavior that e.g. a large video file needs to get > completely copied to the client system first before it can be watched when > it is opened e.g. via Dolphin on a Samba share? > This is an important usebase, since many people store their videos on their > NAS in a local network and the current behavior is really, really > inconvenient. Every KIO slave needs to create a local copy of the remote file - this is how KIO is designed. You can always mount a remote SMB share with CIFS if you really need to work with it as if it were a local file system. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381839] surprise dependency on KEmoticons
https://bugs.kde.org/show_bug.cgi?id=381839 --- Comment #9 from RJVB--- The goal is that ultimately people port their projects to KF5 completely, build system included, no? That would favour obliging them to link with the required frameworks - something that's just a small change to the CMake files if the relevant classes indeed have the same API. But whichever approach is chosen, dependencies shouldn't be hidden like this one was. (FWIW, I probably made a bit more of a point of this because of the kind of framework we're talking about, one you cannot really call of crucial importance...) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382286] New: Connecting SkySIafari
https://bugs.kde.org/show_bug.cgi?id=382286 Bug ID: 382286 Summary: Connecting SkySIafari Product: kstars Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jcjes...@free.fr Target Milestone: --- I saw in the Profile editor that SkySafari could be a selected device. Are you talking about the SkySafari software which runs on Mac ? The INDI Control Panel says : "SkySafari server is running.Connect the App now to this machine using the SkySafari LX200 driver" In SkySafari I select Meade LX-200 Classic but nothing happened. I did obviously misunderstand something ! Please advice. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381786] Make release 4.8.1
https://bugs.kde.org/show_bug.cgi?id=381786 Bug 381786 depends on bug 382218, which changed state. Bug 382218 Summary: GPG encryption could not be enabled https://bugs.kde.org/show_bug.cgi?id=382218 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 382218] GPG encryption could not be enabled
https://bugs.kde.org/show_bug.cgi?id=382218 Ralf Habackerchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Ralf Habacker --- (In reply to Ralf Habacker from comment #2) > Additional I recognized that users are required to generate a public/private > key pair by hand (by running gpg2 --gen-key) or install an available key > pair. Without kmymoney does not allow to enable gpg support. This is common kmymoney behaviour also on linux, so nothing required to fix here. Ralf Habacker from comment #3) > This will be available tomorrow by the mingw32|64-pinentry package. Recent 32bit and 64 bit windows snapshots have working support for gpg encrypted kmymoney files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381839] surprise dependency on KEmoticons
https://bugs.kde.org/show_bug.cgi?id=381839 --- Comment #8 from Michael Pyne--- If the relevant KF5 class is source-compatible with the KDE4-based equivalent, then preferring to make it a dependency of kdelibs4support (instead of unnecessarily adding porting work with additional "K4Emoticons" classes and similar) actually seems preferable to me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 191397] digikam geolocation selection crash
https://bugs.kde.org/show_bug.cgi?id=191397 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 221458] resizing the geotag window causes crash
https://bugs.kde.org/show_bug.cgi?id=221458 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286133] digikam crashed writing geo tags
https://bugs.kde.org/show_bug.cgi?id=286133 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 212239] When leaving the geo-coordinates modify dialog, digikam crashes
https://bugs.kde.org/show_bug.cgi?id=212239 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 301122] crash when writing geolocation information
https://bugs.kde.org/show_bug.cgi?id=301122 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 213815] digikam crashes when setting geolocation
https://bugs.kde.org/show_bug.cgi?id=213815 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 220288] Digikam svn crashes at startup [mem2chunk_check, free_check, Marble::GeoDataObject::~GeoDataObject]
https://bugs.kde.org/show_bug.cgi?id=220288 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375910] Crash when Opening Geolocation Editor
https://bugs.kde.org/show_bug.cgi?id=375910 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 306878] crash after clicking Image - Geo-location
https://bugs.kde.org/show_bug.cgi?id=306878 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 214102] digikam crashes on geo info manipulation
https://bugs.kde.org/show_bug.cgi?id=214102 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376375] Strange Map icon
https://bugs.kde.org/show_bug.cgi?id=376375 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382285] New: KWin crash while installing Steam with Wine
https://bugs.kde.org/show_bug.cgi?id=382285 Bug ID: 382285 Summary: KWin crash while installing Steam with Wine Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.9.35-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Installing Steam through Wine and PlayOnLinux. I was testing some different settings and had probably installed it three times until it crashed. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe852c0d840 (LWP 1084))] Thread 7 (Thread 0x7fe81fd93700 (LWP 24808)): [KCrash Handler] #5 0x7fe85259d670 in raise () at /usr/lib/libc.so.6 #6 0x7fe85259ed00 in abort () at /usr/lib/libc.so.6 #7 0x7fe84fa23807 in () at /usr/lib/libQt5Core.so.5 #8 0x7fe83248da23 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #9 0x7fe84fc4157f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #10 0x7fe84fcbe767 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #11 0x7fe84fc4e008 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fe84fc41e2b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7fe85093d46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fe850944cf4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fe84fc12b98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7fe84fc69bae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x7fe84fc67dc2 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #21 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fe831026700 (LWP 21572)): #0 0x7fe84b80339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe84fa390eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84ac0f8d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe84ac0fd3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe81e829700 (LWP 1194)): #0 0x7fe84b80339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe84eb91ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fe84eb91b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe82bfff700 (LWP 1152)): #0 0x7fe85264d326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe84fc66471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84fc67b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe84a51d645 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8526571ef in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe832eb1700 (LWP 1129)): #0 0x7fe85264d326 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe84fc66471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe84fc67b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe84fc1121a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe84fa3340a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe8496c2d45 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fe84fa37cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84b7fd297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe8526571ef in clone () at
[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed
https://bugs.kde.org/show_bug.cgi?id=381815 Rhys Kiddchanged: What|Removed |Added Version|unspecified |3.14 SVN Status|UNCONFIRMED |CONFIRMED Assignee|jsew...@acm.org |rhysk...@gmail.com Ever confirmed|0 |1 Platform|unspecified |Mac OS X Disk Images CC||rhysk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 347323] Add support for changing cursor shape with extended DECSCUSR escape sequences
https://bugs.kde.org/show_bug.cgi?id=347323 Egmont Koblingerchanged: What|Removed |Added CC||egm...@gmail.com --- Comment #1 from Egmont Koblinger --- Yup gnome-terminal also supports these sequences. Note that while more "standard" than the iTerm2 ones, these sequences kinda suck because most of the time an app wants to touch only the shape or only the blinking property, not both, which cannot be done with these sequences. It's a better design to have separate sequences for the two. Also, for each, there should be a way to revert to the terminal emulator's default as specified in its config. The '\e[1 q' .. '\e[6 q' sequences are implemented in xterm and vte (gnome-terminal etc.) identically. In xterm, the number 0 or omitting the number is the same as number 1. In vte we intentionally differ, the number 0 or omitting the number means to revert to the default (the shape is taken from profile prefs, blinking is from GNOME-wide setting). -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 376893] Bad performance of kaffeine when watching HD channels compared to VLC and other players
https://bugs.kde.org/show_bug.cgi?id=376893 yuli...@mailbox.org changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from yuli...@mailbox.org --- I just freshly installed the new Fedora 26 and compiled kaffeine from git. In my case there is no difference between git and the last version, but it is pretty smooth most of the time now. This has nothing to do with changes of kaffeine, though. The problem was the VDPAU package, that should actually accelerate the video processing. Because after installing the package mesa-vdpau-drivers and enable it via "$ export VDPAU_DRIVER=r600" (known bug in fedora, see e.g. [1]), it starts stuttering. After removing the package it works okay again. Although all 4 cores are at ~100%. Maybe also other changes of the new system are relevant. So it seems not to be a problem of kaffeine alone, but more like a problem of VDPAU. Or the use of VDPAU of libVLC when the used codec is not supported. VDPAU on my GPU does not support H.265. But as VDPAU development seems not very active any more and my hardware is also relatively "old", probably it's not worth to investigate further. Thanks! [1] https://bugzilla.redhat.com/show_bug.cgi?id=1305699 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 154098] bugs in ftp protocol handler, when using proxy
https://bugs.kde.org/show_bug.cgi?id=154098 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 358139] "Open with" dialog's input field should also search in "Known Applications" tree
https://bugs.kde.org/show_bug.cgi?id=358139 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 230367] KIO FTP uses HTTP proxy
https://bugs.kde.org/show_bug.cgi?id=230367 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382239] QUrl::path() returns invalid pathes on Windows
https://bugs.kde.org/show_bug.cgi?id=382239 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 359233] Improve usability of "Open with > Other" file dialog
https://bugs.kde.org/show_bug.cgi?id=359233 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382284] New: Photo jpg failed to open and caused an error
https://bugs.kde.org/show_bug.cgi?id=382284 Bug ID: 382284 Summary: Photo jpg failed to open and caused an error Product: dolphin Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: pinstriped...@yahoo.com Target Milestone: --- I got the following message (after brand new install of Mint KDE 18.0) when clicking on a jpg file to open and view a photo. Copied and pasted: There are two actions (Cut, Delete) that want to use the same shortcut (Shift+Del). This is most probably a bug. Please report it in bugs.kde.org My pc is a Dell Opti-Plex 760 with 8 gigs mem and an 128gb SSD. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 382242] Deprecated hint for KUrl::path() is wrong on Windows
https://bugs.kde.org/show_bug.cgi?id=382242 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 333484] Rabet does not appear on screen the second time Marble is launched
https://bugs.kde.org/show_bug.cgi?id=333484 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 382280] KRunner cannot be opened after pressing Escape key on Wayland
https://bugs.kde.org/show_bug.cgi?id=382280 --- Comment #1 from Martin Flöser--- I modified RunCommand.qml to contain Keys.onEscapePressed: { runnerWindow.visible = false console.log("escape pressed") } and as soon as Escape is pressed the log is printed till eternity. I assume a Qt bug, will create minimal test case tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381848] unable to revert to xserver-xorg-video-intel driver
https://bugs.kde.org/show_bug.cgi?id=381848 --- Comment #1 from PK--- I think it should be possible to go back. Here https://packaging.neon.kde.org/neon/xserver-xorg-video-intel-native-modesetting.git/plain/debian/control I read: If you experience graphics problems installing xserver-xorg-video-intel will install the actual xorg driver for Intel GPUs and might improve results But to my regret that is NOT the way it works -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382283] KWin X11 crashes sometimes
https://bugs.kde.org/show_bug.cgi?id=382283 --- Comment #2 from tesfab...@gmail.com --- I know but this time drkonqi said that backtraces were useful and gave 3 stars so I tried... :( I will try again after recompiling with debug symbols... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382283] KWin X11 crashes sometimes
https://bugs.kde.org/show_bug.cgi?id=382283 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- As always backtraces from Arch are useless. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 382107] kdevplatform FTBFS due to missing __cpu_model
https://bugs.kde.org/show_bug.cgi?id=382107 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381839] surprise dependency on KEmoticons
https://bugs.kde.org/show_bug.cgi?id=381839 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381967] Some lens metadata lost in converting into DNG
https://bugs.kde.org/show_bug.cgi?id=381967 --- Comment #2 from Octopuss--- Hi, Sorry for delay. I can add an example RAW(CR2) and the resulting DNG with the issue. CR2: https://www.dropbox.com/s/y647nngjsonim5h/IMG_6963.CR2?dl=0 DNG: https://www.dropbox.com/s/ximzsacv82g9nz2/IMG_6963.dng?dl=0 Please, let me know when the files are not needed anymore. Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 371673] KMix crashed on login.
https://bugs.kde.org/show_bug.cgi?id=371673 --- Comment #3 from Mad--- This log show from start kmix to exit kmix. On exit the app crash. https://pastebin.com/zPxFMaE9 Regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 382198] No ftp connection after update: "the proxy type is invalid for this operation"
https://bugs.kde.org/show_bug.cgi?id=382198 Rafaelchanged: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #1 from Rafael --- I discovered that, despite I have proxy only for HTTP and HTTPS (and left FTP only with "http://; as all this years ago), if I disable "Enable proxy", ftp is working but not http and https, obviously, so is clear there is a bug similar to bug https://bugs.kde.org/show_bug.cgi?id=154098 or https://bugs.kde.org/show_bug.cgi?id=230367 . Please, fix this bug. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381922] The geometric shapes don't allow choosing the foreground/background color for the stroke.
https://bugs.kde.org/show_bug.cgi?id=381922 Quiraltachanged: What|Removed |Added CC||rjquira...@gmail.com --- Comment #1 from Quiralta --- There would be also very practical to have the "no outline" option applied to the creation of shapes, as it is right now, shapes can be created with out fill color but not without outline. Commenting it here as I think this is an extension of this functionality topic. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381935] When copy-pasting a flower shape, the pasted shape is a regular path.
https://bugs.kde.org/show_bug.cgi?id=381935 Quiraltachanged: What|Removed |Added CC||rjquira...@gmail.com --- Comment #1 from Quiralta --- I think that I experience extra symptoms from this bug, the ellipse and rectangle tool's shapes as svg also suffer from this same situation, will paste as the original shape even after they been converted to path and reshaped their nodes. I also notice that this happens after reopening a document saved with modified shapes, they will revert to its original form. Shapes created with the bezier curve tool do not suffer from this. Tried this on git master build also. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382271] Network
https://bugs.kde.org/show_bug.cgi?id=382271 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Elvis Angelaccio --- The next version of kio-extras will have better samba support. *** This bug has been marked as a duplicate of bug 376344 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 Elvis Angelacciochanged: What|Removed |Added CC||roduffy2...@yahoo.co.uk --- Comment #66 from Elvis Angelaccio --- *** Bug 382271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 --- Comment #65 from Elvis Angelaccio--- (In reply to tempel.julian from comment #64) > Thx for your efforts. > > Does this also fix the behavior that e.g. a large video file needs to get > completely copied to the client system first before it can be watched when > it is opened e.g. via Dolphin on a Samba share? No, and that's likely not going to happen any time soon (no one is working on it). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 359233] Improve usability of "Open with > Other" file dialog
https://bugs.kde.org/show_bug.cgi?id=359233 --- Comment #8 from Simone Gaiarin--- I've submitted a patch to solve the point number 3, app tree filtering. https://git.reviewboard.kde.org/r/130179/ -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382282] Name changes of the "else" alternative on combined fragment is not saved
https://bugs.kde.org/show_bug.cgi?id=382282 --- Comment #1 from Ralf Habacker--- This bug has nearly the same reason as bug 382279 e.g. an additonal if (m_pInstanceWidget->isFloatingDashLineWidget()) ... should fix this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368952] Full screen does not restore to maximized correctly on Windows
https://bugs.kde.org/show_bug.cgi?id=368952 woltherachanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #16 from wolthera --- This is fixed in https://phabricator.kde.org/R37:073305f63844ec1e2e416ca0af8813dde06af23c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382283] New: KWin X11 crashes sometimes
https://bugs.kde.org/show_bug.cgi?id=382283 Bug ID: 382283 Summary: KWin X11 crashes sometimes Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tesfab...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.3) Qt Version: 5.9.1 Frameworks Version: 5.35.0 Operating System: Linux 4.11.7-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Sometimes when opening some apps (mostly Chrome, Steam, and others) or doing some other things, kwin crashes. I'm using ArchLinux x64 and NVIDIA proprietary graphics drivers 381.22 (sorry about that :() The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f1de7d840 (LWP 1189))] Thread 5 (Thread 0x7f0f008fe700 (LWP 2280)): #0 0x7f0f1d928326 in ppoll () at /usr/lib/libc.so.6 #1 0x7f0f1af471a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f0f1af488be in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f0f1aef0efa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f0f1ad1079a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f0f1ad1537d in () at /usr/lib/libQt5Core.so.5 #6 0x7f0f16ad9297 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f0f1d9321ef in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f0ee9986700 (LWP 1411)): #0 0x7f0f16adf39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0f19e6db04 in () at /usr/lib/libQt5Script.so.5 #2 0x7f0f19e6db49 in () at /usr/lib/libQt5Script.so.5 #3 0x7f0f16ad9297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f0f1d9321ef in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f0f0215d700 (LWP 1304)): #0 0x7f0f1d928326 in ppoll () at /usr/lib/libc.so.6 #1 0x7f0f1af471a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f0f1af488be in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f0f1aef0efa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f0f1ad1079a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f0f1499ad45 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f0f1ad1537d in () at /usr/lib/libQt5Core.so.5 #7 0x7f0f16ad9297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f0f1d9321ef in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f0f04389700 (LWP 1201)): #0 0x7f0f1d92824d in poll () at /usr/lib/libc.so.6 #1 0x7f0f1ca118e0 in () at /usr/lib/libxcb.so.1 #2 0x7f0f1ca13679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f0f0546de99 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f0f1ad1537d in () at /usr/lib/libQt5Core.so.5 #5 0x7f0f16ad9297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f0f1d9321ef in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f0f1de7d840 (LWP 1189)): [KCrash Handler] #5 0x7f0f1d878670 in raise () at /usr/lib/libc.so.6 #6 0x7f0f1d879d00 in abort () at /usr/lib/libc.so.6 #7 0x7f0f1ad002c7 in () at /usr/lib/libQt5Core.so.5 #8 0x7f0f1ad0f6ed in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #9 0x7f0f1ad0f749 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #10 0x7f0f1af1f40b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #11 0x7f0f1af28d9b in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #12 0x7f0f01738309 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #13 0x7f0f1af1f40b in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #14 0x7f0f1af28d9b in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #15 0x7f0f1aef4b76 in QCoreApplication::~QCoreApplication() () at /usr/lib/libQt5Core.so.5 #16 0x7f0f1bc18ec9 in QApplication::~QApplication() () at /usr/lib/libQt5Widgets.so.5 #17 0x7f0f1dbf1743 in () at /usr/lib/libkdeinit5_kwin_x11.so #18 0x7f0f1dbf3029 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so #19 0x7f0f1d86543a in __libc_start_main () at /usr/lib/libc.so.6 #20 0x0040069a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 376804] "Else" part outside of alternative combined fragment on creation
https://bugs.kde.org/show_bug.cgi?id=376804 --- Comment #2 from Ralf Habacker--- How to debug: 1. Compile umbrello with debug informations (the easiest way is on linux) 2. Set a breakpoint at the line mentioned below 3. start umbrello 4. add a sequence diagram 5. add a combined fragment, choose "Alternative" and press okay 6. the debugger will stop at the mentioned breakpoint and you can inspect what happens with the coordinate settings of the related m_dashLines. You need to get familiar with QGraphicsScene and its coordinate system and handling to be able to understand what goes wrong. void CombinedFragmentWidget::setCombinedFragmentType(CombinedFragmentType combinedfragmentType) { m_CombinedFragment = combinedfragmentType; UMLWidget::m_resizable = true ; //(m_CombinedFragment == Normal); // creates a dash line if the combined fragment type is alternative or parallel if (m_CombinedFragment == Alt && m_dashLines.isEmpty()) ...< here set breakpoint -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 380879] [Qt 5.9] Konsole tabbar does not have empty space at the right side anymore
https://bugs.kde.org/show_bug.cgi?id=380879 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382279] Name change of combined fragment first alternative is not saved
https://bugs.kde.org/show_bug.cgi?id=382279 Ralf Habackerchanged: What|Removed |Added Summary|Name changes of alternate |Name change of combined |combinded fragment are not |fragment first alternative |saved |is not saved -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382282] Name changes of the "else" alternative on combined fragment is not saved
https://bugs.kde.org/show_bug.cgi?id=382282 Ralf Habackerchanged: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382282] New: Name changes of the "else" alternative on combined fragment is not saved
https://bugs.kde.org/show_bug.cgi?id=382282 Bug ID: 382282 Summary: Name changes of the "else" alternative on combined fragment is not saved Product: umbrello Version: 2.22.3 (KDE Applications 17.04.3) Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- How to reproduce ? 1. start umbrello 2. add a sequence diagram 3. select "combined fragment" from the toolbox 4. Choose "Alternative" 5. press okay and enter something as text for the first alternative, then press okay again 6. Double click on the "else text of the combined fragment 7. Change the text in the first edit widget after the "floating dashline" label from 'else' to 'else12345'. 8 press okay What happens ? The text of the second alternative has not been changed; it still shows 'else'. What is expected ? The text of the second alternative should be 'else12345'. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 382281] New: Can't close any active connection upon losing connection to a VPN server
https://bugs.kde.org/show_bug.cgi?id=382281 Bug ID: 382281 Summary: Can't close any active connection upon losing connection to a VPN server Product: frameworks-networkmanager-qt Version: 5.36.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: redredempt...@protonmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- The latest updates for networkmanager packages causes the QT networkmanager wrapper/applet to be unresponsive upon losing connection to any VPN server. Neither pressing disconnect to close connection to VPN, nor turn off internet connection doesn't do any action. Restarting the NetworkManager daemon manually by the systemctl command doesn't help. The only way to fix it temporarily is to restart a Xorg session. "networkmanager (1.8.0-1 -> 1.8.2-1) networkmanager-qt (5.35.0-1 -> 5.36.0-1)" The bug is reproducible sometimes; it doesn't happen every time I lose connection to a VPN server. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 382280] New: KRunner cannot be opened after pressing Escape key on Wayland
https://bugs.kde.org/show_bug.cgi?id=382280 Bug ID: 382280 Summary: KRunner cannot be opened after pressing Escape key on Wayland Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: mgraess...@kde.org Target Milestone: --- Steps to reproduce: 1. open KRunner through alt+space 2. dismiss KRunner through Escape 3. open KRunner through alt+space Actual behavior: Krunner slides in and out immediately Expected behavior: KRunner slides in and can be used This only happens with Escape key, if dismissed through close button click, or click outside or launching an item, KRunner opens fine again. This might be an issue in Qt 5.9 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382279] Name changes of alternate combinded fragment are not saved
https://bugs.kde.org/show_bug.cgi?id=382279 Ralf Habackerchanged: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Ralf Habacker --- The problem is located in ClassGeneralPage::apply() in the else if (m_pInstanceWidget) { ... case where something like the following text should be added if (!o) { + if (m_pInstanceWidget->isCombinedFragmentWidget()) { + m_pInstanceWidget->setName(name); + return; + } -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 382279] New: Name changes of alternate combinded fragment are not saved
https://bugs.kde.org/show_bug.cgi?id=382279 Bug ID: 382279 Summary: Name changes of alternate combinded fragment are not saved Product: umbrello Version: 2.22.3 (KDE Applications 17.04.3) Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- How to reproduce ? 1. start umbrello 2. add a sequence diagram 3. select "combined fragment" from the toolbox 4. Choose "Alternate" 5. press okay and enter text '12345' for the first alternative 6. Double click on the combined fragment 7. change the text in the first edit widget after the "combined fragment" label from '12345' to '12345678'. 8 press okay What happens ? The text of the first alternative has not been changed, it still shows '12345'. What is expected ? The text of the first alternative should be '12345678'. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 382261] Does not pick color
https://bugs.kde.org/show_bug.cgi?id=382261 Kai Uwe Broulikchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||plasma-addons/0ed491a1b0f10 ||13bfd239ba1dc41210144c23e25 Version Fixed In||5.10.4 --- Comment #5 from Kai Uwe Broulik --- Git commit 0ed491a1b0f1013bfd239ba1dc41210144c23e25 by Kai Uwe Broulik. Committed on 12/07/2017 at 16:11. Pushed by broulik into branch 'Plasma/5.10'. [Color Picker] Fix picking colors in multi-screen Simplifies code and also grab just one pixel instead of the entire screen. FIXED-IN: 5.10.4 Differential Revision: https://phabricator.kde.org/D6639 M +9-8applets/colorpicker/plugin/grabwidget.cpp https://commits.kde.org/kdeplasma-addons/0ed491a1b0f1013bfd239ba1dc41210144c23e25 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378508] when remove panel applet plasma crashed
https://bugs.kde.org/show_bug.cgi?id=378508 Kai Uwe Broulikchanged: What|Removed |Added Version Fixed In||5.8.8 Status|REOPENED|RESOLVED Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-framework/6ffe068b80143 |sma-workspace/8a05294e5b3ef |ba92cae6eaddf1bcd42c5ff4bed |1df86f099edde837b8c8d28ccaf Resolution|--- |FIXED --- Comment #30 from Kai Uwe Broulik --- Git commit 8a05294e5b3ef1df86f099edde837b8c8d28ccaf by Kai Uwe Broulik. Committed on 12/07/2017 at 16:08. Pushed by broulik into branch 'Plasma/5.8'. [Notifications] Check for corona to avoid crash My previous attempt only fixed the case when notifications were directly in a panel. Now it also no longer crashes when removing a panel that has a System Tray with the notifications applet in it. FIXED-IN: 5.8.8 Differential Revision: https://phabricator.kde.org/D6653 M +1-1applets/notifications/lib/notificationsapplet.cpp https://commits.kde.org/plasma-workspace/8a05294e5b3ef1df86f099edde837b8c8d28ccaf -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 382253] Akonadi restart required to see new email in kmail
https://bugs.kde.org/show_bug.cgi?id=382253 --- Comment #1 from thatskinnywhiteguy+...@gmail.com --- It's a little hard to be sure when exactly things stop working, but there's some evidence that suggests that the last two lines (quoted again below) indicate what's actually breaking. That is, when they're there, it seems that the email sync no longer functions. Until they appear, it seems to work properly. org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" org.kde.pim.akonadicore: Error during ItemSync: "Multiple merge candidates, aborting" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381447] Kickoff opens with Super_L (left win) even when using "Left Alt as Ctrl, Left Ctrl as Win, Left Win as Alt"
https://bugs.kde.org/show_bug.cgi?id=381447 --- Comment #2 from Mario Aichinger--- That is strange! I just (5 minutes ago) downgraded kwin and some other packages (plasma-desktop, plasma-integration, plasma-sdk, plasma-workspace, and plasma-nm just so stuff would not break) from 5.10.3 to 5.8.2 and now it works as I described it in the bug report. Just to clear things up I first downgraded the plasma stuff then tested it (it didn't work) and then kwin to make sure that kwin is the relevant part. I didn't change anything else. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363788] Fit to page printing does incorrect scaling and unwanted offsetting
https://bugs.kde.org/show_bug.cgi?id=363788 Sergiochanged: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #14 from Sergio --- Unconditionally trying to fit the document to the page side is not always the sensible thing to do. For instance, if you have a photo in a PDF document, and that is smaller than the paper in your printer, you cannot put it on paper at its intended size. Okular should provide the options to: - Do not scale - Fit to page - Reduce to page As almost all PDF readers do. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382177] Anytime I try to save a file Nothing happens and the save window stays open
https://bugs.kde.org/show_bug.cgi?id=382177 Shlomi Fishchanged: What|Removed |Added CC||shlo...@shlomifish.org --- Comment #1 from Shlomi Fish --- Reportedly it works fine on windows 10, and it works fine here with the latest .appimage on x86-64 linux. Can you try updating and try again? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357574] KDevelop can't find tests/executables when EXECUTABLE_OUTPUT_PATH is set
https://bugs.kde.org/show_bug.cgi?id=357574 --- Comment #3 from Aleix Pol--- Git commit 3c1fd1f09e6002994c17c78ac3efe792bf560fe9 by Aleix Pol. Committed on 12/07/2017 at 15:38. Pushed by apol into branch 'master'. Properly initialize a test's executable M +1-1projectmanagers/cmake/cmakemanager.cpp M +1-1projectmanagers/cmake/cmakeprojectdata.h M +1-1projectmanagers/cmake/cmakeutils.cpp M +15 -20 projectmanagers/cmake/testing/ctestutils.cpp M +1-1projectmanagers/cmake/testing/ctestutils.h M +2-1projectmanagers/cmake/tests/manual/randomexe/CMakeLists.txt M +15 -1projectmanagers/cmake/tests/test_cmakemanager.cpp https://commits.kde.org/kdevelop/3c1fd1f09e6002994c17c78ac3efe792bf560fe9 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375979] Akonadi sqlite backend crashes Akonadi, incompatible qt versions
https://bugs.kde.org/show_bug.cgi?id=375979 --- Comment #7 from Christoph Feck--- Needs a rebuild of akonadi again after update to Qt 5.9.1. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing
https://bugs.kde.org/show_bug.cgi?id=347022 Nicholas Killewaldchanged: What|Removed |Added CC||captains...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382241] Application menu crashes plasmashell on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=382241 --- Comment #2 from bug2...@wolke7.net --- Created attachment 106584 --> https://bugs.kde.org/attachment.cgi?id=106584=edit log of running plasmashell in gdb I've killed the plasmashell and started it from the debugger. The log contains two runs. In the first onethe shell terminated with: "The Wayland connection broke. Did the Wayland compositor die?" On the second run the QSGRenderThread SIGSEGV somewhere in mesa EGL code. It crashed while the application menu was open and the mouspointer above one of the categories. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382278] New: Adding disk usage widget to desktop panel crashes plama
https://bugs.kde.org/show_bug.cgi?id=382278 Bug ID: 382278 Summary: Adding disk usage widget to desktop panel crashes plama Product: plasmashell Version: 5.10.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: michv...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.12.0-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Moved disk usage widget (dont know the exact english name the german is "Festplattenbelegung", should be something like disk usage) from desktop to panel and try to move it back. This will crash plasma. If you try again, then it works. If you try then again, it crashes again. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa8477fd80 (LWP 1546))] Thread 12 (Thread 0x7fa996df4700 (LWP 13045)): #0 0x7faa7ddd524d in poll () at /usr/lib/libc.so.6 #1 0x7faa78990bf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7faa78990d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7faa7e6fde9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7faa7e6a421a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faa7e4c640a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7faa81635645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7faa7e4cacbd in () at /usr/lib/libQt5Core.so.5 #8 0x7faa7d693297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7faa7dddf1ef in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa997fff700 (LWP 7761)): #0 0x7faa789d5a44 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7faa78990128 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7faa78990b2b in () at /usr/lib/libglib-2.0.so.0 #3 0x7faa78990d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7faa7e6fde9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faa7e6a421a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7faa7e4c640a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7faa81635645 in () at /usr/lib/libQt5Qml.so.5 #8 0x7faa7e4cacbd in () at /usr/lib/libQt5Core.so.5 #9 0x7faa7d693297 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7faa7dddf1ef in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa9aa5ae700 (LWP 1648)): #0 0x7faa7e6fd3a4 in () at /usr/lib/libQt5Core.so.5 #1 0x7faa78990601 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7faa78990ba0 in () at /usr/lib/libglib-2.0.so.0 #3 0x7faa78990d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7faa7e6fde9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faa7e6a421a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7faa7e4c640a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fa9ac1d3427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7faa7e4cacbd in () at /usr/lib/libQt5Core.so.5 #9 0x7faa7d693297 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7faa7dddf1ef in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fa9bfbba700 (LWP 1645)): #0 0x7faa7ddd524d in poll () at /usr/lib/libc.so.6 #1 0x7faa78990bf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7faa78990d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7faa7e6fde9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7faa7e6a421a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faa7e4c640a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7faa7e4cacbd in () at /usr/lib/libQt5Core.so.5 #7 0x7faa7d693297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7faa7dddf1ef in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fa9c03bb700 (LWP 1644)): #0 0x7faa7ddd524d in poll () at /usr/lib/libc.so.6 #1 0x7faa78990bf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7faa78990d0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7faa7e6fde9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7faa7e6a421a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faa7e4c640a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa9c09743c5 in () at
[KScreen] [Bug 382277] New: Scale display below 1
https://bugs.kde.org/show_bug.cgi?id=382277 Bug ID: 382277 Summary: Scale display below 1 Product: KScreen Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- The scale in Scale display option should allow for values below 1. Without it, we are only able to work around with the xrand option --scale which is not optimal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381839] surprise dependency on KEmoticons
https://bugs.kde.org/show_bug.cgi?id=381839 --- Comment #7 from RJVB--- I've always seen the main role of KDELibs4Support to provide wrappers for or implementations of old, deprecated classes, not to provide a Qt5-based rewrite of KDELibs... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling
https://bugs.kde.org/show_bug.cgi?id=382276 --- Comment #3 from David Edmundson--- >It is important to note that this would not be necessary if the Scale (in >System Settings -> Display and Monitor -> Scale Display) accepted values below >1. How would that help? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381839] surprise dependency on KEmoticons
https://bugs.kde.org/show_bug.cgi?id=381839 --- Comment #6 from Christoph Feck--- Yes, that's intententionally. Developers can do a quick port using KDELibs4Support, or they can check the exact dependencies for each class they were using and stop linking to KDELibs4Support. Since KDELibs4Support depends on kio, it actually drags in most frameworks that were part of kdelibs4. The exceptions are kemoticons and kunitconversion. That's why these needed to be explicit dependencies. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 382096] KDevelop crash when activating split mode via the tabbar context menu
https://bugs.kde.org/show_bug.cgi?id=382096 Friedrich W. H. Kossebauchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||vplatform/9df0a5bf75cc0e6a0 ||3655b392d4f43f92faabd25 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Friedrich W. H. Kossebau --- Git commit 9df0a5bf75cc0e6a03655b392d4f43f92faabd25 by Friedrich W. H. Kossebau. Committed on 12/07/2017 at 14:30. Pushed by kossebau into branch '5.1'. Fix crash on view split action invoked from tabbar context menu Reviewers: #kdevelop, kfunk Reviewed By: #kdevelop, kfunk Subscribers: graesslin, kfunk, kdevelop-devel Differential Revision: https://phabricator.kde.org/D6625 M +21 -10 sublime/container.cpp https://commits.kde.org/kdevplatform/9df0a5bf75cc0e6a03655b392d4f43f92faabd25 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling
https://bugs.kde.org/show_bug.cgi?id=382276 --- Comment #2 from Raul Kde Bugzilla--- The display card is a NVidia. Driver: nvidia-375 Kubuntu (ubuntu + kubuntu backports) 17.04 About the Screenshot, the black area in the left is where plasma fails to see and use. Note the "add widgets" button on the top right, not being in the top right. Also note that I am able to use this space fine, as I placed a konsole terminal in there. The black area in the top of the right display is correct, as there is an height offset between the two displays to match the physical position. -- You are receiving this mail because: You are watching all bug changes.