[plasma-nm] [Bug 368782] NetworkManager widget not update connection status
https://bugs.kde.org/show_bug.cgi?id=368782 --- Comment #2 from Piotr Rogowski --- Thanks for fast response. Yes I have NetworkManager 1.4.0. I temporary downgraded it to 1.2.4 and it is working again, thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368784] New: Logout/reboot/shutdown window appears on first on the left screen and it has primary screen width
https://bugs.kde.org/show_bug.cgi?id=368784 Bug ID: 368784 Summary: Logout/reboot/shutdown window appears on first on the left screen and it has primary screen width Product: plasmashell Version: 5.7.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: bar...@bugpoint.pl CC: plasma-b...@kde.org I have two screens connected. 1280x720 on the left and 1920x1080 on the right. 1920x1080 is my primary screen. 1280x720 is mostly turned off but is connected and system thinks it is on. When I click logout/reboot/shutdown button from system menu then splash screen window appears. Problem is that it appears on the left screen and I can only see little part of it because it has 1920 width and doesn't fit on my left screen. Reproducible: Always Steps to Reproduce: 1. have two screens with different resolution 2. split them to left and right screen 3. click logout button Actual Results: Can't see logout screen Expected Results: Logout screen should be seen on every screen the same as login screen is. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #3 from Burkhard Lueck --- VM with neo-devedition-gitstable Frameworks 5.27.0 Kate 16.08.1 Plasma 5.7.5 Shows KDE File Dialog and is OK -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368764] Crash when opening a .kra file in krita
https://bugs.kde.org/show_bug.cgi?id=368764 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Boudewijn Rempt --- I can reproduce, but if you want to report bugs in the future and build Krita yourself anyway, please build with RelWithDebInfo or KritaDevs -- this backtrace misses line number information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de, ||mgraess...@kde.org --- Comment #2 from Kai Uwe Broulik --- On a desktop you have a right mouse button? Adding Martin, iirc he said on Wayland we might be able to implement this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366629] Video output is corrupted
https://bugs.kde.org/show_bug.cgi?id=366629 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Martin Gräßlin --- great! I'm happy that helped. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #1 from Heiko Tietze --- Isn't the long press the only means on desktop environment? Why shouldn't it work on touch screens. (+bug -usability imho) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368783] New: Konsole opens few minutes after launch
https://bugs.kde.org/show_bug.cgi?id=368783 Bug ID: 368783 Summary: Konsole opens few minutes after launch Product: konsole Version: 16.08.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: piotrekrogow...@gmail.com when konsole is opened from kickoff or from search bar, window appear after few minutes after that. When konsole is opened from other console (like Yaquake) it is opened immediately. New process is spawned also immediately in both cases. Reproducible: Always Steps to Reproduce: 1. Open konsole Actual Results: Konsole is opened after few minutes Expected Results: Konsole should open without delay This problem was introduced after kde framework update to 5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 368782] NetworkManager widget not update connection status
https://bugs.kde.org/show_bug.cgi?id=368782 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- If you have NetworkManager 1.4.0 you need to wait either for KDE Frameworks update or for NetworkManager update, there are fixes for this issue in both. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366629] Video output is corrupted
https://bugs.kde.org/show_bug.cgi?id=366629 --- Comment #2 from Detlev Casanova --- Indeed, that is fixed with modesetting. It also seems to solve another problem I had. Thanks for the input :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 368782] New: NetworkManager widget not update connection status
https://bugs.kde.org/show_bug.cgi?id=368782 Bug ID: 368782 Summary: NetworkManager widget not update connection status Product: plasma-nm Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: piotrekrogow...@gmail.com CC: lu...@kde.org wifi: widget always shows that you aren't connected to any network (wifi icon with question mark) ethernet: always shows connection status as connecting (ethernet icon with spinner) Problem introduced after update kde frameworks to 5.26.0 Plasma version: 5.7.4 Reproducible: Always Steps to Reproduce: 1. open network manager widget Actual Results: displayed information isn't valid Expected Results: display up to date status This problem is present in 2 independent machines -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368781] New: Kwin Error
https://bugs.kde.org/show_bug.cgi?id=368781 Bug ID: 368781 Summary: Kwin Error Product: plasmashell Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: solomonirai...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: - Kwin windows remains fixed in the background, unclickable, after clicking on the 'close' button. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc24d4b68c0 (LWP 4361))] Thread 9 (Thread 0x7fc183b97700 (LWP 4748)): #0 0x7fc247b8be8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc24491c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc24491c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2484b8a9b in QEventDispatcherGlib::processEvents (this=0x7fc17c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fc24845fdea in QEventLoop::exec (this=this@entry=0x7fc183b96c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fc24827c8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fc24b4b8ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc24828184e in QThreadPrivate::start (arg=0x1d8fed0) at thread/qthread_unix.cpp:331 #8 0x7fc24736e6fa in start_thread (arg=0x7fc183b97700) at pthread_create.c:333 #9 0x7fc247b97b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fc193fff700 (LWP 4745)): #0 0x7ffc81bd59a9 in ?? () #1 0x7ffc81bd5cd5 in clock_gettime () #2 0x7fc247ba5fb6 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7fc193ffea40) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fc248331c16 in qt_clock_gettime (ts=0x7fc193ffea40, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0x7fc2484b6529 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fc18c00fd40) at kernel/qtimerinfo_unix.cpp:84 #7 0x7fc2484b6a95 in QTimerInfoList::timerWait (this=0x7fc18c00fd40, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0x7fc2484b83cc in timerSourcePrepareHelper (timeout=0x7fc193ffeb04, src=) at kernel/qeventdispatcher_glib.cpp:127 #9 idleTimerSourcePrepare (source=, timeout=0x7fc193ffeb04) at kernel/qeventdispatcher_glib.cpp:207 #10 0x7fc24491b92d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fc24491c2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fc24491c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fc2484b8a9b in QEventDispatcherGlib::processEvents (this=0x7fc18c001330, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #14 0x7fc24845fdea in QEventLoop::exec (this=this@entry=0x7fc193ffecc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7fc24827c8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #16 0x7fc1866897d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #17 0x7fc24828184e in QThreadPrivate::start (arg=0x2f99a60) at thread/qthread_unix.cpp:331 #18 0x7fc24736e6fa in start_thread (arg=0x7fc193fff700) at pthread_create.c:333 #19 0x7fc247b97b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fc21b1c4700 (LWP 4523)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc24cf01bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fc24cf01c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fc24736e6fa in start_thread (arg=0x7fc21b1c4700) at pthread_create.c:333 #4 0x7fc247b97b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fc2209b5700 (LWP 4510)): #0 0x7fc247b8be8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc24491c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc24491c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2484b8a9b in QEventDispatcherGlib::processEvents (this=0x7fc2140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fc24845fdea in QEventLoop::exec (this=this@entry=0x7fc22
[valgrind] [Bug 352767] Wine/valgrind: Warning: noted but unhandled ioctl 0x5307 with no size/direction hints. (CDROMSTOP)
https://bugs.kde.org/show_bug.cgi?id=352767 --- Comment #2 from austinengl...@gmail.com --- (In reply to Julian Seward from comment #1) > Austin, do you have a patch for this? Or for bug 348616 ? Not currently, but I took a quick look. There are several more syscalls that wine uses in the source that are bsd/osx specific, but I can't easily test. Should I stub those / put fixme's, or just fix linux/generic? Or only fix the two that currently have bugs? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #2 from Burkhard Lueck --- Ubuntu 16.04.1 LTS + Plasma 5.6.5 + Frameworks 5.23 + kate 15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368779] Missing translations to Categories column in Kipi Plugins settings
https://bugs.kde.org/show_bug.cgi?id=368779 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 368759] lack of translation fo Polish commend ustalKierunek
https://bugs.kde.org/show_bug.cgi?id=368759 Burkhard Lueck changed: What|Removed |Added Version|0.8.1 beta |unspecified CC||lu...@hube-lueck.de Component|general |pl Assignee|c...@kde.nl |kdei18n-pl-uw...@lists.sour ||ceforge.net Product|kturtle |i18n --- Comment #1 from Burkhard Lueck --- Version of frameworks and KDE Applications? Locale pl in stable (Applications 16.04 / 16.08) is fully translated and has no command "ustalKierunek" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Kåre Särs --- Thanks for the report. Are you running Plasma5 or some other DE? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 Burkhard Lueck changed: What|Removed |Added Ever confirmed|0 |1 CC||lu...@hube-lueck.de Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #11 from earl_c...@yahoo.com --- (In reply to Ivo Raisr from comment #10) > As Philippe pointed out, there is a problem with the existing attachment. > Please have a look what is there inside and re-attach. Yes, that's obviously wrong. Let me resurrect the intended content. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368774] org.kde.plasma.taskmanager - missing keyboard accelerators
https://bugs.kde.org/show_bug.cgi?id=368774 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://quickgit.kde.org/?p ||=plasma-desktop.git&a=commi ||t&h=41064e33b965cd91f3240cd ||ac81cf7ddd5cafdc4 Status|UNCONFIRMED |RESOLVED CC||k...@privat.broulik.de Resolution|--- |FIXED Version Fixed In||5.8.0 --- Comment #1 from Kai Uwe Broulik --- This is fixed in 5.8. I couldn't backport this to 5.7 as it changed translateable strings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #16 from Kai Uwe Broulik --- Yes, it was, but Kubuntu probably doesn't ship the update. Ping your distribution about this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368717] The button for switching language layout is unavailable in Screen Locker.
https://bugs.kde.org/show_bug.cgi?id=368717 Kai Uwe Broulik changed: What|Removed |Added Flags||VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 Sourish Basu changed: What|Removed |Added CC||sourish.b...@gmail.com --- Comment #15 from Sourish Basu --- Was this bug ever fixed? I have plasma-framework 5.18 on Kubuntu 16.04, and I still have this bug, i.e., the notes widget background is always transparent no matter which color I select in the settings. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 368780] New: System Monitor not displaying properly.
https://bugs.kde.org/show_bug.cgi?id=368780 Bug ID: 368780 Summary: System Monitor not displaying properly. Product: ksysguard Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ettupara...@hotmail.com Application: ksysguard (4.11.11) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 4.1.3-040103-generic x86_64 Distribution: Linux Mint 17.2 Rafaela -- Information about the crash: No display of Memory or CPU Usage. The crash can be reproduced every time. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fed235867c0 (LWP 6530))] Thread 2 (Thread 0x7fed0a3bb700 (LWP 6540)): #0 0x7fed22e5afdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fed19fa6fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed19fa70ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed20ad57be in QEventDispatcherGlib::processEvents (this=0x7fecfc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7fed20aa70af in QEventLoop::processEvents (this=this@entry=0x7fed0a3bade0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fed20aa73a5 in QEventLoop::exec (this=this@entry=0x7fed0a3bade0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fed209a3c5f in QThread::exec (this=this@entry=0xde3f70) at thread/qthread.cpp:537 #7 0x7fed20a88823 in QInotifyFileSystemWatcherEngine::run (this=0xde3f70) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7fed209a632f in QThreadPrivate::start (arg=0xde3f70) at thread/qthread_unix.cpp:349 #9 0x7fed1a8bc184 in start_thread (arg=0x7fed0a3bb700) at pthread_create.c:312 #10 0x7fed22e6837d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fed235867c0 (LWP 6530)): [KCrash Handler] #6 WorkSheet::updateInterval (this=0x0) at ../../../ksysguard/gui/WorkSheet.cpp:798 #7 0x7fed2319598e in TopLevel::configureCurrentSheet (this=0xa72410) at ../../../ksysguard/gui/ksysguard.cpp:181 #8 0x7fed23197525 in TopLevel::qt_static_metacall (_o=0x0, _id=11, _a=0x7fffe5b4b2d0, _c=) at ./ksysguard.moc:84 #9 0x7fed20abc87a in QMetaObject::activate (sender=sender@entry=0xada3e0, m=m@entry=0x7fed208ebde0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffe5b4b2d0) at kernel/qobject.cpp:3539 #10 0x7fed1fe3ba62 in QAction::triggered (this=this@entry=0xada3e0, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #11 0x7fed1fe3d433 in QAction::activate (this=this@entry=0xada3e0, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #12 0x7fed2026b509 in QMenuPrivate::activateCausedStack (this=this@entry=0xcc9b50, causedStack=..., action=action@entry=0xada3e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1038 #13 0x7fed2026fa39 in QMenuPrivate::activateAction (this=0xcc9b50, action=0xada3e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1130 #14 0x7fed20273405 in QMenu::mouseReleaseEvent (this=this@entry=0xcb02e0, e=e@entry=0x7fffe5b4ba00) at widgets/qmenu.cpp:2372 #15 0x7fed21824615 in KMenu::mouseReleaseEvent (this=0xcb02e0, e=0x7fffe5b4ba00) at ../../kdeui/widgets/kmenu.cpp:464 #16 0x7fed1fe9151a in QWidget::event (this=this@entry=0xcb02e0, event=event@entry=0x7fffe5b4ba00) at kernel/qwidget.cpp:8376 #17 0x7fed2027383b in QMenu::event (this=0xcb02e0, e=0x7fffe5b4ba00) at widgets/qmenu.cpp:2481 #18 0x7fed1fe41e2c in QApplicationPrivate::notify_helper (this=this@entry=0x93f560, receiver=receiver@entry=0xcb02e0, e=e@entry=0x7fffe5b4ba00) at kernel/qapplication.cpp:4567 #19 0x7fed1fe485dd in QApplication::notify (this=this@entry=0x926890, receiver=receiver@entry=0xcb02e0, e=e@entry=0x7fffe5b4ba00) at kernel/qapplication.cpp:4110 #20 0x7fed2176dcca in KApplication::notify (this=0x926890, receiver=0xcb02e0, event=0x7fffe5b4ba00) at ../../kdeui/kernel/kapplication.cpp:311 #21 0x7fed20aa84dd in QCoreApplication::notifyInternal (this=0x926890, receiver=receiver@entry=0xcb02e0, event=event@entry=0x7fffe5b4ba00) at kernel/qcoreapplication.cpp:953 #22 0x7fed1fe47d93 in sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #23 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0xcb02e0, event=event@entry=0x7fffe5b4ba00, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0xcb02e0, buttonDown=buttonDown@entry=0x7fed20927318 , lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3178 #24 0x7fed
[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.
https://bugs.kde.org/show_bug.cgi?id=368689 --- Comment #5 from Jeremy W. Murphy --- (In reply to Jeremy W. Murphy from comment #4) > > If you check that out, try editing the file musser-nishanov.hpp. Sorry, that's "musser_nishanov.hpp". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.
https://bugs.kde.org/show_bug.cgi?id=368689 --- Comment #4 from Jeremy W. Murphy --- (In reply to Milian Wolff from comment #2) > can you please give us an example project (i.e. something we can test > ourselves) and tell us which file you are editing, how, and where, to > reproduce the issue? Best example I can give you is the code that I am working on right now: https://github.com/jeremy-murphy/algorithm/tree/musser-nishanov-search If you check that out, try editing the file musser-nishanov.hpp. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #10 from Ivo Raisr --- As Philippe pointed out, there is a problem with the existing attachment. Please have a look what is there inside and re-attach. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code
https://bugs.kde.org/show_bug.cgi?id=365437 Anton Anikin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||anton.ani...@htower.ru Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368779] Missing translations to Categories column in Kipi Plugins settings
https://bugs.kde.org/show_bug.cgi?id=368779 --- Comment #1 from André Marcelo Alvarenga --- Created attachment 101078 --> https://bugs.kde.org/attachment.cgi?id=101078&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368779] New: Missing translations to Categories column in Kipi Plugins settings
https://bugs.kde.org/show_bug.cgi?id=368779 Bug ID: 368779 Summary: Missing translations to Categories column in Kipi Plugins settings Product: digikam Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: alvare...@kde.org Settings -> Configure digiKam -> Kipi Plugins page See screenshot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 351106] Crash using "Create Copy from Current Image"
https://bugs.kde.org/show_bug.cgi?id=351106 --- Comment #13 from Orlan Rod --- Created attachment 101077 --> https://bugs.kde.org/attachment.cgi?id=101077&action=edit Krita Windows 10 Vid Demonstration of the crash on Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368778] New: KDE Partiton Manager crashed when importing .ISO as partiton table
https://bugs.kde.org/show_bug.cgi?id=368778 Bug ID: 368778 Summary: KDE Partiton Manager crashed when importing .ISO as partiton table Product: partitionmanager Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: iliketurtles...@riseup.net Application: partitionmanager (2.2.1) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-0.rc6.git0.1.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Erroneously selected an .ISO file to import as a partiton table. K Partition Manager immediately crashed after selecting the file. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6bc7617940 (LWP 3846))] Thread 3 (Thread 0x7f6bb42b2700 (LWP 3848)): #0 0x7f6bd2c2c00d in poll () from /lib64/libc.so.6 #1 0x7f6bcc660246 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f6bcc66035c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f6bd3a30d2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f6bd39e202a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f6bd383f533 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f6bd4749779 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f6bd384390a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f6bd069d6ba in start_thread () from /lib64/libpthread.so.0 #9 0x7f6bd2c373cf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f6bbc973700 (LWP 3847)): #0 0x7f6bd2c2c00d in poll () from /lib64/libc.so.6 #1 0x7f6bcbd56d10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f6bcbd58aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f6bc09958d9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f6bd384390a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f6bd069d6ba in start_thread () from /lib64/libpthread.so.0 #6 0x7f6bd2c373cf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f6bc7617940 (LWP 3846)): [KCrash Handler] #6 0x555a6fc9c93d in MainWindow::onImportPartitionTable() () #7 0x7f6bd3a0a2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f6bd4224c22 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #9 0x7f6bd4227652 in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #10 0x7f6bd4395d7a in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5 #11 0x7f6bd439bfec in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) () from /lib64/libQt5Widgets.so.5 #12 0x7f6bd43a0060 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f6bd4272910 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f6bd43a0b0b in QMenu::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f6bd422b63c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f6bd4233c9d in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f6bd39e309a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f6bd423232d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /lib64/libQt5Widgets.so.5 #19 0x7f6bd428d0c3 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f6bd428f303 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f6bd422b63c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f6bd4232de1 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f6bd39e309a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7f6bd3d21d03 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #25 0x7f6bd3d237b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /lib64/libQt5Gui.so.5 #26 0x7f6bd3d0469b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #27 0x7f6bc09cbb20 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #28 0x7f6bcc65ff32 in g_main_context_
[konsole] [Bug 368777] New: Can't use commands for bookmark
https://bugs.kde.org/show_bug.cgi?id=368777 Bug ID: 368777 Summary: Can't use commands for bookmark Product: konsole Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: bookmark Assignee: konsole-de...@kde.org Reporter: tylonhh+kdebugrep...@gmail.com I added the command "nmcli dev show | grep DNS" as an bookmark. But when I run this its "nmcli dev show %7C grep DNS" Reproducible: Always Steps to Reproduce: 1. Add bookmark 2. Adress: nmcli dev show | grep DNS 3. open Bookmark Actual Results: nmcli dev show %7C grep DNS Expected Results: nmcli dev show | grep DNS I know the bookmarks a for locations. But it would be a cool feature also for commands -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 351106] Crash using "Create Copy from Current Image"
https://bugs.kde.org/show_bug.cgi?id=351106 --- Comment #12 from Orlan Rod --- I still have this problem, even with the couple of updates since i last open this bug report, and updated Windows 10. I'll work with anyone to get to the bottom of it. Windows 10 64bit. Intel i7 4770k 16GB ram -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #188 from jamese --- Unplugged my external screen from laptop, next day opened lid, signed in and panel placed on laptop screen in Comment #187 had gone. I added the panel back, result is I now get a minimum of 2 notifications in the Notification area for every notification received. Using KDE Neon User Edition with Plasma 5.7.4 e.g Do the above, load up KDE Connect on Android phone, send a ping to the paired laptop and two notifications appear, one positions above (Y-axis) the other. The lower one seems to be 2 notifications stacked exactly on top of another (Z-axis) as that one has a far darker box-shadow. My guess is that the panel from the external screen and the panel from the laptop screen which disappeared are still adding notifications to the laptop screen along with the new panel I added. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368725] Single tap of wacom pen does not result in brushstroke like a mouse click does
https://bugs.kde.org/show_bug.cgi?id=368725 --- Comment #2 from mattcorb...@gmail.com --- I tried it with the pixel1 brush and a few others, and they all had the same problem. I just now tried a few more brushes, and found that the PixelArt_Square brush works properly with the tablet, in that it can draw a dot with a single tap of the pen. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 368776] Kontact crashing on wayland.....
https://bugs.kde.org/show_bug.cgi?id=368776 --- Comment #1 from Tony --- Created attachment 101076 --> https://bugs.kde.org/attachment.cgi?id=101076&action=edit korganizer backtrace -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 368776] New: Kontact crashing on wayland.....
https://bugs.kde.org/show_bug.cgi?id=368776 Bug ID: 368776 Summary: Kontact crashing on wayland. Product: knotes Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jodr...@live.com CC: myr...@kde.org Application: knotes (5.3.42 pre ()) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: I am doing this from a virtaul box vm. Login to a wayland session and open Kontact, it will crashed right away. This happens due to korganizer, knotes and akregator crashing or having conflicts under wayland. Drkonqui can't generate a backtrace for kontact and akregator, i only get: "Application: Kontact (kontact), signal: Segmentation fault" The crash can be reproduced every time. -- Backtrace: Application: KNotes (knotes), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f034aed5a00 (LWP 4383))] Thread 8 (Thread 0x7f0318d01700 (LWP 4391)): #0 0x7f034766de8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f033fc0d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f033fc0d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f03481bd23b in QEventDispatcherGlib::processEvents (this=0x7f0318c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0348167cea in QEventLoop::exec (this=this@entry=0x7f0318d00bc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f0347f8cfb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f0347f91b98 in QThreadPrivate::start (arg=0xbd9a50) at thread/qthread_unix.cpp:344 #7 0x7f03416c26fa in start_thread (arg=0x7f0318d01700) at pthread_create.c:333 #8 0x7f0347679b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f0319502700 (LWP 4390)): #0 0x7f033fc51ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f033fc0d382 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f033fc0d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f03481bd23b in QEventDispatcherGlib::processEvents (this=0x7f030c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0348167cea in QEventLoop::exec (this=this@entry=0x7f0319501bc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f0347f8cfb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f0347f91b98 in QThreadPrivate::start (arg=0xbe4b70) at thread/qthread_unix.cpp:344 #7 0x7f03416c26fa in start_thread (arg=0x7f0319502700) at pthread_create.c:333 #8 0x7f0347679b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f031a71a700 (LWP 4389)): #0 0x7f034766de8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f033fc0d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f033fc0d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f03481bd23b in QEventDispatcherGlib::processEvents (this=0x7f03140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0348167cea in QEventLoop::exec (this=this@entry=0x7f031a719b90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f0347f8cfb4 in QThread::exec (this=this@entry=0x7f034ce6cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7f034cdf87a5 in QDBusConnectionManager::run (this=0x7f034ce6cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #7 0x7f0347f91b98 in QThreadPrivate::start (arg=0x7f034ce6cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #8 0x7f03416c26fa in start_thread (arg=0x7f031a71a700) at pthread_create.c:333 #9 0x7f0347679b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f031b687700 (LWP 4388)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0320db1aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f0320db1907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f03416c26fa in start_thread (arg=0x7f031b687700) at pthread_create.c:333 #4 0x7f0347679b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f031be88700 (LWP 4387)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0320db1aa3 in ?? () from /usr/lib/
[plasmashell] [Bug 368717] The button for switching language layout is unavailable in Screen Locker.
https://bugs.kde.org/show_bug.cgi?id=368717 --- Comment #5 from Menak Vishap --- And placing button to the screen corner instead of input field vicinity is bad idea as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368717] The button for switching language layout is unavailable in Screen Locker.
https://bugs.kde.org/show_bug.cgi?id=368717 --- Comment #4 from Menak Vishap --- I mean the button itself with its background must be visible permanently, not the letters only. I use Plasma theme Oxygen with desktop theme ThinAir2 modified for use with Plasma 5. But with standard Air and Breeze desktop themes the situation is the same with only difference that letters are white. The white letters are little bit better visible on dark wallpaper, but anyway it is very difficult to note two or three so small letters in the screen corner on the 1920x1080 monitor. And some people use wallpaper with light colors. So, using just a letters instead of completely visible button is a quite bad idea. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368214] FEATURE REQUEST: Notification custom size, look and location
https://bugs.kde.org/show_bug.cgi?id=368214 --- Comment #1 from David Edmundson --- This is very vague without any justification for any of these. We can't just add config options for every possible thing, it will balloon out of control. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368214] FEATURE REQUEST: Notification custom size, look and location
https://bugs.kde.org/show_bug.cgi?id=368214 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #9 from earl_c...@yahoo.com --- Comment on attachment 100145 --> https://bugs.kde.org/attachment.cgi?id=100145 Self contained test case . -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368775] New: Remove automatically silent part of video.
https://bugs.kde.org/show_bug.cgi?id=368775 Bug ID: 368775 Summary: Remove automatically silent part of video. Product: kdenlive Version: 16.04.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: renaud.guezen...@gmail.com I play role playing games through Rolisteam and I record my games. Videos are 3 hours-long and there are many silences. So, I'm looking for a way to remove all silent part of the video. I generated a file with all sequences I would like to remove. I can use that log file to feed a script or tool to do the job or a better way if any tool can detect silent moment and remove them. To make the video shorter, it will be great! Reproducible: Always Steps to Reproduce: 1.Not really a bug, more a feature request. 2. 3. Actual Results: I have tools to do it manually but I have many videos, I really need a way to script it. Expected Results: Menu > misc > Remove silence parts ! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361716] Duplicate suggestions in include file completion
https://bugs.kde.org/show_bug.cgi?id=361716 --- Comment #6 from Alexander Potashev --- Proposed fix: https://phabricator.kde.org/D2765 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368717] The button for switching language layout is unavailable in Screen Locker.
https://bugs.kde.org/show_bug.cgi?id=368717 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from David Edmundson --- It is visible pernamentaly. What Plasma theme are you using? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368774] New: org.kde.plasma.taskmanager - missing keyboard accelerators
https://bugs.kde.org/show_bug.cgi?id=368774 Bug ID: 368774 Summary: org.kde.plasma.taskmanager - missing keyboard accelerators Product: plasmashell Version: 5.7.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: i...@tyro.homenet.org CC: plasma-b...@kde.org The keyboard accelerators in the right-click context menu are missing with the new task manager. The only possible way to move a window to another desktop from the task manager is to select the desired desktop from the menu with the mouse and to click on it. Reproducible: Always Steps to Reproduce: 1. Right-click on an item in the task manger. 2. Press D. 3. Press 1 or 2 or 3 or 4 or 5 etc. Actual Results: The window remains on the same desktop. Expected Results: The window should be moved to desktop 1 or 2 etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368773] New: Application Dashboard doesn't respond properly to touch events
https://bugs.kde.org/show_bug.cgi?id=368773 Bug ID: 368773 Summary: Application Dashboard doesn't respond properly to touch events Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: aleix...@kde.org CC: plasma-b...@kde.org Looks like it should work, but tapping doesn't launch applications. Interestingly, the sections on the right work properly. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 Aleix Pol changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368756] Plasmashell adds obsolete widgets
https://bugs.kde.org/show_bug.cgi?id=368756 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- are you quitting plasma in between 3 to 6? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 366899] Ark fails to open certain .tar file
https://bugs.kde.org/show_bug.cgi?id=366899 d...@kaosx.us changed: What|Removed |Added CC||d...@kaosx.us --- Comment #2 from d...@kaosx.us --- As discussed on IRC, this seems to be an issue with new shared-mime-info 1.7 This commit introduces an official IANA registered type: https://cgit.freedesktop.org/xdg/shared-mime-info/commit/?id=2002c05bb1e85e6e3f0be1427d727e896ebbaf10 Using shared-mime-info 1.7 on a rar file returns correct value: $ xdg-mime query filetype example.rar application/vnd.rar A rebuild of Ark with these 2 sed lines makes it so Ark open .rar. files correctly again: sed -i 's|application/x-rar|application/vnd.rar|' plugins/clirarplugin/CMakeLists.txt sed -i 's|application/x-rar|application/vnd.rar|' plugins/clirarplugin/kerfuffle_clirar.json.cmake (not intended as a patch, since this will break rar files for systems with older then 1.7, just mentioning these sed lines to inform they fix this issue for shared-mime-info 1.7 only) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] New: Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 Bug ID: 368772 Summary: Can't access the plasmoids' context menu Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aleix...@kde.org CC: bhus...@gmail.com, plasma-b...@kde.org Each plasmoid has a menu often with some specific actions and some generic ones (e.g. Alternatives). This menu can't be accessed from a touch screen. I'd expect this one to be available with a long tap. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 368761] Plasma crashes when opening search dialog
https://bugs.kde.org/show_bug.cgi?id=368761 David Edmundson changed: What|Removed |Added Version|5.5.5 |unspecified Target Milestone|1.0 |--- Component|general |general Product|plasmashell |frameworks-baloo Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368771] Sections don't change on touch event
https://bugs.kde.org/show_bug.cgi?id=368771 David Edmundson changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- well yeah - you can't hover a finger. That'd be weird. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368771] New: Sections don't change on touch event
https://bugs.kde.org/show_bug.cgi?id=368771 Bug ID: 368771 Summary: Sections don't change on touch event Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: aleix...@kde.org CC: plasma-b...@kde.org On a touch screen, one needs to tap on a section to have it changed. In contrast, with the mouse hovering is enough. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] New: Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 Bug ID: 368770 Summary: Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO Product: kate Version: 16.04.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mj...@mit.edu packages from kubuntu 16.04.1 with backports Kate version 15.12.3 KDE Frameworks 5.23.0 Qt 5.5.1 (built against 5.5.1) Since upgrading KDE to KDE5 from kubuntu/backports a major showstopper was introduced. The File open/save dialogs are no longer the KDE dialogs but the ultra-simplistic standard QtFileDialog. This means: * no KIO/remote files * no copy&paste or typing of a URL * no "places" * I was so far completely unable to debug the issue as I am not on top of all the Qt5/KDE framworks-plugin mechanism. But I am very willing to help track this down if I can get some help! Kwrite shows the same behaviour, while (strangely) Gwenview opens the proper KDE dialog. Please let me know how I can help! Reproducible: Always Steps to Reproduce: 1. open kate 2. click file-> open 3. Actual Results: Shows simplistic Qt File Dialog Expected Results: Shows KDE File Dialog with all bells and whistles Also happens with a newly created user account (so no stale KDE config files from before the move to KDE5) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open
https://bugs.kde.org/show_bug.cgi?id=368568 RJVB changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from RJVB --- A crash deep in Qt can occur because of something done wrong in the dependent code; are you sure that's not the case here? Can you reproduce the issue? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368769] New: kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=368769 Bug ID: 368769 Summary: kontact crashes on exit 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: mathias.hom...@opensuse.org Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Quitting kontact with ctrl-q or via the menu A lot of times kontact crashes when I quit the app. I can't think of anything else special that I'm doing in such a case, other than quitting the app... The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f96d2d60800 (LWP 4991))] Thread 16 (Thread 0x7f95d17fa700 (LWP 5068)): #0 0x7f96c70b3d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c7071759 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071dcf in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95e0006d00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d17f9dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1576390) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f95d27fc700 (LWP 5066)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95cc004c20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d27fbdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1679d50) at thread/qthread_unix.cpp:344 #7 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f95d2ffd700 (LWP 5065)): #0 0x7f96c70b3cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c70714b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x14548a0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d2ffcdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425330) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f95d37fe700 (LWP 5064)): #0 0x7f96cfa26ccd in read () at /lib64/libc.so.6 #1 0x7f96c70b2b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95d8004820, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d37fddd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #8 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425890) at thread/qthread_unix.cpp:344 #9 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f95d3fff700 (LWP 5063)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in g_main_con
[k3b] [Bug 347034] Error message said, "please submit a bug"
https://bugs.kde.org/show_bug.cgi?id=347034 --- Comment #4 from bk...@gnu.org --- $ (exec 2>&1;cnf cdrecord ; cnf mkisofs)|sed 's/^/> /' . > Program 'cdrecord' is present in package 'cdrkit-cdrtools-compat', which is > installed on your system. > > Absolute path to 'cdrecord' is '/usr/bin/cdrecord'. Please check your $PATH > variable to see whether it contains the mentioned path. > . > Program 'mkisofs' is present in package 'cdrkit-cdrtools-compat', which is > installed on your system. > > Absolute path to 'mkisofs' is '/usr/bin/mkisofs'. Please check your $PATH > variable to see whether it contains the mentioned path. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368768] Panel set to "Windows can cover" randomly disappears when window focus changes
https://bugs.kde.org/show_bug.cgi?id=368768 --- Comment #1 from nonof --- Created attachment 101075 --> https://bugs.kde.org/attachment.cgi?id=101075&action=edit A screen recording showing the repeated clicking on a window and the desktop with the random disappearance of the panel A a screen recording illustrating the behaviour -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368766] KMail crashes when moving mail in reference counting code
https://bugs.kde.org/show_bug.cgi?id=368766 --- Comment #2 from Stephan Diestelhorst --- Please see the duplicate for a very similar crash that does *not* use threaded view (but instead Current Activity, Flat). Still crashes in the same code. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361716] Duplicate suggestions in include file completion
https://bugs.kde.org/show_bug.cgi?id=361716 --- Comment #5 from Milian Wolff --- Heh, I should pay more attention to the surroundings of the actual bug ;-) Sadly, I cannot reproduce this locally. Any chance you could add some debug output and debug it locally to see why it adds two files for you? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368766] KMail crashes when moving mail in reference counting code
https://bugs.kde.org/show_bug.cgi?id=368766 --- Comment #1 from Stephan Diestelhorst --- *** Bug 368767 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368767] KMail crashes when moving messages.
https://bugs.kde.org/show_bug.cgi?id=368767 Stephan Diestelhorst changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Stephan Diestelhorst --- Could not add to other report in DrKonqi. *** This bug has been marked as a duplicate of bug 368766 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368768] New: Panel set to "Windows can cover" randomly disappears when window focus changes
https://bugs.kde.org/show_bug.cgi?id=368768 Bug ID: 368768 Summary: Panel set to "Windows can cover" randomly disappears when window focus changes Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: hugebignumerouslengthybutno...@mailinator.com When set to "windows can cover", the panel randomly disappears upon clicking on another window, as if the desktop itself is covering it. When hovering over the spot where the panel hides, it will reappear, but for it to stay visible, we need to click on it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368767] New: KMail crashes when moving messages.
https://bugs.kde.org/show_bug.cgi?id=368767 Bug ID: 368767 Summary: KMail crashes when moving messages. Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: stephan.diestelho...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: Moving a message to another folder in unthreaded view. KMail crashes with the same backtrace as bug 368766, but I cannot attache in the Crash Reporter :-S The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5638090a00 (LWP 4381))] Thread 40 (Thread 0x7f54c48dd700 (LWP 4954)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5653d6f7af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f5653d6fdc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f5653d6ff80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5653d6c947 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f565d32f6fa in start_thread (arg=0x7f54c48dd700) at pthread_create.c:333 #6 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f55901b3700 (LWP 4912)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5653d6f7af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f5653d6fdc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f5653d6ff80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5653d6c947 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f565d32f6fa in start_thread (arg=0x7f55901b3700) at pthread_create.c:333 #6 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7f54ca467700 (LWP 4910)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5658b86863 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f5658ea7051 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f565d32f6fa in start_thread (arg=0x7f54ca467700) at pthread_create.c:333 #4 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7f54cac68700 (LWP 4909)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5658b86863 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f5658ea7051 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f565d32f6fa in start_thread (arg=0x7f54cac68700) at pthread_create.c:333 #4 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7f54cb469700 (LWP 4908)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5658b86863 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f5658ea7051 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f565d32f6fa in start_thread (arg=0x7f54cb469700) at pthread_create.c:333 #4 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7f54cbc6a700 (LWP 4907)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5658b85834 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f5658ea7051 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f565d32f6fa in start_thread (arg=0x7f54cbc6a700) at pthread_create.c:333 #4 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7f550c56f700 (LWP 4906)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5658e7742b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f5658e77469 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f565d32f6fa in start_thread (arg=0x7f550c56f700) at pthread_create.c:333 #4 0x7f56668d0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7f558d69f700 (LWP 4905)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x
kde-bugs-dist@kde.org
https://bugs.kde.org/show_bug.cgi?id=368663 --- Comment #6 from Dr. Chapatin --- Outra coisa que reparei agora é que "minutos" ficou abreviado como "mins". No nosso idioma a abreviatura correta não tem "s". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368766] New: KMail crashes when moving mail in reference counting code
https://bugs.kde.org/show_bug.cgi?id=368766 Bug ID: 368766 Summary: KMail crashes when moving mail in reference counting code Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: stephan.diestelho...@gmail.com Version 5.3.0 (QtWebEngine) Using: KDE Frameworks 5.25.0 Qt 5.7.0 (built against 5.7.0) The xcb windowing system -- Project Neon User -- I am using threaded view, but was moving a non-threaded message to a different folder. This smells like a race condition to me, maybe someone is free-ing memory while the reference counter is non-zero, and someone still has a reference to it and tries to set that to zero? -- Related: bug 368496 and bug 364994. Thread 1 "kmail" received signal SIGSEGV, Segmentation fault. 0x72160efc in ?? () from /usr/lib/x86_64-linux-gnu/libKF5MimeTreeParser.so.5 (gdb) bt #0 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/5/bits/atomic_base.h:396 #1 QAtomicOps::load (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:103 #2 QBasicAtomicInteger::load (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:99 #3 QtPrivate::RefCount::ref (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55 #4 QVector >::QVector (v=..., this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:363 #5 QForeachContainer > const>::QForeachContainer (t=..., this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:944 #6 MimeTreeParser::toplevelTextNode (messageTree=...) at /workspace/build/mimetreeparser/src/bodyformatter/utils.cpp:55 #7 0x7216127a in MimeTreeParser::toplevelTextNode (messageTree=...) at /workspace/build/mimetreeparser/src/bodyformatter/utils.cpp:64 #8 0x72175d04 in MimeTreeParser::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fffcd80, node=node@entry=0x2b63550) at /workspace/build/mimetreeparser/src/viewer/objecttreeparser.cpp:185 #9 0x72ab4d27 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0xae7670, content=0x2b63550) at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:969 #10 0x72ab531d in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0xae7670) at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:842 #11 0x72ab5d8a in MessageViewer::ViewerPrivate::updateReaderWin (this=0xae7670) at /workspace/build/messageviewer/src/viewer/viewer_p.cpp:2133 #12 0x75ea9f36 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x75eb64e8 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x75eaaa93 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7676a89c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x76772296 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x75e7eda8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x75ed123e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x75ed1771 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fffea2b71a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fffea2b7400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fffea2b74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x75ed22ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x75e7cd9a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x75e853ac in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00403984 in ?? () #27 0x752b7830 in __libc_start_main (main=0x4028d0, argc=1, argv=0x7fffded8, init=, fini=, rtld_fini=, stack_end=0x7fffdec8) at ../csu/libc-start.c:291 #28 0x00404079 in _start () (gdb) q Reproducible: Sometimes Steps to Reproduce: 1. (Not sure: enable threaded view) 2. Move a few messages to other folders Actual Results: KMail crashes with the backtrace above. Expected Results: KMail just move
[kdevelop] [Bug 368695] Crash when using QuickOpen
https://bugs.kde.org/show_bug.cgi?id=368695 Milian Wolff changed: What|Removed |Added Latest Commit||http://commits.kde.org/kdev ||platform/5da01380d6223d2e63 ||00cba1da29e6f031055107 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Milian Wolff --- Git commit 5da01380d6223d2e6300cba1da29e6f031055107 by Milian Wolff. Committed on 13/09/2016 at 21:12. Pushed by mwolff into branch '5.0'. Don't ever return empty icon names, return "none" instead as fallback. M +3-0project/projectmodel.cpp http://commits.kde.org/kdevplatform/5da01380d6223d2e6300cba1da29e6f031055107 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360184] k3b should offer option to select either md5 sum or sha256 when loading dvd iso
https://bugs.kde.org/show_bug.cgi?id=360184 --- Comment #4 from Phil --- Dear KDE "K3b" developers and maintainers, Leslie Zhai, Sebastian Trueg, Thomas Schmitt, 1. To all of you, Thank you for working on this great K3b application, and making it even better. 2. It looks like you are using "QT" development for some if not all of this? I do not yet know enough about "QT" to help with that. Although, the link from Thomas regarding the use of "QCryptographicHash::Sha256" (and its variations) look pretty good too me. I don't know if this will help or not, but when I use Linux Mint for evaluating checksum values, I can use the commands below. As far as I know, all Linux distros (and maybe MS Windows too) have the command "sha256sum" already installed. To get the checksum value: Example: sha256sum -b linuxmint-18-kde-32bit.iso Results in: ff8bacc631e7955fc6b0f86c9014ce27aa455e3ee0913de0b2bc6c366b63c693 *linuxmint-18-kde-32bit.iso To verify a checksum of a file with its downloaded checksum file (sha256sum.txt) in the same folder, I can use either of these console terminal commands: Example: sha256sum --check sha256sum.txt or sha256sum --check --ignore-missing sha256sum.txt Results in: linuxmint-18-cinnamon-32bit.iso: OK linuxmint-18-kde-32bit.iso: OK linuxmint-18-mate-32bit.iso: OK linuxmint-18-xfce-32bit.iso: OK 3.) I tried to compile "K3b" from the link below using the "install.txt" instructions, and could not successfully compile it on my Linux Mint KDE 32-bit system. Unfortunately, I only have an ancient 32- bit computer (11+ years old Pentium 4 computer (single core)) which cannot install any version of QT higher than "Qt v5.5" and 32-bit. So, I still need alternate compiling instructions (easy detailed ones please), or I would prefer easy to install ".deb" files, or a PPA. https://github.com/KDE/k3b Best regards to all of you and yours, Phil -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.
https://bugs.kde.org/show_bug.cgi?id=368689 Sven Brauch changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@svenbrauch.de Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Sven Brauch --- I can confirm the issue is still there, I also see it sometimes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open
https://bugs.kde.org/show_bug.cgi?id=368568 Milian Wolff changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Milian Wolff --- crashes deep inside Qt, please report upstream -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.
https://bugs.kde.org/show_bug.cgi?id=368689 --- Comment #2 from Milian Wolff --- can you please give us an example project (i.e. something we can test ourselves) and tell us which file you are editing, how, and where, to reproduce the issue? this is a really important thing to get fixed, but so far we did not find a reliable way to trigger the issue, thus making the bug fixing pretty much impossible at this point -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368496] KMail crashes in memcpy
https://bugs.kde.org/show_bug.cgi?id=368496 --- Comment #2 from Stephan Diestelhorst --- Yep, I am using those, quite extensively. Will retry that in GDB to see what is happening. Also got another one, this time very different backtrace from either. -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 368751] KCachegrind crashes after a profile gets loaded
https://bugs.kde.org/show_bug.cgi?id=368751 --- Comment #4 from Josef Weidendorfer --- Hmm... probably not out-of-memory then. Any chance for me to reproduce the bug, ie. can you make the file available to me (e.g. via sending me a link in private email)? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368460] function signature picks up template parameter names
https://bugs.kde.org/show_bug.cgi?id=368460 --- Comment #4 from Milian Wolff --- I think https://reviews.llvm.org/D13599 can help to get this fixed. In the meantime, ideas on how to improve that situation are welcome :) -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 368765] New: Toggle of suspending by a hot key
https://bugs.kde.org/show_bug.cgi?id=368765 Bug ID: 368765 Summary: Toggle of suspending by a hot key Product: rsibreak Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: aa...@kde.org Reporter: victor.zemt...@gmail.com Please add a possibility for toggle of suspending RSIBreak by a hot key. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368764] Crash when opening a .kra file in krita
https://bugs.kde.org/show_bug.cgi?id=368764 --- Comment #1 from Pierre --- Created attachment 101074 --> https://bugs.kde.org/attachment.cgi?id=101074&action=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368764] New: Crash when opening a .kra file in krita
https://bugs.kde.org/show_bug.cgi?id=368764 Bug ID: 368764 Summary: Crash when opening a .kra file in krita Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bloodyw...@tastyespresso.de I was able to reproduce this multiple times now: Starting Krita Open a .kra file made with Krita Version from yesterday SIGSEGV in __dynamic_cast() Reproducible: Always Steps to Reproduce: See desciption Actual Results: Makes krita crash Expected Results: Should open the .kra file -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 368763] Crash after closing Ark during a MoveJob
https://bugs.kde.org/show_bug.cgi?id=368763 --- Comment #1 from Elvis Angelaccio --- Created attachment 101073 --> https://bugs.kde.org/attachment.cgi?id=101073&action=edit Stacktrace -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 368763] New: Crash after closing Ark during a MoveJob
https://bugs.kde.org/show_bug.cgi?id=368763 Bug ID: 368763 Summary: Crash after closing Ark during a MoveJob Product: ark Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: elvis.angelac...@kde.org CC: rak...@freebsd.org, rthoms...@gmail.com This happened while Ark was renaming a folder in a huge archive (Linux source tarball). Reproducible: Didn't try -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368717] The button for switching language layout is unavailable in Screen Locker.
https://bugs.kde.org/show_bug.cgi?id=368717 --- Comment #2 from Menak Vishap --- Oh, you are right!!! I had mistaken. It is really present. But it is almost invisible! It is hidden so carefully that no-one anemy for sure will never find it. :))) Very small black (at least with my desktop theme) letters on completely transparent background on dark wallpaper. It is really hard to find. So, the bug probably can be dismissed, but it is good reason for those who work on this code to think about making this button visible permanently, not only at the moment when the mouse cursor is placed over it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #8 from Philippe Waroquiers --- (In reply to earl_chew from comment #4) > Created attachment 100145 [details] > Self contained test case It seems there was an attachment problem. Could you re-attach the self contained test case ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #7 from Philippe Waroquiers --- (In reply to Julian Seward from comment #6) > Philippe, didn't you fix something like this recently? Not recently. Related to thread termination, I did something some years ago, to fix bug 324227. I can take a look at this bug and see if I find something. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368416] Add tc06_two_races_xml.exp output for ppc64.
https://bugs.kde.org/show_bug.cgi?id=368416 --- Comment #4 from Philippe Waroquiers --- (In reply to Will Schmidt from comment #3) > Created attachment 101061 [details] > updated and refactored patch > > Per feedback and commentary, this is a different approach to solving the > problem... > > Update and modify the filter_xml filter to strip out the troublesome frame. > And a tweak to the same to suppress the blurb that typically indicates a > frame has been skipped. > Appears to work OK across the systems I have access to. (a mix of ppc64 and > a couple x86 boxes). That looks good to me. Feel free to commit. Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368762] New: Only Jpg files are visible if importing them into a Subfolder of a Grouped folder
https://bugs.kde.org/show_bug.cgi?id=368762 Bug ID: 368762 Summary: Only Jpg files are visible if importing them into a Subfolder of a Grouped folder Product: digikam Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: AlbumsView-Group Assignee: digikam-de...@kde.org Reporter: flo.hen...@gmail.com I'm having some issues using Groups: I have some Raw and Jpg files in my "root" album called Pictures. The images there are grouped using "Select all" -> "Group by Type". When I import some Files (again Raw and corresponding Jpg) to a subfolder of Pictures, only The Jpg files are shown in the digikam thumbnails view. Expected result: Raw and Jpg files are visible in digikam, Grouping should be possible. Reproducible: Always Steps to Reproduce: 1. Group raw and jpg files in root album using "Group by type" from the context menu 2. Import raw and jpg files to a subfolder of the root album 3. Actual Results: Images are imported to filesystem but only the Jpg files are shown in digikam. Expected Results: Raw and Jpg files are visible in digikam, Grouping should be possible independently from the root folder. Normally my images are located on a NFS network share but for reproducing I used a Collection on my local harddisk. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 294579] GROUP : grouped pictures are not processed together except the first one (Renaming, Tags, Metadata, Labels, etc.)
https://bugs.kde.org/show_bug.cgi?id=294579 tuxflo changed: What|Removed |Added CC||flo.hen...@gmail.com --- Comment #9 from tuxflo --- Also still valid in version 5.1.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368761] New: Plasma crashes when opening search dialog
https://bugs.kde.org/show_bug.cgi?id=368761 Bug ID: 368761 Summary: Plasma crashes when opening search dialog Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: george...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: Plasma crashed after openning seach dialog. Rebooted, tried again, same result. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7feef63668c0 (LWP 4878))] Thread 24 (Thread 0x7fedeb7fe700 (LWP 5459)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7feef116caeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x529d790) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x5b5d5d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fee3dc592bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fee3dc5d4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fee3dc5d542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fee3dc5d542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fee3dc5d542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fee3dc5b353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7feef116b84e in QThreadPrivate::start (arg=0x7fee100035b0) at thread/qthread_unix.cpp:331 #14 0x7feef02586fa in start_thread (arg=0x7fedeb7fe700) at pthread_create.c:333 #15 0x7feef0a81b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 23 (Thread 0x7fede37fe700 (LWP 5458)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7feef116caeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x529d790) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x5b5d5d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fee3dc592bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fee3dc5d4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fee3dc5d542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fee3dc5846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fee3dc5b353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7feef116b84e in QThreadPrivate::start (arg=0x7fedf4003190) at thread/qthread_unix.cpp:331 #10 0x7feef02586fa in start_thread (arg=0x7fede37fe700) at pthread_create.c:333 #11 0x7feef0a81b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 22 (Thread 0x7fedebfff700 (LWP 5457)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7feef116caeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x529d790) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x5b5d5d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fee3dc592bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7fee3dc5d4e8 in ?? () from /usr/lib/x86_64
[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64 and amd64 (membarrier)
https://bugs.kde.org/show_bug.cgi?id=361726 --- Comment #6 from Mark Wielaard --- BTW. This is an awesome overview of all the linux syscalls by architectures: https://fedora.juszkiewicz.com.pl/syscalls.html -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64 and amd64 (membarrier)
https://bugs.kde.org/show_bug.cgi?id=361726 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Summary|WARNING:unhandled syscall |WARNING:unhandled syscall |on ppc64|on ppc64 and amd64 ||(membarrier) CC||m...@redhat.com Status|NEEDSINFO |CONFIRMED --- Comment #5 from Mark Wielaard --- The membarrier() system call was added in Linux 4.3. http://www.man7.org/linux/man-pages/man2/membarrier.2.html Which contains a small test program that also fails on amd64-linux. WARNING: unhandled amd64-linux syscall: 324 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368685] wishlist - systemsettings --> desktop behavior --> screen edges does not allow custom actions.
https://bugs.kde.org/show_bug.cgi?id=368685 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|general |core Resolution|--- |WORKSFORME --- Comment #1 from Martin Gräßlin --- There is already a solution to get the actual use case implemented. You can use a KWin script to bind a screen edge and from there perform a dbus call. This should be sufficient to start any application (e.g. through invoking klauncher). Adding a file picker as suggested in this request is nothing we want to add. This would be a too complicated UI and result in an expert control module. But such an expert modus already exists with the scripts and follows our simple by default (no complicated UI), powerful when needed (full control through scripts). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368737] PresentWindows should also activate with just a single window
https://bugs.kde.org/show_bug.cgi?id=368737 Martin Gräßlin changed: What|Removed |Added Severity|normal |wishlist Summary|[kde5] [User experience]|PresentWindows should also |Desktop corner trigger for |activate with just a single |showing all windows should |window |also darken screen with | |just a single window| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368760] New: Dolphin crashes when navigating to a folder
https://bugs.kde.org/show_bug.cgi?id=368760 Bug ID: 368760 Summary: Dolphin crashes when navigating to a folder Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: george...@gmail.com Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Just after reboot, openned up Dolphin, navigated to a specific folder, and crashed.No other applications running. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d4ea1a8c0 (LWP 6150))] Thread 3 (Thread 0x7f2d42118700 (LWP 6152)): #0 0x7f2d61837e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2d5802c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2d5802c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2d5c640a9b in QEventDispatcherGlib::processEvents (this=0x7f2d3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f2d5c5e7dea in QEventLoop::exec (this=this@entry=0x7f2d42117d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f2d5c4048a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f2d5c40984e in QThreadPrivate::start (arg=0x1b7fbd0) at thread/qthread_unix.cpp:331 #7 0x7f2d58bb76fa in start_thread (arg=0x7f2d42118700) at pthread_create.c:333 #8 0x7f2d61843b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f2d4c09f700 (LWP 6151)): #0 0x7f2d61837e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2d55fc3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2d55fc58d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2d4e3f1629 in QXcbEventReader::run (this=0x16c0da0) at qxcbconnection.cpp:1253 #4 0x7f2d5c40984e in QThreadPrivate::start (arg=0x16c0da0) at thread/qthread_unix.cpp:331 #5 0x7f2d58bb76fa in start_thread (arg=0x7f2d4c09f700) at pthread_create.c:333 #6 0x7f2d61843b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f2d4ea1a8c0 (LWP 6150)): [KCrash Handler] #6 0x7f2d61772418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f2d6177401a in __GI_abort () at abort.c:89 #8 0x7f2d54f15002 in mdb_assert_fail (env=0x1cf0670, expr_txt=expr_txt@entry=0x7f2d54f16adb "i > 0", func=func@entry=0x7f2d54f17380 <__func__.7798> "mdb_page_search_root", line=line@entry=5291, file=0x7f2d54f16a40 "mdb.c") at mdb.c:1481 #9 0x7f2d54f0bf47 in mdb_page_search_root (mc=mc@entry=0x7ffd90c81480, key=key@entry=0x7ffd90c81840, flags=flags@entry=0) at mdb.c:5291 #10 0x7f2d54f0c0c8 in mdb_page_search (mc=mc@entry=0x7ffd90c81480, key=key@entry=0x7ffd90c81840, flags=flags@entry=0) at mdb.c:5436 #11 0x7f2d54f0c7a5 in mdb_cursor_set (mc=mc@entry=0x7ffd90c81480, key=key@entry=0x7ffd90c81840, data=data@entry=0x7ffd90c81850, op=op@entry=MDB_SET, exactp=exactp@entry=0x7ffd90c8147c) at mdb.c:5893 #12 0x7f2d54f0ce3c in mdb_get (txn=, dbi=, key=key@entry=0x7ffd90c81840, data=data@entry=0x7ffd90c81850) at mdb.c:5565 #13 0x7f2d5941e718 in Baloo::DocumentDataDB::get (this=this@entry=0x7ffd90c81880, docId=docId@entry=193655226358562862) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/documentdatadb.cpp:83 #14 0x7f2d59430cde in Baloo::Transaction::documentData (this=this@entry=0x7ffd90c81910, id=id@entry=193655226358562862) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:144 #15 0x7f2d5f68cf69 in Baloo::File::load (this=this@entry=0x7ffd90c81a60) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/file.cpp:111 #16 0x7f2d5fc22796 in Baloo::FileFetchJob::doStart (this=0x1e0b900) at /build/baloo-widgets-A4yGxj/baloo-widgets-15.12.3/src/filefetchjob.cpp:58 #17 0x7f2d5c619ea1 in QObject::event (this=0x1e0b900, e=) at kernel/qobject.cpp:1239 #18 0x7f2d5d0ed05c in QApplicationPrivate::notify_helper (this=this@entry=0x16a93e0, receiver=receiver@entry=0x1e0b900, e=e@entry=0x1e0e310) at kernel/qapplication.cpp:3716 #19 0x7f2d5d0f2516 in QApplication::notify (this=0x7ffd90c82170, receiver=0x1e0b900, e=0x1e0e310) at kernel/qapplication.cpp:3499 #20 0x7f2d5c5ea62b in QCoreApplication::notifyInternal (this=0x7ffd90c82170, receiver=0x1e0b900, event=event@entry=0x1e0e310) at kernel/qcoreapplication.cpp:965 #21 0x7f2d5c5eca26 in QCoreApplication::sendEvent (event=0x1e0e310, receiver=) at ../../includ
[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200
https://bugs.kde.org/show_bug.cgi?id=358620 Mark Wielaard changed: What|Removed |Added Summary|ARM: unhandled syscall: 357 |ARM: disInstr(arm): ||unhandled instruction: ||0xF1010200 CC||m...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 368759] New: lack of translation fo Polish commend ustalKierunek
https://bugs.kde.org/show_bug.cgi?id=368759 Bug ID: 368759 Summary: lack of translation fo Polish commend ustalKierunek Product: kturtle Version: 0.8.1 beta Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: c...@kde.nl Reporter: rafal.michal...@interia.pl Lack of translation fo Polish commend ustalKierunek. Function ustalKierunek in undefinied. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 368412] False positive result for altivec capability check
https://bugs.kde.org/show_bug.cgi?id=368412 --- Comment #6 from Mark Wielaard --- Thanks, pushed as valgrind svn r15952 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368758] New: Printing with grayscale option do not work
https://bugs.kde.org/show_bug.cgi?id=368758 Bug ID: 368758 Summary: Printing with grayscale option do not work Product: okular Version: 0.25.80 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: gzmor...@gmail.com Trying to print a color pdf document in grayscale produces a color printing. This happens when printing to a color printer and also printing to a file. Printing a png file in grayscale works as expected. Reproducible: Always Steps to Reproduce: 1. Open a pdf color file 2. Select "File -> Print -> Options -> Options -> (Color Mode) Grayscale" 3. Press "Print" Actual Results: The document is printed in color Expected Results: The document should be printed in grayscale Tested in Archlinux with version 0.26.0 Frameworks 5.25.0 Plasma 5.7.5 PDF Backend 0.6.5 KDE Development Platform 4.14.24 kdelibs 4.14.24 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366541] git master:2016-08-09: Speed effect should be a clip job
https://bugs.kde.org/show_bug.cgi?id=366541 Evert Vorster changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Evert Vorster --- Thanks for implementing this idea. Already a whole bunch of my open tickets have been closed due to this change. Thank you very much! Being able to type in the actual number that is outside the range of the slider is awesome, and works as advertised. It is not obvious that the range that can be typed in is allowed to be larger than what the slider goes to. Maybe a tooltip would help? Apart from this, I am quite happy with the implementation. -Evert- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 368757] New: quanta+ hangs at startup with 100% CPU-usage
https://bugs.kde.org/show_bug.cgi?id=368757 Bug ID: 368757 Summary: quanta+ hangs at startup with 100% CPU-usage Product: kde Version: 4.14.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m...@wolf-itc.de quanta+ worked fine until my Fedora 21. Now I upgraded to Fedora 24 ... and now quanta+ is not starting anymore. Only the splash-screen is visible and it hangs with 25% CPU-Usage (I've got a Core-i5-2500 with 4 kernels). Because I updated the system from Fedora 21, I too another, fresh harddisk and installed a complete new Fedora 24: Same here. (btw: Where is the component kdewebdev/quanta here in this bugtracker?) Best regards Martin Reproducible: Always Steps to Reproduce: 1. Start quanta+ 2. 3. Actual Results: It hangs/freezes at startup Expected Results: Should start ;-) $ kde-open --version: Qt: 4.8.7 KDE: 4.14.22 KIO-Client: 2.0 $ quanta kbuildsycoca running... DCOP Cleaning up dead connections. Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:186 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:187 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:188 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:189 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:190 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:191 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:192 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:193 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:194 Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:224 -- You are receiving this mail because: You are watching all bug changes.
