[konqueror] [Bug 371847] New: nspluginviewer crashed when browser started
https://bugs.kde.org/show_bug.cgi?id=371847 Bug ID: 371847 Summary: nspluginviewer crashed when browser started Product: konqueror Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: nspluginviewer Assignee: konq-b...@kde.org Reporter: fhj52.i...@gmail.com Target Milestone: --- Application: nspluginviewer () KDE Platform Version: 4.14.25 Qt Version: 4.8.7 Operating System: Linux 4.8.5-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I started the Light browser(lightfirefox 49.0-1) on/in KDE Plasma 5(plasma-workspace 5.8.2-1). - Custom settings of the application: Not settings so much as I had updated flashplayer and this was first start with the new version(flashplugin-beta 24.0.0.138-1). do not know if related but that is only change for that browser since its previous start & close. Unable to duplicate the event. I tried several times by starting Light but to no avail. /usr/bin/nspluginviewer is owned by kdebase-konqueror 16.08.2-1 -- Backtrace: Application: nspluginviewer (nspluginviewer), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f540d68be80 (LWP 7071))] Thread 2 (Thread 0x7f53c3fff700 (LWP 7097)): #0 0x7f5409cea4ed in read () at /usr/lib/libc.so.6 #1 0x7f53e4389f81 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #2 0x7f53e460b50e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f53e460bf80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f53e460c040 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f53e461a069 in () at /usr/lib/libpulse.so.0 #6 0x7f53e43b8ed8 in () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #7 0x7f5409164454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5409cf77df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f540d68be80 (LWP 7071)): [KCrash Handler] #6 0x7f53faa992e2 in () at /usr/lib/mozilla/plugins/libflashplayer.so #7 0x7f53f8f356a1 in () at /usr/lib/libgdk-x11-2.0.so.0 #8 0x7f53f8f36a66 in () at /usr/lib/libgdk-x11-2.0.so.0 #9 0x7f53f8f38396 in () at /usr/lib/libgdk-x11-2.0.so.0 #10 0x7f53f8f3843e in () at /usr/lib/libgdk-x11-2.0.so.0 #11 0x7f540c61e587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #12 0x7f540c61e7f0 in () at /usr/lib/libglib-2.0.so.0 #13 0x7f540c61eb12 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #14 0x7f53faae0bbe in () at /usr/lib/mozilla/plugins/libflashplayer.so #15 0x7f53faa05296 in () at /usr/lib/mozilla/plugins/libflashplayer.so #16 0x7f53faa9e06c in () at /usr/lib/mozilla/plugins/libflashplayer.so #17 0x7f53faa9e17c in () at /usr/lib/mozilla/plugins/libflashplayer.so #18 0x7f53f92c27ac in () at /usr/lib/libgtk-x11-2.0.so.0 #19 0x7f5405e02f75 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0 #20 0x7f5405e14f82 in () at /usr/lib/libgobject-2.0.so.0 #21 0x7f5405e1d66f in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0 #22 0x7f5405e1dfaf in g_signal_emit () at /usr/lib/libgobject-2.0.so.0 #23 0x7f53f93da7ef in () at /usr/lib/libgtk-x11-2.0.so.0 #24 0x7f53f92c0f74 in gtk_propagate_event () at /usr/lib/libgtk-x11-2.0.so.0 #25 0x7f53f92c132b in gtk_main_do_event () at /usr/lib/libgtk-x11-2.0.so.0 #26 0x7f53f8f3846c in () at /usr/lib/libgdk-x11-2.0.so.0 #27 0x7f540c61e587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #28 0x7f540c61e7f0 in () at /usr/lib/libglib-2.0.so.0 #29 0x7f540c61e89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #30 0x7f540b237ece in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQtCore.so.4 #31 0x7f540a5dfe86 in () at /usr/lib/libQtGui.so.4 #32 0x7f540b2063ff in QEventLoop::processEvents(QFlags) () at /usr/lib/libQtCore.so.4 #33 0x7f540b206765 in QEventLoop::exec(QFlags) () at /usr/lib/libQtCore.so.4 #34 0x7f540b20c1c9 in QCoreApplication::exec() () at /usr/lib/libQtCore.so.4 #35 0x00408b7d in () #36 0x7f5409c2f291 in __libc_start_main () at /usr/lib/libc.so.6 #37 0x00408ffa in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484341] New: Translate auto tags in non-english languages
https://bugs.kde.org/show_bug.cgi?id=484341 Bug ID: 484341 Summary: Translate auto tags in non-english languages Classification: Applications Product: digikam Version: 8.3.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Maintenance-AutoTags Assignee: digikam-bugs-n...@kde.org Reporter: zenigata...@gmail.com Target Milestone: --- Automatic tagging feature introduced in Digikam 8.3 is a great feature but it generates word only in english. As suggested in the official news announcement (https://discuss.pixls.us/t/digikam-8-3-0-is-released/42671/3?u=carobinario) future Digikam versions can automatically use online translator to generate keywords in native language. I'm on Linux but this feature request is valid for all platforms. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484341] Translate auto tags in non-english languages
https://bugs.kde.org/show_bug.cgi?id=484341 Ric changed: What|Removed |Added CC||zenigata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 431642] New: Please build a Flatpak for kup
https://bugs.kde.org/show_bug.cgi?id=431642 Bug ID: 431642 Summary: Please build a Flatpak for kup Product: kup Version: 0.8.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: zenigata...@gmail.com Target Milestone: --- Please consider to build a kup-backup Flatpak. It's a great backup tool but it's missing (or it was removed) from many official repositories, for example Fedora and Kubuntu. In Fedora 33 (my main distribution) bup is also not included because months ago was still using Python 2 (I know it supports python 3 since 0.31 version). Also in Fedora there is another package called kup: it's a Kernel.org Uploader. So, please build a Flatpak to help kup to be installed in many systems. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 431642] Please build a Flatpak for kup
https://bugs.kde.org/show_bug.cgi?id=431642 --- Comment #2 from Ric --- You are(In reply to Nate Graham from comment #1) > Kup does not require bup, FWIW. So this hopefully shouldn't be a barrier to > distros packaging it. You are right, but I'm not a package mantainer, a Fedora or Ubuntu developer, so I can't add it. Please read some blog posts (for example https://averagelinuxuser.com/kup-backup/). Users are complaining that the are unable to install it on Kubuntu. So, please build a Flatpak (or a Snap) as other popular kde apps. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 428181] Audacious music player "Open Folder" option no longer working after Plasma 5.20 update
https://bugs.kde.org/show_bug.cgi?id=428181 Ric changed: What|Removed |Added CC||zenigata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407547] New: Open new files in tabs does not work in windows
https://bugs.kde.org/show_bug.cgi?id=407547 Bug ID: 407547 Summary: Open new files in tabs does not work in windows Product: okular Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ric.richte...@gmail.com Target Milestone: --- SUMMARY On my system I have a Win7 and I recently downloaded Okular from https://binary-factory.kde.org/view/Windows%2064-bit (presumably build 12). Okular version 1.7.70 STEPS TO REPRODUCE 1. Go in okular menu to "Tools->Configure Okular..." 2. Under "General" activate "Open new files in tabs" 3. Close okular or keep it open, it does not matter. Ich checked the ~/AppData/Local/okular/okularpartrc and I find a line with "ShellOpenFileInTabs=true" 4. Open any two PDFs in Windows Explorer OBSERVED RESULT There will be two instances of Okular showing the PDFs in their own window. EXPECTED RESULT One instance of Okular is showing the two PDFs in two tabs. SOFTWARE/OS VERSIONS Windows: Win7 macOS: - Linux/KDE Plasma: - (available in About System) KDE Plasma Version: - KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION https://binary-factory.kde.org/view/Windows%2064-bit/job/Okular_Nightly_win64/12/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407548] New: [Wish] Support save/restore session
https://bugs.kde.org/show_bug.cgi?id=407548 Bug ID: 407548 Summary: [Wish] Support save/restore session Product: okular Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ric.richte...@gmail.com Target Milestone: --- Save and restore current okular session. Rough proposal for implementation (without knowing details): * Add a menu checkbox under "General" to support "Restore from last session" * Closing okular with open tabs the open filenames will be stored somewhere (e.g. okularpartrc) along with the sequence * On opening okular, the program will check for the session option. If activated, okular will open the filenames that have been stored. * Please take also care of the correct sequence of the opened tabs and also of files that have been deleted or are not accessible anymore. In my opinion, okular should not force the user to click error messages. Please take those notes above as a proposal for this wish but feel free to implement it in any other way it suits KDE/Okular-Team best. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407640] New: Win7: Okular crashes on resuming from any sort of standby
https://bugs.kde.org/show_bug.cgi?id=407640 Bug ID: 407640 Summary: Win7: Okular crashes on resuming from any sort of standby Product: okular Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ric.richte...@gmail.com Target Milestone: --- SUMMARY In MS Windows, Okular crashes when the Computer wakes up from stand-by or suspend to disk. STEPS TO REPRODUCE 1. Leave okular open 2. Send Computer to stand-by 3. Wake up Computer and click error message that Okular has crashed. OBSERVED RESULT Okular has been crashed. I could only find a windows log message containing the following: Faulting application name: okular.exe, version: 0.0.0.0, time stamp: 0x5cd89195 Faulting module name: ntdll.dll, version: 6.1.7601.24408, time stamp: 0x5c92f30c Exception code: 0xc0fd Fault offset: 0x0002186a Faulting process id: 0x30d4 Faulting application start time: 0x01d50bdba18a3c19 Faulting application path: D:\Program Files\Okular\bin\okular.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 4efa2279-7865-11e9-bbac-3c77e6cd57be EXPECTED RESULT Not to crash. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 406576] Windows binaries for new versions of kdiff3
https://bugs.kde.org/show_bug.cgi?id=406576 ric changed: What|Removed |Added CC||ric.richte...@gmail.com --- Comment #3 from ric --- Good news! I am also very interested in getting binaries for MS Windows of the latest KDiff3. It seems that Version 1.81 has already been released. Could you provide a link where the builds have been published or could you also upload a pre-built version for Windows? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375470] New: systemsettings5 crashes and loses config when exiting to initial display(All Settings button)
https://bugs.kde.org/show_bug.cgi?id=375470
Bug ID: 375470
Summary: systemsettings5 crashes and loses config when exiting
to initial display(All Settings button)
Product: systemsettings
Version: 5.8.5
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: fhj52.i...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.8.5)
Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.4.41-1-MANJARO x86_64
Distribution: "Manjaro Linux"
-- Information about the crash:
- What I was doing when the application crashed:
Trying to configure the KDE.
The crashes occur for multiple configure items and occur with both $USER and
root users.
The last crash was via
* click on "Desktop Behavior" item
* select multiple choices(Desktop effects, then Screen locking, Screen edges
then Workspace.)
(No change to configurables has to be done.)
* select/click the "All Settings" 'button' to return to the initial screen
CRASH
After this crash I forced a crash (by above) so could get the output from
terminal.
OUTPUT from terminal
$> systemsettings5
Constructing a KPluginInfo object from old style JSON. Please use
kcoreaddons_desktop_to_json() for
"/usr/lib/qt/plugins/kwin/effects/configs/kcm_kwin4_genericscripted.so" instead
of kservice_desktop_to_json() in your CMake code.
WP : --- ("/usr/share/wallpapers/")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/sadmin/.local/share/mime", "/usr/share/mime")
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/home/sadmin/.local/share/mime", "/usr/share/mime")
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Andromeda" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Autumn" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Breath" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/BytheWater" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/ColdRipple" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/ColorfulCups" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/DarkestHour" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/EveningGlow" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/FallenLeaf" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/FlyingKonqui" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Grey" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Kite" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Maia" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Next" is a directory.
Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/OneStandsOut" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/PastelHills" is a
directory. Use addDir!
org.kde.kcoreaddons: KDirWatch: "/usr/share/wallpapers/Path" is a directory.
Use addDir!
KCrash: Application 'systemsettings5' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
[1]+ Stopped systemsettings5
---
It crashes a lot. Does not seem to matter what item is selected to configure
but sometimes it will go back to "All Settings" and not crash. The biggest
offenders are, IIRC, "Font", "Desktop Behaviour", "Application Style" and
"Startup and Shutdown" items.
Generally, the changed settings are saved but not applied(after "Apply" is
selected). Sometimes the new settings are applied (changes can be seen) but
when systemsettings5 crashes the settings are lost and it reverts to the
default. I know, ...weird.
I can make it crash everytime as above but sometimes when I am configuring an
item it will not crash until the main window is closed. Then
[1]+ Segmentation fault (core dumped) systemsettings5
This is the last core dump
$> /usr/bin/coredumpctl dump 4046
PID: 4046 (systemsettings5)
UID: 1000 (***)
GID: 1000 (***)
Signal: 11 (SEGV)
Timestamp: Mon 2017-01-23 14:11:01 CST (15min ago)
Command Line: systemsettings5
Executable: /usr/bin/systemsettings5
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owne
[digikam] [Bug 376918] New: Ambiguous Shortcuts
https://bugs.kde.org/show_bug.cgi?id=376918 Bug ID: 376918 Summary: Ambiguous Shortcuts Product: digikam Version: 5.4.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: fhj52.i...@gmail.com Target Milestone: --- Started charge for phone, got a popup in KDE plasma 5.9.2 for 'what to do' and decided to see if Digikam works. It does! (I'm so glad - luv digikam!) However it popped-up a message: " Ambiguous Shortcuts There are two actions (Select Locked Items, Toggle Lock) that want to use the same shortcut (Ctrl+L). This is most probably a bug. Please report it in bugs.kde.org " The configurable Settings/Shortcuts has neither of those items. It does have General/"Place onto Light Table" as Ctrl+L. So not sure what the real problem is here. Nevertheless, I looked for this error in bugs list and did not find it so it is reported as requested. [system info] System:Kernel: 4.9.12-1-MANJARO x86_64 (64 bit gcc: 6.3.1) Desktop: KDE Plasma 5.9.2 (Qt 5.8.0) Distro: Manjaro Linux Machine: Mobo: Supermicro model: X8DTH BIOS: AMI v: 2.1b date: 05/04/12 CPU(s):2 Quad core Intel Xeon X5687s (-HT-MCP-SMP-) cache: 24576 KB Graphics: Card: NVIDIA GP106 [GeForce GTX 1060 6GB] bus-ID: 84:00.0 [digikam info] Name: digikam Version : 5.4.0-2 Depends On : liblqr libkipi lensfun opencv akonadi-contacts knotifyconfig libksane kfilemetadata qtav marble threadweaver kcalcore Optional Deps : kipi-plugins: export to various online services [installed] qt5-imageformats: support for additional image formats (WEBP, TIFF) [installed] Packager: Antonio Rojas Build Date : Sun 29 Jan 2017 03:50:14 PM CST -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 377288] New: kget crashes
https://bugs.kde.org/show_bug.cgi?id=377288
Bug ID: 377288
Summary: kget crashes
Product: kget
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@kde.org
Reporter: fhj52.i...@gmail.com
Target Milestone: ---
Application: kget (2.14.28)
Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-1-MANJARO x86_64
Distribution: "Manjaro Linux"
-- Information about the crash:
- What I was doing when the application crashed:
It took five(5) attempts this time to start the app. Sometimes it takes 3 or
less.
1. Clicked on KGet icon to start the app. => crash.
2. Clicked on KGet icon to start the app. => crash.
3. Started from terminal/shell with `kget` => crash:
$> kget
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kget is already running!
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
unnamed app(20153): Communication problem with "kget" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient
disconnected from message bus without replying" "
It's 6:45 AM CST on Mon Mar 06.
(NB: THE KGET PROCESS FOR THIS REPORT WAS STOPPED BUT STILL "running".)
4. Started from terminal/shell with kget => silent crash:
$> kget
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
KGlobal::locale(): Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related functions before your main component was created. You should
not do that since it most likely will not work
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kget(20182) KGet::setHasNetworkConnection: Existing internet connection: true
old: true
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 200
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 30
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 110
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 80
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 50
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 40
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin found:
rank = 70
plugintype = QVariant(QString, "TransferFactory")
kget(20182) KGet::loadPlugins: TransferFactory plugin (
"kget_checksumsearchfactory" ) found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin (
"kget_mirrorsearchfactory" ) found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin ( "kget_kiofactory" )
found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin (
"kget_multisegkiofactory" ) found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin ( "kget_mmsfactory" )
found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin ( "kget_metalinkfactory"
) found and added to the list of available plugins
kget(20182) KGet::loadPlugins: TransferFactory plugin (
"kget_bittorrentfactory" ) found, but not enabled
kget(20182) KGet::loadPlugins: Number of factories = 6
kget(20182) KGet::load: ( "/home/$USER/.kde4/share/apps/kget/transfers.kgt" )
kget(20182) KGet::load: file: "/home/$USER/.kde4/share/apps/kget/transfers.kgt"
kget(20182) KGet::load: KGet::load -> group = "My Downloads"
kget(20182) KGet::load: KGet::load -> group not found
kget(20182) TransfersView::rowsInserted: TransfersView::rowsInserted
kget(20182) TransfersView::rowsInserted: parent is not valid 00
kget(20182) TransfersView::rowsInserted: openEditor for row 0
kget(20182) TransferGroup::load: TransferGroup::load
kget(20182) TransferGroup::load: TransferGroup::load -> add 4 transfers
kget(20182) KGet::addTransfers: src=
KUrl("http://gigenet.dl.osdn.jp/manjaro/67170/manjaro-kde-17.0-rc2-stable-x86_64.iso";)
dest= KUrl("file:///mnt/*blah*/manjaro-kde-17.0-rc2-stable-x86_64.iso")
group= "My Downloads"
kget(20182) KGet::addTransfers: src=
KUrl("https://cytranet.dl.sourceforge.net/project/manjarotest/kde/17.0-rc1/manjaro-kde-17.0-rc1-stable-x86_64.iso";)
dest= KUrl("file:///mnt/*blah*/manjaro-kde-17.0-rc1-stable-x86_64.iso")
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #45 from Ric Grant --- (In reply to Bug Janitor Service from comment #42) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! As soon as 5.27 enters the stable branch on Gentoo, I'll update and test. Unfortunately need this machine to remain as stable as possible and can't risk pulling a whole DE from testing. Nate, could you perhaps link to the main changelogs that we're hoping fix this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #47 from Ric Grant --- 5.27 still isn't in stable yet on Gentoo, so I haven't been able to test myself, BUT something just occurred to me and I'm wondering if this is the same for all of us... This particular laptop has 8gb RAM and a 512mb swap. It's getting old now but at the time of configuring it, 8gb seemed plentiful and in my ignorance I didn't think I'd need to set much of a swap up. These days with Plasma being quite memory hungry in general, and the likes of Virtualbox guests eating away at remaining resources, I'm hitting that 8gb capacity frustratingly often, and spilling over into swap. What I'm now thinking, is that with so little swap space and so much memory in use, when I close the lid and trigger hibernation, there isn't enough swap for all in-memory data to dump to and perhaps that's why icon placements are getting lost? If on lid-open the system comes back out of hibernation, tries to restore whatever in-memory variables the desktop icons use, and finds that those variables aren't in the swap file so just regenerates them as empties then this would totally explain the skewed locations! Does this sound familiar to others experiencing this issue? I'll resize my partitions as soon as I get chance and confirm if that, or indeed the 5.27 changes do fix this for me, but in the meantime if everybody could just compare their memory and swap capacities, we might find that there isn't anybody here who actually has enough swap to properly hibernate into. Would explain why this has been a problem for so many years, only affecting some but not all devices. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #55 from Ric Grant --- (In reply to Pasha from comment #52) > (In reply to Uwe Dippel from comment #51) > > And please, do it quickly! With the most recent modifications, my way out of > > this problem, described several times in this and the previous threads, my > > fail-safe remedy, the PlasmaConfigSaver, was broken. Now calling it up > > results in a freeze, with a black unresponsive screen with just the mouse > > cursor, reproduceably. > > The black, unresponsive screen with just mouse cursor on it is already 3-4 > years old and it's the very reason, besides dancing icons, which made me > quit KDE. Unfortunately, on the contrary of what you report, results were > pretty much unpredictable: you shut down you machine and at the next > reboot... BOOM! > > At first, the only way out was backupping .kde folder and restoring it - > just imagine the pain in the ass of backupping your DE every time you switch > off your machine... > > Eventually, the bug got so BIG that even restoring the old .kde folder still > didn't sort a way out of the black screen; the problem (and pain) was that I > couldn't exactly find what the heck was causing it it always came after > initial (long) configurations and a small period of use (like one or two > weeks). "Nice" to know this happened on Debian and some other distro I > tried. I got so pissed off with this buttfuck that you know how the story > went. > > Too bad to know that somebody else is getting the same bad black screen :( Not convinced the black screen issues are related to this at all and should probably be a separate discussion, but in my experience black screens tend to be related to video drivers and just recompiling those against your current kernel usually resolves. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #57 from Ric Grant --- (In reply to shadowfire+web from comment #54) > Hi, I'm new to this thread, not to having this issue. This bit me > infrequently between 2015 and 2019 on two separate Fedora workstations (each > with 1 monitor), then it went away but after a recent upgrade from Plasma > 5.26 to 5.27 it came back with a vengeance (single Fedora workstation, 2 > screens). Rather than (after using KDE/Plasma for over a decade) changing to > a different DE (which I was very tempted to do but I guess Gnome 2 isn't > around any more) I decided to try some debugging first. > > I've made an interactive shell script for myself with options to 1) create a > backup of plasma-org.kde.plasma.desktop-appletsrc and to 2) quit > plasmashell/restore appletsrc backup/restart plasmashell > ( kquitapp5 plasmashell ; cp -v $backupfile > $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc ; kstart5 plasmashell > & ) > > This allows me to quickly test out different screen configurations with the > same appletsrc. > > Notes on my current setup: > Left screen: Folder View, icons, panel on top of the screen > Right screen: Desktop View, no icons and panels etc. and set to primary > display (can't remember why I did that) > > Some provisional conclusions based on many tests: > -Turing the right screen off makes scrambling less frequent > -Setting panel to autohide (*) makes scrambling less frequent (50%) > -Setting right screen to Folder View usually moves my icons to the right > screen (arranged in rows) > > *) I've noticed during restart of plasmashell that sometimes icons are lined > up correctly but get scrambled within a few hundred milliseconds. And I also > noticed that their vertical space is squashed by a tiny factor when the > panel is loaded in. I assumed this is so that the panel doesn't cover up > icons so maybe the panel loading in may be a factor in this issue? > > So far I haven't seen this issue happening when the right screen is off and > panel is set to autohide but I want to test that some more... I didn't realise you could set one screen to be Folder view and another to be Desktop view actually. I'd always assumed the desktop settings were global, not per screen. Unsure why I'd have concluded that mind. Reading your post, I wondered if setting the primary screen to Desktop view would stop the icons attempting to move back to it when the secondary screen switches off, and hoped this would in turn prevent scrambling - but apparently not. If I leave my secondary screen as a Folder view with the icons arranged, and switch my primary to Desktop view, rebooting / closing the lid still scrambles everything like before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #22 from Ric Grant --- (In reply to Bharadwaj Raju from comment #21) > Because it's a hard bug to reproduce. Try as I might, I can't seem to get it > on my system. The last one (resolution change) I could at least reproduce, > so that was feasible to fix. > > Still, thanks very much for the findings, Ric Grant — maybe I can try some > fixes using all these clues, but it'll just be flying blind since again I > can't reproduce it at all here. Do you have a second monitor? I've actually never tried icons on the primary display myself (perhaps this only happens when there are no icons on there in fact!), but from everything I've read throughout all of these various bug reports, this is always a secondary screen issue. In case it aids with replication, I'll also attach a screenshot of how I group my icons on this secondary display. I've seen reports that having icons on the first row or in the first cell helps, though this never did for me. Every time when I close the lid and trigger this screen turning off and back on, the icons all end up rearranged and I've to shuffle them back to these locations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #23 from Ric Grant --- Created attachment 152072 --> https://bugs.kde.org/attachment.cgi?id=152072&action=edit Icons arranged neatly on secondary display before Plasma shuffles them on screen turn on -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #25 from Ric Grant --- (In reply to Bharadwaj Raju from comment #24) > Will try. I do have a second monitor but my desktop case only has one VGA > port, so I'll have to get an adapter of some kind, maybe. Just been experimenting. It seems I can do whatever I like on the primary display - icons stay where intended during reboots and lid closure. But the icons on the secondary screen still, even while the primary screen icons behave, get shuffled around. Sometimes they shuffle instantly, other times they look correct until you try to click on one and then they all shuffle. Most weirdly, clicking on the primary screen sometimes then corrects the positions on the secondary but clicking back on the secondary shuffles them again until after a few clicks they just remain in their shuffled position. Another potential clue - if I select my icons and drag them to the primary display, they drop into a long row instead of retaining their abstract order. As if the positions aren't carried over when moving from one screen to another and the new screen just sets them up as new icons at natural positions. I'm wondering therefore, if what's actually happening when the secondary screen is turned off and back on again is that Plasma sets this up as a new screen, moves the icons over to it, and they all just take on a default position? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #27 from Ric Grant --- (In reply to Nate Graham from comment #26) > I have a theory which is borne out by > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2120. > > Bug 354802 fixed the bulk of the bug by making layouts get remembered on a > per-desktop-dimensions basis. > > However the "remember things on a per-desktop-dimensions basis" feature > itself is buggy because the desktop dimensions change during startup, for > example when the panel appears. Because that's animated, there are a bunch > of intermediate states. There's code to batch them up, but it's apparently > rather buggy, and doesn't work well if initial startup is slow beyond a > certain level. So the "save/restore positions" code can get confused by > these intermediate states. We replaced one bug (in Bug 354802) with another, > less severe one. But still a bug, so positions aren't remembered in 100% of > cases. > > We have the same issue with widget positions, which > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2120 is > trying to fix. But it also appears to fix this as well, since now both bugs > are the same: caused by repeated desktop dimension changes at startup. Ohhh this sounds promising! Your mention of animation states and the references in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2118 to resolution changes happening during initiation fits with the console outputs I noted in my https://bugs.kde.org/show_bug.cgi?id=454345#c17 comment. It does sound a lot like we might see this fixed in an upcoming release!!? :-D. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #62 from Ric Grant --- (In reply to Nate Graham from comment #61) > This bug report is closed; please report new information or new > manifestations of the issue with different root causes in new bug reports. > Thanks. Shouldn't be closed, it isn't fixed. The number of separate bug reports that have had to be opened over the years for this because somebody keeps on closing it is ridiculous. Information is being lost in old reports that might actually be useful in the resolve! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #65 from Ric Grant --- (In reply to Nate Graham from comment #63) > The user-facing issue of desktop icons being re-arranged turns out to have > multiple causes. It isn't feasible to track them all in a single bug report; > that's not how issue tracking works. We need a separate bug report per > discovered cause, so we can fix them individually. That's just the way issue > tracking works, I'm afraid. Ignoring previous tickets for now, this ticket as its own instance was originally opened May 2022 by William. His report was that when icons are placed on a desktop and plasmashell is restarted, said icons scramble. This issue, as a standalone bug, is still an issue. If this ticket is closed somebody is just going to open another, reporting the same problem, and we're going to go through all of this again until it's again closed in this utterly ridiculous cycle. I totally appreciate this isn't a simple fix but we can't just keep on closing these tickets and expecting the problem to be resolved somewhere else. Apart from anything else, opening multiple tickets for what is essentially the same problem just makes KDE as a whole appear buggier than it really is, in terms of number of but reports at least. This, and all other related tickets, should be left unresolved, grouped, and cross referenced so that when related issues are resolved, developers can check whether these reports are also resolved and tick them off when that time comes, otherwise leaving them open for somebody to pick up at some point. That's how bug tracking works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #72 from Ric Grant --- (In reply to William from comment #71) > (In reply to Nate Graham from comment #70) > > Please stop changing the status to VERIFIED despite not verifying the fix. > > I'd like William to do that, since he's the one who reported this issue. > > Sry i didnt keep up with what was happening in this isssue and i only > recently got the 5-27 update in manjaro stable. > > But i am happy to report now that it doesnt happen anymore for me. i removed > my "read-only" workaround script and used the command "kquitapp5 plasmashell > && kstart5 plasmashell" at least 50 times in a row, which previously would > always result in some form of icon scramble, but this time it did not. Good > job to whatever was done in the end that fixed it. 5.27 seems like a great > release! > > PS: manjaro skipped the early point releases and went straight to plasma > 5.27.3. This is great news. Looking forward now to 5.27 hitting stable in Gentoo. Apologies, Nate, for my comment #62. I'd interpreted your comment #46 as meaning this hadn't been fixed after all but it sounds like I was wrong there. It's frustrating that this still isn't available in the stable branch for me yet and I can't test first hand, but admittedly I probably shouldn't have jumped the gun on that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #6 from Ric Grant --- (In reply to Nate Graham from comment #5) > Mose of the code here has changed to improve multimonitor use-cases in > Plasma 5.27. Any chance you can upgrade to that version and see if the issue > is fixed now? Still waiting for a stable 5.27 on Gentoo unfortunately, and need this particular laptop to remain stable so I'm being cautious about upgrading to test trees to be honest. https://packages.gentoo.org/packages/kde-plasma/plasma-desktop As soon as it's deemed stable enough though, I'll feedback. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #8 from Ric Grant --- 5.27.4-r1 is finally in the Gentoo stable branch. I'll pull the updates today and report back asap. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 Ric Grant changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #9 from Ric Grant --- (In reply to Nate Graham from comment #5) > Mose of the code here has changed to improve multimonitor use-cases in > Plasma 5.27. Any chance you can upgrade to that version and see if the issue > is fixed now? Running 5.27.4 now, and unfortunately this is still an issue. I rebooted after the upgrades to be certain nothing iffy would still be running from RAM. Positioned the icons, closed the lid for a few seconds, re-opened and all were back along the top row. Re-positioned again, rebooted, and all were scrambled completely. Re-positioned again, set to locked, closed the lid for a few seconds, re-opened and all were scrambled and locked to their scrambled positions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on rotated secondary screen reset to default positions or move to random positions on login/wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #11 from Ric Grant --- (In reply to Nate Graham from comment #10) > Darn. And unfortunately I cannot reproduce the issue with your exact steps. > :/ However while testing I did find another issue that's 100% reproducible > for me even when not using a rotated secondary screen: Bug 469062. > > Maybe I'm not testing correctly. Can you write super duper duper duper > detailed steps to reproduce? Another option is to take a phone video of the > issue happening in real-time. There's a bit of fumbling as using a touchpad while you're trying to both see and record it is apparently more difficult than you'd imagine, but here's a video showing the problem both when rebooting and when closing + opening the lid (effectively turning the screens off). Also tried to show the relevant set-up of both screens, and of the icon settings. Hopefully all clear enough. I can't promise I'll keep this video in Dropbox forever so please download a copy if useful. Came out a bit whopping at 1.6GB ! https://www.dropbox.com/s/rzbmnokilbwzj1e/20230427_182316.mp4?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on rotated secondary screen reset to default positions or move to random positions on login/wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #13 from Ric Grant --- Created attachment 158527 --> https://bugs.kde.org/attachment.cgi?id=158527&action=edit plasma-org.kde.plasma.desktop-appletsrc after scrambling -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on rotated secondary screen reset to default positions or move to random positions on login/wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #14 from Ric Grant --- Created attachment 158528 --> https://bugs.kde.org/attachment.cgi?id=158528&action=edit plasma-org.kde.plasma.desktop-appletsrc before scrambling -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on rotated secondary screen reset to default positions or move to random positions on login/wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #15 from Ric Grant --- (In reply to Nate Graham from comment #12) > Downloaded it, thanks. What an interesting piece of hardware. A screen in > the touchpad; amazing. > > Can you attach your ~/.config/plasma-org.kde.plasma.desktop-appletsrc file > after you re-arrange the icons to be in the right locations, then reproduce > the issue, then attach it again? We can see what changed and maybe why it's > happening. > > If you find any personally-identifying information in there, please do scrub > it before attaching. :) It's a brilliant additional screen for positioning icons on that are then never hidden by apps, or for dragging apps down to that are just useful to be visible while doing something else. Just immensely irritating that the icons keep shuffling! When they're along the top of the screen they become really easy to accidentally click on when intending to tap a minimised window on the main panel too. Tidy and messy versions of plasma-org.kde.plasma.desktop-appletsrc attached, but it seems to only be the positions line within the [Containments][2][General] section that changes, perhaps unsurprisingly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Ric Grant changed: What|Removed |Added CC||rich...@qweb.co.uk --- Comment #17 from Ric Grant --- I've been experiencing this since I set up a new laptop in January 2021. Laptop is an Asus UX563F which has a second screen under the touchpad. It's a vertical phone sized screen rotated 90 degrees to make a touchpad and it's a really handy place to put app icons, except that Plasma scrambles them. In Plasma System Settings -> Display Configuration, the main laptop screen is 3840x2160 at 60hz. Secondary screen is 1080x2160 at 50hz, rotated 90 degrees anticlockwise. There's a 150% global scale applied. This is an Optimus set-up so I'm running Xorg with modesetting drivers and Bumblebee to switch between Intel and nVidia GPUs. For all this time, I've barked up many trees trying to figure out if this is caused by the screen rotation (XrandR under the hood I assume?), the modesetting/bumblebee configuration, the global scale, etc. I've read through all of the comments in this bug report, https://bugs.kde.org/show_bug.cgi?id=354802 , and a bunch of other duplicates, and like many others I've spent some time trying to work around the ever changing plasma-org.kde.plasma.desktop-appletsrc file but this seems to be updated regularly when all sorts of things happen, it's not just for desktop icon arrangement so readonly states etc don't cut it for me. Additionally, adding scripts to shutdown/startup procedures to dynamically fiddle with this isn't enough because closing the laptop lid or just turning off and back on the secondary screens doesn't trigger those events. What I've found though, and hopefully this is useful to somebody with more knowledge of these scripts than me, is that if you open a Konsole and restart plasmashell: $ kquitapp5 plasmashell $ kstart5 plasmashell Then when you do something to trigger the icon scramble, e.g. close and open the lid or turn off and on the second display, the Konsole floods with interesting errors like this: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:382:21: Unable to assign [undefined] to bool file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:497:25: Unable to assign [undefined] to bool and this: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:320:17: QML Label: Binding loop detected for property "width" FolderItemDelegate.qml appears to be used for generating the icons in folder views, which fits with this being a bug for people who run the desktop as a folder view. Lines 382 and 497 reference model.isLink and model.selected so I'm wondering whether model isn't fully set-up yet at the time this script runs. If these couple of lines throw errors because they're expecting to read properties that don't yet exist, then other lines more related to positioning could also be looking at properties that simply don't yet exist. Which makes sense if XrandR for example hasn't yet finished rotating the output. There's also FolderView.qml in here which I assume sets up the main container for these icons to sit in. Interestingly this seems to be where all of the drag handling code sits, including an onPositionChanged handler that I think is designed to figure out where in the grid to bounce icons to when dragging them around. Is it possible that this routine is firing prematurely during the initiation phase and bouncing icons to grid locations before the screen sizing and rotation has happened, because their current position isn't valid at the point of firing? Lots of interesting code in these two files and though I might once again be barking up the wrong tree, I do feel it worth somebody with more knowledge of this stuff looking over it. Hope this in some way helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #2 from Ric Grant --- (In reply to Nate Graham from comment #1) > Ooh, this should have been fixed in Plasma 5.23. Please check again once > that's released in a month and a half! Brilliant news. I'll update as soon as that's in the Gentoo repositories and confirm back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385824] Desktop icons move when you use several displays
https://bugs.kde.org/show_bug.cgi?id=385824 Ric Grant changed: What|Removed |Added CC||rich...@qweb.co.uk --- Comment #6 from Ric Grant --- Experiencing this problem with Plasma 5.19.5 on Gentoo. My laptop is an Asus UX563F which has a permanently attached second screen under the touchpad so I'm trying to use this for desktop icons since it's more useful than having to hide all open windows to get to the primary desktop, but occasionally after a reboot, or after returning from sleep, or after folding the screen over and back again (second screen disconnects while the primary screen is flipped over), I'm finding that the icons lose their placement and just revert to their natural single row position. The screen is positioned and rotated via KDE's System Settings -> Display and Monitor configuration, which presumably writes an xrandr set-up somewhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #38 from Ric Grant --- (In reply to Uwe Dippel from comment #36) > "why is it so hard to remove any logik that touches that desktop-appletrc > file during plasmashell startup? " > I think I can. It's the old topic of systemd. It's water under the bridge. > Some 15 years ago, people wanted to enhance the user experience by > shortening the startup sequence, and therefore started things in parallel. I > never followed the gory details, since I am the old-fashioned style person, > and would have preferred the slow, and clean, start. AFAIK, systemd took > over many items, including login, and spawning independent items in > parallel. I THINK, with a totally clean sequential startup, no other process > would interfere - or could interfere - in desktop applet layout. > This is why I thought, the semaphore-like wrap around the startup, as > proposed recently, could solve the case by isolating the desktop rendering, > protecting the layout. > > [If you look around, you'll find some other startup-bugs, including some > affecting me, that could be attributed to parallelisms introduced by > systemd; leading to RANDOM - that is not always or even rarely occurring - > faulty behaviour. Systemd introduced a clever though not fully deterministic > startup behaviour. I am willing to bet that after taking out systemd and > revert to the old style rc-startup system - which is not possible, so that > this is hypothetical - all these problems would be gone. With a slow, though > fully sequential strictly one-task-at-a-time start sequence, race conditions > are clearly avoided whatever the lengths of the steps. Boringly long, I > agree.] I'm 'afraid' I can confirm it's not systemd related, no. Gentoo user here, and although I've used systemd in the past, this particular laptop hasn't ever seen it. Gentoo has profiles which basically define the base set-up, ( https://wiki.gentoo.org/wiki/Profile_(Portage) ), and this laptop has always been on the OpenRC based "desktop/plasma (stable)" profile, rather than the systemd based "desktop/plasma/systemd (stable)" profile (or any of the other many options), so there's literally never been anything systemd related to get in the way. OpenRC does also support launching startup daemons in parallel via an rc_parallel option in /etc/rc.conf but for me, this too has always been disabled so we can assume this isn't causing problems either. Besides, Plasma starts after X which I believe waits for its own dependencies to fire up anyway, even with a parallel boot, so by the time Plasma kicks in there should be very few daemons still initiating. Things like WiFi connections which need to wait for remote services might not be quite there yet, but probably nothing related to graphics at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 Ric Grant changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Ric Grant --- I've now updated to the finally stable Plasma 5.23.4-r1 and, unfortunately, not only does this issue still seem to occur, now the second screen seems even more problematic. Previously the icons reset their positions when the lid was closed and re-opened but the screen otherwise behaved properly. Now, in addition to this happening, sometimes clicking an icon turns the screen off for a few seconds causing the icons to reset their positions again when it powers back up. Other times after opening the lid the icons actually are in the correct place still, but clicking anywhere on that screen then resets their positions. I'm not seeing anything useful in dmesg or Xorg.0.log when this happens, surprisingly. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492725] New: Using Divi builder, Ad not showing on Update
https://bugs.kde.org/show_bug.cgi?id=492725 Bug ID: 492725 Summary: Using Divi builder, Ad not showing on Update Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ricdras...@gmail.com Target Milestone: --- I am using Divi Builder on Wordpress site. When I update the page, there are page elements missinf and ads are not showing -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492725] Using Divi builder, Ad not showing on Update
https://bugs.kde.org/show_bug.cgi?id=492725 Ric D changed: What|Removed |Added URL||https://www.jailtojob.com/c ||ompanies-hire-felons.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433867] New: Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 Bug ID: 433867 Summary: Icons on secondary screen move around on boot / wake. Possibly because of screen rotation Product: plasmashell Version: 5.20.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: rich...@qweb.co.uk CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY My laptop, an ASUS US563F, includes a secondary screen under the touchpad. The screen is at a 90 degree rotation so within KDE's own display configuration, I have the orientation set to a 90 degrees anticlockwise rotation. KDE picks this up just fine and rotates properly once I'm logged in, although SDDM shows unrotated upon initial boot which is understandable if the display config is user specific, but if I place icons on this screen, they're shuffled to seemingly random locations every time I boot up, or close the lid and re-open, or fold the lid back and reset to a natural position. Each of these events effectively turns the screen off and back on again so presumably it's the power-on event that triggers this shuffle. My feeling is that KDE is setting the icon locations first, then actioning the rotation, and having to shuffle icons around to fit the new orientation. Swapping these two events so as the rotation happens before the icons are loaded would I'm sure resolve. STEPS TO REPRODUCE 1. Add icons to a secondary screen with a 90 degree orientation. 2. Reboot, or close the lid and re-open if a laptop, or probably just reconnect the secondary screen. 3. Compare the icon positions to their original. OBSERVED RESULT Icons move around to seemingly random locations each time the screen is reconnected. EXPECTED RESULT Icons shouldn't move around on their own accord. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Gentoo GNU/Linux on an ASUS UX563F laptop with a secondary screen permanently attached under the touchpad device. I've experienced this bug since originally setting this laptop up probably 6 months or so ago. Unsure of the KDE versions in use at that time but this certainly isn't a new issue to the above versions. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419884] New: Can't align multiple clips at once based on audio.
https://bugs.kde.org/show_bug.cgi?id=419884 Bug ID: 419884 Summary: Can't align multiple clips at once based on audio. Product: kdenlive Version: 19.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ricflo...@labola.net Target Milestone: --- SUMMARY Based on the documentation (see url below), Kdenlive can align multiple clips based on their audio, after having set an audio reference to align them to. But only one clip gets aligned. All the remaining ones are kept in place. STEPS TO REPRODUCE 1. If you don't have a multicamera or multiaudio footage, make 3 copies of the same video file. 2. Put at least three clips in the timeline, then follow the steps given at https://userbase.kde.org/Kdenlive/Manual/Timeline/Right_Click_Menu/en 3. Select the clip that you would like to align to. Right click, select Set Audio Reference. Select all the clips that you would like to get aligned. Right-click and select Align Audio to Reference. OBSERVED RESULT Only one clip gets aligned. EXPECTED RESULT All clips get aligned. SOFTWARE/OS VERSIONS Linux Mint / Kdenlive flatpak 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 360535] New: Crash on add to favorites
https://bugs.kde.org/show_bug.cgi?id=360535 Bug ID: 360535 Summary: Crash on add to favorites Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ricardo.adams...@gmail.com Application: lancelot (1.9.5) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-38-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: For years, the lancelot launchers crashes when I add a application to favorites. Note: this only happens it the favorites column is full. A manual resizing of the laucher is required before adding a new item to prevent the crash. Otherwise the menu crashes every time. thanks The crash can be reproduced every time. -- Backtrace: Application: Lancelot (lancelot), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62c020b800 (LWP 28389))] Thread 3 (Thread 0x7f629c9a1700 (LWP 28390)): #0 0x7f62bc57e82d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f62adc6ff75 in ?? () from /usr/lib/nvidia-352/tls/libnvidia-tls.so.352.63 #2 0x7f62b400bc10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62b3fcab14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f62b3fcaf7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f62b3fcb0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f62bcd067be in QEventDispatcherGlib::processEvents (this=0x7f62980008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #7 0x7f62bccd80af in QEventLoop::processEvents (this=this@entry=0x7f629c9a0da0, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f62bccd83a5 in QEventLoop::exec (this=this@entry=0x7f629c9a0da0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f62bcbd4c5f in QThread::exec (this=this@entry=0xbcc640) at thread/qthread.cpp:537 #10 0x7f62bccb9823 in QInotifyFileSystemWatcherEngine::run (this=0xbcc640) at io/qfilesystemwatcher_inotify.cpp:265 #11 0x7f62bcbd732f in QThreadPrivate::start (arg=0xbcc640) at thread/qthread_unix.cpp:349 #12 0x7f62b48eb182 in start_thread (arg=0x7f629c9a1700) at pthread_create.c:312 #13 0x7f62bc58d47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f6292d6b700 (LWP 28391)): #0 0x7f62b48ee7ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f628c000a80) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7f628c000a80) at pthread_mutex_unlock.c:310 #2 0x7f62b400c9b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62b3fca680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f62b3fcaf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f62b3fcb0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f62bcd067be in QEventDispatcherGlib::processEvents (this=0x7f628c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #7 0x7f62bccd80af in QEventLoop::processEvents (this=this@entry=0x7f6292d6ada0, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f62bccd83a5 in QEventLoop::exec (this=this@entry=0x7f6292d6ada0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f62bcbd4c5f in QThread::exec (this=this@entry=0xbb42e0) at thread/qthread.cpp:537 #10 0x7f62bccb9823 in QInotifyFileSystemWatcherEngine::run (this=0xbb42e0) at io/qfilesystemwatcher_inotify.cpp:265 #11 0x7f62bcbd732f in QThreadPrivate::start (arg=0xbb42e0) at thread/qthread_unix.cpp:349 #12 0x7f62b48eb182 in start_thread (arg=0x7f6292d6b700) at pthread_create.c:312 #13 0x7f62bc58d47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f62c020b800 (LWP 28389)): [KCrash Handler] #6 size (this=) at /usr/include/qt4/QtCore/qlist.h:98 #7 size (this=) at /usr/include/qt4/QtCore/qlist.h:137 #8 Lancelot::Models::Applications::contextActivate (this=0x1, index=1, context=0x2329480) at ../../../libs/lancelot-datamodels/Applications.cpp:307 #9 0x7f62bf24bd64 in Lancelot::ActionListViewItemFactory::itemContext (this=0x226afa0, sender=sender@entry=0x22ee9b0, mouseCoordinate=, mouseCoordinate@entry=true) at ../../../libs/lancelot/widgets/ActionListView.cpp:621 #10 0x7f62bf24be76 in Lancelot::ActionListViewItem::contextMenuEvent (this=0x22ee9b0, event=0x7ffdbcef7620) at ../../../libs/lancelot/widgets/ActionListView.cpp:109 #11 0x7f62bda2f655 in QGraphicsItem::sceneEvent (this=0x22ee9c0, event=0x7ffdbcef7620) at graphicsview/qgraphicsitem.cpp:6725 #12 0x7f62bda567aa in QGraphicsScene::contextMenuEvent
