[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #3 from Raymond Wooninck --- If everyone would have a proper look, then it would have been visible that the KDEPIM package itself was not published yet. Unfortunately KDE Applications finds itself in a slow building state, so it will take time to get this completely published. This is actually the risk of utilizing a development repository. KDE Applications would have come to Tumbleweed and Leap 42.1 as soon as everything would have been build properly. At this moment, I would suggest to revert back to the versions that are offered in Tumbleweed and/or Leap:Updates -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 --- Comment #4 from Raymond Wooninck --- Please close this bug as invalid and this one should have been reported at bugzilla.opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 344778] libkmahjongg installs lib twice
https://bugs.kde.org/show_bug.cgi?id=344778 --- Comment #3 from Raymond Wooninck --- Apologies, it seems that I never received the initial email indicating the bug. I had a quick look at the CMakeLists.txt and it seems that the second install line should be removed. I will do this later today. Apologies for this. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 344778] libkmahjongg installs lib twice
https://bugs.kde.org/show_bug.cgi?id=344778 --- Comment #4 from Raymond Wooninck --- Git commit e8a37284fca8e74986ce3a3ff979afd8e70484af by Raymond Wooninck. Committed on 05/01/2016 at 14:59. Pushed by rwooninck into branch 'master'. Remove the double install call for the library M +0-2CMakeLists.txt http://commits.kde.org/libkmahjongg/e8a37284fca8e74986ce3a3ff979afd8e70484af -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] New: kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Bug ID: 358216 Summary: kmail keeps running in the background after quitting the program Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tittiatc...@gmail.com I have noticed that kmail actually keeps running in the background after you try to close the program. Selecting "File -> Quit" makes the systray icon disappear, but the kmail process is still active in the background. Even with "Alt-Tab" window switcher, you can not find the kmail window anymore. One would expect that kmail is gone. When you now start a new kmail session, you suddenly get a crash reported from kmail indicating if you want to report a bug or to restart the program. The newly started kmail functions normally. This also applies to kontact !! Reproducible: Always Steps to Reproduce: 1. Start kmail or kontact. 2. Choose File -> Quit (kmail or kontact will close normally) 3. Open a konsole and check with ps if kmail or kontact are still there Actual Results: the kmail or kontact process is still active in the background, but can not be reached. Starting now a new kmail or kontact will cause a crash report for the old active process. Expected Results: The kmail or kontact process is normally closed and disappeared. Starting a new session afterwards should not generate a crash. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #2 from Raymond Wooninck --- (In reply to Daniel Vrátil from comment #1) > Could you try to get a backtrace to see what KMail is doing that's > preventing it from closing? Hi Dan, Sure. As long as you let me know what exactly you are looking for or how I should get the backtrace :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #3 from Raymond Wooninck --- Hi Dan, As requested, I attached gdb to the running process and then entered "t a a bt" to create the backtrace. The most interesting part would be this: Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec() () from /usr/lib64/libKF5CoreAddons.so.5 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 Looking at the source code of kmkernel.cpp (at line 1410) then it seems to try to run jobStatistics->exec() which somehow doesn't return. Hope this helps. Let me know if you need more info -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #4 from Raymond Wooninck --- A better one with also the debug info for libKF5CoreAddons. It could be that it is a change in coreaddons. Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec (this=this@entry=0x96df70) at /usr/src/debug/kcoreaddons-5.19.0git.20160109T125454~e8444d1/src/lib/jobs/kjob.cpp:199 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Raymond Wooninck changed: What|Removed |Added Severity|normal |major --- Comment #5 from Raymond Wooninck --- In a number of cases, this also causes a 100% cpu utilization of the remaining kmail process. When this happened, I attached gdb to this kmail process and exactly the same backtrace was generated. At this moment it would make kmail not really a good candidate for KDE Apps 16.04 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #1 from Raymond Wooninck --- I see exactly the same behavior on my system with Qt 5.6 and git master for Plasma, Frameworks and Apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] New: Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Bug ID: 360363 Summary: Systray doesn't initialize itself properly when Widgets are locked Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: tittiatc...@gmail.com The new systray in plasma-workspace does not initialize itself correctly when the widgets are locked. When the session is started and the widgets are locked, the systray itself is created, but there are no entries. Plasmoids like network monitor, notifications, plasma-pa, Powerdevil, etc are not appearing. For those people that uses Wireless connectivity, this means that the network also is not initialized as that the plasmoid itself is not started. However once the desktop session has started and I am starting e.g. Kmail, then the new email icon appears in the systray. As soon as I unlock the widgets and perform a logout/login, the systray is correctly initialized and all plasmoids are there. Reproducible: Always Steps to Reproduce: 1. Lock the widgets on the desktop/Panel 2. Logout 3. Login Actual Results: The systray is empty, not even the little triangle to show the hidden plasmoids is shown Expected Results: Systray to initialize correctly and show the entries for plasma-pa, notifications, network manager, battery, etc -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] New: Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 Bug ID: 359042 Summary: Plugins are displayed as "full" applications. Product: muon Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: tittiatc...@gmail.com CC: echidna...@kubuntu.org, sit...@kde.org I have digikam installed, which has a couple of plugins. When I check in the Gnome Software Center, then I see that these plugins are listed on the detailed page of digikam. In Discover however, these plugins are listed as "full" applications in the installed list and the plugins are not shown on the detailed page of digikam. I have added some screenshots to show the issue. In my view Discover should do the same as the GNome Software Center and list the plugins only on the detailed page of Digikam. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #1 from Raymond Wooninck --- Created attachment 97024 --> https://bugs.kde.org/attachment.cgi?id=97024&action=edit screenshot of the Installed Applications showing the digikam plugins (ImagePlugins) -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #2 from Raymond Wooninck --- Created attachment 97025 --> https://bugs.kde.org/attachment.cgi?id=97025&action=edit Screenshot of the detailed info screen of one of the digikam plugins. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #3 from Raymond Wooninck --- Created attachment 97026 --> https://bugs.kde.org/attachment.cgi?id=97026&action=edit Screenshot of the detailed info screen of digikam. Nowhere it is mentioned that Digikam has some plugins available -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #4 from Raymond Wooninck --- Created attachment 97027 --> https://bugs.kde.org/attachment.cgi?id=97027&action=edit This is how the Gnome software center displays the digikam details -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #5 from Raymond Wooninck --- Created attachment 97028 --> https://bugs.kde.org/attachment.cgi?id=97028&action=edit And scrolling down, the available plugins are shown in the Gnome Software Center. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359222] New: Amarok crashes when doing "Get tags from Musicbrainz".
https://bugs.kde.org/show_bug.cgi?id=359222 Bug ID: 359222 Summary: Amarok crashes when doing "Get tags from Musicbrainz". Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: tittiatc...@gmail.com Application: amarok (2.8.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-3-default x86_64 Distribution: "openSUSE Tumbleweed (20160208) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: >From the music collection, I added about 40 songs to a playlist. I selected all songs and then did a right-click and selected "Edit Track Details". In the newly opened window I selected "Get Tags from Musicbrainz". Amarok now displays a new window in which the found search results are displayed. Underneath one sees a progress bar. As soon as this progress bar reaches 50%, amarok will crash with the attached crashlog. I also tried the following options: 1) Selecting the first song from an album directly from the Local Collection. There is no crash, but strangely enough the tags are not updated. 2) Selecting the first song from the playlist. There is no crash, but strangely enough the tags are not updated despite choose the the entry found and selecting update tags. 3) Selecting the second song from the playlist (less than 20 entries). The search goes fine and seems to stop when the progress bar reaches 50%. Shortly after amarok crashes. 4) Selecting the second song from an album directly from the local Collection. The search goes fine and seems to stop when the progress bar reaches 50%. Shortly after amarok crashes. So the MusicBrainz lookup seems only to work for each first song of an album regardless if in the playlist or in the local collection. - Unusual behavior I noticed: The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4952ab7900 (LWP 21073))] Thread 15 (Thread 0x7f492a83c700 (LWP 21076)): #0 0x7f494f6fb22d in read () at /lib64/libc.so.6 #1 0x7f493c8fad91 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-8.0.so #2 0x7f4946aa5ede in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f4946aa68e0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f4946aa69a0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f4946ab45e6 in () at /usr/lib64/libpulse.so.0 #6 0x7f493c927cc8 in () at /usr/lib64/pulseaudio/libpulsecommon-8.0.so #7 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f490f4ee700 (LWP 21077)): #0 0x7f494e2df428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f491a8469da in () at /usr/lib64/libmysqld.so.18 #2 0x7f491a8315e7 in () at /usr/lib64/libmysqld.so.18 #3 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f490ecb8700 (LWP 21083)): #0 0x7f494e2df428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f494fdc6732 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f49523cbd7f in AbstractDirectoryWatcher::run() () at /usr/lib64/libamaroklib.so.1 #3 0x7f494b8c02f2 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f494b8c04de in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () at /usr/lib64/libthreadweaver.so.4 #5 0x7f494b8bfc0b in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #6 0x7f494fdc623c in () at /usr/lib64/libQtCore.so.4 #7 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f490e4b7700 (LWP 21084)): #0 0x7f49481044b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f49480c0899 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f49480c1193 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f49480c136c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f494fefa29e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f494feca411 in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f494feca725 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f494fdc3a59 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7f494feab4f3 in () at /usr/lib64/libQtCore.so.4 #9 0x7f494fdc623c in () at /usr/lib64/libQtCore.so.4 #10 0x7f494e2d94a4 in start_thread () at /lib
[amarok] [Bug 359222] Amarok crashes when doing "Get tags from Musicbrainz".
https://bugs.kde.org/show_bug.cgi?id=359222 Raymond Wooninck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |DUPLICATE --- Comment #2 from Raymond Wooninck --- Hi Miriam, I should have done a search first on bugs.kde.org. We got a bug report from one of our openSUSE users that amarok was crashing with musicbrainz. I tried to reproduce and when the crash happened, I reported it through drkonqi. Unfortunately drkonqi didn't found any duplicates. I checked the other bug report and it is indeed most likely a duplicate. Will close this one. *** This bug has been marked as a duplicate of bug 328359 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #45 from Raymond Wooninck --- *** Bug 359222 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 359468] New: Plasma-pk-updates does not respect the package flags for restart when set
https://bugs.kde.org/show_bug.cgi?id=359468
Bug ID: 359468
Summary: Plasma-pk-updates does not respect the package flags
for restart when set
Product: plasma-pk-updates
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: tittiatc...@gmail.com
It seems that plasma-pk-updates doesn't do anything to restart the system (or
notifying the user) if a package was updated that has the flag set that the
system needs to be restarted.
Checking the sources, it seems that this functionality was never implemented:
void PkUpdates::onRequireRestart(PackageKit::Transaction::Restart type, const
QString &packageID)
{
qCDebug(PLASMA_PK_UPDATES) << "RESTART" <<
PackageKit::Daemon::enumToString((int)type, "Restart")
<< "is required for package" << packageID;
}
It would make the applet complete when also this functionality could be offered
and on pair with the Gnome counterpart.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdesu] [Bug 359479] kdesu segfaults when clicking "cancel"
https://bugs.kde.org/show_bug.cgi?id=359479 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 359479] kdesu segfaults when clicking "cancel"
https://bugs.kde.org/show_bug.cgi?id=359479 --- Comment #1 from Raymond Wooninck --- I can confirm the same behavior based on git master. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters
https://bugs.kde.org/show_bug.cgi?id=366793 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #2 from Raymond Wooninck --- It seems as parsing the command line is the issue and that everything is seen as an option to konsole. Using konsole -e "sh -C "echo test"", then it works fine. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365265] Add Skanlite to the default set of applications of KDE Neon
https://bugs.kde.org/show_bug.cgi?id=365265 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #2 from Raymond Wooninck --- Package has been added to the build servers and should be available soon. Bug report can be closed as resolved. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 368986] New: Shouldn't the Julia back-end be an optional back-end ?
https://bugs.kde.org/show_bug.cgi?id=368986 Bug ID: 368986 Summary: Shouldn't the Julia back-end be an optional back-end ? Product: cantor Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: fil...@kde.org Reporter: tittiatc...@gmail.com CC: alexanderrie...@gmail.com Recently the Julia back-end was added to Cantor. It is good to see that new back-ends are being developed, but shouldn't this be an optional back-end ? At the moment during build, cmake is not even checking to see if Julia is actually installed and the julia development files are quite different from distro to distro. Looking at Neon, then it seems that the Julia files are not providing any development files, so that means that cantor can no longer be build as that it simply fails. Reproducible: Always Steps to Reproduce: 1. Build cantor on Neon 2. Build fails as that julia/julia.h can not be found 3. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 341762] When utilizing the Breeze theme for SDDM, it takes ages for SDDM to startup.
https://bugs.kde.org/show_bug.cgi?id=341762 --- Comment #10 from Raymond Wooninck --- Actually I haven't seen this for quite some time. Also with the changes that Plasma 5.8 will bring to the SDDM theme, the issue no longer occurs with me. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368835] MS Office icons have newlines in their filenames
https://bugs.kde.org/show_bug.cgi?id=368835 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #1 from Raymond Wooninck --- This should be fixed now, with my three commits. Please test. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Raymond Wooninck changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #2 from Raymond Wooninck --- Marco, I am very sorry, but with the latest git master (Yesterday evening), I still see exactly the same problem. If I lock the widgets, then after a reboot the panel is there and the systray is indeed present in the panel itself, however none of the entries there for network, volume, battery, notifications, etc have been started. Raymond -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Raymond Wooninck changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Raymond Wooninck --- With the last commit from Ivan, the systray is now functioning correctly. I am closing the bugreport. Thank you all. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters
https://bugs.kde.org/show_bug.cgi?id=366793 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #2 from Raymond Wooninck --- It seems as parsing the command line is the issue and that everything is seen as an option to konsole. Using konsole -e "sh -C "echo test"", then it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 344778] libkmahjongg installs lib twice
https://bugs.kde.org/show_bug.cgi?id=344778 --- Comment #3 from Raymond Wooninck --- Apologies, it seems that I never received the initial email indicating the bug. I had a quick look at the CMakeLists.txt and it seems that the second install line should be removed. I will do this later today. Apologies for this. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 344778] libkmahjongg installs lib twice
https://bugs.kde.org/show_bug.cgi?id=344778 --- Comment #4 from Raymond Wooninck --- Git commit e8a37284fca8e74986ce3a3ff979afd8e70484af by Raymond Wooninck. Committed on 05/01/2016 at 14:59. Pushed by rwooninck into branch 'master'. Remove the double install call for the library M +0-2CMakeLists.txt http://commits.kde.org/libkmahjongg/e8a37284fca8e74986ce3a3ff979afd8e70484af -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] New: kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Bug ID: 358216 Summary: kmail keeps running in the background after quitting the program Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tittiatc...@gmail.com I have noticed that kmail actually keeps running in the background after you try to close the program. Selecting "File -> Quit" makes the systray icon disappear, but the kmail process is still active in the background. Even with "Alt-Tab" window switcher, you can not find the kmail window anymore. One would expect that kmail is gone. When you now start a new kmail session, you suddenly get a crash reported from kmail indicating if you want to report a bug or to restart the program. The newly started kmail functions normally. This also applies to kontact !! Reproducible: Always Steps to Reproduce: 1. Start kmail or kontact. 2. Choose File -> Quit (kmail or kontact will close normally) 3. Open a konsole and check with ps if kmail or kontact are still there Actual Results: the kmail or kontact process is still active in the background, but can not be reached. Starting now a new kmail or kontact will cause a crash report for the old active process. Expected Results: The kmail or kontact process is normally closed and disappeared. Starting a new session afterwards should not generate a crash. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #2 from Raymond Wooninck --- (In reply to Daniel Vrátil from comment #1) > Could you try to get a backtrace to see what KMail is doing that's > preventing it from closing? Hi Dan, Sure. As long as you let me know what exactly you are looking for or how I should get the backtrace :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #3 from Raymond Wooninck --- Hi Dan, As requested, I attached gdb to the running process and then entered "t a a bt" to create the backtrace. The most interesting part would be this: Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec() () from /usr/lib64/libKF5CoreAddons.so.5 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 Looking at the source code of kmkernel.cpp (at line 1410) then it seems to try to run jobStatistics->exec() which somehow doesn't return. Hope this helps. Let me know if you need more info -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #4 from Raymond Wooninck --- A better one with also the debug info for libKF5CoreAddons. It could be that it is a change in coreaddons. Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec (this=this@entry=0x96df70) at /usr/src/debug/kcoreaddons-5.19.0git.20160109T125454~e8444d1/src/lib/jobs/kjob.cpp:199 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Raymond Wooninck changed: What|Removed |Added Severity|normal |major --- Comment #5 from Raymond Wooninck --- In a number of cases, this also causes a 100% cpu utilization of the remaining kmail process. When this happened, I attached gdb to this kmail process and exactly the same backtrace was generated. At this moment it would make kmail not really a good candidate for KDE Apps 16.04 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #1 from Raymond Wooninck --- I see exactly the same behavior on my system with Qt 5.6 and git master for Plasma, Frameworks and Apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] New: Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Bug ID: 360363 Summary: Systray doesn't initialize itself properly when Widgets are locked Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: tittiatc...@gmail.com The new systray in plasma-workspace does not initialize itself correctly when the widgets are locked. When the session is started and the widgets are locked, the systray itself is created, but there are no entries. Plasmoids like network monitor, notifications, plasma-pa, Powerdevil, etc are not appearing. For those people that uses Wireless connectivity, this means that the network also is not initialized as that the plasmoid itself is not started. However once the desktop session has started and I am starting e.g. Kmail, then the new email icon appears in the systray. As soon as I unlock the widgets and perform a logout/login, the systray is correctly initialized and all plasmoids are there. Reproducible: Always Steps to Reproduce: 1. Lock the widgets on the desktop/Panel 2. Logout 3. Login Actual Results: The systray is empty, not even the little triangle to show the hidden plasmoids is shown Expected Results: Systray to initialize correctly and show the entries for plasma-pa, notifications, network manager, battery, etc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Raymond Wooninck changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #2 from Raymond Wooninck --- Marco, I am very sorry, but with the latest git master (Yesterday evening), I still see exactly the same problem. If I lock the widgets, then after a reboot the panel is there and the systray is indeed present in the panel itself, however none of the entries there for network, volume, battery, notifications, etc have been started. Raymond -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360363] Systray doesn't initialize itself properly when Widgets are locked
https://bugs.kde.org/show_bug.cgi?id=360363 Raymond Wooninck changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Raymond Wooninck --- With the last commit from Ivan, the systray is now functioning correctly. I am closing the bugreport. Thank you all. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] New: Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 Bug ID: 359042 Summary: Plugins are displayed as "full" applications. Product: muon Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: tittiatc...@gmail.com CC: echidna...@kubuntu.org, sit...@kde.org I have digikam installed, which has a couple of plugins. When I check in the Gnome Software Center, then I see that these plugins are listed on the detailed page of digikam. In Discover however, these plugins are listed as "full" applications in the installed list and the plugins are not shown on the detailed page of digikam. I have added some screenshots to show the issue. In my view Discover should do the same as the GNome Software Center and list the plugins only on the detailed page of Digikam. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #1 from Raymond Wooninck --- Created attachment 97024 --> https://bugs.kde.org/attachment.cgi?id=97024&action=edit screenshot of the Installed Applications showing the digikam plugins (ImagePlugins) -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #2 from Raymond Wooninck --- Created attachment 97025 --> https://bugs.kde.org/attachment.cgi?id=97025&action=edit Screenshot of the detailed info screen of one of the digikam plugins. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #3 from Raymond Wooninck --- Created attachment 97026 --> https://bugs.kde.org/attachment.cgi?id=97026&action=edit Screenshot of the detailed info screen of digikam. Nowhere it is mentioned that Digikam has some plugins available -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #4 from Raymond Wooninck --- Created attachment 97027 --> https://bugs.kde.org/attachment.cgi?id=97027&action=edit This is how the Gnome software center displays the digikam details -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 359042] Plugins are displayed as "full" applications.
https://bugs.kde.org/show_bug.cgi?id=359042 --- Comment #5 from Raymond Wooninck --- Created attachment 97028 --> https://bugs.kde.org/attachment.cgi?id=97028&action=edit And scrolling down, the available plugins are shown in the Gnome Software Center. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359222] New: Amarok crashes when doing "Get tags from Musicbrainz".
https://bugs.kde.org/show_bug.cgi?id=359222 Bug ID: 359222 Summary: Amarok crashes when doing "Get tags from Musicbrainz". Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: tittiatc...@gmail.com Application: amarok (2.8.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-3-default x86_64 Distribution: "openSUSE Tumbleweed (20160208) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: >From the music collection, I added about 40 songs to a playlist. I selected all songs and then did a right-click and selected "Edit Track Details". In the newly opened window I selected "Get Tags from Musicbrainz". Amarok now displays a new window in which the found search results are displayed. Underneath one sees a progress bar. As soon as this progress bar reaches 50%, amarok will crash with the attached crashlog. I also tried the following options: 1) Selecting the first song from an album directly from the Local Collection. There is no crash, but strangely enough the tags are not updated. 2) Selecting the first song from the playlist. There is no crash, but strangely enough the tags are not updated despite choose the the entry found and selecting update tags. 3) Selecting the second song from the playlist (less than 20 entries). The search goes fine and seems to stop when the progress bar reaches 50%. Shortly after amarok crashes. 4) Selecting the second song from an album directly from the local Collection. The search goes fine and seems to stop when the progress bar reaches 50%. Shortly after amarok crashes. So the MusicBrainz lookup seems only to work for each first song of an album regardless if in the playlist or in the local collection. - Unusual behavior I noticed: The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4952ab7900 (LWP 21073))] Thread 15 (Thread 0x7f492a83c700 (LWP 21076)): #0 0x7f494f6fb22d in read () at /lib64/libc.so.6 #1 0x7f493c8fad91 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-8.0.so #2 0x7f4946aa5ede in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7f4946aa68e0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f4946aa69a0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f4946ab45e6 in () at /usr/lib64/libpulse.so.0 #6 0x7f493c927cc8 in () at /usr/lib64/pulseaudio/libpulsecommon-8.0.so #7 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f490f4ee700 (LWP 21077)): #0 0x7f494e2df428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f491a8469da in () at /usr/lib64/libmysqld.so.18 #2 0x7f491a8315e7 in () at /usr/lib64/libmysqld.so.18 #3 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f490ecb8700 (LWP 21083)): #0 0x7f494e2df428 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f494fdc6732 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f49523cbd7f in AbstractDirectoryWatcher::run() () at /usr/lib64/libamaroklib.so.1 #3 0x7f494b8c02f2 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f494b8c04de in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () at /usr/lib64/libthreadweaver.so.4 #5 0x7f494b8bfc0b in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #6 0x7f494fdc623c in () at /usr/lib64/libQtCore.so.4 #7 0x7f494e2d94a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f494f707bdd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f490e4b7700 (LWP 21084)): #0 0x7f49481044b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f49480c0899 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f49480c1193 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f49480c136c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f494fefa29e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f494feca411 in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f494feca725 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f494fdc3a59 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7f494feab4f3 in () at /usr/lib64/libQtCore.so.4 #9 0x7f494fdc623c in () at /usr/lib64/libQtCore.so.4 #10 0x7f494e2d94a4 in start_thread () at /lib
[amarok] [Bug 359222] Amarok crashes when doing "Get tags from Musicbrainz".
https://bugs.kde.org/show_bug.cgi?id=359222 Raymond Wooninck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |DUPLICATE --- Comment #2 from Raymond Wooninck --- Hi Miriam, I should have done a search first on bugs.kde.org. We got a bug report from one of our openSUSE users that amarok was crashing with musicbrainz. I tried to reproduce and when the crash happened, I reported it through drkonqi. Unfortunately drkonqi didn't found any duplicates. I checked the other bug report and it is indeed most likely a duplicate. Will close this one. *** This bug has been marked as a duplicate of bug 328359 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #45 from Raymond Wooninck --- *** Bug 359222 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 359468] New: Plasma-pk-updates does not respect the package flags for restart when set
https://bugs.kde.org/show_bug.cgi?id=359468
Bug ID: 359468
Summary: Plasma-pk-updates does not respect the package flags
for restart when set
Product: plasma-pk-updates
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: tittiatc...@gmail.com
It seems that plasma-pk-updates doesn't do anything to restart the system (or
notifying the user) if a package was updated that has the flag set that the
system needs to be restarted.
Checking the sources, it seems that this functionality was never implemented:
void PkUpdates::onRequireRestart(PackageKit::Transaction::Restart type, const
QString &packageID)
{
qCDebug(PLASMA_PK_UPDATES) << "RESTART" <<
PackageKit::Daemon::enumToString((int)type, "Restart")
<< "is required for package" << packageID;
}
It would make the applet complete when also this functionality could be offered
and on pair with the Gnome counterpart.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdesu] [Bug 359479] kdesu segfaults when clicking "cancel"
https://bugs.kde.org/show_bug.cgi?id=359479 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 359479] kdesu segfaults when clicking "cancel"
https://bugs.kde.org/show_bug.cgi?id=359479 --- Comment #1 from Raymond Wooninck --- I can confirm the same behavior based on git master. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #3 from Raymond Wooninck --- If everyone would have a proper look, then it would have been visible that the KDEPIM package itself was not published yet. Unfortunately KDE Applications finds itself in a slow building state, so it will take time to get this completely published. This is actually the risk of utilizing a development repository. KDE Applications would have come to Tumbleweed and Leap 42.1 as soon as everything would have been build properly. At this moment, I would suggest to revert back to the versions that are offered in Tumbleweed and/or Leap:Updates -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 --- Comment #4 from Raymond Wooninck --- Please close this bug as invalid and this one should have been reported at bugzilla.opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365265] Add Skanlite to the default set of applications of KDE Neon
https://bugs.kde.org/show_bug.cgi?id=365265 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #2 from Raymond Wooninck --- Package has been added to the build servers and should be available soon. Bug report can be closed as resolved. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 368986] New: Shouldn't the Julia back-end be an optional back-end ?
https://bugs.kde.org/show_bug.cgi?id=368986 Bug ID: 368986 Summary: Shouldn't the Julia back-end be an optional back-end ? Product: cantor Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: fil...@kde.org Reporter: tittiatc...@gmail.com CC: alexanderrie...@gmail.com Recently the Julia back-end was added to Cantor. It is good to see that new back-ends are being developed, but shouldn't this be an optional back-end ? At the moment during build, cmake is not even checking to see if Julia is actually installed and the julia development files are quite different from distro to distro. Looking at Neon, then it seems that the Julia files are not providing any development files, so that means that cantor can no longer be build as that it simply fails. Reproducible: Always Steps to Reproduce: 1. Build cantor on Neon 2. Build fails as that julia/julia.h can not be found 3. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 341762] When utilizing the Breeze theme for SDDM, it takes ages for SDDM to startup.
https://bugs.kde.org/show_bug.cgi?id=341762 --- Comment #10 from Raymond Wooninck --- Actually I haven't seen this for quite some time. Also with the changes that Plasma 5.8 will bring to the SDDM theme, the issue no longer occurs with me. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368835] MS Office icons have newlines in their filenames
https://bugs.kde.org/show_bug.cgi?id=368835 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #1 from Raymond Wooninck --- This should be fixed now, with my three commits. Please test. -- You are receiving this mail because: You are watching all bug changes.
