[kdenlive] [Bug 408386] New: Multiple icons missing throughout the application, notably the Main Toolbar
https://bugs.kde.org/show_bug.cgi?id=408386 Bug ID: 408386 Summary: Multiple icons missing throughout the application, notably the Main Toolbar Product: kdenlive Version: 19.04.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: michaelk9...@gmail.com Target Milestone: --- Created attachment 120629 --> https://bugs.kde.org/attachment.cgi?id=120629=edit Screenshot w/ labels of kdenlive UI bugs and issues SUMMARY After updating kdenlive to 19.04.1 from 18.12.X, my Color Theme, Layout, and Main Toolbar were reset. With the biggest issue being various icons are either invisible, or replaced with text. I was able to recover everything from selecting [View > Load Layout], [Settings > Color Theme], and [Settings > Configure Toolbars...]. However, I was not able to find a fix for the icon issue. I have yet to rollback a version. STEPS TO REPRODUCE 1. Setup kdenlive 18.12.X w/ a color theme prefix, custom layout, and custom toolbars 2. Update to kdenlive 19.04.1, the issue will be apparent. OBSERVED RESULT Lack of icons and automatic Color Theme, Layout, and Toolbar recovery from previous version. EXPECTED RESULT (Explained above) SOFTWARE/OS VERSIONS Windows: 10 Pro for Workstations (1809) macOS: ~ Linux/KDE Plasma: ~ (available in About System) KDE Plasma Version: ~ KDE Frameworks Version: "5.57.0" Qt Version: "5.12.3 (built against 5.12.3)" ADDITIONAL INFORMATION - Also found in [Help > About Kdenlive > Libraries], "The windows windowing system" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 408188] New: Make it easier to resize a window via mouse / Usability
https://bugs.kde.org/show_bug.cgi?id=408188 Bug ID: 408188 Summary: Make it easier to resize a window via mouse / Usability Product: frameworks-kwindowsystem Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: off...@mikemitterer.at Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to resize a window without using a cryptic key-combination - use just the mouse 2. 3. OBSERVED RESULT Very hard - you need to fiddle around the window border to find the invisible, one pixel line that lets you grab the border to resize the windows EXPECTED RESULT Set the tolerance for the "grab"-Area higher SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15 ADDITIONAL INFORMATION I think you have a strong focus on usability. This problem should be really on top of your list. It should not be necessary to know the keyboard shortcut to resize a window Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406318] Access Denied
https://bugs.kde.org/show_bug.cgi?id=406318 --- Comment #8 from Mike --- It saves in the Documents folder albeit it did not do it the first time I tried. I made a sub-folder for Krita work and it saved there as well. Thanks for your help. Best Mike -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406318] Access Denied
https://bugs.kde.org/show_bug.cgi?id=406318 --- Comment #4 from Mike --- It behaves this way with all folders...Krita is the only program with this issue...as stated previously, I can see hidden files as well via the save dialog box -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406318] Access Denied
https://bugs.kde.org/show_bug.cgi?id=406318 --- Comment #1 from Mike --- Expected result would be to have my work saved. I've tried saving in various formats and no results. Export yields same results. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406318] New: Access Denied
https://bugs.kde.org/show_bug.cgi?id=406318 Bug ID: 406318 Summary: Access Denied Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: three.vie...@gmail.com Target Milestone: --- Created attachment 119290 --> https://bugs.kde.org/attachment.cgi?id=119290=edit Access Denided Error Message SUMMARY When attempting to save a completed work to my hard drive I receive an Access is Denied error message. I also notice that through Krita I see hidden files when the Windows setting is set to hide said files. STEPS TO REPRODUCE 1. Create a new doc 2. Select File/Save 3. Select Directory 4. Select Save button OBSERVED RESULT Access Denied Error message EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (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.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #36 from Mike Wengelski --- Created attachment 119080 --> https://bugs.kde.org/attachment.cgi?id=119080=edit New crash information added by DrKonqi ktorrent (5.1.1) using Qt 5.12.2 - What I was doing when the application crashed: I clicked File->Quit from the main window. The app appeared to exit properly. 5-10 seconds later the KCrash report appeared. Application state: ~9 torrents seeding ~2 torrents downloading ~5 torrents in queue to download Speed limit Download: No Limit Speed limit Upload: 30 KiB/s Plugins enabled: UPnP (connected by wifi, static ip, no ipv6, dns: 1.1.1.1/1.0.0.1, netgear R8000 router) Fresh install of OpenSUSE Tumbleweed yesterday. I am willing to help test/debug this. Feel free to send me a note if I can be of service. In the mean time, I'm going to start following the stack traces around the source. -- Backtrace (Reduced): #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x74746366) at /usr/include/c++/8/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x74746366) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #10 QString::QString (other=..., this=0x7ffc597c3f50) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958 #11 v_construct_helper (t=..., x=0x7ffc597c3f50) at ../../include/QtCore/5.12.2/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:123 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 Mike Wengelski changed: What|Removed |Added CC||misterw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375943] Task bar shows audio icon for all windows from program playing sound
https://bugs.kde.org/show_bug.cgi?id=375943 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz Version|5.9.0 |5.15.3 --- Comment #18 from Mike Krutov --- Still happens on current release. Tested with Firefox, Falkon, Chromium - all have audio icons on every window. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 405770] Error when starting KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=405770 Mike Krutov changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #2 from Mike Krutov --- moving to needsinfo -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 405770] Error when starting KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=405770 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #1 from Mike Krutov --- Luiz Diego Moraes, Could you provide more information about the crash? At least, the steps to reproduce it; ideally, backtrace as well: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 405881] Kopete crash when trying to manage xoauth2 tokens
https://bugs.kde.org/show_bug.cgi?id=405881 --- Comment #1 from Mike Krutov --- Crash happens only if i have my "password" field empty in the account settings. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 405881] New: Kopete crash when trying to manage xoauth2 tokens
https://bugs.kde.org/show_bug.cgi?id=405881 Bug ID: 405881 Summary: Kopete crash when trying to manage xoauth2 tokens Product: kopete Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mikhail.kru...@seznam.cz Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: 1) Enter some JID on google talks 2) Enter google talks server information 3) Click "Manage XOauth tokens" The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5827a3e380 (LWP 16254))] Thread 4 (Thread 0x7f57f86a6700 (LWP 16273)): #0 0x7f581c6619f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5636ab072c88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5636ab072c38, cond=0x5636ab072c60) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5636ab072c60, mutex=0x5636ab072c38) at pthread_cond_wait.c:655 #3 0x7f57f982bdcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f57f982baf7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f581c65b6db in start_thread (arg=0x7f57f86a6700) at pthread_create.c:463 #6 0x7f58222c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f580cfef700 (LWP 16270)): #0 0x7f58222b40b4 in __GI___libc_read (fd=9, buf=0x7f580cfeeb10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f581a70ccd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f581a6c8027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f581a6c84e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f581a6c864c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5822bfb15b in QEventDispatcherGlib::processEvents (this=0x7f5804000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f5822b9c64a in QEventLoop::exec (this=this@entry=0x7f580cfeed20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f58229c441a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f58229c5bc2 in QThreadPrivate::start (arg=0x5636aad74860) at thread/qthread_unix.cpp:361 #9 0x7f581c65b6db in start_thread (arg=0x7f580cfef700) at pthread_create.c:463 #10 0x7f58222c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f580e200700 (LWP 16259)): #0 0x7f58222b8bf9 in __GI___poll (fds=0x7f580002c160, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f581a6c8539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f581a6c864c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5822bfb15b in QEventDispatcherGlib::processEvents (this=0x7f580b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f5822b9c64a in QEventLoop::exec (this=this@entry=0x7f580e1ffcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f58229c441a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f5824632015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f58229c5bc2 in QThreadPrivate::start (arg=0x7f58248a9d80) at thread/qthread_unix.cpp:361 #8 0x7f581c65b6db in start_thread (arg=0x7f580e200700) at pthread_create.c:463 #9 0x7f58222c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f5827a3e380 (LWP 16254)): [KCrash Handler] #6 Kopete::PasswordedAccount::password (this=0x0) at ./libkopete/kopetepasswordedaccount.cpp:50 #7 0x7f57f5d486e4 in DlgJabberXOAuth2::DlgJabberXOAuth2 (this=0x5636ab256b90, account=, parent=) at ./protocols/jabber/ui/dlgjabberxoauth2.cpp:34 #8 0x7f57f5d2d8ce in JabberEditAccountWidget::slotManageXOAuth2Clicked (this=0x5636aae80540) at ./protocols/jabber/ui/jabbereditaccountwidget.cpp:443 #9 0x7f5822bcde25 in QMetaObject::activate (sender=sender@entry=0x5636ab2dd890, signalOffset=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb50b64c0) at kernel/qobject.cpp:3778 #10 0x7f5822bce4f7 in QMetaObject::activate (sender=sender@entry=0x5636ab2dd890, m=m@entry=0x7f582406bba0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb50b64c0) at kernel/qobject.cpp:3631 #11 0x7f5823a7b6f2 in QAbstractButton::clicked (this=this@entry=0x5636ab2dd890, _t1=) at
[dolphin] [Bug 197009] Enhancement: User-selected tab titles
https://bugs.kde.org/show_bug.cgi?id=197009 Mike Krutov changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 197009] Enhancement: User-selected tab titles
https://bugs.kde.org/show_bug.cgi?id=197009 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #2 from Mike Krutov --- I've added a small patch that implements this feature request: https://phabricator.kde.org/D20052 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377116] Unexpected behavior when calling dolphin with a file as an argument
https://bugs.kde.org/show_bug.cgi?id=377116 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz Status|CONFIRMED |ASSIGNED --- Comment #4 from Mike Krutov --- I've made a small patch for this: https://phabricator.kde.org/D20049 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 195801] go up in folder hierachy when in "edit mode"
https://bugs.kde.org/show_bug.cgi?id=195801 Mike Krutov changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||mikhail.kru...@seznam.cz --- Comment #12 from Mike Krutov --- moving status to assigned, https://phabricator.kde.org/D20026 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405837] Dolphin crashes opening icon changer
https://bugs.kde.org/show_bug.cgi?id=405837 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #2 from Mike Krutov --- Hi! I've tried to reproduce this issue as well, with no luck, on current neon user (5.55.0 frameworks, 5.15.3 plasma, 5.12 qt). I've played around with file permissions and so on, and it didn't help me reproduce it. Alex, could you please provide more information about your system? Is this behaviour specific to a given file? In case it is, please provide us some details about the file - xattrs, permissions Is this behaviour reproducible on more then one file, please try to narrow it down to a location - is it specific to a given filesystem? (Remote FS, local FS, local exact device?) Is this behaviour reproducible on clean profile? (run from a new user or something in that lines) In case you'll be able to reproduce the issue, please update the crash log after installing debug symbols for package that provides libKF5ItemViews.so.5 pacman -Fs /usr/lib/libKF5ItemViews.so.5 should provide you with the package name. Not sure how debug packages are distributed in Arch. #6 0x7f8e187b9fd9 in ?? () from /usr/lib/libKF5ItemViews.so.5 #7 0x7f8e187ba394 in ?? () from /usr/lib/libKF5ItemViews.so.5 #8 0x7f8e187ba496 in ?? () from /usr/lib/libKF5ItemViews.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405835] Add a way to configure if a system tray instance should display desktop notifications
https://bugs.kde.org/show_bug.cgi?id=405835 Mike Krutov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Mike Krutov --- Yep it does. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 405840] New: kiod5 does not provide a bug reporting address
https://bugs.kde.org/show_bug.cgi?id=405840 Bug ID: 405840 Summary: kiod5 does not provide a bug reporting address Product: kio-extras Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: default Assignee: plasma-b...@kde.org Reporter: mikhail.kru...@seznam.cz Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Crash kiod5 2. 3. OBSERVED RESULT Drkonqi opens, "We are sorry, you can not report this error because kiod5 does not provide a bug reporting address" EXPECTED RESULT DrKonqi is able to report the bug. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 405839] New: Dolphin can't copy files over to MTP if files with same name exist on destination
https://bugs.kde.org/show_bug.cgi?id=405839 Bug ID: 405839 Summary: Dolphin can't copy files over to MTP if files with same name exist on destination Product: kio-extras Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MTP Assignee: elvis.angelac...@kde.org Reporter: mikhail.kru...@seznam.cz Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Mount MTP device 2. Create directory called "Alice" 3. Copy other directory called "Alice" from some other source to MTP device OBSERVED RESULT Red notification "Dolphin can't create file Alice" EXPECTED RESULT Dialog "File with same name found. Overwrite?" etc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 405838] New: KIOD5 crashes if user disconnects MTP device during copeing
https://bugs.kde.org/show_bug.cgi?id=405838 Bug ID: 405838 Summary: KIOD5 crashes if user disconnects MTP device during copeing Product: kio-extras Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MTP Assignee: elvis.angelac...@kde.org Reporter: mikhail.kru...@seznam.cz Target Milestone: --- Created attachment 119010 --> https://bugs.kde.org/attachment.cgi?id=119010=edit crash log SUMMARY STEPS TO REPRODUCE 1. Start copying data to MTP device 2. During copy operation, disconnect device 3. Bam OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405835] New: Multiple trays result in multiple notifications
https://bugs.kde.org/show_bug.cgi?id=405835 Bug ID: 405835 Summary: Multiple trays result in multiple notifications Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: mikhail.kru...@seznam.cz Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Add several panels on different monitors 2. Add System Tray to every panel 3. Receive notification OBSERVED RESULT a) In case when all monitors are connected, there are X notifications for each notification, near each system tray b) In case one or more monitors are disconnected, there still are X notifications, on main screen in various corners. EXPECTED RESULT Every system tray should have a configuration item to disable notification display on this given tray plasmoid. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405835] Add a way to configure if a system tray instance should display desktop notifications
https://bugs.kde.org/show_bug.cgi?id=405835 Mike Krutov changed: What|Removed |Added Summary|Multiple trays result in|Add a way to configure if a |multiple notifications |system tray instance should ||display desktop ||notifications -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 405822] KTurtle offers to save a file after changes were reverted
https://bugs.kde.org/show_bug.cgi?id=405822 --- Comment #1 from Mike Krutov --- Found while testing for https://bugs.kde.org/show_bug.cgi?id=405199 -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 405199] KTurtles asks for saving, even for already saved files.
https://bugs.kde.org/show_bug.cgi?id=405199 --- Comment #2 from Mike Krutov --- Christoph, Giorgos, I've tested it; this exact problem seems to be fixed in current master. -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 405822] New: KTurtle offers to save a file after changes were reverted
https://bugs.kde.org/show_bug.cgi?id=405822 Bug ID: 405822 Summary: KTurtle offers to save a file after changes were reverted Product: kturtle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: c...@kde.nl Reporter: mikhail.kru...@seznam.cz Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open KTurtle 2. Input something into code editor 3. Remove everything, so code editor is clean as it was initially 4. Close KTurtle OBSERVED RESULT KTurtle asks if user wants to discard or save changes, which IMO makes no sense since there are no changes to save, since all changes were reverted. EXPECTED RESULT KTurtle remembers initial contents of code editor & doesn't propose to save file when contents were not changed, even after edits. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 (also tried on latest master KTurtle) KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405780] "Create New..." button can't be configured
https://bugs.kde.org/show_bug.cgi?id=405780 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #1 from Mike Krutov --- Can confirm, I don't have the button either. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389963] Tooltips take the whole horizontal screen when showing long download url
https://bugs.kde.org/show_bug.cgi?id=389963 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #3 from Mike Krutov --- Hi! I've created a patch for this issue here: https://phabricator.kde.org/D19988 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405620] Move 'Safely Remove' down in Places popup menu
https://bugs.kde.org/show_bug.cgi?id=405620 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #5 from Mike Krutov --- I've created a MR for this https://phabricator.kde.org/D19987 Please note, there are test failures on current master: FAIL! : PlacesItemModelTest::testDefaultViewProperties(Baloo - Documents) Compared values are not the same Loc: [/home/neko/src-kde/dolphin/src/tests/placesitemmodeltest.cpp(479)] FAIL! : PlacesItemModelTest::testDefaultViewProperties(Places - Audio) Compared values are not the same Loc: [/home/neko/src-kde/dolphin/src/tests/placesitemmodeltest.cpp(479)] FAIL! : PlacesItemModelTest::testDefaultViewProperties(Baloo - Today) Compared values are not the same Loc: [/home/neko/src-kde/dolphin/src/tests/placesitemmodeltest.cpp(479)] Those tests fail without my changes, and I'm not sure what change has introduced those failures. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405765] New: Uninformative error message (The module Multimedia is not a valid configuration module)
https://bugs.kde.org/show_bug.cgi?id=405765 Bug ID: 405765 Summary: Uninformative error message (The module Multimedia is not a valid configuration module) Product: systemsettings Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: mikhail.kru...@seznam.cz Target Milestone: --- Created attachment 118979 --> https://bugs.kde.org/attachment.cgi?id=118979=edit bug displayed (same as imgur link) SUMMARY https://i.imgur.com/m81zXBM.png STEPS TO REPRODUCE 1. Search for Multimedia in system settings 2. Select found item OBSERVED RESULT Per screenshot: "The module multimedia is not a valid configuration module." EXPECTED RESULT First valid submodule of the module "multimedia" is selected as default item. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #21 from Mike Krutov --- I've tried reproducing it in various combinations of monitors, and it seems that bug is not there anymore for me. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389679] baloo_file_extractor crashes in Baloo::Transaction::commit() or mdb_txn_commit()
https://bugs.kde.org/show_bug.cgi?id=389679 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #7 from Mike Krutov --- Still happens on Fedora 29. Both times it happened today was right after mounting readonly NFS share, however after unmounting & mounting again it did not crash. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 405597] Uninformative error message in KCrash when saving stacktrace
https://bugs.kde.org/show_bug.cgi?id=405597 Mike Krutov changed: What|Removed |Added Assignee|fa...@kde.org |unassigned-b...@kde.org Product|frameworks-kcrash |drkonqi Version|5.55.0 |5.14.5 Component|general |general --- Comment #1 from Mike Krutov --- I think I've messed up with the component, reassigning to drkonqi. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 349268] Be able to copy the uploaded url
https://bugs.kde.org/show_bug.cgi?id=349268 --- Comment #4 from Mike Krutov --- Oleg, same versions on Fedora as well; the line with URL is in the window for some 5 minutes and is copied automatically. Are you on Wayland? I'm using X11 and might be that is the difference that leads to that behaviour on your side. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 405597] New: Uninformative error message in KCrash when saving stacktrace
https://bugs.kde.org/show_bug.cgi?id=405597 Bug ID: 405597 Summary: Uninformative error message in KCrash when saving stacktrace Product: frameworks-kcrash Version: 5.55.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: mikhail.kru...@seznam.cz CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 118880 --> https://bugs.kde.org/attachment.cgi?id=118880=edit demonstrating the issue SUMMARY STEPS TO REPRODUCE 1. Generate stacktrace from crash 2. Save it 3. Save it again, using same file name; tick overwrite. OBSERVED RESULT Just a window with file path and yellow exclamation sign EXPECTED RESULT Actual error message (or in this case, as file has write permissions, no error message & file being overwritten) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405594] New: Allow network shares to be renamed in Dolphin
https://bugs.kde.org/show_bug.cgi?id=405594 Bug ID: 405594 Summary: Allow network shares to be renamed in Dolphin Product: dolphin Version: 18.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: mikhail.kru...@seznam.cz Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Add lengthy-host-name:/some-even/lengthier-path/StuffThatMatters to /etc/fstab 2. open dolphin OBSERVED RESULT Dolphin displays very long string describing NFS shares. In case there are a few of network shares, it is easy to mix them up during normal operation. SUGGESTION Add a possibility of "renaming" network share in dolphin. That would not affect anything but visual part, and would allow to show e.g. "StuffThatMatters" instead of having the whole thing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 OS Version: Fedora 29 -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 404162] File/Save acts always acts like "Save as..."
https://bugs.kde.org/show_bug.cgi?id=404162 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #3 from Mike Krutov --- I've put a small patch which fixes it for a review: https://phabricator.kde.org/D19769 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 349268] Be able to copy the uploaded url
https://bugs.kde.org/show_bug.cgi?id=349268 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #2 from Mike Krutov --- Spectacle right now copies the Imgur URL by-default right after upload, also right-clicking URL in spectacle window gives you the ability to copy it yet again. Oleg, Jairo, could you please confirm this as fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395335] If auto-login is enabled in user manager, Wayland session is started incorrectly (plasma uses 25% of the screen)
https://bugs.kde.org/show_bug.cgi?id=395335 --- Comment #7 from Mike Lothian --- I've been seeing this on Gentoo too I thought it might be something to do with my setup but I'm not sure how to diagnose wayland issues Are there logs (like the equivalent of /var/log/Xorg.0.log) that might be of use? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395335] If auto-login is enabled in user manager, Wayland session is started incorrectly (plasma uses 25% of the screen)
https://bugs.kde.org/show_bug.cgi?id=395335 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #17 from Mike Krutov --- I'm affected by this, too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403580] Formats only offers invalid locales for German (en_DE)
https://bugs.kde.org/show_bug.cgi?id=403580 --- Comment #4 from Mike FABIAN --- (In reply to Andreas Schneider from comment #2) > The issue probably is that KDE sets LANG or LC_* variables to locales which > don't exist. So all terminal tools like 'ls', 'git' etc. are printing > warnings that I use locales which don't exist. KDE/Qt5 apparently uses the locale support in libicu. The list of locales libicu supports is different from the locales glibc supports, there is considerable overlap between the list of locales supported by libicu and glibc, but the lists are not equal. If the user chooses a locale in KDE which does not exist in glibc, it makes not sense setting the LANG or LC_* variables to such a locale. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403580] Formats only offers invalid locales for German (en_DE)
https://bugs.kde.org/show_bug.cgi?id=403580 Mike FABIAN changed: What|Removed |Added CC||mfab...@redhat.com --- Comment #3 from Mike FABIAN --- (In reply to Andreas Schneider from comment #1) > It looks like that Qt uses cldr, however glibc doesn't support all locales > of cldr. Also it is strange that it doesn't offer de_DE which is the only > supported locale by glibc. Yes, de_DE is also a valid locale for CLDR/libicu. The list KDE offers is very incomplete. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.
https://bugs.kde.org/show_bug.cgi?id=212268 --- Comment #4 from Mike Goodwin --- Possibly related: https://bugs.kde.org/show_bug.cgi?id=358476 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.
https://bugs.kde.org/show_bug.cgi?id=212268 Mike Goodwin changed: What|Removed |Added CC||m...@mgoodwin.net --- Comment #3 from Mike Goodwin --- This bug is absolutely still valid and has been for some 10 years.. It makes sending/receiving HTML emails a chore in the workplace because if you use KMail to do it, your emails look like they're written by a child. (i.e. unprofessional) Example Business email: --- Hi Mark, Thanks for sending me that info Regards, - Mike Becomes: Hi Mark, Thanks for sending me that info Regads, - Mike When read by any modern client (for me Outlook, Roundcube, Rainloop and Gmail all render Kmail's sent HTML like this) There are also numerous reports on the forums about this issue. Is there any way we can get this bug to the right place to finally gain some traction? It's really the only thing left in my personal list of wants that KMail needs for me to use it exclusively (right now if I'm not sending TEXT email, I have to go use rainloop if I want properly formatted emails). I'm truly baffled as to how this is still a bug. Here's an updated list of possibly related software versions that the bug can be bumped to: kdepim-addons-18.08.3-1.fc29.x86_64 kdepim-runtime-libs-18.08.3-1.fc29.x86_64 kf5-libkdepim-18.08.3-1.fc29.x86_64 kdepim-apps-libs-18.08.3-1.fc29.x86_64 kf5-kmailtransport-akonadi-18.08.3-1.fc29.x86_64 kdepim-runtime-18.08.3-1.fc29.x86_64 kmail-libs-18.08.3-1.fc29.x86_64 kf5-libkdepim-akonadi-18.08.3-1.fc29.x86_64 kf5-kmailtransport-18.08.3-1.fc29.x86_64 kdepimlibs-4.14.10-29.fc29.x86_64 kdepimlibs-gpgme-4.14.10-29.fc29.x86_64 kdepimlibs-kxmlrpcclient-4.14.10-29.fc29.x86_64 kdepim-common-17.12.3-2.fc29.x86_64 kmail-account-wizard-18.08.3-1.fc29.x86_64 kdepimlibs-akonadi-4.14.10-29.fc29.x86_64 kmail-18.08.3-1.fc29.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 403630] New: trigrams.map conflicts with kf5-sonnet-core-5.54
https://bugs.kde.org/show_bug.cgi?id=403630 Bug ID: 403630 Summary: trigrams.map conflicts with kf5-sonnet-core-5.54 Product: frameworks-sonnet Version: 5.54.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: mike.h...@hinzgroup.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Attempting to do 'dnf update' on a previously fully updated Fedora 29 system results in the following conflict that I've been unable to resolve. Error: Transaction check error: file /usr/share/kf5/sonnet/trigrams.map conflicts between attempted installs of kf5-sonnet-core-5.54.0-1.fc29.i686 and kf5-sonnet-core-5.54.0-1.fc29.x86_64 STEPS TO REPRODUCE 1. open a terminal window 2. do 'sudo dnf update' 3. error above occurs every time 4. this is apparently related to the recent k5f 5.54 release OBSERVED RESULT DNF transaction error occurs EXPECTED RESULT DNF update should complete normally without errors SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Fedora 29 kernel 4.20.3-200fc29x86_64 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I've attempted to rename or remove trigrams.map and the behavior doesn't change. The installation still fails. I've found no other bugs relating to this. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403181] New: Discover Crashed each time
https://bugs.kde.org/show_bug.cgi?id=403181 Bug ID: 403181 Summary: Discover Crashed each time Product: Discover Version: 5.14.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: diplar...@gmail.com Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: every time i openning the discover it will crash, so i cannot update my KDE neon The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faf525ea200 (LWP 2599))] Thread 18 (Thread 0x7faee1dbc700 (LWP 2625)): #0 0x7faf4a2579f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fd35f57180) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7faf4a2579f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fd35f57130, cond=0x55fd35f57158) at pthread_cond_wait.c:502 #2 0x7faf4a2579f3 in __pthread_cond_wait (cond=0x55fd35f57158, mutex=0x55fd35f57130) at pthread_cond_wait.c:655 #3 0x7faf2746d46b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faf2746d197 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7faf4a2516db in start_thread (arg=0x7faee1dbc700) at pthread_create.c:463 #6 0x7faf4db5888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7faee2dbe700 (LWP 2623)): #0 0x7faf4db470b4 in __GI___libc_read (fd=51, buf=0x7faee2dbdb90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7faf480f9cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faf480b5027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faf480b54e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7faf480b564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7faf4e48604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faf4e42a30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7faf4e255bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7faf4e260adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7faf4a2516db in start_thread (arg=0x7faee2dbe700) at pthread_create.c:463 #10 0x7faf4db5888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7faee8f7c700 (LWP 2618)): #0 0x7faf4db4bbf9 in __GI___poll (fds=0x55fd33466440, nfds=1, timeout=55085) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7faf480b5539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faf480b564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faf4e48604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7faf4e42a30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faf4e255bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faf4e260adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7faf4a2516db in start_thread (arg=0x7faee8f7c700) at pthread_create.c:463 #8 0x7faf4db5888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7faeeafd2700 (LWP 2617)): #0 0x7faf480b5454 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7faf480b564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faf4e48604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7faf4e42a30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7faf4e255bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faf4e260adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faf4a2516db in start_thread (arg=0x7faeeafd2700) at pthread_create.c:463 #7 0x7faf4db5888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7faf01d10700 (LWP 2616)): #0 0x7faf4db470b4 in __GI___libc_read (fd=21, buf=0x7faf01d0fcd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7faf480f9cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faf480b5027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faf480b54e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7faf480b58d2 in g_main_loop_run () at
[kmail2] [Bug 402364] New: Unclear error dialog with actual error message shadowed in background
https://bugs.kde.org/show_bug.cgi?id=402364 Bug ID: 402364 Summary: Unclear error dialog with actual error message shadowed in background Product: kmail2 Version: 5.9.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: nekoxmach...@gmail.com Target Milestone: --- SUMMARY Akonadi protocol mismatch results in "The email program encountered a fatal error and will terminate now" dialog. This dialog blocks actual error message, displayed in KMail window. STEPS TO REPRODUCE 1. Update. Don't restart Akonadi server yet. 2. Restart KMail 3. Observe OBSERVED RESULT As described, actual error message isn't vieweable. EXPECTED RESULT Dialog should contain erorr message instead of just saying "Fatal error". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #23 from Mike Robinson --- (In reply to Martin Oemus from comment #22) > As the bug is still active I want to add some feedback: contrary to my first > comment the solution presented at stackexchange in fact did solve the issue > for me. > I simply added fs.inotify.max_user_watches=524288 to /etc/sysctl.conf and > rebooted. > > I'm positive that it already worked a year ago (and I forgot to give timely > feedback). Currently I'm running Kubuntu 18.04, KDE-Plasma 5.12.7, > Frameworks 5.47.0, Kernel 4.15.0, Dolphin 17.12.3. With the work-around > described, the bug does not affect me anymore. Confirmed this workaround worked for me. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Mike Krutov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Mike Krutov --- Could you please say what apps have active notifications on your phone when the crash happens? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 401983] With bluetooth integration enabled, system keeps scanning for new bluetooth devices every now and then.
https://bugs.kde.org/show_bug.cgi?id=401983 Mike Krutov changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |NOT A BUG --- Comment #5 from Mike Krutov --- I have this problem re-appear, unfortunatelly, after system restart. First start of my session @ kde resulted in described behaviour. wizard was not running; running applications were: Kate, falkon, Konversation, Firefox, KMail. Second start of my session resulted in normal behaviour, marking as NOTABUG since its not a bug in bluedevil. Need help determining proper component, though. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 401983] With bluetooth integration enabled, system keeps scanning for new bluetooth devices every now and then.
https://bugs.kde.org/show_bug.cgi?id=401983 --- Comment #4 from Mike Krutov --- Thanks for answer. In case I would be able to reproduce this behaviour, how do I find which exact process is calling for KIO bluetooth: ? Only things that (should have been) working with BT were: - pulseaudio, but that should not interact with KIO I think - bluetooth plasmoid from default plasmoid pack (haven't installed any custom BT plasmoids) - Through Pulseaudio, Clementine was playing music All that things are currently running with exact same settings as they were when problem was reproduced, except for "bluetooth integration" setting. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 401983] With bluetooth integration enabled, system keeps scanning for new bluetooth devices every now and then.
https://bugs.kde.org/show_bug.cgi?id=401983 --- Comment #2 from Mike Krutov --- Quite sure Add device wizard was not running. I have plasmoid added to my panel, if that matters. When I disabled "bluetooth integration" feature it stopped scanning (after restart of my session) without any other changes in system. I'll try to tinker around more and reproduce to see if I'll reproduce this behaviour to confirm add device wizard (what is the name of the wizard process?) is not running. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Mike Krutov changed: What|Removed |Added Resolution|WAITINGFORINFO |BACKTRACE --- Comment #4 from Mike Krutov --- Could you please install debug symbols for kdeconnect and re-capture the backtrace? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 401983] New: With bluetooth integration enabled, system keeps scanning for new bluetooth devices every now and then.
https://bugs.kde.org/show_bug.cgi?id=401983
Bug ID: 401983
Summary: With bluetooth integration enabled, system keeps
scanning for new bluetooth devices every now and then.
Product: Bluedevil
Version: 5.14.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: daemon
Assignee: now...@gmail.com
Reporter: nekoxmach...@gmail.com
Target Milestone: ---
SUMMARY
BlueDevil seems to be constantly scanning for new bluetooth devices. On my
hardware (and I suspect on any combined wifi/bluetooth chips, which are mostly
found in laptops) this leads to serious deteoriation in wireless connectivity
quality, up to completely loosing a wifi connection for couple minutes after a
day of uptime.
I'd suggest to add a separate configuration tickable to prevent this behaviour.
STEPS TO REPRODUCE
1. Enable BlueDevil "bluetooth integration" feature
2. Open bluetoothctl to monitor for scan("Discovering") requests
OBSERVED RESULT
Software-wise:
Every 2-3 minutes, device goes into "Discovery" mode.
Hardware-wise:
Wireless speed & packetdrop grows, longer it keeps going worse the connectivity
becomes.
EXPECTED RESULT
As this is not a bug per se, while having quite bad outcome AND being a
non-obvious thing to detect/debug, I've set it to Wishlist.
Expected result would be to have a configuration item to disable this behaviour
while keeping other bluetooth integration features; I'd argue that not scanning
continiously should be the default.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1
ADDITIONAL INFORMATION
Hardware in question:
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 401843] Notification on lockscreen shows artist "Unbekannt" (Unknown) when playing a media
https://bugs.kde.org/show_bug.cgi?id=401843 Mike Krutov changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||nekoxmach...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Mike Krutov --- I was not able to reproduce the problem on Sony phone, but was able to reproduce it on Samsung phone, using latest google play builds of software (1.10.1 according to application screen @ device). I have tried various settings for language, etc - what seemed to be the difference between my sony device, my friend's samsung device and device in this bug report. Any locale on Samsung leads to having this bug (Russian - English - German tested); no locale change on Sony device made this bug appear on Sony device. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Mike Krutov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Mike Krutov --- updating to NEEDSINFO till the backtrace is provided -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Mike Krutov changed: What|Removed |Added CC||nekoxmach...@gmail.com --- Comment #1 from Mike Krutov --- Hello! Thank you for reporting the issue. Could you please provide a backtrace for the crash? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #14 from Mike --- Is there a developer outside who has some insight into the icon placement ? The metioned position (.config/plasma-org.kde.plasma.desktop-appletsrc) seems not to be the only location of icon position information. If I change icon positions and load the file again to compare some data change but it doesn't seem to be data related to the icon I moved. At least I can't see the relation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 Mike changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 313060] No windows/widgets/panel on 2nd head of dual head display after screensaver
https://bugs.kde.org/show_bug.cgi?id=313060 --- Comment #3 from Mike BRIGHT --- Thanks for looking at this. This is a very old issue, and probably dates back to Fedora 24? or less so I suggest we close this. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 359701] Crash at startup
https://bugs.kde.org/show_bug.cgi?id=359701 Mike McCarthy changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED CC||m...@w1nr.net Status|NEEDSINFO |RESOLVED --- Comment #3 from Mike McCarthy --- This is a very old distribution of opensuse. The bug does not exist in current distros so I am closing it as unmaintained. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 400610] Qt Applications crash with SIGBUS if XDG_CACHE_HOME directory is too small (or maybe out of space)
https://bugs.kde.org/show_bug.cgi?id=400610 --- Comment #5 from Mike --- For the sake of completeness: I found a very similar problem in Qt (same test program, missing test before mmap()): https://bugreports.qt.io/browse/QTQAINFRA-2381 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 400610] Qt Applications crash with SIGBUS if XDG_CACHE_HOME directory is too small (or maybe out of space)
https://bugs.kde.org/show_bug.cgi?id=400610 --- Comment #4 from Mike --- @Alexey Min: thanks for fixing this bug so quickly! :-) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 339829] KDE crashes with SIGBUS when /var (i.e. /var/tmp) is out of disk space
https://bugs.kde.org/show_bug.cgi?id=339829 Mike changed: What|Removed |Added CC||b...@ubhofmann.de --- Comment #9 from Mike --- This could be the same as or similar to bug 400610. I was able to track this down to a specific line in kcoreaddons: src/lib/caching/kshareddatacache.cpp, see bug 400610 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 400610] Qt Applications crash with SIGBUS if XDG_CACHE_HOME directory is too small (or maybe out of space)
https://bugs.kde.org/show_bug.cgi?id=400610 Mike changed: What|Removed |Added Summary|Application crashes with|Qt Applications crash with |SIGBUS if XDG_CACHE_HOME is |SIGBUS if XDG_CACHE_HOME |too small (or maybe out of |directory is too small (or |space) |maybe out of space) Version|unspecified |5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 400610] New: Application crashes with SIGBUS if XDG_CACHE_HOME is too small (or maybe out of space)
https://bugs.kde.org/show_bug.cgi?id=400610
Bug ID: 400610
Summary: Application crashes with SIGBUS if XDG_CACHE_HOME is
too small (or maybe out of space)
Product: frameworks-kcoreaddons
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: b...@ubhofmann.de
CC: kdelibs-b...@kde.org
Target Milestone: ---
Qt application crashes with SIGBUS if XDG_CACHE_HOME is too small
We were able to track down the problem to:
- Package: kde-frameworks/kcoreaddons-5.51.0
- File: src/lib/caching/kshareddatacache.cpp
- Function: void mapSharedMemory()
- Lines: 1051 - 1053
- Code:
if (file.open(QIODevice::ReadWrite) &&
(file.size() >= size ||
(file.resize(size) && ensureFileAllocated(file.handle(), size {
STEPS TO REPRODUCE
1) Create a small filesystem (as root): mount -t tmpfs -o size=30k tmpfs /mnt
The size seems to depend on the system. If the value in '-o size=' is too small
or too high, you won't get a SIGBUS crash. 30k works on my machine.
2) Create a small test program (as suggested by user "mv")
File a.cc:
#include
#include
int main(int argc, char ** argv) {
QApplication a(argc,argv);
QFrame *view = new QFrame();
view->show();
a.connect(,SIGNAL(lastWindowClosed()),,SLOT(quit()));
return a.exec();
}
File: a.pro
TARGET = a
SOURCES = a.cc
QT += widgets
3) Compile the program and run it:
qmake && make
XDG_CACHE_HOME=/mnt ./a
4) The program will crash with SIGBUS
5) You can get more details using strace:
XDG_CACHE_HOME=/mnt strace -o /tmp/strace-log -f ./a
6) strace-log shows:
1500 openat(AT_FDCWD, "/mnt/icon-cache.kcache", O_RDWR|O_CREAT|O_CLOEXEC,
0666) = 9
1500 statx(9, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_BASIC_STATS, stx_attributes=0, stx_mode=S_IFREG|0640,
stx_size=0, ...}) = 0
1500 lseek(9, 0, SEEK_CUR) = 0
1500 ftruncate(9, 10547304)= 0
1500 fallocate(9, 0, 0, 10547304) = -1 ENOSPC (No space left on device)
1500 mmap(NULL, 10547304, PROT_READ|PROT_WRITE, MAP_SHARED, 9, 0) =
0x7f71484df000
1500 --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRERR,
si_addr=0x7f71484e3020} ---
The mmap should have stopped with an error message after fallocate, since this
function failed. But the error was ignored and the program continued with an
mmap. A subsequent memory access to the mmaped memory failed with SIGBUS.
7) The lines in the strace log correspond to lines 1051 - 1053 of
src/lib/caching/kshareddatacache.cpp
OBSERVED RESULT: SIGBUS
EXPECTED RESULT: Error message stating that XDG_CACHE_HOME is out of space,
followed by a regular abort() or exit().
SOFTWARE VERSIONS
- OS: Gentoo Linux
- KDE Plasma Version: 5.14.2
- KDE Frameworks Version: 5.51.0
- Qt Version: 5.11.2
ADDITIONAL INFORMATION
- Look at https://forums.gentoo.org/viewtopic-t-1087812.html for additional
information.
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 400519] New: Crash on change of workspaces
https://bugs.kde.org/show_bug.cgi?id=400519 Bug ID: 400519 Summary: Crash on change of workspaces Product: rkward Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: m...@mykolab.ch Target Milestone: --- Application: rkward (0.7.0b) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: A workspace was open I selected a new workspace and from the menu and clicked on it to open it Then it crashed -- Backtrace: Application: RKWard (rkward), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe9762b0500 (LWP 29221))] Thread 6 (Thread 0x7fe8fbbff700 (LWP 29230)): #0 0x7fe96d1bfbf9 in __GI___poll (fds=0x7fe8f4003ce0, nfds=1, timeout=9627) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe967675439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe96767554c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe96de9853b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe96de3c7fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe96dc67bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe96dc72adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe96a8f06db in start_thread (arg=0x7fe8fbbff700) at pthread_create.c:463 #8 0x7fe96d1cc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe941c5e700 (LWP 29225)): #0 0x7fe9676bad94 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe967675556 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe96de9853b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fe96de3c7fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe96dc67bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00638dd0 in RKFrontendTransmitter::run() () #6 0x7fe96dc72adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe96a8f06db in start_thread (arg=0x7fe941c5e700) at pthread_create.c:463 #8 0x7fe96d1cc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fe94d5b2700 (LWP 29224)): #0 0x7fe9676bad79 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe96767541f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe96767554c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe96de9853b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe96de3c7fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe96dc67bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe97047de45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe96dc72adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe96a8f06db in start_thread (arg=0x7fe94d5b2700) at pthread_create.c:463 #9 0x7fe96d1cc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe95503e700 (LWP 29223)): #0 0x7fe96d1bfbf9 in __GI___poll (fds=0x7fe95503db28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe9648a3747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe9648a536a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe957df7ed9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fe96dc72adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe96a8f06db in start_thread (arg=0x7fe95503e700) at pthread_create.c:463 #6 0x7fe96d1cc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe9591de700 (LWP 29222)): #0 0x7fe96a8f69f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fe975994114) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe96a8f69f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x1c86a30, cond=0x7fe9759940e8) at pthread_cond_wait.c:502 #2 0x7fe96a8f69f3 in __pthread_cond_wait (cond=0x7fe9759940e8, mutex=0x1c86a30) at pthread_cond_wait.c:655 #3 0x7fe96d8f179c in std::condition_variable::wait(std::unique_lock&) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7fe974ca6217 in () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663
--- Comment #18 from Mike Robinson ---
I am also having this problem with Kubuntu 18.04, see the above screencast.
This seems to also affects sync programs, (e.g. Seafile), which are supposed to
watch certain directories for changes and upload to the server any files that
have been changed, however I need to manually tell it to rescan the
directories.
I get a "No space left on device" error when running Dolphin:
$ dolphin
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "stash"
inotify_add_watch("/etc/fstab") failed: "No space left on device"
inotify_add_watch("/home/mike/.local/share/user-places.xbel") failed: "No space
left on device"
inotify_add_watch("/home/mike") failed: "No space left on device"
qt.accessibility.core: Cannot create accessible child interface for object:
PlacesView(0x557fc372cf20) index: 12
kf5.kio.core: KLocalSocket(0x557fc389e150) Jumbo packet of 132210 bytes
kf5.kio.core: KSambaShare: Could not find smb.conf!
However there is plenty of space left on all drives:
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.4G 0 3.4G 0% /dev
tmpfs 691M 1.7M 690M 1% /run
/dev/mapper/mike--debian-root 42G 4.2G 36G 11% /
/dev/mapper/mike--debian-usr30G 6.8G 22G 24% /usr
tmpfs 3.4G 101M 3.3G 3% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.4G 0 3.4G 0% /sys/fs/cgroup
/dev/sda1 730M 6.1M 724M 1% /boot/efi
/dev/mapper/mike--debian-tmp42G 49M 40G 1% /tmp
/dev/mapper/mike--debian-home 504G 152G 327G 32% /home
/dev/mapper/mike--debian-var 133G 3.2G 123G 3% /var
tmpfs 691M 16K 691M 1% /run/user/129
tmpfs 691M 20K 691M 1% /run/user/1000
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 Mike Robinson changed: What|Removed |Added CC||kde_b...@multiwebinc.com --- Comment #17 from Mike Robinson --- Created attachment 115697 --> https://bugs.kde.org/attachment.cgi?id=115697=edit Screencast showing folder view is not refreshed -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399438] New: Crash while copying between TABS
https://bugs.kde.org/show_bug.cgi?id=399438 Bug ID: 399438 Summary: Crash while copying between TABS Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: softw...@g7m3.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: Copying files from one tab to another - same Hard drive sorce and destination -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7a62a5b6c0 (LWP 19319))] Thread 6 (Thread 0x7f7a2b786700 (LWP 19333)): #0 0x7f7a622d6bf9 in __GI___poll (fds=0x7f7a240049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7a55232439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a5523254c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a5c4ea90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7a5c48f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7a5c2ae22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a5c2b316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a573a36db in start_thread (arg=0x7f7a2b786700) at pthread_create.c:463 #8 0x7f7a622e388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f7a33fff700 (LWP 19332)): #0 0x7f7a573a99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56329ae770d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56329ae77088, cond=0x56329ae770b0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56329ae770b0, mutex=0x56329ae77088) at pthread_cond_wait.c:655 #3 0x7f7a4200d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7a4200d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f7a573a36db in start_thread (arg=0x7f7a33fff700) at pthread_create.c:463 #6 0x7f7a622e388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f7a40e24700 (LWP 19331)): #0 0x7f7a573a99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56329b0ca8a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56329b0ca850, cond=0x56329b0ca878) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56329b0ca878, mutex=0x56329b0ca850) at pthread_cond_wait.c:655 #3 0x7f7a4200d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7f7a4200d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7f7a573a36db in start_thread (arg=0x7f7a40e24700) at pthread_create.c:463 #6 0x7f7a622e388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f7a491e1700 (LWP 19323)): #0 0x7f7a622d20b4 in __GI___libc_read (fd=7, buf=0x7f7a491e0b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f7a55276a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a55231f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a552323e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a5523254c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a5c4ea90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a5c48f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a5c2ae22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7a5c967d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f7a5c2b316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f7a573a36db in start_thread (arg=0x7f7a491e1700) at pthread_create.c:463 #11 0x7f7a622e388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f7a4b91e700 (LWP 19322)): #0 0x7f7a622d6bf9 in __GI___poll (fds=0x7f7a4b91dca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7a54b73747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f7a54b7536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7a4e6cb2a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f7a5c2b316d in ?? () from
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #4 from Mike --- What info is needed ? It's indeed an old bug but it hit mee some weeks ago again with latest KDE version on Manjaro - rolling release. Right now I have: Kernel: 4.14.71-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.13.5 Distro: Manjaro Linux Can't reproduce but it was on a reboot that all Icons lost theire position and have been placed on the left side of the desktop. Had to rearrange them one by one. Still missing a feature that saves and restores the icons. Even a hint where those settings ins the profile could be found. Regards, Michael -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 398633] Feature request add tests for qt containers and qobjects
https://bugs.kde.org/show_bug.cgi?id=398633 --- Comment #2 from Mike Harris --- Can there at least be some form of bounds checking? I'm not sure what other common standard library like container issues are common but maybe some of the most generic common? -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 398633] New: Feature request add tests for qt containers and qobjects
https://bugs.kde.org/show_bug.cgi?id=398633 Bug ID: 398633 Summary: Feature request add tests for qt containers and qobjects Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mike.a.har...@outlook.com CC: smart...@kde.org Target Milestone: --- I have a very simple example that refuses to be flagged by either clang, clang-tidy, clazy, or Krazy2. QVector myVec; myVec.push_back(1); myVec.push_back(2); int third = myVec.at(3); int otherThird =myVec[3]; obviously this segfaults because there was never a third element. The issue is that no single IDE or plugin will flag this. It'll ASSERT in Qt Creator debug build run but that's after it compiles. there has to be some intellisense like thing in the editor or any static analysis tool that can read Qt Containers. "Just add the Qt source to your code model" you might say well compiling every single part of Qt takes many days so not an option. Another example is QCheckBox *myCheckbox = new QCheckBox(); QListView *myListView = qobject_cast(myCheckBox); //will equal null QSize size = myListView->gridSize(); //myListView is null so crashes with segfault again This leads to deep bugs that aren't flagged with any static analysis tool. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g
https://bugs.kde.org/show_bug.cgi?id=393146 Mike changed: What|Removed |Added CC||cmsim...@gmail.com --- Comment #4 from Mike --- Running into the same issue on two different macs (one installed via compiling the source, one via brew): https://pastebin.com/BdifEEQ4 -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 396735] New: Add a setting to hide loop devices created by snapd (or maybe squashfs filesystems)
https://bugs.kde.org/show_bug.cgi?id=396735 Bug ID: 396735 Summary: Add a setting to hide loop devices created by snapd (or maybe squashfs filesystems) Product: kdf Version: 18.04 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mlippert...@gmail.com Target Milestone: --- KDiskFree could use the ability to hide loop devices created by snapd or perhaps the ability to hide mounts of type "squashfs" (since they're read-only and have no free space, seeing them is not helpful most of the time). Right now when I open KDiskFree I see a sea of red at the top (since loop comes before sda*) none of which is interesting when I run KDiskFree to get a sense of how full the partitions I write to are. There may be occasions when having the loop devices listed is useful (just seeing them enumerated in a gui is useful, as is seeing their sizes), but that's more of an exceptional case. also see bug 379516 which was for frameworks-solid -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167
--- Comment #20 from Mike Lothian ---
On bootup, could it be that Wayland is starting before VT2 is setup/created?
First boot:
fireburn@sky ~ $ ps -ef | grep X
root 405 379 1 11:18 tty1 00:00:00 /usr/libexec/Xorg -nolisten tcp
-auth /var/run/sddm/{ea6c489d-82b5-4ba2-a0c8-d0fad97fe1ea} -background none
-noreset -displayfd 17 -seat seat0 vt1
fireburn 467 463 4 11:18 ?00:00:01 /usr/bin/Xwayland -displayfd 30
-rootless -wm 33
Restart Session:
fireburn@sky ~ $ ps -ef | grep X
root 712 379 1 11:17 tty1 00:00:00 /usr/libexec/Xorg -nolisten tcp
-auth /var/run/sddm/{6e63afef-6365-4f51-8bb7-9f300774a7be} -background none
-noreset -displayfd 17 -seat seat0 vt1
fireburn 780 775 2 11:17 tty2 00:00:00 /usr/bin/Xwayland -displayfd 40
-rootless -wm 43
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 396547] no apparent activity at all but using near 400Mib of RAM according to KSysGuard
https://bugs.kde.org/show_bug.cgi?id=396547 --- Comment #3 from Mike Simms --- recreated a couple of times with clean installs this morning. it's a definite bug unfortunately. steps to recreate: 1. clean install 2. when prompted to install 25 updates, attempt to do so. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396547] no apparent activity at all but using near 400Mib of RAM according to KSysGuard
https://bugs.kde.org/show_bug.cgi?id=396547 --- Comment #2 from Mike Simms --- I sent the KILL signal to the Discover process from KSysGuard. Then tried starting the Discover program again. This time it worked and prompted me for my password before applying the updates successfully. I'm not 100% sure but it looks like an authentication request failure caused the problem the first time Discover ran. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396547] no apparent activity at all but using near 400Mib of RAM according to KSysGuard
https://bugs.kde.org/show_bug.cgi?id=396547 --- Comment #1 from Mike Simms --- running in a Wayland session if that makes any difference -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396547] New: no apparent activity at all but using near 400Mib of RAM according to KSysGuard
https://bugs.kde.org/show_bug.cgi?id=396547 Bug ID: 396547 Summary: no apparent activity at all but using near 400Mib of RAM according to KSysGuard Product: Discover Version: 5.13.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: micsi...@googlemail.com Target Milestone: --- Created attachment 113956 --> https://bugs.kde.org/attachment.cgi?id=113956=edit Discover and KSysGuard screenshots Clean install of KDE Neon 5.13.2 tonight. I was prompted to install 25 updates by Discover's update notification so went ahead and selected all of them and clicked to install. There's only 93.5Mib of downloads but nothing is happening. My internet connection is fine so not sure what the problem is. ISO downloaded: https://files.kde.org/neon/images/neon-useredition/current/neon-useredition-20180705-1025-amd64.iso sha256sum was okay and the media burnt successfully. I don't think it's a corrupt installation as there were no error messages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396527] Dolphin MTP protocol support: "Died unexpectedly" if user has Amarok opened
https://bugs.kde.org/show_bug.cgi?id=396527 --- Comment #2 from Mike Krutov --- Jamie, yep, that is the point - it took a while for me to figure out that amarok is the culprit which blocks MTP. Dolphin should check for amarok, then ask user if user wants to disable amarok MTP plugin instead of just saying that it was unable to mount MTP device. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396527] New: Dolphin MTP protocol support: "Died unexpectedly" if user has Amarok opened
https://bugs.kde.org/show_bug.cgi?id=396527 Bug ID: 396527 Summary: Dolphin MTP protocol support: "Died unexpectedly" if user has Amarok opened Product: dolphin Version: 18.04.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nekoxmach...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Steps to reproduce: 1) Connect android phone, while having Amarok opened 2) Try to mount MTP "Android" device in Dolphin 3) See "MTP died unexpectedly" Reproducibility: 100%. Moment Amarok is closed, Dolphine works flawlessly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396527] Dolphin MTP protocol support: "Died unexpectedly" if user has Amarok opened
https://bugs.kde.org/show_bug.cgi?id=396527 Mike Krutov changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #15 from Mike Lothian --- Created attachment 113861 --> https://bugs.kde.org/attachment.cgi?id=113861=edit kdeglobals after delete --- Comment #16 from Mike Lothian --- Created attachment 113862 --> https://bugs.kde.org/attachment.cgi?id=113862=edit kdeglobals after delete -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #15 from Mike Lothian --- Created attachment 113861 --> https://bugs.kde.org/attachment.cgi?id=113861=edit kdeglobals after delete -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396161] Native X programs seem to be double zoomed on hidpi
https://bugs.kde.org/show_bug.cgi?id=396161 --- Comment #14 from Mike Lothian --- So I deleted my kdeglobals on both my laptop and media box which are both connected to 4K displays that normally run with Scale 2, since deleting that file however, icons look smaller under X11 I do now remember manually increasing the icon size when I first switched to Scale 2. Before I was using a QT environment variable (QT_DEVICE_PIXEL_RATIO=2) I've double checked that this is disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #19 from Mike Lothian --- Would you like me to create a new bug for this issue? Could it be the auto logon doing something screwy? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #16 from Mike Lothian --- Here's the diff between the two diff -u0 env.firstboot env.restartedSession --- env.firstboot 2018-07-06 09:41:15.353376835 +0100 +++ env.restartedSession2018-07-06 09:42:43.555992997 +0100 @@ -10 +10 @@ -SHELL_SESSION_ID=f09d54d32a4e41ff945d0d28cc031101 +SHELL_SESSION_ID=c15f0b195ead455bbde690e9f8782f6f @@ -16 +16 @@ -XDG_VTNR=1 +XDG_VTNR=2 @@ -20 +20 @@ -XDG_SESSION_ID=c1 +XDG_SESSION_ID=c3 @@ -29 +29 @@ -XDG_SESSION_TYPE=x11 +XDG_SESSION_TYPE=wayland @@ -36 +35,0 @@ -GTK_MODULES=canberra-gtk-module @@ -43 +42 @@ -KONSOLE_DBUS_SERVICE=:1.32 +KONSOLE_DBUS_SERVICE=:1.27 @@ -51,0 +51 @@ +QT_WAYLAND_DISABLE_WINDOWDECORATION=1 @@ -57 +57 @@ -WINDOWID=6291463 +WINDOWID=1 @@ -60 +60 @@ -DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-DDAQDmC9XR,guid=1afbe537d8aab7b3ed4a73575b3f2abc +DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-OTaCi1PozB,guid=80b520e5d9ec2cb030ce605c5b3f2b65 @@ -62,2 +62 @@ -XAUTHORITY=/home/fireburn/.Xauthority -XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 +XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2 @@ -70 +69 @@ -SESSION_MANAGER=local/sky.fireburn.co.uk:@/tmp/.ICE-unix/564,unix/sky.fireburn.co.uk:/tmp/.ICE-unix/564 +SESSION_MANAGER=local/sky.fireburn.co.uk:@/tmp/.ICE-unix/867,unix/sky.fireburn.co.uk:/tmp/.ICE-unix/867 I've not noticed when I first boot I can't VT switch, once I've logged out and back in again, Plasma is running on VT2 and VT1 is a black screen with an unthemed mouse cursor Also on the first boot on the part of the screen that's black, it I move the mouse there the mouse cursor is unthemed too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #17 from Mike Lothian --- Created attachment 113796 --> https://bugs.kde.org/attachment.cgi?id=113796=edit sddm.conf -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #14 from Mike Lothian --- Created attachment 113794 --> https://bugs.kde.org/attachment.cgi?id=113794=edit env first boot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #15 from Mike Lothian --- Created attachment 113795 --> https://bugs.kde.org/attachment.cgi?id=113795=edit env after logout and log back in -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #12 from Mike Lothian --- So what is the correct avenue to get this issue resolved? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #10 from Mike Lothian --- Martin, you want people to switch to Wayland, you've made clear that X11 is in maintenance only How on earth are people supposed to use Wayland as a daily driver when switching causes issues? I realise this bug might now be in kwin_wayland itself - it could possibly be in SDDM or some other component, but currently when I first start this machine with wayland it does one thing and when I restart the session it does another - that I hope you can see is a bug You say start a proper wayland session but you don't say _how_ if I'm making a mistake, please point it out. I was under the impression that simply changing the default session in SDDM was enough -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Mike Lothian changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|REOPENED --- Comment #8 from Mike Lothian --- When the bug is resolved to my satisfaction I'll close the bug How does one start a proper Wayland session? Is starting Plasma (Wayland) from SDDM not enough? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #6 from Mike Lothian --- Created attachment 113776 --> https://bugs.kde.org/attachment.cgi?id=113776=edit After logout and back in again -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 --- Comment #5 from Mike Lothian --- Created attachment 113775 --> https://bugs.kde.org/attachment.cgi?id=113775=edit First boot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167
Mike Lothian changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED|REOPENED
--- Comment #4 from Mike Lothian ---
So the reason the 1080p resolution wasn't showing up was because
CONFIG_DRM_VMWGFX_FBCON=y wasn't set in my kernel
However now when my Wayland session starts at boot it takes up a small portion
of the screen
Under "Display and Monitor" it says the screen name is XWAYLAND0 and the
resolution is 1024x768 and that field is not selectable
/usr/libexec/Xorg -nolisten tcp -auth
/var/run/sddm/{f44714bd-0d30-4035-a483-39ff732022cf} -background none -noreset
-displayfd 17 -seat seat0 vt1
/usr/bin/Xwayland -displayfd 30 -rootless -wm 33
/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/lib64/libexec/startplasma
If I logout and back in again it runs at 1080p and "Display and Monitor" says
Virtual-1-unknown and I'm able to change resolutions
I double checked the 2nd login was definitely running wayland:
/usr/libexec/Xorg -nolisten tcp -auth
/var/run/sddm/{9f9e7eba-e4ee-409e-98be-c0c4a3bc8039} -background none -noreset
-displayfd 17 -seat seat0 vt1
/usr/bin/Xwayland -displayfd 40 -rootless -wm 43
/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/lib64/libexec/startplasma
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 396167] Unable to specify a resolution to kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=396167 Mike Lothian changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- Ever confirmed|0 |1 --- Comment #2 from Mike Lothian --- Ignoring VMware, how does one specify a different mode on kwin_wayland? -- You are receiving this mail because: You are watching all bug changes.
