[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374 Harald Sitter changed: What|Removed |Added Version|unspecified |5.8.0 Assignee|neon-b...@kde.org |plasma-de...@kde.org Product|neon|Breeze Component|general |GRUB -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374
Harald Sitter changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Harald Sitter ---
If it was the progressbar I think we'd see more reports of this. I have however
seen this temporarily at some point, since it went away on its own after some
updates I am rather content in saying that this is either a bug in the grub
config or grub itself.
Please attach the following files to the bug report
- /boot/grub/grub.cfg
- /boot/grub/grubenv
- /etc/default/grub
Additionally zip up and attach all files in /etc/grub.d (alternatively attach
the files individually but I expect there to be a bunch of them).
Once you are sure you've attached all files please try the following.
On a terminal run `sudo update-grub`, then reboot and see if that fixed the
problem.
If it did not fix the problem delete the following directories and files:
- /boot/grub/themes/breeze/progress_bar/
- /boot/grub/themes/breeze/terminal/
- /boot/grub/themes/breeze/oxygenmono10.pf2
and again `sudo update-grub`, then reboot and see if that fixed the problem.
If it did not fix the problem edit the file /boot/grub/themes/breeze/theme.txt
and find the bit where it says
> # Show the boot menu
> + boot_menu {
below that insert a new line with this content:
> scrollbar = false
save the file and again `sudo update-grub`, then reboot and see if that fixed
the problem.
If it did not fix the problem edit the same file again and remove the line
again. Towards the end of the file you'll find two "progress_bar {}" blocks.
Remove the bottom one, save the file and again `sudo update-grub`, then reboot
and see if that fixed the problem.
If it did not fix the problem edit the same file again and remove the other
"progress_bar {}" block as well, save, `sudo update-grub`, reboot and see if
that fixed the problem.
If none of the above steps fixed the problem you can restore your theme to the
defaults with the command `sudo apt install --reinstall grub-theme-breeze` and
I'll have to take a closer look at your config.
If one of the steps fixed the problem, please add a comment here. Additionally
restore the default with the command `sudo apt install --reinstall
grub-theme-breeze` followed by `sudo update-grub` and reboot to see if the
problem remains fixed. Please add a comment about this as well.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 367843] Include 54b819679cd39e997cc9319deaf432c37667ae6f in QtWayland
https://bugs.kde.org/show_bug.cgi?id=367843 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Harald Sitter --- https://packaging.neon.kde.org/qt/qtwayland.git/commit/?h=Neon/release&id=7958b36ecd6a7b30f9e5842249d50e9682d49429 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371276] Only black screen with breeze plymouth theme in plasma 5.8.2
https://bugs.kde.org/show_bug.cgi?id=371276 --- Comment #2 from Harald Sitter --- If it works on neon it's hardly a problem with the theme though. Not quite sure what to do with this. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371276] Only black screen with breeze plymouth theme in plasma 5.8.2
https://bugs.kde.org/show_bug.cgi?id=371276 Harald Sitter changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Harald Sitter --- Right, so, Luca just checked on suse and the theme renders fine with the x11 renderer and runs through its test sequence without theme related problems. Meaning the theme itself is working. This leaves us with a number of options on why it breaks: - the distributions' dracut doesn't package all the assets of the theme into the initrd (images, font files maybe) - the script itself fails to parse when run from initrd, which would be super weird considering it is parsing just fine when run through the x11 renderer (at least on opensuse). So. Y'all want to take this to your distributions for investigation. Best thing would be to find out how to switch plymouth into debug mode for your distribution (usually kernel cmdline plymouth:debug) and then have a look at the logs for any obvious errors regarding the breeze theme. Additionally manually unpacking the initrd and checking that the theme tree in the initrd is the same as the tree on-disk would be useful there. When in doubt about the parsing bit: install the plymouth x11 renderer and run sudo test/plytest.sh in the breeze-plymouth source tree. This should run a fairly comprehensive ability test from offline-updates over fsck to password prompt. Most importantly it will touch most code paths to detect parsing errors. Closing this report as it's not a theme problem apparently. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 356071] fail of dragon player / firefox/google chrome with sometime freeze
https://bugs.kde.org/show_bug.cgi?id=356071 Harald Sitter changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- Seeing as multiple somewhat unrelated applications crashed for you this might in fact either be a larger problem with your installation, or a hardware problem (bad memory?) or crashes brought on by the installation of updates. As for the crash at hand. It in fact crashed inside a thing called libfaad. Alas, since you did not have debug symbols installed it's hard to say why or how. Please have a look at [1] on how to get more useful crash information for your distribution, so the next time there'll be more information. For the bug at hand we can't really do anything unless you can actually reproduce this reliably. [1] https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 356081] Dragon player crashes when trying to play a mp4 file from a smb share
https://bugs.kde.org/show_bug.cgi?id=356081 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Harald Sitter --- >From the looks of it during the normal application exit something inside libx11 hit an invalid pointer and that caused the crash. Which Phonon backend were you using at the time? Can you reproduce this crash? Fetching additional debug information using a program called valgrind [1] would likely help finding out why exactly it crashes. If you cannot reproduce the crash I don't think we can do much about it though as the information at hand doesn't really tell us where the crash was caused. Also, please note that Kubuntu 15.04 is going to be unsupported in 1-2 months. It might well be that 15.10 already resolves the issue. [1] https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 364911] Distortion and volume issues when using phonon-vlc backend
https://bugs.kde.org/show_bug.cgi?id=364911 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Harald Sitter --- the volume difference comes from the sounds not actually being sounds as per stream-category remark in https://community.kde.org/Phonon/Releases/VLC/0.9.0 which is fixed for vlc3 https://quickgit.kde.org/?p=phonon-vlc.git&a=commit&h=001c117c2aa543015140f83184d6fb06728a385f the overall sounds quality issues you'll want to report against vlc directly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364897] Can't logout/reboot/shutdown after Qt upgrad
https://bugs.kde.org/show_bug.cgi?id=364897 --- Comment #3 from Harald Sitter --- Yes. I don't see those happening in distributions in any feasible time frame though. I also have the feeling that last time I discussed that with someone raised reasonable concerns against them, alas, I can't remember what they were ^^. Supposedly it was that when the user needs to be informed about something or actively needs to take action (configuration changes, license aggrement, whatever) it makes the entire affair fairly faffy. Also if things break they break hard if reliable rollbacks aren't and option, and TBH the only reliable rollback is a brfs snapshot rollback. Anyway, we need some solution to the problem at hand, in addition to that we could poll distros for thoughts on out-of-session upgrades. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364977] New: device notifier settings should include removable devices kcm
https://bugs.kde.org/show_bug.cgi?id=364977 Bug ID: 364977 Summary: device notifier settings should include removable devices kcm Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: sit...@kde.org the device notifier applet (except for dolphin) is the users primary interaction point with mountable removable devices. as such I was looking in the device notifier for a way to use automount. alas, no such luck. I think the device notifier settings should also include the removable devices kcm for greater discoverability. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365066] New: plasma5.7 + qt5.7 wonky wallpaper init
https://bugs.kde.org/show_bug.cgi?id=365066 Bug ID: 365066 Summary: plasma5.7 + qt5.7 wonky wallpaper init Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: sit...@kde.org CC: plasma-b...@kde.org With plasma 5.7 and qt 5.7 I see weird init problems where only one of the screens gets a background (containment?). So, it has no image, nor a context menu, nor anything. It does however have a panel... I'll attach a screenshot exhibiting the problem. This is with kscreen having been set to render DVI-I-1 right hand side as primary and HDMI-0 left hand side as !primary. I'll also attach an xession-errors from a new user which upon first login had the same issue. Second login seemed to initialize the wallpaper fine though, so this might be either racey or only first-config behavior. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365066] plasma5.7 + qt5.7 wonky wallpaper init
https://bugs.kde.org/show_bug.cgi?id=365066 --- Comment #1 from Harald Sitter --- Created attachment 99843 --> https://bugs.kde.org/attachment.cgi?id=99843&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365066] plasma5.7 + qt5.7 wonky wallpaper init
https://bugs.kde.org/show_bug.cgi?id=365066 --- Comment #2 from Harald Sitter --- Created attachment 99844 --> https://bugs.kde.org/attachment.cgi?id=99844&action=edit xsession errors (full qt logging enabled, so fairly lengthy) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365106] GUI for Ctrl + Alt + Backspace setting doesn't work
https://bugs.kde.org/show_bug.cgi?id=365106 Harald Sitter changed: What|Removed |Added Component|general |kcm_keyboard Assignee|plasma-b...@kde.org |ary...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365106] GUI for Ctrl + Alt + Backspace setting doesn't work
https://bugs.kde.org/show_bug.cgi?id=365106 Harald Sitter changed: What|Removed |Added Assignee|neon-b...@kde.org |plasma-b...@kde.org Component|general |general Product|neon|systemsettings --- Comment #1 from Harald Sitter --- Works just fine for me. Moving to keyboard kcm. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365121] Task Manager doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=365121 Harald Sitter changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Harald Sitter --- you always should do dist-upgrades or use plasma discover. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365150] Running Discover for the first time - see not too detailed message about Appstream
https://bugs.kde.org/show_bug.cgi?id=365150 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365128] no password prompt at boot (luks encrypted disk)
https://bugs.kde.org/show_bug.cgi?id=365128 Harald Sitter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 365169 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added CC||bo...@web.de --- Comment #1 from Harald Sitter --- *** Bug 365128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added Component|general |Plymouth Product|neon|Breeze Assignee|neon-b...@kde.org |plasma-de...@kde.org Version|unspecified |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.7.1 Latest Commit||http://commits.kde.org/bree ||ze-plymouth/a5909e1cd59f592 ||54898421df2eb66d4fe10e393 Resolution|--- |FIXED --- Comment #2 from Harald Sitter --- Git commit a5909e1cd59f59254898421df2eb66d4fe10e393 by Harald Sitter. Committed on 07/07/2016 at 08:24. Pushed by sitter into branch 'Plasma/5.7'. fix spinner height and y to resolve broken layout chain everything lays out relative to the spinner/logo, when changing to in-cpu rotation the spinner code was not correctly updated to retain working y and height calculations after changes to internal data structures. this resulted in all objects layed out relative to the spinner to not be drawn as their position was NaN. plymouth could really benefit from openqa tests :/ FIXED-IN: 5.7.1 M +2-2breeze/breeze.script.cmake http://commits.kde.org/breeze-plymouth/a5909e1cd59f59254898421df2eb66d4fe10e393 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365195] PureRef app font became unreadable after update to Neon 5.7
https://bugs.kde.org/show_bug.cgi?id=365195 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Harald Sitter --- Get in touch with PureRef. It occurs to me they have bad path isolation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365226] Unable to change file type associations on KDE Neon 5.7 User Edition
https://bugs.kde.org/show_bug.cgi?id=365226 Harald Sitter changed: What|Removed |Added Component|stable packaging|kcm_filetypes Product|neon|systemsettings Assignee|neon-b...@kde.org |fa...@kde.org Version|unspecified |5.7.0 --- Comment #2 from Harald Sitter --- Moving to relevant KCM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365226] Unable to change file type associations on KDE Neon 5.7 User Edition
https://bugs.kde.org/show_bug.cgi?id=365226 --- Comment #3 from Harald Sitter --- *** Bug 365224 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365224] KDE Neon 5.7 User Edition won't let me set the default application for file types
https://bugs.kde.org/show_bug.cgi?id=365224 Harald Sitter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 365226 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365213] Installed/reinstalled cron but not found in system settings
https://bugs.kde.org/show_bug.cgi?id=365213 --- Comment #2 from Harald Sitter --- Created attachment 99944 --> https://bugs.kde.org/attachment.cgi?id=99944&action=edit picture of the thing working The software is called 'kcron'. 'cron' is the actual cron underlying kcron. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365212] Neon 5.7 - Shutdown fails - hangs
https://bugs.kde.org/show_bug.cgi?id=365212 --- Comment #1 from Harald Sitter --- (In reply to pmb from comment #0) > I logged into the installed version, downloaded the updates, and clicked > 'Shutdown'. The same action happened again. The logo continued to spin. I > waited 5 minutes and manually powered down from an electrical switch. Ok, so, this is fairly important. Did you actually wait >= 5 minutes or did you wait for what you perceived to be 5 minutes? If you actually waited for 5 minutes -> https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 -> you'll want to file a bug report with Ubuntu since this isn't a neon issue. If you did not wait for actually 5 minutes -> do it please. - If it does not complete within 5 minutes refer to the debugging instructions above. - If it does, also refer to the debugging instructions above (the ones for eventual shutdown obviously). I am reasonably certain what happens is that an application crashed on exit and is holding up session shutdown though. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 365234] New: crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365234 Bug ID: 365234 Summary: crash on quick search Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sit...@kde.org Application: plasma-discover (5.7.0) Qt Version: 5.7.0 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-28-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: searched for 'discover' ctrl+a started typing something else crash All of this happend very quickly and shortly after starting discover. Seems fairly reproducible here. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70c4f298c0 (LWP 17315))] Thread 8 (Thread 0x7f709affd700 (LWP 17346)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f7098c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709affcc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f70cf535044 in QThread::exec (this=this@entry=0x3440920) at thread/qthread.cpp:507 #6 0x7f70d1b02ac6 in QQuickPixmapReader::run (this=0x3440920) at util/qquickpixmapcache.cpp:823 #7 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3440920) at thread/qthread_unix.cpp:344 #8 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f709bfff700 (LWP 17327)): #0 0x7f70cf7634a8 in QTimerInfoList::repairTimersIfNeeded (this=) at kernel/qtimerinfo_unix.cpp:167 #1 0x7f70cf763503 in QTimerInfoList::timerWait (this=0x7f7094002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:389 #2 0x7f70cf764b5c in timerSourcePrepareHelper (timeout=0x7f709bffeb34, src=) at kernel/qeventdispatcher_glib.cpp:132 #3 idleTimerSourcePrepare (source=, timeout=0x7f709bffeb34) at kernel/qeventdispatcher_glib.cpp:212 #4 0x7f70ca88592d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f70ca8862cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709bffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7f70cf535044 in QThread::exec (this=) at thread/qthread.cpp:507 #10 0x7f70cf539c28 in QThreadPrivate::start (arg=0x306bc10) at thread/qthread_unix.cpp:344 #11 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f70a1bef700 (LWP 17326)): #0 0x7f70cc5053a0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f70cf53aadb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3074090) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x3064b68, mutex=mutex@entry=0x3064b60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f70d1b71f5d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x3064b58) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f70d1b72835 in QSGRenderThread::run (this=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3064ae0) at thread/qthread_unix.cpp:344 #7 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f70abc26700 (LWP 17319)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f
[kde] [Bug 365235] New: crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365235 Bug ID: 365235 Summary: crash on quick search Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sit...@kde.org Application: plasma-discover (5.7.0) Qt Version: 5.7.0 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-28-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: searched for 'discover' ctrl+a started typing something else crash All of this happend very quickly and shortly after starting discover. Seems fairly reproducible here. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70c4f298c0 (LWP 17315))] Thread 8 (Thread 0x7f709affd700 (LWP 17346)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f7098c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709affcc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f70cf535044 in QThread::exec (this=this@entry=0x3440920) at thread/qthread.cpp:507 #6 0x7f70d1b02ac6 in QQuickPixmapReader::run (this=0x3440920) at util/qquickpixmapcache.cpp:823 #7 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3440920) at thread/qthread_unix.cpp:344 #8 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f709bfff700 (LWP 17327)): #0 0x7f70cf7634a8 in QTimerInfoList::repairTimersIfNeeded (this=) at kernel/qtimerinfo_unix.cpp:167 #1 0x7f70cf763503 in QTimerInfoList::timerWait (this=0x7f7094002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:389 #2 0x7f70cf764b5c in timerSourcePrepareHelper (timeout=0x7f709bffeb34, src=) at kernel/qeventdispatcher_glib.cpp:132 #3 idleTimerSourcePrepare (source=, timeout=0x7f709bffeb34) at kernel/qeventdispatcher_glib.cpp:212 #4 0x7f70ca88592d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f70ca8862cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709bffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7f70cf535044 in QThread::exec (this=) at thread/qthread.cpp:507 #10 0x7f70cf539c28 in QThreadPrivate::start (arg=0x306bc10) at thread/qthread_unix.cpp:344 #11 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f70a1bef700 (LWP 17326)): #0 0x7f70cc5053a0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f70cf53aadb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3074090) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x3064b68, mutex=mutex@entry=0x3064b60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f70d1b71f5d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x3064b58) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f70d1b72835 in QSGRenderThread::run (this=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3064ae0) at thread/qthread_unix.cpp:344 #7 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f70abc26700 (LWP 17319)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f
[kde] [Bug 365233] New: crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365233 Bug ID: 365233 Summary: crash on quick search Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sit...@kde.org Application: plasma-discover (5.7.0) Qt Version: 5.7.0 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-28-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: searched for 'discover' ctrl+a started typing something else crash All of this happend very quickly and shortly after starting discover. Seems fairly reproducible here. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70c4f298c0 (LWP 17315))] Thread 8 (Thread 0x7f709affd700 (LWP 17346)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f7098c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709affcc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f70cf535044 in QThread::exec (this=this@entry=0x3440920) at thread/qthread.cpp:507 #6 0x7f70d1b02ac6 in QQuickPixmapReader::run (this=0x3440920) at util/qquickpixmapcache.cpp:823 #7 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3440920) at thread/qthread_unix.cpp:344 #8 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f709bfff700 (LWP 17327)): #0 0x7f70cf7634a8 in QTimerInfoList::repairTimersIfNeeded (this=) at kernel/qtimerinfo_unix.cpp:167 #1 0x7f70cf763503 in QTimerInfoList::timerWait (this=0x7f7094002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:389 #2 0x7f70cf764b5c in timerSourcePrepareHelper (timeout=0x7f709bffeb34, src=) at kernel/qeventdispatcher_glib.cpp:132 #3 idleTimerSourcePrepare (source=, timeout=0x7f709bffeb34) at kernel/qeventdispatcher_glib.cpp:212 #4 0x7f70ca88592d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f70ca8862cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f709bffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7f70cf535044 in QThread::exec (this=) at thread/qthread.cpp:507 #10 0x7f70cf539c28 in QThreadPrivate::start (arg=0x306bc10) at thread/qthread_unix.cpp:344 #11 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f70a1bef700 (LWP 17326)): #0 0x7f70cc5053a0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f70cf53aadb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3074090) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x3064b68, mutex=mutex@entry=0x3064b60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f70d1b71f5d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x3064b58) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f70d1b72835 in QSGRenderThread::run (this=0x3064ae0) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f70cf539c28 in QThreadPrivate::start (arg=0x3064ae0) at thread/qthread_unix.cpp:344 #7 0x7f70cc4ff6fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f70ceb3db5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f70abc26700 (LWP 17319)): #0 0x7f70ceb31e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f70ca88639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f70ca8864ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f70cf76530b in QEventDispatcherGlib::processEvents (this=0x7f70a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f70cf70fd9a in QEventLoop::exec (this=this@entry=0x7f
[Discover] [Bug 365235] crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365235 Harald Sitter changed: What|Removed |Added Component|general |discover Product|kde |Discover Assignee|unassigned-b...@kde.org |aleix...@kde.org Version|unspecified |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365236] New: add installation support for native formats
https://bugs.kde.org/show_bug.cgi?id=365236 Bug ID: 365236 Summary: add installation support for native formats Product: Discover Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org Currently discover can not handle native distribution archive formats such as .deb or .rpm. This means that unless a distribution installs a secondary tool users can not install google-chrome or steam as they ship a bootstrap harness via native formats. Would be handy to be able to install that sort of stuff with discover. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365213] Installed/reinstalled cron but not found in system settings
https://bugs.kde.org/show_bug.cgi?id=365213 --- Comment #4 from Harald Sitter --- So this seems to be working fine, you were just looking for the wrong entry in systemsettings? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 365233] crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365233 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 365235 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365235] crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365235 --- Comment #1 from Harald Sitter --- *** Bug 365233 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365235] crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365235 --- Comment #2 from Harald Sitter --- *** Bug 365234 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 365234] crash on quick search
https://bugs.kde.org/show_bug.cgi?id=365234 Harald Sitter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 365235 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365150] Running Discover for the first time - see not too detailed message about Appstream
https://bugs.kde.org/show_bug.cgi?id=365150 --- Comment #3 from Harald Sitter --- the error message doesnt say that, nor does it provide info fo the distro to help -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365352] Virtual desktops are not remembered when switching activities
https://bugs.kde.org/show_bug.cgi?id=365352 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Harald Sitter --- neon dev stable is not equal to what that gentoo system is. I'd rather have you reopen the other bug for investigation as you are effectively on kf5 master and plasma 5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 365611] New: crash on every cold boot
https://bugs.kde.org/show_bug.cgi?id=365611 Bug ID: 365611 Summary: crash on every cold boot Product: ksplash Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: sit...@kde.org every cold boot login kplashqml crashes inside qt. debug output suggests KQuickAddons involvement though. overall, I am rather thinking this might have to do with kscreen shuffling my two screens about Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 365611] crash on every cold boot
https://bugs.kde.org/show_bug.cgi?id=365611 --- Comment #1 from Harald Sitter --- dump PID: 2160 (ksplashqml) UID: 1000 (me) GID: 1000 (me) Signal: 11 (SEGV) Timestamp: Mit 2016-07-13 15:39:37 CEST (7min ago) Command Line: ksplashqml org.kde.breezedark.desktop --pid Executable: /usr/bin/ksplashqml Control Group: / Slice: -.slice Boot ID: 2ca6c6d275ee4d9c8403a13e3bf4 Machine ID: a4c8250cb9ad40cd8cbc60c5e8e9967c Hostname: smith Coredump: /var/lib/systemd/coredump/core.ksplashqml.1000.2ca6c6d275ee4d9c8403a13e3bf4.2160.1468417177.xz Message: Process 2160 (ksplashqml) of user 1000 dumped core. Stack trace of thread 2195: #0 0x7f2d54c59594 n/a (libnvidia-glcore.so.367.27) #1 0x7f2d54c59e58 n/a (libnvidia-glcore.so.367.27) #2 0x7f2d548b0370 n/a (libnvidia-glcore.so.367.27) #3 0x7f2d548b2272 n/a (libnvidia-glcore.so.367.27) #4 0x7f2d6df653cf _ZN16QOpenGLFunctions12glBufferDataEjlPKvj (libQt5Quick.so.5) #5 0x7f2d6df67119 _ZN16QSGBatchRenderer8Renderer11uploadBatchEPNS_5BatchE (libQt5Quick.so.5) #6 0x7f2d6df7171e _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #7 0x7f2d6df7d3cf _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #8 0x7f2d6df7da8b _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #9 0x7f2d6df8d65e _ZN16QSGRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #10 0x7f2d6dfd6d19 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #11 0x7f2d6dfa809a _ZN15QSGRenderThread13syncAndRenderEv (libQt5Quick.so.5) #12 0x7f2d6dfac70c _ZN15QSGRenderThread3runEv (libQt5Quick.so.5) #13 0x7f2d6d046c28 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5) #14 0x7f2d6b4a76fa start_thread (libpthread.so.0) #15 0x7f2d6c953b5d __clone (libc.so.6) Stack trace of thread 2171: #0 0x7f2d6b4b02ad __lll_lock_wait (libpthread.so.0) #1 0x7f2d6b4a9e82 pthread_mutex_lock (libpthread.so.0) #2 0x7f2d55c4677c n/a (libGLX_nvidia.so.0) #3 0x7f2d54cf1a5e n/a (libnvidia-glcore.so.367.27) #4 0x7f2d54d366ea n/a (libnvidia-glcore.so.367.27) #5 0x7f2d54dd0bfb n/a (libnvidia-glcore.so.367.27) #6 0x7f2d54cc78e4 n/a (libnvidia-glcore.so.367.27) #7 0x7f2d54cc799e n/a (libnvidia-glcore.so.367.27) #8 0x7f2d54c66893 n/a (libnvidia-glcore.so.367.27) #9 0x7f2d548bb43b n/a (libnvidia-glcore.so.367.27) #10 0x7f2d6df6beca _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5) #11 0x7f2d6df71774 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5) #12 0x7f2d6df7d3cf _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5) #13 0x7f2d6df7da8b _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5) #14 0x7f2d6df8d65e _ZN16QSGRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5) #15 0x7f2d6dfd6d19 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSize (libQt5Quick.so.5) #16 0x7f2d6dfa809a _ZN15QSGRenderThread13syncAndRenderEv (libQt5Quick.so.5) #17 0x7f2d6dfac70c _ZN15QSGRenderThread3runEv (libQt5Quick.so.5) #18 0x7f2d6d046c28 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5) #19 0x7f2d6b4a76fa start_thread (libpthread.so.0) #20 0x7f2d6c953b5d __clone (libc.so.6) Stack trace of thread 2161: #0 0x7f2d6c947e8d __poll (libc.so.6) #1 0x7f2d6311dc62 n/a (libxcb.so.1) #2 0x7f2d6311f8d7 xcb_wait_for_event (libxcb.so.1) #3 0x7f2d61e5da39 _ZN15QXcbEventReader3runEv (libQt5XcbQpa.so.5) #4 0x7f2d6d046c28 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5) #5 0x7f2d6b4a76fa start_thread (libpthread.so.0) #6 0x7f2d6c953b5d __clone (libc.so.6) Stack trace of thread 2163: #0 0x7f2d6c947e8d __poll (libc.so.6) #1 0x7f2d697eb39c n/a (libglib-2.0.so.0) #2 0x7f2d697eb4ac g_main_context_iteration (libglib-2.0.so.0) #3 0x7f2d6d27230b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7f2d6d21cd9a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #
[ksplash] [Bug 365611] crash on every cold boot
https://bugs.kde.org/show_bug.cgi?id=365611 Harald Sitter changed: What|Removed |Added Version|unspecified |5.7.1 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 365611] crash on every cold boot
https://bugs.kde.org/show_bug.cgi?id=365611 --- Comment #2 from Harald Sitter --- Created attachment 100065 --> https://bugs.kde.org/attachment.cgi?id=100065&action=edit debug output -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365647] can't input Japanese with fcitx-mozc IME on Konsole and Kwrite
https://bugs.kde.org/show_bug.cgi?id=365647 Harald Sitter changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- see my comment @ https://forum.kde.org/viewtopic.php?f=309&t=134856#p360806 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365614] KDE Neon 5.7 gets stuck on the login screen after entering password
https://bugs.kde.org/show_bug.cgi?id=365614 --- Comment #1 from Harald Sitter --- Not sure what we can do about this. Best check if it is an issue in Kubuntu and if so report the bug on launchpad. If the system itself actually gets stuck this would be a driver/kernel issue supposedly. Neither of which is managed by us. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 364549] Cannot boot into lvm encrypted system after kernel upgrade
https://bugs.kde.org/show_bug.cgi?id=364549 --- Comment #2 from Harald Sitter --- attach /var/log/apt/* and /var/log/dpkg/* to the bug report -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 363898] Konversation is lacking AppStream data
https://bugs.kde.org/show_bug.cgi?id=363898 Harald Sitter changed: What|Removed |Added Latest Commit|http://commits.kde.org/konv |http://commits.kde.org/konv |ersation/2d6799710641778d74 |ersation/4229311a6a45b039f9 |a728f1f15c272978e143f4 |7801679b1c220e53df431b --- Comment #3 from Harald Sitter --- Git commit 4229311a6a45b039f97801679b1c220e53df431b by Harald Sitter. Committed on 21/07/2016 at 13:02. Pushed by sitter into branch '1.6'. add appdata for konversation create org.kde.konversation.appdata.xml with data from konversation.json on kde.org update CMakeLists.txt REVIEW:128094 REVIEW:128489 # Conflicts: #data/CMakeLists.txt M +1-0data/CMakeLists.txt A +42 -0data/org.kde.konversation.appdata.xml http://commits.kde.org/konversation/4229311a6a45b039f97801679b1c220e53df431b -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 366158] Switching sections inside Info module results with small lag when rendering their content
https://bugs.kde.org/show_bug.cgi?id=366158 Harald Sitter changed: What|Removed |Added Ever confirmed|0 |1 CC||sit...@kde.org Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Harald Sitter --- You can actually keep clicking the about-distro module to reload it and observe this happening. Why there is such a noticable delay in loading is a bit peculiar. Assuming it's not just bad code that takes longer than necessary we probably should simply setHidden(true) everything and setHidden(false) when loading is done. Alas, that simply changes the issue from "random text" to "noticable time empty" so it's probably more of a workaround. Also I'd say this applies to some KCMs but not all of them. e.g. Memory looks fine. Energy Information however also has the weird delay going on. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 366158] Switching sections inside Info module results with small lag when rendering their content
https://bugs.kde.org/show_bug.cgi?id=366158 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kinf ||ocenter/8600dff7216c8f983ce ||991ac2e856b3aa7df28b7 --- Comment #4 from Harald Sitter --- Git commit 8600dff7216c8f983ce991ac2e856b3aa7df28b7 by Harald Sitter. Committed on 27/07/2016 at 13:25. Pushed by sitter into branch 'Plasma/5.7'. always load about-distro in ctor Summary: otherwise get a noticable delay during which we show dummy data. since we only access on-disk content and only very little of it loading via ctor should have next to no impact. Reviewers: cfeck, sebas Reviewed By: sebas Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2300 M +6-0Modules/about-distro/src/Module.cpp http://commits.kde.org/kinfocenter/8600dff7216c8f983ce991ac2e856b3aa7df28b7 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365236] add installation support for native formats
https://bugs.kde.org/show_bug.cgi?id=365236 Harald Sitter changed: What|Removed |Added URL||https://phabricator.kde.org ||/T3210 --- Comment #1 from Harald Sitter --- needs https://github.com/hughsie/PackageKit/issues/142 on apt systems to have install-local work. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366196] New: update mode defaults to "all good" while waiting for transactions
https://bugs.kde.org/show_bug.cgi?id=366196 Bug ID: 366196 Summary: update mode defaults to "all good" while waiting for transactions Product: Discover Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org System shows notifications in applet. One wants to update. Discover comes up with busy spin. Then it switches to the updat-to-date screen until the query transaction completed in package. Only then will it actually show the updates and offer an update. Reproducible: Always Expected Results: Should busy spin until the transactions come back. Plasma/5.7 build -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366196] update mode defaults to "all good" while waiting for transactions
https://bugs.kde.org/show_bug.cgi?id=366196 --- Comment #1 from Harald Sitter --- Created attachment 100348 --> https://bugs.kde.org/attachment.cgi?id=100348&action=edit video -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366180] Environment variable XDG_DATA_DIRS may be incorrect?
https://bugs.kde.org/show_bug.cgi?id=366180 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Harald Sitter --- > DESKTOP_SESSION=/usr/share/xsessions/plasma which will be prepended to the variable by a core x11 setup script > $ grep -r SESSION\": /etc/X11/Xsession.d/60x11-common_xdg_path > > XDG_CONFIG_DIRS="$DEFAULT_XDG_CONFIG_DIRS"/xdg-"$DESKTOP_SESSION":"$XDG_CONFIG_DIRS" > XDG_DATA_DIRS=/usr/share/"$DESKTOP_SESSION":"$XDG_DATA_DIRS" So I am guessing that every DM other than SDDM actually treats DESKTOP_SESSION as the basename (excluding suffix) of the xsession file name. Please forward this bug to SDDM on github. As for your actual problem of icons not working. This probably has nothing to do with it since /usr/share//usr/share/xsessions/plasma == /usr/share/usr/share/xsessions/plasma which is a valid path, and the XDG spec doesn't mandate that the paths in the variable exist at all, so even though it is malformed it shouldn't matter. That said, depending on how Nylas renders the systray icons and whether it has own icon lookup code involved it is entirely possible that the lookup code is incorrect and breaks on non-existant paths in XDG_DATA_DIRS. I suggest you file a bug report with the Nylas authors as they are probably in a better position to guess where the problem might be. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems
https://bugs.kde.org/show_bug.cgi?id=366285 Harald Sitter changed: What|Removed |Added Assignee|neon-b...@kde.org |j...@jriddell.org --- Comment #1 from Harald Sitter --- Jonathan. I do so very much hope this isn't what I predicted would happen. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366366] Please provide a package for qtvirtualkeyboard
https://bugs.kde.org/show_bug.cgi?id=366366 --- Comment #2 from Harald Sitter --- I think you just volunteered to upstream this. - copyright file is incomplete - should put examples into -dev package - should put cmake file into -dev package - possibly should split qml from actual inputplugin (not actually sure that is useful though) - build-depends on kde-pkg-tools but doesn't seem to use it at all - shouldn't buildpdep on qt5-default - all qt builddeps should be tightly versioned - the rules file seems a bit ugh should export these flags: export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(shell dpkg-buildflags --get CPPFLAGS) export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(shell dpkg-buildflags --get CPPFLAGS) export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed export QT_SELECT := qt5 - shouldn't phony override_dh_auto_test or document why that is absolutely necessary -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366509] Include 25df38cad562c458538037b9e50552b6885e5d05 in QtWayland
https://bugs.kde.org/show_bug.cgi?id=366509 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Harald Sitter --- http://packaging.neon.kde.org/cgit/qt/qtwayland.git/commit/?id=c7f883fe8ad4b448702002934b96f9b0d358cee8 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363166] xterm still seeded
https://bugs.kde.org/show_bug.cgi?id=363166 Harald Sitter changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Harald Sitter --- No longer listed in manifest so I am guessing this is fixed now. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363314] wrong version in installer
https://bugs.kde.org/show_bug.cgi?id=363314 --- Comment #3 from Harald Sitter --- Created attachment 100489 --> https://bugs.kde.org/attachment.cgi?id=100489&action=edit still broken -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363314] wrong version in installer
https://bugs.kde.org/show_bug.cgi?id=363314 Harald Sitter changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #28 from Harald Sitter --- I think this should be solved in dev editions within the hour and for user edition some time this week. http://packaging.neon.kde.org/cgit/neon/settings.git/commit/?id=3a723d1daf55ce4b69b5af56c0a2ef35a31430b6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #29 from Harald Sitter --- nevermind, still broken. won't be solved until plasma learns to clean up and our software learns to not crash in destructors. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 366543] New: dropdown doesn't follow color scheme
https://bugs.kde.org/show_bug.cgi?id=366543 Bug ID: 366543 Summary: dropdown doesn't follow color scheme Product: Plasma SDK Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: cuttlefish Assignee: plasma-b...@kde.org Reporter: sit...@kde.org CC: giorgos.tsiapalio...@kde.org when using the breeze dark color scheme the "folder" dropdown in cuttlefish isn't correctly colored making it nigh impossible to read. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 366543] dropdown doesn't follow color scheme
https://bugs.kde.org/show_bug.cgi?id=366543 --- Comment #1 from Harald Sitter --- Created attachment 100509 --> https://bugs.kde.org/attachment.cgi?id=100509&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366701] os-release id_like invalid
https://bugs.kde.org/show_bug.cgi?id=366701 Harald Sitter changed: What|Removed |Added Assignee|neon-b...@kde.org |j...@jriddell.org Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366701] New: os-release id_like invalid
https://bugs.kde.org/show_bug.cgi?id=366701
Bug ID: 366701
Summary: os-release id_like invalid
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: neon-b...@kde.org
Reporter: sit...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
> [15:32] sitter: Some more stuff, use line.split("=", 1) in case
> there are multiple = - Your ID_LIKE use does not match the spec/manpage:
> ID_LIKE should be ID_LIKE="ubuntu debian", not unquoted.
> [15:33] Relevant quotes: (1) Variable assignment values must be
> enclosed in double or single quotes if they include spaces
> [15:33] (2) Example: for an operating system with "ID=centos", an
> assignment of "ID_LIKE="rhel fedora"" would be appropriate
i.e. needs changing to ID_LIKE="ubuntu debian"
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 364303] ksystemlog tests stuck for 3 hours
https://bugs.kde.org/show_bug.cgi?id=364303 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Harald Sitter --- fixed by https://git.reviewboard.kde.org/r/128328 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #31 from Harald Sitter --- The developer editions are about to get a neon-settings update which may prevent this from happening (for as long as it does right now). It would be awesome if people could test and see if it improves the situation (may need two reboots to apply). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #32 from Harald Sitter --- sudo apt update && sudo apt install neon-settings then reboot at least twice -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 369230] New: kexi duplicates all breeze icons
https://bugs.kde.org/show_bug.cgi?id=369230 Bug ID: 369230 Summary: kexi duplicates all breeze icons Product: kexi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: sit...@kde.org CC: a...@piggz.co.uk, in...@fables.co.za kexi wants breeze-icons.rcc which is a 100% duplication wasting disk space and bandwith. it maybe should just hardcode the searchpath for kiconloader/qicon. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 369232] New: cmake fails on missing rcc, it's a runtime dep though
https://bugs.kde.org/show_bug.cgi?id=369232
Bug ID: 369232
Summary: cmake fails on missing rcc, it's a runtime dep though
Product: kexi
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: General
Assignee: kexi-b...@kde.org
Reporter: sit...@kde.org
CC: a...@piggz.co.uk, in...@fables.co.za
cmake/modules/CheckGlobalBreezeIcons.cmake:message(FATAL_ERROR "No valid
breeze-icons.rcc resource file found. \
but the file apparently is only loaded at runtime
src/main/KexiRegisterResource_p.h:return
registerResource("icons/breeze/breeze-icons.rcc",
QStandardPaths::GenericDataLocation,
the file should not be required at build time, instaed cmake should issue a
runtime requirement information (e.g. https://phabricator.kde.org/D2377)
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kexi] [Bug 369230] kexi duplicates all breeze icons
https://bugs.kde.org/show_bug.cgi?id=369230 --- Comment #2 from Harald Sitter --- What does file count have to do with anything though? Everything but kexi uses the theme files, so the rcc is a waste on top of that. The rcc simply makes no sense in a platform scenario as we have on Linux. The entire platform uses one single thing, only kexi is the odd one out and needs its own thing. Hell, even if that wasn't the case from a platform perspective we always need to ship the SVG icons unless KIconLoder and QIcon learn to resolve via the rcc as through the present APIs we are implicitly bound to supply XDG icon theme resolution. I do not see the link between only breeze being supported and the rcc file. You can coerce a specific icon theme inside the application by telling KIconLoader/QIcon which theme you want. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 369232] cmake fails on missing rcc, it's a runtime dep though
https://bugs.kde.org/show_bug.cgi?id=369232 --- Comment #2 from Harald Sitter --- I have to confess I am going a bit TLDR on the response but I think the key problem is that previously before cmake RUNTIME we didn't have a way to communicate runtime deps in a *standardized* way. Which means packagers had no chance to deal with them efficiently. They now do, exactly the way as we do with other dependencies. If they don't make use of that, then they are just being bad at their job. find_package could even be made required and skipped with CMAKE_DISABLE_FIND_PACKAGE_$NAME by the packagers. So you get the same end result but you do it in a standard fashion. Regardless of any of this. I cannot think of a single packaging environment where build environment == run environment. The rcc being there at buildtime doesn't mean anything WRT runtime. On deb/rpm the rcc would need to be a runtime dep. In snap/flatpak/appimage the rcc needs to end up in the bundle (which fortunately is the default), same on other platforms. You need to assert it as runtime dependency in a standard fashion, everything else is just wishful thinking. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 369230] kexi duplicates all breeze icons
https://bugs.kde.org/show_bug.cgi?id=369230 --- Comment #4 from Harald Sitter --- The Qt way is to ship the rcc with your app. Do that and I probably wouldn't even care. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369307] Wrong find command in file validate_svg.sh
https://bugs.kde.org/show_bug.cgi?id=369307 Harald Sitter changed: What|Removed |Added Latest Commit||9e0466a1996717e44ca8c3842ab ||d304d69af7ea7 Resolution|--- |FIXED CC||sit...@kde.org Version Fixed In||5.27 Status|UNCONFIRMED |RESOLVED --- Comment #2 from Harald Sitter --- http://commits.kde.org/breeze-icons/9e0466a1996717e44ca8c3842abd304d69af7ea7 https://git.reviewboard.kde.org/r/129020/ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369307] Wrong find command in file validate_svg.sh
https://bugs.kde.org/show_bug.cgi?id=369307 --- Comment #3 from Harald Sitter --- For future reference. Review Board is (currently) the place to put patches, they easily get lost in the bug tracker https://community.kde.org/Infrastructure/Review_Board -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 369388] no kdevelop in appstream data
https://bugs.kde.org/show_bug.cgi?id=369388 Harald Sitter changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- Computer says no $ wget http://archive.neon.kde.org/user/dists/xenial/main/dep11/Components-amd64.yml.gz -q -O - |zcat |grep org.kde.kdevelop ID: org.kde.kdevelop.desktop - url: org/kde/kdevelop.desktop/3AB221131AD1A6F86A8E5B569751F2C0/screenshots/image-1_1248x681.png - url: org/kde/kdevelop.desktop/3AB221131AD1A6F86A8E5B569751F2C0/screenshots/image-1_752x410.png - url: org/kde/kdevelop.desktop/3AB221131AD1A6F86A8E5B569751F2C0/screenshots/image-1_624x340.png - url: org/kde/kdevelop.desktop/3AB221131AD1A6F86A8E5B569751F2C0/screenshots/image-1_224x122.png url: org/kde/kdevelop.desktop/3AB221131AD1A6F86A8E5B569751F2C0/screenshots/image-1_orig.png -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 369414] KDE System Settings crash
https://bugs.kde.org/show_bug.cgi?id=369414 Harald Sitter changed: What|Removed |Added CC||bcooks...@kde.org, ||f...@kde.org, ||j...@videolan.org Component|general |general Product|Phonon |phonon-backend-vlc -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Harald Sitter changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #35 from Harald Sitter --- I'll file a task to follow up on resolving the underlying causes of this. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369521] New: multiarch not supported (installing wrong package!)
https://bugs.kde.org/show_bug.cgi?id=369521 Bug ID: 369521 Summary: multiarch not supported (installing wrong package!) Product: Discover Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: sit...@kde.org On systems where multiple architectures can be installed (e.g. debian on x64 also can install and run x32) discover has a 50:50 chance of installing the wrong package if a package is both available for both architectures. The reason for this is that discover never uses the packagekit ARCH filter (PackageKit::Transaction::FilterArch) to limit the selection to the preferred architecture, ultimately resulting in all architectures being returned in arbitrary order (or rather, the API makes no assertions about the order). This for example results in kipi-plugins on neon installing the i386 package (or trying to) when really it should pick amd64. When changing the resolve call to > PackageKit::Transaction * t = PackageKit::Daemon::resolve(names, > PackageKit::Transaction::FilterArch); only native architecture will be tracked. Supposedly this would be unsuitable as well as then one can't install i386 packages (e.g. potential third party binary blob packages that only are available as i386). The way I understand it this needs a bit of a restructuring WRT how applications are mapped to packages. a) A Resource could stop holding packageids. Specifically the backend would get all apps from appstream, resolve them via packagekit and note that a given resource is resolved (or not) BUT not keep the packageid in the resource. Since PK can resolve the name we don't need the pkgid and can later simply call install(packagename, filter_ARCH) and if that fails install(packagename, filter_NO_ARCH) as fallback to pick a secondary architecutre package if no primary arch is available. b) Backend does two resolve queries. One with ARCH and once that is done for all resources that were not resolved it does another resolve run with NO_ARCH. i.e. a Resources has a packagelist that is either from the primary arch or a !primary arch, but not both. Since we map one app to one packageid for installation this might be the best and most efficient option since we effectively want either-or for installation. c) A combination of a) and b) might be possible. By default the backend requests two resolves, one with ARCH and one with NO_ARCH. It keeps both sets of information so a discover resource knows which packageids it maps to for the primary architecture as well as !primary. Upon installation request discover could request primary and fall back to !primary if primary installation failed (not sure that is good). NB: limiting the packageids to ARCH filtered ones may impact update listing as update listing ought to be a complete list of all packages, so only option c) could be a viable option. I am unclear about the implications. It's also worth noting that if discover has daemon interaction where it throws packagenames (rather than packageids) at the daemon those need to have their need for filtering reviewed as well. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369521] multiarch not supported (installing wrong package!)
https://bugs.kde.org/show_bug.cgi?id=369521 --- Comment #2 from Harald Sitter --- That is the line I was pasting :P The problem is this isn't enough. FilterArch will filter everything that is not native (i.e. amd64). There are however things that are only available from i386 (skype, what have you). So we need both, we just need to prefer a native package when there is one. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 369527] New: applet should color through system colors
https://bugs.kde.org/show_bug.cgi?id=369527 Bug ID: 369527 Summary: applet should color through system colors Product: telepathy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: presence-applet Assignee: kde-telepathy-b...@kde.org Reporter: sit...@kde.org since some recent frameworks version mono icons can be colored depending on the system theme. the presence applet does not follow this new tech and looks grotesquely out of place Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 369527] applet should color through system colors
https://bugs.kde.org/show_bug.cgi?id=369527 --- Comment #1 from Harald Sitter --- Created attachment 101344 --> https://bugs.kde.org/attachment.cgi?id=101344&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 369560] New: qml-modules-org-kde-purpose has excess s
https://bugs.kde.org/show_bug.cgi?id=369560 Bug ID: 369560 Summary: qml-modules-org-kde-purpose has excess s Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: sit...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org qml-modules-org-kde-purpose is incorrectly named. note the s in moduleS. best practise is qml-module-, so qml-modules- is out of line Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 369863] New: purpose conflicty
https://bugs.kde.org/show_bug.cgi?id=369863 Bug ID: 369863 Summary: purpose conflicty Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: sit...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org dpkg: error processing archive /var/cache/apt/archives/libkf5purpose5_1.1+p16.04+git20160930.1710-0_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libKF5PurposeWidgets.so.5.27.0', which is also in package libkf5purposewidgets5:amd64 1.1+p16.04+git20160920.-0 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369879] New: deselecting all krunners renables all of them
https://bugs.kde.org/show_bug.cgi?id=369879 Bug ID: 369879 Summary: deselecting all krunners renables all of them Product: plasmashell Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sit...@kde.org CC: bhus...@gmail.com, plasma-b...@kde.org was trying to debug something, so I disabled all runners. next start krunner has all enabled. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370981] Can't enter LUKS password
https://bugs.kde.org/show_bug.cgi?id=370981 Harald Sitter changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Harald Sitter --- Please get in touch with your distribution, this is an integration issue. Password queries are meant to go through a standardized system which is behaving correctly as per our test https://github.com/KDE/breeze-plymouth/blob/master/test/plytest.sh#L59 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374 --- Comment #5 from Harald Sitter --- Well, if that is the case then I guess you should be filing a bug with GRUB, not the theme? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #7 from Harald Sitter --- Sure if it is laggish then it shouldn't be themed. That too is something that ought to be addressed in GRUB though, as only GRUB knows if rendering is obscenely slow. Now this doesn't seem particularly common given you are the only person who complained. Best I can do is make distributions aware of this. If you think that we should not advise using the theme based on the rendering lag, that is something you want to take up with the VDG. Personally I advise whoever has the problem to simply disable the theme. It's basically having shit UX for everyone (no theme) or shit UX for a select few (laggish rendering). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374 --- Comment #9 from Harald Sitter --- If everyone used refind we'd all be happier for it ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368239] Dropbox Icon Will not appear in System Tray
https://bugs.kde.org/show_bug.cgi?id=368239 Harald Sitter changed: What|Removed |Added Assignee|neon-b...@kde.org |plasma-b...@kde.org Version|unspecified |5.7.3 Target Milestone|--- |1.0 Product|neon|plasmashell Component|Packages User Edition |System Tray --- Comment #1 from Harald Sitter --- Moving to plasma. Can't reproduce by the way. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368683] New: kmail should recommend or depend on accountwizard
https://bugs.kde.org/show_bug.cgi?id=368683 Bug ID: 368683 Summary: kmail should recommend or depend on accountwizard Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: sit...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org without accountwizard kmail can't help people setup accounts and throws stupid warnigns when one tries to start the wizard via the menu Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368691] New: qtwebengine-dev needs qtwebchannel-dev
https://bugs.kde.org/show_bug.cgi?id=368691 Bug ID: 368691 Summary: qtwebengine-dev needs qtwebchannel-dev Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: sit...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5WebEngineCore/Qt5WebEngineCoreConfig.cmake:99 (find_package): Could not find a package configuration file provided by "Qt5WebChanne Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368694] New: mailto url body lost for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=368694 Bug ID: 368694 Summary: mailto url body lost for unknown reasons Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: sit...@kde.org kgpg can sign and send a key by mail. it does so via qdesktopservices::openurl to which it passes an url of the form mailto:sit...@kde.org?subject=Your%20key%20asfadfafadsf&body=-BEGIN%20PGP%20MESSAGE-%0AVer The body part of this url is subsequently lost in kmail for unkown reasons and doens't display in the editor window at all. Subject works as expected. this doesn't work: kmail 'mailto:gr...@kde.org?subject=Your%20key%207FEA3DA6169C77D6&body=-BEGIN%20PGP%20' this works: kmail 'mailto:gr...@kde.org?subject=Your%20key%207FEA3DA6169C77D6&body=-BEGIN%20PGP' Parsing in kmkernel works correctly, it passes the string as expected to ::action to ::openComposer where the body is still correct before it is put in a KMime::Message and handed to KMail::makeComposer which in turn goes to KMComposerWin::KMComposerWin where it goes into MessageComposer::ComposerViewBase::setMessage. Unfortunately I couldn't build all the necessary stuff, so that's where I gave up. Working theory is that the composer eats the body for unknown reasons. It can't be decryption problems though since from what I can tell in all my tests the relevant bool argument was false. Nevertheless it could be that invalid pgp messages get rejected (if so it should still put a warning or something in the body). If so, it's conceivable that somewhere along the line the fairly long body constructed by kgpg (encrypted message blob) would get truncated resulting in no body in kmail due to invalid pgp block. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368894] New: device notifier popups do not respect display rules
https://bugs.kde.org/show_bug.cgi?id=368894
Bug ID: 368894
Summary: device notifier popups do not respect display rules
Product: plasmashell
Version: 5.7.5
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Device Notifier
Assignee: plasma-b...@kde.org
Reporter: sit...@kde.org
devicenotifier applet has a config set to select which type of devices to
display. if one adds a loop mount this appers as an event in the applet code
plasmashell(17632)/(default) unknown:
"/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces:
("org.freedesktop.UDisks2.Filesystem")
plasmashell(17632)/(qml) onDataChanged: DATA CHANGED
the applet subsequently sets expanded=true ignoring its own display rule. so if
the applet was configured to only show removable devices it will trigger a
popup of an empty device notifier
Reproducible: Always
Steps to Reproduce:
1. config applet to only show removable devices
2. cause a loop mount (e.g. by installing a snap package)
Actual Results:
applet pops up persistently but doesn't show the loop device
Expected Results:
pop up should not appear if the device type is filtered from view
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 369048] [packaging] kwin: Optionally depend on libhybris-dev for armhf and enable hwcomposer plugin
https://bugs.kde.org/show_bug.cgi?id=369048 --- Comment #5 from Harald Sitter --- If the package is armhf and armel, so needs the build-dep (currently only armhf) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 369048] [packaging] kwin: Optionally depend on libhybris-dev for armhf and enable hwcomposer plugin
https://bugs.kde.org/show_bug.cgi?id=369048 --- Comment #7 from Harald Sitter --- No clue, probably. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366826] New: Adding sources in discover cannot possibly work
https://bugs.kde.org/show_bug.cgi?id=366826 Bug ID: 366826 Summary: Adding sources in discover cannot possibly work Product: Discover Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org The sources view has an add button but packagekit documentation says the following: https://www.freedesktop.org/software/PackageKit/pk-faq.html#repo-add-remove I also couldn't find any API that can add sources. Which raises the question of how a person is meant to add repos. I guess this should be brought to the attention of the VDG as well. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 333438] Search not working: Add search for packages without appstream data
https://bugs.kde.org/show_bug.cgi?id=333438 Harald Sitter changed: What|Removed |Added Summary|Not all packages show when |Search not working: Add |searched|search for packages without ||appstream data -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365713] typing search term in discover does nothing
https://bugs.kde.org/show_bug.cgi?id=365713 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #1 from Harald Sitter --- So what's the search term to test then? And which Linux are you using? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365713] typing search term in discover does nothing
https://bugs.kde.org/show_bug.cgi?id=365713 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Harald Sitter --- Change state -- You are receiving this mail because: You are watching all bug changes.
