[kwin] [Bug 373091] Plasma crashed while switching windows
https://bugs.kde.org/show_bug.cgi?id=373091 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is (as always with Arch) lacking debug symbols. We see that it crashes, but not where and why. There is nothing we can do to investigate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373089] KWin crashed several times on virtual desktop switching
https://bugs.kde.org/show_bug.cgi?id=373089 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is (as always with Arch) lacking debug symbols. We see that it crashes, but not where and why. There is nothing we can do to investigate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373078] KWin wayland freezes when clicking on the kickoff
https://bugs.kde.org/show_bug.cgi?id=373078 --- Comment #3 from Martin Gräßlin--- Best option would be to ssh in from another system -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before
https://bugs.kde.org/show_bug.cgi?id=371990 --- Comment #22 from Ralf Habacker--- (In reply to clushkou from comment #20) > I tried to fulfill your request in comment #17, but do not understand how to > achieve this. If I simply move the calls to ComponentWidget, I get a crash > on undo because restoring of child element does not work. > In addition, if the code needs to be added to ComponentWidget, the same > adaption is needed in all widgets that allow child Pins / Ports. I see. For the record: umbrello uses saveToXMI and loadFromXMI() to handle xmi file save/load, object (de)serialisation on copy/paste between same and other umbrello instances and undo framework so it would be nice to hold related stuff together and to implement stuff in the same way if possible to reduce req What I did: I created a component widget with ports and saved it into a xmi file. Inspecting this file shows that the component widget and the pin widgets does not have any direct association. The association is performed by the related UML:Component which has UML:Port as child. The in-memory representation changes this behavior by adding a direct association former with m_pow and now this QGraphicsItem child api. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373100] Deleting duplicate image in "Find duplicates" removes all other found duplicates
https://bugs.kde.org/show_bug.cgi?id=373100 --- Comment #2 from Mario Frank--- (In reply to Kristian Karl from comment #1) > I noticed afterwards that step 8) is not necessary. Hi, I stumbled over this one yesterday, too. This dysfunction was not present before. Will trace it today. The other duplicate albums are cleared since when the image is deleted, a rescan of duplicates is done. What I found is that if you apply your steps, you should see a progress bar which does not increase its value. Can you confirm this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373102] Changing "run as user" option for program is not reflected in Kicker
https://bugs.kde.org/show_bug.cgi?id=373102 --- Comment #1 from opensuse.lietuviu.ka...@gmail.com --- Created attachment 102542 --> https://bugs.kde.org/attachment.cgi?id=102542=edit video.webm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373100] Deleting duplicate image in "Find duplicates" removes all other found duplicates
https://bugs.kde.org/show_bug.cgi?id=373100 Mario Frankchanged: What|Removed |Added CC||mario.fr...@uni-potsdam.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373102] New: Changing "run as user" option for program is not reflected in Kicker
https://bugs.kde.org/show_bug.cgi?id=373102 Bug ID: 373102 Summary: Changing "run as user" option for program is not reflected in Kicker Product: plasmashell Version: 5.8.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: opensuse.lietuviu.ka...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 In KDE Plasma 5 Kicker menu, I changed properties of program to run it as root. But then I re-enter in settings, these changes looks not saved; also running program via Kicker still runs as regular user. However, ~/.local/share/applications/*.desktop file is changed and running it directly – will ask for root password. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373101] Incorrect reflection for cylinder animation (it uses cube reflection causing it to separate at edge)
https://bugs.kde.org/show_bug.cgi?id=373101 --- Comment #3 from David Rankin--- Created attachment 102541 --> https://bugs.kde.org/attachment.cgi?id=102541=edit cylinder reflection looking straight-on desktop showing reflection with cylinder looking straight-on the desktop (as it should be, it is attached at the bottom desktop edge) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373101] Incorrect reflection for cylinder animation (it uses cube reflection causing it to separate at edge)
https://bugs.kde.org/show_bug.cgi?id=373101 --- Comment #2 from David Rankin--- Created attachment 102540 --> https://bugs.kde.org/attachment.cgi?id=102540=edit cylinder rotation between desktops (reflection detached) Showing the reflection detached from cylinder rotation between desktops (moving down away from the cylinder because it is using the cube rotation code) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373101] Incorrect reflection for cylinder animation (it uses cube reflection causing it to separate at edge)
https://bugs.kde.org/show_bug.cgi?id=373101 --- Comment #1 from David Rankin--- Created attachment 102539 --> https://bugs.kde.org/attachment.cgi?id=102539=edit cube reflection between desktops showing proper reflection attachment at the corner of desktops with cube rotation -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373101] New: Incorrect reflection for cylinder animation (it uses cube reflection causing it to separate at edge)
https://bugs.kde.org/show_bug.cgi?id=373101 Bug ID: 373101 Summary: Incorrect reflection for cylinder animation (it uses cube reflection causing it to separate at edge) Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: drankina...@suddenlinkmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 102538 --> https://bugs.kde.org/attachment.cgi?id=102538=edit cube reflection looking straight-on at the desktop If this should go with some other component, feel free to change the selected component, there isn't a desktop effects choice. When using the cylinder animation (with zoom set at roughly 1/4), the reflection bounces up and down below the cylinder on rotation. Meaning, with reflection enabled, when you invoke the cylinder animation (e.g. win+F11 key) and tilt the cylinder toward, or away, from you about 15-20 degrees, you find the reflection properly bound to the lower edge of the desktop. Now, if you rotate the cylinder 45 degrees left/right so you are looking at the divider between desktop 1/2 (or 4/1) you see the reflection is now detached from the cylinder and it has moved down (and sometimes off the screen) depending on the amount you have the cylinder tilted toward or away from you. If you rotate the cylinder (make it spin slowly), the reflection hops up-and-down at the bottom of the screen. Why? The 'cube' reflection code is being used for the 'cylinder' rotation. That's not right -- they are separate pieces of code. Why? with the 'cylinder', the reflection distance from the cube does NOT change with rotation angle (you are rotating a circle, (the radius never changes), but with the 'cube' it does (e.g. the perpendicular distance from the center to the front edge is shorter than the distance from the center of the cube to the corner between virtual desktops) Now go perform the same test with the 'cube' animation. The reflection moves up and down to stay attached to the cube rotation as it should, both when viewing a desktop straight-on (see: cube_reflection_desktop.png) and between desktops (see: cube_reflection_corner.png) Now do it with the cylinder. The reflection is attached when viewing the desktop straight-on (see: cylinder_reflection_desktop.png), but detaches from the cylinder between desktops (see: cylinder_reflection_corner.png) The reflection should remain attached at all points during the rotation, because the distance from the center of the cylinder to the edge never changes. It looks like somebody simply forgot to implement the cylinder rotation code from compiz (it's actually much simpler than the cube model), or it may be there, but all rotations are using the cube code for rotation (I haven't tested the sphere, it has more serious issues with the skydome deformation bug), but I suspect it is using the cube rotation code as well for reflection control. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373081] kmail2 doesn't render messages correctly with HiDPI
https://bugs.kde.org/show_bug.cgi?id=373081 Andreas Schneiderchanged: What|Removed |Added Assignee|kdepim-b...@kde.org |mon...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373081] kmail2 doesn't render messages correctly with HiDPI
https://bugs.kde.org/show_bug.cgi?id=373081 --- Comment #1 from Andreas Schneider--- Kmail version 5.3.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373100] Deleting duplicate image in "Find duplicates" removes all other found duplicates
https://bugs.kde.org/show_bug.cgi?id=373100 --- Comment #1 from Kristian Karl--- I noticed afterwards that step 8) is not necessary. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365327] Support macOS Sierra (10.12)
https://bugs.kde.org/show_bug.cgi?id=365327 --- Comment #9 from Rhys Kidd--- Apple have just this week finally released the source code for critical system components that shipped in macOS Sierra (10.12). This includes xnu, the kernel. https://opensource.apple.com/release/macos-1012.html -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373100] New: Deleting duplicate image in "Find duplicates" removes all other found duplicates
https://bugs.kde.org/show_bug.cgi?id=373100 Bug ID: 373100 Summary: Deleting duplicate image in "Find duplicates" removes all other found duplicates Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Searches-Fuzzy Assignee: digikam-de...@kde.org Reporter: kristian.hermann.k...@gmail.com Target Milestone: --- Created attachment 102537 --> https://bugs.kde.org/attachment.cgi?id=102537=edit Screenshot When removing a duplicate image, all other found duplicates are removed. 1) Create a folder 'bug_test'. 2) In folder 'bug_test', put some images in there. (I used these: http://snippets.khromov.se/wp-content/uploads/2013/08/stock_pictures_from_morguefile.zip from: https://snippets.khromov.se/stock-photo-archive-zip-77-images/ 3) In folder 'bug_test', create another folder called 'dupes'. Copy some images from step 2) and put them into 'bug_test'. 4) Start digikam in folder 'bug_test': 'digikam --database-directory .' 5) Add folder 'bug_test' as a collection. 6) Open view 'Fuzzy' 7) In tab 'Duplicates' do 'Update fingerprints'. 8) Set 'Similarity range:' to from 100% to 100%. 9) Click button 'Find duplicates' 10) When done, select the first pair of duplicates in the list to the left. 11) Delete one of the duplicate in the view to the right. Expected result === The selected image to be deleted, was deleted. The pair of duplicates in the list to the left is removed from the list of duplicates. Actual result = The selected image to be deleted, was deleted. But, all items in the list to the left was removed. The list of duplicates was cleared. Additional info === I compiled from sources. Source is the master branch latest commit from core: 88e7d6fef15790d3588c6d9307e9fe45104ba778 I tested this on an Linux KDE Neon desktop machine. This was perpahs a wall of text, so I added a screenshot as well :-) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373090] Reply to mailing list empty "TO" field
https://bugs.kde.org/show_bug.cgi?id=373090 Laurent Montelchanged: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Could you attach mail as mbox for testing ? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 373099] New: Login button not enabled
https://bugs.kde.org/show_bug.cgi?id=373099 Bug ID: 373099 Summary: Login button not enabled Product: drkonqi Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: i...@pnb.co.za Target Milestone: --- My laptop connected to a network that does not allow internet access after returning from standby. At this time Plasma crashed and when I tried to report the bug DrKonqi did not enable the login button, even after I connected to a network that does allow internet access. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373098] New: Plasma crash after returning from standby
https://bugs.kde.org/show_bug.cgi?id=373098 Bug ID: 373098 Summary: Plasma crash after returning from standby Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: i...@pnb.co.za Target Milestone: 1.0 Created attachment 102536 --> https://bugs.kde.org/attachment.cgi?id=102536=edit Stack trace The stack trace looks different from that of bug 372614 as such I'm reporting a new crash. The same system and setup applies as that of 372614 with the same multi screen return from standby scenario. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364249] The total size shown in properties of /root folder is incorrect
https://bugs.kde.org/show_bug.cgi?id=364249 Chinmoy Ranjan Pradhanchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Chinmoy Ranjan Pradhan --- *** This bug has been marked as a duplicate of bug 353391 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353391] wrong calculated size of direcories
https://bugs.kde.org/show_bug.cgi?id=353391 Chinmoy Ranjan Pradhanchanged: What|Removed |Added CC||chinmoyr...@gmail.com --- Comment #4 from Chinmoy Ranjan Pradhan --- *** Bug 364249 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 366131] Illegal opcode in OS X 11.0 when using function getpwuid()
https://bugs.kde.org/show_bug.cgi?id=366131 --- Comment #3 from Rhys Kidd--- Ping? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 334799] Import button on toolbar not activated after plugging in USB stick/memory card with photos
https://bugs.kde.org/show_bug.cgi?id=334799 --- Comment #5 from Michal Sylwester--- Yes, just tried with current sources. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372772] Brew doesn't allow for Valgrind 3.12.0 installation on Sierra OSX
https://bugs.kde.org/show_bug.cgi?id=372772 Rhys Kiddchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Assignee|jsew...@acm.org |rhysk...@gmail.com Resolution|--- |DUPLICATE CC||rhysk...@gmail.com --- Comment #1 from Rhys Kidd --- Am marking this as a duplicate of 365327, as it goes to support of the latest macOS 10.12. That Homebrew chooses to flag that issue via a failed installation on this specific version of macOS is their choice, but not something we should ourselves track separately. *** This bug has been marked as a duplicate of bug 365327 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365327] Support macOS Sierra (10.12)
https://bugs.kde.org/show_bug.cgi?id=365327 Rhys Kiddchanged: What|Removed |Added CC||zalbi...@gmail.com --- Comment #8 from Rhys Kidd --- *** Bug 372772 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373097] New: kwin fails to compile, due to strange issues with Mesa headers
https://bugs.kde.org/show_bug.cgi?id=373097 Bug ID: 373097 Summary: kwin fails to compile, due to strange issues with Mesa headers Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: bluescreenaven...@gmail.com Target Milestone: --- Hi I am getting the following build output when trying to compile kwin It seems to involve the mesa headers, I'm not sure if I have something that is suddenly configured wrong, as I have been encountering more issues with compile errors coming from them... I am using Debian Testing, but a hand built mesa [ 83%] Built target kdeinit_kwin_x11 /srcbuild/kwin/plugins/platforms/x11/common/eglonxbackend.cpp: In member function ‘bool KWin::EglOnXBackend::initRenderingContext()’: /srcbuild/kwin/plugins/platforms/x11/common/eglonxbackend.cpp:194:33: error: invalid conversion from ‘Display* {aka _XDisplay*}’ to ‘EGLNativeDisplayType {aka int}’ [-fpermissive] dpy = eglGetDisplay(m_x11Display); ^ /srcbuild/kwin/plugins/platforms/wayland/egl_wayland_backend.cpp: In member function ‘bool KWin::EglWaylandBackend::initializeEgl()’: /srcbuild/kwin/plugins/platforms/wayland/egl_wayland_backend.cpp:86:55: error: invalid conversion from ‘wl_display*’ to ‘EGLNativeDisplayType {aka int}’ [-fpermissive] display = eglGetDisplay(m_wayland->display()); ^ /srcbuild/kwin/plugins/platforms/x11/common/eglonxbackend.cpp: In member function ‘void* KWin::EglOnXBackend::createSurface(xcb_window_t)’: /srcbuild/kwin/plugins/platforms/x11/common/eglonxbackend.cpp:271:81: error: invalid conversion from ‘xcb_window_t {aka unsigned int}’ to ‘EGLNativeWindowType {aka void*}’ [-fpermissive] surface = eglCreateWindowSurface(eglDisplay(), config(), window, nullptr); ^ Scanning dependencies of target KWinIntegrationTestFramework [ 83%] Building CXX object autotests/integration/CMakeFiles/KWinIntegrationTestFramework.dir/kwin_wayland_test.cpp.o -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 373096] New: Krecipes crashed while importing USDA Nutrient Data in
https://bugs.kde.org/show_bug.cgi?id=373096 Bug ID: 373096 Summary: Krecipes crashed while importing USDA Nutrient Data in Product: krecipes Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krecipes-de...@kde.org Reporter: mymadmillions2...@gmail.com Target Milestone: --- Krecipes crashed while importing USDA Nutrient Data in -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)
https://bugs.kde.org/show_bug.cgi?id=348812 Kai Krakowchanged: What|Removed |Added CC|k...@kaishome.de | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354534] kscreen-console MUST NOT use qDebug for output
https://bugs.kde.org/show_bug.cgi?id=354534 Rex Dieterchanged: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373074] Perspective transform of a vector layer provides a completely incorrect result.
https://bugs.kde.org/show_bug.cgi?id=373074 Dave Freemanchanged: What|Removed |Added CC||segad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 --- Comment #40 from Leslie Zhai--- Created attachment 102535 --> https://bugs.kde.org/attachment.cgi?id=102535=edit growisofs-burn-archlinux-iso-debugging-output1.txt But growisofs worked! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 --- Comment #39 from Leslie Zhai--- Created attachment 102534 --> https://bugs.kde.org/attachment.cgi?id=102534=edit cdrskin-burn-archlinux-iso-debugging-output2.txt Failed to burn ArchLinux iso created by CDEmu with --allow_emulated_drives -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 --- Comment #38 from Leslie Zhai--- Git commit c17d307523a08c1e6042381bdbdfe1971fffc84a by Leslie Zhai. Committed on 30/11/2016 at 02:52. Pushed by lesliezhai into branch 'cdrskin'. Change features and arguments for Cdrskin Test plan1: burn ArchLinux iso created by CDEmu with --allow_emulated_drives FAILED! see debugging log attachment: cdrskin-burn-archlinux-iso-debugging-output2.txt Test plan2: burn ArchLinux iso created by CDEmu with growisofs SUCCESS! see debugging log attachment: growisofs-burn-archlinux-iso-debugging-output1.txt CCMAIL: scdbac...@gmx.net M +4-24 libk3b/core/k3bdefaultexternalprograms.cpp M +1-2libk3b/jobs/k3bmetawriter.cpp M +23 -13 libk3b/projects/k3bcdrskinwriter.cpp https://commits.kde.org/k3b/c17d307523a08c1e6042381bdbdfe1971fffc84a -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373095] Crash when opening setting
https://bugs.kde.org/show_bug.cgi?id=373095 Greg Martynchanged: What|Removed |Added CC||greg.mar...@gmail.com --- Comment #1 from Greg Martyn --- I wasn't able to reproduce this after relaunching Amarok. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373095] New: Crash when opening setting
https://bugs.kde.org/show_bug.cgi?id=373095 Bug ID: 373095 Summary: Crash when opening setting Product: amarok Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: greg.mar...@gmail.com Target Milestone: 2.9 Application: amarok (2.8.90) KDE Platform Version: 4.14.25 Qt Version: 4.8.7 Operating System: Linux 4.8.8-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: It had been a while since I've opened Amarok. I turned on the lyrics embedding from the menu, then tried to open Settings. It crashed immediately. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff08c350940 (LWP 30479))] Thread 24 (Thread 0x7fef1b3ee700 (LWP 30551)): #0 0x7ff089643e76 in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQtCore.so.4 #1 0x7ff081b1f699 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7ff081b2007b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7ff081b2026c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7ff08964447e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x7ff0896127bf in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #6 0x7ff089612b25 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #7 0x7ff089501af9 in QThread::exec() () at /lib64/libQtCore.so.4 #8 0x7ff0895f2613 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4 #9 0x7ff0895043ca in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #10 0x7ff08749a6ca in start_thread () at /lib64/libpthread.so.0 #11 0x7ff088e35f6f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fef1bbef700 (LWP 30550)): #0 0x7ff0874a0460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff089504936 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQtCore.so.4 #2 0x7ff08a089f5c in QFileInfoGatherer::run() () at /lib64/libQtGui.so.4 #3 0x7ff0895043ca in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #4 0x7ff08749a6ca in start_thread () at /lib64/libpthread.so.0 #5 0x7ff088e35f6f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fef2170a700 (LWP 30503)): #0 0x7ff088e2a00d in poll () at /lib64/libc.so.6 #1 0x7ff081b20156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7ff081b2026c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7ff08964447e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #4 0x7ff0896127bf in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x7ff089612b25 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #6 0x7ff089501af9 in QThread::exec() () at /lib64/libQtCore.so.4 #7 0x7ff0895043ca in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #8 0x7ff08749a6ca in start_thread () at /lib64/libpthread.so.0 #9 0x7ff088e35f6f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7feffbbd6700 (LWP 30500)): #0 0x7ff0874a0460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff087d4d85a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQtScript.so.4 #2 0x7ff087d4d889 in () at /lib64/libQtScript.so.4 #3 0x7ff08749a6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7ff088e35f6f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff00cff9700 (LWP 30499)): #0 0x7ff0874a0460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff089504936 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQtCore.so.4 #2 0x7ff0864d87e0 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /lib64/libthreadweaver.so.4 #3 0x7ff0864db043 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4 #4 0x7ff0864db05c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4 #5 0x7ff0864db05c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4 #6 0x7ff0864db05c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4 #7 0x7ff0864db05c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4 #8 0x7ff0864db05c in
[krita] [Bug 372679] Crash when creating new document
https://bugs.kde.org/show_bug.cgi?id=372679 --- Comment #5 from jeanlucpont...@gmail.com --- Hi Wolthera, No luck there either. I tried both renaming and deleting (though saving a backup elsewhere), and no difference. I'm not sure this is a problem, but, in the instructions, it says the path is: user\Appdata\Roaming\krita\kritarc or %APPDATA%\Roaming\krita\kritarc, But I didn't find it in this path. Instead, in \Roaming\, I found it further down than that: [image: Inline image 1] /AppData/Roaming/krita/share/config I did find another kritarc file that sort of matched that path structure, but it was in \Local\ rather than \Roaming\: [image: Inline image 2] wrote: > https://bugs.kde.org/show_bug.cgi?id=372679 > > woltherachanged: > >What|Removed |Added > > > CC||griffinval...@gmail.com > > --- Comment #4 from wolthera --- > If the problem is caused by toggling the openGL, maybe there's something > wrong > with the config file instead. Could you rename the file(as noted here: > https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration ), check if > that > has an effect, and if so, upload it here? That way we can check if there's > something funny going on with the config file. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372679] Crash when creating new document
https://bugs.kde.org/show_bug.cgi?id=372679 --- Comment #6 from jeanlucpont...@gmail.com --- Created attachment 102533 --> https://bugs.kde.org/attachment.cgi?id=102533=edit image.png -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373065] Range-based for-loop doesn't have uses on the container side
https://bugs.kde.org/show_bug.cgi?id=373065 --- Comment #2 from Nicolás Alvarez--- I was using clang 3.5. Using 3.8.1 indeed fixes this. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369840] kdevelop drops modifiers for types declared using decltype
https://bugs.kde.org/show_bug.cgi?id=369840 Nicolás Alvarezchanged: What|Removed |Added CC||nicolas.alva...@gmail.com --- Comment #1 from Nicolás Alvarez --- This seems to affect auto too: unsigned long int x; auto y = x; The tooltip for y says 'int', dropping the 'unsigned' and 'long' modifiers. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373063] Tooltip for variables declared "auto" doesn't show actual type
https://bugs.kde.org/show_bug.cgi?id=373063 --- Comment #2 from Nicolás Alvarez--- I confirm this is fixed when using clang 3.8.1. Well, kind of fixed. It seems bug 369840 affects auto too: unsigned long int x; auto y = x; The tooltip for y says 'int', dropping the 'unsigned' and 'long' modifiers. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 372731] If tags 'Artist' & 'Album Artist' content is equal, both tags are not displayed in playlist
https://bugs.kde.org/show_bug.cgi?id=372731 --- Comment #3 from Christoph Feck--- Not sure if I understand comment #2 correctly. Does it mean the issue is not really present and this ticket can be closed? -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 373044] The last time, apper before finish updating packages, returned an Update Error
https://bugs.kde.org/show_bug.cgi?id=373044 Christoph Feckchanged: What|Removed |Added Severity|normal |crash --- Comment #2 from Christoph Feck --- Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f05e7a984c0 (LWP 1868))] Thread 4 (Thread 0x7f05c8720700 (LWP 1872)): #0 0x7f05f2f1f460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f05cb93c6b3 in radeon_drm_cs_emit_ioctl () at /usr/lib64/dri/r600_dri.so #2 0x7f05cb93bdf7 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f05f2f196ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f05f4b78f6f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f05d3fff700 (LWP 1871)): #0 0x7f05f4b6d00d in poll () at /lib64/libc.so.6 #1 0x7f05ee838156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f05ee83826c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f05f5972d8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f05f59240ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f05f5781643 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f05f84a87a9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f05f5785a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f05f2f196ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f05f4b78f6f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f05dc74a700 (LWP 1870)): #0 0x7f05f4b6d00d in poll () at /lib64/libc.so.6 #1 0x7f05f1f3cd10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f05f1f3eaa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f05e0e11a19 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f05f5785a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f05f2f196ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f05f4b78f6f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f05e7a984c0 (LWP 1868)): [KCrash Handler] #6 0x7f05f594bad1 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #7 0x7f05d1e2e20f in PackageKit::Transaction::finished(PackageKit::Transaction::Exit, unsigned int) () at /lib64/libpackagekitqt5.so.0 #8 0x7f05d1e3327d in PackageKit::TransactionPrivate::finished(unsigned int, unsigned int) () at /lib64/libpackagekitqt5.so.0 #9 0x7f05d1e3353b in PackageKit::TransactionPrivate::daemonQuit() () at /lib64/libpackagekitqt5.so.0 #10 0x7f05d1e30a99 in PackageKit::Transaction::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libpackagekitqt5.so.0 #11 0x7f05f594bff1 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #12 0x7f05d1e2a4fe in PackageKit::DaemonPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /lib64/libpackagekitqt5.so.0 #13 0x7f05d1e24708 in PackageKit::Daemon::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libpackagekitqt5.so.0 #14 0x7f05f594bff1 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #15 0x7f05f8501dcf in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /lib64/libQt5DBus.so.5 #16 0x7f05f8501e8f in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged(QString const&, QString const&, QString const&) () at /lib64/libQt5DBus.so.5 #17 0x7f05f850240f in QDBusServiceWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libQt5DBus.so.5 #18 0x7f05f85027e0 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /lib64/libQt5DBus.so.5 #19 0x7f05f84b47f0 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5 #20 0x7f05f594d0d9 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #21 0x7f05f616d96c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #22 0x7f05f6175111 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x7f05f592512a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7f05f5927800 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #25 0x7f05f5972cf3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #26 0x7f05ee837e42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #27 0x7f05ee8381c0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #28 0x7f05ee83826c in
[dolphin] [Bug 372920] Create an option to enable the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372920 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Christoph Feck --- It affects all applications that use KIO, not just Dolphin. It cannot be configured in KIO, though, because it is actually the Plasma shell that decides to override the default progress notifications. So the option to disable it needs to be in Plasma. If you run a different shell, you always get the 'old' dialog. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372919] Recreate the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372919 Christoph Feckchanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Already reported as bug 372920. -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 371507] libvlc loads Qt4 plugin in a Qt5 application [ArchLinux]
https://bugs.kde.org/show_bug.cgi?id=371507 Christoph Feckchanged: What|Removed |Added CC||pri...@marco-grimmeissen.de --- Comment #20 from Christoph Feck --- *** Bug 372852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 372852] While login over SDDM this crash happend. Only the crashreport appears.
https://bugs.kde.org/show_bug.cgi?id=372852 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 371507 *** -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 364185] K3b crashes burning DL DVD image
https://bugs.kde.org/show_bug.cgi?id=364185 Christoph Feckchanged: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #5 from Christoph Feck --- Please report this issue to the developers of the "Adwaita" application widget style. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 373013] KWrite crashes when closing the application
https://bugs.kde.org/show_bug.cgi?id=373013 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 371507 *** -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 371507] libvlc loads Qt4 plugin in a Qt5 application [ArchLinux]
https://bugs.kde.org/show_bug.cgi?id=371507 Christoph Feckchanged: What|Removed |Added CC||bbresla...@gmail.com --- Comment #19 from Christoph Feck --- *** Bug 373013 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 350630] The composers cancel button should indicate that this will either save or drop
https://bugs.kde.org/show_bug.cgi?id=350630 Spencer Brownchanged: What|Removed |Added CC||spencerbrown...@gmail.com --- Comment #3 from Spencer Brown --- Hi. I've set the composer's cancel button's text to change from "Cancel" to "Save/Ignore Changes" when the composer state changes to SaveRequired. (i.e. in the Composer::MessageUpdated slot) I did run into a minor issue: the slot is called as soon as the compositor object is created, in the slotUpdateSignature function. To solve this, i just set the button's text back to "Cancel" after the slotUpdateSignature function in the ComposeWidget Constructor. Now it works perfectly. gerrit patch: https://gerrit.vesnicky.cesnet.cz/r/#/c/842/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373045] Plasma crashes switching to text console and back to X
https://bugs.kde.org/show_bug.cgi?id=373045 --- Comment #1 from Christoph Feck--- It is a bit unfortunate that you are reporting two issues with a single ticket. I assume that the crash will be marked as a duplicate, so you should report the freezing separately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373045] Plasma crashes switching to text console and back to X
https://bugs.kde.org/show_bug.cgi?id=373045 Christoph Feckchanged: What|Removed |Added Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk Component|general |general Product|kde |plasmashell CC||bhus...@gmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 Version|unspecified |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373094] systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=373094 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 344942 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344942] deco kcm segfaults in QV4::ExecutionEngine::~ExecutionEngine
https://bugs.kde.org/show_bug.cgi?id=344942 Christoph Feckchanged: What|Removed |Added CC||kdebu...@outlook.com --- Comment #45 from Christoph Feck --- *** Bug 373094 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373094] New: systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=373094 Bug ID: 373094 Summary: systemsettings crash Product: systemsettings Version: 5.8.2 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdebu...@outlook.com Target Milestone: --- Application: systemsettings5 (5.8.2) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.7.0-0.bpo.1-amd64 x86_64 Distribution: Debian GNU/Linux stable-updates (sid) -- Information about the crash: - What I was doing when the application crashed: I was going to systemsettings-application style and changed the window decoration, clicked on apply and all settings. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8c658685c0 (LWP 4399))] Thread 4 (Thread 0x7f8c37184700 (LWP 4405)): #0 0x7f8c61f6d56d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8c5d2699f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c5d269b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c6288b6fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8c6283507a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c626570d3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c60fdd5d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f8c6265bd88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8c5f179464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f8c61f769df in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f8c4b6ac700 (LWP 4401)): #0 0x7f8c61f6d56d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8c5d2699f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c5d269b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c6288b6fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8c6283507a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c626570d3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c659bb6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f8c6265bd88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8c5f179464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f8c61f769df in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f8c541a7700 (LWP 4400)): #0 0x7f8c61f6d56d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8c5f9f3150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8c5f9f4ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8c56706b69 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f8c6265bd88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c5f179464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f8c61f769df in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f8c658685c0 (LWP 4399)): [KCrash Handler] #6 0x7f8c60eafd85 in QV4::WeakValue::free() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f8c60f20a82 in QV4::QObjectWrapper::destroyObject(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f8c60db6dbf in QV4::MemoryManager::sweep(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f8c60db81cc in QV4::MemoryManager::~MemoryManager() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f8c60e9f69b in QV4::ExecutionEngine::~ExecutionEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f8c60fdf086 in QV8Engine::~QV8Engine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f8c60fdf1a9 in QV8Engine::~QV8Engine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f8c60e369a6 in QJSEngine::~QJSEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f8c60f4a90d in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f8c60f4a9c9 in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f8c628614b1 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f8c6286a82f in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f8c612ab084 in QQuickWindow::~QQuickWindow() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #19
[frameworks-ktexteditor] [Bug 373093] Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 Sven Brauchchanged: What|Removed |Added Product|kdevelop|frameworks-ktexteditor Assignee|kdevelop-bugs-n...@kde.org |kwrite-bugs-n...@kde.org Component|UI: general |general Version|git master |5.28.0 CC||m...@svenbrauch.de --- Comment #2 from Sven Brauch --- Changing product to frameworks-ktexteditor, the issue is there. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373093] Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 --- Comment #1 from Janek Bevendorff--- Created attachment 102531 --> https://bugs.kde.org/attachment.cgi?id=102531=edit Find in document: no matches found -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373093] New: Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 Bug ID: 373093 Summary: Search / Find box unreadable when using dark theme Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Created attachment 102530 --> https://bugs.kde.org/attachment.cgi?id=102530=edit Find in document, matches found When searching for text inside a document (Ctrl+F) the text inside the search / find box becomes unreadable when using a dark UI theme (see screenshots). The reason for this is that the background color is changed to either a light green or light red, but the text color is the default theme color. This works for bright themes with black text, but not at all for dark themes with white text. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 --- Comment #36 from erwinvanst...@gmail.com --- Just tested krita_2.9.9.2ae_beta_x64 This does a lot better job. No jumping connection lines between two strokes. Less lagg. Only thing that's not correct is the outline. It doesn't follow the cursor. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 373092] Add Krita Dark Syntax Schema
https://bugs.kde.org/show_bug.cgi?id=373092 Janek Bevendorffchanged: What|Removed |Added Version|unspecified |Git Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 373092] New: Add Krita Dark Syntax Schema
https://bugs.kde.org/show_bug.cgi?id=373092 Bug ID: 373092 Summary: Add Krita Dark Syntax Schema Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Hi, I really like the new Breeze Dark syntax highlighting schema. However, for the UI I prefer slightly toned-down colors such as those provided by the Krita Dark theme. The background color is less intensive and a little more neutral, but still dark enough to be easy on the eye. Unfortunately, there is no matching syntax schema, so the editor area always looks a little off when using a different dark theme than Breeze Dark. It would therefore be great if Kate (and KDevelop) would also ship with a Krita Dark Schema. The colors would be basically the same as the Breez Dark Theme with the following changes: Editor Background Colors: Text Area: #313131 Current Line: #393939 Icon Border: Background Area: #363636 Word Wrap Marker: #424242 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373091] New: Plasma crashed while switching windows
https://bugs.kde.org/show_bug.cgi?id=373091 Bug ID: 373091 Summary: Plasma crashed while switching windows Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: brian.d.all...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-ck-haswell x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Google Chrome was loading after being opened via launcher icon. I clicked on its icon in the task area of the bottom panel while it was loading. It didn't come up instantly, so (impatiently), I clicked the icon a few times in rapid succession. - Unusual behavior I noticed: When Chrome finally came up, it had some strange black artifacts in the title bar decoration until I clicked the window into focus. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6705a1840 (LWP 780))] Thread 6 (Thread 0x7fa64d50e700 (LWP 1788)): #0 0x7fa66ffe3551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa66d690ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa66d6923b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa66d63f23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa66d4620f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa667fd82d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa66d466d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa66927a454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa66ffec7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fa63895a700 (LWP 1164)): #0 0x7fa66928010f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa66c5d6ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fa66c5d6b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa66927a454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa66ffec7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa64e50f700 (LWP 1099)): #0 0x7fa66ffe3551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa66d690ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa66d6923b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa66d63f23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa66d4620f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa667fd82d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa66d466d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa66927a454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa66ffec7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fa654d8e700 (LWP 883)): #0 0x7fa66ffe3551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa66d690ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa66d6923b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa66d63f23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa66d4620f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa6671a2e55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fa66d466d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa66927a454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa66ffec7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa656eb5700 (LWP 818)): #0 0x7fa66ffe348d in poll () at /usr/lib/libc.so.6 #1 0x7fa66f1238e0 in () at /usr/lib/libxcb.so.1 #2 0x7fa66f125679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fa657d8d449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa66d466d78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fa66927a454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa66ffec7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa6705a1840 (LWP 780)): [KCrash Handler] #6 0x4029293b in () #7 0x7fa63b40ef34 in () at /usr/lib/libnvidia-glcore.so.375.20 #8 0x7fa63b4141f8 in () at /usr/lib/libnvidia-glcore.so.375.20 #9 0x7fa63afe8838 in () at /usr/lib/libnvidia-glcore.so.375.20 #10 0x7fa66dea6ec4 in QOpenGLTextureGlyphCache::resizeTextureData(int, int) () at /usr/lib/libQt5Gui.so.5 #11 0x7fa66de46ea6 in QTextureGlyphCache::fillInPendingGlyphs() () at /usr/lib/libQt5Gui.so.5 #12 0x7fa668688d38 in () at /usr/lib/libQt5Quick.so.5 #13 0x7fa668686bf4 in () at /usr/lib/libQt5Quick.so.5 #14 0x7fa66870de07 in
[kmail2] [Bug 373090] Reply to mailing list empty "TO" field
https://bugs.kde.org/show_bug.cgi?id=373090 Martin Bednarchanged: What|Removed |Added CC||martin+...@serafean.cz -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373090] New: Reply to mailing list empty "TO" field
https://bugs.kde.org/show_bug.cgi?id=373090 Bug ID: 373090 Summary: Reply to mailing list empty "TO" field Product: kmail2 Version: 5.3.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: martin+...@serafean.cz Target Milestone: --- Reply to mailing list produces a reply with an empty "TO" header, which it then (correctly) refuses to send. >From what I see, the list adds the following mailing-list related headers : List-ID: X-Mailing-List: netfil...@vger.kernel.org In the kmail GUI, the header shows the list Id. >From what I understand, kmail uses the "reply-to" header to recognize the mailing list. Could it also use List-ID if it contains a valid email? (no idea how workable that is...) If not, then at least notifying about missing information (why the "TO" field is empty) would be nice. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372953] Crash when printing
https://bugs.kde.org/show_bug.cgi?id=372953 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in the intel video drivers, probably similar to the multi-threading issues that we see with QtWebEngine on nouveau drivers. Please report this issue directly to intel video driver developers via https://bugs.freedesktop.org/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368983] Kmail crashes randomly
https://bugs.kde.org/show_bug.cgi?id=368983 Christoph Feckchanged: What|Removed |Added CC||k...@pcfe.net --- Comment #5 from Christoph Feck --- *** Bug 372948 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368983] Kmail crashes randomly
https://bugs.kde.org/show_bug.cgi?id=368983 Christoph Feckchanged: What|Removed |Added CC||matthias.h.na...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 372034 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373089] New: KWin crashed several times on virtual desktop switching
https://bugs.kde.org/show_bug.cgi?id=373089 Bug ID: 373089 Summary: KWin crashed several times on virtual desktop switching Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bogdan.sinit...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: 1. Enabled fade virtual desktop effect 2. Randomly switched virtual desktops for some time The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3871bc5840 (LWP 32763))] Thread 4 (Thread 0x7f382aa77700 (LWP 309)): #0 0x7f386a8a310f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f386dbf9ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f386dbf9b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f386a89d454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f387160f7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f38358f0700 (LWP 308)): #0 0x7f3871606551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f386ecb3ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f386ecb53b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f386ec6223a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f386ea850f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f38695fb2d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f386ea89d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f386a89d454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f387160f7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f38554b3700 (LWP 32767)): #0 0x7f3871606551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f386ecb3ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f386ecb53b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f386ec6223a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f386ea850f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f38687c5e55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f386ea89d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f386a89d454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f387160f7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3871bc5840 (LWP 32763)): [KCrash Handler] #6 0x7f3869592254 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f386958feb2 in QQmlMetaType::qmlSingletonTypes() () at /usr/lib/libQt5Qml.so.5 #8 0x7f38695672d0 in QQmlEngine::~QQmlEngine() () at /usr/lib/libQt5Qml.so.5 #9 0x7f3869567449 in QQmlEngine::~QQmlEngine() () at /usr/lib/libQt5Qml.so.5 #10 0x7f387155c990 in __run_exit_handlers () at /usr/lib/libc.so.6 #11 0x7f387155c9ea in () at /usr/lib/libc.so.6 #12 0x7f3857e82ba3 in () at /usr/lib/libQt5XcbQpa.so.5 #13 0x7f386ec904b9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f386f943e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f386f94b581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7f386ec63de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7f386ec6656d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #18 0x7f386ecb51fa in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f3857ef917d in () at /usr/lib/libQt5XcbQpa.so.5 #20 0x7f386ec6223a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7f386ec6a73c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #22 0x7f38718ce495 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so #23 0x7f3871547291 in __libc_start_main () at /usr/lib/libc.so.6 #24 0x0040069a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected
https://bugs.kde.org/show_bug.cgi?id=372034 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 368983 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 372948] crash upon opening large mailbox (552 messages)
https://bugs.kde.org/show_bug.cgi?id=372948 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 368983 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 373051] Kontact crash
https://bugs.kde.org/show_bug.cgi?id=373051 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 368983 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368983] Kmail crashes randomly
https://bugs.kde.org/show_bug.cgi?id=368983 Christoph Feckchanged: What|Removed |Added CC||than...@gmail.com --- Comment #4 from Christoph Feck --- *** Bug 373051 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 369363] Type not inferred when iterating objects with __next__
https://bugs.kde.org/show_bug.cgi?id=369363 Francis Hernechanged: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||v-python/e0a92aac7d716bf706 ||205a913d92246716e8727e Resolution|--- |FIXED --- Comment #3 from Francis Herne --- Git commit e0a92aac7d716bf706205a913d92246716e8727e by Francis Herne. Committed on 29/11/2016 at 23:05. Pushed by flherne into branch 'master'. Get iterable content using __iter__() and __next__(). Supports unpacking and iterating over custom sequence types. See tests for examples (by Nicolás Alvarez). Returning `iter(builtin_container)` isn't handled usefully because they use docstring cheats with no real return values. Differential Revision: https://phabricator.kde.org/D3540 M +4-6duchain/declarationbuilder.cpp M +3-0duchain/declarationbuilder.h M +1-1duchain/expressionvisitor.cpp M +31 -25 duchain/helpers.cpp M +1-1duchain/helpers.h M +21 -0duchain/tests/pyduchaintest.cpp https://commits.kde.org/kdev-python/e0a92aac7d716bf706205a913d92246716e8727e -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 373073] akonadi Server not comes up (D-Bus, Resources)
https://bugs.kde.org/show_bug.cgi?id=373073 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 372236 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372236] Akonadi will not start
https://bugs.kde.org/show_bug.cgi?id=372236 Christoph Feckchanged: What|Removed |Added CC||sbops...@yahoo.com --- Comment #10 from Christoph Feck --- *** Bug 373073 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs or crashes with new glibc pthread barrier implementation
https://bugs.kde.org/show_bug.cgi?id=358213 Philippe Waroquierschanged: What|Removed |Added CC||philippe.waroquiers@skynet. ||be Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Philippe Waroquiers --- Was fixed in r16154, fix announced in NEWS revision 16165 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373088] New: Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 Bug ID: 373088 Summary: Current tab highlighting counter-intuitive when using dark themes Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Created attachment 102529 --> https://bugs.kde.org/attachment.cgi?id=102529=edit Guess which one is the active tab. Hint: it's not main.cpp When using the Breeze Dark theme (or any other dark theme such as Krita Dark), highlighting of the current tab is completely counter-intuitive. While with the normal (bright) Breeze theme, the current tab has a brighter background color than any of the other tabs, it is the other way round for dark themes (see attached screenshot). This is so absolutely counter-intuitive that even after many weeks of using KDevelop I'm still clicking the wrong tabs again and again, although I know that the colors are wrong. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 373060] Will not save documents in any format
https://bugs.kde.org/show_bug.cgi?id=373060 --- Comment #2 from Glenn--- Thanks for looking into this. I loaded the current version of KDE desktop. KolourPaint will save files in KDE. I also loaded the current version of Gnome and Kolourpaint will NOT save files in that desktop. Hope this helps. Best regards. Thanks for a great little application. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 373087] plasma icons from system settings icon theme
https://bugs.kde.org/show_bug.cgi?id=373087 andreaschanged: What|Removed |Added CC||kain...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 373087] New: plasma icons from system settings icon theme
https://bugs.kde.org/show_bug.cgi?id=373087 Bug ID: 373087 Summary: plasma icons from system settings icon theme Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: kain...@gmail.com Target Milestone: --- plasma use the icon's for the system tray from the plasma theme. when you look at gnome and xfce the system tray and panel icons come from the icon theme (/usr/share/icons/...). Most popular icon designers add support for system tray icons in there icon set it would be awesome if plasma can use this icons and only as backup the icons from the plasma theme were used. Not every icon designer want to make a new plasma theme only to have the right icons in the system tray. In addition since plasma 5 all kde applications use first the icons from system settings and if there isn't the needed icon the icon from the app source was used. why should there be a difference for plasma. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354534] kscreen-console MUST NOT use qDebug for output
https://bugs.kde.org/show_bug.cgi?id=354534 Christoph Feckchanged: What|Removed |Added CC||cf...@kde.org, ||se...@kde.org --- Comment #2 from Christoph Feck --- The bug triaging team was not sure if this is the right patch and can be applied as is. If possible, please add a review request for your patch to https://phabricator.kde.org/ or https://reviewboard.kde.org/ These pages make it easier to discuss the patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352395] Please provide SVN revision info in --version -v
https://bugs.kde.org/show_bug.cgi?id=352395 Philippe Waroquierschanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #30 from Philippe Waroquiers --- Committed in revision 16164 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370553] Adjust date - not possible to update "digikam timestamp"
https://bugs.kde.org/show_bug.cgi?id=370553 Nicofochanged: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version Fixed In|5.4.0 | Resolution|FIXED |--- Version|5.2.0 |5.3.0 --- Comment #8 from Nicofo --- OK, Thanks for the explanations, I agree with you. But therefore, as DK timestamp is automatically updated to EXIF, there is no need to keep the possibility to use it as a reference to adjust the date. This option should be removed from the "Timestamp used" fields (top of screenshot in comment #2). And so totally disappear from UI ? (it's an internal variable, not useful for user I think ?) Note also there are minor problems in the UI: see comment #1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352395] Please provide SVN revision info in --version -v
https://bugs.kde.org/show_bug.cgi?id=352395 Philippe Waroquierschanged: What|Removed |Added Summary|Please provide SVN revision |Please provide SVN revision |info in --version |info in --version -v -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 372977] dialog's text incomplete
https://bugs.kde.org/show_bug.cgi?id=372977 Christoph Feckchanged: What|Removed |Added Ever confirmed|0 |1 Component|general |general Status|UNCONFIRMED |CONFIRMED Product|kwalletmanager |frameworks-kwallet CC||kdelibs-b...@kde.org --- Comment #2 from Christoph Feck --- Trying on master, the dialog can be resized to a smaller size than needed, so depending on fonts and style it could open with a too small size. This affects both "knewwalletdialog" as well as "kwalletwizzard" (maybe also the migration wizzards; I did not test them). To fix it, use label.setMinimumSize(label.sizeHint()) for all word-wrap enabled labels, because Qt still cannot handle them correctly in layouts. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373086] Implement additional Xen hypercalls
https://bugs.kde.org/show_bug.cgi?id=373086 Mihai DONȚUchanged: What|Removed |Added CC||mihai.do...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373086] New: Implement additional Xen hypercalls
https://bugs.kde.org/show_bug.cgi?id=373086 Bug ID: 373086 Summary: Implement additional Xen hypercalls Product: valgrind Version: 3.13 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mihai.do...@gmail.com Target Milestone: --- Created attachment 102528 --> https://bugs.kde.org/attachment.cgi?id=102528=edit extra xen monitor ops The attached patch adds support for a number of monitor ops (hypercalls) used when doing virtual machine introspection. These have been tested on xen 4.6 and 4.7. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #12 from Nicofo--- Hi Gilles, I tested again with DK 5.3. There is progress, this problem is nearly solved, but not with the Tags. I made the same test as in comment #8 I have no problem anymore related to the properties of the pictures (geolocalisation icon is OK, 'modified date' is ok, ...) BUT well with the tags. The tags are not correct anymore. And the behaviour is different depending if I make the renaming while DK is running or not. Say that picture 3 has a tag 'TAG'. If I delete picture 2 and rename the other (picture 3 becomes 2 ...): -> I expect that picture 2 has now the 'TAG', BUT: - if DK is running: now picture 2 and 3 have 'TAG' - if DK is not running: after restart of DK, the tags are 'shifted' to the neighbour picture: now picture 3 has the 'TAG' -> so in both situations it is not good. (hope the explanation is clear ;) ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 Nicofochanged: What|Removed |Added Version|5.0.0 |5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 370907] Kdenlive freeze through rdesktop / xrdp
https://bugs.kde.org/show_bug.cgi?id=370907 --- Comment #2 from Cyril Giraud--- Booting with USB Stick (no-mode-set): . Ubuntu Studio 16.10 x64 . Kdenlive 16.04.3 . xrdp 0.9.0 . rdesktop 1.8.3 The problem is more accurate: . rdesktop -g 1272x992 localhost --> rdesktop windows opens, but never draws Ubuntu menu. So I guess a problem around xrdp or rdesktop. I tried the same with old Ubuntu Studio 15.10 x64 USB stick (no-mode-set), and got different symptoms (than my Ubuntu Studio 15.10 x64 production PC): . rdesktop -g 1272x992 localhost # ok . launch kdenlive --> GUI never appears (kdenlive GUI works fine in local session) (My HW gots an AMD GPU, and oroduction PC includes proprietary AMD drivers). Sorry for this unclear status... Does somebody could report a working status on those operations? -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373085] Door in Labyrinth
https://bugs.kde.org/show_bug.cgi?id=373085 Jazeix Johnnychanged: What|Removed |Added CC||jaz...@gmail.com --- Comment #1 from Jazeix Johnny --- Hi, thank you. The image you sent is a png so it won't be scalable. Also, it misses a license. Is it you who created it or have you found it on internet? In first case, you should tell us if it's free to use and in second, there is probably a license telling in which conditions the image is usable. Also, you played with the older version not the new one where we already updated the images for maze. Can you check if it's needed with the new version? Johnny -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 Nicofochanged: What|Removed |Added Version|4.2.0 |5.3.0 --- Comment #5 from Nicofo --- Hi Gilles, I tried with DK 5.3 and the problem is still there. I.e. the map from the left view does not work like the map from the top menu. - The map from the left menu (besides Albums/Tags/Labels/Fuzzy/People/... buttons): it is not possible to select pictures by clicking on them (which is the most obvious and convenient way to select pictures I think). - While it works well in the map on the top menu (besides Thumbnails and Preview_Image). There just click on a pictures and its easy. I suppose the map view from the left could also work like that to be able to select pictures easily ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 --- Comment #35 from Mikky--- Wanted to update that I'm no longer having this issue on my Turcom TS-6580 since updating to Krita 3.0.91. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before
https://bugs.kde.org/show_bug.cgi?id=371990 --- Comment #21 from clush...@gmx.net --- Created attachment 102527 --> https://bugs.kde.org/attachment.cgi?id=102527=edit Another patch proposal. CompoentWidget::loadFromXmi and ::saveToXmi adapted, but crashing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 352870] Image is missing from album thumbnails
https://bugs.kde.org/show_bug.cgi?id=352870 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 Gábor Katonachanged: What|Removed |Added CC||kato...@gmail.com --- Comment #26 from Gábor Katona --- (In reply to Marco Parillo from comment #22) I also have this problem on Opensuse Tumbleweed running Plasma 5.8.4, Frameworks 5.28.0, Qt 5.7.0. The Meta+Tab for switching activity, and the Meta+Q for the activity manager DO work, but assigning a shortcut to the activities doesn't have effect. Moreover, I have the following finding maybe related to the hotkey problem. I had 3 activities, deleted them (because of not working shortcuts) and created again. After this I have 6 activities in the global shortcuts menu, 3 for the old, deleted ones and 3 for the new. There should be some information exchange problem between the activity manager and the shortcut management. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before
https://bugs.kde.org/show_bug.cgi?id=371990 --- Comment #20 from clush...@gmx.net --- I tried to fulfill your request in comment #17, but do not understand how to achieve this. If I simply move the calls to ComponentWidget, I get a crash on undo because restoring of child element does not work. In addition, if the code needs to be added to ComponentWidget, the same adaption is needed in all widgets that allow child Pins / Ports. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373085] New: Door in Labyrinth
https://bugs.kde.org/show_bug.cgi?id=373085 Bug ID: 373085 Summary: Door in Labyrinth Product: gcompris Version: unspecified Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: plo2...@i.ua Target Milestone: --- Created attachment 102526 --> https://bugs.kde.org/attachment.cgi?id=102526=edit Door for the labyrinth Hi, I am a Google Code-In contestant and this is my second bug report. It would be better to replace the door photo in the labyrinth by vector picture. Look attached file. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 --- Comment #37 from Thomas Schmitt--- Correction: "ATA:1,1,0" is "/dev/hdd", not "/dev/hdc". -- You are receiving this mail because: You are watching all bug changes.