[kdepim] [Bug 392105] Editing message list themes doesn't work
https://bugs.kde.org/show_bug.cgi?id=392105 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- did you select the new theme ? Here it works fine -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 392122] New: KRDC could not connect to a Windows Server 2016 over RDP after a update of the Server
https://bugs.kde.org/show_bug.cgi?id=392122 Bug ID: 392122 Summary: KRDC could not connect to a Windows Server 2016 over RDP after a update of the Server Product: krdc Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: pa...@web.de Target Milestone: --- Hi, i updated my Windows server 2016 with this Windows Update 2018-03 Kumulatives Update für Windows Server 2016 für x64-basierte Systeme (KB4088787). After this KRDC 17.04.2 can not connectet to the Server over RDP, i think it like a Problem with this changes in the CretSSP https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 391960] NETWinInfo::setFullscreenMonitors incorrectly implemented
https://bugs.kde.org/show_bug.cgi?id=391960 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||ndowsystem/cc5d6fde1abad968 ||a6c54e872a56833db876dca4 --- Comment #2 from Martin Flöser --- Git commit cc5d6fde1abad968a6c54e872a56833db876dca4 by Martin Flöser. Committed on 18/03/2018 at 10:45. Pushed by graesslin into branch 'master'. [xcb] Fix implementation of _NET_WM_FULLSCREEN_MONITORS Summary: According to NETWM spec the client "wishing to change this list MUST send a _NET_WM_FULLSCREEN_MONITORS client message to the root window". This was not implemented at all, instead the property was updated. The property must be set by the window manager, or as the spec says: "The Window Manager MUST keep this list updated to reflect the current state of the window." In KWin (as the user of NETWinInfo) this was implemented correctly (see kwin, file netinfo.cpp method WinInfo::changeFullscreenMonitors). Test Plan: New test case added which verifies the client/wm interplay, old and incorrect test case removed Reviewers: #frameworks, #kwin, #plasma Tags: #frameworks Differential Revision: https://phabricator.kde.org/D11414 M +0-44 autotests/netwininfotestclient.cpp M +85 -0autotests/netwininfotestwm.cpp M +17 -11 src/platforms/xcb/netwm.cpp https://commits.kde.org/kwindowsystem/cc5d6fde1abad968a6c54e872a56833db876dca4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392121] New: color selector settings icon preferences slight ui issue
https://bugs.kde.org/show_bug.cgi?id=392121 Bug ID: 392121 Summary: color selector settings icon preferences slight ui issue Product: krita Version: 3.3.2 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: pricelist2...@gmx.com Target Milestone: --- Created attachment 111536 --> https://bugs.kde.org/attachment.cgi?id=111536&action=edit ui bug mac os preferences, the color selector settings icon has a little white line next to it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392120] New: double clicking on a .kra file opens krita, but not the file
https://bugs.kde.org/show_bug.cgi?id=392120 Bug ID: 392120 Summary: double clicking on a .kra file opens krita, but not the file Product: krita Version: 3.3.2 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: pricelist2...@gmx.com Target Milestone: --- When i double click on a .kra file it launches Krita, but does not open the file. I have to double click the .kra file a second time when Krita is already launched for it to open. Tested a few times with different files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392119] New: quick look config conflicting with qlstephen
https://bugs.kde.org/show_bug.cgi?id=392119 Bug ID: 392119 Summary: quick look config conflicting with qlstephen Product: krita Version: 3.3.2 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: pricelist2...@gmx.com Target Milestone: --- qlstephen is a mac os quick look plugin used by macvim to allow users of mac ox to quick view text files with no file extension. the quick look plugin config file that comes with krita to quick look at .kra files has a seemingly unneeded key which blocks the qlstephen plugin from working. after installing krita, there are quick look warnings in the console, warning that a plugin is shadowing another, it's most likely the public.data key you can enable quick look logging with: defaults write -g QLEnableLogging YES by deleting the CFBundleDocumentTypes > Item 1 > LSItemContentTypes > public.data key from the krita quick look plugin's Info.plist I was able to restore the functionality of qlstephen to normal, without seemingly effecting the krita quick look plugin. I restarted the machine and tested again and both file formats now go to the proper quick look plugin. https://i.imgur.com/XSDq8nx.png -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392111] Kwin crashes when displaying overview repeatedly
https://bugs.kde.org/show_bug.cgi?id=392111 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #3 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 392077] Import data headers treat spaces as tab delimiter
https://bugs.kde.org/show_bug.cgi?id=392077 --- Comment #3 from Justin --- Looking at AsciiFilterPrivate::prepareDeviceToRead, the column names are always taken to be the first row of the file rather than the last row of the header. Would the latter behavior make more sense? It fits my uses better but I don't know if there was a reason behind why it was implemented this way. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392118] New: unhandled amd64-linux syscall: 332 [KDE executables]
https://bugs.kde.org/show_bug.cgi?id=392118 Bug ID: 392118 Summary: unhandled amd64-linux syscall: 332 [KDE executables] Product: valgrind Version: 3.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: kjs...@gmail.com Target Milestone: --- I get an unhandled amd64-linux syscall 332 warning when I run valgrind on a KDE program. For example, all of the commands below result in the warning: valgrind /bin/konsole valgrind /bin/dolphin valgrind /bin/kwrite valgrind /bin/okular more output: $ valgrind /bin/konsole ==13964== Memcheck, a memory error detector ==13964== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==13964== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==13964== Command: /bin/konsole ==13964== --13964-- WARNING: unhandled amd64-linux syscall: 332 --13964-- You may be able to write your own handler. --13964-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --13964-- Nevertheless we consider this a bug. Please report --13964-- it at http://valgrind.org/support/bug_reports.html. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392118] unhandled amd64-linux syscall: 332 [KDE executables]
https://bugs.kde.org/show_bug.cgi?id=392118 Kevin changed: What|Removed |Added CC||kjs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] New: Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's alre
https://bugs.kde.org/show_bug.cgi?id=392117 Bug ID: 392117 Summary: Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already loaded Product: plasma-pa Version: 5.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: --- The PulseAudio switch-on-connect module can only be loaded once in PulseAudio <= 11, or else PulseAudio will crash (https://bugs.freedesktop.org/show_bug.cgi?id=95104). This PulseAudio bug was recently fixed in the upcoming PulseAudio 12 release (https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=f0dfddead3cf1ff7af4c9c09a8027fde26065003), but that's still unreleased and a long way off for many of our users. Plasma-pa has a checkbox for "Automatically switch all running streams when a new output becomes available" that loads the module when checked. But it does so unconditionally, without first checking to see if the module is already loaded. If the module is already loaded, checking this checkbox will crash PulseAudio 11 and earlier. This caused a downstream bug in Kubuntu for many users after the Ubuntu devs tried loading the switch-on-connect module by default to improve usability: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519 Likely for this reason, plasma-pa has the checkbox unchecked by default, to avoid crashing PulseAudio in any distros that enable the module by default. However, this means that by default, users don't get the generally desirable switch-on-connect behavior unless their distro loads the module by default--and even then, the users need to avoid touching the checkbox in plasma-pa or else they'll break PulseAudio on their systems. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392103] Enable switchOnConnect by default
https://bugs.kde.org/show_bug.cgi?id=392103 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392117 --- Comment #10 from Nate Graham --- OK, here's a bug report that describes the bug without proposing a solution: https://bugs.kde.org/show_bug.cgi?id=392117 In the process, I learned a lot about PulseAudio, so thanks for pushing me a bit. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392117] Checking "Automatically switch all running streams when a new output becomes available" unconditionally loads switch-on-connect module without looking to see if it's already l
https://bugs.kde.org/show_bug.cgi?id=392117 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392103 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392028] Incomplete refresh of selected are in menus
https://bugs.kde.org/show_bug.cgi?id=392028 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-67199 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392033] SIGABORT opening file dialogue to add second include directory path [crash in concatPaths]
https://bugs.kde.org/show_bug.cgi?id=392033
--- Comment #3 from red...@cox.net ---
(In reply to Kai Uwe Broulik from comment #2)
> I can't reproduce your issue but it hits the following assert:
>
> QString concatPaths(const QString &path1, const QString &path2)
> {
> Q_ASSERT(!path2.startsWith(QLatin1Char('/')));
The source/project path is /home//projects/llvm, not familiar with this
code so I'm not sure what path2 is supposed to be. I did notice that my other
project did not have this problem though so I'm not surprised you could not
reproduce it. When I have the time I will try to find out where the bad string
is coming from.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #34 from Nate Graham --- Thanks David! What's the bug tracking #2? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #33 from David Edmundson --- 1) We need to depend on Qt 5.11, which is going to be ~Plamsa 5.14 2) blur rects in KwindowSystem. 3) testing, as no-one has mentioned 2 yet! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392116] New: Layer tab doesn't give option to add/remove/etc. and shortcut keys don't assign correctly.
https://bugs.kde.org/show_bug.cgi?id=392116 Bug ID: 392116 Summary: Layer tab doesn't give option to add/remove/etc. and shortcut keys don't assign correctly. Product: krita Version: 3.3.3 Platform: MS Windows OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: cheesepuff...@yahoo.com Target Milestone: --- layer tab shows but none of the options that come with it are showing. The shortcut keys that allow me to add a layer aren't working either. Also, tabs won't detach or minimize. Please fix :^((( -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 346445] Crash on exit after opening GIF animation
https://bugs.kde.org/show_bug.cgi?id=346445 Huon changed: What|Removed |Added CC||h...@plonq.org --- Comment #16 from Huon --- I can't reproduce this in 17.12.3. Possibly fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 David Edmundson changed: What|Removed |Added Summary|plasmashell does not|plasmashell does not |respect |respect |QT_DEVICE_PIXEL_RATIO |QT_DEVICE_PIXEL_RATIO on X -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392050] Applications > Launch Feedback > Cursor: effect does not save when changed
https://bugs.kde.org/show_bug.cgi?id=392050 Eike Hein changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/8af970fd49f3ca3 ||3450cf3ccd81856694a0dc752 Resolution|--- |FIXED --- Comment #18 from Eike Hein --- Git commit 8af970fd49f3ca33450cf3ccd81856694a0dc752 by Eike Hein, on behalf of Scott Harvey. Committed on 21/03/2018 at 02:37. Pushed by hein into branch 'master'. KCM Launch Feedback not saving cursor settings Reviewers: #plasma, hein, davidedmundson, ngraham Reviewed By: #plasma, hein Subscribers: davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D11522 M +5-4kcms/launch/package/contents/ui/main.qml https://commits.kde.org/plasma-desktop/8af970fd49f3ca33450cf3ccd81856694a0dc752 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #32 from Nate Graham --- David, with your Qt fix that's landing in 5.11, what more will be needed to enable this behavior by default? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 392115] New: Crash while diagnosing another crash
https://bugs.kde.org/show_bug.cgi?id=392115 Bug ID: 392115 Summary: Crash while diagnosing another crash Product: drkonqi Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kamika...@web.de Target Milestone: --- Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f250563b440 (LWP 11529))] Thread 3 (Thread 0x7f24ea012700 (LWP 11535)): #0 0x7f2500c25179 in poll () from /lib64/libc.so.6 #1 0x7f24fcaca429 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f24fcaca53c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2501563a2b in QEventDispatcherGlib::processEvents (this=0x7f24e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f250150a95a in QEventLoop::exec (this=this@entry=0x7f24ea011d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2501331baa in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7f2502bdaa35 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2501336ba0 in QThreadPrivate::start (arg=0x7f2502e4ad60) at thread/qthread_unix.cpp:376 #8 0x7f24ff0c259b in start_thread () from /lib64/libpthread.so.0 #9 0x7f2500c2fa1f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f24f3618700 (LWP 11531)): #0 0x7f2500c25179 in poll () from /lib64/libc.so.6 #1 0x7f24fbd47387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f24fbd48faa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f24f65e50a9 in QXcbEventReader::run (this=0x5556dde481c0) at qxcbconnection.cpp:1370 #4 0x7f2501336ba0 in QThreadPrivate::start (arg=0x5556dde481c0) at thread/qthread_unix.cpp:376 #5 0x7f24ff0c259b in start_thread () from /lib64/libpthread.so.0 #6 0x7f2500c2fa1f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f250563b440 (LWP 11529)): [KCrash Handler] #6 BacktraceLine::type (this=) at /usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/parser/backtraceline.h:59 #7 GdbHighlighter::highlightBlock (this=this@entry=0x5556de4abdb0, text=...) at /usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/gdbhighlighter.cpp:80 #8 0x7f2501be79e8 in QSyntaxHighlighterPrivate::reformatBlock (this=this@entry=0x5556de38c720, block=...) at text/qsyntaxhighlighter.cpp:203 #9 0x7f2501be7b80 in QSyntaxHighlighterPrivate::reformatBlocks (this=0x5556de38c720, from=, charsRemoved=, charsAdded=15) at text/qsyntaxhighlighter.cpp:184 #10 0x7f250153a26a in QMetaObject::activate (sender=sender@entry=0x5556de08def0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc43e72590) at kernel/qobject.cpp:3766 #11 0x7f250153a977 in QMetaObject::activate (sender=sender@entry=0x5556de08def0, m=m@entry=0x7f2502115d00 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc43e72590) at kernel/qobject.cpp:3628 #12 0x7f2501e35bea in QTextDocument::contentsChange (this=this@entry=0x5556de08def0, _t1=, _t2=, _t3=) at .moc/moc_qtextdocument.cpp:383 #13 0x7f2501ba66a1 in QTextDocumentPrivate::finishEdit (this=0x5556de105a90) at text/qtextdocument_p.cpp:1217 #14 0x7f2501ba68dc in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1201 #15 0x7f2501bd2874 in QTextCursor::endEditBlock (this=this@entry=0x7ffc43e72638) at text/qtextcursor.cpp:2510 #16 0x7f250245f93c in QWidgetTextControlPrivate::append (this=0x5556de105930, text=..., format=format@entry=Qt::AutoText) at widgets/qwidgettextcontrol.cpp:3136 #17 0x7f250245f9ae in QWidgetTextControl::append (this=, text=...) at widgets/qwidgettextcontrol.cpp:3142 #18 0x7f250244a059 in QTextEdit::append (this=, text=...) at widgets/qtextedit.cpp:2624 #19 0x5556dc9a12e0 in BacktraceWidget::backtraceNewLine (this=, line=...) at /usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/backtracewidget.cpp:316 #20 0x7f250153a36c in QtPrivate::QSlotObjectBase::call (a=0x7ffc43e72800, r=0x5556de087c90, this=0x5556de08bd00) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #21 QMetaObject::activate (sender=sender@entry=0x5556ddf99e30, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc43e72800) at kernel/qobject.cpp:3749 #22 0x7f250153a977 in QMetaObject::activate (sender=sender@entry=0x5556ddf99e30, m=m@entry=0x5556dcc235c0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc43e72800) at kernel/qobject.cpp:3628 #23 0x5556dc9edde5 in BacktraceGenerator::newLine (this=this@entry=0x5556ddf99e30, _t1=...) at /usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/build/src/drkonqi_autogen/EWIEGA46WW/moc_backtracegenerator.cpp:201 #24 0x5556dc9a54da in BacktraceGenerator::slotReadInput (this=0x555
[neon] [Bug 392113] Poor quality thumbnail for Kdenlive
https://bugs.kde.org/show_bug.cgi?id=392113 --- Comment #2 from Scott Harvey --- (In reply to Nate Graham from comment #1) > So the bug is that Neon is inheriting Ubuntu 16.04's lousy icon for the > kdenlive package. This will be fixed automatically once Neon is re-based on > top of Ubuntu 18.04, but could be fixed in the current version; up to the > Neon packagers. Interesting. Thanks for the explanation. With just a month or so to go until Ubuntu 18.04, I won't blame anyone for not making this fix a priority. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 392114] New: No bug report address, can't report DrKonqi crashes
https://bugs.kde.org/show_bug.cgi?id=392114 Bug ID: 392114 Summary: No bug report address, can't report DrKonqi crashes Product: drkonqi Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kamika...@web.de Target Milestone: --- #344404 says it's fixed but I just had DrKonqi 5.12.3 crash and get the same error. openSUSE TW, lastest updates as of 21 March 2018. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 392107] KGet should be able to download Youtube videos
https://bugs.kde.org/show_bug.cgi?id=392107 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391997] Two redundant ways to open a folder in a new window from the context menu
https://bugs.kde.org/show_bug.cgi?id=391997 --- Comment #2 from Nate Graham --- Both of them do; each Dolphin window is its own process. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 392113] Poor quality thumbnail for Kdenlive
https://bugs.kde.org/show_bug.cgi?id=392113 Nate Graham changed: What|Removed |Added CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Assignee|aleix...@kde.org|neon-b...@kde.org Component|discover|Packages Dev Edition ||[unstable] Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Product|Discover|neon Version|5.12.3 |unspecified --- Comment #1 from Nate Graham --- The icon comes from Kdenlive itself, but can be modified by downstream packaging. The versions of Kdenlive available from the Flathub or Kdeapps flatpak repos both use a better icon, which comes from the app itself: https://cgit.kde.org/kdenlive.git/plain/data/icons/128-apps-kdenlive.png So the lousy icon you're seeing comes from Neon packaging, which is based on Ubuntu 16.04 packaging. In Kubuntu 17.04, I see the better icon, which means that it's already been fixed in later Ubuntu releases. So the bug is that Neon is inheriting Ubuntu 16.04's lousy icon for the kdenlive package. This will be fixed automatically once Neon is re-based on top of Ubuntu 18.04, but could be fixed in the current version; up to the Neon packagers. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391997] Two redundant ways to open a folder in a new window from the context menu
https://bugs.kde.org/show_bug.cgi?id=391997 --- Comment #1 from Christoph Feck --- But doesn't the latter spawn a new process? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 391547] KNotify seg fault when a KMyMoney notification is displayed
https://bugs.kde.org/show_bug.cgi?id=391547 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 335111 *** -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5
https://bugs.kde.org/show_bug.cgi?id=335111 Christoph Feck changed: What|Removed |Added CC||cont...@symbioxy.com --- Comment #114 from Christoph Feck --- *** Bug 391547 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392113] Poor quality thumbnail for Kdenlive
https://bugs.kde.org/show_bug.cgi?id=392113 Scott Harvey changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392113] New: Poor quality thumbnail for Kdenlive
https://bugs.kde.org/show_bug.cgi?id=392113 Bug ID: 392113 Summary: Poor quality thumbnail for Kdenlive Product: Discover Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bund...@gmail.com Target Milestone: --- Created attachment 111535 --> https://bugs.kde.org/attachment.cgi?id=111535&action=edit Kdenlive thumbnail Do we have any control over this? The icon/thumbnail for Kdenlive that's currently showing up in Discover is really poor quality. It looks like a pixelated enlargement of a too-small icon. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 392036] Discuss how to handle image navigation when tool is activated
https://bugs.kde.org/show_bug.cgi?id=392036
Huon changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/gwe
||nview/312ab20ca12f393e69032
||bc426942759401f2616
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Huon ---
Git commit 312ab20ca12f393e69032bc426942759401f2616 by Huon Imberger.
Committed on 21/03/2018 at 01:30.
Pushed by huoni into branch 'Applications/18.04'.
Fix crop tool not saving config when navigating away
Summary:
Tool settings are saved in `toolDeactivated`, which is only triggered
when the tool is exited gracefully (e.g. when clicking Crop or Cancel).
This patch calls `toolDeactivated` when the parent `RasterImageView`
object is destroyed, ensuring settings are saved even when navigating
away, e.g. to another image, or back to {nav Browse}.
Test Plan:
{nav Crop} tool > activate/deactivate {nav Advanced} > navigate to next
image > open {nav Crop} tool > ensure the {nav Advanced} state is saved.
Also navigate away by clicking {nav Browse}.
Ensure navigating without {nav Crop} active is unaffected.
Reviewers: #gwenview, rkflx
Reviewed By: #gwenview, rkflx
Differential Revision: https://phabricator.kde.org/D11535
M +3-0lib/documentview/rasterimageview.cpp
https://commits.kde.org/gwenview/312ab20ca12f393e69032bc426942759401f2616
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 392063] [PackageKit] Update Notifier didn't update after using Discover to perform updates
https://bugs.kde.org/show_bug.cgi?id=392063 Ashberian changed: What|Removed |Added CC||kdeb...@mail.com --- Comment #6 from Ashberian --- Exacly as described by Nate but on KDE Neon ( 5.12.3 ) : Update Notifier Plasmoid ( UNP from now on ) & Discover don't agree , even after updating everything through Discover, the UNP gets stuck with the same info permanently . But it gets even worse: ( Once again, on KDE Neon ) Since Plasma 5.12.x ( not 100%, i'd say this behavior started after the first update on 5.12.1 ) this UNP always claim there's updates avaliable, ( it always shows the little blue dot ) whether there really are updates or not, status won't change . Additional info: using KDE Neon on a daily basis since 5.10.X. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 111743] Color themes + optionally derive color options from current system palette
https://bugs.kde.org/show_bug.cgi?id=111743 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #11 from Michael D --- It would be *very* nice if it inherited the system color scheme as much as possible, or if there were at least two variants, a light and dark option. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 383850] Gwenview shows unreadable paths in Recent Folders
https://bugs.kde.org/show_bug.cgi?id=383850
Henrik Fehlauer changed:
What|Removed |Added
Version Fixed In||18.04.0
Latest Commit||https://commits.kde.org/gwe
||nview/b4e9e0fc238dde9027412
||5d47664fd0e04ca9f81
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #7 from Henrik Fehlauer ---
Git commit b4e9e0fc238dde90274125d47664fd0e04ca9f81 by Henrik Fehlauer.
Committed on 21/03/2018 at 01:03.
Pushed by rkflx into branch 'Applications/18.04'.
Prettify display of URLs in Recent Folders and Places
Summary:
Entries in the {nav Recent Folders} tab on the {nav Start Page}
contained superfluous information like `file://` for local folders and
the user's home directory, taking away valuable space and unnecessarily
eliding the text:
file:///home/user/Documents/
By abbreviating to `~` and omitting the protocol for local folders, the
entries can look much neater, making them faster to scan for users:
~/Documents/
The changes not only affect the {nav Recent Folders} tab, but also what
is displayed in the {nav Recent Files} tab and the hover overlays for
very long entries.
In addition, adding folders to the {nav Places} panel now uses the last
subfolder for naming the entry, bringing the behaviour in line with
Dolphin.
FIXED-IN: 18.04.0
Test Plan:
- Inspected {nav Recent Folders} and {nav Recent Files} on the {nav Start
Page}.
- In {nav Browse} mode, used {nav File > Add Folder to Places}.
- Tested that remote paths containing `~` are still intact.
Before:
{F5758862}
After:
{F5758864}
Reviewers: #gwenview, muhlenpfordt
Reviewed By: #gwenview, muhlenpfordt
Subscribers: ngraham, muhlenpfordt
Differential Revision: https://phabricator.kde.org/D11493
M +1-1app/browsemainpage.cpp
M +1-1app/startmainpage.cpp
M +10 -1lib/historymodel.cpp
M +7-1lib/recentfilesmodel.cpp
https://commits.kde.org/gwenview/b4e9e0fc238dde90274125d47664fd0e04ca9f81
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 383850] Gwenview shows unreadable paths in Recent Folders
https://bugs.kde.org/show_bug.cgi?id=383850
--- Comment #6 from Henrik Fehlauer ---
Git commit 79a537ee840c629ed59ae8542f1041991910c1a2 by Henrik Fehlauer.
Committed on 21/03/2018 at 01:02.
Pushed by rkflx into branch 'Applications/18.04'.
Prevent duplicate slashes in Recent Folders
Summary:
Sometimes the {nav Recent Folders} tab on the {nav Start Page} would
show directory entries with multiple `/` at the end. Clicking on those
folders works fine, but as the same folder could also be added without
two slashes, in some cases there were multiple entries for the same
location.
The duplicate slash is caused by a porting mistake in d760ced7cb5b,
which added `/` unconditionally while `KUrl::AddTrailingSlash` only
added `/` if there was none at the end. Performing this check manually
fixes the bug.
Note that the fix for Bug #312060 (differentiate between home and root
folder for remote hosts) and what was added in 7eb5472f6539 (no password
dialog right after startup) are still in effect as well, even after
porting away from `KUrl`.
As a side effect, visiting `/` does not result anymore in broken
{nav Recent Folder} entries (non-functional and showing an error icon).
KIO warnings are gone, too:
kf5.kio.core: Invalid URL: QUrl("")
Test Plan:
Open folder, {nav Go > Up}, switch to {nav Start Page} and notice how
now the added recent folder only has a single slash at the end. In
particular, there is only a single entry for this location after
navigating back and forth again.
Start `sshd`, `sftp://localhost` still shows home folder,
`sftp://localhost/` shows root dir. Killing `kiod` and restarting
Gwenview does not show a password prompt on the {nav Start Page}.
Visit `/`, switch back to {nav Start Page} and observe that the newly
added entry shows and works correctly.
Reviewers: #gwenview, muhlenpfordt
Reviewed By: #gwenview, muhlenpfordt
Subscribers: muhlenpfordt
Differential Revision: https://phabricator.kde.org/D11492
M +5-2app/gvcore.cpp
https://commits.kde.org/gwenview/79a537ee840c629ed59ae8542f1041991910c1a2
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 387650] unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 --- Comment #4 from Marcus Sundman --- The segfault stack dump is using kdenlive 18.03.70 and mlt 6.7.0 where these problems still occurs. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387650] unsharp is broken
https://bugs.kde.org/show_bug.cgi?id=387650 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi --- Comment #3 from Marcus Sundman --- Created attachment 111534 --> https://bugs.kde.org/attachment.cgi?id=111534&action=edit segfault stack dump -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 322488] Use a single timer to monitor directory changes
https://bugs.kde.org/show_bug.cgi?id=322488 --- Comment #3 from Christoph Feck --- Comment #0 says I used "powertop" to measure wakeups. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips
https://bugs.kde.org/show_bug.cgi?id=350948 Bob changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||arkon...@yahoo.com --- Comment #14 from Bob --- There seems to be a regression of this bug in v17 (17.12.0). I created a 1080p @ 29fps project into which I imported clips of 720p @ 59fps. Having created a lengthy edit, I then changed the project settings to 720p @ 59fps to match the clips. This caused all the edit in/out points to shift to completely different points in the clips. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357628] Emptying trash, from trash icon on desktop, causes Task Manager to disappear from all but 1 Desktop.
https://bugs.kde.org/show_bug.cgi?id=357628 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391722] Hqdn3d doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=391722 --- Comment #2 from Marcus Sundman --- Same problem with kdenlive 18.03.70 and mlt 6.7.0. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392050] Applications > Launch Feedback > Cursor: effect does not save when changed
https://bugs.kde.org/show_bug.cgi?id=392050 --- Comment #17 from Scott Harvey --- (In reply to Eike Hein from comment #8) > > Changes do take effect after logging out and back in. A simple restart of > > plasmashell isn't sufficient. > > That means KWin isn't watching launchrc for changes. I can retract this portion, now that klaunchrc is being updated. KWin appears to catch it and make a change. Although "blink" doesn't seem to blink - it's static instead, at least on my system. I *can* change from "none" to "bounce" and KWin correctly makes the change. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 392036] Discuss how to handle image navigation when tool is activated
https://bugs.kde.org/show_bug.cgi?id=392036 --- Comment #4 from Huon --- (In reply to Henrik Fehlauer from comment #3) > > currently Gwenview can only operate on one URL at a time) > Um, I did not mean it in such a complicated way ;) I was just thinking about > cropping one image at a time, and instead of having to reopen the crop tool > again it would simply stay open. Anyway, as we'll be able to remember the > last used crop setting after your patch, adding this is perhaps not strictly > necessary anymore… Reading back, indeed it doesn't necessitate batch editing. Thinking about this more, #2 will at least require #1 to be implemented, because switching images destroys the image view and any active tool along with it. That also means we'd have to save all config, not just the ratio. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned
https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #12 from IWBR --- I've been doing some tests to determine the exact nature of this behavior. Let's say that some tag was removed from a group of pictures, so it no longer exists. Digikam does not remove that tag from the Tag list (and the count number indicating how many pictures have it remains untouched). Only removing the picture collection from the database will bring that count to 0 (but the tag will still appear in the list). Upon adding the picture collection once more, and letting digikam scan for pictures, tags will be populated again. But even the deleted tag, that no picture has anymore, and it was empty in the database, will be populated once more and recover its previous count. Not even cleaning the database, even when there isn't a single collection, will get rid of these inexistent tags. Only manually deleting the empty tag will get rid of it, but that would require a previous knowledge of which tags have been modified (possibly by another user). So the only option that currently remains, in order to properly update the library, is deleting the whole database and start anew. I hope it helps... -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 392036] Discuss how to handle image navigation when tool is activated
https://bugs.kde.org/show_bug.cgi?id=392036 --- Comment #3 from Henrik Fehlauer --- > currently Gwenview can only operate on one URL at a time) Um, I did not mean it in such a complicated way ;) I was just thinking about cropping one image at a time, and instead of having to reopen the crop tool again it would simply stay open. Anyway, as we'll be able to remember the last used crop setting after your patch, adding this is perhaps not strictly necessary anymore… > I would prefer going with just #1 now Okay, makes sense to me. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 392036] Discuss how to handle image navigation when tool is activated
https://bugs.kde.org/show_bug.cgi?id=392036 --- Comment #2 from Huon --- (In reply to Henrik Fehlauer from comment #1) > (This was split off from a discussion while working on the crop tool, see > https://phabricator.kde.org/D11378#229012.) > > Not yet sure what's best, but here are more thoughts: "Navigate away" is not > only about pressing the previous/next buttons, but also concerns switching > to Browse mode, using another tool like "Red Eye Reduction" (although using > tools like rotating while cropping is quite handy) or quitting Gwenview. > > I imagine it would get annoying if in any of these cases we would show a > warning message. Also, some users might not notice there is a Cancel button > they now have to press, so they would be stuck. > > Perhaps solution #1 is the best indeed? Or combine #1 and #3? (But once #1 > is solved, the #3 workaround is probably not needed anymore.) > > I think you are right about #2, which would go more in the direction of > batch editing. Nevertheless, #2 is a nice idea, maybe this could be added as > an option in Gwenview's settings dialog, because currently for cropping lots > of images you have to open the crop tool again and again. Of course for > regular users it should default to "off". #1 is an easy fix. #2 would require implementing batch editing support (currently Gwenview can only operate on one URL at a time). #3 as you say, is less necessary if we go with #1. I would prefer going with just #1 now, then considering #2. #3 could annoy some users? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357628] Emptying trash, from trash icon on desktop, causes Task Manager to disappear from all but 1 Desktop.
https://bugs.kde.org/show_bug.cgi?id=357628 --- Comment #21 from ryan_s...@yahoo.com --- This bug has been fixed. My Task Manager bar no longer disappears. Thank you for fixing it. -- You are receiving this mail because: You are watching all bug changes.
[kwebkitpart] [Bug 382641] Build kwebkitpart as module
https://bugs.kde.org/show_bug.cgi?id=382641 --- Comment #1 from Yaakov Selkowitz --- Updated patch: https://github.com/cygwinports/kwebkitpart/blob/9230a67b26b673808faf837d50a71bfd5423c50e/1.3-cmake-module.patch -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391352] Trim margins breaks mouse wheel zoom out
https://bugs.kde.org/show_bug.cgi?id=391352 Nate Graham changed: What|Removed |Added CC||n...@kde.org Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 392106] opening (e)PS files from the commandline
https://bugs.kde.org/show_bug.cgi?id=392106 RJVB changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from RJVB --- No error, just a white page. I just see that the file that fails is actually a pdf file that somehow got the eps extension. That's not a problem for ghostscript when left to its own, but probably explains why the backend fails. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391352] Trim margins breaks mouse wheel zoom out
https://bugs.kde.org/show_bug.cgi?id=391352 Albert Astals Cid changed: What|Removed |Added CC||t.soer...@gmail.com --- Comment #14 from Albert Astals Cid --- *** Bug 391894 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391894] Zoom out doesn't work when zoom is Fit Width
https://bugs.kde.org/show_bug.cgi?id=391894 Albert Astals Cid changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #15 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 391352 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391894] Zoom out doesn't work when zoom is Fit Width
https://bugs.kde.org/show_bug.cgi?id=391894 --- Comment #14 from t.soer...@gmail.com --- Yes, disabling it fixes the zoom out. I thought setting defaults in options would have removed any options I had set. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 388265] Repaint issues with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=388265 Dr. Chapatin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Dr. Chapatin --- qt bug https://bugreports.qt.io/browse/QTBUG-67199 *** This bug has been marked as a duplicate of bug 392028 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392028] Incomplete refresh of selected are in menus
https://bugs.kde.org/show_bug.cgi?id=392028 --- Comment #9 from Dr. Chapatin --- *** Bug 388265 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392028] Incomplete refresh of selected are in menus
https://bugs.kde.org/show_bug.cgi?id=392028 --- Comment #8 from Dr. Chapatin --- No problem, Luca. Reported here https://bugreports.qt.io/browse/QTBUG-67199 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391897] lldb debugger "setting set takes more arguments"
https://bugs.kde.org/show_bug.cgi?id=391897 --- Comment #2 from joonato...@gmail.com --- (In reply to Aetf from comment #1) > This is only a warning and doesn't cause any problem with actual debugging. > Anyway, fix posted to https://phabricator.kde.org/D11524 > > BTW, newly created project uses empty CMAKE_BUILD_TYPE by default, so the > built binary doesn't include debug symbols. That's why the debugger seems > not working. > > Try reconfigure cmake in project settings by setting CMAKE_BUILD_TYPE to > Debug and rebuild, then the debugger will work correctly. Doesn't look like the project is running at all? It needs to be stopped manually, and no output appears in the konsole tab. `file` shows `test123: ELF 64-bit [...], with debug_info, not stripped`, and debugging manually with `lldb` seems to work just fine? Am I just missing something? -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 392112] Deleted physical tables still visible in project navigator
https://bugs.kde.org/show_bug.cgi?id=392112 Jarosław Staniek changed: What|Removed |Added Target Milestone|3.1.1 |3.2 Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 392112] Deleted physical tables still visible in project navigator
https://bugs.kde.org/show_bug.cgi?id=392112 Jarosław Staniek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Target Milestone|--- |3.1.1 --- Comment #1 from Jarosław Staniek --- Possible solution at KDb level: on first call to KDbConnection::tableNames() obtain list of physical tables and compare with tables from kexi__objects metadata. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391894] Zoom out doesn't work when zoom is Fit Width
https://bugs.kde.org/show_bug.cgi?id=391894 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #13 from Albert Astals Cid --- Do you have trim margins enabled in the view menu? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 392106] opening (e)PS files from the commandline
https://bugs.kde.org/show_bug.cgi?id=392106 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Albert Astals Cid --- okular opens ps and eps files just fine from the command line. Which error do you get? -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 392112] New: Deleted physical tables still visible in project navigator
https://bugs.kde.org/show_bug.cgi?id=392112 Bug ID: 392112 Summary: Deleted physical tables still visible in project navigator Product: KEXI Version: 3.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tables Assignee: kexi-b...@kde.org Reporter: stan...@kde.org CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Deleted physical table is still visible in project navigator. To reproduce (example for sqlite3): 1. Create a new table in a KEXI project, save and close the project. 2. Delete the table in low-level tool such as sqlite3 or sqlite browser 3. Re-open the project in KEXI Actual result: table entry is visible and empty grid is opened on click, queries based on the table can be designed and raise error "table not found" in data view Expected: the table entry is no longer visible in the navigator. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth
https://bugs.kde.org/show_bug.cgi?id=391127 --- Comment #9 from Christoph Roick --- @Kevin: I'm not fully convinced. One problem is, that SSH_ASKPASS is ignored if a terminal is set [1]. So one would have to trick ssh into believing that there is no terminal; which is explained in [1]. Interestingly ssh-askpass is not part of my system (probably due to relying on the environment variable). That's where the idea of making KDevelop itself some kind of default askpass program was coming from. Nevertheless, setting the environment variable to some default value would surely be a start. [1] https://unix.stackexchange.com/a/272524 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392103] Enable switchOnConnect by default
https://bugs.kde.org/show_bug.cgi?id=392103 David Edmundson changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #9 from David Edmundson --- >But maybe that's because the internal speakers and headphones are both Yes. Which is also why it's not a bug that it doesn't auto switch back. The sound card of my laptop doesn't get added when I plug something into the jack. I don't like bug reports in the form of proposing a solution rather than in the form of a bug so I'm closing this. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392028] Incomplete refresh of selected are in menus
https://bugs.kde.org/show_bug.cgi?id=392028 --- Comment #7 from Luca Carlon --- Unfortunately I don't know anything about the code in Breeze, it would be pretty difficult for me to report a bug to Qt about something I don't know. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362715] Imap constant refresh of IMAP directory
https://bugs.kde.org/show_bug.cgi?id=362715 CnZhx changed: What|Removed |Added CC||z...@cnzhx.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370245] Be able to rename tags which have been setted in pictures
https://bugs.kde.org/show_bug.cgi?id=370245 --- Comment #11 from IWBR --- As I accidentally submitted a duplicated bug that was closed, I repeat the comment that I left in the other one (bug #392109): The reasoning behind not saving these specific changes to the metadata is because of the possible large amount of elements that could be affected. But the same applies to removing or adding a new tag, which are indeed saved immediately to metadata. It should be user's choice if it's worth saving those changes to the pictures (as it is asked during the first run), regardless of the time that it might take. If the option to write metadata to files is checked, it should be written. If it's not, only digikam's metadata should be changed. The current state is inconsistent, and because of that I just realized that many changes have not actually been applied to my library. A fair compromise would be showing a confirmation dialog before the change: "This change will affect ### pictures in your library, are you sure you want to continue?". (this is actually what happens in picasa if you try to write over more than 50 or 100 pictures at a time, if I recall correctly). Thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391683] Brightness 100% after screen locking
https://bugs.kde.org/show_bug.cgi?id=391683 --- Comment #6 from Yves Glodt --- Any brightness higher than the minimum value is too bright for me, that's why I set it to minimum. I just tried setting the slider one step higher than the minimum and so far the unwanted change to full brightness did not happen. p.s. I have two laptops. On one (running Fedora 27), the minimum value (slider full to the left) for brightness results in "medium bright", and on the other one (Fedora 28), it results in a black laptop screen. The external screen is not influenced by the slider in the plasma planel. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392109] Renamed tags are not written to metadata
https://bugs.kde.org/show_bug.cgi?id=392109 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com --- Comment #3 from IWBR --- But the same applies with removing or adding a new tag. It's the user's choice if it's worth saving those changes to the pictures, with the time that it might take. If the option to write metadata to files is checked, it should be written. If it's not, only digikam's metadata should be changed. The current state is inconsistent, and because of that I just realized that many changes have not actually been applied to my library. A fair compromise would be showing a confirmation dialog before the change: "This change will affect ### pictures in your library, are you sure you want to continue?". (this is actually what happens in picasa if you try to write over more than 50 or 100 pictures at a time, if I recall correctly). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392111] Kwin crashes when displaying overview repeatedly
https://bugs.kde.org/show_bug.cgi?id=392111 --- Comment #2 from Edward Oubrayrie --- Also, I can reproduce by frenetically moving mouse around top-left corner for some time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392109] Renamed tags are not written to metadata
https://bugs.kde.org/show_bug.cgi?id=392109 --- Comment #2 from Maik Qualmann --- Thousands of images could be affected when renaming a tag. This would take a long time. It is possible to use the maintenance tool to select only the new tag and have all metadata written. Or select the tag in the left sidebar, select all images and write the metadata in the images. An automatic update may be time critical. Maik -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 392077] Import data headers treat spaces as tab delimiter
https://bugs.kde.org/show_bug.cgi?id=392077 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392111] Kwin crashes when displaying overview repeatedly
https://bugs.kde.org/show_bug.cgi?id=392111 --- Comment #1 from Edward Oubrayrie --- Glad to see Drkonqi now works in fedora :) qdbus org.kde.KWin /KWin supportInformation: https://paste.kde.org/pkg8mrjic/fplgla -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392111] New: Kwin crashes when displaying overview repeatedly
https://bugs.kde.org/show_bug.cgi?id=392111 Bug ID: 392111 Summary: Kwin crashes when displaying overview repeatedly Product: kwin Version: 5.12.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: edoubray...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.3) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.16.0-0.rc5.git0.2.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: hit the top-left corner multiple times. looks like a race condition. - Custom settings of the application: kwin_x11, kwin-5.12.3-2.fc28.x86_64 (fedora beta) The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90b1412940 (LWP 20710))] Thread 5 (Thread 0x7f90790dc700 (LWP 20749)): #0 0x7f90a77dda46 in ppoll () at /lib64/libc.so.6 #1 0x7f90a86a5e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f90a86a7159 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f90a865812b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f90a84a69c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f90af60d489 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f90a84ab11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f90aa92a564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f90a77e833f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9067fff700 (LWP 20722)): #0 0x7f90aa9304fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90b06829f8 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f90b0682a63 in () at /lib64/libQt5Script.so.5 #3 0x7f90aa92a564 in start_thread () at /lib64/libpthread.so.0 #4 0x7f90a77e833f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f907b7cb700 (LWP 20719)): #0 0x7f90a77dda46 in ppoll () at /lib64/libc.so.6 #1 0x7f90a86a5e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f90a86a7159 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f90a865812b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f90a84a69c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f90af60d489 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f90a84ab11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f90aa92a564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f90a77e833f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f908a22b700 (LWP 20715)): #0 0x7f90a77dda46 in ppoll () at /lib64/libc.so.6 #1 0x7f90a86a5e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f90a86a7159 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f90a865812b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f90a84a69c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f90b14d2299 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #6 0x7f90a84ab11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f90aa92a564 in start_thread () at /lib64/libpthread.so.0 #8 0x7f90a77e833f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f90b1412940 (LWP 20710)): [KCrash Handler] #6 0x7f90b0defefc in QVector::contains(int const&) const [clone .isra.139] () at /lib64/libkwin.so.5 #7 0x7f90b0df4016 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /lib64/libkwin.so.5 #8 0x7f90a8656c2c in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /lib64/libQt5Core.so.5 #9 0x7f908c99ac84 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /lib64/libQt5XcbQpa.so.5 #10 0x7f908c99b843 in QXcbConnection::processXcbEvents() () at /lib64/libQt5XcbQpa.so.5 #11 0x7f90a8682a26 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f90a8f20e95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f90a8f2883a in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f90a8659376 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #15 0x7f90a865c09b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #16 0x7f90a86a6fcf in QEventDispatcherUN
[digikam] [Bug 392109] Renamed tags are not written to metadata
https://bugs.kde.org/show_bug.cgi?id=392109 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||metzping...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 370245 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370245] Be able to rename tags which have been setted in pictures
https://bugs.kde.org/show_bug.cgi?id=370245 --- Comment #10 from Maik Qualmann --- *** Bug 392109 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362647] Can't search with Chinese characters
https://bugs.kde.org/show_bug.cgi?id=362647
Stefan Brüns changed:
What|Removed |Added
CC||stefan.bruens@rwth-aachen.d
||e
--- Comment #7 from Stefan Brüns ---
I think a good start would be to create a database of testcases, so even a
developer not proficient in a specific script can test and improve the
coverage.
One possible format could be:
# description of the testcase
! filename_1234.png
+ filename ;; match filename
+ png ;; match png
+ 1234 ;; match 1234
- file ;; do not match file
+ file* ;; match with wildcard
# chinese testcase 1: match 測試 ("test")
! 測試testcase.txt
+ 測試
+ testcase
+ txt
;- 試測 ;; expected to fail, requires dictionary
+ 測試 txt
Testcases should probably be split into one file per language (combination).
Correct handling of languages like chinese - where words are not separated -
is hard, and requires a dictionary as far as I understand. The best one can do
currently is to split at a grapheme level. This would likely create a lot of
false positives when searching, but false positives are IMHO better than no
results at all.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 392110] New: Missing 2 .h files in /usr/include/kmymoney
https://bugs.kde.org/show_bug.cgi?id=392110 Bug ID: 392110 Summary: Missing 2 .h files in /usr/include/kmymoney Product: kmymoney Version: 5.0.1 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-de...@kde.org Reporter: larsson...@gmail.com Target Milestone: --- Created attachment 111533 --> https://bugs.kde.org/attachment.cgi?id=111533&action=edit Patch that adds the two missing .h files Two .h files is missing in /usr/include/kmymoney Added a patch that fixes the problem The missing files is: kmymoneysettings.h mymoneyenums.h Regards Thorbjorn -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392109] New: Renamed tags are not written to metadata
https://bugs.kde.org/show_bug.cgi?id=392109 Bug ID: 392109 Summary: Renamed tags are not written to metadata Product: digikam Version: 5.9.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- I noticed that if you rename a tag, changes appear in digikam but are not written to metadata, even when the option to write to files is checked in the configuration menu. Manually using the "Write information to metadata" in the main menu is currently required. This contrasts to other changes, like adding and removing tags, which are written successfully to pictures' metadata immediately. PS: it is possible that changing a tag hierarchy is also affected by this bug, since technically it's a form of renaming. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392103] Enable switchOnConnect by default
https://bugs.kde.org/show_bug.cgi?id=392103 --- Comment #8 from David Rosca --- > That seems like another bug that needs fixing, then. I don't have hardware > that can replicate that setup; could you file a bug for the issue if you > still do? What bug? That's a behavior of pulseaudio itself and I don't really see any issue with it. Both modules (switch-on-connect and device-manager) are trying to do the same thing (automatic routing of streams), so it makes sense that they conflict with each other. Audio/Video KCM interacts directly with the module-device-manager, so it is also expected to not be working when you unload this module from pulseaudio. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391667] Security bug
https://bugs.kde.org/show_bug.cgi?id=391667 paalsteek changed: What|Removed |Added CC||k...@paalsteek.de --- Comment #6 from paalsteek --- I would like to look into this issue (step...@stephan-platz.de, FBA2C336A60037576EAEC5C72BB88734955D8A24) -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 356784] baloo-widgets-15.12.0 fails its extractortest
https://bugs.kde.org/show_bug.cgi?id=356784 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Julian Schraner --- The test passes for me with baloo-widgets-17.12.3. I'll close this bug, if extractortest still fails for you then please reopen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392052] No way to launch Kwin Scripting console from command-line
https://bugs.kde.org/show_bug.cgi?id=392052 --- Comment #3 from Edward Oubrayrie --- Wiki updated. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389508] Dates Side Menu Is Not Updated Automatically After Exif Date Change [patch]
https://bugs.kde.org/show_bug.cgi?id=389508 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0 Latest Commit||https://commits.kde.org/dig ||ikam/537bca8473d58c28e26d4a ||8d83af6c2afc8fd073 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Maik Qualmann --- Git commit 537bca8473d58c28e26d4a8d83af6c2afc8fd073 by Maik Qualmann. Committed on 20/03/2018 at 19:37. Pushed by mqualmann into branch 'master'. add signal/slot from the image attribute watcher to date album update timer FIXED-IN: 6.0.0 M +2-3NEWS M +6-1core/libs/album/albummanager.cpp https://commits.kde.org/digikam/537bca8473d58c28e26d4a8d83af6c2afc8fd073 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392108] QML Failed to get image from provider
https://bugs.kde.org/show_bug.cgi?id=392108 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org Resolution|--- |UPSTREAM --- Comment #1 from Boudewijn Rempt --- Hi Aleksey, That's not a bug in krita. It's a warning, and it's annoying noise, but actually, the touch docker loads the images fine... I have no idea why Qt complains about those images -- if it's a bug, it's a bug in Qt. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392108] New: QML Failed to get image from provider
https://bugs.kde.org/show_bug.cgi?id=392108 Bug ID: 392108 Summary: QML Failed to get image from provider Product: krita Version: 4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: samoilov@gmail.com Target Milestone: --- Debian 9, Qt 5.7.1. Terminal output: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/opacity-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/opacity-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/lightness-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/lightness-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/zoom-in file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotate-canvas-left file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotation-reset file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotate-canvas-right file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/zoom-out file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/brushsize-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/brushsize-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/preset-switcher file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/edit-clear -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] GTKHeaderBar is dark when nothing else in Breeze theme is
https://bugs.kde.org/show_bug.cgi?id=392104 --- Comment #3 from Mike H --- Created attachment 111532 --> https://bugs.kde.org/attachment.cgi?id=111532&action=edit Same test-case with Adwaita theme; notice, its brighter -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392102] kmail close when resend an email
https://bugs.kde.org/show_bug.cgi?id=392102 --- Comment #2 from Jorge --- Version 5.7.3 Sometimes it is fixed by restarting the computer 2018-03-20 9:34 GMT-06:00 Laurent Montel : > https://bugs.kde.org/show_bug.cgi?id=392102 > > Laurent Montel changed: > >What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Backtrace please > kmail version please > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387611] Multitouch rotate, zoom-less pan
https://bugs.kde.org/show_bug.cgi?id=387611 Karen changed: What|Removed |Added CC||guru...@yandex.ru --- Comment #1 from Karen --- Please add rotation to multitouch support. Please support zoomless pan - to pan with multitouch requires two fingers. To pan without zooming requires those fingers to maintain a constant distance. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 306745] scrolling past document reverts back to the end of the document when you type
https://bugs.kde.org/show_bug.cgi?id=306745 Dominik Haumann changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #8 from Dominik Haumann --- Unfortunately, this change introduced a regression, therefore reopening. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 391838] window doesn't scroll when cursor traverses dynamically-wrapped line
https://bugs.kde.org/show_bug.cgi?id=391838 Dominik Haumann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kte ||xteditor/e75bde233b9fe6b1a7 ||d24cc63fa9baf9e89de895 Version Fixed In||5.45 Status|CONFIRMED |RESOLVED --- Comment #3 from Dominik Haumann --- Git commit e75bde233b9fe6b1a7d24cc63fa9baf9e89de895 by Dominik Haumann. Committed on 20/03/2018 at 18:51. Pushed by dhaumann into branch 'master'. Revert Fix: View jumps when Scroll past end of document is enabled Unfortunately, this introduced a regression that scrolling down in dynamically wrapped lines did not move the view at all. We need to find a better fix, and introduce a unit test. Related: bug 306745 FIXED-IN: 5.45 M +2-0autotests/src/kateview_test.cpp M +1-1src/view/kateviewinternal.cpp https://commits.kde.org/ktexteditor/e75bde233b9fe6b1a7d24cc63fa9baf9e89de895 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 306745] scrolling past document reverts back to the end of the document when you type
https://bugs.kde.org/show_bug.cgi?id=306745 --- Comment #7 from Dominik Haumann --- Git commit e75bde233b9fe6b1a7d24cc63fa9baf9e89de895 by Dominik Haumann. Committed on 20/03/2018 at 18:51. Pushed by dhaumann into branch 'master'. Revert Fix: View jumps when Scroll past end of document is enabled Unfortunately, this introduced a regression that scrolling down in dynamically wrapped lines did not move the view at all. We need to find a better fix, and introduce a unit test. Related: bug 391838 FIXED-IN: 5.45 M +2-0autotests/src/kateview_test.cpp M +1-1src/view/kateviewinternal.cpp https://commits.kde.org/ktexteditor/e75bde233b9fe6b1a7d24cc63fa9baf9e89de895 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391897] lldb debugger "setting set takes more arguments"
https://bugs.kde.org/show_bug.cgi?id=391897 Aetf <7437...@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Aetf <7437...@gmail.com> --- This is only a warning and doesn't cause any problem with actual debugging. Anyway, fix posted to https://phabricator.kde.org/D11524 BTW, newly created project uses empty CMAKE_BUILD_TYPE by default, so the built binary doesn't include debug symbols. That's why the debugger seems not working. Try reconfigure cmake in project settings by setting CMAKE_BUILD_TYPE to Debug and rebuild, then the debugger will work correctly. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 358516] KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0).
https://bugs.kde.org/show_bug.cgi?id=358516 Daniel Lin changed: What|Removed |Added CC||ephemi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362647] Can't search with Chinese characters
https://bugs.kde.org/show_bug.cgi?id=362647 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 347302] reassign name to face
https://bugs.kde.org/show_bug.cgi?id=347302 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 392103] Enable switchOnConnect by default
https://bugs.kde.org/show_bug.cgi?id=392103 --- Comment #7 from Nate Graham --- That seems like another bug that needs fixing, then. I don't have hardware that can replicate that setup; could you file a bug for the issue if you still do? I'll mention that the use case of plugging headphones into my laptop and having the audio automatically transferred there works fine for me, even without this setting turned on. But maybe that's because the internal speakers and headphones are both on the same device? -- You are receiving this mail because: You are watching all bug changes.
