[frameworks-baloo] [Bug 465801] Near-constant crashes in ext_idle_notifier_v1_destroy on Wayland
https://bugs.kde.org/show_bug.cgi?id=465801 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 171460] [PATCH] FindKipi, FindKdcraw, FindKexiv2 cmake modules ignore correct pkgconfig lib paths and return incorrect ones.
https://bugs.kde.org/show_bug.cgi?id=171460 Matěj Laitl changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #7 from Matěj Laitl --- Right, this has been reported for a very old version. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 431738] Amarok sometimes crashes when searching in Collection Browser
https://bugs.kde.org/show_bug.cgi?id=431738 Matěj Laitl changed: What|Removed |Added Version|unspecified |kf5 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 431738] New: Amarok sometimes crashes when searching in Collection Browser
https://bugs.kde.org/show_bug.cgi?id=431738 Bug ID: 431738 Summary: Amarok sometimes crashes when searching in Collection Browser Product: amarok Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: ma...@laitl.cz Target Milestone: kf5 Application: amarok (2.9.70) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.10.4-gentoo x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Searching Collection Browser. Amarok based on Qt5 / KDE Frameworks 5 compiled from sources. Git commit 0e15bdf35d from Dec 30, 2020. I want to eventually look into fixing this, but wanted to have a record for this in issue tracker. The crash can be reproduced sometimes. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x in () #7 0x7f55d2aec8b2 in Collections::SqlQueryMaker::abortQuery() (this=this@entry=0x562f340142e0) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/core-impl/collections/db/sql/SqlQueryMaker.cpp:172 #8 0x7f55d2af23da in Collections::SqlQueryMaker::~SqlQueryMaker() (this=0x562f340142e0, __in_chrg=) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/core-impl/collections/db/sql/SqlQueryMaker.cpp:159 #9 0x7f55d2af2609 in Collections::SqlQueryMaker::~SqlQueryMaker() (this=0x562f340142e0, __in_chrg=) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/core-impl/collections/db/sql/SqlQueryMaker.cpp:165 #10 0x7f55ebcabc7f in QObject::event(QEvent*) (this=0x562f340142e0, e=0x562f35228770) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:1301 #11 0x7f55ec6d4d8f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x562f33c307b0, receiver=receiver@entry=0x562f340142e0, e=e@entry=0x562f35228770) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632 #12 0x7f55ec6dda40 in QApplication::notify(QObject*, QEvent*) (this=0x7ffc504580b0, receiver=0x562f340142e0, e=0x562f35228770) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3156 #13 0x7f55ebc80497 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562f340142e0, event=0x562f35228770) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063 #14 0x7f55ebc82fc0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x562f33bba8f0) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1817 #15 0x7f55ebcd5df3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x562f33c93f50) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #16 0x7f55e7145887 in g_main_dispatch (context=0x7f55dc005000) at ../glib-2.64.5/glib/gmain.c:3309 #17 g_main_context_dispatch (context=context@entry=0x7f55dc005000) at ../glib-2.64.5/glib/gmain.c:3974 #18 0x7f55e7145b10 in g_main_context_iterate (context=context@entry=0x7f55dc005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.64.5/glib/gmain.c:4047 #19 0x7f55e7145b9f in g_main_context_iteration (context=0x7f55dc005000, may_block=may_block@entry=1) at ../glib-2.64.5/glib/gmain.c:4108 #20 0x7f55ebcd5b9d in QEventDispatcherGlib::processEvents(QFlags) (this=0x562f33ca5730, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #21 0x7f55ebc7f2c3 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffc50457f60, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f55ebc87220 in QCoreApplication::exec() () at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x562f32666764 in main(int, char**) (argc=, argv=) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/main.cpp:391 [Inferior 1 (process 1417290) detached] Possible duplicates by query: bug 431077, bug 430722, bug 430698, bug 429973, bug 429643. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 312639] Creating KUrl( QString::fromUtf8( "places://Kořen" ) ) asserts with debugging Qt, QUrl does not
https://bugs.kde.org/show_bug.cgi?id=312639
Matěj Laitl changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #3 from Matěj Laitl ---
I can confirm that this is fixed, or at least no longer reproducible with
KDE Frameworks 5.74
Qt 5.15.1
I've compiled a slightly modified test executable: [main.cpp]
#include
#include
#include
int main(void) {
std::cout << "QLibraryInfo::isDebugBuild(): " <<
QLibraryInfo::isDebugBuild() << std::endl;
volatile QUrl qurl( QString::fromUtf8( "places://Kořen" ) ); // okay
volatile KUrl kurl( QString::fromUtf8( "places://Kořen" ) ); // crashes
here
return 0;
}
...with the following command:
g++ main.cpp -I /usr/include/KF5/KDELibs4Support/KDE -I
/usr/include/KF5/KDELibs4Support -I /usr/include/qt5/QtCore -I /usr/include/qt5
-fPIC -l Qt5Core
...and it gives:
$ ./a.out
QLibraryInfo::isDebugBuild(): 1
$ echo $?
0
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 427877] Tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877 --- Comment #5 from Matěj Laitl --- (In reply to Christoph Feck from comment #4) > Matěj, can you confirm this issue is fixed? Sure, it works like a charm here in Plasma 5.20.2. ;-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427877] Tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877 --- Comment #2 from Matěj Laitl --- Hi, I can confirm than after building plasma-workspace patched with https://github.com/KDE/plasma-workspace/commit/f0764d87fe5275a123cdf6dca1ab3d0399c97578?branch=f0764d87fe5275a123cdf6dca1ab3d0399c97578=split and re-logging, gitk now starts just fine. Cool! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427877] New: tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877
Bug ID: 427877
Summary: tk apps fail to start with unknown color name
"BACKGROUND" after upgrading to Plasma 5.20
Product: systemsettings
Version: 5.20.0
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: krdb
Assignee: kdelibs-b...@kde.org
Reporter: ma...@laitl.cz
Target Milestone: ---
Created attachment 132487
--> https://bugs.kde.org/attachment.cgi?id=132487=edit
xrdb -query output. Are colour definitions missing?
STEPS TO REPRODUCE
1. Use plasma-desktop 5.20 on Linux
2. Try to start a Tk based gui application, like gitk
OBSERVED RESULT
Fails to start with the following in the console:
```
$ gitk
application-specific initialization failed: unknown color name "BACKGROUND"
Error in startup script: unknown color name "BACKGROUND"
(database entry for "-background" in widget ".")
invoked from within
"load /usr/lib64/libtk8.6.so Tk"
("package ifneeded Tk 8.6.8" script)
invoked from within
"package require Tk"
(file "/usr/bin/gitk" line 10)
```
EXPECTED RESULT
Tk apps start normally. This was the case with Plasma 5.19.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux (X11)
KDE Plasma Version: 5.20.0
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
ADDITIONAL INFORMATION
This has the same symptoms as one old issue reported to Red Hat Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1043686
This has been patched by Red Hat somehow, but I was unable to find the exact
patch.
The problem seems to stem from krdb trying to update xrdb so that colours of
non-KDE apps match ones set in KDE settings as mentioned in
https://github.com/KDE/plasma-workspace/blob/master/kcms/krdb/ad/README
I'm adding output of `xrdb -query`.
One work-around mentioned on the Red Had bugzilla was to disable `Apply colors
to non-KDE4 applications` in System Settings -> Application Appearance ->
Colors -> Options - but I was unable to find this setting in Plasma 5.20.
Another harsher work-around is to reset xrdb with `xrdb -load /dev/null` - but
that has unwanted side-effects.
This seems to be happening to multiple people with Plasma 5.20, e.g.
https://www.reddit.com/r/kdeneon/comments/jckwxk/help_cant_run_gitk_on_kde_520/
Reading https://stackoverflow.com/questions/25357156/gitk-package-require-tk
(which is not directly related to the bug), it seems that krdb should put
entries like:
`#define BACKGROUND#b58900`
into xrdb, but it may not be doing so properly (just guessing)
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 427877] Tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877 Matěj Laitl changed: What|Removed |Added Summary|tk apps fail to start with |Tk apps fail to start with |unknown color name |unknown color name |"BACKGROUND" after |"BACKGROUND" after |upgrading to Plasma 5.20|upgrading to Plasma 5.20 CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398439] "Windows can cover" panel does not pop-up with with mouse on screen edge under Wayland
https://bugs.kde.org/show_bug.cgi?id=398439 --- Comment #6 from Matěj Laitl --- Thanks a bunch! This combined with support for primary clipboard makes Plasma Wayland smooth for me. Sending lots of love. <3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396727] Crash when magnet removed from list
https://bugs.kde.org/show_bug.cgi?id=396727 --- Comment #2 from Matěj Laitl --- Created attachment 125070 --> https://bugs.kde.org/attachment.cgi?id=125070=edit New crash information added by DrKonqi ktorrent (5.1.2) using Qt 5.13.2 - What I was doing when the application crashed: Clicked on a magnet link, the magnet quickly downloaded, then KTorrent crashes, probably when removing the magnet from a list of magnets to download. To reproduce, one can just call ktorrent 'magnet:?xt=urn:btih:712922130bb7d83696a18a139454ce0a74455134=Apocalypse-The+Second+World+War+-+Season+1=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969=udp%3A%2F%2Ftracker.openbittorrent.com%3A80=udp%3A%2F%2Fopen.demonii.com%3A1337=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969=udp%3A%2F%2Fexodus.desync.com%3A6969' My Qt is compiled with debug assertions enabled. (that seems necessary to reproduce the bug). -- Backtrace (Reduced): #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #8 0x7f20c264b535 in __GI_abort () at abort.c:79 #9 0x7f20c4ac9bd8 in bt::QtMessageOutput (type=, msg=...) at /var/tmp/portage/net-libs/libktorrent-2.1.1/work/libktorrent-2.1.1/src/util/log.cpp:312 #10 0x7f20c2ca0c68 in qt_message_print (msgType=QtFatalMsg, context=..., message=...) at global/qlogging.cpp:1836 [...] #12 0x7f20c2c56782 in QMessageLogger::fatal (this=this@entry=0x7fff750aed90, msg=msg@entry=0x7f20c2f3df68 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:885 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 414830] Remove myself from "default CC" list of some Amarok components
https://bugs.kde.org/show_bug.cgi?id=414830 --- Comment #2 from Matěj Laitl --- Thanks, Christophe. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 414830] New: Remove myself from "default CC" list of some Amarok components
https://bugs.kde.org/show_bug.cgi?id=414830 Bug ID: 414830 Summary: Remove myself from "default CC" list of some Amarok components Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: ma...@laitl.cz CC: christo...@krop.fr Target Milestone: --- Hi, it seems that my e-mail (under which I'm posting right now) is still filled under "default CC list" of some Amarok components (I used to be a contributor to Amarok) as my e-mail stil gets added to new bugs for some Amarok components. I've tried to remove myself, but is seems that Amarok component administration is now allowed at my privilege level. Can you please remove me? Thanks, Matěj -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396727] Crash when magnet removed from list
https://bugs.kde.org/show_bug.cgi?id=396727 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 405603] Local Collection does't scan files with special characters or accents (latin)
https://bugs.kde.org/show_bug.cgi?id=405603 Matěj Laitl changed: What|Removed |Added CC|ma...@laitl.cz | -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 311193] Switching equalizer presets from/to Inactive resets song playback
https://bugs.kde.org/show_bug.cgi?id=311193 Matěj Laitl changed: What|Removed |Added CC|ma...@laitl.cz | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz --- Comment #6 from Matěj Laitl --- Happens to me, too, I'm attaching slightly more detailed backtrace, for the reference: Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69d6626880 (LWP 5248))] Thread 2 (Thread 0x7f69bee8d700 (LWP 5249)): #0 0x7f69d47565f3 in __GI___poll (fds=0x7f69b8003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f69d0bcf029 in g_main_context_poll (priority=, n_fds=1, fds=0x7f69b8003ce0, timeout=, context=0x7f69b8000bf0) at /var/tmp/portage/dev-libs/glib-2.56.2/work/glib-2.56.2/glib/gmain.c:4203 #2 g_main_context_iterate (context=context@entry=0x7f69b8000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.56.2/work/glib-2.56.2/glib/gmain.c:3897 #3 0x7f69d0bcf13c in g_main_context_iteration (context=0x7f69b8000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.56.2/work/glib-2.56.2/glib/gmain.c:3963 #4 0x7f69d4cddbab in QEventDispatcherGlib::processEvents (this=0x7f69b8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f69d4c806eb in QEventLoop::exec (this=this@entry=0x7f69bee8ccf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f69d4ac73ea in QThread::exec (this=this@entry=0x7f69c99e5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #7 0x7f69c975d055 in QDBusConnectionManager::run (this=0x7f69c99e5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f69d4ad2bc6 in QThreadPrivate::start (arg=0x7f69c99e5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #9 0x7f69d2b4096a in start_thread (arg=0x7f69bee8d700) at pthread_create.c:463 #10 0x7f69d47621bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f69d6626880 (LWP 5248)): [KCrash Handler] #6 0x7f69d5d02373 in XAddExtension (dpy=dpy@entry=0x55c41b3fd610) at /var/tmp/portage/x11-libs/libX11-1.6.7/work/libX11-1.6.7/src/InitExt.c:73 #7 0x7f69b5e67a5d in _XftDisplayInfoGet (dpy=dpy@entry=0x55c41b3fd610, createIfNecessary=createIfNecessary@entry=1) at /var/tmp/portage/x11-libs/libXft-2.3.2-r1/work/libXft-2.3.2/src/xftdpy.c:91 #8 0x7f69b5e6c46e in XftFontInfoFill (dpy=dpy@entry=0x55c41b3fd610, pattern=pattern@entry=0x55c41b576b10, fi=fi@entry=0x7ffd5faa8c40) at /var/tmp/portage/x11-libs/libXft-2.3.2-r1/work/libXft-2.3.2/src/xftfreetype.c:367 #9 0x7f69b5e6cd2a in XftFontOpenPattern (dpy=0x55c41b3fd610, pattern=pattern@entry=0x55c41b576b10) at /var/tmp/portage/x11-libs/libXft-2.3.2-r1/work/libXft-2.3.2/src/xftfreetype.c:1015 #10 0x7f69b607c02f in KFI::CFcEngine::getFont (this=this@entry=0x55c41b57aec8, size=size@entry=8) at /var/tmp/portage/kde-plasma/plasma-desktop-5.14.3/work/plasma-desktop-5.14.3/kcms/kfontinst/lib/FcEngine.cpp:1299 #11 0x7f69b607c602 in KFI::CFcEngine::queryFont (this=this@entry=0x55c41b57aec8) at /var/tmp/portage/kde-plasma/plasma-desktop-5.14.3/work/plasma-desktop-5.14.3/kcms/kfontinst/lib/FcEngine.cpp:1233 #12 0x7f69b607cd98 in KFI::CFcEngine::getSizes (this=0x55c41b57aec8) at /var/tmp/portage/kde-plasma/plasma-desktop-5.14.3/work/plasma-desktop-5.14.3/kcms/kfontinst/lib/FcEngine.cpp:1391 #13 0x7f69b607e7a8 in KFI::CFcEngine::draw (this=this@entry=0x55c41b57aec8, name=..., style=style@entry=4294967295, faceNo=faceNo@entry=0, txt=..., bgnd=..., w=128, h=128, thumb=true, range=..., chars=0x0) at /var/tmp/portage/kde-plasma/plasma-desktop-5.14.3/work/plasma-desktop-5.14.3/kcms/kfontinst/lib/FcEngine.cpp:876 #14 0x7f69b62850ef in KFI::CFontThumbnail::create (this=0x55c41b57aec0, path=..., width=128, height=128, img=...) at /var/tmp/portage/kde-plasma/plasma-desktop-5.14.3/work/plasma-desktop-5.14.3/kcms/kfontinst/thumbnail/FontThumbnail.cpp:114 #15 0x7f69c2fc5170 in ThumbnailProtocol::createSubThumbnail (this=this@entry=0x7ffd5faa9640, thumbnail=..., filePath=..., segmentWidth=segmentWidth@entry=54, segmentHeight=segmentHeight@entry=34) at /var/tmp/portage/kde-apps/kio-extras-18.08.3-r1/work/kio-extras-18.08.3/thumbnail/thumbnail.cpp:719 #16 0x7f69c2fc5788 in ThumbnailProtocol::drawSubThumbnail (this=this@entry=0x7ffd5faa9640, p=..., filePath=..., width=width@entry=54, height=height@entry=34, xPos=xPos@entry=64, yPos=38, frameWidth=2) at /var/tmp/portage/kde-apps/kio-extras-18.08.3-r1/work/kio-extras-18.08.3/thumbnail/thumbnail.cpp:751 #17 0x7f69c2fc5e50 in ThumbnailProtocol::thumbForDirectory (this=this@entry=0x7ffd5faa9640, directory=
[kdev-python] [Bug 403045] KDev-Python crashes when parsing RHS of annotated assignment with lambda [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 --- Comment #4 from Matěj Laitl --- Wow, thank you for super-fast fix, Francis! Kudos and keep up the good work. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403045] KDev-Python crashes when parsing RHS of annotated assignment with lambda [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 Matěj Laitl changed: What|Removed |Added Summary|KDev-Python crashes when|KDev-Python crashes when |parsing Python 3.6 |parsing RHS of annotated |@dataclass definition with |assignment with lambda |field() |[Python::UseBuilder::contex |[Python::UseBuilder::contex |tAtOrCurrent] |tAtOrCurrent] | -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403045] New: KDev-Python crashes when parsing Python 3.6 @dataclass definition with field()
https://bugs.kde.org/show_bug.cgi?id=403045 Bug ID: 403045 Summary: KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() Product: kdevelop Version: 5.2.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ma...@laitl.cz Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.14.78-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: KDevelop started to crash as soon as I typed following code (the last line): @dataclass class RecordData: imagery_files: int = 0 record_files: int = 0 per_type_sqkm: dict = field(default_factory=lambda: defaultdict(float)) The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f8eea4880 (LWP 11395))] Thread 19 (Thread 0x7f7f15ffb700 (LWP 11526)): #0 0x7f7f8b5a1ab8 in __GI___nanosleep (requested_time=requested_time@entry=0x7f7f15ff9c10, remaining=remaining@entry=0x7f7f15ff9c10) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7f7f8befd55d in qt_nanosleep (amount=...) at kernel/qelapsedtimer_unix.cpp:195 #2 0x7f7f8bd14d60 in QThread::usleep (usecs=usecs@entry=500) at thread/qthread_unix.cpp:542 #3 0x7f7f8972cba8 in KDevelop::DUChainLock::lockForWrite (this=0x7f7f89ec8c60 , timeout=0) at /var/tmp/portage/dev-util/kdevelop-5.2.4/work/kdevelop-5.2.4/kdevplatform/language/duchain/duchainlock.cpp:152 #4 0x7f7f8972cdbc in KDevelop::DUChainWriteLocker::lock (this=0x7f7f15ff9d80) at /var/tmp/portage/dev-util/kdevelop-5.2.4/work/kdevelop-5.2.4/kdevplatform/language/duchain/duchainlock.cpp:246 #5 0x7f7f2b95ac57 in Python::DeclarationBuilder::createModuleImportDeclaration (this=this@entry=0x7f7f15ffa780, moduleName=..., declarationName=..., declarationIdentifier=declarationIdentifier@entry=0x7f7f0002f3e0, problemEncountered=..., rangeNode=rangeNode@entry=0x0) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:683 #6 0x7f7f2b95bf5f in Python::DeclarationBuilder::visitImportFrom (this=0x7f7f15ffa780, node=0x7f7f9e90) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:451 #7 0x7f7f2b956938 in Python::DeclarationBuilder::visitNode (this=0x7f7f15ffa780, node=0x7f7f9e90) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:1844 #8 0x7f7f48fc6b7c in Python::AstVisitor::visitNodeList (l=..., this=0x7f7f15ffa968) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/parser/astvisitor.h:50 #9 Python::AstDefaultVisitor::visitCode (this=this@entry=0x7f7f15ffa968, node=node@entry=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/parser/astdefaultvisitor.cpp:91 #10 0x7f7f2b952280 in Python::ContextBuilder::visitCode (this=this@entry=0x7f7f15ffa780, node=node@entry=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/contextbuilder.cpp:318 #11 0x7f7f2b95749a in Python::DeclarationBuilder::visitCode (this=0x7f7f15ffa780, node=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:345 #12 0x7f7f2b956938 in Python::DeclarationBuilder::visitNode (this=0x7f7f15ffa780, node=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:1844 #13 0x7f7f2b967835 in KDevelop::AbstractContextBuilder::supportBuild (context=0x7f7f00065520, node=0x7f7f0002a400, this=0x7f7f15ffa780) at /usr/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:131 #14 KDevelop::AbstractTypeBuilder::supportBuild (this=0x7f7f15ffa780, node=0x7f7f0002a400, context=) at /usr/include/kdevplatform/language/duchain/builders/abstracttypebuilder.h:84 #15 0x7f7f2b94dfdb in KDevelop::AbstractContextBuilder::build (updateContext=..., node=0x7f7f0002a400, url=..., this=0x7f7f15ffa780) at /usr/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:111 #16 Python::ContextBuilder::build (this=this@entry=0x7f7f15ffa780, url=..., node=node@entry=0x7f7f0002a400, updateContext=...) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/contextbuilder.cpp:75 #17 0x7f7f2b95708b in Python::DeclarationBuilder::build (this=this@entry=0x7f7f15ffa780, url=..., node=0x7f7f0002a400, updateContext=...) at
[frameworks-baloo] [Bug 397644] baloo_file crashes in Baloo::DocumentTimeDB::get()
https://bugs.kde.org/show_bug.cgi?id=397644 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397644] baloo_file crashes in Baloo::DocumentTimeDB::get()
https://bugs.kde.org/show_bug.cgi?id=397644 --- Comment #9 from Matěj Laitl --- Created attachment 116935 --> https://bugs.kde.org/attachment.cgi?id=116935=edit New crash information added by DrKonqi baloo_file (5.52.0) using Qt 5.11.1 - What I was doing when the application crashed: Crashes immediately on session startup. -- Backtrace (Reduced): #6 0x7f4aa5046ecd in Baloo::DocumentTimeDB::get (this=this@entry=0x7f4a98897960, docId=, docId@entry=6798499437873171) at /var/tmp/portage/kde-frameworks/baloo-5.52.0/work/baloo-5.52.0/src/engine/documenttimedb.cpp:89 #7 0x7f4aa5054d39 in Baloo::Transaction::documentTimeInfo (this=, id=id@entry=6798499437873171) at /var/tmp/portage/kde-frameworks/baloo-5.52.0/work/baloo-5.52.0/src/engine/transaction.cpp:142 #8 0x559b987d82f5 in Baloo::UnIndexedFileIterator::shouldIndex (this=0x7f4a98897c10, filePath=..., mimetype=...) at /var/tmp/portage/kde-frameworks/baloo-5.52.0/work/baloo-5.52.0/src/file/unindexedfileiterator.cpp:104 #9 0x559b987d8613 in Baloo::UnIndexedFileIterator::next (this=this@entry=0x7f4a98897c10) at /var/tmp/portage/kde-frameworks/baloo-5.52.0/work/baloo-5.52.0/src/file/unindexedfileiterator.cpp:82 #10 0x559b987cf7ad in Baloo::UnindexedFileIndexer::run (this=0x559b9a8da4d0) at /var/tmp/portage/kde-frameworks/baloo-5.52.0/work/baloo-5.52.0/src/file/unindexedfileindexer.cpp:49 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Matěj Laitl changed: What|Removed |Added CC||ma...@laitl.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398439] New: "Windows can cover" panel does not pop-up with with mouse on screen edge under Wayland
https://bugs.kde.org/show_bug.cgi?id=398439 Bug ID: 398439 Summary: "Windows can cover" panel does not pop-up with with mouse on screen edge under Wayland Product: plasmashell Version: 5.13.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ma...@laitl.cz Target Milestone: 1.0 Flags: Wayland+, X11- Hi, one Wayland-specific. Steps to reproduce: 1. Use Wayland session (kwin_wayland) 2. Set your panel to "Windows can cover" 3. Launch a maximized application 4. Move your mouse to edge of the screen where the panel is Expected results: Panel pops up. This is the way it works under X session. Actual results: Panel does not show up. You need to move windows away from panel to see it. It does not matter whether the covering window is native Wayland or XWayland one. After setting the panel to "Auto hide" it works correctly - it pops up even with maximized applications. KDE Plasma: 5.13.5 KDE Frameworks: 5.49.0 Qt: 5.11.1 Wayland: 1.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 396849] Parsing valid Python 3.6 f-string syntax fails with "invalid syntax"
https://bugs.kde.org/show_bug.cgi?id=396849 Matěj Laitl changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Matěj Laitl --- Rebuilding indeed help. Thanks and keep up the good work! :) -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 396849] Parsing valid Python 3.6 f-string syntax fails with "invalid syntax"
https://bugs.kde.org/show_bug.cgi?id=396849 --- Comment #2 from Matěj Laitl --- (In reply to Sven Brauch from comment #1) > What linux distro is your package from? It seems like they built it against > Python 3.5. Gentoo, so it is my fault, because you can set Python version to build against and I've indeed build kdev-python against 3.5. I'll rebuild, confirm, then close this. Thanks for quick help, Sven! -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 396849] New: Parsing valid Python 3.6 f-string syntax fails with "invalid syntax"
https://bugs.kde.org/show_bug.cgi?id=396849
Bug ID: 396849
Summary: Parsing valid Python 3.6 f-string syntax fails with
"invalid syntax"
Product: kdev-python
Version: 5.2.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: ma...@laitl.cz
Target Milestone: ---
Python 3.6 introduced new string formatting syntax, f-strings:
https://docs.python.org/3/reference/lexical_analysis.html#f-strings, e.g.
number = 42
message = f'there is {number} apples'
This doesn't seem to be supported, at least with my setup. Is there some
setting/configuration/unreleased version that could help?
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Matěj Laitl changed: What|Removed |Added CC|ma...@laitl.cz | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added CC||arichardson@gmail.com, ||ma...@laitl.cz Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Version|5.6.95 |5.9.5 --- Comment #5 from Matěj Laitl <ma...@laitl.cz> --- Also happens to me with more KDE components: org_kde_powerdevil (5.9.5) polkit-kde-authentication-agent-1 (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.34.0 polkit-qt-1: 0.112.0 Operating System: Linux 4.9.16-gentoo x86_64 Distribution (Platform): Gentoo Packages All the crashes have common end of the backtrace: Thread 1 (Thread 0x7f5a98552840 (LWP 3681)): [KCrash Handler] #6 0x7f5a96b13128 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f5a96b1457a in __GI_abort () at abort.c:89 #8 0x7f5a97306999 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1682 #9 QMessageLogger::fatal (this=this@entry=0x7ffd00abfaa0, msg=msg@entry=0x7f5a986b0098 "QDBusArgument: read from a write-only object") at global/qlogging.cpp:793 #10 0x7f5a98645e08 in QDBusArgumentPrivate::checkRead (d=) at qdbusargument.cpp:142 #11 0x7f5a98693ee8 in QDBusArgumentPrivate::checkRead (d=) at qdbusargument.cpp:166 #12 QDBusArgumentPrivate::checkReadAndDetach (d=@0x7ffd00abfc50: 0x2503980) at qdbusargument.cpp:152 #13 0x7f5a98696ea9 in QDBusArgument::beginMapEntry (this=0x7ffd00abfc50) at qdbusargument.cpp:1069 #14 0x7f5a7edba93f in operator>> (list=..., arg=...) at /usr/include/qt5/QtDBus/qdbusargument.h:275 #15 PolkitQt1::Authority::Private::init (this=0x24e1090) at /var/tmp/portage/sys-auth/polkit-qt-0.112.0-r1/work/polkit-qt-1-0.112.0/core/polkitqt1-authority.cpp:226 ...and appear indeed only when QtDBus is compiled in debug mode: https://code.qt.io/cgit/qt/qtbase.git/tree/src/dbus/qdbusargument.cpp?h=5.7#n141 The assertion has been however probably fixed in polkit-qt master in this commit: https://cgit.kde.org/polkit-qt-1.git/commit/?id=fb1667ac9a5437b4784d2806a3e816cbdbe404a5 Alex, maybe this warrants releasing new polkit-qt-1 with the fix? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 335217] Auto-expand after collection browser search expands less than desired (affects also 'Show in Media sources')
https://bugs.kde.org/show_bug.cgi?id=335217 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Latest Commit||http://commits.kde.org/amar ||ok/9fb00e5a97574af3f0cb22d7 ||40da7e0cd0761d78 Version Fixed In||2.9 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Matěj Laitl <ma...@laitl.cz> --- Git commit 9fb00e5a97574af3f0cb22d740da7e0cd0761d78 by Matěj Laitl. Committed on 16/10/2016 at 22:03. Pushed by laitl into branch 'master'. Fix Collection Browser auto-expand after search expanding too little Underlying model is asynchronous, we need to cope with that. Do it using a RAII self-destructing object AutoExpander. As a side-effect, Amarok no longer expands collection after start in split collection mode. If this is desired, we may expand them explicitly upon start. Related: bug 300557 FIXED-IN: 2.9 M +1-0ChangeLog M +68 -20 src/browsers/CollectionTreeView.cpp http://commits.kde.org/amarok/9fb00e5a97574af3f0cb22d740da7e0cd0761d78 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 300557] When a collection is updated, Amarok expands collapsed entries in the Collection Browser
https://bugs.kde.org/show_bug.cgi?id=300557 --- Comment #10 from Matěj Laitl <ma...@laitl.cz> --- Git commit 9fb00e5a97574af3f0cb22d740da7e0cd0761d78 by Matěj Laitl. Committed on 16/10/2016 at 22:03. Pushed by laitl into branch 'master'. Fix Collection Browser auto-expand after search expanding too little Underlying model is asynchronous, we need to cope with that. Do it using a RAII self-destructing object AutoExpander. As a side-effect, Amarok no longer expands collection after start in split collection mode. If this is desired, we may expand them explicitly upon start. Related: bug 335217 FIXED-IN: 2.9 M +1-0ChangeLog M +68 -20 src/browsers/CollectionTreeView.cpp http://commits.kde.org/amarok/9fb00e5a97574af3f0cb22d740da7e0cd0761d78 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 365275] MPRIS2 DesktopEntry value of kde4-amarok doesn't match name of installed .desktop file
https://bugs.kde.org/show_bug.cgi?id=365275 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit||http://commits.kde.org/amar ||ok/9449ec56d1fd77a0bfa1f713 ||4a2bf4f91ffd14d3 Resolution|--- |FIXED Version Fixed In||2.9 --- Comment #10 from Matěj Laitl <ma...@laitl.cz> --- Git commit 9449ec56d1fd77a0bfa1f7134a2bf4f91ffd14d3 by Matěj Laitl, on behalf of Antonio Rojas. Committed on 20/08/2016 at 11:10. Pushed by laitl into branch 'master'. Fix MPRIS2 DesktopEntry value According to the MPRIS2 spec, the DesktopEntry value should be "the basename of the .desktop file" [1], not the desktop-file-id. So for amarok it should be "amarok" and not "kde4-amarok", regardless of where the desktop file is installed. This fixes displaying MPRIS controls in the Amarok taskbar tooltip in Plasma 5.7 [1] https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:DesktopEntry Testing done by Antonio: Player controls are displayed again in the Amarok taskbar tooltip in Plasma 5.7. REVIEW: 128418 FIXED-IN: 2.9 M +2-0ChangeLog M +1-5src/dbus/mpris2/MediaPlayer2.cpp http://commits.kde.org/amarok/9449ec56d1fd77a0bfa1f7134a2bf4f91ffd14d3 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 226144] remember filename schema used last
https://bugs.kde.org/show_bug.cgi?id=226144 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=341092 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 341092] Preselection for files are not saved
https://bugs.kde.org/show_bug.cgi?id=341092 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/amar ||ok/0e760e5f8d06d00e084c14b6 ||4875f58bb42bd8f1 Version Fixed In||2.9 CC||ma...@laitl.cz See Also||https://bugs.kde.org/show_b ||ug.cgi?id=226144 --- Comment #4 from Matěj Laitl <ma...@laitl.cz> --- I think this may be resolved by work done on bug 226144: > Git commit 0e760e5f8d06d00e084c14b64875f58bb42bd8f1 by Matěj Laitl, on > behalf of Stefano Pettini. > Committed on 20/08/2016 at 10:37. > Pushed by laitl into branch 'master'. > > Organize tracks / Guess tags presets persisted properly. > > FilenameLayoutWidget is reworked to fix an old bug regarding the presets > not being saved properly, that I was also able to reproduce. > > Logic is not a bit more "linear". Presets are shared between "Organize > tracks" > and "Guess tags" dialog. If this is not what is wanted, it can be easily > changed, > just let me know. Presets are saved as soon as they are added, updated or > deleted. > It is not anymore necessary to accept the dialog to save eventual changes. > > The preset used is not saved with the marker "#DELIM#selected" anymore. > Presets are just presets. The one used is matched on the fly using the custom > preset field. If a preset matches the custom preset field, it's considered > selected. Users can of course create custom presets as before. > While presets are shared between the two dialogs, custom presets are not. > > Add/Update/Remove work properly. Clicking on a preset name in the combobox > resets the custom pattern to the preset value, this is a new feature, > before it was not possible. > > It's a bit difficult to explain, but UX is more natural, just give it a try. > > A lot of testing was done (by Stefano), like: > - adding/updating/removing presets. > - if settings are persisted and shared when dialogs are cancelled or > accepted. > - if custom patterns are persisted and not shared. > - resetting a modified pattern to its defualt. > - cancelling dialogs, modified presets are kept but custom patterns are not. > > REVIEW: 128565 > > M +3-1ChangeLog > M +1-1src/amarokconfig.kcfg > M +0-5src/dialogs/OrganizeCollectionDialog.cpp > M +0-2src/dialogs/OrganizeCollectionDialog.h > M +53 -49 src/widgets/FilenameLayoutWidget.cpp > M +4-6src/widgets/FilenameLayoutWidget.h > > http://commits.kde.org/amarok/0e760e5f8d06d00e084c14b64875f58bb42bd8f1 Please re-test with current git master and reopen if it is not the case. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 226144] remember filename schema used last
https://bugs.kde.org/show_bug.cgi?id=226144 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added CC||ma...@laitl.cz Version Fixed In||2.9 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 226144] remember filename schema used last
https://bugs.kde.org/show_bug.cgi?id=226144 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/amar ||ok/0e760e5f8d06d00e084c14b6 ||4875f58bb42bd8f1 Status|CONFIRMED |RESOLVED --- Comment #17 from Matěj Laitl <ma...@laitl.cz> --- Git commit 0e760e5f8d06d00e084c14b64875f58bb42bd8f1 by Matěj Laitl, on behalf of Stefano Pettini. Committed on 20/08/2016 at 10:37. Pushed by laitl into branch 'master'. Organize tracks / Guess tags presets persisted properly. FilenameLayoutWidget is reworked to fix an old bug regarding the presets not being saved properly, that I was also able to reproduce. Logic is not a bit more "linear". Presets are shared between "Organize tracks" and "Guess tags" dialog. If this is not what is wanted, it can be easily changed, just let me know. Presets are saved as soon as they are added, updated or deleted. It is not anymore necessary to accept the dialog to save eventual changes. The preset used is not saved with the marker "#DELIM#selected" anymore. Presets are just presets. The one used is matched on the fly using the custom preset field. If a preset matches the custom preset field, it's considered selected. Users can of course create custom presets as before. While presets are shared between the two dialogs, custom presets are not. Add/Update/Remove work properly. Clicking on a preset name in the combobox resets the custom pattern to the preset value, this is a new feature, before it was not possible. It's a bit difficult to explain, but UX is more natural, just give it a try. A lot of testing was done (by Stefano), like: - adding/updating/removing presets. - if settings are persisted and shared when dialogs are cancelled or accepted. - if custom patterns are persisted and not shared. - resetting a modified pattern to its defualt. - cancelling dialogs, modified presets are kept but custom patterns are not. REVIEW: 128565 M +3-1ChangeLog M +1-1src/amarokconfig.kcfg M +0-5src/dialogs/OrganizeCollectionDialog.cpp M +0-2src/dialogs/OrganizeCollectionDialog.h M +53 -49 src/widgets/FilenameLayoutWidget.cpp M +4-6src/widgets/FilenameLayoutWidget.h http://commits.kde.org/amarok/0e760e5f8d06d00e084c14b64875f58bb42bd8f1 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 314854] regression with KDE 4.10: Lyrics background has the wrong colour
https://bugs.kde.org/show_bug.cgi?id=314854 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/amar ||ok/bdbb3a27f556c41910d3b814 ||e5a4c73a2a93362f Status|CONFIRMED |RESOLVED --- Comment #13 from Matěj Laitl <ma...@laitl.cz> --- Git commit bdbb3a27f556c41910d3b814e5a4c73a2a93362f by Matěj Laitl, on behalf of Stefano Pettini. Committed on 07/08/2016 at 09:42. Pushed by laitl into branch 'master'. Use transparent background for lyrics browser This makes the lyrics browser similar to every other context applet. Please note that, when editing lyrics, the default textbox background is still used. REVIEW: 128246 M +1-0ChangeLog M +5-7src/context/applets/lyrics/LyricsBrowser.cpp http://commits.kde.org/amarok/bdbb3a27f556c41910d3b814e5a4c73a2a93362f -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 341661] Recent build from git if length is used to build filter it is always show as zero
https://bugs.kde.org/show_bug.cgi?id=341661 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/amar ||ok/6c49cfdfd97faa146ce7b0d8 ||e95ce2bf596f2b0d Resolution|--- |FIXED --- Comment #8 from Matěj Laitl <ma...@laitl.cz> --- Git commit 6c49cfdfd97faa146ce7b0d8e95ce2bf596f2b0d by Matěj Laitl, on behalf of Stefano Pettini. Committed on 07/08/2016 at 09:34. Pushed by laitl into branch 'master'. Handle numeric fields properly in filter creation dialogs Every numeric field, like length, disc number and track number, were not properly parsed by the filter dialog or by the dynamic playlist dialog into the textual query string used to then apply the filter. The bug was due to what sounds like an "optimization" that swapped the first and second value of a "between" condition, to make sure the smaller value was always the first value and the larger always the second. The problem was that this was applied also to non-between conditions, actually swapping the lenth or disc number with 0, making 0 appear in the textual representation of the condition. The fix makes sure that "optimization" is applied only in case of actual "between" conditions, leaving the values "unoptimized" for any other kind of condition (=, <, > and similar). REVIEW: 128245 M +2-0ChangeLog M +5-1src/widgets/MetaQueryWidget.cpp http://commits.kde.org/amarok/6c49cfdfd97faa146ce7b0d8e95ce2bf596f2b0d -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 354255] [PATCH]: Handle removed --myisam-recover option in MySQL 5.7
https://bugs.kde.org/show_bug.cgi?id=354255 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||2.9 Latest Commit||http://commits.kde.org/amar ||ok/a07f44ddcd61bac1bb2f1e17 ||cfc07d40a940bb5a Resolution|--- |FIXED --- Comment #7 from Matěj Laitl <ma...@laitl.cz> --- Git commit a07f44ddcd61bac1bb2f1e17cfc07d40a940bb5a by Matěj Laitl, on behalf of Terje Rosten. Committed on 07/08/2016 at 09:05. Pushed by laitl into branch 'master'. Substitute deprecated MySQL option --myisam-recover Deprecated MySQL option --myisam-recover has been removed in MySQL 5.7, replacement is --myisam-recover-options. Use MYSQL_VERSION_ID to handle this. Signed-off-by: Terje Rosten <terje.ros...@oracle.com> Signed-off-by: Stefano Pettini <stefano.pett...@gmail.com> CCMAIL: Terje Rosten <terje.ros...@oracle.com> REVIEW: 128157 FIXED-IN: 2.9 M +2-0ChangeLog M +4-0src/core-impl/storage/sql/mysqlestorage/MySqlEmbeddedStorage.cpp http://commits.kde.org/amarok/a07f44ddcd61bac1bb2f1e17cfc07d40a940bb5a -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Matěj Laitl <ma...@laitl.cz> changed: What|Removed |Added CC|ma...@laitl.cz | -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 361307] Last.fm plugin creates a non hidden folder in user home directory for cache
https://bugs.kde.org/show_bug.cgi?id=361307 --- Comment #1 from Matěj Laitl <ma...@laitl.cz> --- I think this problem is caused by liblastfm library itself. What version do you have? Can you try with a newer version? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 357548] Gwenview crashes when I activate 100% zoom by either middle click or toolbar button
https://bugs.kde.org/show_bug.cgi?id=357548 --- Comment #1 from Matěj Laitl <ma...@laitl.cz> --- Created attachment 96461 --> https://bugs.kde.org/attachment.cgi?id=96461=edit gwenview-crash-scan-012.jpg -- You are receiving this mail because: You are watching all bug changes.
