[krita] [Bug 399639] my brush stroke lags about an inch behind where it is supposed to write. it doesnt write within the circle but when i drag it an inch outside the circle it begins writing.
https://bugs.kde.org/show_bug.cgi?id=399639 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Emmet O'Neill --- Hello Karan, Is it possible that you have turned the Brush Stabilizer option on? What you're describing sounds like that feature and may not be a bug at all. To check, select the Brush Tool (B), look in the Tool Options Docker (if you can't find it, activate it in the menu bar under Settings > Dockers > Tool Options Docker), and please make sure the "Brush Smoothing" option is not set to "Stabilizer". -- You are receiving this mail because: You are watching all bug changes.
[kvkbd] [Bug 399640] New: [feature request] better customizable on-screen keyboard
https://bugs.kde.org/show_bug.cgi?id=399640 Bug ID: 399640 Summary: [feature request] better customizable on-screen keyboard Product: kvkbd Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: smar...@ubuntu.com Reporter: f4tm...@web.de Target Milestone: --- Touchscreen devices are becoming more popular and thus also the application possibilities. For instance I need to set up a kiosk system only with number input. It would be handy to have an on-screen keyboard that allows to change the layout easily. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399637] libksysguard fails to build without QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=399637 --- Comment #1 from Rik Mills --- For the record, seeing the same failure on Neon and Kubuntu CI builds of master branch. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393112] Autosave files don't get made for new documents derived from templates
https://bugs.kde.org/show_bug.cgi?id=393112 --- Comment #8 from Wysteria --- This bug still exists for me on the 4.2.0-pre-alpha (git 715ad13) appimage I downloaded yesterday. (In reply to Boudewijn Rempt from comment #4) > If the name in the titlebar includes "[Write Protected]" then that means the > location cannot be written to; that's not something we can fix. Could you > check whether that's the case? I figured out that templates are stored in directories like /tmp/.mount_krita-hWinAD/usr/share/krita/templates, everything contained in .mount_krita-hWinAD/ is owned by root, so krita can't autosave there. drwxrwxr-x 3 root root 0 Oct 10 00:19 .mount_krita-hWinAD I tried to chown it but it didn't work, am I using chown incorrectly? $ sudo chown -R wyst /tmp/.mount_krita-hWinAD/ chown: cannot access '/tmp/.mount_krita-hWinAD': Permission denied Seems to be an issue with my machine, no idea how to fix it though. I think Krita should warn the user that it can't do an autosave in situations like this, similar to how it warns the user that it is post-poning autosave when the document is busy (can happen when a CPU intensive filter is still processing). The "[Write Protected]" warning only appears in the window title (not visible in fullscreen) and in the tab title (not visible in sub-window mode). It ought to appear in the status bar like the autosave post-pone waring does. Should I make a new wishlist ticket and close this ticket, or just edit this ticket? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399637] libksysguard fails to build without QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=399637 Rik Mills changed: What|Removed |Added CC||rikmi...@kubuntu.org -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399637] libksysguard fails to build without QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=399637 Rik Mills changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 --- Comment #5 from Alexei Podtelezhnikov --- Thomas Dickey pointed me to this: https://github.com/mattiase/wraptest/blob/master/results.txt It is just funny how inconsistent the BS handling is, no pun intended -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397589] Crash while first starting Kmail
https://bugs.kde.org/show_bug.cgi?id=397589 --- Comment #6 from Martin Tlustos --- In case the reporter does not supply more info, should I try to run kmail in gdb? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399639] my brush stroke lags about an inch behind where it is supposed to write. it doesnt write within the circle but when i drag it an inch outside the circle it begins writing.
https://bugs.kde.org/show_bug.cgi?id=399639 --- Comment #1 from Karan Singh --- There is a center pixel where my brush stroke is supposed to start HOWEVER, when i try to start my brush stroke there it lags an inch behind every single time. I cannot unlclick Open GL as well. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354077] Git Master 2015-10-17 - HEVC profile does not pass the quality setting to the renderer.
https://bugs.kde.org/show_bug.cgi?id=354077 Evert Vorster changed: What|Removed |Added Status|VERIFIED|RESOLVED Resolution|REMIND |FIXED --- Comment #7 from Evert Vorster --- This has been working properly for quite a while now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399639] New: my brush stroke lags about an inch behind where it is supposed to write. it doesnt write within the circle but when i drag it an inch outside the circle it begins writing.
https://bugs.kde.org/show_bug.cgi?id=399639 Bug ID: 399639 Summary: my brush stroke lags about an inch behind where it is supposed to write. it doesnt write within the circle but when i drag it an inch outside the circle it begins writing. Product: krita Version: 4.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: artistkara...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399638] New: Noticeable lag when drawing
https://bugs.kde.org/show_bug.cgi?id=399638 Bug ID: 399638 Summary: Noticeable lag when drawing Product: krita Version: 4.1.3 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: wontoon...@gmail.com Target Milestone: --- SUMMARY After the October 2018 update on Windows 10, when drawing with a Cintiq Pro 16 tablet (this may extend to all Wacom tablets; unsure) there is a noticeable delay (around 1 ~ 1.5 seconds) between when the the pen is on the canvas and the stroke appears on the canvas. This appears in both Krita 4.1.1 and 4.1.3, and both tablet input APIs. This seems to be somewhat sporadic, but it definitely happens very, very often. On the Surface 4 Pro, this problem does not exist (I have tested 4.0, got the Cintiq Pro shortly after-- and 4.1.3. I expected 4.1.3 to have the same issue but it is not there, making me conclude that this is possibly isolated to Wacom tablets). STEPS TO REPRODUCE 1. Run Krita after the October 2018 update for Windows 10. 2. Make a line. It may take a few lines. 3. (Optional) Curse at Microsoft at the top of your lungs. OBSERVED RESULT Lag in strokes appearing on screen. EXPECTED RESULT Smooth drawing. SOFTWARE VERSIONS (available in About System) 4.1.1, 4.1.3 KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: 5.9.3 ADDITIONAL INFORMATION OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 364680] feature request: restore previous session
https://bugs.kde.org/show_bug.cgi?id=364680 ganesh09...@gmail.com changed: What|Removed |Added CC||ganesh09...@gmail.com --- Comment #3 from ganesh09...@gmail.com --- Hi Okular developers, I have been using okular for past ~4 years. this is my preferred and default pdf reader in all my systems. I never had any issue but the only problem with okular is it doesn't restore the previous session. I have to open multiple pdf across multiple folders. It will be good if developers can provide the solution. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #6 from Diane Trout --- Went home opened laptop from suspend, then laptop screen appeared with 1x scale. Plugged in dock and it didnt detect it. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393120] Elisa crash on editing local music indexer settings
https://bugs.kde.org/show_bug.cgi?id=393120 Neousr changed: What|Removed |Added CC||neo...@protonmail.com --- Comment #4 from Neousr --- Created attachment 115554 --> https://bugs.kde.org/attachment.cgi?id=115554=edit Elisa backtrace 10-10-18 Having the same symptoms on Elisa 0.3.0 it crashes while editing music folders. KDE neon 5.14 KDE Plasma: 5.14.0 Qt: 5.11.1 KDE Frameworks: 5.50.0 This apply to adding, removing folders to the music library as well as using the default button on the indexer settings and pressing either apply or accept. Adding or removing multiple times folders seems to reduce the number of subsequent crashes. Bug 399211 is a posible duplicate. Adding a backtrace of it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 398766] Desktop crash while changing application launchers icon.
https://bugs.kde.org/show_bug.cgi?id=398766 Tony changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Tony --- I don't get the crash anymore after updating to the latest packages of KDE unstable repository and snapshot for Tumbleweed. The speed while loading the icons noticeably varies though depending on the theme used. Tested with different icon themes, breeze, breeze tumbleweed, elementary kde, oxygen, MacOSX one, El general and Infinity clear. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397827] Invoking the Media Player/Controller widget for the first time causes the song to restart
https://bugs.kde.org/show_bug.cgi?id=397827 Neousr changed: What|Removed |Added CC||neo...@protonmail.com --- Comment #9 from Neousr --- I'm not longer able to reproduce on Neon 5.14 User Edition and Neon 5.14.80 Developer Unstable using Elisa 0.3.0 and 0.3.80 respectively. -- You are receiving this mail because: You are watching all bug changes.
[lskat] [Bug 105124] advanced mode algorithm 'cheats'
https://bugs.kde.org/show_bug.cgi?id=105124 --- Comment #2 from Christoph Feck --- We need to find someone who knows the rules of Leutnant Skat and Qt/C++ to check the code if the AI player is indeed cheating. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399637] New: libksysguard fails to build without QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=399637 Bug ID: 399637 Summary: libksysguard fails to build without QtWebEngine Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libksysguard Assignee: plasma-de...@kde.org Reporter: cf...@kde.org Target Milestone: --- STEPS TO REPRODUCE compile libksysguard without installed QtWebEngine devel headers OBSERVED RESULT processui/scripting.cpp:58:27: error: 'QWebEngineUrlRequestInfo' has not been declared Full log: https://build.opensuse.org/package/live_build_log/home:cfeck:branches:KDE:Unstable:Frameworks/libksysguard5/openSUSE_Factory/x86_64 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 399637] libksysguard fails to build without QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=399637 Christoph Feck changed: What|Removed |Added CC||fab...@ritter-vogt.de -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 293230] Legend entries can no longer be set manually
https://bugs.kde.org/show_bug.cgi?id=293230 netterfi...@astro.utoronto.ca changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kst ||-plot/eeddc65e4fac824a66825 ||349b49c66c11429e267 Status|CONFIRMED |RESOLVED --- Comment #3 from netterfi...@astro.utoronto.ca --- Git commit eeddc65e4fac824a66825349b49c66c11429e267 by Barth Netterfield. Committed on 05/10/2018 at 15:28. Pushed by netterfield into branch 'master'. Curve Dialog gets a manual Legend Name entry. This overrides all automatic naming. M +31 -2src/libkstapp/curvedialog.cpp M +6-0src/libkstapp/curvedialog.h M +60 -1src/libkstapp/curvetab.ui M +13 -4src/libkstapp/datadialog.cpp M +1-0src/libkstapp/datadialog.h M +22 -42 src/libkstapp/legenditem.cpp M +47 -1src/libkstmath/relation.cpp M +8-1src/libkstmath/relation.h https://commits.kde.org/kst-plot/eeddc65e4fac824a66825349b49c66c11429e267 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 --- Comment #4 from Alexei Podtelezhnikov --- If I use my keyboard to do the same I will get the 80th zero removed. 40% of modern emulators do the right thing. Old gnome terminal 2.9.3 was ok too. Good luck with that backward compatibility head in the sand. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 388196] akonadi_control crash after login
https://bugs.kde.org/show_bug.cgi?id=388196 --- Comment #4 from Christoph Feck --- Comment #1 is bug 392092. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 Martin Hostettler changed: What|Removed |Added CC||textshell-dIA3f6@uchuujin.d ||e --- Comment #3 from Martin Hostettler --- I think it's somewhat logical in the VTxxx model of cursor movement. In the VTxxx terminals the cursor does not move past the right most column ever, but instead has a "pending wrap" flag that takes effect only on the next printed character unless it's cleared in between. Then Backspace is only a alias for cursor left (CUB) which as all cursor movement commands clears the "pending wrap" flag before executing the movement. This results in the somewhat unintuitive result. I think it's just a fact of terminal programming that the right-most column is deeply special. Some applications use " \b" after text to force wrapping. But in general software needs to know the width of the terminal to correctly handle output when reaching the end of the line. It might be unfortunate that the VTxxx cursor model results in one column less that behaves like the others. But i think it's best to stick to the backwards compatible model. Especially for terminals that claim TERM=xterm where xterm usually tries to be historically accurate to what the original DEC VTxxx terminals do. I'm trying to document what terminal emulators currently do. See https://terminalguide.netlify.com/printing/ and https://terminalguide.netlify.com/seq/a_c0-h/ for my attempt at documenting this(still work in progress). (@egmont: Thank for retesting different terminal emulators, i had to fix the implementation specific notes on urxvt in my documentation) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397589] Crash while first starting Kmail
https://bugs.kde.org/show_bug.cgi?id=397589 --- Comment #5 from Christoph Feck --- >From the backtrace, could be. But the fatal() message could also be different, and without the Qt logging output, we cannot know. Comment #2 either does not show the complete output, or Qt logging was redirected elsewhere (xorg-session.log, systemd log, ...) -- You are receiving this mail because: You are watching all bug changes.
[lskat] [Bug 105124] advanced mode algorithm 'cheats'
https://bugs.kde.org/show_bug.cgi?id=105124 Lukas changed: What|Removed |Added Version|1.0 |1.40 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 398918] Akonadi server crashes after enabling Notification Monitor
https://bugs.kde.org/show_bug.cgi?id=398918 --- Comment #1 from Christoph Feck --- Pasting relevant part of backtrace from comment #0: Thread 3 (Thread 0x7fcbed5f5700 (LWP 27402)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/bits/atomic_base.h:713 #7 std::atomic::load (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/atomic:452 #8 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227 #9 QBasicAtomicPointer::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:238 #10 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x0) at tools/qsharedpointer.cpp:1445 #11 0x5626c27c9fd1 in QWeakPointer::QWeakPointer (ptr=0x0, this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:684 #12 QPointer::QPointer (p=0x0, this=) at /usr/include/qt5/QtCore/qpointer.h:71 #13 Akonadi::Server::NotificationSubscriber::notify (this=this@entry=0x0, notification=...) at /var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationsubscriber.cpp:646 #14 0x5626c27c2ca6 in Akonadi::Server::NotificationManager::emitPendingNotifications (this=0x5626c2b76230) at /var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationmanager.cpp:226 #15 0x7fcbf99890a7 in QtPrivate::QSlotObjectBase::call (a=0x7fcbed5f4500, r=0x5626c2b76230, this=0x7fcbe0005120) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #16 QMetaObject::activate (sender=sender@entry=0x7fcbe0004f00, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fcbed5f4500) at kernel/qobject.cpp:3750 #17 0x7fcbf9989607 in QMetaObject::activate (sender=sender@entry=0x7fcbe0004f00, m=m@entry=0x7fcbf9da8ec0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fcbed5f4500) at kernel/qobject.cpp:3629 #18 0x7fcbf9995427 in QTimer::timeout (this=this@entry=0x7fcbe0004f00, _t1=...) at .moc/moc_qtimer.cpp:200 #19 0x7fcbf9995738 in QTimer::timerEvent (this=0x7fcbe0004f00, e=) at kernel/qtimer.cpp:255 #20 0x7fcbf9989c8b in QObject::event (this=0x7fcbe0004f00, e=) at kernel/qobject.cpp:1269 #21 0x7fcbf996025a in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1099 #22 0x7fcbf9960347 in QCoreApplication::notifyInternal2 (receiver=0x7fcbe0004f00, event=event@entry=0x7fcbed5f4680) at kernel/qcoreapplication.cpp:1024 #23 0x7fcbf99b0c8b in QCoreApplication::sendEvent (event=0x7fcbed5f4680, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #24 QTimerInfoList::activateTimers (this=0x7fcbe0004cf0) at kernel/qtimerinfo_unix.cpp:643 #25 0x7fcbf99b1581 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #26 0x7fcbf5a4a5a7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7fcbf5a4a810 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x7fcbf5a4a8bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x7fcbf99b19bf in QEventDispatcherGlib::processEvents (this=0x7fcbeb20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7fcbf995f0ba in QEventLoop::exec (this=this@entry=0x7fcbed5f4910, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #31 0x5626c27c3963 in Akonadi::Server::NotificationManager::waitForSocketData (this=0x5626c2b76230) at /var/tmp/portage/kde-apps/akonadi-18.04.3/work/akonadi-18.04.3/src/server/notificationmanager.cpp:129 #32 0x7fcbf99954d4 in QtPrivate::QSlotObjectBase::call (a=0x7fcbed5f49c0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #33 QSingleShotTimer::timerEvent (this=0x7fcbe00142e0) at kernel/qtimer.cpp:318 #34 0x7fcbf9989c8b in QObject::event (this=0x7fcbe00142e0, e=) at kernel/qobject.cpp:1269 #35 0x7fcbf996025a in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1099 #36 0x7fcbf9960347 in QCoreApplication::notifyInternal2 (receiver=0x7fcbe00142e0, event=event@entry=0x7fcbed5f4b10) at kernel/qcoreapplication.cpp:1024 #37 0x7fcbf99b0c8b in QCoreApplication::sendEvent (event=0x7fcbed5f4b10, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #38 QTimerInfoList::activateTimers (this=0x7fcbe0004cf0) at kernel/qtimerinfo_unix.cpp:643 #39 0x7fcbf99b1581 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #40 0x7fcbf5a4a5a7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #41 0x7fcbf5a4a810 in ?? () from /usr/lib64/libglib-2.0.so.0 #42 0x7fcbf5a4a8bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #43 0x7fcbf99b19bf in QEventDispatcherGlib::processEvents (this=0x7fcbeb20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #44 0x7fcbf995f0ba in QEventLoop::exec (this=this@entry=0x7fcbed5f4d60, flags=...,
[akregator] [Bug 382575] Akregator crash when middle-clicking a link
https://bugs.kde.org/show_bug.cgi?id=382575 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Christoph Feck --- See comment #2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399501] kio master fails to compile looking for KIO::SlaveInterface::open64()
https://bugs.kde.org/show_bug.cgi?id=399501 --- Comment #2 from bluescreenaven...@gmail.com --- Seeing that is a year old, it looks like it must be a cmake regression? I was using cmake from the Release branch... ...trying cmake's v3.12.3 tag, and it worked. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396730] Discover crashes when closed while checking for updates
https://bugs.kde.org/show_bug.cgi?id=396730 Aleix Pol changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit|https://commits.kde.org/dis |https://commits.kde.org/dis |cover/f55fd33c294284a0a1e64 |cover/9a8f22b373095cabdb1c0 |c0c7c626e3bb0f853d4 |33709ac4c8d22ed5ea7 Resolution|--- |FIXED --- Comment #4 from Aleix Pol --- Git commit 9a8f22b373095cabdb1c033709ac4c8d22ed5ea7 by Aleix Pol. Committed on 10/10/2018 at 23:55. Pushed by apol into branch 'Plasma/5.14'. flatpak: wait for threads to finish before closing completely M +1-0libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp https://commits.kde.org/discover/9a8f22b373095cabdb1c033709ac4c8d22ed5ea7 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399502] During search, show the correct sort order
https://bugs.kde.org/show_bug.cgi?id=399502 Aleix Pol changed: What|Removed |Added Summary|Search results sorted |During search, show the |seemingly randomly, and do |correct sort order |not respect selected sort | |order | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399502] Search results sorted seemingly randomly, and do not respect selected sort order
https://bugs.kde.org/show_bug.cgi?id=399502 --- Comment #9 from Aleix Pol --- Alright, then let's give this a go. I'll rename this bug to show when we're sorting by relevance, please if you find cases where what we're displaying is clearly wrong report so and we'll address it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399341] all backends + no internet = GUI update blocked for literal seconds
https://bugs.kde.org/show_bug.cgi?id=399341 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dis ||cover/2623dae7b9ff2f89887f8 ||e9a5f3268a5a57deedd --- Comment #2 from Aleix Pol --- Git commit 2623dae7b9ff2f89887f8e9a5f3268a5a57deedd by Aleix Pol. Committed on 10/10/2018 at 23:49. Pushed by apol into branch 'Plasma/5.14'. fwupd: move blocking dbus call into the initialization thread M +23 -33 libdiscover/backends/FwupdBackend/FwupdBackend.cpp M +5-10 libdiscover/backends/FwupdBackend/FwupdBackend.h https://commits.kde.org/discover/2623dae7b9ff2f89887f8e9a5f3268a5a57deedd -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #29 from Stefan Brüns --- (In reply to José Alberto from comment #28) > (In reply to Stefan Brüns from comment #27) > > (In reply to José Alberto from comment #26) > > > This is back for LUKS containers (or maybe it was never completely gone, I > > > did never tested LUKS containers, I didn't even knew what they were last > > > time I posted here). > > > > > > I have recorded a video, just in case it helps. It will be in this link > > > for > > > a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG > > > > > > Thanks! > > > > Please describe exactly > > - how your setup looks like > > - what you do > > - what happens > > > > I will *not* try to extract information from some random internet video > > link! > > I didn't open a new bug because the setup has always been the same, you can > find all the things you ask for in the first comment talking about luks > containers. If you need more info than that, just ask more specifically and > I'll give more information (see > https://bugs.kde.org/show_bug.cgi?id=391706#c14 ). I asked *you* about *your* setup. It may be similar or even identical to the one originally reported, but without detailed information it is impossible to know. It is also impossible to know if your setup is completely unaltered since, this includes any other software, e.g. kernel, udev, udisks2 at least. It is not possible to check the data you provided earlier (which may be deprecated anyway) as the pastebin has vanished. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395506] "use same aspect as pixel" ignores monitor resolution when calculating display size
https://bugs.kde.org/show_bug.cgi?id=395506 --- Comment #3 from Storm Engineer --- (In reply to Boudewijn Rempt from comment #2) > Could you please check whether this is reproducible in the latest nightly > build? I can't reproduce anymore. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 --- Comment #2 from Egmont Koblinger --- I've tested all the independent terminal emulator implementations I have on my system. The following 7 of them erase the 79th character: Linux console, xterm, VTE, konsole, mlterm, st (suckless), terminology. The following 5 of them erase the 80th character: urxvt, pterm (PuTTY), Kitty, screen, tmux. Sigh. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399632] Can't load mail via VPN
https://bugs.kde.org/show_bug.cgi?id=399632 sr-tr...@yandex.ru changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from sr-tr...@yandex.ru --- Bad ipv6 setups on VPN -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399632] Can't load mail via VPN
https://bugs.kde.org/show_bug.cgi?id=399632 sr-tr...@yandex.ru changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399615] Mishandling \b at the right margin
https://bugs.kde.org/show_bug.cgi?id=399615 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #1 from Egmont Koblinger --- xfce4-terminal and gnome-terminal uses the very same terminal emulation widget (VTE), they must behave identically. As far as VTE is concerned, see https://gitlab.gnome.org/GNOME/vte/issues/60 and https://bugzilla.gnome.org/show_bug.cgi?id=731155. It would be great to know how some popular hardware emulators behaved. Not sure if this info can be found somewhere, e.g. on vt100.net. I'm almost sure they behaved like VTE and Konsole do now. Carefully reading ECMA-48 would possibly also provide the right answer for the expected (documented) behavior. C99 is not a reference for the behavior of terminal emulators. In my opinion the current behavior makes no sense at all, I agree with you that it'd be better if the character at the 80th position was removed. But you can't just change the behavior against the standards and the assumptions of existing software, this would result in potentially plenty of apps breaking. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 399608] Notifications in kde truncate after '<' character in body
https://bugs.kde.org/show_bug.cgi?id=399608 --- Comment #7 from Christoph Feck --- I don't have libnotify installed, but using kdialog I could confirm that Plasma properly substitutes XML entities. kdialog --passivepopup "Hello Plasma Qt" 1 kdialog --passivepopup "while (1<2)" 1 --icon dialog-error kdialog --passivepopup "while (12)" 1 --icon dialog-information First line demonstrates XML markup, second line truncates, third line works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399598] Can't pick colors from palettes anymore (nightly build)
https://bugs.kde.org/show_bug.cgi?id=399598 wolthera changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED CC||griffinval...@gmail.com --- Comment #3 from wolthera --- it should be 'fixed now', we still need to do some stuff about it because that was a fix for another bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394057] ghost clicking when using selection tools
https://bugs.kde.org/show_bug.cgi?id=394057 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from mvowada --- Hi Arielle, are you still able to reproduce it with the latest Krita (https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/)? Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399634] System Settings crashes when launched from system tray
https://bugs.kde.org/show_bug.cgi?id=399634 Nate Graham changed: What|Removed |Added Component|general |general CC||n...@kde.org Product|kde |systemsettings Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Version|unspecified |5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure()
https://bugs.kde.org/show_bug.cgi?id=375913 Nate Graham changed: What|Removed |Added CC||mike.spa...@gmail.com --- Comment #25 from Nate Graham --- *** Bug 399635 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399635] Discover crashed when launched from "Updates" widget
https://bugs.kde.org/show_bug.cgi?id=399635 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- Problem with your graphics drivers. *** This bug has been marked as a duplicate of bug 375913 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 --- Comment #6 from Nate Graham --- Done. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 --- Comment #5 from Chris Holland --- > add you to the email list for new bugs? For AWC? Sure. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 --- Comment #4 from Christoph Feck --- Ouch, I search everything starting with 'a' and 'w' ... -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659 --- Comment #30 from manuel fernández --- Created attachment 115553 --> https://bugs.kde.org/attachment.cgi?id=115553=edit text file you asked for. It is a bib file but has extension .txt -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Ben Bullard changed: What|Removed |Added CC||benbullar...@cox.net --- Comment #8 from Ben Bullard --- Yes, I don't quite understand why anyone needs an e-mail client for one e-mail account anyway. But the argument around here is whether I'm old fashioned or just old... Anyway I would very much like to see Trojita with ability to do multiple e-mail accounts. Perhaps I can help with testing? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659
--- Comment #29 from manuel fernández ---
(In reply to manuel fernández from comment #27)
> (In reply to Thomas Fischer from comment #26)
> > Created attachment 115552 [details]
> > Second patch to print more debug output
> >
> > Comment 25 contained the output I was looking for. Unfortunately, it did not
> > help me to trace back the problem. So, here comes a new patch which prints
> > debug output at other places.
> > Please test it. It should be possible to apply this patch even with the
> > first one still applied. If you encounter problems applying this patch, run
> > git checkout -- src
> > first.
> >
> > Also, I saw that KBibTeX tried to open a .txt file. I wonder what this
> > file's content may be. Could you please tell me more? In case the file is
> > not too large, just attach it to the bug report; otherwise post the first 10
> > lines or so.
>
> Here is the console output once the patch was applied:
>
> mfg@bix:~/sysi/com/down/kbibtex/kbibtex$ /tmp/usr/bin/kbibtex
> kbibtex.program: Starting KBibTeX version "4c322b11 (master)"
>
> QCommandLineParser: option not defined: "author"
>
> QCommandLineParser: option not defined: "license"
>
> QCommandLineParser: option not defined: "desktopfile"
>
> Empty filename for XSLT
>
> Empty filename for XSLT
>
> kbibtex.program: WebEngine is available, using it instead of WebKit or HTML
> KPart (both neither considered nor tested for) for HTML/Web preview.
> No file found for ".xml" , even though update-mime-info said it would exist.
> Either it was just removed, or the directory doesn't have executable
> permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
> kbibtex.program: Using service "BibTeX Viewer and Editor" ( "KParts
> component to view and edit bibliographic files" ) for mime type
> "text/x-bibtex" through library "kbibtexpart"
> kf5.kxmlgui: this does not work on a KActionCollection containing actions!
> kbibtex.io: BibUtils found, using it to import/export certain types of
> bibliographies
> kbibtex.io: Unknown token ' 'e' ( "0x0065" ) ' near line 1140 ( ""
> "fe" ) , treating as comment
> kf5.kio.core: KSambaShare: Could not find smb.conf!
> kbibtex.program: Located KPart service: "kbibtexpart" with description
> "KParts component to view and edit bibliographic files" from library
> "kbibtexpart"
> No file found for ".xml" , even though update-mime-info said it would exist.
> Either it was just removed, or the directory doesn't have executable
> permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
> No file found for ".xml" , even though update-mime-info said it would exist.
> Either it was just removed, or the directory doesn't have executable
> permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
> No file found for ".xml" , even though update-mime-info said it would exist.
> Either it was just removed, or the directory doesn't have executable
> permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
> kbibtex.program: Using service "BibTeX Viewer and Editor" ( "KParts
> component to view and edit bibliographic files" ) for mime type
> "text/x-bibtex" through library "kbibtexpart"
> kf5.kxmlgui: this does not work on a KActionCollection containing actions!
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = kbibtex path = /tmp/usr/bin pid = 6861
> KCrash: Arguments: /tmp/usr/bin/kbibtex
> KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
> kdeinit
> sock_file=/run/user/1000/kdeinit5__0
>
> [1]+ Stopped /tmp/usr/bin/kbibtex
> mfg@bix:~/sysi/com/down/kbibtex/kbibtex$
--
here is the output with patch2
mfg@bix:~/sysi/com/down/kbibtex/kbibtex$ /tmp/usr/bin/kbibtex
kbibtex.program: Starting KBibTeX version "4c322b11 (master)"
QCommandLineParser: option not defined: "author"
QCommandLineParser: option not defined: "license"
QCommandLineParser: option not defined: "desktopfile"
Empty filename for XSLT
Empty filename for XSLT
kbibtex.program: WebEngine is available, using it instead of WebKit or HTML
KPart (both neither considered nor tested for) for HTML/Web preview.
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
kbibtex.program: Using service "BibTeX Viewer and Editor" ( "KParts component
to view and edit bibliographic files" ) for mime type "text/x-bibtex" through
library "kbibtexpart"
kf5.kxmlgui: this does not work on a KActionCollection containing actions!
kbibtex.io: BibUtils found, using it to import/export certain types of
bibliographies
kbibtex.io: Unknown token ' 'e' ( "0x0065" ) ' near line 1140
[krita] [Bug 399560] Bezier Curve Tool doesn't have a Solid Fill option
https://bugs.kde.org/show_bug.cgi?id=399560
mvowada changed:
What|Removed |Added
CC||freebo...@tiscali.it
Status|REPORTED|NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #1 from mvowada ---
Hi danil,
I'm not sure it is a bug actually.
Can you attach an image of the result you want to achieve ("Geometrical figures
filled with solid color with solid edges")?
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659
--- Comment #27 from manuel fernández ---
(In reply to Thomas Fischer from comment #26)
> Created attachment 115552 [details]
> Second patch to print more debug output
>
> Comment 25 contained the output I was looking for. Unfortunately, it did not
> help me to trace back the problem. So, here comes a new patch which prints
> debug output at other places.
> Please test it. It should be possible to apply this patch even with the
> first one still applied. If you encounter problems applying this patch, run
> git checkout -- src
> first.
>
> Also, I saw that KBibTeX tried to open a .txt file. I wonder what this
> file's content may be. Could you please tell me more? In case the file is
> not too large, just attach it to the bug report; otherwise post the first 10
> lines or so.
Here is the console output once the patch was applied:
mfg@bix:~/sysi/com/down/kbibtex/kbibtex$ /tmp/usr/bin/kbibtex
kbibtex.program: Starting KBibTeX version "4c322b11 (master)"
QCommandLineParser: option not defined: "author"
QCommandLineParser: option not defined: "license"
QCommandLineParser: option not defined: "desktopfile"
Empty filename for XSLT
Empty filename for XSLT
kbibtex.program: WebEngine is available, using it instead of WebKit or HTML
KPart (both neither considered nor tested for) for HTML/Web preview.
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
kbibtex.program: Using service "BibTeX Viewer and Editor" ( "KParts component
to view and edit bibliographic files" ) for mime type "text/x-bibtex" through
library "kbibtexpart"
kf5.kxmlgui: this does not work on a KActionCollection containing actions!
kbibtex.io: BibUtils found, using it to import/export certain types of
bibliographies
kbibtex.io: Unknown token ' 'e' ( "0x0065" ) ' near line 1140 ( ""
"fe" ) , treating as comment
kf5.kio.core: KSambaShare: Could not find smb.conf!
kbibtex.program: Located KPart service: "kbibtexpart" with description "KParts
component to view and edit bibliographic files" from library "kbibtexpart"
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/mfg/.local/share/mime", "/usr/share/mime")
kbibtex.program: Using service "BibTeX Viewer and Editor" ( "KParts component
to view and edit bibliographic files" ) for mime type "text/x-bibtex" through
library "kbibtexpart"
kf5.kxmlgui: this does not work on a KActionCollection containing actions!
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kbibtex path = /tmp/usr/bin pid = 6861
KCrash: Arguments: /tmp/usr/bin/kbibtex
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
[1]+ Stopped /tmp/usr/bin/kbibtex
mfg@bix:~/sysi/com/down/kbibtex/kbibtex$
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 373430] No immediate effect of adding currently indexed dir to excludes.
https://bugs.kde.org/show_bug.cgi?id=373430 --- Comment #8 from Nate Graham --- Gotcha. Thanks James! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659 --- Comment #28 from manuel fernández --- sorry, compiled with release, let me do it again! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Christoph Feck changed: What|Removed |Added Version Fixed In|18.08.2 |18.08.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 373430] No immediate effect of adding currently indexed dir to excludes.
https://bugs.kde.org/show_bug.cgi?id=373430 --- Comment #7 from Jamie Smith --- (In reply to Nate Graham from comment #6) > So would this be effectively fixed by fixing Bug 353559? It's part of the fix. The indexer needs to be restarted whenever the config changes, which isn't currently monitored for such changes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 399608] Notifications in kde truncate after '<' character in body
https://bugs.kde.org/show_bug.cgi?id=399608 --- Comment #6 from Nate Graham --- So yes, to answer your question forneus48, you should contact the Clementine developers and tell them to properly escape their strings. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 399636] Integrate Phabricator and Bugzilla
https://bugs.kde.org/show_bug.cgi?id=399636 Nathan Moos changed: What|Removed |Added OS|Linux |unspecified Platform|Other |unspecified -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 399636] New: Integrate Phabricator and Bugzilla
https://bugs.kde.org/show_bug.cgi?id=399636 Bug ID: 399636 Summary: Integrate Phabricator and Bugzilla Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: moosingin3sp...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY Mozilla's Bugzilla and Phabricator instances integrate well with each other. In particular, I can log into Mozilla Phabricator with my BMO account and when I submit diffs to Phabricator, they automatically link to the bug on BMO (and the inverse: BMO bug links to my Phabricator diff). I really like the workflow that Phabricator and Bugzilla promote, but it can be intimidating for new contributors who may be used to a GitHub/GitLab-style workflow. Deeper integration between the tools used would significantly reduce the overhead (and possibly even enable reuse of some Mozilla VCS documentation). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 399608] Notifications in kde truncate after '<' character in body
https://bugs.kde.org/show_bug.cgi?id=399608 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #5 from Christoph Feck --- To answer my own question: According to https://wiki.archlinux.org/index.php/Desktop_notifications libnotify follows the Notification Spec at https://developer.gnome.org/notification-spec/ which says the body may contain simple XML based Markup etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399587] Clicking on the palette slots in Text dialogue's Text Color popup does not change text color after the merge of new color palette code
https://bugs.kde.org/show_bug.cgi?id=399587 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it Ever confirmed|0 |1 --- Comment #1 from mvowada --- Hi and thanks again :) Could be a consequence of Bug 399598? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399596] Tag tree keeps reverting back to incorrect format after re-adding collection
https://bugs.kde.org/show_bug.cgi?id=399596 --- Comment #4 from Sebas --- Using 6.x now. I opened a photo in Notepad++ and found some interesting things. Apparently Digikam saves tag trees in images apart from the tags themselves. The latter ones can not be read by software like Windows Explorer or IrfanView. Digikam tag trees are saved in custom metadata fields. The strange thing is though...if I have moved all those images out of the wrong tree, why is this wrong tree still present in the custom metadata fields. It should have been cleared out. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 399608] Notifications in kde truncate after '<' character in body
https://bugs.kde.org/show_bug.cgi?id=399608 --- Comment #4 from Christoph Feck --- I am not sure if this is intentional. Is 'libnotify' using some XDG standard for notifications? If there is a standard, and it forbids rich text, then Plasma notifications should have a way to show plain notifications, without any character substitutions. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399635] New: Discover crashed when launched from "Updates" widget
https://bugs.kde.org/show_bug.cgi?id=399635 Bug ID: 399635 Summary: Discover crashed when launched from "Updates" widget Product: Discover Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mike.spa...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I saw that the "Updates" widget on my notification area had a blue dot. I clicked it to launch Discover so that I could apply the updates. The Discover window displayed briefly (about 2 seconds) in an incomplete state, and then went away. A crash handler popped up just before the Discover window disappeared. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ec3a68800 (LWP 12308))] Thread 11 (Thread 0x7f9e77fff700 (LWP 12318)): #0 0x7f9eb9873963 in g_private_get () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9eb9856370 in g_thread_self () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9eb982e53d in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9ebf98490b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9ebf9299ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ebf74822a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ebf74d16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9ebb95b6db in start_thread (arg=0x7f9e77fff700) at pthread_create.c:463 #8 0x7f9ebf04888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f9e853da700 (LWP 12317)): #0 0x7f9ebb961ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f9e853d9c40, expected=0, futex_word=0x7f9e7c0042f4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f9ebb961ed9 in __pthread_cond_wait_common (abstime=0x7f9e853d9d00, mutex=0x7f9e7c0042a0, cond=0x7f9e7c0042c8) at pthread_cond_wait.c:533 #2 0x7f9ebb961ed9 in __pthread_cond_timedwait (cond=0x7f9e7c0042c8, mutex=0x7f9e7c0042a0, abstime=0x7f9e853d9d00) at pthread_cond_wait.c:667 #3 0x7f9ebf74e458 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9ebf74a52d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ebf74d16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ebb95b6db in start_thread (arg=0x7f9e853da700) at pthread_create.c:463 #7 0x7f9ebf04888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f9e85bdb700 (LWP 12316)): #0 0x7f9eb982b3c7 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9eb982dd62 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9eb982e3e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9eb982e54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9ebf98490b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9ebf9299ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ebf74822a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9ebf74d16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ebb95b6db in start_thread (arg=0x7f9e85bdb700) at pthread_create.c:463 #9 0x7f9ebf04888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f9e877fe700 (LWP 12315)): #0 0x7f9ebf0370b4 in __GI___libc_read (fd=17, buf=0x7f9e877fdb90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f9eb9872a00 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9eb982df27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9eb982e3e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9eb982e54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9ebf98490b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9ebf9299ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9ebf74822a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ebf74d16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9
[frameworks-baloo] [Bug 373430] No immediate effect of adding currently indexed dir to excludes.
https://bugs.kde.org/show_bug.cgi?id=373430 --- Comment #6 from Nate Graham --- So would this be effectively fixed by fixing Bug 353559? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399586] Picking color from screen is missing in Text dialogue after merging the new color palette codes
https://bugs.kde.org/show_bug.cgi?id=399586 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it Ever confirmed|0 |1 --- Comment #1 from mvowada --- Hi Tyson and thanks for the report. I'm marking this as "Confirmed". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384102] Stuck at "Waiting for image operation to complete" after undoing "Convert Image Color Space"
https://bugs.kde.org/show_bug.cgi?id=384102 --- Comment #7 from mvowada --- (In reply to mvowada from comment #6) > (Just encountered the issue in Krita 4.2.0-pre-alpha (git 4a0b033) - Ubuntu > 14.04 LTS) In my case: 1. "CTRL + N" (New document, any type) 2. (menu >) Image > Convert Image Color Spece... 3. "CTRL + Z" (Undo) Actual Results: the waiting box appears and stays open Expected Results: waiting box closing when done with the color space conversion. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397863] Discover crashes somewhere in QQuickMenu
https://bugs.kde.org/show_bug.cgi?id=397863 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||5.51 Resolution|--- |FIXED --- Comment #14 from Nate Graham --- Oh lol of course. Let's re-open again if the crashes keep crashing after 5.51 is in users' hands. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399634] New: System Settings crashes when launched from system tray
https://bugs.kde.org/show_bug.cgi?id=399634 Bug ID: 399634 Summary: System Settings crashes when launched from system tray Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stephe...@lineone.net Target Milestone: --- Application: kdeinit5 (5.12.5) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.19-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Opening "configure layouts" dialog from context menu for Keyboard Layout icon in system tray -- Backtrace: Application: System Settings Module (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2ad91a3900 (LWP 30879))] Thread 3 (Thread 0x7f2ab9f00700 (LWP 30883)): #0 0x7f2ad3987774 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f2ad3941fbd in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2ad394221c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2ad77edc0b in QEventDispatcherGlib::processEvents (this=0x7f2ab4000b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2ad779609a in QEventLoop::exec (this=this@entry=0x7f2ab9effca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2ad75c54da in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f2acbae3985 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2ad75ca0ce in QThreadPrivate::start (arg=0x7f2acbd53d60) at thread/qthread_unix.cpp:368 #8 0x7f2ad58dc559 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2ad725282f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2ac0ce9700 (LWP 30880)): #0 0x7f2ad724808b in poll () from /lib64/libc.so.6 #1 0x7f2ad8615387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f2ad8616faa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f2ac3262029 in QXcbEventReader::run (this=0x5634a547c740) at qxcbconnection.cpp:1330 #4 0x7f2ad75ca0ce in QThreadPrivate::start (arg=0x5634a547c740) at thread/qthread_unix.cpp:368 #5 0x7f2ad58dc559 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2ad725282f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2ad91a3900 (LWP 30879)): [KCrash Handler] #6 0x7f2ac3267880 in QHash::remove (this=0x5634a5412508, akey=@0x7fff5029698c: 201326597, akey@entry=@0x7fff5029698c: ) at ../../../../include/QtCore/../../src/corelib/tools/qhash.h:800 #7 0x7f2ac3261e39 in QXcbConnection::removeWindowEventListener (this=, id=) at qxcbconnection.cpp:722 #8 0x7f2ac327705a in QXcbWindow::destroy (this=this@entry=0x5634a5a57b00) at qxcbwindow.cpp:631 #9 0x7f2ac327717b in QXcbWindow::~QXcbWindow (this=0x5634a5a57b00, __in_chrg=) at qxcbwindow.cpp:599 #10 0x7f2abbbf2a8d in QXcbGlxWindow::~QXcbGlxWindow (this=0x5634a5a57b00, __in_chrg=) at qxcbglxwindow.cpp:52 #11 QXcbGlxWindow::~QXcbGlxWindow (this=0x5634a5a57b00, __in_chrg=) at qxcbglxwindow.cpp:54 #12 0x7f2ad7d730a1 in QWindowPrivate::destroy (this=0x5634a573d7f0) at kernel/qwindow.cpp:1838 #13 0x7f2ad5e8e294 in QWidgetPrivate::deleteTLSysExtra (this=0x5634a5527860) at kernel/qwidget.cpp:1918 #14 0x7f2ad5e92cb8 in QWidget::destroy (this=this@entry=0x5634a55a6a70, destroyWindow=destroyWindow@entry=true, destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget.cpp:12456 #15 0x7f2ad5e99d38 in QWidget::~QWidget (this=0x5634a55a6a70, __in_chrg=) at kernel/qwidget.cpp:1705 #16 0x7f2ac5670f0d in KCMShellMultiDialog::~KCMShellMultiDialog (this=0x5634a55a6a70, __in_chrg=) at /usr/src/debug/kde-cli-tools5-5.12.5-lp150.1.1.x86_64/build/kcmshell/kdeinit_kcmshell5_autogen/EWIEGA46WW/../../../../kcmshell/main.h:81 #17 KCMShellMultiDialog::~KCMShellMultiDialog (this=0x5634a55a6a70, __in_chrg=) at /usr/src/debug/kde-cli-tools5-5.12.5-lp150.1.1.x86_64/build/kcmshell/kdeinit_kcmshell5_autogen/EWIEGA46WW/../../../../kcmshell/main.h:81 #18 0x7f2ad77c5a58 in QObject::event (this=this@entry=0x5634a55a6a70, e=e@entry=0x5634a596ddf0) at kernel/qobject.cpp:1237 #19 0x7f2ad5e9e473 in QWidget::event (this=0x5634a55a6a70, event=0x5634a596ddf0) at kernel/qwidget.cpp:9345 #20 0x7f2ad5e61e8c in QApplicationPrivate::notify_helper (this=this@entry=0x5634a550f270, receiver=receiver@entry=0x5634a55a6a70, e=e@entry=0x5634a596ddf0) at kernel/qapplication.cpp:3723 #21 0x7f2ad5e69244 in QApplication::notify (this=0x7fff50297210, receiver=0x5634a55a6a70, e=0x5634a596ddf0) at kernel/qapplication.cpp:3482 #22 0x7f2ad7797a88 in QCoreApplication::notifyInternal2 (receiver=0x5634a55a6a70, event=event@entry=0x5634a596ddf0) at
[Discover] [Bug 397863] Discover crashes somewhere in QQuickMenu
https://bugs.kde.org/show_bug.cgi?id=397863 --- Comment #13 from Christoph Feck --- Commit from comment #7 is in kirigami 5.51, which is not released yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384102] Stuck at "Waiting for image operation to complete" after undoing "Convert Image Color Space"
https://bugs.kde.org/show_bug.cgi?id=384102 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #6 from mvowada --- (Just encountered the issue in Krita 4.2.0-pre-alpha (git 4a0b033) - Ubuntu 14.04 LTS) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 --- Comment #3 from Nate Graham --- I found it at https://cgit.kde.org/plasma-active-window-control.git -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 --- Comment #2 from Christoph Feck --- > Active Window Control is a KDE project Where is it's repo? I cannot remember we incubated it. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 398416] Crash on startup via Panel icon
https://bugs.kde.org/show_bug.cgi?id=398416 --- Comment #16 from Albert Astals Cid --- https://phabricator.kde.org/D16118 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Thomas Surrel changed: What|Removed |Added Latest Commit|https://commits.kde.org/dol |https://commits.kde.org/dol |phin/105fe62eeb3ec3258a3540 |phin/200e0d1f07428427913bd1 |0a1e6cb2901e01ac2d |18467909d77c14a742 --- Comment #4 from Thomas Surrel --- Git commit 200e0d1f07428427913bd118467909d77c14a742 by Thomas Surrel. Committed on 10/10/2018 at 21:05. Pushed by thsurrel into branch 'Applications/18.08'. Update hidden state correctly Summary: When renaming a file from '.hidden' to 'not_hidden', the file would still be displayed like a hidden file with a semi-transparent icon and a grey text. Reviewers: #dolphin, elvisangelaccio Reviewed By: elvisangelaccio Subscribers: elvisangelaccio, kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D16115 M +2-2src/kitemviews/kfileitemmodel.cpp https://commits.kde.org/dolphin/200e0d1f07428427913bd118467909d77c14a742 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399633] Compiling fails with QT 5.9
https://bugs.kde.org/show_bug.cgi?id=399633 --- Comment #2 from Pierre "bloodywing" Geier --- Yes just saw it after I finished writing the bug :( 2444d1f75f70b321dca6cda36d1965548e5ff5b0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399633] Compiling fails with QT 5.9
https://bugs.kde.org/show_bug.cgi?id=399633 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |FIXED --- Comment #1 from Boudewijn Rempt --- Dmitry already fixed this... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399633] New: Compiling fails with QT 5.9
https://bugs.kde.org/show_bug.cgi?id=399633 Bug ID: 399633 Summary: Compiling fails with QT 5.9 Product: krita Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bloodyw...@tastyespresso.de Target Milestone: --- SUMMARY Commit 16ce49fc158d6c379c8a180b7c2f6c46549543cd breaks compatibility with QT 5.9 which is currently LTS STEPS TO REPRODUCE 1. Get QT 5.9 2. try to compile OBSERVED RESULT A call to screenAt for QApplication fails with everything below QT 5.10. This is a new feature that was added. EXPECTED RESULT Krita compiles just fine SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.3 KDE Frameworks Version: 5.43.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION QT 5.9 is LTS and the most recent version you can get on Gentoo and Funtoo without overlay. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Nate Graham changed: What|Removed |Added Version Fixed In||18.08.2 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Nate Graham changed: What|Removed |Added CC||terce...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 389270 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389270] Color of hidden files don't change after renaming them
https://bugs.kde.org/show_bug.cgi?id=389270 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- Just fixed in Bug 399599! *** This bug has been marked as a duplicate of bug 399599 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399419] Show Painting Assistants toggle is inconsistent between windows
https://bugs.kde.org/show_bug.cgi?id=399419 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #6 from mvowada --- (In reply to Boudewijn Rempt from comment #4) > That > looks like an interesting comic, btw... Oh yes, agree :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] KDE Discover crashes on launch in QSGRenderLoop::handleContextCreationFailure()
https://bugs.kde.org/show_bug.cgi?id=375913 Nate Graham changed: What|Removed |Added CC||agentti0...@gmail.com --- Comment #24 from Nate Graham --- *** Bug 399557 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399557] Gwenview plugin installation menu does not open
https://bugs.kde.org/show_bug.cgi?id=399557 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- Problem with your graphics drivers. See duped bug. *** This bug has been marked as a duplicate of bug 375913 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Thomas Surrel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dol ||phin/105fe62eeb3ec3258a3540 ||0a1e6cb2901e01ac2d Resolution|--- |FIXED --- Comment #2 from Thomas Surrel --- Git commit 105fe62eeb3ec3258a35400a1e6cb2901e01ac2d by Thomas Surrel. Committed on 10/10/2018 at 20:49. Pushed by thsurrel into branch 'master'. Update hidden state correctly Summary: When renaming a file from '.hidden' to 'not_hidden', the file would still be displayed like a hidden file with a semi-transparent icon and a grey text. Reviewers: #dolphin, elvisangelaccio Reviewed By: elvisangelaccio Subscribers: elvisangelaccio, kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D16115 M +2-2src/kitemviews/kfileitemmodel.cpp https://commits.kde.org/dolphin/105fe62eeb3ec3258a35400a1e6cb2901e01ac2d -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399553] "need to remove to install" prompt scales poorly
https://bugs.kde.org/show_bug.cgi?id=399553 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #4 from Nate Graham --- A scrollview would be nice. Also, there's no reason for the dang thing to take up the entire window width when the window is wide. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 394659] crash after compilation
https://bugs.kde.org/show_bug.cgi?id=394659 --- Comment #26 from Thomas Fischer --- Created attachment 115552 --> https://bugs.kde.org/attachment.cgi?id=115552=edit Second patch to print more debug output Comment 25 contained the output I was looking for. Unfortunately, it did not help me to trace back the problem. So, here comes a new patch which prints debug output at other places. Please test it. It should be possible to apply this patch even with the first one still applied. If you encounter problems applying this patch, run git checkout -- src first. Also, I saw that KBibTeX tried to open a .txt file. I wonder what this file's content may be. Could you please tell me more? In case the file is not too large, just attach it to the bug report; otherwise post the first 10 lines or so. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399435] crash when rightclicking the animation timeline.
https://bugs.kde.org/show_bug.cgi?id=399435 mvowada changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399435] crash when rightclicking the animation timeline.
https://bugs.kde.org/show_bug.cgi?id=399435 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #4 from mvowada --- Created attachment 115551 --> https://bugs.kde.org/attachment.cgi?id=115551=edit (Video example) (Krita 4.2.0-pre-alpha (git 4a0b033) - Ubuntu 14.04 LTS, Unity) Hi all, possibly the same issue still affects the "Animation Curves" docker in the latest nightly build? (see video) 1. right-click over the timeline of the "Animation Curves" docker Actual Results: assert abort -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399355] Add callgrind_diff
https://bugs.kde.org/show_bug.cgi?id=399355 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #3 from Philippe Waroquiers --- I tried callgrind_diff at work on big callgrind out files, but I got several error messages. At least one of them can be reproduced by doing: ./vg-in-place --tool=callgrind --dump-instr=yes --collect-jumps=yes --collect-systime=yes ./perf/memrw -l 5 ./vg-in-place --tool=callgrind --dump-instr=yes --collect-jumps=yes --collect-systime=yes ./perf/memrw -l 3 and then running callgrind_diff on the resulting 2 files: ./Inst/bin/callgrind_diff callgrind.out.8448 callgrind.out.8452 Line 179: too many event counts On the big file, before this 'too many event counts', I have a bunch of errors such as: Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 27. Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 28. Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 29. Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 32. Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 34. Argument "*" isn't numeric in addition (+) at /home/philippe/valgrind/git/fixes/Inst/bin/callgrind_diff line 139, line 35. The first few lines of the big callgrind files are: # callgrind format version: 1 creator: callgrind-3.14.0.GIT pid: 24494 cmd: counterp_process part: 5 desc: I1 cache: desc: D1 cache: desc: LL cache: desc: Timerange: Basic block 21282324349 - 244375501750 desc: Trigger: dump End_of_script_./replay/scripts/minutely_targets.replay.el positions: instr line events: Ir sysCount sysTime summary: 1006404365481 50339204 252715138 ob=(3) /usr/lib64/libc-2.17.so fl=(613) /usr/src/debug/glibc-2.17-c758a686/misc/tsearch.c fn=(4236) tfind 0xf43a0 307 2 +2 +3 2 +3 -3 2 +3 * 2 +1 * 2 +3 * 2 +1 +3 2 jcnd=2/2 +37 +5 * * +37 +5 2 +3 * 2 +3 * 2 +2 +12 2 +1 * 2 +1 -16 2 +2 +16 2 +2 * 2 -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 398416] Crash on startup via Panel icon
https://bugs.kde.org/show_bug.cgi?id=398416 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #15 from Albert Astals Cid --- Actually i can reproduce the problem myself. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 398416] Crash on startup via Panel icon
https://bugs.kde.org/show_bug.cgi?id=398416 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #14 from Albert Astals Cid --- If you start it from the terminal does it have the same problem? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 399562] Update Notifier appears as blank space
https://bugs.kde.org/show_bug.cgi?id=399562 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399539] [Feature Request] More Remote Options
https://bugs.kde.org/show_bug.cgi?id=399539 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399554] Empty space above "Recent apps" when plasma panel is positioned on top of the screen and the favorites list contains several apps
https://bugs.kde.org/show_bug.cgi?id=399554 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Yes, it's because there are so many favorites. Clearly intentional at the moment, but maybe worth revisiting the design to better accommodate this situation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399630] Kwin crash when starting short script
https://bugs.kde.org/show_bug.cgi?id=399630 David Edmundson changed: What|Removed |Added Resolution|BACKTRACE |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #2 from David Edmundson --- Edit. We've got two of these in 5.14.0, clearly some regression. Time to sleuth without symbols. It's a window being repainted in a postPaintScreen looking at all the calls, that means it has to be DimInactive. The rest of the calls from other effects are in the effect's postPaintWindow. >From the trace, I suspect we're getting a group change after a windowClosed which is reinserting it into our m_transitions hash. @Robby if you can reproduce it if you could note how the window you're closing are stacked that would help. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399536] Need a place on KDE Bug Tracker for Active Window Control widget
https://bugs.kde.org/show_bug.cgi?id=399536 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org, ||zrenf...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- Done: https://bugs.kde.org/describecomponents.cgi?product=Active%20Window%20Control Chris, would you like me to add you to the email list for new bugs? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399598] Can't pick colors from palettes anymore (nightly build)
https://bugs.kde.org/show_bug.cgi?id=399598 mvowada changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
