[systemsettings] [Bug 399961] Suggestion on changing the default Desktop Session options
https://bugs.kde.org/show_bug.cgi?id=399961 --- Comment #2 from Tyson Tan --- Ah, I forgot one of my arguments: Why restore previous session, when you can SLEEP?(In reply to Kai Uwe Broulik from comment #1) > Do you have any evidence for your "most users want" claim? > > I agree that shutting down should be the preferred logout option and I think > we're planning to change that soon as we're refactoring the session manager > right now. > > I also disable session restoration but mostly because it's not very > reliable. Doesn't mean it shouldn't be fixed instead of disabling it. Ah, I forgot one of my arguments: Why restore previous session, when you can SLEEP? I don't feel such a function today makes much sense anymore. But that's my two cents. I do not have hard data to backup my "claims", but judging from almost every other popular OS/DE's design choice, I dare say I made an educated guess. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399968] Suggestion on improving selection markers' visual consistency
https://bugs.kde.org/show_bug.cgi?id=399968 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- For that pretty much the "somewhat best fitting" icons were chosen in the iconset, never were dedicated icons created for this. I agree, this needs some polish. I even copied that to Folder View, to at least be consistently bad :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 399958] Consider making FormLayout centered by default
https://bugs.kde.org/show_bug.cgi?id=399958 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- If you do any behavioral changes here make sure to make it consistent with QFormLayout which has always been not centered horizontally for KDE. [1] "Recommended style for KDE applications. Similar to MacStyle, except that the form is left-aligned and all fields grow to fill the available space." [1] https://doc.qt.io/qt-5/qformlayout.html -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399968] New: Suggestion on improving selection markers' visual consistency
https://bugs.kde.org/show_bug.cgi?id=399968 Bug ID: 399968 Summary: Suggestion on improving selection markers' visual consistency Product: dolphin Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY I have 2 suggestions on improving the visual consistency of Dolphin's selection markers. Please allow me to explain them separately below. 1) A Square Plus selection marker: Right now the "Plus" (+) selection marker in Dolphin is round. It creates visual inconsistency because almost everything else including the "Minus" [-] icon is sharp and rectangle. It really stands out right now as a green round icon and doesn't match anything else there. 2) Do not highlight selection markers with colors: Right now the (+) icon turns green and the [-] icon turns red when cursor is over them. Again this creates visual inconsistency because KDE's visual style is very grey-white-oriented and low-key-elegant. The green and red used here are way too intense and they stand out in a bad way. Although they serve their functions, I think we can either: a) Turn it down a notch so they look greyish-green/red b) Use blue instead of green, use orange-yellow instead of red c) Use only transparency difference as over hints Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399960] Screen Corner Activation delay's default value is too high
https://bugs.kde.org/show_bug.cgi?id=399960 Kai Uwe Broulik changed: What|Removed |Added Component|general |general Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Product|systemsettings |kwin CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- It's also one of the first settings I have to change to a lower value. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399961] Suggestion on changing the default Desktop Session options
https://bugs.kde.org/show_bug.cgi?id=399961 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Do you have any evidence for your "most users want" claim? I agree that shutting down should be the preferred logout option and I think we're planning to change that soon as we're refactoring the session manager right now. I also disable session restoration but mostly because it's not very reliable. Doesn't mean it shouldn't be fixed instead of disabling it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399964] Click Behavior settings should be in Dolphin's configuration dialogue
https://bugs.kde.org/show_bug.cgi?id=399964 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@privat.broulik.de Resolution|--- |DUPLICATE --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 399963 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399963] Click Behavior settings should be in Dolphin's configuration dialogue
https://bugs.kde.org/show_bug.cgi?id=399963 --- Comment #1 from Kai Uwe Broulik --- *** Bug 399964 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399966] Folder thumbnails should be turned off by default
https://bugs.kde.org/show_bug.cgi?id=399966 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- The thumbnails could be aligned more nicely. The old "randomly rotated with a picture frame" was the taste of the time when this feature was created. I disagree that they should be disabled by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399967] Application launcher's Computer tab should separate its Places section from Dolphin's sidebar
https://bugs.kde.org/show_bug.cgi?id=399967 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- KFilePlacesModel allows to mark items as "only show in $application", which currently isn't accessible from the Application Launcher. I don't they should be completely separate, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399967] New: Application launcher's Computer tab should separate its Places section from Dolphin's sidebar
https://bugs.kde.org/show_bug.cgi?id=399967 Bug ID: 399967 Summary: Application launcher's Computer tab should separate its Places section from Dolphin's sidebar Product: plasmashell Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: tyson...@mail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Right now Application launcher's Computer tab is using information from Dolphin's sidebar for its Places section. I suggest we change that by making the two independent. Reasons: 1) Changing Dolphin's sidebar affects something else outside of it. This is not something a normal user would expect. 2) It gives the impression of an unreliable Application Launcher. Because the user never changed anything in Application Launcher and yet it "changes itself". 3) Dolphin has more vertical space in its sidebar. Naturally it can display more, or we can even say it MUST display more, otherwise it looks uncomfortably barren; 4) Application Launcher's Computer tab has so little vertical space, with 3 slots already occupied by System Applications. We cannot display a lot items on it, otherwise it forces the whole thing to scroll around. It doesn't look very tidy nor reliable like that. 5) By making Dolphin's sidebar and Application Launcher's Computer tab being managed separately, we can fine-tune items being shown for each of them. They are very different beasts and I suggest we treat them differently. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 399932] budget sceen don't show the amounts
https://bugs.kde.org/show_bug.cgi?id=399932 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Baumgart --- Did you try to right click on the header and activate the columns you want to see? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399966] New: Folder thumbnails should be turned off by default
https://bugs.kde.org/show_bug.cgi?id=399966 Bug ID: 399966 Summary: Folder thumbnails should be turned off by default Product: dolphin Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tyson...@mail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY By default Dolphin displays thumbnails for folders. I suggest we change that. Reasons being: 1) It looks awful with all those tiny thumbnails of different sizes and orientations scattering on a folder's already small icon face. It doesn't give an impression of professionalism and reliability. 2) For our small default icon size, we can't learn much from those thumbnails. So they are pretty much useless distractions. 3) The option to turn if off is not very easy to discover, because the responsible checkbox is overwhelmed by a list with other file types. SUGGESTIONS 1) Folder thumbnails should be turned off by default 2) Or, only show folder thumbnails when icon size is above a certain threshold 3) Align and crop 4 displayed thumbnails into 4 squares, making it tidy-looking 4) Move [ ] Folders checkbox out from the Preview file type list, put it right below the "Show preview for:" text. Because in normal people's mind, a folder is not a file, it is what holds files, and thus should not be treated equally. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399913] Make drag drop, copy and paste work more transparently with desktop/filemanager
https://bugs.kde.org/show_bug.cgi?id=399913 --- Comment #2 from b...@bertenselena.net --- Hi Maik, I am using the standard filemanager on ubuntu (18.04 at time of writing). It is the nautilus filemanager. I just double-checked and copy-paste does not work here. Also with Right mouse button context menue the paste option is grayed out. But thanks for the hint. I opened dolphin and by golly, paste works. So it might be a nautilus bug. or even setting.. not sure. Can you check on your side if this behaviour is visible? And regarding the drop action, that makes complete sense. DnD to gimp is a good thing to have. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399965] New: Changing icon in Dolphin toolbar
https://bugs.kde.org/show_bug.cgi?id=399965 Bug ID: 399965 Summary: Changing icon in Dolphin toolbar Product: dolphin Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 11wallac...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.08.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.0-rc7-jwrdegoede+ x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Trying to select an icon for delete button in Dolphin toolbar. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f77e94800 (LWP 1885))] Thread 5 (Thread 0x7f1f6d661700 (LWP 1891)): #0 0x7f1f8232ec21 in poll () at /usr/lib/libc.so.6 #1 0x7f1f7d326ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1f7d326fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1f80444fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1f803f08cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1f80239eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1f80243f65 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1f7e1f9a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1f82339b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1f6e282700 (LWP 1890)): #0 0x7f1f7e1ffafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1f6e61217c in () at /usr/lib/dri/i965_dri.so #2 0x7f1f6e611eb8 in () at /usr/lib/dri/i965_dri.so #3 0x7f1f7e1f9a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1f82339b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1f6700 (LWP 1889)): #0 0x7f1f8232ec21 in poll () at /usr/lib/libc.so.6 #1 0x7f1f7d326ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1f7d326fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1f80444fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1f803f08cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1f80239eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1f80698ba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f1f80243f65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1f7e1f9a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f1f82339b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1f7665f700 (LWP 1888)): #0 0x7f1f8232ec21 in poll () at /usr/lib/libc.so.6 #1 0x7f1f7ccda630 in () at /usr/lib/libxcb.so.1 #2 0x7f1f7ccdc2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f1f77a00c5a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1f80243f65 in () at /usr/lib/libQt5Core.so.5 #5 0x7f1f7e1f9a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1f82339b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1f77e94800 (LWP 1885)): [KCrash Handler] #6 0x7f1f802b5732 in QString::mid(int, int) const () at /usr/lib/libQt5Core.so.5 #7 0x7f1f818973cd in () at /usr/lib/libKF5IconThemes.so.5 #8 0x7f1f8189ae71 in () at /usr/lib/libKF5IconThemes.so.5 #9 0x7f1f8189963f in () at /usr/lib/libKF5IconThemes.so.5 #10 0x7f1f8189b827 in () at /usr/lib/libKF5IconThemes.so.5 #11 0x7f1f803f194b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f1f80dfce04 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f1f80e046e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f1f803f1c39 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f1f80e38edd in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5 #16 0x7f1f80e3c1d5 in QWidget::setVisible(bool) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f1f80ff2fdd in QDialog::setVisible(bool) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f1f80ff2638 in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5 #19 0x7f1f81898d9a in KIconDialog::openDialog() () at /usr/lib/libKF5IconThemes.so.5 #20 0x7f1f81898f80 in KIconDialog::getIcon(KIconLoader::Group, KIconLoader::Context, bool, int, bool, QWidget*, QString const&) () at /usr/lib/libKF5IconThemes.so.5 #21 0x7f1f81928e5d in () at /usr/lib/libKF5XmlGui.so.5 #22 0x7f1f8192e7f9 in () at /usr/lib/libKF5XmlGui.so.5 #23 0x7f1f8192e838 in () at /usr/lib/libKF5Xml
[frameworks-baloo] [Bug 388897] baloo_file crashed in Baloo::DocumentTimeDB::put()
https://bugs.kde.org/show_bug.cgi?id=388897 --- Comment #2 from Papoteur --- Hello, Since this time, baloo never reindexed new files. I have run the command balooctl checkDb and got a crash. Here is the backtrace. gdb --args balooctl checkDb GNU gdb (GDB) 7.12-16.1.mga6 (Mageia release 6) ... Reading symbols from balooctl...Reading symbols from /usr/lib/debug/usr/bin/balooctl.debug...done. done. (gdb) run Starting program: /usr/bin/balooctl checkDb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe7b05700 (LWP 26783)] mdb.c:5884: Assertion 'IS_LEAF(mp)' failed in mdb_cursor_next() Thread 1 "balooctl" received signal SIGABRT, Aborted. 0x7662a818 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Missing separate debuginfos, use: debuginfo-install lib64bsd0-0.8.3-1.mga6.x86_64 lib64bzip2_1-1.0.6-10.mga6.x86_64 lib64dbus1_3-1.10.16-1.mga6.x86_64 lib64drm2-2.4.91-1.1.mga6.x86_64 lib64expat1-2.2.1-1.mga6.x86_64 lib64fam0-0.1.10-17.mga6.x86_64 lib64freetype6-2.7.1-2.2.mga6.tainted.x86_64 lib64gcrypt20-1.7.10-1.mga6.x86_64 lib64glapi0-17.3.9-1.mga6.x86_64 lib64glib2.0_0-2.54.3-1.1.mga6.x86_64 lib64gpg-error0-1.24-1.mga6.x86_64 lib64graphite2_3-1.3.10-1.1.mga6.x86_64 lib64harfbuzz0-1.3.2-5.mga6.x86_64 lib64icu58-58.2-3.2.mga6.x86_64 lib64kconfigCore5-5.42.0-1.mga6.x86_64 lib64kf5coreaddons5-5.42.0-1.mga6.x86_64 lib64kf5filemetadata5-5.42.0-1.mga6.x86_64 lib64kf5i18n5-5.42.0-1.mga6.x86_64 lib64kf5solid5-5.42.0-1.mga6.x86_64 lib64lzma5-5.2.3-1.mga6.x86_64 lib64mesagl1-17.3.9-1.mga6.x86_64 lib64pcre1-8.41-1.mga6.x86_64 lib64png16_16-1.6.34-1.mga6.x86_64 lib64qt5core5-5.9.4-1.1.mga6.x86_64 lib64qt5dbus5-5.9.4-1.1.mga6.x86_64 lib64qt5gui5-5.9.4-1.1.mga6.x86_64 lib64qt5widgets5-5.9.4-1.1.mga6.x86_64 lib64qt5xml5-5.9.4-1.1.mga6.x86_64 lib64systemd0-230-12.3.mga6.x86_64 lib64udev1-230-12.3.mga6.x86_64 lib64x11-xcb1-1.6.5-1.1.mga6.x86_64 lib64x11_6-1.6.5-1.1.mga6.x86_64 lib64xau6-1.0.8-7.mga6.x86_64 lib64xcb-dri2_0-1.12-2.mga6.x86_64 lib64xcb-dri3_0-1.12-2.mga6.x86_64 lib64xcb-glx0-1.12-2.mga6.x86_64 lib64xcb-present0-1.12-2.mga6.x86_64 lib64xcb-sync1-1.12-2.mga6.x86_64 lib64xcb1-1.12-2.mga6.x86_64 lib64xdamage1-1.1.4-8.mga6.x86_64 lib64xdmcp6-1.1.2-5.mga6.x86_64 lib64xext6-1.3.3-4.mga6.x86_64 lib64xfixes3-5.0.3-1.mga6.x86_64 lib64xshmfence1-1.2-2.mga6.x86_64 lib64xxf86vm1-1.1.4-2.mga6.x86_64 lib64zlib1-1.2.11-4.1.mga6.x86_64 libgcc1-5.5.0-1.mga6.x86_64 libstdc++6-5.5.0-1.mga6.x86_64 (gdb) bt #0 0x7662a818 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7662bf2a in __GI_abort () at abort.c:89 #2 0x75eba321 in mdb_assert_fail (env=0x645880, expr_txt=expr_txt@entry=0x75ebba91 "IS_LEAF(mp)", func=func@entry=0x75ebc2b0 <__func__.7255> "mdb_cursor_next", line=line@entry=5884, file=0x75ebb9e0 "mdb.c") at mdb.c:1536 #3 0x75eb1ad9 in mdb_cursor_next (mc=0x646000, key=0x7fffd740, data=data@entry=0x7fffd750, op=MDB_NEXT) at mdb.c:5884 #4 0x75eb0688 in mdb_cursor_get (mc=0x646000, key=key@entry=0x7fffd740, data=data@entry=0x7fffd750, op=op@entry=MDB_NEXT) at mdb.c:6404 #5 0x77991ab9 in Baloo::PostingDB::toTestMap (this=this@entry=0x7fffd820) at /usr/src/debug/baloo-5.42.0/src/engine/postingdb.cpp:281 #6 0x7799cbe6 in Baloo::Transaction::checkPostingDbinTermsDb (this=this@entry=0x7fffd9a0) at /usr/src/debug/baloo-5.42.0/src/engine/transaction.cpp:559 #7 0x00408491 in main (argc=2, argv=) at /usr/src/debug/baloo-5.42.0/src/tools/balooctl/main.cpp:324 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399964] New: Click Behavior settings should be in Dolphin's configuration dialogue
https://bugs.kde.org/show_bug.cgi?id=399964 Bug ID: 399964 Summary: Click Behavior settings should be in Dolphin's configuration dialogue Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY Right now KDE Plasma's Click behavior is located in: >> System Settings >> Workspace (section) >> Desktop Behavior >> Left column >> >> Workspace >> Not only is this so difficult to find, but it is also located in an unexpected place. Making the situation even worse. I understand we also open files and folders on desktop, but don't we we primarily use Dolphin to open files and folders? It only makes sense that we put this option in Dolphin's configuration, so that the learning curve and user experience can be greatly improved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399963] New: Click Behavior settings should be in Dolphin's configuration dialogue
https://bugs.kde.org/show_bug.cgi?id=399963 Bug ID: 399963 Summary: Click Behavior settings should be in Dolphin's configuration dialogue Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY Right now KDE Plasma's Click behavior is located in: >> System Settings >> Workspace (section) >> Desktop Behavior >> Left column >> >> Workspace >> Not only is this so difficult to find, but it is also located in an unexpected place. Making the situation even worse. I understand we also open files and folders on desktop, but don't we we primarily use Dolphin to open files and folders? It only makes sense that we put this option in Dolphin's configuration, so that the learning curve and user experience can be greatly improved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399962] New: Making Double-click to open files and folders as the default Click Behavior
https://bugs.kde.org/show_bug.cgi?id=399962 Bug ID: 399962 Summary: Making Double-click to open files and folders as the default Click Behavior Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY Right now KDE Plasma uses Single-click to open files and folders as the default Click Behavior. I suggest we change it to Double-click. Reasons: 1) That's how almost every other OS/DE do things, normal people expect such behavior 2) Single-click to open causes way too many accidental actions 3) Single-click to open breaks inline rename action (select and click to rename) 4) The option for it is way too difficult for a normal people to find: >> System Settings >> Workspace (section) >> Desktop Behavior >> Left column >> >> Workspace >> All and all, single-click opening is just way too confusing for normal people who used to a mouse-like pointing device in general. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399961] New: Suggestion on changing the default Desktop Session options
https://bugs.kde.org/show_bug.cgi?id=399961 Bug ID: 399961 Summary: Suggestion on changing the default Desktop Session options Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY Right now the Desktop Session page's default settings are: General: [X] Confirm logout [X] Offer shutdown options Default Leave Option: [X] End current session [ ] Turn off computer [ ] Restart computer On Login: [X] Restore previous session [ ] Restore manually saved session [ ] Start with an empty session The page can be found at: >> System Settings >> Workspace (section) >> Startup and Shutdown >> Left >> column >> Desktop Session >> SUGGESTION I suggest we change the default settings to: General: [ ] Confirm logout [X] Offer shutdown options Reason: I think for a logout action there are way too many steps. It is already super safe without the extra confirmation. Windows 10, macOS and GNOME are all very straight forward when it comes to logout. I suggest we streamline the user experience here. Default Leave Option: [ ] End current session [X] Turn off computer [ ] Restart computer Reason: Most users want to turn off the computer when they leave. It makes it easier to find what they want in the launcher too, because of this arrangement. On Login: [ ] Restore previous session [ ] Restore manually saved session [X] Start with an empty session Reason: Most users want to start a computer with a NEW, CLEAN session. Restoring the previous session introduces a lot of intricacies and gives a feeling of an OLD, UNCLEAN, UNSAFE session is being loaded. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399960] New: Screen Corner Activation delay's default value is too high
https://bugs.kde.org/show_bug.cgi?id=399960 Bug ID: 399960 Summary: Screen Corner Activation delay's default value is too high Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY The default value (150 ms) of Screen Corner's Activation delay is too high. Although a high value minimizes the risk of accidental triggering, it also makes intended triggering feels slow and unresponsive. It doesn't help that it was actually determined by time -- in normal user's perception it must be determined how far that push into the corner, only to be confused by the inconsistent outcome. I suggest we change it to: 50 ms. The related option can be found at: >> System Settings >> Workspace (section) >> Desktop Behavior >> Left column >> >> Screen Edges >> Other Settings (section) >> Tested under Manjaro 17.1.12 KDE. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #39 from Tyson Tan --- @Everybody Recently I've been asking around the programmers from a few very active groups I'm in. Their feedbacks are: 1) Yes we are using Window Action key all the time! (and yes, I'm sorry about doubting its usefulness) 2) I'm using ALT for my Window Action key. (he quickly added: But that does not represent the common choice in my workplace) 3) I'm a heavy KDE user. The first thing I do after installing the system is always changing the Window Action key from ALT to META. 4) Changing Window Action key is very easy for me to do. Why don't you change it? >> System Settings >> Workspace (section) >> Window Management >> * Left Column >> * >> Window Behavior >> * Tab * Window Actions >> Innter Window, Titlebar & >> Frame >> Modifier key >> * droplist* >> Meta (not I would call easy for normal people) 5) I think a Window Manager should not occupy ALT. A WM should use SUPER/META. That's just common sense. 6) I think modern OS/DE should strife towards practicality. 7) Kwin should release any key when an application requires it. So that's as far as I can go. As programmers their opinions are stilling falling on both sides. But I think that's compelling enough for me to agree that we can let Kwin stay the same as a measure to securing its current userbase. >From now on I will not push changes or argue with you about this matter. I think writing a guide for normal people to adapt to KDE Plasma seems to be a better solution. When your proposed solution on Kwin's code is done, We can try to pass your proposal to Krita developers. Please remember: Me and David Revoy are not Krita developers, we are only users with heavier-than-usual involvements. I don't think we can fully understand the technicality you mentioned here. I may try to let other non-KDE projects like GIMP/Inkscape/Blender know about it, hopefully they might consider adapting to kwin too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 399959] New: Could use a separator element that's just 18px of whitespace, not a line
https://bugs.kde.org/show_bug.cgi?id=399959 Bug ID: 399959 Summary: Could use a separator element that's just 18px of whitespace, not a line Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: n...@kde.org Target Milestone: Not decided Kirigami.Separator draws a line. It would be nice if we could get a version that's just 18px tall (i.e. gridUnit) of whitespace. Sometimes instead of a line you just want a bit of whitespace! This is what we use for QWidgets-based FormLayouts, such as the ones used in Dolphin and Spectacle's settings windows. It would be nice to make a Kirigami version of this for greater visual consistency. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #38 from Tyson Tan --- @Martin >> System Settings >> Workspace (section) >> Window Management >> * Left Column >> * >> Window Behavior >> * Tab * Window Actions >> Innter Window, Titlebar & >> Frame >> Modifier key >> * droplist* The droplist has no "Disable" option. So whether Meta or Alt is selected here, Meta/Alt + Arrow keys will still function as Window Action shortcuts. So there is no way Meta and Alt apps can coexist with our current design. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 399958] New: Consider making FormLayout centered by default
https://bugs.kde.org/show_bug.cgi?id=399958 Bug ID: 399958 Summary: Consider making FormLayout centered by default Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: n...@kde.org Target Milestone: Not decided In doing my first port to Kirigami.FormLayout, I'm very impressed so far. It's a nice API to work with. The only issue I ran into was that I had to manually add `anchors.horizontalCenter: parent.horizontalCenter` to get it to be centered, as the HIG prescribes in https://hig.kde.org/patterns/content/form.html. It would be nice if Kirigami FormLayouts centered themselves automatically unless overridden, just to cut down on the amount of boilerplate needed for implementation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399957] kcm-wacomtablet should be included by default
https://bugs.kde.org/show_bug.cgi?id=399957 --- Comment #1 from Tyson Tan --- CORRECTION: 3) If (1) and (2) are not feasible, keep "Graphics Tablet" page visible even when kcm-wacomtablet is absent, with instructions about installing kcm-wacomtablet can enable this page. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399957] New: kcm-wacomtablet should be included by default
https://bugs.kde.org/show_bug.cgi?id=399957 Bug ID: 399957 Summary: kcm-wacomtablet should be included by default Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY I suggest we include kcm-wacomtablet by default in System Settings. Because right now, it is very difficult for a new user to figure out what to do to make their graphics tablet work. Suggestions: 1) We include kcm-wacomtablet by default in System Settings 2) We tell distros that it depends on xf86-input-wacom and libwacom 3) If (1) and (2) are not feasible, keep "Graphics" page visible even when kcm-wacomtablet is absent, with instructions about installing kcm-wacomtablet can enable this page. By doing only point (3) below we can greatly improve the learning curve for our new users. Reported on Manjaro 17.1.12 KDE. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 377145] colord-kde should be installed by default
https://bugs.kde.org/show_bug.cgi?id=377145 Tyson Tan changed: What|Removed |Added CC||tyson...@mail.com --- Comment #3 from Tyson Tan --- (In reply to Jonathan Riddell from comment #1) > We only ship a very minimal set of software pre-installed, based around > choices made by Plasma and VDG teams. colour management is an advanced tool > most users have no need or understanding of. colord-kde depends on > gnome-color-manager which pulls in lots of extra deps. On Manjaro 17.1.12 KDE, colord-kde does not require gnome-color-manager. It's only an optional dependency for CALIBRATING the screen, and colord-kde's dialogue teaches user about this fact very well. colord-kde's most important function is to ASSIGN color profiles to displays. It does not require gnome-color-manager to perform this function. By not intalling colord-kde by default we take away the ability to assign color profile to displays. This is an ESSENTIAL function on every modern operating system. There is a reason why Windows, macOS, GNOME all has this very basic function built-in by default. I strongly suggest: 1) We reconsider the inclusion of colord-kde by default 2) We tell distros that: gnome-color-manager is only a optional dependency 3) If (1) and (2) are not feasible, keep "Color Corrections" page visible even when colord-kde is absent, with instructions about installing colord-kde can enable this page. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395671] Pressing enter key on lockscreen wont focus returning unlocking failed
https://bugs.kde.org/show_bug.cgi?id=395671 --- Comment #5 from Neousr --- Just tried this on neon unstable all the interactions/combinations work as expected (Enter, Intro and Escape). Waiting until this lands on 5.14.2. Appreciated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399956] New: On a newly installed system, multiple display arrangement is not remembered after restart
https://bugs.kde.org/show_bug.cgi?id=399956 Bug ID: 399956 Summary: On a newly installed system, multiple display arrangement is not remembered after restart Product: systemsettings Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyson...@mail.com Target Milestone: --- SUMMARY On a newly installed system, multiple display arrangement is not remembered after restart. Display arrangement buttons are being displayed upon every login, as if a new monitor is being connected while the system is running. To rectify this, user must click the display arrangement button once, like "Unify" but not "Keep unchanged". After that the arrangement can be remembered. If the user press "Keep unchanged" button, the same thing will happen every time upon login. STEPS TO REPRODUCE 1. Fresh install Manjaro 17.1.12 KDE on a multiple display PC 2. Change display arrangement in System Settings 3. Restart OBSERVED RESULT Display arrangement is not remembered. Display arrangement buttons are being displayed upon every login, as if a new monitor is being connected while the system is running. To rectify this, user must click the display arrangement button once, like "Unify" but not "Keep unchanged". After that the arrangement can be remembered. If the user press "Keep unchanged" button, the same thing will happen every time upon login. EXPECTED RESULT On a newly installed system, multiple display arrangement is remembered after restart SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399849] Baloo crashed after I delete a folder containing some files and subfolders
https://bugs.kde.org/show_bug.cgi?id=399849 --- Comment #8 from Nate Graham --- Ahh, thanks for the clarification. It's probably at least partly my fault that 367480 has PostingCodec::decode() in it. I'll be more careful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399849] Baloo crashed after I delete a folder containing some files and subfolders
https://bugs.kde.org/show_bug.cgi?id=399849 --- Comment #7 from Stefan Brüns --- (In reply to Stefan Brüns from comment #6) > No, only the *PositionCodec* - unfortunately, 367480 has instances of both. This one here has PostingCodec in KF5.50 and DocTermsCodec in KF5.51 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399849] Baloo crashed after I delete a folder containing some files and subfolders
https://bugs.kde.org/show_bug.cgi?id=399849 --- Comment #6 from Stefan Brüns --- No, only the *PositionCodec* - unfortunately, 367480 has instances of both. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 Martin Flöser changed: What|Removed |Added Component|decorations |window decoration Product|kwin|Breeze Assignee|kwin-bugs-n...@kde.org |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399849] Baloo crashed after I delete a folder containing some files and subfolders
https://bugs.kde.org/show_bug.cgi?id=399849 --- Comment #5 from Nate Graham --- Hmm, I thought we fixed the PostingCodec::decode() issue with Bug 367480 in Frameworks 5.51; this is from 5.50, before that fix went in. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 399896] kdeinit5 crashes in ThumbnailProtocol::createSubThumbnail() when opening a folder with a WMF file that has the .eps file extension
https://bugs.kde.org/show_bug.cgi?id=399896 Nate Graham changed: What|Removed |Added Summary|kdeinit5 crashes in |kdeinit5 crashes in |ThumbnailProtocol::createSu |ThumbnailProtocol::createSu |bThumbnail() when opening a |bThumbnail() when opening a |certain folder |folder with a WMF file that ||has the .eps file extension Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED CC||k...@privat.broulik.de --- Comment #4 from Nate Graham --- Thanks so much for the info! Very helpful. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 399955] New: Build is broken with trunk LLVM/Clang
https://bugs.kde.org/show_bug.cgi?id=399955 Bug ID: 399955 Summary: Build is broken with trunk LLVM/Clang Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.zele...@gmail.com CC: smart...@kde.org Target Milestone: --- Build is broken with trunk LLVM/Clang. I think will be good idea to run Include What You Use over Clazy code. In file included from src/checks/detachingbase.cpp:28: In file included from src/QtUtils.h:28: src/MacroUtils.h:66:9: error: unknown type name 'StringRef' StringRef macro = clang::Lexer::getImmediateMacroName(loc, context->getSourceManager(), context->getLangOpts()); ^ In file included from src/checks/detachingbase.cpp:28: In file included from src/QtUtils.h:29: src/FunctionUtils.h:107:5: error: unknown type name 'StringRef' StringRef methodName = method->getName(); ^ In file included from src/checks/manuallevel/container-inside-loop.cpp:23: src/ClazyContext.h:127:9: error: unknown type name 'StringRef' StringRef fileName((*file)->getName()); ^ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375321] When selecting a screen edge to invoke the window switcher, moving the mouse quickly shows and hides the switcher
https://bugs.kde.org/show_bug.cgi?id=375321 King changed: What|Removed |Added CC||rayfinkle2008-...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #309 from Michael Butash --- I've been waiting for general multi-monitor support to not suck since kde4, but to no avail with things like this, and more. They love tinkering with adding other crap to kde, but leave core functionality like multi-display broken at the best. I usually try a fresh kde a couple times a year under arch linux, see it's *still* broken, and go back to whatever DE sucks less at the time. Typically Cinnamon lately, at least it doesn't throw my windows around every day my displays power on, and compositor far more stable than I've ever seen kwin to last even a week before freaking out. I really like KDE, if it were usable more than a day or 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #308 from Michael Butash --- I've been waiting for general multi-monitor support to not suck since kde4, but to no avail with things like this, and more. They love tinkering with adding other crap to kde, but leave core functionality like multi-display broken at the best. I usually try a fresh kde a couple times a year under arch linux, see it's *still* broken, and go back to whatever DE sucks less at the time. Typically Cinnamon lately, at least it doesn't throw my windows around every day my displays power on, and compositor far more stable than I've ever seen kwin to last even a week before freaking out. I really like KDE, if it were usable more than a day or 3. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 360865] google-chrome don't honor default web browser KDE Plasma settings
https://bugs.kde.org/show_bug.cgi?id=360865 King changed: What|Removed |Added CC||rayfinkle2008-...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 399954] New: Default audio device is ignored
https://bugs.kde.org/show_bug.cgi?id=399954 Bug ID: 399954 Summary: Default audio device is ignored Product: plasma-pa Version: 5.14.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: now...@gmail.com Reporter: et...@ethanhussong.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY My default audio device is ignored. STEPS TO REPRODUCE 1. Set default audio device to one other than the one that is selected after a fresh installation. 2. Open an application and start playing audio (e.g. Clementine, Vivaldi browser) OBSERVED RESULT Application begins playing through the original default device and not the newly selected one. By selecting a different default, then selecting the desired default all playing applications will then begin playing through that device. EXPECTED RESULT Selected default device should play audio. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 53.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Certain applications will seem to retain settings once they are selected in the "Applications" section of the Audio settings. e.g. I can open Clementine and experience the bug, but if I set it on the application page it will start playing through that device even if the application is closed and reopened. Other applications lose this any time that the application stops playing long enough to disappear from the "Applications" settings page. e.g. Vivaldi can have a video playing and will default to the incorrect device. If it is set on the application page it will work fine. If the video is paused for a few moments and the application output disappears from the "Applications" page it will then start playing audio back to the incorrect (original default, before being changed) output device and needs to be set again every time the audio stream is restarted. Behavior is consistent across multiple distributions. Kubuntu 18.04.1 does not appear to have this issue, but Fedora 28, Manjaro KDE, and now KDE Neon do. Possibly related to Bug 396296 as I end up often seeing similar issues as described in this bug, but am not reporting on the same thing. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399926] Clear the search results when backspace key is used to clear the search field
https://bugs.kde.org/show_bug.cgi?id=399926 Aleix Pol changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Aleix Pol --- You need to press enter to clear the search. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399883] In new review form, content box have no hint of focus
https://bugs.kde.org/show_bug.cgi?id=399883 --- Comment #4 from Aleix Pol --- https://phabricator.kde.org/source/qqc2-desktop-style/ I suggest telling them to review what the style looks like on the Desktop style we use for QtQuick Controls. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399858] Plasma-Discover always shows updates
https://bugs.kde.org/show_bug.cgi?id=399858 Aleix Pol changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #5 from Aleix Pol --- No, don't worry, this a different bug. *** This bug has been marked as a duplicate of bug 395923 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395923] Port FlatpakBackend to use FlatpakTransaction: Installing steam doesn't pull nvidia binaries
https://bugs.kde.org/show_bug.cgi?id=395923 Aleix Pol changed: What|Removed |Added CC||b...@briandwright.com --- Comment #9 from Aleix Pol --- *** Bug 399858 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399953] New: libatomic breaks compilation in MacOS
https://bugs.kde.org/show_bug.cgi?id=399953 Bug ID: 399953 Summary: libatomic breaks compilation in MacOS Product: krita Version: git master Platform: Compiled Sources OS: OS X Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: a...@amyspark.me Target Milestone: --- SUMMARY Krita git master c2ea92c55535f00cf72661680e1ee8fb10116d74 cannot be compiled under MacOS, as libatomic is not available. See e.g. https://github.com/mavlink/mavros/issues/849. STEPS TO REPRODUCE 1. Upgrade local copy to c2ea92c55535f00cf72661680e1ee8fb10116d74. 2. Issue `cmake .` on the build folder. 3. Open Xcode and try building Krita. OBSERVED RESULT Build target kritaimage of project krita with configuration RelWithDebInfo Ld /Users/amalia/Desktop/krita/build/libs/image/RelWithDebInfo/libkritaimage.18.0.0.dylib normal x86_64 cd /Users/amalia/Desktop/krita/source export MACOSX_DEPLOYMENT_TARGET=10.12 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch x86_64 -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -L/Users/amalia/Desktop/krita/build/libs/image/RelWithDebInfo -F/Users/amalia/Desktop/krita/build/libs/image/RelWithDebInfo -F/usr/local/opt/qt5/lib -filelist /Users/amalia/Desktop/krita/build/libs/image/krita.build/RelWithDebInfo/kritaimage.build/Objects-normal/x86_64/kritaimage.18.0.0.LinkFileList -install_name /libkritaimage.18.0.0.dylib -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/widgets/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/psd/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/metadata/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/flake/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/command/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/pigment/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/widgetutils/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/odf/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/store/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/version/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/global/RelWithDebInfo -Xlinker -rpath -Xlinker /Users/amalia/Desktop/krita/build/libs/koplugin/RelWithDebInfo -mmacosx-version-min=10.12 -Xlinker -object_path_lto -Xlinker /Users/amalia/Desktop/krita/build/libs/image/krita.build/RelWithDebInfo/kritaimage.build/Objects-normal/x86_64/kritaimage.18.0.0_lto.o -single_module -multiply_defined suppress -dynamiclib -Wl,-headerpad_max_install_names -install_name @rpath/libkritaimage.18.dylib /Users/amalia/Desktop/krita/build/libs/widgets/RelWithDebInfo/libkritawidgets.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/psd/RelWithDebInfo/libkritapsd.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/metadata/RelWithDebInfo/libkritametadata.18.0.0.dylib /usr/local/lib/libboost_system-mt.dylib -latomic /usr/local/lib/libImath.dylib /usr/local/lib/libIlmImf.dylib /usr/local/lib/libIex.dylib /usr/local/lib/libHalf.dylib /usr/local/lib/libIlmThread.dylib /usr/local/lib/libfftw3.dylib /usr/local/Cellar/vc/1.3.3/lib/libVc.a /usr/local/lib/libgsl.dylib /usr/local/lib/libgslcblas.dylib /Users/amalia/Desktop/krita/build/libs/flake/RelWithDebInfo/libkritaflake.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/command/RelWithDebInfo/libkritacommand.18.0.0.dylib /usr/local/opt/qt5/lib/QtSvg.framework/QtSvg /usr/local/lib/libKF5Completion.5.50.0.dylib /Users/amalia/Desktop/krita/build/libs/pigment/RelWithDebInfo/libkritapigment.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/widgetutils/RelWithDebInfo/libkritawidgetutils.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/odf/RelWithDebInfo/libkritaodf.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/store/RelWithDebInfo/libkritastore.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/version/RelWithDebInfo/libkritaversion.18.0.0.dylib /Users/amalia/Desktop/krita/build/libs/global/RelWithDebInfo/libkritaglobal.18.0.0.dylib /usr/local/opt/qt5/lib/QtConcurrent.framework/QtConcurrent /usr/local/lib/libKF5Archive.5.50.0.dylib /usr/local/opt/qt5/lib/QtPrintSupport.framework/QtPrintSupport /usr/local/lib/libKF5ConfigGui.5.50.0.dylib /usr/local/lib/libKF5GuiAddons.5.50.0.dylib /usr/local/lib/libKF5WidgetsAddons.5.50.0.dylib /usr/local/opt/qt5/lib/QtXml.framework/QtXml /usr/local/lib/libKF5ItemViews.5.50.0.dylib /usr/local/opt/qt5/lib/QtWidgets.framework/QtWidgets /usr/local/opt/qt5/lib/QtGui.framework/QtGui /Users/amalia/Desktop/krita/build/libs/koplugin/RelWithDebInfo/libk
[frameworks-kiconthemes] [Bug 396990] [Regression from Frameworks 5.47 -> 5.48] Dolphin icons are incorrectly aligned if display scaling is used
https://bugs.kde.org/show_bug.cgi?id=396990 --- Comment #9 from Nate Graham --- I can no longer reproduce this issue with git master when doing `QT_SCALE_FACTOR=[anything] dolphin` or using the KScreen KCM's scaling UI. Icons now look correct at all scale factors for me. Is anyone else still able to reproduce this with KDE Frameworks 5.51 and/or git master? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 399952] PlasmaComponents Button: different button & icon size between PC2 with iconSource and PC3 with icon.name
https://bugs.kde.org/show_bug.cgi?id=399952 --- Comment #1 from Nate Graham --- > import org.kde.plasma.components 3.0 as PC2 Sigh, should of course be `import org.kde.plasma.components 2.0 as PC2` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399888] Missing icon in "Configure..." button
https://bugs.kde.org/show_bug.cgi?id=399888 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Have a patch: https://phabricator.kde.org/D16287 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 399952] New: PlasmaComponents Button: different button & icon size between PC2 with iconSource and PC3 with icon.name
https://bugs.kde.org/show_bug.cgi?id=399952
Bug ID: 399952
Summary: PlasmaComponents Button: different button & icon size
between PC2 with iconSource and PC3 with icon.name
Product: frameworks-plasma
Version: 5.51.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: components
Assignee: notm...@gmail.com
Reporter: n...@kde.org
Target Milestone: ---
Created attachment 115716
--> https://bugs.kde.org/attachment.cgi?id=115716&action=edit
Button and icon sizes: PC3 vs PC2
Consider the following two pieces of code in a Widget:
import org.kde.plasma.components 3.0 as PC2
PC2.Button {
iconSource: "configure"
text: i18nc("@action:button", "Configure...")
onClicked: {
plasmoid.action("configure").trigger();
}
}
import org.kde.plasma.components 3.0 as PC3
PC3.Button {
icon.name: "configure"
text: i18nc("@action:button", "Configure...")
onClicked: {
plasmoid.action("configure").trigger();
}
}
The PC2 version produces a reasonably-sized button with a reasonably-sized icon
in it. The PC3 version will produce a larger button with a larger icon. See
attached screenshot.
For a concrete example, see the weather and comic widgets.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 399951] New: Upload Schemes does noting.
https://bugs.kde.org/show_bug.cgi?id=399951 Bug ID: 399951 Summary: Upload Schemes does noting. Product: systemsettings Version: 5.14.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: andythe_gr...@pm.me CC: jpwhit...@kde.org Target Milestone: --- SUMMARY When edit an existing color scheme and then press " * Upload Scheme" noting happen. I tried start systemsettings5 from terminal this is what I get checking permissions of "/usr/share/color-schemes/KritaDarker.colors" path for color scheme "Krita darker" couldn't be found The second line immediately appear when I press upload scheme SOFTWARE VERSIONS (available in About System) openSUSE Tumbleweed KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 Kernel Version: 4.18.12-1-default OS Type: 64 bit -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399764] i18n: No support for plurals in "... seconds"
https://bugs.kde.org/show_bug.cgi?id=399764 Nate Graham changed: What|Removed |Added Version Fixed In||18.12.0 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/spe ||ctacle/f53c2d09f30b370a42f1 ||c3fb40d26b381d853e0e Resolution|--- |FIXED --- Comment #2 from Nate Graham --- Git commit f53c2d09f30b370a42f1c3fb40d26b381d853e0e by Nate Graham. Committed on 17/10/2018 at 22:31. Pushed by ngraham into branch 'master'. Fix localization for number of seconds in spinbox Summary: FIXED-IN: 18.12.0 Test Plan: Works for English:: ``` 0.5 seconds 1 second 1.5 seconds 2 seconds 2.5 seconds [etc] ``` Reviewers: #localization, #spectacle, aspotashev, aacid Reviewed By: #localization, aacid Subscribers: stikonas, sdepiets, kde-i18n-doc, aacid Tags: #spectacle Differential Revision: https://phabricator.kde.org/D16186 M +4-3src/Gui/SmartSpinBox.cpp https://commits.kde.org/spectacle/f53c2d09f30b370a42f1c3fb40d26b381d853e0e -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399950] Window that indicates the progress of file operations appears together "File already exists" dialog if data transfer tracking is disabled in task manager and notifications apple
https://bugs.kde.org/show_bug.cgi?id=399950 Patrick Silva changed: What|Removed |Added Version|18.08.0 |18.08.2 Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399950] New: Window that indicates the progress of file operations appears together "File already exists" dialog if data transfer tracking is disabled in task manager and notifications
https://bugs.kde.org/show_bug.cgi?id=399950 Bug ID: 399950 Summary: Window that indicates the progress of file operations appears together "File already exists" dialog if data transfer tracking is disabled in task manager and notifications applet Product: dolphin Version: 18.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 115715 --> https://bugs.kde.org/attachment.cgi?id=115715&action=edit screenshot Steps to disable data transfer tracking in task manager and notifications applet: Right click on notifications applet in the system tray -> Notifications Settings -> uncheck "Track file transfers and other jobs", click "ok" button. Right click the task manager in the plasma panel, select "configure task manager...", uncheck "Show progress and status information in task buttons", click "ok" button and restart plasma session. Steps to reproduce: open dolphin copy some file to another folder repeat previous step OBSERVED RESULT "Copying" window appears and remains visible until I click some button in "File already exists" dialog. See the screenshot. EXPECTED RESULT "Copying" window only should appear after dolphin start the file operation. SOFTWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 399949] New: Can't extract from files with extension ".zip.NNN"
https://bugs.kde.org/show_bug.cgi?id=399949 Bug ID: 399949 Summary: Can't extract from files with extension ".zip.NNN" Product: ark Version: 17.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: rafael.linux.u...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY Some clients send me zipped files volumes with extension filename.zip.001 , filename.zip.002 and so on. Ark is unable to unzip those files in any way. I needed to install Peazip to uncompress the content of that kind of zip volumes. STEPS TO REPRODUCE 1. As usual, right click on first volume file 2. Select "Extract here" OBSERVED RESULT Ark doesn't recognize the file as a zip file EXPECTED RESULT Extract content of the pack of ZIP files SOFTWARE VERSIONS KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION After trying several ways to make Ark extract the files (renaming files as ZIP, 001, 002 ... ) and after contact with clients that related that they were able to extract the content, I decided to try Peazip, that finally is able to extract correctly the content, following the same steps but selecting PeaZip to extract the files. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 399948] New: Phone not showed on "Open device list" with or w/o kio_mtp installed
https://bugs.kde.org/show_bug.cgi?id=399948 Bug ID: 399948 Summary: Phone not showed on "Open device list" with or w/o kio_mtp installed Product: krusader Version: 2.7.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY When I connect my phone thru USB cable, Dolphin show my device despite I have or not kio_mtp installed. I can connect to my phone using Dolphin. However, even if I close Dolphin, disconnect my phone and connect it again, Krusader doesn't show my phone in the device list. STEPS TO REPRODUCE 1. Connect phone thru USB 2. Open Krusader 3. Open device list in Krusader OBSERVED RESULT Phone is not showed in devices list EXPECTED RESULT Phone should show my phone icon too SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.46 Qt Version: 5.3.4 ADDITIONAL INFORMATION Dolphin shows the phone device just when plugged, with or without kio_mtp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399947] New: [Qt 5.12 beta2] "Minimize all windows" widget stopped working on Wayland
https://bugs.kde.org/show_bug.cgi?id=399947 Bug ID: 399947 Summary: [Qt 5.12 beta2] "Minimize all windows" widget stopped working on Wayland Product: plasmashell Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Created attachment 115714 --> https://bugs.kde.org/attachment.cgi?id=115714&action=edit error message After upgrade to Qt 5.12 beta2 I get the error message shown in my screenshot when I try to use the "Minimize all windows" widget by pressing its shortcut or by clicking its icon placed in plasma panel. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392965] save a copy (of the project file) /2018
https://bugs.kde.org/show_bug.cgi?id=392965 --- Comment #2 from peter josvai --- (In reply to emohr from comment #1) > Why not use "save as" and rename the saved file? well... you work on a project... and you want to keep working on it... but you know that it is good so far... and you want to have a copy of it so that you could get back there if you need to... "save as" means: "save as" + close + open the previous file... MANY applications have "save a copy" function so, in short: Why not? because it is NOT the same.. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #27 from roger.li...@cedalo.com --- I've just added some updated patches. The two small ones add some coregrind features that are needed for this tool - implementing VG_(apply_ExeContext)() and adding a way for a tool to force a syscall to fail in the pre_syscall callback. The big one is the patch for the tool. This now has a lot of control over how the allocation failures occur. It can be turned on/off at the start of the run, set to toggle on entry and exit from named functions, limited to a certain number of failures per run, automatically accepted based on size of allocation requested, automatically accepted based on matching function name, automatically accepted based on a dice roll, or to some degree controlled with gdb or client requests. It also implements syscall failures, which is turned off by default. If you turn it on, then all syscalls (bar those that are marked as always succeeding) will fail with errno set to EINVAL. You can change to have all syscalls fail with a different errno, and/or set individual syscalls to fail with specific errors. You can set all syscalls with a matching name to be automatically accepted. You can set all syscalls that aren't given a specific error to be automatically accepted. You can accept based on the number of failures in a run, or based on a dice roll, or to some degree controlled with gdb or client requests. There are tests for most features, but they haven't been tried on different Linux releases or distributions (Kubuntu 18.04 only) nor on Mac or Solaris. The documentation is pretty complete with examples for most situations. The bits that are missing - I've taken a lot of code from callgrind to support the function enter/leave feature, but I may have taken too much out. The bit that needs looking at is function name wildcard support which I initially removed but now see it was included in callgrind to allow C++ names to be dealt with correctly. That needs putting back in, but I could do with a break from this for a few days at least and was hoping for some feedback. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399888] Missing icon in "Configure..." button
https://bugs.kde.org/show_bug.cgi?id=399888 Thomas Surrel changed: What|Removed |Added CC||thomas.sur...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397707] While mounting a slow USB device, the plasmashell and dolphin process status become "uninterruptible sleep" (freeze)
https://bugs.kde.org/show_bug.cgi?id=397707 alex...@gmx.net changed: What|Removed |Added Version|unspecified |5.14.0 Component|general |general CC||plasma-b...@kde.org Target Milestone|--- |1.0 Assignee|dolphin-bugs-n...@kde.org |k...@davidedmundson.co.uk Product|dolphin |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 397707] While mounting a slow USB device, the plasmashell and dolphin process status become "uninterruptible sleep" (freeze)
https://bugs.kde.org/show_bug.cgi?id=397707 --- Comment #7 from alex...@gmx.net --- Mounting the SD card of the device in the Konsole results in a freezing plasmashell as well. That means it's not Dolphin specific. @Stefan Brüns, in case you are strongly interested in debugging that issue, I could lend you my device as I am located very closely to you. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind
https://bugs.kde.org/show_bug.cgi?id=396290 roger.li...@cedalo.com changed: What|Removed |Added Attachment #114630|0 |1 is obsolete|| Attachment #114817|0 |1 is obsolete|| --- Comment #26 from roger.li...@cedalo.com --- Created attachment 115713 --> https://bugs.kde.org/attachment.cgi?id=115713&action=edit Tool patch October 2018 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #25 from roger.li...@cedalo.com --- Created attachment 115712 --> https://bugs.kde.org/attachment.cgi?id=115712&action=edit Patch that implements VG_(apply_ExeContext)(). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #24 from roger.li...@cedalo.com --- Created attachment 115711 --> https://bugs.kde.org/attachment.cgi?id=115711&action=edit Patch that allows tools to set a syscall error. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395671] Pressing enter key on lockscreen wont focus returning unlocking failed
https://bugs.kde.org/show_bug.cgi?id=395671 Nate Graham changed: What|Removed |Added Version Fixed In||5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 399810] URL recognition + underline on hover + clickable
https://bugs.kde.org/show_bug.cgi?id=399810 Thomas Surrel changed: What|Removed |Added CC||thomas.sur...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 330536] Bluetooth device link
https://bugs.kde.org/show_bug.cgi?id=330536 alex...@gmx.net changed: What|Removed |Added Platform|openSUSE RPMs |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 330536] Bluetooth device link
https://bugs.kde.org/show_bug.cgi?id=330536 alex...@gmx.net changed: What|Removed |Added CC||alex...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395671] Pressing enter key on lockscreen wont focus returning unlocking failed
https://bugs.kde.org/show_bug.cgi?id=395671 Thomas Surrel changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-workspace/754efdedd4ee1 ||b7dbafda06bd7858e2f51346ea0 --- Comment #4 from Thomas Surrel --- Git commit 754efdedd4ee1b7dbafda06bd7858e2f51346ea0 by Thomas Surrel. Committed on 17/10/2018 at 20:53. Pushed by thsurrel into branch 'Plasma/5.14'. [Lock Screen] Do not try to unlock when unvisible Summary: In the lock screen, pressing the enter key while the UI is not yet visible ends up trying to unlock (and would usually fail because the password field is empty). Ensure that the UI is visible before unlocking. Test Plan: Lock the session, press enter. The UI should appear without any "Unlocking failed" message. Reviewers: #plasma, #vdg, ngraham, davidedmundson Reviewed By: #plasma, #vdg, ngraham, davidedmundson Subscribers: ngraham, davidedmundson, abetts, filipf, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D16219 M +1-0lookandfeel/contents/lockscreen/LockScreenUi.qml M +6-1lookandfeel/contents/lockscreen/MainBlock.qml https://commits.kde.org/plasma-workspace/754efdedd4ee1b7dbafda06bd7858e2f51346ea0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399676] Not comfortable removing icons set
https://bugs.kde.org/show_bug.cgi?id=399676 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- @Patrick Silva Hmm. You are right. I didn't notice it till you didn't tell me :/. I suppose the reason was that this icon is transparent and when icons are bright then "remove icon" is barely visible. Anyway contrast is very low and hence the problem of noticing this icon. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399913] Make drag drop, copy and paste work more transparently with desktop/filemanager
https://bugs.kde.org/show_bug.cgi?id=399913 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Which file manager do you use? Ctrl-C and Ctrl-V works very well with Dolphin. It also works under Windows with the File Explorer. Yes, drag & drop to outside of digiKam is a copy action. There are users who want to drag their image to Gimp or another application and that only works with a copy action. We will not change that. Maik -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398900] "Quick open" got much (100x) slower with 18.08 [regression]
https://bugs.kde.org/show_bug.cgi?id=398900 --- Comment #7 from Alexander Neundorf --- I'll give it a try. I had a closer look at the performance issue. The project were it is slow is quite big, it contains around 19.000 files. On the slow machine/installation, void KateQuickOpen::update() takes 10 seconds. All the time is spent in the loop which puts the project files into the model: foreach(const QString & file, projectFiles) My two installations (a relatively old version and one from current git) both run fast, here this loop over 19.000 files takes 100 milliseconds. I.e. it is 100 times faster. In the slow install, it seems like most of the time is spent when putting the two QStandardItems into the model. Below are three backtraces from within those 10 seconds. They are all QStandardItemPrivate::setChild() which emits QAbstractItemModel::layoutChanged(...). Updating a layout 19.000 times probably can take some time. This would be around 0.5 milliseconds per update. But why is it slow on one setup and fast on another ? Could this be related to the "environment", the window manager (fast with kwin, slow with i3 and xfce?), Qt options, X driver ? #0 0x730d0d27 in QSortFilterProxyModelPrivate::create_mapping(this=this@entry=0x56059490, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:375 #1 0x730d15f9 in QSortFilterProxyModelPrivate::update_persistent_indexes(QVector > const&) () at itemmodels/qsortfilterproxymodel.cpp:1079 #2 0x730d1c79 in QSortFilterProxyModelPrivate::_q_sourceLayoutChanged (this=0x56059490, sourceParents=..., hint=) at itemmodels/qsortfilterproxymodel.cpp:1454 #3 0x730d6823 in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:174 #4 0x7311ae1e in QMetaObject::activate(QObject*, int, int, void**)() at kernel/qobject.cpp:3771 #5 0x7311b4ab in QMetaObject::activate (sender=, m=m@entry=0x7337bbe0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffd3f0) at kernel/qobject.cpp:3633 #6 0x730ae5ba in QAbstractItemModel::layoutChanged(this=, _t1=..., _t2=, _t2@entry=QAbstractItemModel::NoLayoutChangeHint) at .moc/moc_qabstractitemmodel.cpp:566 #7 0x73ce89ae in QStandardItemPrivate::setChild(int, int, QStandardItem*, bool) () at itemmodels/qstandarditemmodel.cpp:147 #8 0x555ca30c in KateQuickOpen::update (this=0x560493a0) at /usr/src/debug/kate-18.08.2-1.fc28.x86_64/kate/katequickopen.cpp:258 #9 0x555944b4 in KateMainWindow::slotQuickOpen (this=0x55a44fc0) at /usr/src/debug/kate-18.08.2-1.fc28.x86_64/kate/katemainwindow.cpp:1144 #0 0x730be222 in mergeIndexes(QVector const&) () at itemmodels/qitemselectionmodel.cpp:967 #1 0x730c4236 in QItemSelectionModelPrivate::_q_layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () at itemmodels/qitemselectionmodel.cpp:1085 #2 0x730c489b in QItemSelectionModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at itemmodels/qitemselectionmodel.h:148 #3 0x7311ae1e in QMetaObject::activate(QObject*, int, int, void**)() at kernel/qobject.cpp:3771 #4 0x7311b4ab in QMetaObject::activate(sender=sender@entry=0x560613c0, m=m@entry=0x7337bbe0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffd260) at kernel/qobject.cpp:3633 #5 0x730ae5ba in QAbstractItemModel::layoutChanged (this=this@entry=0x560613c0, _t1=..., _t2=, _t2@entry=QAbstractItemModel::NoLayoutChangeHint) at .moc/moc_qabstractitemmodel.cpp:566 #6 0x730d1ca4 in QSortFilterProxyModelPrivate::_q_sourceLayoutChanged (this=0x5605b480, sourceParents=..., hint=) at itemmodels/qsortfilterproxymodel.cpp:1463 #7 0x730d6823 in QSortFilterProxyModel::qt_static_metacall (_o=, _c=, _id=, _a=) at itemmodels/qsortfilterproxymodel.h:174 #8 0x7311ae1e in QMetaObject::activate(QObject*, int, int, void**)() at kernel/qobject.cpp:3771 #9 0x7311b4ab in QMetaObject::activate (sender=, m=m@entry=0x7337bbe0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffd3f0) at kernel/qobject.cpp:3633 #10 0x730ae5ba in QAbstractItemModel::layoutChanged(this=, _t1=..., _t2=, _t2@entry=QAbstractItemModel::NoLayoutChangeHint) at .moc/moc_qabstractitemmodel.cpp:566 #11 0x73ce89ae in QStandardItemPrivate::setChild(int, int, QStandardItem*, bool) () at itemmodels/qstandarditemmodel.cpp:147 #12 0x555ca322 in KateQuickOpen::update (this=0x56056380) at /usr/src/debug/kate-18.08.2-1.fc28.x86_64/kate/katequickopen.cpp:259 #13 0x555944b4 in KateMainWindow::slotQuickOpen (this=0x55a44270) at /usr/src/debug/kate-18.08.2-1.fc28.x86_64/kate/katemainwindow.cpp:1144 #0 0x730ceb72 in QVector::fill (asize=-1, from=, this=0x5654ccb0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:61 #1 QSortFilterProxyModelPriva
[kwin] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 Patrick Silva changed: What|Removed |Added Version|5.14.0 |5.14.1 --- Comment #5 from Patrick Silva --- Now I see the same bug on Wayland after change fonts DPI to 120. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 394765] Paste doesn't work in libreoffice with wayland
https://bugs.kde.org/show_bug.cgi?id=394765 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- I can't paste text copied from kate running under X11 (started with 'QT_QPA_PLATFORM=xcb kate') into lo writer running natively on Wayland or vice-versa. Context menu of the destination app shows enabled "Paste" entry but it does not work. I use libre office 6.1.2.1, kate 18.08.2. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399613] user-trash should not look like a folder at large sizes
https://bugs.kde.org/show_bug.cgi?id=399613 --- Comment #4 from Nate Graham --- (In reply to Ivan Čukić from comment #3) > > I thought the trash was a folder? > > Even if it was, that is a technicality. The icon should reflect what it is > used as, and it is not used as a normal folder. Exactly. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399613] user-trash should not look like a folder at large sizes
https://bugs.kde.org/show_bug.cgi?id=399613 Ivan Čukić changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #3 from Ivan Čukić --- > I thought the trash was a folder? Even if it was, that is a technicality. The icon should reflect what it is used as, and it is not used as a normal folder. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399613] user-trash should not look like a folder at large sizes
https://bugs.kde.org/show_bug.cgi?id=399613 Noah Davis changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #2 from Noah Davis --- (In reply to Nate Graham from comment #0) > Right now the `user-trash` icon looks like a trash can at small sizes but > starts looking like a folder with a trash icon in it at large sizes. This is > undesirable; the trash is really not something to be thought of as a folder. > We should make its large size stop looking like a folder. Instead, it should > be a pretty full-color Breeze-style trash can. I thought the trash was a folder? If that is not how it works, then I agree. If it is a folder, then I think the icon should stay a folder. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop
https://bugs.kde.org/show_bug.cgi?id=384376 Christoph Feck changed: What|Removed |Added CC||chicopsych...@gmail.com --- Comment #15 from Christoph Feck --- *** Bug 399859 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 399859] KDE desktop in ubuntu
https://bugs.kde.org/show_bug.cgi?id=399859 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384376 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 399939] Feature request. Possibility select and copy to clipboard data from info pages
https://bugs.kde.org/show_bug.cgi?id=399939 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 366266 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 366266] Add right-click context menu or button to copy system info
https://bugs.kde.org/show_bug.cgi?id=366266 Christoph Feck changed: What|Removed |Added CC||fuxfwgc4a2i...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 399939 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 399946] New: [Feature request] Dark mode for websites
https://bugs.kde.org/show_bug.cgi?id=399946 Bug ID: 399946 Summary: [Feature request] Dark mode for websites Product: Falkon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: joaopauloa...@gmail.com Target Milestone: --- An extension that enables night mode creating dark themes for websites. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=381850 --- Comment #5 from Edward Tomasz Napierala --- FWIW, I'm wondering if it could have been fixed in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181741. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 399069] allow edit metadata
https://bugs.kde.org/show_bug.cgi?id=399069 Clint Moyer changed: What|Removed |Added CC||cont...@clintmoyer.com --- Comment #2 from Clint Moyer --- Gwenview uses Exiv2 to interpret image metadata. http://www.exiv2.org/metadata.html We will need an interface to use the edit functions. I like the idea. Something similar can be done from the command line like $ exiv2 modify --Modify 'set Exif.Image.Artist "Famous Artist"' testimage.jpg -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #12 from Patrick Silva --- (In reply to Ardith Metz from comment #11) > Interestingly the crash happens only when hovering over scrollbar minimap is > the first action I do after opening file in kate directly. > > If I simply click inside the document body or click somewhere in kate > toolbar and then hover over scrollbar minimap the crash doesn't happen. > > It also doesn't happen when I start kate with empty session and open > document trough File -> Open. I can confirm on my system. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.12.0 beta2 KDE Frameworks Version: 5.51.0 Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f00dd0d9800 (LWP 3208))] Thread 3 (Thread 0x7f00d23df700 (LWP 3210)): #0 0x7f00e22feafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f00d29cc17c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f00d29cbeb8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f00e22f8a9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f00e381db23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f00da263700 (LWP 3209)): #0 0x7f00e3812c21 in poll () from /usr/lib/libc.so.6 #1 0x7f00e1890ee0 in g_main_context_poll (priority=, n_fds=1, fds=0x7f00d4003ce0, timeout=, context=0x7f00d4000bf0) at ../glib/glib/gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7f00d4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3915 #3 0x7f00e1890fce in g_main_context_iteration (context=0x7f00d4000bf0, may_block=1) at ../glib/glib/gmain.c:3981 #4 0x7f00e3d47624 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f00e3cf065c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f00e3b34599 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f00e3fb8ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f00e3b3599c in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f00e22f8a9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f00e381db23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f00dd0d9800 (LWP 3208)): [KCrash Handler] #6 0x5644d7ba47b0 in ?? () #7 0x7f00e3cfae59 in QMetaObject::cast(QObject const*) const () from /usr/lib/libQt5Core.so.5 #8 0x7f00e48227b4 in QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7f00e4225765 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5 #10 0x7f00e422a33e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #11 0x7f00e4203bac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #12 0x7f00dcd44ce1 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #13 0x7f00e188f3cf in g_main_dispatch (context=0x5644d70ca3a0) at ../glib/glib/gmain.c:3182 #14 g_main_context_dispatch (context=context@entry=0x5644d70ca3a0) at ../glib/glib/gmain.c:3847 #15 0x7f00e1890f89 in g_main_context_iterate (context=context@entry=0x5644d70ca3a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3920 #16 0x7f00e1890fce in g_main_context_iteration (context=0x5644d70ca3a0, may_block=1) at ../glib/glib/gmain.c:3981 #17 0x7f00e3d47609 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #18 0x7f00e3cf065c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #19 0x7f00e3cf8966 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #20 0x5644d5a53072 in ?? () #21 0x7f00e3746223 in __libc_start_main () from /usr/lib/libc.so.6 #22 0x5644d5a547ae in _start () [Inferior 1 (process 3208) detached] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396276] Increased font DPI not recognized by Gtk applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=396276 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399945] New: Panel & other desktop functionality hang following network drop if CIFS mounted SMB directory exists
https://bugs.kde.org/show_bug.cgi?id=399945 Bug ID: 399945 Summary: Panel & other desktop functionality hang following network drop if CIFS mounted SMB directory exists Product: plasmashell Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: d...@aninstanceofme.com Target Milestone: 1.0 If network connection is lost while a SMB share is mounted with CIFS, or the SMB share becomes unavailable on the network for other reasons, the panel and other desktop functionality hangs for several minutes. During this time, attempting to open the menu opens only a blank, semi-transparent pane, which sticks in the 'open' position. Clicking other panel object or tray items - such as the 'network manager' icon, yields no response. Dolphin becomes unresponsive. In short, all desktop environment graphical elements are rendered almost entirely dysfunctional. Konsole does still work to a point, however attempting to enter or list the SMB directory hangs the session. In that case, another terminal session (tab or window) needs to be opened to resume using Konsole. After several minutes of this hang, normal service appears to be resumed. STEPS TO REPRODUCE 1. Mount an SMB share with CIFS. 2. Disconnect from the network. 3. Attempt to open the main menu on the panel. OBSERVED RESULT: As summarised above. EXPECTED RESULT: Desktop functionality remains unaffected by network loss and associated loss to access to the source of the CIFS mounted SMB share. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 399944] New: Properties and Information can probably be combined
https://bugs.kde.org/show_bug.cgi?id=399944 Bug ID: 399944 Summary: Properties and Information can probably be combined Product: gwenview Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: cont...@clintmoyer.com Target Milestone: --- SUMMARY This may be biased towards my own environment. It seems there is a lot of excess space in the sidebar, which defaults to the "Information" tab when viewing files or directories. In particular it seems most objects lack metadata, and the "Description" metadata seems particularly unused/unloved. Conversely, to view "Properties" users must either right click the object or go to File > Properties. It seems intuitively this information should be available alongside the "Information", and the user shouldn't be expected to take strange routes to reach Properties. We could add the Properties as a tab or merge into "Information". STEPS TO REPRODUCE 1. Browse to a file or directory OBSERVED RESULT Must right-click or go to "File" to reach Properties EXPECTED RESULT Ideally this would be available in the sidebar or even merged with Information. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399943] New: kdeconnect quits unexpectedly
https://bugs.kde.org/show_bug.cgi?id=399943 Bug ID: 399943 Summary: kdeconnect quits unexpectedly Product: kdeconnect Version: 1.3.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: i...@bluelupo.net Target Milestone: --- Created attachment 115710 --> https://bugs.kde.org/attachment.cgi?id=115710&action=edit Dialogbox Screenshot If you want to access the smartphone with kdeconnect from the control panel or from the file manager Dolphin, a dialog box opens with the error message: --- The process for the Protocol kdeconnect: // 637813d43352f8c8 was quit unexpectedly. --- I can reproduce the error at any time. Thus, it is no longer possible to access the smartphone from the KDE desktop. Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-36-generic Plasma : 5.14.0 Qt : 5.11.1 KF : 5.51.0 Kwin: 5.14.0 Akonadi : 5.9.2 Kmail : 5.9.2 What can I do to prevent the error from occurring? regards Michael -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 399942] New: Gwenview does not work with gstreamer
https://bugs.kde.org/show_bug.cgi?id=399942 Bug ID: 399942 Summary: Gwenview does not work with gstreamer Product: gwenview Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: cont...@clintmoyer.com Target Milestone: --- SUMMARY Videos do not play with the Gstreamer Phonon backend. This is highly pronounced for users NOT using KDE as their desktop environment. Gwenview only works with the VLC backend for Phonon. Users not running KDE will not be able to switch their Phonon backend, as they have no access to Kcontrol/Phonon settings panel. Most operating systems offer the option between a Gstreamer or VLC backend for Phonon (a QT based API). Most operating systems default to using gstreamer to avoid proprietary codecs. Users who want to run Gwenview will have to first remove phonon-qt5-gstreamer and then install phonon-qt5-vlc, before installing Gwenview to use the right backend. STEPS TO REPRODUCE 1. If phonon-qt5-vlc exists on your machine, remove it 2. Install phonon-qt5-gstreamer 3. Install Gwenview 4. When running Gwenview, will not be able to load videos OBSERVED RESULT Videos not playing with the often standard Gstreamer backend for Phonon EXPECTED RESULT Videos should play -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399941] New: Broken fonts during scrolling Desktop Effects settings
https://bugs.kde.org/show_bug.cgi?id=399941 Bug ID: 399941 Summary: Broken fonts during scrolling Desktop Effects settings Product: systemsettings Version: 5.8.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fuxfwgc4a2i...@gmail.com Target Milestone: --- Created attachment 115709 --> https://bugs.kde.org/attachment.cgi?id=115709&action=edit broken fonts SUMMARY Broken fonts during scrolling happen only in System settings -> Desktop Behavior -> Desktop Effects. Everywhere else scrolling ok.Example screen-shot in attachment. STEPS TO REPRODUCE 1. open System settings -> Desktop Behavior -> Desktop Effects 2. try to scroll with with mouse wheel up and down OBSERVED RESULT Ugly broken fonts. Which in some positions of mouse wheel become nice looking. EXPECTED RESULT Nice and clean fonts. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 3.8.6 KDE Frameworks Version: 5.28.0 Qt Version: 5.7.1 ADDITIONAL INFORMATION As i seen in Internet it is very very old bug. Which not fixed during ages. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399941] Broken fonts during scrolling Desktop Effects settings
https://bugs.kde.org/show_bug.cgi?id=399941 yP6pxFJmSpO2xZwPW changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371526] Improvement: Unify Library and Project Bin buttons position
https://bugs.kde.org/show_bug.cgi?id=371526 emohr changed: What|Removed |Added Keywords||junior-jobs CC||fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 360049] WISHLIST - new feature - Ability to import clips directly to timeline
https://bugs.kde.org/show_bug.cgi?id=360049 emohr changed: What|Removed |Added Keywords||junior-jobs CC||fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356034] SUGGESTION: transition UI: project-specific wipes
https://bugs.kde.org/show_bug.cgi?id=356034 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353051] Consider having Play button and SPACEBAR in Project Monitor play project from the beginning of timeline
https://bugs.kde.org/show_bug.cgi?id=353051 emohr changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363409] A little clean-up on new tabs-on-top layout
https://bugs.kde.org/show_bug.cgi?id=363409 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352409] SUGGESTION: Add markers at video gaps
https://bugs.kde.org/show_bug.cgi?id=352409 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
