[kajongg] [Bug 362381] When making a wrong claim, game stops
https://bugs.kde.org/show_bug.cgi?id=362381 Wolfgang Rohdewald changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||16.08.1 Latest Commit||http://commits.kde.org/kajo ||ngg/c219ffc2fcfc6a040595ce6 ||a349d4efbecde7f49 --- Comment #1 from Wolfgang Rohdewald --- Git commit c219ffc2fcfc6a040595ce6a349d4efbecde7f49 by Wolfgang Rohdewald. Committed on 25/08/2016 at 06:43. Pushed by wrohdewald into branch 'master'. Do not stop after wrong claim FIXED-IN: 16.08.1 M +6-1src/humanclient.py http://commits.kde.org/kajongg/c219ffc2fcfc6a040595ce6a349d4efbecde7f49 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367770] Position of window wrong when using opengl
https://bugs.kde.org/show_bug.cgi?id=367770 --- Comment #1 from Martin Gräßlin --- can you please provide a screenshot of that? I cannot really understand it from the description. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 367790] New: ZERO WIDTH NON-JOINER and some other (space) chacters cannot be entered in kate and other KDE5 apps
https://bugs.kde.org/show_bug.cgi?id=367790 Bug ID: 367790 Summary: ZERO WIDTH NON-JOINER and some other (space) chacters cannot be entered in kate and other KDE5 apps Product: kde Version: unspecified Platform: Ubuntu Packages URL: http://askubuntu.com/questions/816434 OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: iran...@outlook.com The ZERO WIDTH NON-JOINER character (U+200C) is very useful in arabic-like languages. However, if you assin a key to it and type it in a KDE5-base app eg kate, nothing will be entered. However there is not such problem with gedit and other non-kde apps. Reproducible: Always Steps to Reproduce: 1. Switch to Arabic keyboard layout in Kububtu 16.04 2. Press shift+space between any Arabic word in `kate`. 3. Press shift+space between any Arabic word in `gedit`. 4. Compare the results. 5. Copy what you type in gedit and paste it in `kate`. There is no problem when pasting. Just typing ZERO WIDTH NON-JOINER and similar characters is prohibited in `kate`. Actual Results: Nothing is typed when you press a key assigned for typing ZERO WIDTH NON-JOINER in kate and other KDE5-based apps. There is no such problem in `gedit` and other gnome apps. there was not such problem in KDE4 in Ubuntu 14.04. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 367790] ZERO WIDTH NON-JOINER and some other (space) characters cannot be entered in kate and other KDE5 apps
https://bugs.kde.org/show_bug.cgi?id=367790 H. K. changed: What|Removed |Added Summary|ZERO WIDTH NON-JOINER and |ZERO WIDTH NON-JOINER and |some other (space) chacters |some other (space) |cannot be entered in kate |characters cannot be |and other KDE5 apps |entered in kate and other ||KDE5 apps -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366795] "Paste one file"/Ctrl-V disabled when copying a local file to an smb share
https://bugs.kde.org/show_bug.cgi?id=366795 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #6 from David Faure --- Ah, I think this happens when the slave doesn't emit a UDSItem for "." in its directory listing. This leads to a null root item, which leads (now) to the action being disabled. I would say that's a bug in the slave, it's supposed to emit a UDSItem for ".". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367788] It should be possible to save Metadata templates
https://bugs.kde.org/show_bug.cgi?id=367788 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- The template file exists in fact. It's based on XML on your home directory. For 4.x, file are located to ~/.kde4/share/apps/digikam/ With 5.x, file must be moved to ~/.local/share/apps/digikam/ For technical reasons which give crash, the files are not migrated when you switch from 4 to 5. See this bug for details : https://bugs.kde.org/show_bug.cgi?id=364258 So there is no need a save/load methods for templates. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 367781] marble-qt's UI is not translatable
https://bugs.kde.org/show_bug.cgi?id=367781 Burkhard Lueck changed: What|Removed |Added Ever confirmed|0 |1 CC||lu...@hube-lueck.de Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Burkhard Lueck --- confirmed with recent frameworks + marble master compiled from sources -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 367762] Icons for own created menu or submenu do not visible
https://bugs.kde.org/show_bug.cgi?id=367762 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- Works for me with kmenuedit 5.7.4 in a VM with KDE neon User Edition 5.7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367774] csv format doesn't export
https://bugs.kde.org/show_bug.cgi?id=367774 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Stepan, Thanks for your report. I can confirm the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367739] Krita forgets sketch_line preset randomly on startup, also unable to edit favorite presets, 2.8.1
https://bugs.kde.org/show_bug.cgi?id=367739 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Hi, We're already at Krita 3.0, 2.8 is really old and we're not fixing bugs in that version anymore. Please update to the latest version and check whether the bug still happens in that version. You can just download the appimage, make it executable and run it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367789] Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=367789 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Laurent Montel --- Sorry 4.14 is very old. IT works fine here. So I think it fixed in new release. Reopen if you still have problem in 5.x. version (last is 5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 231115] Some Plasma desktop effects create flickering / garbled screen effects /black stripes on screen
https://bugs.kde.org/show_bug.cgi?id=231115 noodle...@free.fr changed: What|Removed |Added CC||noodle...@free.fr --- Comment #23 from noodle...@free.fr --- Hello, I know this is is an old post but I had the exact same problem and found the solution ! (I've got a ATI HD5770) In fact, this is a conflict between 2 effects : wobbly windows and maximize animation. I just deactivated the second one, and now the flickering/blinking "remain" on the other monitor has gone. Works perfectly now ! ps. Also I'm almost sure this happens more with proprietary drivers than with free ones. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367789] Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=367789 --- Comment #2 from Don Curtis --- openSUSE 13.2 (KDE4 Plasma) is however still current. Yes, it maybe that openSUSE Leap 42.x no longer suffers from this issue, but . . . -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366741] Krita crashes with segmentation fault if all gradients are removed
https://bugs.kde.org/show_bug.cgi?id=366741 --- Comment #6 from Boudewijn Rempt --- Hm, I still cannot confirm: it is impossible to not have the two default generated gradients, as far as I can tell. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366757] Preset tags are not always loaded
https://bugs.kde.org/show_bug.cgi?id=366757 Boudewijn Rempt changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED CC||b...@valdyas.org Summary|Tags for extra brushes |Preset tags are not always |don't seem to be loaded.|loaded Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from Boudewijn Rempt --- I also don't get the tags for presets loaded -- seems to happen on Windows only, as far as I can tell. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367791] New: Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze
https://bugs.kde.org/show_bug.cgi?id=367791 Bug ID: 367791 Summary: Kontact 5.3: Sometimes oxygen-icons are shown instead of breeze Product: kontact Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: robby.engelm...@igfs-ev.de Using 16.08 iteration of KDE apps now for some days. Sometimes I get oxygen icons in kmail component instead of breeze. Restart Kontact resolves it until it appears again. Affects the folder icons on the left pane as well as toolbar icons. Reproducible: Sometimes Expected Results: use breeze consistently -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367792] New: Can't see the previous frame using the onion skin
https://bugs.kde.org/show_bug.cgi?id=367792 Bug ID: 367792 Summary: Can't see the previous frame using the onion skin Product: krita Version: 3.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kazulia.valeri...@gmail.com I've never seen this bug reported anywhere, I create a new frame, draw on it and use the onion skin, then I create an other frame and can't see the last drawing with low opacity, like I should do. I already saw things about having the image on a white (and not transparent) layer, but I draw on a transparent layer and still it doesn't see the previous drawing Sorry if I made English mistakes Reproducible: Always Steps to Reproduce: 1. Create an animation layer 2. Draw something on a new frame in the keyframe 3. switch onion skin on 4. Create a new frame on the keyframe (with right click, "new fram" or the "new frame" button) Actual Results: Can't see the previous drawing using the onion skin Expected Results: See the previous drawing using the onion skin I use the french version of Krita but I tried other languages and the bug is still here -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367793] New: regression: system load viewer applet no longer opens system activity on click
https://bugs.kde.org/show_bug.cgi?id=367793 Bug ID: 367793 Summary: regression: system load viewer applet no longer opens system activity on click Product: plasmashell Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kol...@aon.at CC: bhus...@gmail.com, plasma-b...@kde.org With KDE4 desktop I could click on the system load viewer applet and the system activity window appeared (same as using Ctrl+Esc keys). This no longer works with plasma5 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 367794] New: mail crash when importing archived messages
https://bugs.kde.org/show_bug.cgi?id=367794 Bug ID: 367794 Summary: mail crash when importing archived messages Product: kdepim Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: importwizard Assignee: kdepim-b...@kde.org Reporter: pascal.vo...@freesbee.fr Application: importwizard (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Kmail kontact in open, I wanted to import messages stored in an existing folder. At the first stage of validation, crash of kmail. The crash can be reproduced every time. -- Backtrace: Application: Outil d'importation pour PIM (importwizard), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8168bb7800 (LWP 6568))] Thread 7 (Thread 0x7f81272fd700 (LWP 6578)): #0 0x7f815dbebe8b in pthread_getspecific () at /lib64/libpthread.so.0 #1 0x7f8156d15400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8156ceeecc in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8156cefd25 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8156ceff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8163ee7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8163e978cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8163cde06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8163ce2899 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f815dbe70a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f81633d402d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f8133fff700 (LWP 6573)): #0 0x7f8156d31cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8156cef4b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8156cefd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8156ceff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8163ee7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8163e978cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8163cde06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f8163ce2899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f815dbe70a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f81633d402d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f8140d29700 (LWP 6572)): #0 0x7f81633cbbfd in poll () at /lib64/libc.so.6 #1 0x7f8156cefe64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8156ceff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8163ee7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8163e978cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8163cde06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8163ce2899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f815dbe70a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f81633d402d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f814152a700 (LWP 6571)): #0 0x7f815dbed79c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f815dbe94a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f815dbe9306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f8157e6c80c in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f8157e71731 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f8157e71beb in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f814dc170f1 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #7 0x7f8156d30b60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f8156cef999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f8156cefdf8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f8156ceff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7f8163ee7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f8163e978cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #13 0x7f8163cde06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #14 0x7f8163ce2899 in () at /usr/lib64/libQt5Core.so.5 #15 0x7f815dbe70a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7f81633d402d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f814273b700 (LWP 6570)): #0 0x7f815dbed79c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f815dbe94a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f815dbe9306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f8157e6c80c in
[kdelibs] [Bug 311656] duplex printing option greyed out when it shouldn't be.
https://bugs.kde.org/show_bug.cgi?id=311656 --- Comment #6 from P. Christeas --- I guess this is the corresponding Qt bug, although for Qt5: https://bugreports.qt.io/browse/QTBUG-46093 A quick browse in the source of kdelibs/kutils/... suggests that KDE has little to do with printer options; they seem to be in Qt. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 367764] Text barely readable depending on background image
https://bugs.kde.org/show_bug.cgi?id=367764 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- We could set style Text.Raised on the labels to get them somewhat of a shadow. Unfortunately there's no styleWidth (to determin the stroke thickness) and the outline doesn't scale with DPI. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367795] New: Kontact crash closure
https://bugs.kde.org/show_bug.cgi?id=367795 Bug ID: 367795 Summary: Kontact crash closure Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: pascal.vo...@freesbee.fr Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: When closing Kontact by the "quit" menu or when closing the session, Kontact crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02212c67c0 (LWP 7358))] Thread 23 (Thread 0x7f014bfff700 (LWP 7393)): #0 0x7f021555fcf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f021551d4b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f021551dd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f021551df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f021ea97f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f021ea478cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f021e88e06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f021e892899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f02172e10a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f021df8402d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f016cff9700 (LWP 7391)): #0 0x7f021df7bbfd in poll () at /lib64/libc.so.6 #1 0x7f021551de64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f021551df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f021ea97f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f021ea478cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f021e88e06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f021e892899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f02172e10a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f021df8402d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f016d7fa700 (LWP 7389)): #0 0x7f02172e783a in __lll_unlock_wake () at /lib64/libpthread.so.0 #1 0x7f02172e45b9 in _L_unlock_554 () at /lib64/libpthread.so.0 #2 0x7f02172e44f6 in __pthread_mutex_unlock_usercnt () at /lib64/libpthread.so.0 #3 0x7f021669a525 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f021669fbeb in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f020d0d30f1 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #6 0x7f021555eb60 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f021551d999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7f021551ddf8 in () at /usr/lib64/libglib-2.0.so.0 #9 0x7f021551df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7f021ea97f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f021ea478cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f021e88e06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7f021e892899 in () at /usr/lib64/libQt5Core.so.5 #14 0x7f02172e10a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7f021df8402d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f016dffb700 (LWP 7387)): #0 0x7fffaf0f1b41 in clock_gettime () #1 0x7f021df90c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f021e9368f1 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f021ea96609 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f021ea96b85 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f021ea97d4e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f021551d4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f021551dd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f021551df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f021ea97f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f021ea478cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f021e88e06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f021e892899 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f02172e10a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f021df8402d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f016effd700 (LWP 7383)): #0 0x7f021555fcf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f021551df68 in g_main_context
[Breeze] [Bug 364981] Some breeze icons for KStars are inappropiate
https://bugs.kde.org/show_bug.cgi?id=364981 --- Comment #7 from Jasem Mutlaq --- Sorry to bring this up again but I didn't see any updates, is this on git master or somewhere else? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 363634] KF5 fails to load Windows executables located in the application bin directory
https://bugs.kde.org/show_bug.cgi?id=363634 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 362849] meinproc5.exe searches the wrong path for kdoctools
https://bugs.kde.org/show_bug.cgi?id=362849 Jasem Mutlaq changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 363467] Portage fails to construct runtime dependencies for packages under kde/applications
https://bugs.kde.org/show_bug.cgi?id=363467 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367554] Special Window Settings are written with lowercased WM_WINDOW_ROLE
https://bugs.kde.org/show_bug.cgi?id=367554 Martin Gräßlin changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #12 from Martin Gräßlin --- sorry, you are right. Existing rules should also be supported. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 357930] SSHFS mount - Dolphin complains disk is full
https://bugs.kde.org/show_bug.cgi?id=357930 Ruman Gerst changed: What|Removed |Added CC||mrbo...@live.de -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 367796] New: GVFS SSH mount - Dolphin can't write anything
https://bugs.kde.org/show_bug.cgi?id=367796 Bug ID: 367796 Summary: GVFS SSH mount - Dolphin can't write anything Product: kio Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: fa...@kde.org Reporter: mrbo...@live.de I have a remote directory over SSH that is mounted via GVFS (by using Gigolo). The problem is that Dolphin refuses to write anything to these folders (Create a new file via menu, pasting, ...). Deleting and opening works fine. Using the console works fine. Other programs (e.g. Emacs) and other file managers don't have any problems. If I create a file, you can see that some error message pops up (at the error bar), but disappears within milliseconds. Dolphin reports unknown size of the file system (0 of 0 bytes). I set this bug as Major one as basic operations are not possible and Dolphin is pretty much unusable now. Reproducible: Always Steps to Reproduce: 1. Mount a SSH directory via GVFS (e.g. use Gigolo) 2. Go into the mounted folder 3. Create a new file via context menu or paste something into the folder Actual Results: File won't be created / pasted. A error appears for some milliseconds (but quickly disappears). Expected Results: File is created / pasted Other people reported similar bugs ( eg https://bugs.kde.org/show_bug.cgi?id=357930). Could the be related? Are there any space checks that don't respect the "Unknown size" case? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #27 from dns2utf8 --- I am running yakuake 3.0.2-3 and qt 5.7.0-2 on Arch. It works now on my laptop too. I noticed plasmashell hanging from time to time and I/O blocking dbus along with it. The funny thing is, when I ran kdeutils-sweeper 16.04.3-1 all problems disappeared. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367730] Modifier Meta key always opens launcher
https://bugs.kde.org/show_bug.cgi?id=367730 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kwin ||/9c5f972c6a5a8f0ebd06db3249 ||d8edd1ace7686c --- Comment #3 from Martin Gräßlin --- Git commit 9c5f972c6a5a8f0ebd06db3249d8edd1ace7686c by Martin Gräßlin. Committed on 25/08/2016 at 09:47. Pushed by graesslin into branch 'master'. Forward x11 raw pointer buttons to PointerInputRedirection Summary: The raw pointer button events intercepted in the XInput2 input filter get sent through the Platform to the PointerInputRedirection. This makes the PointerInputRedirection track the pointer button state and emit the signals for button changed and axis changed. These signals are used by the modifier-only shortcut detection to determine whether the shortcut should trigger. On X11 the "normal" input handling doesn't use the InputRedirection and the emitted signals are not consumed by anything else. As PointerInputRedirection is not inited the events are not forwarded to the input filter, thus won't be processed by other parts and won't interfere with the normal event processing on X11. Given that it also doesn't matter that the input filter does not apply the left-handed setting. The internal tracking will have a wrong mouse button, but nothing is going to do decisions based on the value of the pressed mouse button. For the moment all we are interested in is that a button is pressed. Test Plan: Pressed meta, clicked, scrolled, released meta: launcher did not open. Pressed meta, released meta: launcher opened Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2506 M +58 -0plugins/platforms/x11/standalone/xinputintegration.cpp M +6-4pointer_input.cpp http://commits.kde.org/kwin/9c5f972c6a5a8f0ebd06db3249d8edd1ace7686c -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Mikhail Krasilnikov changed: What|Removed |Added CC||m.krasilni...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367797] New: Kmail crashes trying to reply an email / Can't start after that
https://bugs.kde.org/show_bug.cgi?id=367797 Bug ID: 367797 Summary: Kmail crashes trying to reply an email / Can't start after that Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: onekor...@gmail.com Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: I'm trying to reply an email, and kmail crashes. After that i'm not able to start the application againt. I've solved that deleting the content of ~/.local/share/kmail2autosave/ The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb0bea459c0 (LWP 15168))] Thread 26 (Thread 0x7faf9f342700 (LWP 15216)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7fb0e20bbe82 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fb0dcb8939c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb0dcb894ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb0e2bfc23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb0e2ba6cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb0e29cbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb0e29d0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb0deaf36fa in start_thread (arg=0x7faf9f342700) at pthread_create.c:333 #9 0x7fb0e20c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 25 (Thread 0x7fafa92b5700 (LWP 15214)): #0 0x7fb0e2a761a0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fb0e2bf9eb9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb0e2bfa425 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb0e2bfb7ee in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb0dcb8892d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb0dcb892cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb0dcb894ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fb0e2bfc23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb0e2ba6cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb0e29cbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb0e29d0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb0deaf36fa in start_thread (arg=0x7fafa92b5700) at pthread_create.c:333 #12 0x7fb0e20c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 24 (Thread 0x7fafb8b4c700 (LWP 15212)): #0 0x7fb0dcb88ddc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb0dcb89340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb0dcb894ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb0e2bfc23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb0e2ba6cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb0e29cbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb0e29d0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb0deaf36fa in start_thread (arg=0x7fafb8b4c700) at pthread_create.c:333 #8 0x7fb0e20c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 23 (Thread 0x7fafb934d700 (LWP 15210)): #0 0x7fb0dcbcdac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb0dcb88b51 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb0dcb89317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb0dcb894ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb0e2bfc23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb0e2ba6cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb0e29cbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
[kontact] [Bug 367797] Kmail crashes trying to reply an email / Can't start after that
https://bugs.kde.org/show_bug.cgi?id=367797 OnekO changed: What|Removed |Added Version|unspecified |GIT (master) --- Comment #1 from OnekO --- I'm using stable version from kde neon sources -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #28 from silentz0r --- (In reply to dns2utf8 from comment #27) > I am running yakuake 3.0.2-3 and qt 5.7.0-2 on Arch. It works now on my > laptop too. "It works" as in the problem is solved? The proper split is focused? > I noticed plasmashell hanging from time to time and I/O blocking dbus along > with it. The funny thing is, when I ran kdeutils-sweeper 16.04.3-1 all > problems disappeared. Including this issue? What did the sweeper clean? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 341157] Konsole5 doesn't send Ctrl+Space anymore
https://bugs.kde.org/show_bug.cgi?id=341157 --- Comment #19 from Chirag Anand --- (In reply to sabrewolfy from comment #18) > Chirag Anand: That command waits for me to press keys. Pressing Ctrl-Space > doesn't do/output anything. It's not clear what you're asking for ... ? If you can try running that command in another application, say xterm, then we would make sure this is a Konsole issue and not some system/keymap or some other issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 341157] Konsole5 doesn't send Ctrl+Space anymore
https://bugs.kde.org/show_bug.cgi?id=341157 --- Comment #20 from sabrewo...@gmail.com --- Ctrl-Space works in xterm on the same system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367740] Album View not updated after moving albums
https://bugs.kde.org/show_bug.cgi?id=367740 --- Comment #8 from Maik Qualmann --- Git commit 25a0431a0bf97192cee802444d074f79c8b0f01b by Maik Qualmann. Committed on 25/08/2016 at 10:29. Pushed by mqualmann into branch 'master'. remove suspendCollectionScan() from FileActionMngrDatabaseWorker M +0-18 libs/fileactionmanager/databaseworkeriface.cpp M +0-2libs/fileactionmanager/databaseworkeriface.h http://commits.kde.org/digikam/25a0431a0bf97192cee802444d074f79c8b0f01b -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://
https://bugs.kde.org/show_bug.cgi?id=366795 Elvis Angelaccio changed: What|Removed |Added Summary|"Paste one file"/Ctrl-V |Paste action disabled when |disabled when copying a |copying a local file to |local file to an smb share |smb:// or mtp:// Component|general |default Assignee|dolphin-bugs-n...@kde.org |plasma-de...@kde.org Product|dolphin |kio-extras Version|unspecified |5.7.3 --- Comment #7 from Elvis Angelaccio --- (In reply to David Faure from comment #6) > Ah, I think this happens when the slave doesn't emit a UDSItem for "." in > its directory listing. > This leads to a null root item, which leads (now) to the action being > disabled. > > I would say that's a bug in the slave, it's supposed to emit a UDSItem for > ".". Yes I can confirm (tested by patching kio-gdrive, also affected). Thus I'm moving this to kio-extras (where mtp and samba slaves live) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367798] New: There is no higlighting for keywords like off_t socklen_t time_t pid_t FILE (i actualy run 16.04.2 but was not sure isthat git so checked the .1 )
https://bugs.kde.org/show_bug.cgi?id=367798 Bug ID: 367798 Summary: There is no higlighting for keywords like off_t socklen_t time_t pid_t FILE (i actualy run 16.04.2 but was not sure isthat git so checked the .1 ) Product: kate Version: 16.04.1 Platform: Debian unstable URL: http://storage8.static.itmages.com/i/16/0825/h_1472122 326_2493371_1d64978b4c.png OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: kalory...@poczta.pl // save this as txt.c than set C highlighting. // C 11 keywords auto goto break if case inline // sice this is c11 feature and is colored than rest of c11should be colored too char int const long unsigned continue register void defaultrestrict volatile do returnwhile double short _Alignas else signed_Alignof enum sizeof_Atomic extern static_Bool float struct_Complex forswitch_Generic typedef _Imaginary union _Noreturn _Static_assert _Thread_local // Now posix // this is Hard choice but if I had chance to at least choose I would go within off_t socklen_t time_t pid_t FILE //ofc it would be super cool if all woould be added. I have listed them here: sig_atomic_t // The header shall define the following data types through typedef: FILE // A structure containing information about a file. fpos_t // A non-array type containing all information needed to specify uniquely every position within a file. off_t //As described in . size_t //As described in . ssize_t //[CX] [Option Start] As described in . [Option End] va_list //[CX] [Option Start] As described in . [Option End] // The header shall define at least the following types: blkcnt_t // Used for file block counts. blksize_t // Used for block sizes. clock_t // Used for system times in clock ticks or CLOCKS_PER_SEC; see . clockid_t // Used for clock ID type in the clock and timer functions. dev_t // Used for device IDs. fsblkcnt_t // Used for file system block counts. fsfilcnt_t // Used for file system file counts. gid_t // Used for group IDs. id_t // Used as a general identifier; can be used to contain at least a pid_t, uid_t, or gid_t. ino_t // Used for file serial numbers. key_t // [XSI] [Option Start] Used for XSI interprocess communication. [Option End] mode_t // Used for some file attributes. nlink_t // Used for link counts. off_t // Used for file sizes. pid_t // Used for process IDs and process group IDs. pthread_attr_t // Used to identify a thread attribute object. pthread_barrier_t // Used to identify a barrier. pthread_barrierattr_t // Used to define a barrier attributes object. pthread_cond_t // Used for condition variables. pthread_condattr_t // Used to identify a condition attribute object. pthread_key_t // Used for thread-specific data keys. pthread_mutex_t // Used for mutexes. pthread_mutexattr_t // Used to identify a mutex attribute object. pthread_once_t // Used for dynamic package initialization. pthread_rwlock_t // Used for read-write locks. pthread_rwlockattr_t // Used for read-write lock attributes. pthread_spinlock_t // Used to identify a spin lock. pthread_t // Used to identify a thread. size_t // Used for sizes of objects. ssize_t // Used for a count of bytes or an error indication. suseconds_t // [XSI] [Option Start] Used for time in microseconds. [Option End] time_t // Used for time in seconds. timer_t // Used for timer ID returned by timer_create(). trace_attr_t // [OB TRC] [Option Start] Used to identify a trace stream attributes object [Option End] trace_event_id_t // [OB TRC] [Option Start] Used to identify a trace event type. [Option End] trace_event_set_t // [OB TEF] [Option Start] Used to identify a trace event type set. [Option End] trace_id_t // [OB TRC] [Option Start] Used to identify a trace stream. [Option End] uid_t // Used for user IDs. // there is also from signals. sigset_t // from etworking socklen_t Reproducible: Always Steps to Reproduce: 1.copy the details t txt.c 2.set highlighting for C 3. look what is highlighted ignore the comments ( soe are taken from source files) Actual Results: do not see some of keywords/types to be highlighted. Expected Results: I could *set it by my self ;/* I took data from C11 iso standart (keywords) and
[krunner] [Bug 353995] krunner crashes after searching for an application
https://bugs.kde.org/show_bug.cgi?id=353995 Michael Palimaka changed: What|Removed |Added CC||kensing...@gentoo.org --- Comment #3 from Michael Palimaka --- Duplicate of bug #353342? What's the output of: $ balooctl checkDb and does the crash stop if you move the baloo db (~/.local/share/baloo/index) somewhere else (please save the db, it could useful for debugging if it is the cause of the crashes). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367798] There is no higlighting for keywords like off_t socklen_t time_t pid_t FILE (i actualy run 16.04.2 but was not sure isthat git so checked the .1 )
https://bugs.kde.org/show_bug.cgi?id=367798 hue changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 367799] New: Prioritise future transactions
https://bugs.kde.org/show_bug.cgi?id=367799 Bug ID: 367799 Summary: Prioritise future transactions Product: kmymoney4 Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: j...@iwmail.com Hi, Thanks for considering this feature request. Is it possible to add a field called Priority for Scheduled Transactions where the user can allocate a priority from, let's say 1 to 10, 1 being lowest priority and 10 being highest, or something similar? This value would then be used by KMyMoney to list in the Home screen (and other places if required) the upcoming transactions, in order of priority - high to low, that should be processed. This becomes handy when funds are running low and the system or user needs to decide what needs to be prioritised and which transactions should be deferred to a later date until more funds is available and in order to always have funds for future scheduled transactions with the higher priorities. This ability is the only thing keeping us from moving completely to KMyMoney from our existing financial/budgeting service provider. KMyMoney does a fantastic job and I was able to reproduce everything I needed in KMyMoney that our financial/budgeting service provider current does. Keep up the good work guys. :) Jerome Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 364220] Crash after downloading mails
https://bugs.kde.org/show_bug.cgi?id=364220 --- Comment #4 from Ian --- (In reply to wurfbaum from comment #3) > had the same problems after updating to the newest packages of opensuse > tumbleweed. > Akonadiserver always restarts with the following message: > Database "akonadi" opened using driver "QMYSQL" > Executing search "searchUpdate-1472078875" > searchUpdateResultsAvailable 270 0 results > Got 0 results, out of which 0 are already in the collection > Added 0 > Search done "searchUpdate-1472078875" (without remote search) > Search update finished > All results: 0 > Removed results: 0 > Executing search "searchUpdate-1472078875" > log_akonadiplugin_indexer: unknown term "attachment" > "[\n0: akonadiserver() [0x574fe6]\n1: akonadiserver() [0x575300]\n2: > /lib64/libc.so.6(+0x349f0) [0x7f7589a619f0]\n3: [0x7f7560050030]\n]\n" > ProcessControl: Application 'akonadiserver' returned with exit code 255 > (Unknown error) > > > So i thougt it might have to do something with email Search. > I went to Kontact Search Folder and deleted the folder "last search". This > brings Kontact to crash. But after starting Kontact again the problem with > akonadiserver restart was gone. > > To verify i did again in Kontact a search, after this i had the same > behaviour. Akonadiserver begins to restart again. After delete the last > search folder again akonadiserver is stable. > > Regards, > Thomas Cheers Thomas, that seems to work for me as well. kmail still crashes for other reasons though -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 362381] When making a wrong claim, game stops
https://bugs.kde.org/show_bug.cgi?id=362381 Wolfgang Rohdewald changed: What|Removed |Added Latest Commit|http://commits.kde.org/kajo |http://commits.kde.org/kajo |ngg/c219ffc2fcfc6a040595ce6 |ngg/f1094054650e93cc7d62224 |a349d4efbecde7f49 |3f30f0b604622b49e --- Comment #2 from Wolfgang Rohdewald --- Git commit f1094054650e93cc7d622243f30f0b604622b49e by Wolfgang Rohdewald. Committed on 25/08/2016 at 11:17. Pushed by wrohdewald into branch 'Applications/16.08'. Do not stop after wrong claim FIXED-IN: 16.08.1 M +9-2src/humanclient.py http://commits.kde.org/kajongg/f1094054650e93cc7d622243f30f0b604622b49e -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 366795] Paste action disabled when copying a local file to smb:// or mtp://
https://bugs.kde.org/show_bug.cgi?id=366795 --- Comment #8 from Elvis Angelaccio --- Git commit 6b9991bbb3b327fea01735a4d844df97c3435bd8 by Elvis Angelaccio. Committed on 25/08/2016 at 11:18. Pushed by elvisangelaccio into branch 'master'. Fix paste action with KIO >= 5.25 After 5.25, KIO::pasteActionText() (called by Dolphin) no longer allows null KFileItem destinations, so we need to explicitly create a writable UDSEntry for "." M +9-1src/kio_gdrive.cpp http://commits.kde.org/kio-gdrive/6b9991bbb3b327fea01735a4d844df97c3435bd8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367798] There is no higlighting for keywords like off_t socklen_t time_t pid_t FILE (i actualy run 16.04.2 but was not sure isthat git so checked the .1 )
https://bugs.kde.org/show_bug.cgi?id=367798 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de Assignee|kwrite-bugs-n...@kde.org|m...@svenbrauch.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367554] Special Window Settings are written with lowercased WM_WINDOW_ROLE
https://bugs.kde.org/show_bug.cgi?id=367554 --- Comment #13 from Martin Gräßlin --- Git commit 6e8a8913d1b4d6a95a2c2b74612d57ba1cce37c7 by Martin Gräßlin. Committed on 25/08/2016 at 11:23. Pushed by graesslin into branch 'master'. [autotests/integration] Add test case for rule matching on window role New test infrastructure which supports testing window rules at runtime. Test exposes problem of window rules not able to match window roles in a case insensitive manner. M +1-0autotests/integration/CMakeLists.txt A +13 -0autotests/integration/data/rules/maximize-vert-apply-initial A +172 -0autotests/integration/window_rules_test.cpp [License: GPL (v2)] M +1-1rules.h http://commits.kde.org/kwin/6e8a8913d1b4d6a95a2c2b74612d57ba1cce37c7 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #27 from Martin Gräßlin --- can you post the output of: qdbus org.kde.KWin /KWin supportInformation when having the problem? I would like to know what kwin thinks what the screens look like. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Martin Gräßlin changed: What|Removed |Added CC||mgraess...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367554] Special Window Settings are written with lowercased WM_WINDOW_ROLE
https://bugs.kde.org/show_bug.cgi?id=367554 Martin Gräßlin changed: What|Removed |Added URL||https://phabricator.kde.org ||/D2574 Flags||ReviewRequest+ --- Comment #14 from Martin Gräßlin --- Possible fix at https://phabricator.kde.org/D2574 -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 362232] Voice files switched
https://bugs.kde.org/show_bug.cgi?id=362232 Wolfgang Rohdewald changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||16.08.1 Status|CONFIRMED |RESOLVED --- Comment #3 from Wolfgang Rohdewald --- Kajongg now gives an explanation why this happens and what do to. The voice female2 is not optimal anyway, I will have to find another one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 94470] unilaterally violate the NETWM spec to support inner xinerama struts
https://bugs.kde.org/show_bug.cgi?id=94470 Martin Gräßlin changed: What|Removed |Added Resolution|WONTFIX |FIXED Version Fixed In||5.8.0 Latest Commit||http://commits.kde.org/plas ||ma-workspace/f5d966ee77f43b ||758f23eda02d879dd21442e5a2 --- Comment #69 from Martin Gräßlin --- Git commit f5d966ee77f43b758f23eda02d879dd21442e5a2 by Martin Gräßlin. Committed on 25/08/2016 at 11:44. Pushed by graesslin into branch 'master'. Allow struts on panels between screen edges if WM is KWin Summary: KWin starting with 5.7 supports struts on panels between screen edges. Thus we can start setting struts on such panels, it won't exclude a complete screen. But we don't know how other window managers handle it and it's in general a rather "dangerous" change. Thus to not affect other window managers, we check whether KWin is running and only allow struts on thus panels if KWin is running. Unfortunately we need to test this every time we go into the code path as the WM might have changed. In case the user replaces the window manager at runtime this still can result in a bad situation. FIXED-IN: 5.8.0 Test Plan: Tested whether it works in general in X11. Further testing needed by X11, multi-screen users. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2164 M +68 -41 shell/panelview.cpp M +1-0shell/panelview.h http://commits.kde.org/plasma-workspace/f5d966ee77f43b758f23eda02d879dd21442e5a2 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 363913] Improve export menu structure
https://bugs.kde.org/show_bug.cgi?id=363913 --- Comment #3 from caulier.gil...@gmail.com --- > * it is still a flat menu without (obvious) sorting or grouping of services export is... export in fact, to web service. Look well. So the menu contents is correct. > * exporting (optionally compressed & converted) images to a local folder is > still not there (right? Or did I miss something?) ==> all moved to BQM. >Also, I would remove the "Export to" string from all exports, just list the >name like I did above. The menu entries are shared with other kipi host applications, which are plugged in different manner to root menu. We can't manage this in kipi-plugins. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365324] Fatal flaws in the Dynamic Brush engine!
https://bugs.kde.org/show_bug.cgi?id=365324 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/9fb7eda716fd82dea825e44d3 ||b5a0dee1aa19e8b Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Boudewijn Rempt --- Git commit 9fb7eda716fd82dea825e44d3b5a0dee1aa19e8b by Boudewijn Rempt. Committed on 25/08/2016 at 12:06. Pushed by rempt into branch 'master'. M +19 -10 plugins/paintops/dynadraw/wdgdynaoptions.ui http://commits.kde.org/krita/9fb7eda716fd82dea825e44d3b5a0dee1aa19e8b -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 367800] New: Over instances entries in droplist of location bar disappear
https://bugs.kde.org/show_bug.cgi?id=367800 Bug ID: 367800 Summary: Over instances entries in droplist of location bar disappear Product: dolphin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: qemu-buro-point-d...@yandex.com 16.04 xubuntu, clean installation Version 15.12.3, dolphin Hi, Over instances or sessions the entries in the droplist of the location bar of dolphin disappear. I miss this feature so strongly since 16.04, I can not believe that this could be intended ; that means the droplist is empty next time one starts dolphin. is it a bug or a feature? That mean bread crumb protection lasts only a session long? No. A bug in my opinion. Tia Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360017] build error: opencv_contrib is required but was not found
https://bugs.kde.org/show_bug.cgi?id=360017 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from caulier.gil...@gmail.com --- Use bootstrap opencv option to switch between 2 or 3. It work fine here... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 311656] duplex printing option greyed out when it shouldn't be.
https://bugs.kde.org/show_bug.cgi?id=311656 --- Comment #7 from P. Christeas --- I seem to have nailed the "bug" in Qt (the one above), but this may require non-trivial changes, unlikely to be fixed in stable branches. In the meanwhile, looking for the corresponding CUPS failure. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 366537] Improper Highlighting
https://bugs.kde.org/show_bug.cgi?id=366537 Looserof7 changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #7 from Looserof7 --- Sorry for the delay!, as I'm far away from internet, I was unable to reply. There was no problem with this and fourth screen shots, but I mean they were different. I did find a work around, with this command, where I was able to even do highlighting properly, without any loss of data. Command is:'qpdf input filename outputfilename'. I was able to open the same book in which I lost the data, without any problems, I don't known anything about qpdf, it just worked. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367797] Kmail crashes trying to reply an email / Can't start after that
https://bugs.kde.org/show_bug.cgi?id=367797 Øystein Olsen changed: What|Removed |Added CC||dr.sci...@gmail.com --- Comment #2 from Øystein Olsen --- I have the same problem. A possible work-around is to remove sonnet-plugins: $ sudo apt-get purge sonnet-plugins* You then loose spellchecking, but kmail started again on my machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367615] Launcher hangs on unavailable nfs mount in home directory
https://bugs.kde.org/show_bug.cgi?id=367615
Deepankar Sharma changed:
What|Removed |Added
Status|NEEDSINFO |UNCONFIRMED
Resolution|WAITINGFORINFO |---
--- Comment #4 from Deepankar Sharma ---
I found the offending syscall, it was a lstat. Here is the output from strace,
last column shows time spent inside the call. ->
lstat("/home/dman/mounts/nas/data/lect4.mp4", 0x7fffd3e0) = -1 EHOSTDOWN
(Host is down) <9.997394>
I suspect that lstat is being called on recently accessed files?
ls blocks too in this case.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 367801] New: Two monitors are blacks
https://bugs.kde.org/show_bug.cgi?id=367801 Bug ID: 367801 Summary: Two monitors are blacks Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: frenchte...@gmail.com CC: plasma-b...@kde.org This bug may be related to https://bugs.kde.org/show_bug.cgi?id=365602, but I'm not sure, so I report a new one. My computer has two nvidia-based video cards (latest nvidia driver) and 3 physical monitors ; each one is a separate X screen and xrandr is unavailable. I'm currently running Ubuntu 2012 for 4 years because it has the last version of KDE to support my configuration (KDE SC 4.9.5). Often since, I've tried to update to the last version with no success ; others like Gnome or LXDE works ok, but KDE does not. Last weekend for the first time I had limited success, which lead me to the bug referenced at the top of this post. I've installed the last Ubuntu with the last packages from the Neon unstable repository ; now KDE starts but with the following symptom: - when KDE start all three monitors show the KDE logo but the two non-main monitors go quickly black - the main monitor works OK, the other two are black but seems to be working "offscreen" : if I take a window and drag it to a second monitor, I see the "moving window" mouse cursor. It feels like there's a black mask between the window and the mouse cursor. Unpluging or disabled the screen don't change anything. How can I help debug this problem? Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367792] Can't see the previous frame using the onion skin
https://bugs.kde.org/show_bug.cgi?id=367792 wolthera changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Click on the areas saying -2, -1, 0, 1, 2. This is a buggy default that snuck in. The reason there's no report for it, is because the bug is already fixed in master, and will be in the next version. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #28 from darkba...@linuxsystems.it --- Created attachment 100750 --> https://bugs.kde.org/attachment.cgi?id=100750&action=edit kscreen.log kscreen.log after failed attempt -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #29 from darkba...@linuxsystems.it --- Created attachment 100751 --> https://bugs.kde.org/attachment.cgi?id=100751&action=edit qdbus_KWin_supportInformation qdbus org.kde.KWin /KWin supportInformation after failed attempt -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #30 from darkba...@linuxsystems.it --- Created attachment 100752 --> https://bugs.kde.org/attachment.cgi?id=100752&action=edit plasma_backtrace.log Also, did you notice the compositor settings window at the start of my previous video? Here it is: https://drive.google.com/open?id=0Bwe9Wtc-5xF1dk5JZlg5QXJuV2c You are not supposed to get it unless something's wrong. Also in my previous video I didn't notice the Crash Reporting Assistant after disabling the laptop's main monitor, but it seems plasma crashed. Here is the log (attached plasma_backtrace.log) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367802] New: kontact crashes on quit
https://bugs.kde.org/show_bug.cgi?id=367802 Bug ID: 367802 Summary: kontact crashes on quit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: marara...@gmx.net Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: A normal exit of kontact repeatedly leads to a crash after adjusting width or height of columns in kmail interface. After restart and not touching any UI elements, kontact quits successfully. Alas, without change the subject-column in the message-list pane is set to zero width, columns of unread and total in folder pane are invisible, favourite-folder pane is way to small ... The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2bc0e607c0 (LWP 6999))] Thread 8 (Thread 0x7f2ae67b7700 (LWP 7115)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2baab2b9cb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2baab2b9f9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2b48f6f700 (LWP 7007)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bbb126443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2bbb4480a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2b49770700 (LWP 7006)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bbb126443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2bbb4480a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2b49f71700 (LWP 7005)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bbb126443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2bbb4480a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f2b4a772700 (LWP 7004)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bbb12546d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2bbb4480a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f2b9a707700 (LWP 7002)): #0 0x7f2bb6e7d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bbb4195d3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2bbb4195f9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f2b9b918700 (LWP 7001)): #0 0x7f2bbdb0fccd in read () at /lib64/libc.so.6 #1 0x7f2bb51a3b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2bb5162999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2bb5162df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2bb5162f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2bbe62ff7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2bbe5df8cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2bbe42606a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2bbcd5b4b5 in () at /usr/lib64/libQt5DBus.so.5 #9 0x7f2bbe42a899 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f2bb6e790a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f2bbdb1c02d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f2bc0e607c0 (LWP 6999)): [KCrash Handler] #6 0x7f2bbda6c0c7 in raise () at /lib64/libc.so.6 #7 0x7f2bbda6d478 in abort () at /lib64/libc.so.6 #8 0x7f2bbdaa9784 in () at /lib64/libc.so.6 #9 0x7f2bbdaaf026 in malloc_printerr () at /lib64/libc.so.6 #10 0x7f2bbdaaffcd in _int_free () at /lib64/libc.so.6 #11 0x7f2bb8d7c21e in KCoreConfigSkeleton::~KCoreConfigSkeleton() () at /usr/lib64/libKF5ConfigCore.so.5 #12 0x7f2b31863bc9 in MessageViewer::MessageViewerSettings::~MessageV
[kontact] [Bug 367802] kontact crashes on quit
https://bugs.kde.org/show_bug.cgi?id=367802 Mara Raram changed: What|Removed |Added CC||marara...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #31 from darkba...@linuxsystems.it --- Created attachment 100753 --> https://bugs.kde.org/attachment.cgi?id=100753&action=edit plasma_backtrace_nomst.log > Does this always happen with the same monitor? Could you try switching the > cables around > and see if it's random, or if you could pin it down to one of the connectors > or displays? It always happen to the monitor on the right (DP1-1), but simply because it is the "secondary" monitor of the MST setup. The laptop's mDP cable is attached to the monitor on the left (DP1-8), the output of which is then attached to the monitor on the right (DP1-1). If I switch them nothing changes, the "black" one is always the "secondary". > If your laptop has an HDMI port, could you hook up one of the Dell displays > to that and see > if it shows the problem as well? It doesn't have HDMI, but I have an mDP->HDMI adapter if you want. Anyway I think the problem is MST, so I can simply disable it in the monitor on the left and the right monitor will be a duplicate, not seen by the system. This is how I disable MST on the left monitor: 1) https://drive.google.com/open?id=0Bwe9Wtc-5xF1dU5qU0RYQ2ZiT28 2) https://drive.google.com/open?id=0Bwe9Wtc-5xF1eFVqMERfTlVlNms Here is the video with MST turned off: https://www.youtube.com/watch?v=a2hgzNzo8PM&feature=youtu.be First thing to notice: there is no compositor settings window anymore at startup! This is a good sign, because you are not supposed to see it unless there are troubles with compositing. Second thing to notice: no back screens. Third thing to notice: Crash Reporting Assistant still pops up after disabling the laptop's main monitor (see attached plasma_backtrace_nomst.log) > Love your videos and screen setup, by the way. :) Thanks, I both love and hate my multi-screen setup. I love it because it's awesome to code with it and a mechanical keyboard. I hate it because I had lots of multi-screen troubles with Plasma and I love to use Plasma as well :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367803] New: Crash when viewing file.
https://bugs.kde.org/show_bug.cgi?id=367803
Bug ID: 367803
Summary: Crash when viewing file.
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: m...@flherne.uk
Just compiled git master of KDevelop/kdevplatform/kdev-python, having been
using the 5.0 branch up to now. KDevelop crashes when opening/viewing any file,
regardless of the content.
kdevelop --ps works fine. Selecting any of my existing sessions, all of which
have open files, triggers a crash. Creating a new session does not crash,
giving a working KDevelop window, until I open or create a file.
Reproducible: Always
Steps to Reproduce:
1. Start kdevelop.
2. Open or create a file.
Backtrace is somewhat variable, but always seems to finish inside addPlugin().
CLI output and backtrace below:
(gdb) run
Starting program: /usr/bin/kdevelop
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffd60ba700 (LWP 17522)]
[New Thread 0x7fffc700 (LWP 17523)]
org.kde.knotifications: Audio notification requested, but sound file from
notifyrc file was not found, aborting audio notification
[New Thread 0x7fffc18c1700 (LWP 17524)]
cannot find .rc file "kdevlldbui.rc" for component "kdevlldb"
[New Thread 0x7fffb1ae3700 (LWP 17525)]
Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
0x7559306a in KActionCollection::addAssociatedWidget(QWidget*) () from
/usr/lib/libKF5XmlGui.so.5
(gdb) bt full
#0 0x7559306a in KActionCollection::addAssociatedWidget(QWidget*) ()
from /usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#1 0x755ebc4e in KXMLGUIClient::beginXMLPlug(QWidget*) () from
/usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#2 0x755f7d43 in KXMLGUIFactory::addClient(KXMLGUIClient*) () from
/usr/lib/libKF5XmlGui.so.5
No symbol table info available.
#3 0x77a2d228 in KDevelop::MainWindowPrivate::addPlugin
(this=0x87ee70, plugin=0x277afd0) at
/home/flh/projects/kdevplatform/shell/mainwindow_p.cpp:97
__PRETTY_FUNCTION__ = "void
KDevelop::MainWindowPrivate::addPlugin(KDevelop::IPlugin*)"
ownClient = 0x2768d68
#4 0x77a2cb8f in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KDevelop::MainWindowPrivate::*)(KDevelop::IPlugin*)>::call (f=
(void (KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x77a2d022
, o=0x87ee70,
arg=0x7fffa4f0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:507
No locals.
#5 0x77a2c610 in QtPrivate::FunctionPointer::call,
void> (f=
(void (KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x77a2d022
, o=0x87ee70,
arg=0x7fffa4f0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:526
No locals.
#6 0x77a2baaf in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x8e9de0,
r=0x87ee70, a=0x7fffa4f0, ret=0x0)
at /usr/include/qt/QtCore/qobject_impl.h:149
No locals.
#7 0x710ea85e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#8 0x761c299f in KDevelop::IPluginController::pluginLoaded
(this=0x8e7db0, _t1=0x277afd0) at
/home/flh/projects/kdevplatform/build/interfaces/moc_iplugincontroller.cpp:235
_a = {0x0, 0x7fffa4e0}
#9 0x77a38604 in KDevelop::PluginController::loadPluginInternal
(this=0x8e7db0, pluginId=...) at
/home/flh/projects/kdevplatform/shell/plugincontroller.cpp:565
timer = {t1 = 147598, t2 = 299522362}
info = {m_metaData = {d = 0x9addf0, o = 0xa8b218}, m_fileName = {static
null = {}, d = 0x9a5a30}, d = {d = 0x0}}
__PRETTY_FUNCTION__ = "KDevelop::IPlugin*
KDevelop::PluginController::loadPluginInternal(const QString&)"
missingInterfaces = {> = {>
= {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x7116c180 }, d =
0x7116c180 }}, }
failedDependency = {static null = {}, d =
0x7116a360 }
loader =
factory = 0x89c3f0
plugin = 0x277afd0
group =
#10 0x77a3908a in KDevelop::PluginControlleroperator()(const KPluginMetaData &) const
(__closure=0x7fffaa30, info=...)
at /home/flh/projects/kdevplatform/shell/plugincontroller.cpp:645
plugin = 0x0
plugins = @0x7fffaba0: {> =
{}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x7116c180 }, d =
0x7116c180 }}
this = 0x8e
[calligraplan] [Bug 317022] Scheduler doesn't take actual finish times into account
https://bugs.kde.org/show_bug.cgi?id=317022 Dag Andersen changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Dag Andersen --- You can add a sub-schedule to your schedule and reschedule the project. It will then take finished tasks and remaining effort into account when scheduling. -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 317022] Scheduler doesn't take actual finish times into account
https://bugs.kde.org/show_bug.cgi?id=317022 Dag Andersen changed: What|Removed |Added CC||pe...@adrieng.fr --- Comment #4 from Dag Andersen --- *** Bug 320179 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 320179] Scheduler doesn't take into account progresses on tasks
https://bugs.kde.org/show_bug.cgi?id=320179 Dag Andersen changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Dag Andersen --- *** This bug has been marked as a duplicate of bug 317022 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367803] Crash when viewing file.
https://bugs.kde.org/show_bug.cgi?id=367803 Francis Herne changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Francis Herne --- My fault, didn't properly delete some files when upgrading. Thanks to olijg on IRC. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367804] New: Ratio option doesn't calculate the right rect.
https://bugs.kde.org/show_bug.cgi?id=367804 Bug ID: 367804 Summary: Ratio option doesn't calculate the right rect. Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com When using the ratio option with rotation, the paint rect doesn't get updated, meaning you end up with weirdly cut-off dabs. Reproducible: Always Steps to Reproduce: 1. Make a highly spaces brush that rotates the dab, but also uses the ratio modifier somehow. Draw diagonal lines. -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 329430] Description fields outputs html tags when used in Reports
https://bugs.kde.org/show_bug.cgi?id=329430 Dag Andersen changed: What|Removed |Added Resolution|--- |INVALID CC||dand...@get2net.dk Status|UNCONFIRMED |RESOLVED --- Comment #2 from Dag Andersen --- KReport field and text items does not know about rich text. You can use the web item to display rich text- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367804] Ratio option doesn't calculate the right rect.
https://bugs.kde.org/show_bug.cgi?id=367804 --- Comment #1 from wolthera --- https://www.dropbox.com/s/77iedn81og3iqjy/offsetbug-2.ogv?dl=0 < link to video. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286398] Allow to input coordinates manually in items list
https://bugs.kde.org/show_bug.cgi?id=286398 Pascal Volat changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286398] Allow to input coordinates manually in items list
https://bugs.kde.org/show_bug.cgi?id=286398 --- Comment #7 from caulier.gil...@gmail.com --- Pascal, Why this file have been closed ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367774] csv format doesn't export
https://bugs.kde.org/show_bug.cgi?id=367774 László Fazekas changed: What|Removed |Added CC||mn...@freemail.hu --- Comment #2 from László Fazekas --- fazek committed rKRITAeda471fe0ebd: bug 367774: csv format doesn't export (authored by fazek). please try this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367788] It should be possible to save Metadata templates
https://bugs.kde.org/show_bug.cgi?id=367788 --- Comment #2 from Wolfgang Scheffner --- O.k., I copied the template.xml from the 4.x location to the 5.x location and it works. digiKam comes up with my old templates. But: >For 4.x, file are located to ~/.kde4/share/apps/digikam/ This is not quite right, at least not for Kubuntu. The correct path is ~/.kde/share/apps/digikam >With 5.x, file must be moved to ~/.local/share/apps/digikam/ This is also not the path under Kubuntu, it's ~/.local/share/digikam/ >So there is no need a save/load methods for templates. And here I don't agree as a matter of principle. digiKam is a program for photographers, i.e. "graphic people", and those like to use GUIs and not moving around files by browser or even terminal (there are exceptions, I know). And even if they were willing to go through that "ordeal", how can they know where to find that file? So the absolute minimum IMHO would be a hint, a tipp within the template manager where to find that file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286398] Allow to input coordinates manually in items list
https://bugs.kde.org/show_bug.cgi?id=286398 --- Comment #8 from Pascal Volat --- (In reply to caulier.gilles from comment #7) > Pascal, > > Why this file have been closed ? > > Gilles Caulier Hi Gilles, This bug is not in the agenda, several versions are being followed since the opening. That's why I ended. Pascal VOLAT -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286398] Allow to input coordinates manually in items list
https://bugs.kde.org/show_bug.cgi?id=286398 --- Comment #9 from caulier.gil...@gmail.com --- But the problem still valid no ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367788] It should be possible to save Metadata templates
https://bugs.kde.org/show_bug.cgi?id=367788 --- Comment #3 from caulier.gil...@gmail.com --- Well for the last point, i'm not agree. As explained in bug https://bugs.kde.org/show_bug.cgi?id=364258, the files must be moved to new location automatically. No need an extra rules for that. But for the moment, it's not clear why this is not yet done properly. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 367805] New: kalarm crashed editing an alarm
https://bugs.kde.org/show_bug.cgi?id=367805 Bug ID: 367805 Summary: kalarm crashed editing an alarm Product: kalarm Version: 2.11.4-5ak Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: a...@polverini.org Application: kalarm (2.11.4-5ak) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I clicked "edit" on the window where the alarm popped out. It was a daily alarm -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2031755940 (LWP 11588))] Thread 3 (Thread 0x7f200de6f700 (LWP 11593)): #0 0x7f2029d9be8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f202401b39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f202401b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f202a8eda9b in QEventDispatcherGlib::processEvents (this=0x7f20040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f202a894dea in QEventLoop::exec (this=this@entry=0x7f200de6ec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f202a6b18a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f202a6b684e in QThreadPrivate::start (arg=0x23bd180) at thread/qthread_unix.cpp:331 #7 0x7f20249786fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f2029da7b5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f200e670700 (LWP 11591)): #0 0x7f2029d9be8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f202401b39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f202401b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f202a8eda9b in QEventDispatcherGlib::processEvents (this=0x7f2008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f202a894dea in QEventLoop::exec (this=this@entry=0x7f200e66fc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f202a6b18a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f202a6b684e in QThreadPrivate::start (arg=0x23c2400) at thread/qthread_unix.cpp:331 #7 0x7f20249786fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f2029da7b5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f2031755940 (LWP 11588)): [KCrash Handler] #6 0x7f202ad2826c in QWeakPointer::data (this=0x30e4fb0) at ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:588 #7 QPointer::data (this=0x30e4fb0) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:70 #8 QPointer::operator QScreen* (this=0x30e4fb0) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:76 #9 QPlatformScreen::screen (this=this@entry=0x22f2a50) at kernel/qplatformscreen.cpp:116 #10 0x7f20123ad7cc in QXcbWindow::create (this=0x3acf540) at qxcbwindow.cpp:426 #11 0x7f201239a001 in QXcbIntegration::createPlatformWindow (this=, window=0x3ac6c30) at qxcbintegration.cpp:201 #12 0x7f202ad425c4 in QWindowPrivate::create (this=0x3ac6c90, recursive=recursive@entry=false) at kernel/qwindow.cpp:392 #13 0x7f202ad427cb in QWindow::create (this=this@entry=0x3ac6c30) at kernel/qwindow.cpp:548 #14 0x7f202b3233c0 in QWidgetPrivate::create_sys (this=this@entry=0x243b080, window=window@entry=0, initializeWindow=initializeWindow@entry=true, destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1454 #15 0x7f202b3237fb in QWidget::create (this=0x23a62c0, window=0, initializeWindow=, destroyOldWindow=) at kernel/qwidget.cpp:1318 #16 0x7f202b323e31 in QWidgetPrivate::createWinId (this=, winid=0) at kernel/qwidget.cpp:2514 #17 0x7f202b321d07 in QWidget::setAttribute (this=0x25945a0, attribute=attribute@entry=Qt::WA_NativeWindow, on=on@entry=true) at kernel/qwidget.cpp:11076 #18 0x7f202b321abe in QWidgetPrivate::enforceNativeChildren (this=0x249b060) at ../../include/QtWidgets/5.5.1/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:574 #19 QWidget::setAttribute (this=0x27e4c50, attribute=, on=) at kernel/qwidget.cpp:11074 #20 0x7f202b84258f in KWindowSystem::setMainWindow(QWidget*, unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 #21 0x0052e34c in MessageWin::slotEdit() () #22 0x7f202a8c5e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffc21a4a640, r=0x2c542b0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #23 QMetaObject::activate (sender=sender@entry=0x31ba190, signalOffset=, lo
[Discover] [Bug 367806] New: updater problem
https://bugs.kde.org/show_bug.cgi?id=367806 Bug ID: 367806 Summary: updater problem Product: Discover Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: dirk.de.schepp...@telenet.be updater gives error pakket:software-properties-common + pakket:software-properties-kde +pakket:python3-software-propertiesor An error occurred while applying changes: PLease help Dirk De Schepper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367807] New: Media player reposition panel widgets when starting the next playlist track or repeating the track
https://bugs.kde.org/show_bug.cgi?id=367807 Bug ID: 367807 Summary: Media player reposition panel widgets when starting the next playlist track or repeating the track Product: plasmashell Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: safa1996alful...@gmail.com CC: plasma-b...@kde.org When I have a player (SMPlayer currently), and it has several tracks in the playlist, the media player widget disappears from the panel when it reaches to the end of the first track, and reappears when the next track strats. This causes the widgets in the Panel to be repositioned, which is annoying. A good idea is to wait 5 seconds (for example) for the player to starts the next track or repeats the current. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 111743] Color themes + optionally derive color options from current system palette
https://bugs.kde.org/show_bug.cgi?id=111743 --- Comment #8 from andydecle...@gmail.com --- Is there any likelihood of Konversation getting color scheme support (not setting each color individually from scratch each time the user wants to test a new scheme) within, say, the next year? I really like the client otherwise, but after 11 years of waiting for this . . . unless this is actually gonna happen I need to investigate replacements; so I just want to know if this feature can be realistically expected. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 366075] Create New Folder shortcut F10 not indicated in the menu File->Create New
https://bugs.kde.org/show_bug.cgi?id=366075 Elvis Angelaccio changed: What|Removed |Added Version|4.14.2 |unspecified Product|dolphin |kio Ever confirmed|0 |1 Component|general |general Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Status|UNCONFIRMED |CONFIRMED CC||elvis.angelac...@kdemail.ne ||t --- Comment #2 from Elvis Angelaccio --- Moving to KIO. Patch in https://git.reviewboard.kde.org/r/128759/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 366075] Create New Folder shortcut F10 not indicated in the menu File->Create New
https://bugs.kde.org/show_bug.cgi?id=366075 Elvis Angelaccio changed: What|Removed |Added Product|kio |frameworks-kio CC||kdelibs-b...@kde.org Component|general |general Version|unspecified |5.24.0 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367749] Kontact crashes
https://bugs.kde.org/show_bug.cgi?id=367749 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 365944 *** -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 365944] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=365944 --- Comment #12 from Denis Kurz --- *** Bug 367749 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 367808] New: kontact crashed when closing
https://bugs.kde.org/show_bug.cgi?id=367808 Bug ID: 367808 Summary: kontact crashed when closing Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@munin-soft.de Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.7.1-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160822) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Currently I have seemingly some issues with kontact/akonadi. Here I deleted the last serach folder which led to a weird UI of kmail (folder tree with empty labels). I wnated to restart, therefore closed it, which led to this crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2cb2e60900 (LWP 18376))] Thread 18 (Thread 0x7f2be0c96700 (LWP 18471)): #0 0x7f2cafa0fa1d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2ca839b056 in g_main_context_iterate (priority=, n_fds=1, fds=0x7f2bcc002c20, timeout=, context=0x7f2bcc000990) at gmain.c:4135 #2 0x7f2ca839b056 in g_main_context_iterate (context=context@entry=0x7f2bcc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f2ca839b16c in g_main_context_iteration (context=0x7f2bcc000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f2cb0552aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2bcc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f2cb04fa76a in QEventLoop::exec(QFlags) (this=this@entry=0x7f2be0c95cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2cb03203b3 in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7f2cb03252d8 in QThreadPrivate::start(void*) (arg=0x1300260) at thread/qthread_unix.cpp:341 #8 0x7f2ca8bbe474 in start_thread (arg=0x7f2be0c96700) at pthread_create.c:333 #9 0x7f2cafa183ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f2be1d9e700 (LWP 18468)): #0 0x7f2cafa25081 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7f2be1d9da20) at ../sysdeps/unix/clock_gettime.c:93 #1 0x7f2cb03d0d96 in qt_gettime() (ts=0x7f2be1d9da20, clock=) at tools/qelapsedtimer_unix.cpp:105 #2 0x7f2cb03d0d96 in qt_gettime() (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #3 0x7f2cb03d0d96 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:165 #4 0x7f2cb0550699 in QTimerInfoList::updateCurrentTime() (this=this@entry=0x7f2bd80030d0) at kernel/qtimerinfo_unix.cpp:84 #5 0x7f2cb0550c45 in QTimerInfoList::timerWait(timespec&) (this=0x7f2bd80030d0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #6 0x7f2cb0551fde in timerSourcePrepare(GSource*, gint*) (timeout=0x7f2be1d9daf4, src=) at kernel/qeventdispatcher_glib.cpp:126 #7 0x7f2cb0551fde in timerSourcePrepare(GSource*, gint*) (source=, timeout=timeout@entry=0x7f2be1d9daf4) at kernel/qeventdispatcher_glib.cpp:159 #8 0x7f2ca839a5a9 in g_main_context_prepare (context=context@entry=0x7f2bd8000990, priority=priority@entry=0x7f2be1d9db80) at gmain.c:3442 #9 0x7f2ca839af7b in g_main_context_iterate (context=context@entry=0x7f2bd8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #10 0x7f2ca839b16c in g_main_context_iteration (context=0x7f2bd8000990, may_block=may_block@entry=1) at gmain.c:3901 #11 0x7f2cb0552aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2bd80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #12 0x7f2cb04fa76a in QEventLoop::exec(QFlags) (this=this@entry=0x7f2be1d9dcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #13 0x7f2cb03203b3 in QThread::exec() (this=) at thread/qthread.cpp:500 #14 0x7f2cb03252d8 in QThreadPrivate::start(void*) (arg=0x1de03e0) at thread/qthread_unix.cpp:341 #15 0x7f2ca8bbe474 in start_thread (arg=0x7f2be1d9e700) at pthread_create.c:333 #16 0x7f2cafa183ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f2be2bd0700 (LWP 18411)): #0 0x7f2ca839a563 in g_main_context_prepare (context=context@entry=0x7f2bd4000990, priority=priority@entry=0x7f2be2bcfb80) at gmain.c:3424 #1 0x7f2ca839af7b in g_main_context_iterate (context=context@entry=0x7f2bd4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #2 0x7f2ca839b16c in g_main_context_iteration (context=0x7f2bd4000990, may_block=may_block@entry=1) at gmain.c:3901 #3 0x7f2cb0552aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2bd40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f2cb04fa76a in QEv
[kde] [Bug 367745] KDE neon User Edition 5.7 - xenial 16.04 - sudo apt-get upgrade - appstream is crashing the install or upgrade of software - appstreamcli: symbol lookup error: appstreamcli: undefin
https://bugs.kde.org/show_bug.cgi?id=367745 Cristian Umaña changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Cristian Umaña --- Hi, I confused, Does KDE Neon has a different bug tracking system? Regards -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366564] Please change autostart defaults to not interfere with non-KDE desktops
https://bugs.kde.org/show_bug.cgi?id=366564 Albert Vaca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Albert Vaca --- KDE Connect works in every desktop, so it's by design that it autostarts everywhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366718] Dragging url and hovering a task does not reveal hovered window
https://bugs.kde.org/show_bug.cgi?id=366718 --- Comment #2 from anewuser --- I confirm that this has been fixed on KDE Neon. You can close this issue now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 367632] Kmail2 v 5.3.0 -random crashes (seg fault 11) and freezing desktop
https://bugs.kde.org/show_bug.cgi?id=367632 Denis Kurz changed: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #5 from Denis Kurz --- The crash happens deep down in some OpenGL context in the nouveau driver. Does this still happen if you use the nvidia driver instead of the nouveau one? Also, which version of nouveau do you use when this crash occurs? Can you test it with another version? Which version of Qt do you have installed? I assume you are on openSuSE Tumbleweed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 --- Comment #2 from Tony --- Yes it is fixed, close it down. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 362596] shared clipboard between two pc's and phone cause plasma UI freeze and app to crash
https://bugs.kde.org/show_bug.cgi?id=362596 Albert Vaca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Albert Vaca --- It's fixed in 1.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367809] New: Date label almost overlaps panel, not centered vertically
https://bugs.kde.org/show_bug.cgi?id=367809 Bug ID: 367809 Summary: Date label almost overlaps panel, not centered vertically Product: plasmashell Version: master Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: heire...@exherbo.org Created attachment 100754 --> https://bugs.kde.org/attachment.cgi?id=100754&action=edit before screenshot With the latest master the digital clock almost overlaps the panel when "Show date" is enabled. Or at least it's glued to the border of the panel. As a consequence it's isn't centered vertically. I've attached two screenshots, one of 5.7.4 and one of current master. The commit which introduced this seems to be 9016eaae22db317811f5fdae29bdeba594cf6310 "Don't set both font and pixel size in DigitalClock". When I revert it the clock looks the same as with 5.7.4. Qt version is 5.7.0 in both cases. -- You are receiving this mail because: You are watching all bug changes.
