[kwin] [Bug 391858] New: KDE screengrabs login screen, then uses it in Compiz cube background
https://bugs.kde.org/show_bug.cgi?id=391858 Bug ID: 391858 Summary: KDE screengrabs login screen, then uses it in Compiz cube background Product: kwin Version: 5.8.7 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: linuxst...@dski.net Target Milestone: --- Clean install: Mageia 6, KDE Plasma 5.8.7, Frameworks 5.32.0, x86_64. What appears to happen, is that when you login, KDE takes a screenshot of the login page, complete with the number of dots you used for your password (if it's shorter than the field length - tested that on clean test profile). When you use Compiz with the cube display, middle clicking the desktop to show the cube, you are shown the screenshot of the login screen behind whatever image you are using as a desktop image (you need to change opacity in Compiz to prove it). This should not happen, KDE should not be taking a screenshot, nor adding it as a background to the cube. If you change Compiz transparency of the cube, you can see the login screen screenshot. If the cube is 100% transparent, you should see the "skydome" behind the applications running and cube, instead, you see the KDE login screenshot. When you logout / reboot, you are also flashed up the screenshot of the KDE login screen before being kicked to terminal display of shutdown. This is on a clean install, and also reproducible on a clean / new user creation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389647] Syslog filling up hundreds of lines plasmashell kcoreaddons.desktopparser errors
https://bugs.kde.org/show_bug.cgi?id=389647 --- Comment #2 from Ski --- Created attachment 111400 --> https://bugs.kde.org/attachment.cgi?id=111400&action=edit Screenshot of package manager Screenshot of package manger of all "KCM" files on the system. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 389646] Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
https://bugs.kde.org/show_bug.cgi?id=389646 --- Comment #3 from Ski --- Sorry for the delay in replying. The problem text is put into /var/log/syslog and /var/log/messages, both become huge with the error, and if not caught, can make the system unstable, or hard to reboot when it eventually fills up /var . There is a "temporary" workaround, but not an acceptable one. You can move all the text files out of the user's home directory, and put it in any sub-directory, but the bug remains. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391858] KDE screengrabs login screen, then uses it in Compiz cube background
https://bugs.kde.org/show_bug.cgi?id=391858 Ski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- Ever confirmed|0 |1 --- Comment #2 from Ski --- (In reply to Martin Flöser from comment #1) > You are reporting vor KWin. If you have issues Witz compiz you need to > report to compiz. Compiz starts AFTER login, KWin before. It's a KDE problem, KDE is doing screenshot of the login screen, screenshot application is nothing to do with Compiz either. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 389646] Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
https://bugs.kde.org/show_bug.cgi?id=389646 --- Comment #5 from Ski --- (In reply to Christoph Feck from comment #4) > In the bug description, you replaced the config file name with "In file > whatever". Unless you show us the actual file names, we cannot proceed with > this issue. Sorry, I edited a bit too much out of the original report in the file names. The file can be named "whatever.txt" - the bug is the same whatever the text file name actually is. It only affects text files, and looks like it only specifically affects .txt extension, as no other text files (config etc) are shown in the log files. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 388594] New: Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 Bug ID: 388594 Summary: Dolphin crash trying to close it Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: linuxst...@dski.net Target Milestone: --- Application: kdeinit5 (16.12.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: Was closing Dolphin and Digikam when Dolphin crashesd / popup on sdcreen - Unusual behavior I noticed: Dolphon crashed just from trying to close it. -- Backtrace: Application: Dolphin (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e11f5b800 (LWP 7655))] Thread 3 (Thread 0x7f8df8b02700 (LWP 7657)): #0 0x7f8e104ecf0d in poll () from /lib64/libc.so.6 #1 0x7f8e0d0acc94 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f8e0d0acd9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f8e10a7ce2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8e10a2849a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8e108623bc in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f8e11e80635 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f8e10866ff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f8e0de0266d in start_thread () from /lib64/libpthread.so.0 #9 0x7f8e104f8d4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8dfa9a2700 (LWP 7656)): #0 0x7f8e1050622b in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f8e1048264a in calloc () from /lib64/libc.so.6 #2 0x7f8e0c10d3e3 in ?? () from /usr/lib64/nvidia-current/tls/libnvidia-tls.so.384.98 #3 0x7f8e0d0b1ed1 in g_malloc0 () from /lib64/libglib-2.0.so.0 #4 0x7f8e0d0ca93d in g_slice_free1 () from /lib64/libglib-2.0.so.0 #5 0x7f8e0de013d9 in __nptl_deallocate_tsd.part.4 () from /lib64/libpthread.so.0 #6 0x7f8e0de02809 in start_thread () from /lib64/libpthread.so.0 #7 0x7f8e104f8d4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8e11f5b800 (LWP 7655)): [KCrash Handler] #6 0x7f8e1047c083 in malloc_consolidate () from /lib64/libc.so.6 #7 0x7f8e1047eb28 in _int_free () from /lib64/libc.so.6 #8 0x7f8e10481db8 in free () from /lib64/libc.so.6 #9 0x7f8dfd6da500 in QXcbEventReader::~QXcbEventReader() () from /lib64/libQt5XcbQpa.so.5 #10 0x7f8dfd6aab3b in QXcbConnection::~QXcbConnection() () from /lib64/libQt5XcbQpa.so.5 #11 0x7f8dfd6ab049 in QXcbConnection::~QXcbConnection() () from /lib64/libQt5XcbQpa.so.5 #12 0x7f8dfd6ac7c6 in QXcbIntegration::~QXcbIntegration() () from /lib64/libQt5XcbQpa.so.5 #13 0x7f8dfd6ac8c9 in QXcbIntegration::~QXcbIntegration() () from /lib64/libQt5XcbQpa.so.5 #14 0x7f8e10d678a7 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /lib64/libQt5Gui.so.5 #15 0x7f8e0f2c2f69 in QApplicationPrivate::~QApplicationPrivate() () from /lib64/libQt5Widgets.so.5 #16 0x7f8e10a5c98c in QObject::~QObject() () from /lib64/libQt5Core.so.5 #17 0x7f8e10a2bfd4 in QCoreApplication::~QCoreApplication() () from /lib64/libQt5Core.so.5 #18 0x7f8e0f2c4904 in QApplication::~QApplication() () from /lib64/libQt5Widgets.so.5 #19 0x7f8e0718f46e in kdemain () from /usr/lib64/libkdeinit5_dolphin.so #20 0x0040818f in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #21 0x00409437 in handle_launcher_request(int, char const*) [clone .isra.26] () #22 0x00409bd6 in handle_requests(int) () #23 0x00404dd3 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388594] Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 --- Comment #2 from Ski --- I filed the initial bug as the system was a clean install of KDE5 / Plasma. However, the problem was/is random, and so far it hasn't happened again. If it does happen again, I will post whatever I can get from the bug report. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386764] equalizer is not working
https://bugs.kde.org/show_bug.cgi?id=386764 Ski changed: What|Removed |Added CC||linuxst...@dski.net --- Comment #2 from Ski --- I have a clean install of my Linux distro, phonon gstreamer is the backend, the equaliser does NOT work for me either. It worked fine in KDE4. The only thing that has been fixed in Amarok is it finally after years of blank, shows the frequencies of the bands. Also, the graphic equaliser does not work either ./ does not show. Has it been removed? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 388819] New: Amarok equaliser does not work, no graphic equaliser either
https://bugs.kde.org/show_bug.cgi?id=388819 Bug ID: 388819 Summary: Amarok equaliser does not work, no graphic equaliser either Product: amarok Version: 2.8.90 (2.9 beta) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Equalizer Assignee: amarok-bugs-d...@kde.org Reporter: linuxst...@dski.net Target Milestone: 2.9 Starting new bug as bug report https://bugs.kde.org/show_bug.cgi?id=386764 closed / is marked "works for me", when it does not work. I have a clean install of my Linux distro - KDE5, phonon gstreamer is the backend, the equaliser does NOT work for me. It worked fine in KDE4. The only thing that has been fixed in Amarok is it finally after years of blank, shows the frequencies of the bands. Also, the graphic equaliser does not show. Has it been removed? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 389646] Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
https://bugs.kde.org/show_bug.cgi?id=389646 --- Comment #7 from Ski --- It's taken few days for the bug to re-appear, but below is the result of "ps -x", redirected into a text file, where even that text file caused the error text to get logged into syslog! ps -x https://pastebin.com/TeHXDbGg And the syslog entries because of this "ps -x" text file.. Apr 6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 1: " Invalid entry (missing '=') Apr 6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 2: " Invalid entry (missing '=') Apr 6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 3: " Invalid entry (missing '=') Apr 6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 4: " Invalid entry (missing '=') etc. etc. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388594] Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 --- Comment #3 from Ski --- Created attachment 109930 --> https://bugs.kde.org/attachment.cgi?id=109930&action=edit Screnshot, need debug files... I managed to get a few more Dolphin crashes just by closing Dolphin, but I cannot get more information because it wants debug stuff and doesn't say the actual package needed to install. The files mentioned in the screenshot exist on the system. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388594] Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 --- Comment #5 from Ski --- You're right, I am using the nVidia driver, but the Nouveau driver in the clean install of the OS made the video horribly unstable, where it used to be rock solid. It's something in KDE5, there were no problems with either driver under KDE4. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388594] Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 --- Comment #7 from Ski --- I have changed to the Nouveau driver temporarily, which seems to have got more stable since a kernel update a few days ago, but had to change some settings to get video to work in VLC etc., I loose VDPAU. For the moment the bug has not happened again. Will run the system for a few days and update the bug again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388594] Dolphin crash trying to close it
https://bugs.kde.org/show_bug.cgi?id=388594 --- Comment #9 from Ski --- Whatever the problem is, it seems to be triggered by somehow interacting between KDE5 and the nVidia driver, I have so far not seen any crash of Dolphin using the free Nouveau driver. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 389327] New: Amarok does not play last second(s) of tracks, affects played stats and last.fm scrobbling
https://bugs.kde.org/show_bug.cgi?id=389327 Bug ID: 389327 Summary: Amarok does not play last second(s) of tracks, affects played stats and last.fm scrobbling Product: amarok Version: 2.8.90 (2.9 beta) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: linuxst...@dski.net CC: ma...@laitl.cz Target Milestone: 2.9 Sound system backend: Phonon-gstreamer With a clean install of Linux / KDE5, Amarok does not play songs to the very end of the track, it is especially noticeable when tracks are continuous - there's no gapless playback. The problem causes two problems: 1. When playing tracks, the statistics of being played are not necessarily logged into the database (I use MariaDB, although the version that uses Amarok's own database has the same result). If you queue songs, or play songs normally, the ONLY song guaranteed to be logged into the database as played / date / time etc, is the very last track, which usually plays right to the very end of the track. I have played a few new tracks a few times, but they are not being logged as having ever been played because the tracks do not play to the end, The tracks are in the database correctly. 2. Because of the problem described in 1, this is affecting last.FM scrobbling. What happens is, a track plays, the details are sent to Last.FM as "now playing..." and you can see that on your Last.FM stats page. Then when you refresh your stats page on Last.FM when the next track starts playing, the track you were playing is deleted - it is registering as a user interrupted track, so it is not logged as having been played. Again, the one track that does get logged, is the very last track you play - it plays to the end. I have tracks on a tablet to test Last.FM using VLC, there is no problem with the Last.FM account, all tracks played on the tablet are logged, so it is definitely an Amarok problem. As a further test. I have queued just one track and let that play. It plays to the end, and it does get logged into Last/M stats properly as having been played. So the problem is with the tracks being cut short. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 389328] New: Enabling recursive scan folders locks up / crashes Amarok
https://bugs.kde.org/show_bug.cgi?id=389328 Bug ID: 389328 Summary: Enabling recursive scan folders locks up / crashes Amarok Product: amarok Version: 2.8.90 (2.9 beta) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/Local Assignee: amarok-bugs-d...@kde.org Reporter: linuxst...@dski.net CC: ma...@laitl.cz, ralf-eng...@gmx.de Target Milestone: 2.9 Sound system: phonon-gstreamer Despite a clean install of Linux/KDE5, I have noticed this bug is still around (it's been in previous versions of Amarok, but I only recently got a KDE account to report it). Go to Configure Amarok > Local Collection. Enable "Scan folders recursively", it hard locks up Amarok, you have to do a kill -9 (or xkill) to get to restart Amarok. If you played songs before the lockup, all the stats will be lost. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 389646] New: Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
https://bugs.kde.org/show_bug.cgi?id=389646 Bug ID: 389646 Summary: Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors Product: kdelibs Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: linuxst...@dski.net Target Milestone: --- Not sure what category to put this problem in.. KDE Plasma: 5.8.7 KDE Frameworks version: 5.32.0 Mageia 6, x86_64 Clean install. My syslog file is multi-GB in file size, filling up with the following nonsense with 10's thousands of lines generated per boot.. kdeinit5[15348]: "KConfigIni: In file whatever, line 1: " Invalid entry (missing '=') kdeinit5[15348]: "KConfigIni: In file whatever, line 2: " Invalid entry (missing '=') .. etc .. etc kdeinit5[15348]: "KConfigIni: In file whatever, line 684: " Invalid entry (missing '=') -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389647] New: Syslog filling up hundreds of lines plasmashell kcoreaddons.desktopparser errors
https://bugs.kde.org/show_bug.cgi?id=389647
Bug ID: 389647
Summary: Syslog filling up hundreds of lines plasmashell
kcoreaddons.desktopparser errors
Product: plasmashell
Version: 5.8.7
Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Desktop Containment
Assignee: se...@kde.org
Reporter: linuxst...@dski.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
KDE Plasma: 5.8.7
KDE Frameworks version: 5.32.0
Mageia 6, x86_64
Clean install.
Hundreds of lines in my syslog filled up with nonsense like:
Jan 30 14:58:20 local plasmashell[4792]: kf5.kcoreaddons.desktopparser: Could
not locate service type file kservicetypes5/, tried
("/home/someuser/.local/share", "/var/lib/plasma5-profiles/common/share",
"/usr/local/share", "/usr/share")
--
You are receiving this mail because:
You are watching all bug changes.
