[umbrello] [Bug 379899] unable to save work
https://bugs.kde.org/show_bug.cgi?id=379899 pnadegen...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from pnadegen...@gmail.com --- Thank for your answer. It doesn't help me but after posting my problem, i had found the solution to it. I had to install "kio" packages: "sudo apt-get install kio". , before installing umbrello. Have a nice day. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 380024] New: Opening a remote file and clicking "Open" resets the file picker's location to the user's home directory
https://bugs.kde.org/show_bug.cgi?id=380024 Bug ID: 380024 Summary: Opening a remote file and clicking "Open" resets the file picker's location to the user's home directory Product: kate Version: 16.12 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kde_b...@multiwebinc.com Target Milestone: --- When I open a local file in Kate that is located somewhere outside of my home directory and then click the "Open" button to open a second file, the directory of the currently open file is used in the file picker dialog. For example, open /home/user/Desktop/folder/file.txt and when you click on "Open" again, the file picker displays /home/user/Desktop/folder/. This makes opening several files from the same directory very convenient. This was also the behaviour for previous versions of kate, but after upgrading from Ubuntu 16.10 to 17.04, that is no longer the case for remote files. When opening subsequent remote files, the directory in the file picker is reset every time back to the user's home directory. Note: I have tested using SFTP, but not any other remote protocol since I don't have any others available. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 380023] New: Quit after ending turn without move or attack
https://bugs.kde.org/show_bug.cgi?id=380023 Bug ID: 380023 Summary: Quit after ending turn without move or attack Product: kdelibs Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: knotify Assignee: ogoff...@kde.org Reporter: guest26118...@gmail.com Target Milestone: --- Application: knotify4 (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: I added armies and quit my turn without moving or attacking. I pressed 'Next Player', Answered yes to the pop-up to confirm my action, then the crash reporter came up indicating a problem. This is the first time that this happened to me. Note: I have been playing this game for a long time, but it has deteriorated quite a bit. I used to be able to turn off sound and animation which allowed a faster paced game, now that option is not available which slows down the game a whole lot. The manual is no longer available. Is anyone even working on the game? There does not seem to be any support. If someone is actually reading this, please let me know or I must presume that there is no point in reporting bugs for KsirK. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f532919b7c0 (LWP 6403))] Thread 9 (Thread 0x7f530fd17700 (LWP 6404)): #0 0x7f532632884d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5323708fe4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f53080034d0, timeout=-1, context=0x7f53080009a0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:4028 #2 g_main_context_iterate (context=context@entry=0x7f53080009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3729 #3 0x7f53237090ec in g_main_context_iteration (context=0x7f53080009a0, may_block=1) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795 #4 0x7f5326ab27be in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f5326a840af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f5326a843a5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f5326980c5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f5326a65823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f532698332f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f5323be8184 in start_thread (arg=0x7f530fd17700) at pthread_create.c:312 #11 0x7f5326335bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 8 (Thread 0x7f52c700 (LWP 7132)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f5323bea67f in _L_lock_1081 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f5323bea5f8 in __GI___pthread_mutex_lock (mutex=0xdf1e20) at ../nptl/pthread_mutex_lock.c:134 #3 0x7f532374a981 in g_mutex_lock (mutex=mutex@entry=0x7f53239c7360) at /build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:209 #4 0x7f5323723c73 in private_thread_memory_cleanup (data=0x7f52c40008c0) at /build/buildd/glib2.0-2.40.2/./glib/gslice.c:781 #5 0x7f5323be7f82 in __nptl_deallocate_tsd () at pthread_create.c:158 #6 0x7f5323be8197 in start_thread (arg=0x7f52c700) at pthread_create.c:325 #7 0x7f5326335bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 7 (Thread 0x7f52f4ff1700 (LWP 7133)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f5323bea67f in _L_lock_1081 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f5323bea5f8 in __GI___pthread_mutex_lock (mutex=0xdf1e20) at ../nptl/pthread_mutex_lock.c:134 #3 0x7f532374a981 in g_mutex_lock (mutex=mutex@entry=0x7f53239c7360 ) at /build/buildd/glib2.0-2.40.2/./glib/gthread-posix.c:209 #4 0x7f5323723c73 in private_thread_memory_cleanup (data=0x7f52c80008c0) at /build/buildd/glib2.0-2.40.2/./glib/gslice.c:781 #5 0x7f5323be7f82 in __nptl_deallocate_tsd () at pthread_create.c:158 #6 0x7f5323be8197 in start_thread (arg=0x7f52f4ff1700) at pthread_create.c:325 #7 0x7f5326335bed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f52cf7fe700 (LWP 7134)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f5323bea67f in _L_lock_1081 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f5323bea5f8 in __GI___pthread_mutex_lock
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #80 from fl...@mailoo.org --- I suspect the bunch of updates you had was the recent Kubuntu updates specifically for KDE PIM (finally bumping it to a recent release, they probably had issues with QtWebEngine), so it would appear that up-to-date versions are not affected anymore. -- You are receiving this mail because: You are watching all bug changes.
[ktouchpadenabler] [Bug 380004] Touchpad does not toggle with keyboard shortcut unless systemsettings is opened first
https://bugs.kde.org/show_bug.cgi?id=380004 --- Comment #3 from wizard10...@gmail.com --- (In reply to wizard1 from comment #2) > My apologies. This is an issue with Plasma5 in Neon Dev Unstable. > > Can you route to the proper team, please? > > Thank you - Correction. Neon Dev Testing. -- You are receiving this mail because: You are watching all bug changes.
[ktouchpadenabler] [Bug 380004] Touchpad does not toggle with keyboard shortcut unless systemsettings is opened first
https://bugs.kde.org/show_bug.cgi?id=380004 --- Comment #2 from wizard10...@gmail.com --- My apologies. This is an issue with Plasma5 in Neon Dev Unstable. Can you route to the proper team, please? Thank you - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379554] Packaging for Solus: Plasma Desktop refuses to show up
https://bugs.kde.org/show_bug.cgi?id=379554 --- Comment #1 from Federico Damián Schonborn--- Plasma is now included in the official repositories and works, please close this :D -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 379301] Starting Plasma desktop failed
https://bugs.kde.org/show_bug.cgi?id=379301 a12321a...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from a12321a...@gmail.com --- Hi,Christoph, Thanks for your reply. You are right, this is caused by python widget I installed. Slackware then update pykde4 package then the problem fixed. Thanks again for point out what's wrong with my desktop setting. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 379961] Wrong type for 'or' operator expression
https://bugs.kde.org/show_bug.cgi?id=379961 Nicolás Alvarezchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||v-python/f046a4fe91cfc4608b ||f2c1c7421ed565624270ab Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Nicolás Alvarez --- Git commit f046a4fe91cfc4608bf2c1c7421ed565624270ab by Nicolás Alvarez. Committed on 20/05/2017 at 00:56. Pushed by nalvarez into branch 'master'. Infer correct type from 'and' / 'or' expressions kdev-python was assuming boolean operator expressions like 'foo or bar' always returned 'bool', but Python defines them to always return the value of either variable depending on whether the first one is false-like. Thus, 'someString or "bar"' should be interpreted as a string, not a boolean. This commit makes such boolean operator expressions have a type of unsure(type(foo), type(bar)) instead. I also added new tests for this new behavior, and to ensure the good old "True or False" is still interpreted as a bool. Differential Revision: https://phabricator.kde.org/D5915 M +9-2duchain/expressionvisitor.cpp M +6-0duchain/tests/pyduchaintest.cpp https://commits.kde.org/kdev-python/f046a4fe91cfc4608bf2c1c7421ed565624270ab -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 --- Comment #76 from Navid Zamani--- Since this bug has turned into a bulletin board by now… Frankly, there is no viable desktop environment for Linux nowadays. • KDE hasn’t left “early beta” quality since 4.0, as this bug shows. Try anything out of the ordinary in the settings, and it will either be broken or not exist anymore. (Kate is still my favorite though.) • Gnome took it to its logical conclusion, and just removed all the features right away anyway. Including themability. (Qalculate still can’t be beaten though.) • Ditto for Cinnamon/Mate, which are of better quality, but still crippled by minimalism. • XFCE et al are even more minimal, so even less viable for non-consumers. • Enlightenment is currently in a large transition, and also only works if you don’t try anything too much out of the ordinary, if at all. I think it is time for something new. Something clean and elegant, yet uncompromisingly powerful. A true Linux PC graphical shell. Not a “desktop environment”. Not a command line / search. Yet with all the advantages of both. Where is it though? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 --- Comment #75 from madumlao--- I have a morbid fascination with watching this bug remain unfixed. There should be Linux user group parties all over the world for the 10 year anniversary. Mark it in your korganizers folks: 2019-02-06, the 10-year kde numpad bug party. Heck invite your GNOME friends along! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380022] New: kdeconnect: can't browse files
https://bugs.kde.org/show_bug.cgi?id=380022 Bug ID: 380022 Summary: kdeconnect: can't browse files Product: kdeconnect Version: 1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: fergus.incoron...@gmail.com Target Milestone: --- I installed `kdeconnect` and `indicator-kdeconnect` as explained at [OMG! Ubuntu!](http://www.omgubuntu.co.uk/2017/02/easy-way-connect-android-to-ubuntu-pc) and [github](https://github.com/vikoadi/indicator-kdeconnect/issues/43): sudo add-apt-repository ppa:varlesh-l/indicator-kdeconnect sudo apt update sudo apt install kdeconnect indicator-kdeconnect Everything seems to work properly except the ***Browse device*** functionality. If I click on the indicator and then on *Browse device*, `nautilus` pops-up however the directory (`$HOME/.config/kdeconnect/[DEVICEID]/kdeconnect_sftp/[DEVICEID]`) is empty. Do you have any suggestion on how to proceed from here? Thanks in advance. Environment === --- $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial Package Version === --- **dbus** $ apt show dbus Version: 1.10.6-1ubuntu3.3 **kdeconnect** $ apt show kdeconnect Version: 1.0.3ubuntu16.04 **indicator-kdeconnect** $ apt show indicator-kdeconnect Version: 0.6ubuntu16.04.1 Syslog === --- org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Mount device: "google" org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Created mounter org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Unmount QObject(0x0) org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.168.1.3:/ /home/ncrfgs/.config/kdeconnect/28cebede2fc57937/kdeconnect_sftp/28cebede2fc57937 -p 1739 -f -F /dev/null -o IdentityFile=/home/ncrfgs/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin" org.kde.kdeconnect[12766]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packageReceived(NetworkPackage): Unregistered input type in parameter list: NetworkPackage org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Process started org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: "google" "Remote filesystem mounted at /home/[USER]/.config/kdeconnect/[DEVICEID]/kdeconnect_sftp/[DEVICEID]" org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: stdout: "fuse: bad mount point `/home/[USER]/.config/kdeconnect/[DEVICEID]/kdeconnect_sftp/[DEVICEID]': Transport endpoint is not connected\n" org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Process finished (exit code: 1 ) org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: "google" Remote filesystem unmounted org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Unmount KProcess(0x1d92650) org.kde.kdeconnect[12766]: kdeconnect.plugin.sftp: Destroy mounter -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 379840] Akregator crashes at start (metakit backend)
https://bugs.kde.org/show_bug.cgi?id=379840 --- Comment #1 from Andrei Slavoiu--- Created attachment 105648 --> https://bugs.kde.org/attachment.cgi?id=105648=edit Metakit file that causes the crash -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 380007] Improvements for Gettext entries wordwrapping
https://bugs.kde.org/show_bug.cgi?id=380007 Azamat H. Hackimovchanged: What|Removed |Added Attachment #105632|0 |1 is obsolete|| --- Comment #4 from Azamat H. Hackimov --- Created attachment 105647 --> https://bugs.kde.org/attachment.cgi?id=105647=edit 0002-Reworking-word-wrapping-for-Gettext-catalog.patch Fixed small typo in code. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380021] Background image doesn't support Unicode file names or directory names
https://bugs.kde.org/show_bug.cgi?id=380021 Guo Yunhe (郭云鹤)changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380021] New: Background image doesn't support Unicode file names or directory names
https://bugs.kde.org/show_bug.cgi?id=380021 Bug ID: 380021 Summary: Background image doesn't support Unicode file names or directory names Product: systemsettings Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: guoyunhebr...@gmail.com Target Milestone: --- 1. Open KCM > SDDM 2. Choose Breeze theme 3. Choose a background picture with Chinese/Japanese/Korean file name 4. Save 5. Logout to see actual SDDM background image If the image file name or path contains Unicode characters, it will not save the image. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368069] SMS messages not shown in the list even though they are sent
https://bugs.kde.org/show_bug.cgi?id=368069 --- Comment #7 from Cqoicebordel--- I'm sorry to say it, but no, it didn't fix it for me. I still don't see the answer written on the desktop in the discussion. -- You are receiving this mail because: You are watching all bug changes.
[ktouchpadenabler] [Bug 380004] Touchpad does not toggle with keyboard shortcut unless systemsettings is opened first
https://bugs.kde.org/show_bug.cgi?id=380004 Albert Astals Cidchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Albert Astals Cid --- Sorry but ktouchpadneabler for Plasma 4 is unmaintained (basically can't fix something that isn't being released anymore) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 Chris Hollandchanged: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374276] Have to log-out and log back in to apply icon theme.
https://bugs.kde.org/show_bug.cgi?id=374276 Chris Hollandchanged: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378469] 17.04 - Crash on Exit
https://bugs.kde.org/show_bug.cgi?id=378469 Frédéric COIFFIERchanged: What|Removed |Added CC||frederic.coiff...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378763] kdenlive-git - crash on exist
https://bugs.kde.org/show_bug.cgi?id=378763 Frédéric COIFFIERchanged: What|Removed |Added CC||frederic.coiff...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359587] akonadi server hangs and needs continual rebooting, email address autosuggest not working, using the "TO" column to select causes akonadi resource to crash
https://bugs.kde.org/show_bug.cgi?id=359587 --- Comment #3 from Ken Freeland--- BTW, I should add that even though the address book shows my groups for emailing from google, Kontact has never been able to use them...you click on them and they do not show the addresses included...it's a worthless feature for me On Fri, May 19, 2017 at 4:04 PM, Ken Freeland wrote: > Denis, > the bug continues...now on different machines; desktop kubuntu 16.04 > kontact 5.2.3 > laptop kubuntu 17.04 kontact 5.1.3 > no prediction despite configuring for google address book search in both > (correctly configured in both, and even unchecking "use recent email > addresses). The laptop will predict from recent addresses if i check the > box, but neither will predict from my google contacts address book. > Thanks for asking. This is really frustrating...makes using Kontact a > royal pain. > ken > > On Fri, May 19, 2017 at 6:19 AM, Denis Kurz > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=359587 >> >> Denis Kurz changed: >> >>What|Removed |Added >> >> >> Status|UNCONFIRMED |NEEDSINFO >> CC||kde...@posteo.de >> Resolution|--- |WAITINGFORINFO >> >> --- Comment #1 from Denis Kurz --- >> Ken, version 5.0 of Kontact was a "Technology Preview". Does this still >> happen >> to you? If so, which version do you use? Some other email address >> autocompletion issues have been resolved in the past year, so yours might >> be >> fixed as well. >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359587] akonadi server hangs and needs continual rebooting, email address autosuggest not working, using the "TO" column to select causes akonadi resource to crash
https://bugs.kde.org/show_bug.cgi?id=359587 --- Comment #2 from Ken Freeland--- Denis, the bug continues...now on different machines; desktop kubuntu 16.04 kontact 5.2.3 laptop kubuntu 17.04 kontact 5.1.3 no prediction despite configuring for google address book search in both (correctly configured in both, and even unchecking "use recent email addresses). The laptop will predict from recent addresses if i check the box, but neither will predict from my google contacts address book. Thanks for asking. This is really frustrating...makes using Kontact a royal pain. ken On Fri, May 19, 2017 at 6:19 AM, Denis Kurz wrote: > https://bugs.kde.org/show_bug.cgi?id=359587 > > Denis Kurz changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > CC||kde...@posteo.de > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Denis Kurz --- > Ken, version 5.0 of Kontact was a "Technology Preview". Does this still > happen > to you? If so, which version do you use? Some other email address > autocompletion issues have been resolved in the past year, so yours might > be > fixed as well. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380010] Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist.
https://bugs.kde.org/show_bug.cgi?id=380010 --- Comment #3 from Martin Flöser--- Yes that option is the one. If that doesn't have an effect the applications are disabling compositing in another way. And yes it is totally fine that compositing gets disabled in that case. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 380020] New: Save and restore position of tool windows
https://bugs.kde.org/show_bug.cgi?id=380020 Bug ID: 380020 Summary: Save and restore position of tool windows Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: thomas.friedrichsme...@ruhr-uni-bochum.de Target Milestone: --- E.g. when moving the workspace browser to the right toolbar, that position should be remembered on the next run. Note: What about (semi-accidentally) removed tool windows? Will casual users be able to figure out, how to restore these? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380017] Can't change DateTime format in modified column
https://bugs.kde.org/show_bug.cgi?id=380017 --- Comment #2 from Esteban Adrián Pérez--- (In reply to Alex Bikadorov from comment #1) > QLocale with QLocale::ShortFormat is used for the datetime format. Only the > language can be set here, not the exact format. > > What about other Qt applications (e.g. Dolphin)? The time format should be > the same there. Oh! Alex... You are right... :( In Dolphin happens the same... So, here I'm fighting with 2 probmes: my ignorance about the ¿KDE configuration? and the datetime format I expected, I guess... When I refer to "all my system", I talk about terminal (MC, ll, and others) and never think about this can be realted to KDE configuration... I'm sorry... I'll search again in google how to "set up" this... My appologies... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380016] The window can't be resized down
https://bugs.kde.org/show_bug.cgi?id=380016 --- Comment #3 from Esteban Adrián Pérez--- (In reply to Alex Bikadorov from comment #1) > Please post a screenshot. Added screenshot... >Is there some content in the window that prevents resizing? Just the usual columns, I tried to shrink the columns, edit the krusaderrc file, and the same result > 1300pixel in width, I assume. What about height? Yes, 1300 in width... About the height, it works as expected :) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380016] The window can't be resized down
https://bugs.kde.org/show_bug.cgi?id=380016 --- Comment #2 from Esteban Adrián Pérez--- Created attachment 105644 --> https://bugs.kde.org/attachment.cgi?id=105644=edit Screenshoot showing krusader min width -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 312834] closing split view closes the currently focused view instead of the inactive
https://bugs.kde.org/show_bug.cgi?id=312834 Chris Hollandchanged: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] New: Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 Bug ID: 380019 Summary: Kdenlive crashes when using "Fade from black" on an image Product: kdenlive Version: 17.04.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: cadenga...@mail.com Target Milestone: --- Application: kdenlive (17.04.1) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I put a "Fade from black" effect on an image (PNG, 1920x1080) and when you play the video kdenlive crashes. - Custom settings of the application: GPU Processing was enabled. The crash can be reproduced every time. NOTE: The crash reporting wizard could not submit the report, so I am doing it manually through the website. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f45b4de6800 (LWP 7798))] Thread 16 (Thread 0x7f453abfd700 (LWP 8078)): #0 0x7f45ab1e0756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f457db356dd in () at /usr/lib/mlt/libmltsdl.so #2 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f453b3fe700 (LWP 8043)): #0 0x7f45a4d3e6fe in pa_stream_get_state () at /usr/lib/libpulse.so.0 #1 0x7f457d8cc541 in () at /usr/lib/libSDL-1.2.so.0 #2 0x7f457d8a076b in () at /usr/lib/libSDL-1.2.so.0 #3 0x7f457d8a8e18 in () at /usr/lib/libSDL-1.2.so.0 #4 0x7f457d8e9d39 in () at /usr/lib/libSDL-1.2.so.0 #5 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f4554f91700 (LWP 8042)): [KCrash Handler] #6 0x7f4580aafb84 in MltInput::set_pixel_data(unsigned char const*) () at /usr/lib/mlt/libmltopengl.so #7 0x7f4580aa93b1 in () at /usr/lib/mlt/libmltopengl.so #8 0x7f4580aa8b3d in () at /usr/lib/mlt/libmltopengl.so #9 0x7f4580aa9b08 in () at /usr/lib/mlt/libmltopengl.so #10 0x7f45b3eef1e8 in mlt_frame_get_image () at /usr/lib/libmlt.so.6 #11 0x7f45b3f051d9 in () at /usr/lib/libmlt.so.6 #12 0x7f45b3eef197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6 #13 0x7f45b3f0286f in () at /usr/lib/libmlt.so.6 #14 0x00759d9d in () #15 0x7f45adbae6d8 in () at /usr/lib/libQt5Core.so.5 #16 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #17 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f4552a48700 (LWP 8041)): #0 0x7f45ab1e0756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f45b3f02beb in mlt_consumer_rt_frame () at /usr/lib/libmlt.so.6 #2 0x7f457db35b10 in () at /usr/lib/mlt/libmltsdl.so #3 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f45397fb700 (LWP 7890)): #0 0x7f45ab1e0b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f45adbaf4c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f45adbaabc4 in () at /usr/lib/libQt5Core.so.5 #3 0x7f45adbae6d8 in () at /usr/lib/libQt5Core.so.5 #4 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f453bfff700 (LWP 7824)): #0 0x7f45ad1a467d in poll () at /usr/lib/libc.so.6 #1 0x7f45a4fad9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f45a4fadacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f45addde09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f45add878ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f45adba9a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f45adbae6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f45ad1ae54f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f455434c700 (LWP 7823)): #0 0x7f45ab1e0756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f45adbaf58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f45b35ef665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f45b35eff72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f45adbae6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f45ab1da2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f45ad1ae54f in clone
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 --- Comment #79 from Michael Barraclough--- I managed to implement KMail 5.4.3 but this did not seem to fix the issue. However, very shortly after that I received a flurry of updates via the updater and it started working after that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380010] Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist.
https://bugs.kde.org/show_bug.cgi?id=380010 --- Comment #2 from unsuspicious.fakename+kdeb...@gmail.com --- Sorry, maybe I wrote too much gibberish and failed to sum up the problem clearly enough again, so here you go: * When applications that use the window hint are started, Desktop switching features, accessibility features and more that are provided through compositing suddenly stop working without any indication as to why - or how to restore basic Desktop functionality. Are you sure this is all included in expected behavior? As in "the end user should be able to expect it and deal with it without problems"? Or is it just not the compositing managers job / should the applications that use the flag take care of the resulting problem somehow? Also I can't find a config option to change the behavior (for all applications at once). The only one in the GUI that mentions compositing is "Display_and_Monitor>Compositor>Allow_applications_to_block_compositing" and that one does not appear to affect the BYPASS_COMPOSITOR-behavior at all (had the system option disabled all along, applications are still able to block compositing with the flag and I still have to change it in the "more Actions menu" for each one). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346744] [WACOM INTUOS] Mapping and Pressure Problems with Krita and Wacom Intuos Pro tablet when I use two monitors (laptop+second hdmi monitor).
https://bugs.kde.org/show_bug.cgi?id=346744 Finnchanged: What|Removed |Added CC||thegaybisc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 --- Comment #74 from Lord Alveric--- This is a long-standing bug. I'm affected by it too. It is also embarrassing. I know workarounds have been posted over what is nearly a decade... My keyboards all have the numeric pad that never sees much use because of this bug. I have 9 virtual desktops, and would only been massively cool if I could simply use this keypad to call them up. Please, please, PLEASE fix this bug already. I'd do it myself but I have so many projects in the fire right now I don't have the time. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 Lord Alvericchanged: What|Removed |Added CC||fred.mitch...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 Martin Flöserchanged: What|Removed |Added Attachment #105641|text/x-log |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380017] Can't change DateTime format in modified column
https://bugs.kde.org/show_bug.cgi?id=380017 Alex Bikadorovchanged: What|Removed |Added CC||alex.bikado...@kdemail.net --- Comment #1 from Alex Bikadorov --- QLocale with QLocale::ShortFormat is used for the datetime format. Only the language can be set here, not the exact format. What about other Qt applications (e.g. Dolphin)? The time format should be the same there. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update
https://bugs.kde.org/show_bug.cgi?id=379796 Martin Flöserchanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #5 from Martin Flöser --- Resetting as it is a driver bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380010] Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist.
https://bugs.kde.org/show_bug.cgi?id=380010 Martin Flöserchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|general |compositing Product|frameworks-kwindowsystem|kwin Resolution|--- |INVALID Assignee|mgraess...@kde.org |kwin-bugs-n...@kde.org Version|5.34.0 |5.9.5 --- Comment #1 from Martin Flöser --- This is the expected behavior. For users disliking this behavior there is a config option to disable. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380016] The window can't be resized down
https://bugs.kde.org/show_bug.cgi?id=380016 Alex Bikadorovchanged: What|Removed |Added CC||alex.bikado...@kdemail.net --- Comment #1 from Alex Bikadorov --- Please post a screenshot. Is there some content in the window that prevents resizing? 1300pixel in width, I assume. What about height? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369157] Kmail2 doesn't work with Icons-Only task manager
https://bugs.kde.org/show_bug.cgi?id=369157 Denis Kurzchanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Component|general |misc Resolution|WAITINGFORINFO |--- Version|unspecified |5.4.3 --- Comment #3 from Denis Kurz --- The most recent version is 17.04.1 (should actually be 5.5.1), but I guess 16.12.3 (actually 5.4.3) is recent enough. Thank you for the quick respond and the new information. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380018] 'Stop all jobs' does not stop compilation (CMake, Makefile generator)
https://bugs.kde.org/show_bug.cgi?id=380018 Maciej Mrozowskichanged: What|Removed |Added Component|Build tools: CMake |Build tools: Make -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380018] New: 'Stop all jobs' does not stop compilation (CMake, Makefile generator)
https://bugs.kde.org/show_bug.cgi?id=380018 Bug ID: 380018 Summary: 'Stop all jobs' does not stop compilation (CMake, Makefile generator) Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: reave...@gmail.com Target Milestone: --- Steps to reproduce: 1. Open some CMake managed project and configure it to use Makefiles generator 2. Start compilation in KDevelop (Project->Build all or just selection) 3. Check 'top' in other terminal and number of compilation processes 4. In KDevelop, click 'Stop All'. 5. Build output will show: "make: *** [all] Terminated *** Killed process ***" 6. but hey.. check 'top' again. Code is still compiling, just like compilation processes were orphaned. Indeed they are. pstree shows that they went under PID 1. I haven't checked kdevelop code but I can bet you are sending SIGKILL instead of SIGINT, so 'make' doesn't have a chance to cleanup its children. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 --- Comment #3 from Dr. Chapatin--- Confirmed on plasma 5.10 beta built against qt 5.9 beta 3 on Arch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 Dr. Chapatinchanged: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380009] Pictures file repeats any picture interminably for ever paralyzing the whole computer.
https://bugs.kde.org/show_bug.cgi?id=380009 --- Comment #2 from diazbeat...@gmail.com --- Hi Elvis, Sorry, I am not a computer person, but I will try to explain the best I can. Every time I go to File Manager and click on a picture on the folder Pictures,the file with the picture I try to open starts repeating forever. When I try to close it I cannot do it just continue repeating again and again. I only can turn the computer off. The problem is that I don't want to lose my pictures. Sometimes I can return back and the situation continues and I have to turn the computer off more than one time. Once I return back and it is stable, I have to close the file one by one. Thank you, Beatriz On Fri, May 19, 2017 at 10:10 AM, Elvis Angelacciowrote: > https://bugs.kde.org/show_bug.cgi?id=380009 > > Elvis Angelaccio changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > CC||elvis.angelac...@kde.org > > --- Comment #1 from Elvis Angelaccio --- > Please describe exactly what you were doing. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 379068] Capability to check OpenType features
https://bugs.kde.org/show_bug.cgi?id=379068 --- Comment #1 from Esteban Adrián Pérez--- I think this missed feature it's a "must have" one today... Please, consider add it soon... All of we who needs to work with fonts (from graphic dessigner to technical writters crosing the wide spectre of others specialities) Thanks in advance... E. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380017] Can't change DateTime format in modified column
https://bugs.kde.org/show_bug.cgi?id=380017 Esteban Adrián Pérezchanged: What|Removed |Added CC||dgeape...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380016] The window can't be resized down
https://bugs.kde.org/show_bug.cgi?id=380016 Esteban Adrián Pérezchanged: What|Removed |Added CC||dgeape...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #4 from Alex Sidorenko--- Hi Michael, the upstream BZ says: "Pushed by arojas into branch 'Applications/17.04'" This essentially means that if Neon maintainers do not care about backporthing this bugfix to 17.04.1 (should be trivial), we will get the fixed package when 17.04.2 is released. According to https://community.kde.org/Schedules/Applications/17.04_Release_Schedule this is expected on Thursday, June 8, 2017 Alex -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 379068] Capability to check OpenType features
https://bugs.kde.org/show_bug.cgi?id=379068 Esteban Adrián Pérezchanged: What|Removed |Added CC||dgeape...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380002] Dolphin crashing
https://bugs.kde.org/show_bug.cgi?id=380002 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- What you were doing exactly when it crashed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380009] Pictures file repeats any picture interminably for ever paralyzing the whole computer.
https://bugs.kde.org/show_bug.cgi?id=380009 Elvis Angelacciochanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Please describe exactly what you were doing. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380017] New: Can't change DateTime format in modified column
https://bugs.kde.org/show_bug.cgi?id=380017 Bug ID: 380017 Summary: Can't change DateTime format in modified column Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: dgeape...@gmail.com Target Milestone: --- Hi!... I searched in Google before bored you with this, but I can't found a solution... I tried the Locale section in ~/.config/krusaderrc file without success... All my system show the date with 2 digits for day and month and the year (context depending) with 2 or 4 digits; and the time with 2 digits for hour and minutes in 24 hours format (without AM/PM) But krusader seems ignore it completely: shows the dates without precedent 0 (for 2 digits day or month from 1 to 9) and the time in 12 hours format... Is it another information you need to help you to fix it? Thanks in advance... E. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380016] New: The window can't be resized down
https://bugs.kde.org/show_bug.cgi?id=380016 Bug ID: 380016 Summary: The window can't be resized down Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: dgeape...@gmail.com Target Milestone: --- Hello... I can't resize the main window under 1300px. I'm using dual monitor, both with a resolution of 1280*1024... Here is a partial copy from my Krusader config file finded in ~/.config/krusaderrc [Private] Maximized=false ... Start Position=0,28 Start Size=1307,840 ... [Startup] Left Side Is Active=false Show Cmd Line=false Show FN Keys=true Show Terminal Emulator=false Show status bar=true Splitter Sizes=653,653 ... Terminal Emulator Splitter Sizes=722,0 Vertical Mode=false I tried modifying Start Size = 1001 and Splitter Sizes = 500,500 (I realized that Start Size = Spliter Sizes * 2 + 1) without success, and the file returns to the values showed before... Is it there other info you need to help you to fix that? :) Thank you in advance... E. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380015] New: Crash when setting ntp Mageia 5.1
https://bugs.kde.org/show_bug.cgi?id=380015 Bug ID: 380015 Summary: Crash when setting ntp Mageia 5.1 Product: systemsettings Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rpochm...@comcast.net Target Milestone: --- Application: systemsettings (4.11.16) KDE Platform Version: 4.14.30 Qt Version: 4.8.6 Operating System: Linux 4.4.65-desktop-1.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: - What I was doing when the application crashed: I had Just installed NTP via Rpmdrake, and was configuring NTP in System Settings, when I got the crash. The configuration utility wouldn't save the settings, it was stuck in a loop, I tried to save and quit three times, and then it crashed. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb54cbc8800 (LWP 377))] Thread 2 (Thread 0x7fb52803f700 (LWP 380)): #0 0x7fb549b79d6d in poll () at /lib64/libc.so.6 #1 0x7fb542b6aeb4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb542b6b232 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #3 0x7fb53f80f9b6 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #4 0x7fb542b90d75 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7fb542e365bd in start_thread () at /lib64/libpthread.so.0 #6 0x7fb549b8562d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb54cbc8800 (LWP 377)): [KCrash Handler] #5 0x7fb54a2dea62 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /lib64/libQtCore.so.4 #6 0x7fb54a2e686c in QSingleShotTimer::QSingleShotTimer(int, QObject*, char const*) () at /lib64/libQtCore.so.4 #7 0x7fb54a2e692e in QTimer::singleShot(int, QObject*, char const*) () at /lib64/libQtCore.so.4 #8 0x7fb52d9e22c3 in KclockModule::save() () at /usr/lib64/kde4/kcm_clock.so #9 0x7fb54c2ef697 in KCModuleProxy::save() () at /lib64/libkcmutils.so.4 #10 0x7fb54c0c4b23 in ModuleView::moduleSave(KCModuleProxy*) () at /lib64/libsystemsettingsview.so.2 #11 0x7fb54c0c64f5 in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.30] () at /lib64/libsystemsettingsview.so.2 #12 0x7fb54a2dd88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #13 0x7fb54bd4739f in KPushButton::authorized(KAuth::Action*) () at /lib64/libkdeui.so.5 #14 0x7fb54a2dd88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #15 0x7fb54b59de92 in QAbstractButton::clicked(bool) () at /lib64/libQtGui.so.4 #16 0x7fb54b2ff7f3 in QAbstractButtonPrivate::emitClicked() () at /lib64/libQtGui.so.4 #17 0x7fb54b300a70 in QAbstractButtonPrivate::click() () at /lib64/libQtGui.so.4 #18 0x7fb54b300b64 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQtGui.so.4 #19 0x7fb54af9b388 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4 #20 0x7fb54af4b79c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #21 0x7fb54af51f8e in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #22 0x7fb54bc7e40a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #23 0x7fb54a2c9cad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #24 0x7fb54af5166f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib64/libQtGui.so.4 #25 0x7fb54afc38b2 in QETWidget::translateMouseEvent(_XEvent const*) () at /lib64/libQtGui.so.4 #26 0x7fb54afc22ac in QApplication::x11ProcessEvent(_XEvent*) () at /lib64/libQtGui.so.4 #27 0x7fb54afe9442 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtGui.so.4 #28 0x7fb542b6ac6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #29 0x7fb542b6af18 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #30 0x7fb542b6afbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #31 0x7fb54a2f6e1e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #32 0x7fb54afe94f6 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #33 0x7fb54a2c8931 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #34 0x7fb54a2c8c45 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #35 0x7fb54a2cde59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4 #36 0x0040aa8c in main () Possible duplicates by query: bug 378162, bug 378019. Reported using
[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update
https://bugs.kde.org/show_bug.cgi?id=379796 NiOchanged: What|Removed |Added Status|RESOLVED|UNCONFIRMED CC||arco...@gmail.com Resolution|UPSTREAM|--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update
https://bugs.kde.org/show_bug.cgi?id=379796 --- Comment #4 from NiO--- I wanted to chime back in about this. I decided for no particular reason that I wanted to reformat my system and start a clean install of Neon. I ran into this issue again after a fresh install.. so it may be worth looking into. I installed Neon (neon-useredition-20170518-1018-amd64.iso), started it up for the first time with nomodeset in Grub (black screen on boot otherwise), and the first thing I did was new install Nvidia proprietary drivers 378.13 from the ppa (ppa:graphics-drivers/ppa). After install, I went to reboot from the launcher and ksmserver-logout-greeter immediately crashed. I had to reboot from the terminal. It seems that installing a driver update changes something that greeter doesn't expect to change, so it spazzes out. But then it's fine after rebooting (presumably when greeter reinitializes with the new changes). I think there is still some kind of exception handling that needs to be put into place to catch this. System info: ASRock H270M-ITX/ac, i7-6700k, GTX 970 Neon installed with encrypted home directory. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380005] Not detecting Windows Edge on first try
https://bugs.kde.org/show_bug.cgi?id=380005 --- Comment #3 from Martin Flöser--- Does it make a difference whether the window is maximized? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378320] SMIME/X509: Encrypted message Not enough information to check signature. %1(I18N_ARGUMENT_MISSING)
https://bugs.kde.org/show_bug.cgi?id=378320 --- Comment #9 from Dennis Schridde--- When I disable CRL checks, I can send S/MIME encrypted & signed emails. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378320] SMIME/X509: Encrypted message Not enough information to check signature. %1(I18N_ARGUMENT_MISSING)
https://bugs.kde.org/show_bug.cgi?id=378320 --- Comment #8 from Dennis Schridde--- When I enable S/MIME OCSP checks, I also see the following in the logs: ``` ... 4 - 2017-05-19 17:21:21 gpgsm[8356]: DBG: chan_10 -> ISVALID <> 4 - 2017-05-19 17:21:21 gpgsm[8356]: DBG: chan_10 <- ERR 167772220 Not supported ... 4 - 2017-05-19 17:21:36 gpgsm[8562]: DBG: chan_10 -> ISVALID <> 4 - 2017-05-19 17:21:36 gpgsm[8562]: DBG: chan_10 <- ERR 167772220 Not supported 4 - 2017-05-19 17:21:36 gpgsm[8562]: certificate <> 4 - 2017-05-19 17:21:36 gpgsm[8562]: checking the CRL failed: Not supported 4 - 2017-05-19 17:21:36 gpgsm[8562]: validation model used: shell ... ``` -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378745] s/mime x509: could not compose message: Nicht gefunden (en: not found)
https://bugs.kde.org/show_bug.cgi?id=378745 --- Comment #3 from Dennis Schridde--- In my KWatchGnuPG logs, I found following messages that somewhat relate to "not found": ``` ... failed to open '/home/<>/.gnupg/policies.txt': No such file or directory ... 4 - 2017-05-19 17:13:09 gpgsm[3596]: DBG: chan_10 <- INQUIRE SENDCERT <<...>> 4 - 2017-05-19 17:13:09 gpgsm[3596]: certificate not found: Ambiguous name 4 - 2017-05-19 17:13:09 gpgsm[3596]: DBG: chan_10 -> CAN 4 - 2017-05-19 17:13:09 gpgsm[3596]: DBG: chan_10 <- ERR 167772217 Missing certificate ... [client at fd 4 connected (local)] 4 - 2017-05-19 17:13:09 gpg[3601]: enabled debug flags: memstat 4 - 2017-05-19 17:13:09 gpg[3601]: error reading key: No public key 4 - 2017-05-19 17:13:09 gpg[3601]: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 4 - 2017-05-19 17:13:09 outmix=0 getlvl1=0/0 getlvl2=0/0 4 - 2017-05-19 17:13:09 gpg[3601]: secmem usage: 0/65536 bytes in 0 blocks [client at fd 4 disconnected] ... 4 - 2017-05-19 17:13:12 gpgsm[3711]: failed to open '/home/<>/.gnupg/policies.txt': No such file or directory 4 - 2017-05-19 17:13:12 gpgsm[3711]: Note: non-critical certificate policy not allowed ... 4 - 2017-05-19 17:13:12 gpgsm[3711]: checking the CRL failed: Not found 4 - 2017-05-19 17:13:12 gpgsm[3711]: validation model used: shell ... ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337690] QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9
https://bugs.kde.org/show_bug.cgi?id=337690 --- Comment #3 from Martin Flöser--- Sorry, there's nothing we can do. The warning is thrown by Qt. Qt should use categorized logging so that it can be suppressed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380005] Not detecting Windows Edge on first try
https://bugs.kde.org/show_bug.cgi?id=380005 --- Comment #2 from richardlm--- $ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.9.5 Qt Version: 5.8.0 Qt compile version: 5.8.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11704000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 7, 9, 6, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 3 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 3 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 2 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 1 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: DisplayPort-0 Geometry: 0,0,2560x1440 Refresh Rate: 143.856 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD FIJI (DRM 3.3.0 / 4.8.6-1-CHAKRA, LLVM 3.9.1) OpenGL version string: 4.3 (Core Profile) Mesa 13.0.2 OpenGL platform interface: GLX OpenGL shading language version string: 4.30 Driver: Unknown GPU class: Unknown OpenGL version: 4.3 GLSL version: 4.30 Mesa version: 13.0.2 X server version: 1.17.4 Linux kernel version: 4.8.6 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 --- Comment #3 from hering2...@web.de --- Created attachment 105642 --> https://bugs.kde.org/attachment.cgi?id=105642=edit kwinrc Added kwinrc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 --- Comment #2 from hering2...@web.de --- Created attachment 105641 --> https://bugs.kde.org/attachment.cgi?id=105641=edit qdbus log Here is the qdbus output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 Martin Flöserchanged: What|Removed |Added Component|platform-x11-standalone |general --- Comment #1 from Martin Flöser --- Please provide output of qdbus org.kde.KWin /KWin supportInformation And in addition your kwinrc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379975] PNG transparency not available with multiple layers
https://bugs.kde.org/show_bug.cgi?id=379975 woltherachanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- You need to be able to see the transparency checkers if you want to save with transparency: https://docs.krita.org/Saving_for_the_Web -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 251180] Fails at attempts to make backups.
https://bugs.kde.org/show_bug.cgi?id=251180 Janetchanged: What|Removed |Added CC|bugzi...@kerridis.de| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378745] s/mime x509: could not compose message: Nicht gefunden (en: not found)
https://bugs.kde.org/show_bug.cgi?id=378745 Dennis Schriddechanged: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337690] QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9
https://bugs.kde.org/show_bug.cgi?id=337690 hering2...@web.de changed: What|Removed |Added CC||hering2...@web.de --- Comment #2 from hering2...@web.de --- Unfortunately it is filling up my journal to the point that I have to use a script to delete those lines before the size explodes to several gigabytes every day... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378320] SMIME/X509: Encrypted message Not enough information to check signature. %1(I18N_ARGUMENT_MISSING)
https://bugs.kde.org/show_bug.cgi?id=378320 Dennis Schriddechanged: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380014] New: QObject::startTimer: Timers cannot be started from another thread
https://bugs.kde.org/show_bug.cgi?id=380014 Bug ID: 380014 Summary: QObject::startTimer: Timers cannot be started from another thread Product: plasmashell Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: hering2...@web.de Target Milestone: 1.0 I am seeing some "plasmashell[848]: QObject::startTimer: Timers cannot be started from another thread" in my journal. Not sure why it is happening though or what might cause it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] New: Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 Bug ID: 380013 Summary: Could not locate service type file kservicetypes5/kwin-effect.desktop Product: kwin Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: hering2...@web.de Target Milestone: --- Recently I keep seeing lots of kwin_x11[844]: kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/kwin-effect.desktop, tried ("/home/hering/.local/share", "/usr/share", "/usr/local/share") in my journal. This happens when Composer gets disabled and enabled again and happens on new installations as well. It might not be a severe bug but it does spam the journal. I am running the arch packages of plasma including kwin_x11. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 naworsk...@gmail.com changed: What|Removed |Added Summary|CalDAV Sync not Working |CalDAV-sync not working |with Communigate|with Communigate -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] New: CalDAV Sync not Working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Bug ID: 380012 Summary: CalDAV Sync not Working with Communigate Product: Akonadi Version: 5.5.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: naworsk...@gmail.com Target Milestone: --- Created attachment 105640 --> https://bugs.kde.org/attachment.cgi?id=105640=edit akonadi-konsole debbuging-output I cannot Sync my CalDAV ressources from a "Communigate-Pro" (CGP) Server (unkown Version) on my Work. Environment: - multiple Devices with KDE-Neon and Arch. More detailed description/What I've tried: 1. Kontact/Korganizer/Akonadi recognizes the calendar/task-folders, but I can't see any events/tasks. 2. I can create events/tasks in KOrganizer which are (and stay) visible and actually "really" created on the Server. I checked it with the CGP Web-Client ("Pronto"?), "Thunderbird Lightning" and/or "DavDroid". 3. So the only events/tasks that are visible in KOrganizer are the ones created in the current running Installation. 4. Changes on this events/tasks with other Installations/Clients are not synced. If I modify a created and visible event/task in Korganizer it will overwrite changes that are made with other Clients. 5. I can also "delete" the visible events in Korganizer, but they're not really deleted from the Server. (checked like in 2.) Side-Notes: - Issues 1-4 are new, it worked before the last updates. Issue 5 was older but it did not annoy me that much. - Owncloud (9.1.0) resources are working as expected with KOrganizer/Akonadi. - Thunderbird Lightning and DAVDroid are working the affected resources (CGP). - Same Behaviour with Arch-Linux (also same Akonadi Version) - Attachment: (Anonymized) Debbuging Output from Akonadi-Konsole while refreshing/syncing the affected resource in KOrganizer. - In general i'd like to thank you for this great piece of software. I really love to use it. Unfortunately this Bug is a really big issue for me :( -- You are receiving this mail because: You are watching all bug changes.
[blogilo] [Bug 380011] New: Blogilio crashes when manipulating images
https://bugs.kde.org/show_bug.cgi?id=380011 Bug ID: 380011 Summary: Blogilio crashes when manipulating images Product: blogilo Version: 1.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: xmu...@ldktn.com Target Milestone: --- Application: blogilo (1.1) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: I was trying to get an image set in the blog entry. However, when trying to move it, or resize it, the application crashes. This is consistent. The crash can be reproduced every time. -- Backtrace: Application: Blogilo (blogilo), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcf233ff940 (LWP 18035))] Thread 5 (Thread 0x7fce3649a700 (LWP 18087)): #0 0x7fcf1d1b149d in poll () from /lib64/libc.so.6 #1 0x7fcf1a572314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcf1a57242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcf1e66bfce in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7fcf1e63dd3f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #5 0x7fcf1e63e035 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7fcf1e53b49f in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7fcf1e53db7f in ?? () from /usr/lib64/libQtCore.so.4 #8 0x7fcf197c7744 in start_thread () from /lib64/libpthread.so.0 #9 0x7fcf1d1b9d3d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fcebda23700 (LWP 18086)): #0 0x7fcf197cc0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcebe0e782b in ?? () from /usr/lib64/libQtScript.so.4 #2 0x7fcebe0e7869 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x7fcf197c7744 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcf1d1b9d3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fcebf9f2700 (LWP 18085)): #0 0x7fcf197cc0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcf2204e95d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7fcf22303806 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7fcf197c7744 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcf1d1b9d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fcf002f5700 (LWP 18080)): #0 0x7fcf197cc0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcf222dbcb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7fcf222dbce9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7fcf197c7744 in start_thread () from /lib64/libpthread.so.0 #4 0x7fcf1d1b9d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcf233ff940 (LWP 18035)): [KCrash Handler] #6 0x7fcf1e63f16d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #7 0x7fcf1da50ca0 in ?? () from /usr/lib64/libQtGui.so.4 #8 0x7fcf1da4f6bc in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #9 0x7fcf1da76552 in ?? () from /usr/lib64/libQtGui.so.4 #10 0x7fcf1a572134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #11 0x7fcf1a572388 in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7fcf1a57242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7fcf1e66bfae in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #14 0x7fcf1da76606 in ?? () from /usr/lib64/libQtGui.so.4 #15 0x7fcf1e63dd3f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #16 0x7fcf1e63e035 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #17 0x7fcf1e643489 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #18 0x0041e311 in main (argc=5, argv=0x7ffce806d5d8) at /usr/src/debug/kdepim-4.14.10/blogilo/src/main.cpp:63 Possible duplicates by query: bug 374466, bug 368137, bug 363687. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 380010] New: Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist.
https://bugs.kde.org/show_bug.cgi?id=380010 Bug ID: 380010 Summary: Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist. Product: frameworks-kwindowsystem Version: 5.34.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: unsuspicious.fakename+kdeb...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- ( See https://bugs.kde.org/show_bug.cgi?id=349910 for when this was implemented. ) As far as I can tell, ALL compositing is turned off completely if a window has "_NET_WM_BYPASS_COMPOSITOR flag 1". In contrast to that, the specifications (https://specifications.freedesktop.org/wm-spec/latest/ar01s05.html#idm139870829920368) might encourage applications to use the flag "generously" ("The Client MAY set this property to hint the compositor that the window would benefit from running uncomposited"). Nothing suggests that this might / should trigger actions which are generally disruptive to the user experience or able to affect the whole Desktop / other windows. Accordingly, there is no indicator that the flag should or would be used sparingly or carefully by applications. P.E.: SDL and allegro appear to use it by default, because - according to the code comments: "/* This seems like a good idea */". Even for windowed applications that work perfectly fine with compositing enabled. Considering this, what does not seem like an especially good idea is: deactivating essential features of KDE without asking the user first - as a default - every time an application uses that flag. There should probably be - at the very least - a clear indicator that makes it obvious to the user that compositing has been turned off due to a window hint, so users know why their [Desktop Switching / Accessibility Features / WM Hotkeys] suddenly stopped working, can find out how to fix it (shift+alt+F12) and how to deactivate the behavior (more actions => window manager settings => "allow application to block compositing"). According to the specifications it appears to be the responsibility of the compositing manager to decide wether it is a good idea to grant the "wish" of the application with the flag at a given time. One relatively simple addition to mitigate potential problems therefore might be to honor the flag only from visible full-screen windows that have input focus ("steam" appears to have a heuristic detection as a counterpart that does that and goes a bit further, I think?). Also a more prominent, system-wide option to "disallow applications to block compositing by default" could be useful for people who prefer to remain in full control of it. Optimally, if it is possible at all, then all reactions to "_NET_WM_BYPASS_COMPOSITOR 1" should probably affect ONLY the window that has the flag and nothing else (**I haven't encountered any problems with compositing for a long time though, so I can't guess what trade-offs would be of allowing the necessary kinds of redirection). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #3 from bluelupo--- Hi Alex, a question yet, in which version exactly is the error in KDE Neon then fixed? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379988] TNEF attachments not properly represented in UI
https://bugs.kde.org/show_bug.cgi?id=379988 Laurent Montelchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||pim-addons/648a48afbb50187c ||18d9452433549ae660f12b08 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.5.2 Resolution|--- |FIXED --- Comment #4 from Laurent Montel --- Git commit 648a48afbb50187c18d9452433549ae660f12b08 by Montel Laurent. Committed on 19/05/2017 at 14:29. Pushed by mlaurent into branch 'Applications/17.04'. Fix Bug 379988 - TNEF attachments not properly represented in UI FIXED-IN: 5.5.2 M +1-1 plugins/messageviewer/bodypartformatter/ms-tnef/application_ms-tnef.cpp https://commits.kde.org/kdepim-addons/648a48afbb50187c18d9452433549ae660f12b08 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380009] New: Pictures file repeats any picture interminably for ever paralyzing the whole computer.
https://bugs.kde.org/show_bug.cgi?id=380009 Bug ID: 380009 Summary: Pictures file repeats any picture interminably for ever paralyzing the whole computer. Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: diazbeat...@gmail.com Target Milestone: --- Opera Version 42.0.2393.85 - New version 45.0.2552.812 is available Update stream: Stable System: Ubuntu 16.04.1 LTS (x86_64; KDE) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 Mircea Kitsunechanged: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #7 from Mircea Kitsune --- Important: This is a mirrored report of an older issue, which has been happening for nearly 3 months now. I decided to post it here as well because it seems like it might be KDE related, considering only Plasma Desktop / KWin appears to trigger this specific crash. The original reports with openSUSE and OpenDesktop can be found below, their comments contain more information about what has been happening as I've been noticing it: https://bugzilla.opensuse.org/show_bug.cgi?id=1028575 https://bugs.freedesktop.org/show_bug.cgi?id=100306 This is a major problem and I'm trying to find a solution for it ASAP! Any feedback worth sharing is welcome, and I'd like to know of any possible fix or workaround. Please don't suggest desktop compositing however, as I've already verified that the issue takes place with it turned off. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #6 from Mircea Kitsune--- Created attachment 105639 --> https://bugs.kde.org/attachment.cgi?id=105639=edit lspci -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #5 from Mircea Kitsune--- Created attachment 105638 --> https://bugs.kde.org/attachment.cgi?id=105638=edit dmesg -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #3 from Mircea Kitsune--- Created attachment 105636 --> https://bugs.kde.org/attachment.cgi?id=105636=edit xsession-errors-:0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #4 from Mircea Kitsune--- Created attachment 105637 --> https://bugs.kde.org/attachment.cgi?id=105637=edit journalctl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #2 from Mircea Kitsune--- Created attachment 105635 --> https://bugs.kde.org/attachment.cgi?id=105635=edit Xorg.0.log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #1 from Mircea Kitsune--- Created attachment 105634 --> https://bugs.kde.org/attachment.cgi?id=105634=edit Xorg.0.log.old -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 380008] New: System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 Bug ID: 380008 Summary: System randomly freezes or crashes to the login screen, glitches until rebooted Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: --- Approximately once every 1 to 3 days of uptime, the system experiences a sudden and inexplicable crash: The image completely freezes in place, although unlike similar crashes in the past I can keep moving the mouse pointer around. A few seconds afterward, I find myself in a black console... and a few seconds after that, I'm back at the login screen. If I attempt to log back in however, the image either freezes again or desktop effects are no longer working without any error message as to why. Not even forcefully restarting X11 (control + alt + backspace twice) fixes the remaining glitches, and the only way to truly recover the system is to also reboot. The crashes are completely random, but always caused by a desktop event... however it is not exclusive to desktop effects! The freeze will occur even with compositing completely disabled, although slightly more rarely. It seems to occur either when some desktop effects are playing (like the desktop switching cube animation) but it's usually when I select a new window or a panel pops up (alt-tab switching to another window can alone trigger this). I use the free video drivers and default system packages, all latest versions of openSUSE Tumbleweed. My card is a Radeon R7 370, GCN 1.0 on RadeonSI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380005] Not detecting Windows Edge on first try
https://bugs.kde.org/show_bug.cgi?id=380005 Martin Flöserchanged: What|Removed |Added Component|compositing |core --- Comment #1 from Martin Flöser --- please provide output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 Vit Pelcakchanged: What|Removed |Added Version|Other (add details in bug |17.04.0 |description)| --- Comment #3 from Vit Pelcak --- The issue is still here. I can confirm for Gentoo 16.12.3 and openSUSE in version 17.04. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 Vit Pelcakchanged: What|Removed |Added CC||v...@pelcak.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 380007] Improvements for Gettext entries wordwrapping
https://bugs.kde.org/show_bug.cgi?id=380007 --- Comment #3 from Azamat H. Hackimov--- Created attachment 105633 --> https://bugs.kde.org/attachment.cgi?id=105633=edit 0003-Simplify-code-where-we-need-to-add-empty-line.patch -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 380007] Improvements for Gettext entries wordwrapping
https://bugs.kde.org/show_bug.cgi?id=380007 --- Comment #2 from Azamat H. Hackimov--- Created attachment 105632 --> https://bugs.kde.org/attachment.cgi?id=105632=edit 0002-Reworking-word-wrapping-for-Gettext-catalog.patch -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 380007] Improvements for Gettext entries wordwrapping
https://bugs.kde.org/show_bug.cgi?id=380007 --- Comment #1 from Azamat H. Hackimov--- Created attachment 105631 --> https://bugs.kde.org/attachment.cgi?id=105631=edit 0001-Count-separator-during-word-wrapping-in-PO.patch -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 380007] New: Improvements for Gettext entries wordwrapping
https://bugs.kde.org/show_bug.cgi?id=380007 Bug ID: 380007 Summary: Improvements for Gettext entries wordwrapping Product: lokalize Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: editor Assignee: sha...@ukr.net Reporter: azamat.hacki...@gmail.com Target Milestone: --- These series of patches improves word wrapping code for Gettext catalog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379978] Runtime error
https://bugs.kde.org/show_bug.cgi?id=379978 --- Comment #2 from Ray--- Thanks for the prompt reply. Ray On Thu, May 18, 2017 at 9:09 PM, Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=379978 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > Hi Ray, > > Please update to 3.1.3. 3.0.1.1 is pretty old by now! Also, run a memory > checker. If things suddenly start getting unstable, it's probably not that > the > application suddenly develops bugs. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 379996] IMAP resource chrashing when trying to configure
https://bugs.kde.org/show_bug.cgi?id=379996 Gerd Fleischerchanged: What|Removed |Added CC||gerdfleisc...@web.de --- Comment #4 from Gerd Fleischer --- No backtrace window. Just nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378315] KMail crash on logout
https://bugs.kde.org/show_bug.cgi?id=378315 --- Comment #6 from Gerd Fleischer--- The crash was with 5.8.0 Now 5.7.1 no crashes. -- You are receiving this mail because: You are watching all bug changes.