[neon] [Bug 488033] KDE Neon developer edition’s installer won’t launch
https://bugs.kde.org/show_bug.cgi?id=488033 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #2 from Stuart K. Smith --- Using a VM and the KDEneon Developer ISO dated 05/27, I launched Calamares from Konsole instead of using the graphical launcher and it revealed this error message: filesystem not found "/run/live/medium/live/filesystem.squashfs" The file itself - filesystem.squashfs - exists on the ISO in "casper", so I created the directory "/run/live/medium/live" and symlinked to "/cdrom/casper/filesystem.squashfs" in it. Voila, the installer ran. It still crashed at grub-install (I didn't take the time to prep the drive properly) but it did do the installation. Clearly, it seems, a Debian Calamares set up was used and not edited to work with KDEneon. Notably, this is now the THIRD time there has been a Calamares mis-configuration in the last 6 weeks or so. Previously there were typos relating to networking and one other thing I can't recall at the moment. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486925] "EQ and Filters" Audio effects no Impact
https://bugs.kde.org/show_bug.cgi?id=486925 Stuart changed: What|Removed |Added Version|24.02.0 |24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486925] "EQ and Filters" Audio effects no Impact
https://bugs.kde.org/show_bug.cgi?id=486925 Stuart changed: What|Removed |Added Version|24.02.2 |24.02.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486925] "EQ and Filters" Audio effects no Impact
https://bugs.kde.org/show_bug.cgi?id=486925 Stuart changed: What|Removed |Added CC||stuar...@linux.com --- Comment #1 from Stuart --- I can confirm this as well. I recently installed Ubuntu 24.04 and downloaded Kdenlive Version 24.02.2 AppImage from the official Kdenlive website. For some inexplicable reason, most of my audio effects are not working. I can add them to the audio clips, but they have no effect whatsoever. Here are the steps I’ve taken so far: * Tried using the Kdenlive version from the Ubuntu repository. * Tested older AppImage versions of Kdenlive. Unfortunately, none of these attempts resolved the issue. Below, I’ve attached the terminal output I get when running Kdenlive. Any help or suggestions would be greatly appreciated. ## Hardware Information:## - **Hardware Model:** Micro-Star International Co., Ltd. MS-7D41 - **Memory:** 64.0 GiB - **Processor:** 13th Gen Intel® Core™ i7-13700KF × 24 - **Graphics:** NVIDIA GeForce RTX™ 4070 - **Disk Capacity:** 6.0 TB ## Software Information:## - **Firmware Version:** 2.D0 - **OS Name:**Ubuntu 24.04 LTS - **OS Build:** (null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:** X11 - **Kernel Version:**Linux 6.8.0-31-generic ## Terminal Output:## kdenlive-24.02.2-x86_64.AppImage’ Loaded icon theme: “breeze” Loaded icon theme: “breeze-dark” kf.config.core: Watching absolute paths is not supported “/tmp/.mount_kdenliuRGRlr/usr/share/color-schemes/BreezeDark.colors” Starting render server profilePath from $MLT_PROFILES_PATH: “/tmp/.mount_kdenliuRGRlr/usr/share/mlt-7/profiles/” meltPath from KdenliveSetting::meltPath: “/tmp/.mount_kdenliuRGRlr/usr/bin/melt” plugin not available: “region” Empty metadata for “glsl.manager” Empty metadata for “telecide” plugin not available: “avfilter.acompressor” plugin not available: “avfilter.aecho” plugin not available: “avfilter.agate” plugin not available: “avfilter.atadenoise” plugin not available: “avfilter.bs2b” plugin not available: “avfilter.bwdif” plugin not available: “avfilter.deblock” plugin not available: “avfilter.dedot” plugin not available: “avfilter.deflate” plugin not available: “avfilter.derain” plugin not available: “avfilter.doubleweave” plugin not available: “avfilter.field” plugin not available: “avfilter.framestep” plugin not available: “avfilter.fspp” plugin not available: “avfilter.graphmonitor” plugin not available: “avfilter.hqdn3d” plugin not available: “avfilter.inflate” plugin not available: “avfilter.lagfun” plugin not available: “avfilter.loudnorm” plugin not available: “avfilter.random” plugin not available: “avfilter.removegrain” plugin not available: “avfilter.separatefields” plugin not available: “avfilter.shuffleplanes” plugin not available: “avfilter.sofalizer” plugin not available: “avfilter.sr” plugin not available: “avfilter.tmix” plugin not available: “avfilter.w3fdif” plugin not available: “avfilter.weave” plugin not available: “avfilter.yadif” plugin not available: “frei0r.baltan” plugin not available: “frei0r.bgsubtract0r” plugin not available: “frei0r.delay0r” plugin not available: “frei0r.delaygrab” plugin not available: “frei0r.lightgraffiti” plugin not available: “frei0r.lightgraffiti” plugin not available: “frei0r.tehRoxx0r” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “ladspa” plugin not available: “movit.unsharp_mask” plugin not available: “timewarp” === /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER qt.qml.typeresolution.cycle: Cyclic dependency detected between “qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml” and “qrc:/qt/qml/org/kde/desktop/MenuItem.qml” qt.qml.typeresolution.cycle: Cyclic dependency detected between “qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml” and “qrc:/qt/qml/org/kde/desktop/MenuItem.qml” begin OpenGL vendor “NVIDIA Corporation” OpenGL renderer “NVIDIA GeForce RTX 4070/PCIe/SSE2” OpenGL threaded? true OpenGL ES? false OpenGL maximum texture
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 --- Comment #15 from Stuart K. Smith --- Another alternative to have the needed functionality is to install Webmin on the system in question and launch it locally. I still believe it would be preferable to have the needed functionality native to Plasma 5/6 -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from Stuart K. Smith --- NOT resolved. No actual way to modify users from System Settings of than: Name, Username, Account type, Email address. The old KUser allowed editing of Home directory, Groupmemberships (and editing of Groups themselves), and login shell. At a minimum, the ability to add a user to a group is required unless the decision has been made to move all administrative tasks to the command line. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482993] New: Dolphin no longer handling group permissions correctly
https://bugs.kde.org/show_bug.cgi?id=482993 Bug ID: 482993 Summary: Dolphin no longer handling group permissions correctly Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: stuartksm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY: Previously, folders not owned by the user were fully accessible via Dolphin if the user had group membership and permissions. This version of Dolphin appears to disregard group permissions when the user is not the owner. STEPS TO REPRODUCE 1. Create a folder not owned by your user but with any group your user belongs to. 2. Set permissions of the folder to drwxrwxr_x. 3. Open Dolphin and right-click on the folder to open the context menu OBSERVED RESULT Notice that these three menu options are grayed out: "Create New", "Duplicate Here", and "Compress". The same results are observed when entering the test folder and right-clicking on the empty space. NOTE: I can drag and drop items into the un-owned folder but the associated mouse cursor shows "not permitted" symbol (red circle with line through it). EXPECTED RESULT If the user has group access to a folder the menu options should all be available as they were in previous versions of Dolphin. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480308] Plasmashell crashes when waking up from sleep or connecting/disconnecting monitors
https://bugs.kde.org/show_bug.cgi?id=480308 Stuart Anderson changed: What|Removed |Added CC||stuwander...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480308] Plasmashell crashes when waking up from sleep or connecting/disconnecting monitors
https://bugs.kde.org/show_bug.cgi?id=480308 --- Comment #1 from Stuart Anderson --- Created attachment 165229 --> https://bugs.kde.org/attachment.cgi?id=165229=edit New crash information added by DrKonqi plasmashell (5.24.7) using Qt 5.15.3 - What I was doing when the application crashed: Wake from sleep - Unusual behavior I noticed: Taskbar disappeared briefly, error notification - Custom settings of the application: -- Backtrace (Reduced): #4 0x7f2b247ccb10 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f2b247ccb8a in QSGAreaAllocator::deallocate(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #14 0x7f2b22294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #15 0x7f2b22326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 [...] #5 0x7f2b22d1312e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470788] Tree with folder structure scrolls on top when try to drop email on any folder
https://bugs.kde.org/show_bug.cgi?id=470788 Stuart Morrison changed: What|Removed |Added CC||stu...@hadez.org --- Comment #1 from Stuart Morrison --- This bug looks related to bug 440874 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462482] Folder list scrolls upwards when moving mails to folders
https://bugs.kde.org/show_bug.cgi?id=462482 Stuart Morrison changed: What|Removed |Added CC||stu...@hadez.org --- Comment #1 from Stuart Morrison --- This bug looks related to bug 440874 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 444108] kmail dragging mail to sidebar starts scrolling fast in wayland sessions
https://bugs.kde.org/show_bug.cgi?id=444108 Stuart Morrison changed: What|Removed |Added CC||stu...@hadez.org --- Comment #2 from Stuart Morrison --- This bug looks related to bug 440874 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 444475] can't find music on Android
https://bugs.kde.org/show_bug.cgi?id=75 --- Comment #14 from Stuart Dilts --- It could also be that the correct sqlite dependency is missing from the build environment, which is probably more likely. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 444475] can't find music on Android
https://bugs.kde.org/show_bug.cgi?id=75 Stuart Dilts changed: What|Removed |Added CC||stuart.di...@gmail.com --- Comment #13 from Stuart Dilts --- Based on other places on the web, and the above error message, the problem seems to be that the appropriate .so file for the SQLite driver either isn't being included in the build or isn't found during runtime. The androiddeployqt tool seems to control which qt libraries get included in the build. According to https://doc.qt.io/qt-5/deployment-android.html, it should be able to tell us if the dependency is detected correctly and if it's being included in the build: "If you are wondering why a particular plugin is not included automatically, you can run androiddeployqt with the --verbose option to get the list of missing dependencies for each excluded plugin. You can achieve the same in Qt Creator by ticking the Verbose output check box in the Projects > Build Steps > Build Android APK > Advanced Actions." Looking at the build output for the latest build, (https://binary-factory.kde.org/job/Elisa_Nightly_android-arm/806/console), I see the following output: > -- Skipping > /home/user/Craft/BinaryFactory/android-arm-clang/plugins/sqldrivers/libplugins_sqldrivers_qsqlite_armeabi-v7a.so. > It has unmet dependencies: lib/libsqlite3.so. As a wild guess, will adding a dependency to libsqlite in the CMAKE file resolve the issue? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Stuart Morrison changed: What|Removed |Added CC||stu...@hadez.org --- Comment #2 from Stuart Morrison --- Can replicate. Dragging a message into the folder list tree view causes it to scroll to the top of the list if the folder list tree view is scrollable due to size of folder list entries making it impossible to drop a message into any folders not at the top of the list. This does not happen in a X11 session. Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-24-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470720] New: Manually set coordinates are not preserved across launches of kstars
https://bugs.kde.org/show_bug.cgi?id=470720 Bug ID: 470720 Summary: Manually set coordinates are not preserved across launches of kstars Classification: Applications Product: kstars Version: 3.6.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: a...@randomuseless.info Target Milestone: --- SUMMARY If RA and dec are manually input using "Pointing -> Set Coordinates Manually". It goes to the location properly. If kstars is then quit and reopened, it goes to some oddball RA and dec different from what was entered. In addition, The HiPS images don't display properly until a new location is entered. In versions before 3.6, the code would start up with the map centered on your previously entered RA and dec. This was a feature I used extensively. If "Pointing -> Find Object..." is used instead, it works as one would expect without error. STEPS TO REPRODUCE 1. Start kstars 2. Goto "Pointing -> Find Object..." and enter an object name. e.g. M 61 and hit "OK". The display will center on M 61. 3. quit kstars 4. Start kstars. The display will be centered on M 61 as it was when the program was quit. 5. goto "Pointing -> Set Coordinates Manually...". The dialog will already contain the coordinates of M61 so simply click "OK". The display will not change since it's pointing at the same location. 6. quit kstars 7. Start kstars. The map will be mostly black with some flashing junk from HiPS. Zooming out very far may show some stars in part of the sky. Looking at "Pointing -> Set Coordinates Manually..." will show different coordinates than those for M61. 8. Either "Pointing -> Find object..." or "Pointing -> Set Coordinates Manually..." can be used to select a location and the display will go back to normal. OBSERVED RESULT When restarting after manually entering a coordinate, the sky map will be centered in the wrong location and the HiPS image of the sky will be messed up. EXPECTED RESULT The sky map should be centered on he coordinate entered in the previous session. SOFTWARE/OS VERSIONS Note this fails the same way under both MacOS and Ubuntu. Windows: macOS: 12.6.5 Linux/KDE Plasma: Ubuntu 22.04.2 LTS (available in About System) KDE Plasma Version: I'm using fvwm on the Linux box but it happens on the Mac too, so probably not important KDE Frameworks Version: Qt Version: 5.15.3? (linux), no idea on the Mac ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #5 from Stuart K. Smith --- Seeing the same thing here when kscreen is installed. AMD RX580 and KDEneon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469794] No sound in Dolphin while deleting a file.
https://bugs.kde.org/show_bug.cgi?id=469794 Stuart changed: What|Removed |Added CC||stu...@stella-maris.org.uk -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 469736] New: Device Connect/Diconnect buttons ambiguity when connected to a remote server .
https://bugs.kde.org/show_bug.cgi?id=469736 Bug ID: 469736 Summary: Device Connect/Diconnect buttons ambiguity when connected to a remote server . Classification: Applications Product: kstars Version: 3.6.4 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: sja...@hydrasystems.co.uk Target Milestone: --- Created attachment 158934 --> https://bugs.kde.org/attachment.cgi?id=158934=edit Ekos Configurtion tab SUMMARY Device Connect/Diconnect buttons ambiguity when connected to a remote server . STEPS TO REPRODUCE 1. Running Kstars on Windows 11 2. Configure to connect to remote server eg Rock Pi running Indi Server 3. Start Ekos with auto connect enabled OBSERVED RESULT 'Connect' button enabled. 'Disconnect' button disabled. EXPECTED RESULT 'Connect 'button disabled 'Disconnect' button enabled or both disabled SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: 11 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463218] New: The Discover App fails to load ANY apps whatsoever, and the configuration/settings window offers no means to configure or query ANY backends!
https://bugs.kde.org/show_bug.cgi?id=463218 Bug ID: 463218 Summary: The Discover App fails to load ANY apps whatsoever, and the configuration/settings window offers no means to configure or query ANY backends! Classification: Applications Product: Discover Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jmorgano3...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT 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.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Stuart Prescott changed: What|Removed |Added CC||bugs.kde.org@nanonanonano.n ||et -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 458566] "Restart Game" opens "Save Game" dialog
https://bugs.kde.org/show_bug.cgi?id=458566 --- Comment #2 from Stuart K. Smith --- (In reply to Albert Astals Cid from comment #1) > I think it makes sense, imagine you're almost done and Press F5 by mistake, > having a dialog that lets you save, not save, cancel, makes sense to me As someone who plays the game almost daily, I find it highly annoying and unnecessary. It's rare to solve a game on the first go so restarting is a common thing to do for 3 or 4 rounds at least. An accidental F5 only means you have to start over with the same tiles - something one does anyway. An intentional F5 now means you have to stop what you are doing and close a dialog. If it was an intentional change, it is not a benefit and has a negative impact on game play. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 458566] New: "Restart Game" opens "Save Game" dialog
https://bugs.kde.org/show_bug.cgi?id=458566 Bug ID: 458566 Summary: "Restart Game" opens "Save Game" dialog Product: kmahjongg Version: 0.9.22080 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stuartksm...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Since last update, F5 (Reload Game) results in a "Save Game?" dailog instead of just reloading the current game as in the past. STEPS TO REPRODUCE 1. Start a game and take one or more turns. 2. Press F5 to reload. OBSERVED RESULT Save Game dialog window opens. EXPECTED RESULT No dialog, just the game reloading. 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.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Stuart Morrison changed: What|Removed |Added CC||stu...@hadez.org --- Comment #11 from Stuart Morrison --- (In reply to Kishore Gopalakrishnan from comment #8) > Does anyone still have this issue? STMP with XOAUTH2 on Gmail works for me > without any problems (I earlier had the issue described here). I still have the same problem, SMTP stops working after a while and requires an Akonadi restart so can't realistically use KMail at work any more. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-41-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 --- Comment #7 from Stuart Morgan --- So I played a hunch based on the backtrace and completely wiped everything in the .cache folder. Following this I could no longer reproduce the crash. Since I deleted everything I can't narrow down exactly what file(s) were causing issues and why (doh). Possibly files were in an unexpected format after the upgrade or corrupted somehow (when system ran out of space due to kactivitymanager bug?). Either way, root cause seems to be a KDE bug and lack of sanity checking and error handling obviously needs to be addressed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 --- Comment #6 from Stuart Morgan --- Created attachment 149785 --> https://bugs.kde.org/attachment.cgi?id=149785=edit New crash information added by DrKonqi systemsettings (5.24.5) using Qt 5.15.3 - What I was doing when the application crashed: I open any settings dialog - shortcuts, search plugins, power settings it immediately crashes. - Unusual behavior I noticed: Listing out all issues seen even though it's unlikely that all or even any are connected: Like the original reporter, I also noticed a problem with database-wal in kactivitymanagerd growing uncontrolled until all disk space is consumed - 225GB most recently. I've taken to killing kactivitymanagerd just to prevent this issue. Also having issues with taskbar becoming unresponsive requiring a plasmashell restart. Media and 'windows' key no longer working. The desktop becomes completely unusable after resuming from sleep - very weird render buffer issues it seems like, desktops on two monitors continually switching places and being rendered mirrored in both x and y axis - although it seems even more complex that this as certain (backwards and upside down) characters are also substituted e.g. s becomes e -- Backtrace (Reduced): #11 0x7f76263cc38f in QV4::CompiledData::CompilationUnit::setUnitData(QV4::CompiledData::Unit const*, QV4::CompiledData::QmlUnit const*, QString const&, QString const&) () from /lib64/libQt5Qml.so.5 #12 0x7f76264b6c15 in QV4::ExecutableCompilationUnit::loadFromDisk(QUrl const&, QDateTime const&, QString*) () from /lib64/libQt5Qml.so.5 #13 0x7f7626532627 in QQmlTypeData::tryLoadFromDiskCache() () from /lib64/libQt5Qml.so.5 #14 0x7f7626537603 in QQmlTypeData::dataReceived(QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5 #15 0x7f762658407b in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 Stuart Morgan changed: What|Removed |Added CC||stu...@tase.co.uk -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447677] New: Google Maps not showing correctly
https://bugs.kde.org/show_bug.cgi?id=447677 Bug ID: 447677 Summary: Google Maps not showing correctly Product: digikam Version: 7.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-GoogleMaps Assignee: digikam-bugs-n...@kde.org Reporter: stuart.h...@hey.com Target Milestone: --- Created attachment 144951 --> https://bugs.kde.org/attachment.cgi?id=144951=edit Google Maps error SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Select Google Maps as map provider 2. For development purposes only shows up 3. OBSERVED RESULT 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.
[kscreenlocker] [Bug 415443] Wrong password delay should respect PAM nodelay setting
https://bugs.kde.org/show_bug.cgi?id=415443 Stuart Morgan changed: What|Removed |Added CC||stu...@tase.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 444782] New: Random no sound issue when playing back tracks
https://bugs.kde.org/show_bug.cgi?id=444782 Bug ID: 444782 Summary: Random no sound issue when playing back tracks Product: Elisa Version: 21.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: stu...@tase.co.uk Target Milestone: --- SUMMARY When playing back tracks in Elisa periodically Elisa will output no sound at all. It most often happens from the start of the track and skipping backwards will often fix the issue, although it can take a few tries. Usually when it finishes playing the track and moves to the next track in the playlist the sound resumes. Pavucontrol GUI shows no audio activity from Elisa when this happens but sound from other applications works fine. I've been seeing this issue for a while but with less frequency so it's difficult to know exactly which version it start with. This is in Fedora 34 using pipewire. STEPS TO REPRODUCE 1. Play a playlist 2. At some random point, when it moves to the next track no audio can be heard. 3. Clicking back on the progress bar will sometime 'fix' the issue, until it happens the next time. OBSERVED RESULT No sound from application. EXPECTED RESULT Sound from Application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (fully updated) (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 102142] Unable to select text
https://bugs.kde.org/show_bug.cgi?id=102142 Stuart Morgan changed: What|Removed |Added CC||stu...@tase.co.uk -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Stuart Longland changed: What|Removed |Added OS|Linux |All Platform|Archlinux Packages |unspecified --- Comment #12 from Stuart Longland --- (Changing platform as this is not specific to ArchLinux… I've got the same problem on both Gentoo and Debian.) -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Stuart Longland changed: What|Removed |Added CC||stuartl+...@longlandclan.id ||.au --- Comment #11 from Stuart Longland --- Is there an up-to-date branch that can be tried out? Earlier comments are from 2014 suggesting there was a branch that was incomplete then. My situation: I have effectively three email accounts. My home email account is on Dovecot IMAP, but my workplace has decided to adopt Office365 (not my decision, looking forward to no work email when it stops working on Feb29 each leap year), which despite IMAP namespaces being a Microsoft creation, instead uses whole separate accounts to represent shared mail directories. That means that I need to be able to log in to Office365 as both m...@example.com, and as me\mail...@example.com; simultaneously. --profile isn't workable as the whole point of a shared mail box is that you can move emails in and out of it from your own personal account. Having experimented with Trojitá it's looking promising, but I'm having to put up with Claws mail in the interim due to this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441146] Autosave and recovery for unsaved changes
https://bugs.kde.org/show_bug.cgi?id=441146 --- Comment #2 from Stuart Axon --- Cheers, I'll try and find a way to report them, though not sure I want to submit the exact document (it's a survey of a house). It was pretty fiddly but all I was doing was highlighting items and hitting ctrl-s (sometimes the ctrl-s in quick succession). I realise this isn't that helpful, as the document structure must be important. Part of the reason I thought autosave is useful, is that PDF is a complex legacy format and all sorts of interactions must be possible. I'll try and get more info, but about to be very time starved so it may take a while. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441146] New: Feature request: Autosave and recovery
https://bugs.kde.org/show_bug.cgi?id=441146 Bug ID: 441146 Summary: Feature request: Autosave and recovery Product: okular Version: 21.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: stu.a...@gmail.com Target Milestone: --- It would be good if Okular had an autosave option. I was adding a lot of highlights to a 79 page document and crashed it 3 times. One of the times I corrupted the file I was saving (using the archive feature). (I may have hit save while it was already saving / restoring?) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 437099] Changing the track rating is quite clumsy
https://bugs.kde.org/show_bug.cgi?id=437099 Stuart Morgan changed: What|Removed |Added CC||stu...@tase.co.uk --- Comment #2 from Stuart Morgan --- This probably merits a separate ticket, but it should also read (and optionally write) the ratings from the file metadata/tags if present. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437114] System Monitor widgets cannot be used to replicate appearance and functionality of the old System Load Viewer widget
https://bugs.kde.org/show_bug.cgi?id=437114 Stuart changed: What|Removed |Added CC||stu...@stella-maris.org.uk -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 436479] New: KCrash
https://bugs.kde.org/show_bug.cgi?id=436479 Bug ID: 436479 Summary: KCrash Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: stuart.e...@olcs.com.au Target Milestone: --- Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault [KCrash Handler] #4 0x7f777c2ca9aa in wl_proxy_marshal_constructor () from /lib64/libwayland-client.so.0 #5 0x7f777c3550d7 in QtWaylandClient::QWaylandDisplay::createSurface(void*) () from /lib64/libQt5WaylandClient.so.5 #6 0x7f777c36179c in QtWaylandClient::QWaylandSurface::QWaylandSurface(QtWaylandClient::QWaylandDisplay*) () from /lib64/libQt5WaylandClient.so.5 #7 0x7f777c35396a in QtWaylandClient::QWaylandWindow::initializeWlSurface() () from /lib64/libQt5WaylandClient.so.5 #8 0x7f777c36129d in QtWaylandClient::QWaylandShmWindow::QWaylandShmWindow(QWindow*, QtWaylandClient::QWaylandDisplay*) () from /lib64/libQt5WaylandClient.so.5 #9 0x7f777c34ff61 in QtWaylandClient::QWaylandIntegration::createPlatformWindow(QWindow*) const () from /lib64/libQt5WaylandClient.so.5 #10 0x7f777de188c0 in QWindowPrivate::create(bool, unsigned long long) () from /lib64/libQt5Gui.so.5 #11 0x7f777e5bdae5 in QWidgetPrivate::create() () from /lib64/libQt5Widgets.so.5 #12 0x7f777e5be02e in QWidget::create(unsigned long long, bool, bool) () from /lib64/libQt5Widgets.so.5 #13 0x7f777e5cb22e in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #14 0x7f777e78a608 in QDialog::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #15 0x5566b4bf2c45 in main () [Inferior 1 (process 591739) detached] -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #8 from Stuart K. Smith --- Tested this on Debian Sid with Plasma 5.20.5/ Frameworks 5.78.0 and no error. Still seems to be an (K)Ubuntu problem -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #6 from Stuart K. Smith --- Just checked on an updated Manjaro KDE running plasma 5.21.3 and OK there. Must be related to Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 --- Comment #4 from Stuart K. Smith --- Same again on 20.10 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 434635] Partition Manager's Help files can not be parsed in Help Center
https://bugs.kde.org/show_bug.cgi?id=434635 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #3 from Stuart K. Smith --- I am seeing the same results on Kubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 426177] Palapeli fails to run
https://bugs.kde.org/show_bug.cgi?id=426177 --- Comment #4 from Stuart Langridge --- No worries, and thank you for that Justin. I thought it was a bit strange myself; maybe I should have picked up on the product being wrong in the bug filing link! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426177] Palapeli fails to run
https://bugs.kde.org/show_bug.cgi?id=426177 Stuart Langridge changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #2 from Stuart Langridge --- I am reporting it to the snap creator. https://snapcraft.io/palapeli shows that KDE is the snap creator (and verified), and the "Contact KDE" link there is to https://bugs.kde.org/enter_bug.cgi?product=neon=Snaps which is what I used to file this issue, as requested. -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 260163] Character formating when entire paragraph selected should affect paragraph
https://bugs.kde.org/show_bug.cgi?id=260163 --- Comment #3 from Stuart Jarvis --- This issue persists as originally reported (tested today in Calligra Words Version 3.2.1 on Fedora 33. The workaround mentioned by Thomas still exists (explicitly set paragraph font), so this is really just something that works differently to all other word processors I have used and so perhaps confusing to the user, rather than a bug per se. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on starting connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 --- Comment #5 from stuart --- Pleas note, the crashes started before upgrading postgresql, so this is not related to postgresql upgrade. Further, if I revert akonadi to 20.04, it connects ok, and is usable. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on starting connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 stuart changed: What|Removed |Added Summary|Any version of |Any version of |akonadi-server after 20.04 |akonadi-server after 20.04 |fails on staring connection |fails on starting |to backend postgresql |connection to backend |database|postgresql database -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 --- Comment #3 from stuart --- This started in August after the initial upgrade to 20.08 while I was running postgresql 12.4. I later upgraded to postgresql t0 13.1. After reverting to 20.04, akonadi successfully connects to the backend. I do see in the akonadictl output that the database version may not be supported, but I don't see this message in v20.04, so I don't think this is related to the database version. The revert has been a workaround, but I was hoping for an eventual fix. Since this has persisted, I am opening this bug report. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 stuart changed: What|Removed |Added CC||sfbar...@gmail.com --- Comment #2 from stuart --- Created attachment 134257 --> https://bugs.kde.org/attachment.cgi?id=134257=edit akonadi.error.old file akonadi.error is blank on this test, but akonadi.error.old shows errors. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 --- Comment #1 from stuart --- Created attachment 134256 --> https://bugs.kde.org/attachment.cgi?id=134256=edit postgresql log during akonadi query failure -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 430689] New: Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database
https://bugs.kde.org/show_bug.cgi?id=430689 Bug ID: 430689 Summary: Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database Product: Akonadi Version: 5.15.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: sfbar...@gmail.com Target Milestone: --- Created attachment 134255 --> https://bugs.kde.org/attachment.cgi?id=134255=edit console output of akonadictl start --verbose SUMMARY After Tumbleweed distribution upgrade, akonadi-server updated from 20.04 to 20.08. All later packages report the same error attempting to start. Error during selection of all records from table "SchemaVersionTable" "SSL SYSCALL error: Bad file descriptor\n() QPSQL: Unable to create query" "SELECT version, generation FROM SchemaVersionTable" STEPS TO REPRODUCE 1. Setup and start local postgres db server 2. Configure akonadi to user postgres as backend db 3. akonadictl start OBSERVED RESULT akonadi performs many queries to the db successfully, but then starts failing with multiple errors Error during selection of all records from table "SchemaVersionTable" "SSL SYSCALL error: Bad file descriptor\n() QPSQL: Unable to create query" "SELECT version, generation FROM SchemaVersionTable" EXPECTED RESULT Register new connection notifications: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f5e7c0d9cf0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f5e7c0f5630) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f5e7c0fdfb0) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f5e7c1073d0) ) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuSE Tumbleweed > 2020-08-18 (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 PostgreSQL: 13.1 ADDITIONAL INFORMATION I can revert to the following packages from openSuSE Leap 15.2 which contain akonadi v20.04 and akonadi-server starts ok. Also, since release 20.12, I have to first remove these packages rpm -ev libKPimAddressbookImportExport5 kaddressbook kdepim-addons kaddressbook-lang korganizer kmail kdepim-addons-lang korganizer-lang pim-sieve-editor kmail-lang pim-sieve-editor-lang Preparing packages... kmail-20.12.0-172.1.x86_64 kaddressbook-20.12.0-153.2.x86_64 korganizer-20.12.0-149.1.x86_64 kdepim-addons-20.12.0-187.1.x86_64 pim-sieve-editor-20.12.0-141.1.x86_64 pim-sieve-editor-lang-20.12.0-141.1.noarch libKPimAddressbookImportExport5-20.12.0-153.2.x86_64 kdepim-addons-lang-20.12.0-187.1.noarch korganizer-lang-20.12.0-149.1.noarch kaddressbook-lang-20.12.0-153.2.noarch kmail-lang-20.12.0-172.1.noarch then revert to these, with rpm -Uvh --oldpackage akonadi-calendar-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-calendar-tools-20.04.2-lp152.1.1.x86_64.rpm akonadi-calendar-tools-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-contact-20.04.2-lp152.1.1.x86_64.rpm akonadi-contact-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-import-wizard-20.04.2-lp152.1.1.x86_64.rpm akonadi-import-wizard-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-mime-20.04.2-lp152.1.1.x86_64.rpm akonadi-mime-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-notes-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-plugin-calendar-20.04.2-lp152.1.1.x86_64.rpm akonadi-plugin-contacts-20.04.2-lp152.1.1.x86_64.rpm akonadi-plugin-kalarmcal-20.04.2-lp152.1.1.x86_64.rpm akonadi-plugin-mime-20.04.2-lp152.1.1.x86_64.rpm akonadi-search-20.04.2-lp152.1.1.x86_64.rpm akonadi-search-lang-20.04.2-lp152.1.1.noarch.rpm akonadi-server-20.04.2-lp152.1.1.x86_64.rpm akonadi-server-lang-20.04.2-lp152.1.1.noarch.rpm akregator-20.04.2-lp152.1.1.x86_64.rpm akregator-lang-20.04.2-lp152.1.1.noarch.rpm calendarsupport-20.04.2-lp152.1.1.x86_64.rpm calendarsupport-lang-20.04.2-lp152.1.1.noarch.rpm eventviews-20.04.2-lp152.1.1.x86_64.rpm eventviews-lang-20.04.2-lp152.1.1.noarch.rpm incidenceeditor-20.04.2-lp152.1.1.x86_64.rpm incidenceeditor-lang-20.04.2-lp152.1.1.noarch.rpm kaccounts-integration-20.04.2-lp152.1.1.x86_64.rpm kaccounts-integration-lang-20.04.2-lp152.1.1.noarch.rpm kaccounts-providers-20.04.2-lp152.1.1.x86_64.rpm kaccounts-providers-lang-20.04.2-lp152.1.1.noarch.rpm kaddressbook-20.04.2-lp152.1.1.x86_64.rpm kaddressbook-doc-20.04.2-lp152.1.1.noarch.rpm kaddressbook-lang-20.04.2-lp152.1.1.noarch.rpm kalarmcal-20.04.2-lp152.1.1.x86_64.rpm kalarmcal-lang-20.04.2-lp152.1.1.noarch.rpm kdepim-addons-20.04.2-lp152.1.1.x86_64.rpm kdepim-addons-lang-20.04.2-lp152.1.1.noarch.rpm kdepim-apps-libs-20.04.2-lp152.1.1.x86_64.rpm
[krita] [Bug 428376] Selecting Save won't overwrite the file and I have to SaveAs new file
https://bugs.kde.org/show_bug.cgi?id=428376 --- Comment #7 from Stuart McWhinney --- I have replicated the same save difficulty in the document folder. There are no folder restricitons that would prevent it from saving into its own file location. === SESSION: 01 Nov 2020 21:55:54 +0900. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 4.4.1, Qt version compiled: 5.12.9, loaded: 5.12.9. Process ID: 16348 -- -- -- -- -- -- -- -- ... 02 Nov 2020 23:19:53 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Documents/test.kra. Real location: C:/Users/Stuart/Documents/test.kra. Batchmode: 0 02 Nov 2020 23:19:54 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 02 Nov 2020 23:20:08 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Documents/test.kra. Real location: C:/Users/Stuart/Documents/test.kra. Batchmode: 0 02 Nov 2020 23:20:09 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 02 Nov 2020 23:20:23 +0900: Saving Document C:/Users/Stuart/Documents/test.kra as C:/Users/Stuart/Documents/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 02 Nov 2020 23:20:23 +0900: Failed to create a simple backup for C:/Users/Stuart/Documents/test.kra in the same location as the file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428376] Selecting Save won't overwrite the file and I have to SaveAs new file
https://bugs.kde.org/show_bug.cgi?id=428376 Stuart McWhinney changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Stuart McWhinney --- SESSION: 01 Nov 2020 21:24:24 +0900. Executing C:\Program Files\Krita (x64)\bin\krita.exe C:\Users\Stuart\Desktop\test.kra Krita Version: 4.4.0, Qt version compiled: 5.12.9, loaded: 5.12.9. Process ID: 12720 -- -- -- -- -- -- -- -- 01 Nov 2020 21:24:24 +0900: Style: fusion. Available styles: windowsvista, Windows, Fusion 01 Nov 2020 21:24:40 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Desktop/test.kra. Real location: C:/Users/Stuart/Desktop/test.kra. Batchmode: 0 01 Nov 2020 21:24:41 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 01 Nov 2020 21:25:25 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Desktop/xxx.kra. Real location: C:/Users/Stuart/Desktop/xxx.kra. Batchmode: 0 01 Nov 2020 21:25:29 +0900: Loaded image from application/x-krita. Size: 1400 * 990 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB IEC61966-2.1). Layers: 8 01 Nov 2020 21:26:09 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Desktop/test.kra. Real location: C:/Users/Stuart/Desktop/test.kra. Batchmode: 0 01 Nov 2020 21:26:09 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 01 Nov 2020 21:26:23 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:26:23 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:26:31 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:26:31 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:26:38 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:26:38 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:27:15 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Desktop/test.kra. Real location: C:/Users/Stuart/Desktop/test.kra. Batchmode: 0 01 Nov 2020 21:27:16 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 01 Nov 2020 21:27:27 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:27:27 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:28:16 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:28:16 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:28:25 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3 layers. 101 frames, 24 framerate. Export configuration: No configuration 01 Nov 2020 21:28:25 +0900: Failed to create a simple backup for C:/Users/Stuart/Desktop/test.kra in the same location as the file. 01 Nov 2020 21:29:11 +0900: Importing application/x-krita to application/x-krita. Location: C:/Users/Stuart/Desktop/test.kra. Real location: C:/Users/Stuart/Desktop/test.kra. Batchmode: 0 01 Nov 2020 21:29:11 +0900: Loaded image from application/x-krita. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 3 01 Nov 2020 21:29:19 +0900: Saving Document C:/Users/Stuart/Desktop/test.kra as C:/Users/Stuart/Desktop/test.kra (mime: application/x-krita). 1920 * 1080 pixels, 3
[krita] [Bug 428376] Selecting Save won't overwrite the file and I have to SaveAs new file
https://bugs.kde.org/show_bug.cgi?id=428376 --- Comment #2 from Stuart McWhinney --- The file is only open with Krita and is saved on the desktop. I tried creating a test file in Documents as well, but the same result. > Save doesn't overwrite the file > SaveAs doesn't overwrite the file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428376] New: Selecting Save won't overwrite the file and I have to SaveAs new file
https://bugs.kde.org/show_bug.cgi?id=428376 Bug ID: 428376 Summary: Selecting Save won't overwrite the file and I have to SaveAs new file Product: krita Version: 4.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mcwhi...@gmail.com Target Milestone: --- SUMMARY The asterisk (*) appears next to my file name to indicate there are unsaved changes. No matter hotkey or menu a save, the asterisk doesn't disappear and the the file is not overwritten to update the changes made. When prompting SaveAs, if I select the file and select to overwrite the old file, it won't and to save any progress I have to keep making new files along the way. SOFTWARE/OS VERSIONS Windows: 10 for Surface Pro 3 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.
[krita] [Bug 427735] Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering
https://bugs.kde.org/show_bug.cgi?id=427735 --- Comment #4 from Stuart McWhinney --- I was using the return key, but after switching to the ! key command, it works as it should. Thank you for your assistance. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427735] Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering
https://bugs.kde.org/show_bug.cgi?id=427735 --- Comment #2 from Stuart McWhinney --- I can create blank frames by alternating the right arrow and the shortcut, however if I draw on the blank frame, I can only move with the arrows rather and no longer create new frames. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427735] New: Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering
https://bugs.kde.org/show_bug.cgi?id=427735 Bug ID: 427735 Summary: Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering Product: krita Version: 4.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: mcwhi...@gmail.com Target Milestone: --- SUMMARY hotkey to make a blank frame needs reseleciton of Timeline Docker to trigger. STEPS TO REPRODUCE 1. blank frame keyframe hotkey 2. arrow key to new frame 3. *cannot hit hotkey to make new keyframe OBSERVED RESULT Need to mouseclick on the Timeline Docker to enable hotkey to trigger. 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.
[neon] [Bug 426177] New: Palapeli fails to run
https://bugs.kde.org/show_bug.cgi?id=426177 Bug ID: 426177 Summary: Palapeli fails to run Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: sil-...@kryogenix.org CC: neon-b...@kde.org Target Milestone: --- SUMMARY $ palapeli /snap/palapeli/29/kf5-launch: line 209: /snap/palapeli/29/kf5-locale-gen: No such file or directory STEPS TO REPRODUCE 1. Install Palapeli from Ubuntu Software. 2. Run it, and nothing happens. 3. Run it from a terminal to see the above error. SOFTWARE/OS VERSIONS Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424775] I will NOT go out to a bank or ANY institution and retrieve any data!, I have USED Quicken for years. I printed the connection data, tested each by hand with a browser. and
https://bugs.kde.org/show_bug.cgi?id=424775 --- Comment #6 from Richard L. Stuart --- Guys it was NOT my intent to come across in that way. There is a typo in the reference you make. - it seriously change things. The quote: "I will NOT go out to a bank " Should have been "It will NOT go out to a bank... simple meaning that none of my attenpt to get it to retrieve the banking transaction - would not result in the software connecting to a bank or credit card institution. Basically nothing happened. My bad, the t was missing - I should have been IT. Some play you all asked where I am located and I forgot to respond to that part. I am in Columbia, Maryland. Additionally, You ask for me to review the wording. Very Happy to do that -- HOW, were do I go etc. and what login is required?? Thanks for the support. PS: Mint update doesn't seem to further update. I have used Ubuntu, Centos and I could change for this purpose if repositories for them would have a later version. Or as with some distros, they have various packages all ready installed. Like Libre Office etc. Is there a distro, ISO with KMyMoney installed. I could run it in Virtualbox and get familiar with it. Actually, I run Quicken in a Virtualbox with WIN 10 as the Isolation provides a bit more security. - As "Box" is shutdown normally and some what hidden. Anyway let make ammends somehow. If you want to edit my earlier imput - I am happy with that.. Richard On 7/29/20 8:26 PM, Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=424775 > > --- Comment #5 from Jack --- > Richard - a lot of this is in the wording. Please consider editing the > subject. It starts by saying "I will NOT go out to a bank " which sounds > like you are refusing to do what the program requires. I now suspect you > meant > that you couldn't find a way to make to program download data from the bank. > A > good start here would be to reword the subject. Second, if you reply by > email, > and not directly at bugs.kde.org, you can trim all the original unless you > explicitly need to show what you are referring to. The bug system just takes > your entire email and makes it the next comment. > > If you had dome much searching, you would have found many cases in the > kmymoney > mailing list of people with problems importing lots of data from Quicken. In > addition to what Brendan said, those threads probably have additional > suggestions. > > Now - I think the bottom line is not that you are reporting a bug, but asking > for help getting started using KMyMoney. That is better done on the mailing > list (see https://mail.kde.org/mailman/listinfo/kmymoney as well as > https://kmymoney.org/support.html for other ways of getting help. > > Finally, it's really good to work at one or maybe two parts of the problem at > a > time. If you've been working at it for days, and then put all the problems > you've had in a single message, it gets overwhelming, and makes things seem > much worse than they are. There are plenty of folks here who want to see you > succeed with KMyMoney - but give it some time. > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424775] I will NOT go out to a bank or ANY institution and retrieve any data!, I have USED Quicken for years. I printed the connection data, tested each by hand with a browser. and
https://bugs.kde.org/show_bug.cgi?id=424775 --- Comment #3 from Richard L. Stuart --- First, I am sorry if I offended you or anyone else. I read much about - GnuCash, KMyMoney etc. etc. before trying any of these softwares for Linux. I have thought about this in the past, but Quicken's new Licence arrangement push me on to trying.(You basically have to re-up every year, they claim new features but all I note is a difference in the GUI, for me just added frustration. So I am looking for something more solid and stable, and consistent. That has always been my experience with Linux based software. LybreOffice, GIMP, Thunderbird Mail etc. etc. We are human and so our past experience usually shapes our expectation in a similar area.. I didn't try KMyMoney first, and my first "setup" experience went very well - it imported my Quicken Backup file directly. But when I tried to get "accustom" to it's GUI, organization of accounts, Institutions etc.- Well - certainly not my cup of tea. I fooled around looking at others, must did NOT have any pictures of the Interface/Organization etc. Until I ran across KMyMoney- So I had great expectation. On trying to setup, KMyMoney would not import the QuickenBk file as others had.( I mention this to indicate that the backup file I am using is Likely OK) So, I got the data and I had entered it into KMyMoney, 10 accounts. and it displayed OK, had starting amount, beginning of the year - all looks good, but of course, no actual transactions yet. Save works, and reopen work and back to, of course the exact same, so far nice display etc. Now how do I get this to wifi contact the banks/institution and update - I could be wrong but I am thinking that was the idea, - the plan - developed in the software. The "disconnect" I am thinking is in one or two areas or both. Data input to KMyMoney, I went to all of the displays for data input in Quicken and copied all the data, ( I think) but something is missing. I found what I thought was the corresponding locations in KMyMoney - but some thing is not correct?. The Main page shows the Checking and Savings accounts - under Assets, and Credit Cards under Liabilities. Nothing stands out as strange, It all saves and reopens fine, but will NOT update the Transctions, etc. (That is NOT a criticism of YOU - It is just stating my experience, so you have something to go on to assist in finding a solution! ) How I installed this, I have Mint 19.3 on this computer, and several others, I also have Mint 20 (they skipped .5-.9 and went to 20.0 As you likely know Mint is based on Ubuntu. In Mint to install a software, you just go to the Software Manager, Search: KMyMoney and it finds it and installs it and the dependencies. It indicates it is installing the latest. and I do frequent Updates. BUT from you guys there is a later version of KMyMoney - 5.1.0 I assume I should be able to get a copy of same. so I will look for it. Thanks for any help. Richard Stuart PS: When you have a free moment, I know not very likely, checkout: www.itu-int.us PPS: Other software like Quicken etc which DID read the Quicken Backup file duplcated a number of the transaction, so while it looked nice it had a final total that was way off. On 7/29/20 10:37 AM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=424775 > > bren...@coupeware.com changed: > > What|Removed |Added > > CC||bren...@coupeware.com > > --- Comment #1 from bren...@coupeware.com --- > I'm not a developer so I'm less offended by the rude way you seem to be either > asking for help or criticizing the developers. Since you claim to write code, > I > assume your code is always perfect so you've never received a comment on your > code that is like your comment here. > > As far as the forums that you mentioned, it's possible you have been asking > for > help on forums/mailing lists that are no longer monitored. While the response > on this list is not always immediate it's usually fairly quick and very > helpful. Keep in mind the developers are volunteers and respond a lot better > to > polite questions than criticism. > > I have been using KMM for about 15 years and I have been using online banking > (direct connect) for most of that time. I don't recall if it was supported > back > in 2005 but it has been for a long time. So if it's not working for you it's > probably the bank or a setup issue. > > Version 5.0 is a very early version of the new 5 branch and was not > recommended > for daily use. There have been many updates since then and the current version > is 5.1.0. The previous version w
[kmymoney] [Bug 424775] New: I will NOT go out to a bank or ANY institution and retrieve any data!, I have USED Quicken for years. I printed the connection data, tested each by hand with a browser.
https://bugs.kde.org/show_bug.cgi?id=424775 Bug ID: 424775 Summary: I will NOT go out to a bank or ANY institution and retrieve any data!, I have USED Quicken for years. I printed the connection data, tested each by hand with a browser. and manually enter all. They all appear nice on the opening screen.watched YouTubea Product: kmymoney Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: rich...@rlstuart.com Target Milestone: --- SUMMARY I AM USING MINT 19.3 AND YOUR SW - 5.0.0 i HAS mINT 20.0 another laptop. STEPS TO REPRODUCE 1.Open,& in my case see six assents and 4 Credit Card with detailed data from Quicken 2. Click on so many items I have lost count. NOTHING makes it go update any accounts! NOTHING - Look, I write code, See www.itu-int.us for an example. seems to work - I can't imagine it's that bad. BUT I have tried a Forum and that is pathetic, Do you look at these forums. Lots of folks can't get to first base. and YOUR SW is useless without download, It has been suggested to me by several that I now try GnuCash. - YOU really need a YOUTUBE of step by step and have someone like your receptionist try it. HELP, I I move on I will NOT come back. 3. OBSERVED RESULT 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.
[plasmashell] [Bug 421749] Plasma desktop crashes when choosing to configure the thermal monitor widget
https://bugs.kde.org/show_bug.cgi?id=421749 Stuart changed: What|Removed |Added CC||viking...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419612] New: Set video speed to take a specific time rather than scale to a specific percentage
https://bugs.kde.org/show_bug.cgi?id=419612 Bug ID: 419612 Summary: Set video speed to take a specific time rather than scale to a specific percentage Product: kdenlive Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: sil-...@kryogenix.org Target Milestone: --- SUMMARY Kdenlive allows me to change the speed of a video to a percentage of its normal playback speed. However, I quite often would like to change a video clip, not to be 85% of its current speed, but so that it takes the same amount of time as another clip: that is, to make that change visually rather than by numbers. It would be very useful to allow changing a video's speed by dragging it out on the timeline so that I can visually set it to take a certain time to play back. Without this, I have to iteratively guess at percentages by doing a sort of mental version of binary search: let's try setting it to 60%, no, that's too short, hit Undo, try 70%, no, that's too long, Undo, try 65%, too long, Undo, 63%, too short, Undo, 64%, that seems about right. It would be much nicer to be able to drag the video clip to the right length and have the computer do the mathematics to calculate exactly the speed change. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 403524] URL navigator's drop down list of recent places doesn't contain recent places
https://bugs.kde.org/show_bug.cgi?id=403524 Stuart Prescott changed: What|Removed |Added CC||bugs.kde.org@nanonanonano.n ||et -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 415817] New: "Set Coordinates Manually..." always treats input as J2000 even if Jnow is selected.
https://bugs.kde.org/show_bug.cgi?id=415817 Bug ID: 415817 Summary: "Set Coordinates Manually..." always treats input as J2000 even if Jnow is selected. Product: kstars Version: 3.3.9 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: a...@randomuseless.info Target Milestone: --- SUMMARY The option to "Set Coordinates Manually..." has the option to input RA and Dec as either J2000 or Jnow. The buttons have no effect, though. The conversion from J2000 to Jnow is always applied, even if Jnow coordinates were entered and the Jnow button was clicked. This causes the wrong location to be used if Jnow coordinates are entered. STEPS TO REPRODUCE 1. Pointing -> Set Coordinates Manually... 2. In the dialog that pops up, the default is Jnow coordinates. Leave it set to Jnow and enter Jnow coordinates for Pollux: RA=07h 46m 31.63s, Dec=27:58:32.82 3. Leave the option set to Jnow and hit "OK". OBSERVED RESULT The sky view will change but Pollux will not be in the center. The error is equal to the difference between Jnow and J2000. EXPECTED RESULT The sky view will change and Pollux will be in the center of the view. The test can be redone by leaving the button set at Jnow but inputting the J2000 coordinates of Pollux: RA=07h 45m 19.38s, Dec=28:01:34.72. Leave it set for Jnow and hit "OK". The sky view will now center on Pollux even though the wrong datum was used. SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 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.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #35 from Stuart K. Smith --- Still not resolved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 --- Comment #3 from Stuart K. Smith --- One more possible issue: I have an older USB attached SD card reader. "Safely Remove" powers down the entire device rather than the subject SD card. In my case, the device is internally installed in a desktop machine and internally connected to a USB buss, so unplugging and plugging it back in is not an option. Either rebooting or some device power control magic if you're that familiar with the device is required. Granted, this case is a poorly designed hardware issue, but it is easily managed by a more friendly Dolphin context. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 --- Comment #2 from Stuart K. Smith --- Thank you for the quick reply. Yes: You want to reformat or install an ISO to a thumb drive. You plug it in, mount it, view it to be sure it's blank or doesn't contain any data you want to save, then unmount it and format it or whatever. Or you copy a file or two off of it, then hit the "Safely Remove", then realize you wanted one more file. Too bad, you have to pull it and start all over again. Clearly, one can do this from the command line, but using the GUI and a mouse has benefits. Also not all computers have easily reachable USB ports (some of us still have desktop machines). Conversely, why does a thumb drive need to be powered down at all? if it's unmounted, there's no benefit to making it inaccessible, is there? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414906] New: Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove"
https://bugs.kde.org/show_bug.cgi?id=414906 Bug ID: 414906 Summary: Dolphin does not allow UNMOUNT of USB thumb drives, only "Safely Remove" Product: dolphin Version: 19.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: stuartksm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin Removable Devices context menu needs Unmount just like the Devices context menu. Safely remove powers down and logically ejects a thumb drive requiring one to physically remove and re-insert it before use again. STEPS TO REPRODUCE 1. Right-Click on removable USB device 2. 3. OBSERVED RESULT Context menu contains: - Open in New Window - Open in New Tab - Properties - Safely Remove - - Hide - Hide Section 'Removable Devices' EXPECTED RESULT - Open in New Window - Open in New Tab - Properties - Unmount - Safely Remove - - Hide - Hide Section 'Removable Devices' SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon 5.17 (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Kernel 5.0.0-36-generic -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413941] Crash when opening Kmail
https://bugs.kde.org/show_bug.cgi?id=413941 --- Comment #2 from Stuart Morgan --- Given this was 3 weeks ago, I really cannot remember. I am using the proprietary driver. I doubt I would have filed a report if I knew that to be the case but it's still a possibility. Feel free to close, if the same crash occurs again I can re-open. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413941] New: Crash when opening Kmail
https://bugs.kde.org/show_bug.cgi?id=413941 Bug ID: 413941 Summary: Crash when opening Kmail Product: kmail2 Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: stu...@tase.co.uk Target Milestone: --- Application: kmail (5.11.3) Qt Version: 5.12.5 Frameworks Version: 5.61.0 Operating System: Linux 5.3.8-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Kmail's message window was only showing black, so I quit kmail and started it again, only now it crashes immediately on startup before any windows are displayed. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f1106c680 (LWP 559274))] Thread 20 (Thread 0x7f7ec8ff9700 (LWP 559318)): #0 0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f171d92e1 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f17199a12 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f1719c525 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f1719cae4 in base::internal::SchedulerWorker::RunPooledWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f7ec97fa700 (LWP 559304)): #0 0x7f7f1d718d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d875a in base::ConditionVariable::Wait() () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91f8 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f171d929f in base::WaitableEvent::Wait() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f17199a28 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f1719c838 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f1719cb64 in base::internal::SchedulerWorker::RunDedicatedWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f7ec9ffb700 (LWP 559303)): #0 0x7f7f1ff0aa1f in poll () from /lib64/libc.so.6 #1 0x7f7f1220e196 in poll_func () from /lib64/libpulse.so.0 #2 0x7f7f121ff801 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7f7f121ffe83 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f7f121fff30 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f7f1220e0dd in thread () from /lib64/libpulse.so.0 #6 0x7f7f1154eb9c in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f7eca7fc700 (LWP 559302)): #0 0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f17156188 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f1717820f in base::RunLoop::Run() () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f171aa86e in base::Thread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f7ecaffd700 (LWP 559301)): #0 0x7f7f1d718d45 in
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 --- Comment #3 from stuart --- Ok, I didn't suspect that since it is communicating with the database. Just that the query fails and Akonadi shuts down. On Thu, Oct 10, 2019 at 9:20 PM Sandro Knauß wrote: > https://bugs.kde.org/show_bug.cgi?id=412629 > > Sandro Knauß changed: > >What|Removed |Added > > > CC||skna...@kde.org > Status|REPORTED|CONFIRMED > Ever confirmed|0 |1 > > --- Comment #2 from Sandro Knauß --- > Keep in mind, that even Qt does not support Postgres 12 atm, so in first > glance > there needs to be a bug filed against Qt: > > > https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080 > > also in Debian this bug is reported: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941763 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412818] Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12
https://bugs.kde.org/show_bug.cgi?id=412818 stuart changed: What|Removed |Added CC||sfbar...@gmail.com Keywords||reproducible URL||https://www.postgresql.org/ ||docs/12/release-12.html#id- ||1.11.6.5.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412818] New: Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12
https://bugs.kde.org/show_bug.cgi?id=412818 Bug ID: 412818 Summary: Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12 Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: sfbar...@gmail.com Target Milestone: --- SUMMARY When backed by the postgres db, Akonadi executes the query; "SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_attrdef.adsrc FROM pg_class, pg_attribute LEFT JOIN pg_attrdef ON (pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attrelid = pg_class.oid AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum ;" In versions of PostGreSQL before 12, this query succeeds. Due to the changes to the informationschema, as identified in PostGreSQL PostgreSQL release notes: E.1. Release 12 https://www.postgresql.org/docs/12/release-12.html#id-1.11.6.5.5 PostgreSQL Version 12 removes: obsolete pg_constraint.consrc column obsolete pg_attrdef.adsrc column STEPS TO REPRODUCE 1. Upgrade PostGreSQL backend database to 12.x 2. Restart with Akonadictl start 3. OBSERVED RESULT This causes the query to fail and Akonadi quits with the error. org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: "\nSql error: ERROR: column \"version\" of relation \"schemaversiontable\" already exists\n(42701) QPSQL: Unable to create query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. org.kde.pim.akonadiserver: Shutting down AkonadiServer... EXPECTED RESULT When the query succeeds, Akonadi continues to process emails. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ANY (available in About System) KDE Plasma Version: ANY KDE Frameworks Version: ANY Qt Version: ANY ADDITIONAL INFORMATION The schema information for these dropped columns can be obtained using the functions, pg_constraint.consrc pg_get_constraintdef(pg_constraint.oid) pg_attrdef.adsrc pg_get_expr(pg_attrdef.adbin, pg_class.oid) So the Akonadi query: SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_attrdef.adsrc FROM pg_class, pg_attribute LEFT JOIN pg_attrdef ON (pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attrelid = pg_class.oid AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum ; should probably be changed to something like: SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_get_expr(pg_attrdef.adbin, pg_class.oid) AS adsrc FROM pg_class LEFT JOIN pg_attribute ON ( pg_attribute.attrelid = pg_class.oid ) LEFT JOIN pg_attrdef ON ( pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum ) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum; This will produce something like the following table: attname | atttypid | attnotnull | attlen | atttypmod | adsrc +--+++---+--- version| 23 | t | 4 |-1 | 0 generation | 23 | t | 4 |-1 | 0 (2 rows) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411450] New: Crash on startup in Raspbian Buster
https://bugs.kde.org/show_bug.cgi?id=411450 Bug ID: 411450 Summary: Crash on startup in Raspbian Buster Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: stujone...@gmail.com Target Milestone: --- Digikam installs, but crashes on startup in Raspbian Buster STEPS TO REPRODUCE 1. Install Digikam from Peferences/Add or Remove Software 2. Start Digikam from Graphics application menu 3. Digikam crashed When starting Digikam from console, multiple error messages result indicating missing components. 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.
[systemsettings] [Bug 410475] New: System Configuration App Crashing
https://bugs.kde.org/show_bug.cgi?id=410475 Bug ID: 410475 Summary: System Configuration App Crashing Product: systemsettings Version: 5.16.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: daniel.stuar...@gmail.com Target Milestone: --- Application: systemsettings5 (5.16.4) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 5.0.0-23-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Configuring my system. - Unusual behavior I noticed: Usually crashes when maximizing the window, also when changing the render type (xrandr, opengl, etc) The crash can be reproduced sometimes. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5d010f7680 (LWP 15298))] Thread 15 (Thread 0x7f5c7f5f1700 (LWP 18960)): #0 0x7f5cfc65bbf9 in __GI___poll (fds=0x7f5c6c001500, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5cdb946481 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f5cdb937e40 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5cdb9384d0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5cdb938560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5cdb9463c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5cdb4e3318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f5cf7a7a6db in start_thread (arg=0x7f5c7f5f1700) at pthread_create.c:463 #8 0x7f5cfc66888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f5c7fdf2700 (LWP 15367)): #0 0x7f5cfc6570b4 in __GI___libc_read (fd=46, buf=0x7f5c7fdf1b50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5cf57002d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cf56bb0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cf56bb570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cf56bb6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5cfcf9edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5cfcf4003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5cfcd674ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5cfcd68c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5cf7a7a6db in start_thread (arg=0x7f5c7fdf2700) at pthread_create.c:463 #10 0x7f5cfc66888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f5c8c983700 (LWP 15366)): #0 0x7f5cfc65bbf9 in __GI___poll (fds=0x7f5c780020d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5cf56bb5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cf56bb6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cfcf9edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5cfcf4003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5cfcd674ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5cfcd68c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5cf7a7a6db in start_thread (arg=0x7f5c8c983700) at pthread_create.c:463 #8 0x7f5cfc66888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f5c8eeb8700 (LWP 15365)): #0 0x7f5cfc6570b4 in __GI___libc_read (fd=44, buf=0x7f5c8eeb7b50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5cf57002d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cf56bb0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cf56bb570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cf56bb6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5cfcf9edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5cfcf4003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5cfcd674ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5cfcd68c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5cf7a7a6db in start_thread
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #11 from Stuart K. Smith --- BTW, agreed on the security issue. I had narrowed it to just the specific PC and it's in a rather controlled environment. I had widened it (ALL ALL etc.) when trying to trouble shoot this issue. My laptop does not have this setup. I haven't ventured into polkit much, but worth a look. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #10 from Stuart K. Smith --- Thank for the detailed info. Always good to be armed with the facts in my world. Funny you should make that recommendation about pkcon as I starting looking into it right after my last post here. My apt use was due to the burgeoning problems with early Discover in conjunction with Muon being without a dev. I just put apt into some aliases and made the suoders entry and went full CLI for updates and installations. That was about 5 years ago I think? pkcon looks good in the CLI and I'm looking at the GUIs also. Thanks again. Beverages on me if we ever meet in the real world :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #8 from Stuart K. Smith --- So neon-settings redirected bin/apt to sbin/apt ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #7 from Stuart K. Smith --- Seems like an odd way to implement a change like that; /usr/sbin/apt calls /usr/sbin/apt-overly which calls /usr/bin/apt. No wonder sudoers got confused! At least this explains why my sudo apt overrides worked in the 16.04 version. Thanks for running it down, I would have never found this. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #4 from Stuart K. Smith --- Results here are unchanged. Removing neon-settings allows sudoers.d/apt to work but it does not when neon-settings are installed. The issue appears to be specific to apt and apt-get. Echoing Harald commands do indeed work for 'ls' but '/usr/bin/apt' in sudoers.d does NOT work when neon-settings is installed, but does when neon-settings is not installed. Same goes for '/usr/bin/apt'. '/usr/bin/add-apt-repository' works with or without neon-settings installed so it is not related to the '/usr/bin/' folder but appears to be specific to apt and apt-get. All of the above 'apt' related commands and others are in a single file together on a single line and all but apt and apt-get work without a sudo password. I confirmed this on a VM as well as on my bare metal install. To recap: While neon-settings is installed: /bin/ls in /etc/sudoers.d/foo does allow 'sudo ls' to work without a password. Others, like 'sudo pwrstat' and 'sudo btrfs' that are on my system also work. Identically formatted '/etc/sudoers.d/apt' containing '/usr/bin/apt' and '/usr/bin/apt-get' among other commands all work EXCEPT apt and apt-get. Uninstalling neon-settings allows 'sudo apt' and 'sudo apt-get' to work without a password with no other modifications. Could someone specifically test this against /usr/bin/apt and/or /usr/bin/apt-get to confirm? Test procedure requested please: With neon-settings installed, use Harald's series of commands above and substitute '/usr/bin/apt' for '/bin/ls'. Then enter 'sudo -k' and 'sudo apt update'. Assuming the result is a password is requested, do CTRL+C to cancel and then uninstall neon-settings and re-test. Be sure to do 'sudo -k' between commands if package uninstall is done in the same terminal to force a reset of the environment. Please report results here. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #1 from Stuart K. Smith --- I installed all the dependencies for neon-settings and sudoers.d/ files worked normally. Installing the specific neon-settings package breaks the functionality. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] New: neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 Bug ID: 407729 Summary: neon-settings package causes files in /sudoers.d to not be honored Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: stuartksm...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Using a new install of KDEneon I noticed any entries in /etc/sudoers.d/ did not have the desired effect of allowing sudo actions without a password. Replacing the "neon-settings" package with "kubuntu-settings-desktop" results in the files in /etc/sudoers.d to begin working again. STEPS TO REPRODUCE 1. Fresh install of KDEneon. 2. Add file in /etc/sudoers.d/ using "sudo visudo -f ..." 3. Test action and see that sudo password is still required. OBSERVED RESULT Install "kubuntu-settings-desktop" which forces removal of "neon-settings". Test action and see that sudo password is no longer required. EXPECTED RESULT Files in sudoers.d should be parsed by KDEneon as they are when using Kubuntu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDEneon User Edition - latest (5.15.5) (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I'm not sure yet if it's actually neon-settings or one of is depends or a missing depends. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #32 from Stuart K. Smith --- Mihai Sorin Dobrescu: I totally got what you meant and my comment wasn't pointed at you. Rather, I was try to illustrate a broader point that different devices needs different actions and the terms are important because of that. Using "Safely Eject" obfuscates the actual needed action and is part of the problem in my view. Christoph Feck: Precisely and exactly to the issue. There are many uses for the Notifier when controlling USB storage devices and there is no "one size fits all" solution. Fully ejecting a non-spinning device in unwarranted and in many cases very inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #29 from Stuart K. Smith --- That doesn't seem to work here, at least not with a USB stick: sudo hdparm -y /dev/sdi [sudo] password for stuart: /dev/sdi: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The drive is still mounted after this and unmounting first has the same results. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #27 from Stuart K. Smith --- Thinking it over, what I would like to see is; If the USB storage device is a CD/DVD/BR, "Eject" is the default action. If the device is a USB attached file system but not a CD/DVD/BR, then set "Unmount all file systems on this device" as default action, and offer "Unmount only this file system" as an action in the list for the device. Then if you want to unmount and grab your thumb drive or USB hard drive, the default is perfect. If you are continuing to work with a multi-file system USB device, then you can select and specify which file system to unmount (or mount). In both cases, the device remains accessible because it has not been powered off by Eject. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #26 from Stuart K. Smith --- Agreed, however in the case of USB thumb drive, unmounting forces commit or it won't unmount until cache is clear. It least that's my belief. IME I can't unmount any file system until it's not being used. Part of the issue might be the understanding of eject vs. unmount. A file system is unmounted, but not ever "ejected". A device may be ejected, but only cleanly if it has been unmounted prior. A device, like a USB thumb drive or USB hard drive is never really in need of "Eject" because once the file system(s) on it are unmounted you can just pull it out. This is where this whole mess started. Someone had multiple file systems on a USB device and failed to unmount one or more of them before pulling the plug. This could cause a file corruption if a write were not complete. This potential outweighed (at least in some persons minds) the inconvenience to the thousands of users just a thumb drive. In my mind, the best possible solution for USB r/w storage devices is an "unmount all" condition where all file systems on the device are unmounted. "Eject" does this conveniently enough but then you end up where we are - pulling a re-inserting the device. Seems like an expansion of the Notifier actions in this regard is in order. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402660] Device notifier clears a device after unmount, but before unplug
https://bugs.kde.org/show_bug.cgi?id=402660 --- Comment #24 from Stuart K. Smith --- There seems to be a lot of rambling on this bug report about loosely related topics. My issue is that a USB device should not have to be unplugged and re-inserted by design. That is a very poor working practice. You should be able to choose or default to Unmount rather than Eject (aka "Safely Remove") devices that do not require ejection. Is there no way for the programming of the Device Notifier to detect if a plugged in device is a spinning hard drive vs. a USB thumb drive? BTW, my WD USB spinning hard drive does not need to be "parked" to be removed. This effectively make Notifier mostly useless for USB thumb drives. If I have to go to the command line so I don't have to reach behind my monitor or PC case to unplug and reinsert my USB drive, then why have the GUI Notifier? At a minimum, "Unmount" should be in the options available and at best be the default choice when clicking the up arrow in Notifier. I'd bet that there are oodles more thumb drives being used than portable hard drives. Let the lesser sized user group have the extra "Fully Eject" option available in the action list but make Unmount the option. Seems way more logical to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406362] New: Device Notifier treats USB thumb drives like CDs - "Safely remove" ejects instead of unmounting
https://bugs.kde.org/show_bug.cgi?id=406362 Bug ID: 406362 Summary: Device Notifier treats USB thumb drives like CDs - "Safely remove" ejects instead of unmounting Product: plasmashell Version: 5.12.8 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: stuartksm...@gmail.com Target Milestone: 1.0 SUMMARY The Device Notifier "Ejects" USB thumb drives rendering them unusable until they are pulled from the port and re-inserted. This is both unnecessary and poor work-flow. There is no justification for ejecting a USB thumb drive. A much better action would be for "Unmount" to be the default action instead of "Eject". This would allow multiple actions to be taken on a thumb drive without continuously removing and re-inserting it, such as reformatting or burning and ISO to it. This is especially important if the USB port is difficult to physically access, such as the back-side of a monitor or PC. STEPS TO REPRODUCE 1. Insert thumb drive and observe Device Notifier pop-up indication that a drive has been inserted. 2. Select "Open with File Manager" from access options in Device Notifier. 3. Select the up-arrow button "Click to Safely Remove this device." using Device Notifier. OBSERVED RESULT The USB device is no longer listed in attached devices via "lsusb" although it is still physically present and cannot be accessed until it is removed and re-inserted. EXPECTED RESULT File system should be unmounted but the physical device should still addressable. "Safely Remove" when referring to a USB drive should only unmount the device, not eject it from the bus. Ejecting is only preferred if the physical device requires that for access such as with a CDROM/DVD. Unmounting a USB drive prior to its physical removal is sufficient for file system safety. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDEneon LTS 5.12 (available in About System) KDE Plasma Version: 5.12.8 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.
[krita] [Bug 403194] New: Desktop files could be amalgamated to avoid multiple entries in Gtk App Chooser for Krita
https://bugs.kde.org/show_bug.cgi?id=403194 Bug ID: 403194 Summary: Desktop files could be amalgamated to avoid multiple entries in Gtk App Chooser for Krita Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: stu.a...@gmail.com Target Milestone: --- Created attachment 117450 --> https://bugs.kde.org/attachment.cgi?id=117450=edit Many krita entries in Gtk App Chooser In nautilus right click a file, Open With Other Application->View All Applications, there are many Krita entries. (Same bug will show in other places using the GtkAppChooser, e.g. Firefox). This occurs because Krita creates one desktop file for each file association. Desktop files can have a list of mimetypes, so amalgamating these into one desktop file should fix the bug. Tested on 4.1.7 - since I'm not sure how to setup file associations with the appimage. See conversation here https://gitlab.gnome.org/GNOME/gtk/issues/1581#note_407441 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395033] New: No artist shown if track has multiple artists
https://bugs.kde.org/show_bug.cgi?id=395033 Bug ID: 395033 Summary: No artist shown if track has multiple artists Product: dolphin Version: 17.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: s.g.trot...@stuiet.com Target Milestone: --- Created attachment 113076 --> https://bugs.kde.org/attachment.cgi?id=113076=edit Screenshot displaying issue If a track has multiple artists e.g. Room 5 feat. Oliver Cheatham, this seems to be recorded as two separate artists in the information pane and nothing shown in the artist column in details view (see screenshot) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388593] Krunner spellcheck plugin does not work (Could not find a dictionary)
https://bugs.kde.org/show_bug.cgi?id=388593 Stuart K. Smith <stuartksm...@gmail.com> changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #2 from Stuart K. Smith <stuartksm...@gmail.com> --- Same here: kf5.karchive: bzDecompress returned -5 The dictionary data engine timed out (word: "app" ) The dictionary data engine timed out (word: "appl" ) The dictionary data engine timed out (word: "apple" ) The dictionary data engine timed out (word: "apple" ) Neon user addition, Plasma 5.12 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384162] New: Crash just after switching session
https://bugs.kde.org/show_bug.cgi?id=384162 Bug ID: 384162 Summary: Crash just after switching session Product: kdevelop Version: 5.1.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: stu...@tase.co.uk Target Milestone: --- Application: kdevelop (5.1.1) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.43-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I changed from one session to another, a few seconds later the instance crashed. Upon restarting it opened the old session again, and every time I attempt to switch to the desired session it will again crash. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3dc56c7800 (LWP 10341))] Thread 24 (Thread 0x7f3d567fc700 (LWP 10549)): #0 0x7f3dd8550ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bd46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3ddec87764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f3ddec8aff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f3dd854b66d in start_thread () at /lib64/libpthread.so.0 #5 0x7f3dde5a3e4d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f3d56ffd700 (LWP 10548)): #0 0x7f3dd8550ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bd46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3ddec87764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f3ddec8aff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f3dd854b66d in start_thread () at /lib64/libpthread.so.0 #5 0x7f3dde5a3e4d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f3d577fe700 (LWP 10547)): #0 0x7f3dd8550ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bd46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3ddec87764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f3ddec8aff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f3dd854b66d in start_thread () at /lib64/libpthread.so.0 #5 0x7f3dde5a3e4d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f3d57fff700 (LWP 10546)): #0 0x7f3dd8550ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bd46 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3ddec87764 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f3ddec8aff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f3dd854b66d in start_thread () at /lib64/libpthread.so.0 #5 0x7f3dde5a3e4d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f3d74ff9700 (LWP 10545)): #0 0x7f3dd8550c4f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3dd3dfa2f7 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f3dd3dfdfe8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f3dd3df9579 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f3dd3dfbddf in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f3ddec8aff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f3dd854b66d in start_thread () at /lib64/libpthread.so.0 #8 0x7f3dde5a3e4d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f3d757fa700 (LWP 10544)): #0 0x7f3dd8550c4f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3ddec8bdfb in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3dd3dfa2f7 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f3dd3dfdfe8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f3dd3df9579 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f3dd3dfbddf in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6
[neon] [Bug 379721] neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer.
https://bugs.kde.org/show_bug.cgi?id=379721 --- Comment #4 from Stuart K. Smith <stuartksm...@gmail.com> --- (In reply to Jonathan Riddell from comment #3) > Much KDE software depends on Phonon which needs one of its backends > installed to function. If you remove that it's entirely reasonable that apt > wants to remove the software that needs it. I completely understand and agree, but I don't see this as the central issue. The problem as I see it is the lack of a fail-back to the gstreamer backend in the event the user wants to remove VLC. As it stands, removing VLC is impossible unless the user knows to install the gstreamer backend prior to attempting the removal. This requirement is not obvious to the uninitiated and is not apparent by the error messages created by the attempt. IMO, this situation could be easily resolved in one of these ways: 1) The removal of phonon4qt5-backend-vlc triggers the installation of phonon4qt5-backend-gstreamer - and vice-versa, thus preventing the unintentional breakage of the entire system. 2) Both backends installed by default, thus allowing VLC to be removed without incident. 3) VLC not be installed by default at all, instead having gtreamer be the default backend. Again, IMO #1 would be the most beneficial as it provides protection from "silly user tricks." Interesting points to note: **Removing the gstreamer backend (whilst the VLC backend is not present) automatically installs the VLC backend. It's only when you attempt the reverse as stated above that the removal of KDE is at risk. **Even VLC does not have the VLC backend as a dependency. Removing the VLC backend on it's own does not force the removal of VLC. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379721] New: neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer.
https://bugs.kde.org/show_bug.cgi?id=379721 Bug ID: 379721 Summary: neon only dependency bug: phonon4qt5-backend-vlc and -gstreamer. Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: stuartksm...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Attempting to remove vlc from KDEneon results in removal of entire plasma desktop. I found the problematic package is "phonon4qt5-backend-vlc" which takes everything else with it. If, prior to removing vlc, you first install "phonon4qt5-backend-gtreamer" then you can remove vlc and it's depends successfully. This requirement to have either phonon4qt5-backend-vlc or -gstreamer is not present in Kubuntu 16.04. Either the dependencies are incorrect or at a minimum, the gstreamer package should be installed as fall-back if one wants to remove vlc. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when Plasma is running
https://bugs.kde.org/show_bug.cgi?id=358957 --- Comment #17 from Stuart Morgan <stu...@tase.co.uk> --- I completely understand the volunteer nature of the project, I've been an open source contributor for well over 10 years now. However no-one wants to waste their time working on a solution when there is one already in progress by someone in the core team. I'm going to take it from your response that it isn't currently the case, so yes, time permitting (and it generally doesn't these days), I will work on it myself. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when Plasma is running
https://bugs.kde.org/show_bug.cgi?id=358957 Stuart Morgan <stu...@tase.co.uk> changed: What|Removed |Added CC||stu...@tase.co.uk --- Comment #15 from Stuart Morgan <stu...@tase.co.uk> --- The lack of hybrid suspend support in KDE/Plasma has been discussed for several years now. Instead of getting bogged down in implementation details, just add the option in any form, it can always be improved later. Laptop users need the option now, not in another 5 years when someone finally makes an executive decision. If no-one currently active on the project is able (too busy) or interested in implementing this, then please tell us now so that one of us from the community can step up and do it instead. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 376539] New: Crash while using 'find' to search current directory
https://bugs.kde.org/show_bug.cgi?id=376539 Bug ID: 376539 Summary: Crash while using 'find' to search current directory Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stu...@tase.co.uk Target Milestone: --- Application: kdeinit5 (16.12.0) Qt Version: 5.6.2 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I was searching for a file in the current directory using the first three letters of the file name. -- Backtrace: Application: Dolphin (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f679aef1800 (LWP 18842))] Thread 4 (Thread 0x7f677b1dd700 (LWP 18845)): #0 0x7f67994a48bd in read () at /lib64/libc.so.6 #1 0x7f6795333073 in () #2 0x2e27f653 in () #3 0x7f677b1dcbd0 in () #4 0x7f67740025a0 in () #5 0x7f67700013c0 in () #6 0x0001 in () #7 0x7f67960bab50 in g_poll () at /lib64/libglib-2.0.so.0 #8 0x0001 in () #9 0x7f67960ee320 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #10 0x7f67960aa55e in g_main_context_check () at /lib64/libglib-2.0.so.0 #11 0x7f67960aa9f8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #12 0x7f67960aab5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #13 0x7f6799a3495b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #14 0x7f67999dff9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7f67998193bc in QThread::exec() () at /lib64/libQt5Core.so.5 #16 0x7f679981dff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #17 0x7f6796df266d in start_thread () at /lib64/libpthread.so.0 #18 0x7f67994b4ded in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6780d76700 (LWP 18844)): #0 0x7f67994a48bd in read () at /lib64/libc.so.6 #1 0x7f6795333073 in () #2 0x2e27de69 in () #3 0x7f6780d75ba0 in () #4 0x7f677c0015b0 in () #5 0x7f67740188d0 in () #6 0x0001 in () #7 0x7f67960bab50 in g_poll () at /lib64/libglib-2.0.so.0 #8 0x0004 in () #9 0x7f67960ee320 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #10 0x7f67960aa55e in g_main_context_check () at /lib64/libglib-2.0.so.0 #11 0x7f67960aa9f8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #12 0x7f67960aab5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #13 0x7f6799a3495b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #14 0x7f67999dff9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7f67998193bc in QThread::exec() () at /lib64/libQt5Core.so.5 #16 0x7f679ae15615 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #17 0x7f679981dff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #18 0x7f6796df266d in start_thread () at /lib64/libpthread.so.0 #19 0x7f67994b4ded in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f678295b700 (LWP 18843)): #0 0x7f67994a8f9d in poll () at /lib64/libc.so.6 #1 0x7f679a3f3902 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f679a3f5657 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f678562dba9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f679981dff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f6796df266d in start_thread () at /lib64/libpthread.so.0 #6 0x7f67994b4ded in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f679aef1800 (LWP 18842)): [KCrash Handler] #6 0x7f67993f2828 in raise () at /lib64/libc.so.6 #7 0x7f67993f3f3a in abort () at /lib64/libc.so.6 #8 0x7f6799805f7e in () at /lib64/libQt5Core.so.5 #9 0x7f679ae207a1 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5 #10 0x7f6799a0deca in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7f6798298c4c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7f679829ddb6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f67999e2118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f67999e3f3b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #15 0x7f6799a34523 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #16 0x7f67960aa887 in g_main_context_dispatch
[kde] [Bug 376030] New: Dolphin crash when cutting/pasting file
https://bugs.kde.org/show_bug.cgi?id=376030 Bug ID: 376030 Summary: Dolphin crash when cutting/pasting file Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: stu...@tase.co.uk Target Milestone: --- Application: kdeinit5 (16.12.0) Qt Version: 5.6.2 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: Had cut a file from one location and was navigating to a subfolder to paste the file. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b2fed9800 (LWP 5571))] Thread 4 (Thread 0x7f8b0700 (LWP 5574)): #0 0x7f8b2b0d7604 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f8b2b09262a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #2 0x7f8b2b092ab8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f8b2b092b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f8b2ea1c95b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f8b2e9c7f9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f8b2e8013bc in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f8b2e805ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f8b2bdda66d in start_thread () at /lib64/libpthread.so.0 #9 0x7f8b2e49cded in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8b15d5e700 (LWP 5573)): #0 0x7f8b2bde2a7a in __lll_unlock_wake () at /lib64/libpthread.so.0 #1 0x7f8b2bdddf2f in pthread_mutex_unlock () at /lib64/libpthread.so.0 #2 0x7f8b2c817b45 in () at /usr/lib64/nvidia-current/libGL.so.1 #3 0x7f8b2c81d278 in () at /usr/lib64/nvidia-current/libGL.so.1 #4 0x7f8b2a31b102 in () at /usr/lib64/nvidia-current/tls/libnvidia-tls.so.375.26 #5 0x7f8b2b0d6320 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #6 0x7f8b2b09255e in g_main_context_check () at /lib64/libglib-2.0.so.0 #7 0x7f8b2b0929f8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x7f8b2b092b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x7f8b2ea1c95b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #10 0x7f8b2e9c7f9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7f8b2e8013bc in QThread::exec() () at /lib64/libQt5Core.so.5 #12 0x7f8b2fdfd615 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #13 0x7f8b2e805ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x7f8b2bdda66d in start_thread () at /lib64/libpthread.so.0 #15 0x7f8b2e49cded in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8b17943700 (LWP 5572)): #0 0x7f8b2e490f9d in poll () at /lib64/libc.so.6 #1 0x7f8b2f3db902 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f8b2f3dd657 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f8b1a615ba9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f8b2e805ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f8b2bdda66d in start_thread () at /lib64/libpthread.so.0 #6 0x7f8b2e49cded in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8b2fed9800 (LWP 5571)): [KCrash Handler] #6 0x7f8b2e3da828 in raise () at /lib64/libc.so.6 #7 0x7f8b2e3dbf3a in abort () at /lib64/libc.so.6 #8 0x7f8b2e7edf7e in () at /lib64/libQt5Core.so.5 #9 0x7f8b2fe087a1 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5 #10 0x7f8b2e9f5eca in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7f8b2d280c4c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7f8b2d285db6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f8b2e9ca118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f8b2e9cbf3b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #15 0x7f8b2ea1c523 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #16 0x7f8b2b092887 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #17 0x7f8b2b092ab8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #18 0x7f8b2b092b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7f8b2ea1c936 in QEventDispatcherGlib::processEvents(QFlags) () at
