[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #11 from Alex Turbov --- Janek Bevendorff, I've tried your buggy snippet w/ kate 4, and can't reproduce... unfortunately I have no idea whats changed in KF5/Plasma5 version of kate... I still use C++/boost indenter w/ Kate 4 and can't migrate while there is no Python support %( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #12 from Alex Turbov --- I'll fix as soon as it would be possible to me to move to kate5. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 365800] Since I moved to Kubuntu 16.04, kaddressbook crashes.
https://bugs.kde.org/show_bug.cgi?id=365800 --- Comment #9 from Hans-Peter Guggenbichler --- I did this: rm -r ~/.local/share/akonadi rm -r ~/.config/akonadi rm -r ~/.kde/share/apps/nepomuk rm -r ~/.kde/share/apps/akonadi_nepomuk_feeder rm -r ~/.kde/share/config/nepomuk* rm -r ~/.kde/share/config/akona* I don't know, if this still is the correct way to do it, because I worked this out a few months (years??) ago. But it did the job this time. If you want to be shure to hit all the akonadi related stuff, just do a find in your home directory for akonadi. Akonadi stores info about your emails, mainboxes, contacts, ... in its own databases. By removing these databases you don't remove your emails, contacts, ... Thats why you emails disappeared in kmail. akonadi first had to crawl your file system and search for all the information and build its database. Once this jas finished, your emails reappeared in kmail. When I wiped akonadi, I recognized, that some config got lost, unfortunately. So I had to use akonadiconsole to restart the Birthday agent, the Local Contacts agent. And I had to reconfig the pop3 account in kmail. So you have to have a close look at your system after removing the akonadi files. Until now, I've lost no information afer removing akonadi, fingers crossed. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 370959] Dolphin crashes when trying to extract a rar archive file.
https://bugs.kde.org/show_bug.cgi?id=370959 --- Comment #3 from Stephane Couturier --- sorry I forgot to mention: - yes, unrar is installed - in Konsole, "unrar x rar_archive_filename" works fine, the files are extracted correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Khaymi Pavel changed: What|Removed |Added CC|drea...@vniiftri.ru | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 346135] Kmail support for DarkThemes and HTML-Mails
https://bugs.kde.org/show_bug.cgi?id=346135 Samuel Suther changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #4 from Samuel Suther --- I've switched to Manjaro-Linux. In meantime, i've switched to Thunderbird, because I don't wan't the overhead of akonadi in KDE anymore. What shouly I say, Thunderbird just works. I do not regret to switch. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 370990] New: Firefox e Kmail.
https://bugs.kde.org/show_bug.cgi?id=370990 Bug ID: 370990 Summary: Firefox e Kmail. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucianomari...@gmail.com Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-43-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Every time I make a file download programs ranging crash and kwin_x11 crashes The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8222b4e8c0 (LWP 1729))] Thread 2 (Thread 0x7f80d798e700 (LWP 2174)): [KCrash Handler] #6 QVector::reallocData (this=0x7f80d798daa0, asize=-100653488, aalloc=, options=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:514 #7 0x7f8221d3e896 in QVector::resize (asize=, this=0x7f80d798daa0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:386 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f80d798d9ef, arr=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/codecs/postingcodec.cpp:40 #9 0x7f8221d2a814 in Baloo::PostingDB::get (this=this@entry=0x7f80d798dad0, term=...) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/postingdb.cpp:100 #10 0x7f8221d3b3c6 in Baloo::WriteTransaction::commit (this=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/writetransaction.cpp:277 #11 0x7f8221d33032 in Baloo::Transaction::commit (this=this@entry=0x7f80d798dbd0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/engine/transaction.cpp:262 #12 0x0041c8e0 in Baloo::NewFileIndexer::run (this=0x18250c0) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/newfileindexer.cpp:75 #13 0x7f8221651343 in QThreadPoolThread::run (this=0x1d43c10) at thread/qthreadpool.cpp:93 #14 0x7f822165484e in QThreadPrivate::start (arg=0x1d43c10) at thread/qthread_unix.cpp:331 #15 0x7f82202b86fa in start_thread (arg=0x7f80d798e700) at pthread_create.c:333 #16 0x7f8220c61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8222b4e8c0 (LWP 1729)): #0 0x7f8220c519cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f821de69740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f821de25e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f821de26340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f821de264ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f822188ba7f in QEventDispatcherGlib::processEvents (this=0x17a4fe0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #6 0x7f8221832dea in QEventLoop::exec (this=this@entry=0x7ffd970d5e80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f822183ae8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #8 0x0041698c in main (argc=1, argv=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/file/main.cpp:88 Possible duplicates by query: bug 356445. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370676] Screenlock: no input widgets, loginctl unlock-session not working
https://bugs.kde.org/show_bug.cgi?id=370676 Tommi Tervo changed: What|Removed |Added Ever confirmed|0 |1 CC||tommi.te...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Tommi Tervo --- I've same problem, dual-head setup. ThinkPad x230 & OpenSUSE 42.1. Enabling modeset does not help systool -m i915 -av Module = "i915" Attributes: coresize= "1204224" initsize= "0" initstate = "live" refcnt = "8" srcversion = "17F9DEDA72F2C053AD17DFB" taint = "" uevent = Parameters: disable_display = "N" disable_power_well = "1" disable_vtd_wa = "N" enable_cmd_parser = "1" enable_execlists= "0" enable_fbc = "-1" enable_hangcheck= "Y" enable_ips = "1" enable_ppgtt= "1" enable_psr = "0" enable_rc6 = "3" fastboot= "N" invert_brightness = "0" load_detect_test= "N" lvds_channel_mode = "0" lvds_downclock = "0" lvds_use_ssc= "-1" mmio_debug = "0" modeset = "1" nuclear_pageflip= "N" panel_ignore_lid= "1" prefault_disable= "N" preliminary_hw_support= "1" reset = "Y" semaphores = "-1" use_mmio_flip = "0" vbt_sdvo_panel_type = "-1" verbose_state_checks= "Y" -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
https://bugs.kde.org/show_bug.cgi?id=367639 --- Comment #51 from Thomas Schmitt --- http://commits.kde.org/k3b/15d3b05ce24a9158e120d4eaf0caadb0407fc0e7 looks good to me. Now we'd need a tester who confirms that DVD-RAM can be used for multi-session like DVD+RW. (BD-R RRM might be hard to achieve and possibly were never tested with growisofs. But maybe somebody still has a DVD-RAM on the shelf.) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370651] Dependency lines not shown correctly
https://bugs.kde.org/show_bug.cgi?id=370651 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Version Fixed In||2.18.80 (KDE Applications ||16.03.80) Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Ralf Habacker --- *** This bug has been marked as a duplicate of bug 360531 *** -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 360531] Line Styles are not correctly created initially and restored from file
https://bugs.kde.org/show_bug.cgi?id=360531 Ralf Habacker changed: What|Removed |Added CC||c...@roberthairgrove.com --- Comment #8 from Ralf Habacker --- *** Bug 370651 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 370991] New: Black screen coming out of sleep
https://bugs.kde.org/show_bug.cgi?id=370991 Bug ID: 370991 Summary: Black screen coming out of sleep Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rajind...@hotmail.com Put system into RAM suspend from the taskbar, wait several hours and wake up system. I see a black screen with a mouse pointer that I can move around, nothing else. I am unable to login my system and forced to do a cold reboot. Using Kubuntu 16.04.01 KDE Plasma: 5.5.5 Qt Ver: 5.5.1 Kernel: 4.4.0-43-generic Reproducible: Sometimes Steps to Reproduce: 1. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 370991] Black screen coming out of sleep
https://bugs.kde.org/show_bug.cgi?id=370991 --- Comment #1 from Rajinder Yadav --- My system is set to request a password to login, so could be issues with login screen or window system, note the mouse is visible and responds to mouse moves. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 370747] Plasma freezes in attempt to store password for this user only to VPN
https://bugs.kde.org/show_bug.cgi?id=370747 --- Comment #1 from Jan Grulich --- This sounds like an issue between Qt and your hardware, I'm not able to reproduce this and also nobody else seems to experience this as I read about this problem for the first time. Was this working for you before? Let's say with Plasma 5.6 or Plasma 5.5? Or is it happening in any other configuration, e.g. when configuring a wireless connection and filling WEP/WPA password? Also, thanks to you I noticed that after importing OpenVPN connection we set that we should ask for the password everytime, instead of defaulting to storing it into KWallet. I fixed this already and it should kinda workaround your problem, because you don't have to switch from "Always ask" to "Store the password for this user", but still would be nice to figure out what's going on. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370705] Current Album is deselected when clearing search bar
https://bugs.kde.org/show_bug.cgi?id=370705 Frédéric COIFFIER changed: What|Removed |Added CC||frederic.coiff...@free.fr --- Comment #3 from Frédéric COIFFIER --- Gilles, No, I have no filter in this case. And yes, I'm using the search bar under the album tree view. It's strange that you cannot reproduce it : I can reproduce it with the old Digikam 4.14 on Fedora 23 (in fact, it's an old bug which is still present in Digikam 5). To be more accurate : 1. Select an album (i.e. Apples) 2. Type three letters like 'ban' (the search bar is green) 3. Click on album Banana to view it 4. Click on 'clear' icon in the search bar 5. Album Apples is selected automatically... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 370857] WiFi is always connecting and never stop
https://bugs.kde.org/show_bug.cgi?id=370857 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #3 from Jan Grulich --- What are yours NetworkManager and NetworkManagerQt (or kf5-networkmanager-qt or how this package is called in OpenSuse) versions? -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 362646] When video is paused goes blank
https://bugs.kde.org/show_bug.cgi?id=362646 --- Comment #2 from Rajinder Yadav --- It's there a time line to get this resolved? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 300557] When a collection is updated, Amarok expands collapsed entries in the Collection Browser
https://bugs.kde.org/show_bug.cgi?id=300557 --- Comment #11 from Piotr Keplicz --- Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 Henri changed: What|Removed |Added CC||cer...@luukku.com --- Comment #1 from Henri --- I can reproduce with opensuse tumbleweed, kwalletmanager5-16.08.1-1.2.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 Freddy Rietdijk changed: What|Removed |Added CC||fr...@fridh.nl --- Comment #2 from Freddy Rietdijk --- I can reproduce on NixOS Unstable. Frameworks 5.26.0, Apps 16.08.1, Qt 5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 370857] WiFi is always connecting and never stop
https://bugs.kde.org/show_bug.cgi?id=370857 --- Comment #4 from Guo Yunhe (郭云鹤) --- NetworkManager: 1.0.6 libKF5NetworkManagerQt6: 5.27.0 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 370708] alarms disappeared after disk full
https://bugs.kde.org/show_bug.cgi?id=370708 --- Comment #2 from turcovadio --- Hi, again As you know, it is possible to prevent the complete losing of information in a case of full disk. It is logical to lose some information in the case of creating new alarms (in a full disk scenario), but now what remains in a full disk scenario is the deleted alarms. All the active alarms disappear. I think it is a good policy, when updating new alarms, keep the old file, create a new one, and after being successful, change the old file to the new one. In a case of a crash or full disk, create the possibility to recover the old file. Of course this is not new to you. What you surely didn't remember is that the disks can become full. Anyway, Kalarm is a great program. Thank you for your reply. Luis Duarte 2016-10-16 17:41 GMT+01:00 David Jarvie via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=370708 > > --- Comment #1 from David Jarvie --- > KAlarm is probably not the only application which can potentially lose data > when the disk becomes full. This is due to the way that files on disk are > updated - unless it's just a case of appending data to the end of a file, > when > a file is updated it is completely rewritten in an empty part of the disk > and > then the old data is marked as free. This handled by the file system > itself, > and it may not be possible to prevent data loss in such cases other than by > creating a new file with the new data, checking whether that succeeded, and > then deleting the old file only if it did succeed. This may not be > compatible > with the way that Akonadi (which handles file updates) works. This needs > investigation. > > In the meantime, the best advice it to always keep backups of important > data, > and don't let your disk fill up completely. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370992] New: Search is broken in Application Dashboard
https://bugs.kde.org/show_bug.cgi?id=370992 Bug ID: 370992 Summary: Search is broken in Application Dashboard Product: plasmashell Version: 5.7.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: sud...@sudhirkhanger.com CC: plasma-b...@kde.org When I search for a file in the AppDash it show me results of directories and files that have never been opened. It would show me pretty random files say from sdk folder which would typically contain like 10k text files but it never shows me one file that I open everyday and is available in the recent document history too. Reproducible: Always Steps to Reproduce: 1. open a document which will probably get added in recent document 2. search for the document 3. Actual Results: The recent document or any useful document opened by a user are never shown in the app dash search instead it shows random files from sdk folder or bookmarks. Expected Results: At least recent documents should get much more priority. Priority of files that have never been opened should be severely reduced. Please see the attached image. For example, I open the file Udacity Ap.. everyday. If you look for that file you won't find it in the search results shown by AppDash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370992] Search is broken in Application Dashboard
https://bugs.kde.org/show_bug.cgi?id=370992 --- Comment #1 from Sudhir Khanger --- Created attachment 101596 --> https://bugs.kde.org/attachment.cgi?id=101596&action=edit screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370993] New: KDevelop crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=370993 Bug ID: 370993 Summary: KDevelop crashes shortly after startup Product: kdevelop Version: 5.0.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andras.vuk...@gmail.com Application: kdevelop (5.0.1) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.7.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: KDevelop crashes immediately after opening a project (either from an existing .kdev4 file or from a CMakeLists.txt). It doesn’t seem to get to the point of loading the project (listing the files, etc.), but the window remains completely empty. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f925439d800 (LWP 28214))] Thread 15 (Thread 0x7f91ee9a6700 (LWP 28390)): #0 0x7f9251152455 in sysmalloc () at /usr/lib/libc.so.6 #1 0x7f92511533dd in _int_malloc () at /usr/lib/libc.so.6 #2 0x7f9251154d44 in malloc () at /usr/lib/libc.so.6 #3 0x7f91de9bf282 in () at /usr/lib/libclang.so.3.8 #4 0x7f91de9bf813 in () at /usr/lib/libclang.so.3.8 #5 0x7f91de9cf57d in () at /usr/lib/libclang.so.3.8 #6 0x7f91de9d6b37 in () at /usr/lib/libclang.so.3.8 #7 0x7f91de9d90fd in () at /usr/lib/libclang.so.3.8 #8 0x7f91de850f14 in () at /usr/lib/libclang.so.3.8 #9 0x7f91de8826fd in () at /usr/lib/libclang.so.3.8 #10 0x7f91de8829d4 in () at /usr/lib/libclang.so.3.8 #11 0x7f91dec750d6 in () at /usr/lib/libclang.so.3.8 #12 0x7f91dec748e9 in () at /usr/lib/libclang.so.3.8 #13 0x7f91dec74959 in () at /usr/lib/libclang.so.3.8 #14 0x7f91decb50c9 in () at /usr/lib/libclang.so.3.8 #15 0x7f91decb26cf in () at /usr/lib/libclang.so.3.8 #16 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #17 0x7f91decb7629 in () at /usr/lib/libclang.so.3.8 #18 0x7f91decb7d9e in () at /usr/lib/libclang.so.3.8 #19 0x7f91decb7dd2 in () at /usr/lib/libclang.so.3.8 #20 0x7f91decb23f2 in () at /usr/lib/libclang.so.3.8 #21 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #22 0x7f91decb2994 in () at /usr/lib/libclang.so.3.8 #23 0x7f91decb5fe6 in () at /usr/lib/libclang.so.3.8 #24 0x7f91decb228b in () at /usr/lib/libclang.so.3.8 #25 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #26 0x7f91decb7629 in () at /usr/lib/libclang.so.3.8 #27 0x7f91decb7d9e in () at /usr/lib/libclang.so.3.8 #28 0x7f91decb992e in () at /usr/lib/libclang.so.3.8 #29 0x7f91decb9bb4 in () at /usr/lib/libclang.so.3.8 #30 0x7f91decb21a8 in () at /usr/lib/libclang.so.3.8 #31 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #32 0x7f91decb7629 in () at /usr/lib/libclang.so.3.8 #33 0x7f91decb7d9e in () at /usr/lib/libclang.so.3.8 #34 0x7f91decb7dd2 in () at /usr/lib/libclang.so.3.8 #35 0x7f91decb23f2 in () at /usr/lib/libclang.so.3.8 #36 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #37 0x7f91decb2994 in () at /usr/lib/libclang.so.3.8 #38 0x7f91decb5fe6 in () at /usr/lib/libclang.so.3.8 #39 0x7f91decb228b in () at /usr/lib/libclang.so.3.8 #40 0x7f91decb2867 in () at /usr/lib/libclang.so.3.8 #41 0x7f91decb7629 in () at /usr/lib/libclang.so.3.8 #42 0x7f91decba41a in () at /usr/lib/libclang.so.3.8 #43 0x7f91dec37be8 in () at /usr/lib/libclang.so.3.8 #44 0x7f91decc5bb1 in () at /usr/lib/libclang.so.3.8 #45 0x7f91decc695f in () at /usr/lib/libclang.so.3.8 #46 0x7f91decc6c6f in () at /usr/lib/libclang.so.3.8 #47 0x7f91dec59587 in () at /usr/lib/libclang.so.3.8 #48 0x7f91dec3aa91 in () at /usr/lib/libclang.so.3.8 #49 0x7f91dec66547 in () at /usr/lib/libclang.so.3.8 #50 0x7f91dec66b8c in () at /usr/lib/libclang.so.3.8 #51 0x7f91dec595dd in () at /usr/lib/libclang.so.3.8 #52 0x7f91dec3aa91 in () at /usr/lib/libclang.so.3.8 #53 0x7f91dec3b46c in () at /usr/lib/libclang.so.3.8 #54 0x7f91dec2eb53 in () at /usr/lib/libclang.so.3.8 #55 0x7f91de65688e in () at /usr/lib/libclang.so.3.8 #56 0x7f91de618a0a in () at /usr/lib/libclang.so.3.8 #57 0x7f91de618d2e in () at /usr/lib/libclang.so.3.8 #58 0x7f91de61cb64 in () at /usr/lib/libclang.so.3.8 #59 0x7f91de3e4f97 in () at /usr/lib/libclang.so.3.8 #60 0x7f91d1a4f539 in llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) () at /usr/lib/../lib/libLLVM-3.8.so #61 0x7f91d1a4f5c4 in () at /usr/lib/../lib/libLLVM-3.8.so #62 0x7f91d1ac2c5d in () at /usr/lib/../lib/libLLVM-3.8.so #63 0x7f924aa93454 in start_thread () at /usr/lib/l
[frameworks-baloo] [Bug 370983] Plasma crashes while searching chromium in application launcher
https://bugs.kde.org/show_bug.cgi?id=370983 David Edmundson changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |frameworks-baloo Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com Version|5.8.0 |unspecified Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370933] Upgrade from 16.4 to 16.10 silently fails
https://bugs.kde.org/show_bug.cgi?id=370933 bym7...@gmail.com changed: What|Removed |Added CC||bym7...@gmail.com --- Comment #1 from bym7...@gmail.com --- Hey. Had the same issue as you. Was able to fit it by running: sudo apt-get install ubuntu-release-upgrader-qt Not sure why the files were missing (perhaps some dist-upgrade gone amiss?). But it's working fine now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370867] plasmashell suddenly segfault
https://bugs.kde.org/show_bug.cgi?id=370867 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- seems upstream in the amd driver? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357564] Widgets in panel freeze and becomes unremovable until one restarts the session
https://bugs.kde.org/show_bug.cgi?id=357564 Sudhir Khanger changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370989] Panel clock fall backs to LMT for istanbul.
https://bugs.kde.org/show_bug.cgi?id=370989 TrevizeDaneel changed: What|Removed |Added CC||compor...@gmail.com --- Comment #1 from TrevizeDaneel --- Confirming this. KDE Plasma 5.5.5 here, setting Istanbul timezone displays wrong time on panel clock as reported above and it is really annoying. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 370642] Plasma crashed after adding Webcut plasmoid to the desktop
https://bugs.kde.org/show_bug.cgi?id=370642 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Component|general |webbrowser Target Milestone|1.0 |--- Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Product|plasmashell |kdeplasma-addons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370576] Plasma crash after dropping comic plasmoid to desktop
https://bugs.kde.org/show_bug.cgi?id=370576 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- does this happen every time? can you reproduce with debug symbols installed? (qt, plasma-framework, plasma-workspace and kdeplasma-addons) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368588] Okular preview of certain PDF documents shows empty pages with Okular logo only
https://bugs.kde.org/show_bug.cgi?id=368588 --- Comment #7 from han_in_nederl...@hotmail.com --- ghostscript-9.15-5.1.x86_64 libspectre1-0.2.7-13.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 368929] SSL certificate *.kde.org is vulnerable to DROWN attack
https://bugs.kde.org/show_bug.cgi?id=368929 Ben Cooksley changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Ben Cooksley --- We're in the process of replacing this certificate now, so I consider this issue resolved (or soon to be resolved). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 370933] Upgrade from 16.4 to 16.10 silently fails
https://bugs.kde.org/show_bug.cgi?id=370933 --- Comment #2 from bym7...@gmail.com --- (In reply to bym7444 from comment #1) > Hey. Had the same issue as you. Was able to fit it by running: > > sudo apt-get install ubuntu-release-upgrader-qt > > Not sure why the files were missing (perhaps some dist-upgrade gone amiss?). > But it's working fine now. Ah, seems that this has already been found before: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692 It's also in the "Known Problems" section of: https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 370994] New: can't restore default internal editor
https://bugs.kde.org/show_bug.cgi?id=370994 Bug ID: 370994 Summary: can't restore default internal editor Product: krusader Version: 2.4.0-beta3 "Single Step" Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: krviewer Assignee: m...@fork.pl Reporter: sweduv_gh...@centrum.cz I want back the default internal editor after I've changed it. But don't know how. In the tip below the field Editor in configuration/ general/ viewer/editor is: Tip: use 'internal editor' if you want fast editor from krusader (don't know exact english sentence, I've Czech translation) but when I use 'internal editor' and try to open file for edit F4 -> can't open "internal editor". If I let the field blank, same: can't open "" I want the default editor same as if I open viewer F3 and than type ctrl+shift+e Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 370995] New: Kontact stop
https://bugs.kde.org/show_bug.cgi?id=370995 Bug ID: 370995 Summary: Kontact stop Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jr.li...@free.fr Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.6-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I ave changed the colors of KDE. At fisrt glance, it would seem that Kontact has not borne the color change of the KDE interface... - Unusual behavior I noticed: no. Sudden crash - Custom settings of the application: Nothing special to my knowledge -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc3d78e940 (LWP 2621))] Thread 43 (Thread 0x7fdb39670700 (LWP 3001)): #0 0x7ffc61ed8b84 in clock_gettime () #1 0x7fdc559454e6 in clock_gettime () at /lib64/libc.so.6 #2 0x7fdc565dfab3 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x7fdc5672f869 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x7fdc5672fc65 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x7fdc56730dac in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7fdc56730e75 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #7 0x7fdc4c3d5f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #8 0x7fdc4c3d692b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #9 0x7fdc4c3d6b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #10 0x7fdc5673124b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7fdc566e05ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7fdc5653f343 in QThread::exec() () at /lib64/libQt5Core.so.5 #13 0x7fdc5654399a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x7fdc4e0875ca in start_thread () at /lib64/libpthread.so.0 #15 0x7fdc55936f6d in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7fdb39e71700 (LWP 2999)): #0 0x7ffc61ed8b84 in clock_gettime () #1 0x7fdc559454e6 in clock_gettime () at /lib64/libc.so.6 #2 0x7fdc565dfab3 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x7fdc5672f869 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x7fdc5672fc65 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x7fdc56730dac in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7fdc56730e75 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #7 0x7fdc4c3d5f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #8 0x7fdc4c3d692b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #9 0x7fdc4c3d6b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #10 0x7fdc5673124b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7fdc566e05ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7fdc5653f343 in QThread::exec() () at /lib64/libQt5Core.so.5 #13 0x7fdc5654399a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x7fdc4e0875ca in start_thread () at /lib64/libpthread.so.0 #15 0x7fdc55936f6d in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7fdb3b08c700 (LWP 2989)): #0 0x7fdc5592b3ed in poll () at /lib64/libc.so.6 #1 0x7fdc4c3d6a06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fdc4c3d6b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdc5673124b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fdc566e05ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fdc5653f343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fdc5654399a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fdc4e0875ca in start_thread () at /lib64/libpthread.so.0 #8 0x7fdc55936f6d in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7fdb3c387700 (LWP 2837)): #0 0x7ffc61ed8b84 in clock_gettime () #1 0x7fdc559454e6 in clock_gettime () at /lib64/libc.so.6 #2 0x7fdc565dfab3 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x7fdc5672f869 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x7fdc5672fc65 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x7fdc56730dac in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7fdc56730e75 in
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||elvis.angelac...@kde.org, ||martin.sandsm...@kde.org Ever confirmed|0 |1 --- Comment #3 from Elvis Angelaccio --- Confirmed. Adding Martin in CC, according to git blame the only commit that changed this code is e6f52caa71116b4a3b9c921748e977d43312621a (although I can't see what's wrong there). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 --- Comment #5 from hrvo...@jankovci.net --- Now when you say out of memory, last week I was copying something from webdav to network via samba. My cache folder was full and there were no space left on root partition. Now I have 40 GB free and it's hard to simulate that problem again. Does partitionmanager need disk space also? It doesn't take too much time, maybe 20 seconds. This is ok now on Kubuntu. I will try later in Mint with no space left in root partiotion. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355006] Can't adjust the resolution via "kcmshell5 kscreen" without issuing "sudo" first
https://bugs.kde.org/show_bug.cgi?id=355006 --- Comment #6 from Sebastian Kügler --- You shouldn't be running it as root, though... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #116 from Sebastian Kügler --- @Robin Please don't muddy up this bugreport with unrelated requests. It's already too long, and adding a discussion here will make it longer to read, which reduces the time available to work on a fix. If you have a separate problem, please report a separate bugs as to avoid this report to become useless and harder to handle. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 370959] Dolphin crashes when trying to extract a rar archive file.
https://bugs.kde.org/show_bug.cgi?id=370959 --- Comment #4 from Elvis Angelaccio --- Can you attach here the complete debug output when you start Ark from Konsole? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 chris.tay...@cantab.net changed: What|Removed |Added CC||chris.tay...@cantab.net -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 --- Comment #2 from Kåre Särs --- Thanks for the report! I wonder if you are scanning in 8 or 16 bits per color mode? It looks a bit like it could be a byte order problem. What scanner are you using and are you using 16 bits / color mode? Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 Martijn changed: What|Removed |Added CC||martijn...@gmail.com --- Comment #6 from Martijn --- I have the same problem but the cause is different. I simply have to hover the cursor around a bit and it will randomly stop receiving mouse events. When this happens, SOME of the files/folders that are listed will still be able to receive the events. It seems to be completely random. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369072] Regression kMail 5.3.x: Plain-text quoting display is messed up
https://bugs.kde.org/show_bug.cgi?id=369072 Gunter Ohrner changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from Gunter Ohrner --- Unfortunately, the quoted parts still do not look correctly. You still cannot determine the context / quoting levels. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370953] plasma folder view: icon labels corrupted using nvidia binary driver
https://bugs.kde.org/show_bug.cgi?id=370953 Eike Hein changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #4 from Eike Hein --- Don't see how this can be in our code. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369072] Regression kMail 5.3.x: Plain-text quoting display is messed up
https://bugs.kde.org/show_bug.cgi?id=369072 Gunter Ohrner changed: What|Removed |Added Attachment #101186|0 |1 is obsolete|| --- Comment #4 from Gunter Ohrner --- Created attachment 101597 --> https://bugs.kde.org/attachment.cgi?id=101597&action=edit Screenshot showing the bug after the 5.3.2 patch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370969] Desktop pager missing under Wayland
https://bugs.kde.org/show_bug.cgi?id=370969 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Eike Hein --- Please see the Plasma 5.8 errata for missing features and known bugs in the Wayland session: https://community.kde.org/Plasma/5.8_Errata#Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370964] panel does not reappear after auto-hide is selected
https://bugs.kde.org/show_bug.cgi?id=370964 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from David Edmundson --- Also do you have Switch Desktop on Edge enabled in System settings -> screen edges? Please set the status back to unconfirmed when you reply. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368862] Thumbnails for Olympus raw (ORF) in albumview are blurred
https://bugs.kde.org/show_bug.cgi?id=368862 --- Comment #25 from Guenther M. Erhard --- Hello Maik, Is there any progress here? I've compiled a current version from git, but the problem is still there. You mention libexiv2 is probably the root cause when writing to raw files. Is there anything I can check? Thanks Guenther -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 370959] Dolphin crashes when trying to extract a rar archive file.
https://bugs.kde.org/show_bug.cgi?id=370959 --- Comment #5 from Elvis Angelaccio --- Ah right, you might simply be affected by bug 368786 Do you have shared-mime-info 1.7? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369072] Regression kMail 5.3.x: Plain-text quoting display is messed up
https://bugs.kde.org/show_bug.cgi?id=369072 --- Comment #5 from Gunter Ohrner --- In more detail: The mail is currently displayed as follows: Am Montag, 19. September 2016, 21:01:11 CEST schrieb Gunter Ohrner: | Am Montag, 19. September 2016, 21:00:44 CEST schrieb Gunter Ohrner: | Am Montag, 19. September 2016, 21:00:25 CEST schrieb Gunter Ohrner: | Text Level 1 Text Level 2 Text Level 3 Text Level 4 This does not really make sense and you still cannot determine that "Text Level 3" is an answer to "Text Level 2", but "Text Level 4" is not, and you also cannot determine that "Text Level 2" belongs to the introduction line from "21:00:44" and "Text Level 3" belongs to the introduction line from "21:01:11". You cannot even easily see that "Text Level 2" and 3 are quoted but "Text Level 4" is not. (Except possibly due to font face and color, if configured accordingly, which is applied correctly.) It should look as follows however to make clear which part belongs to what and what part is an answer to which: Am Montag, 19. September 2016, 21:01:11 CEST schrieb Gunter Ohrner: | Am Montag, 19. September 2016, 21:00:44 CEST schrieb Gunter Ohrner: | | Am Montag, 19. September 2016, 21:00:25 CEST schrieb Gunter Ohrner: | | | Text Level 1 | | Text Level 2 | Text Level 3 Text Level 4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370576] Plasma crash after dropping comic plasmoid to desktop
https://bugs.kde.org/show_bug.cgi?id=370576 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 357222 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 357222] Crash Plasma while I put an object
https://bugs.kde.org/show_bug.cgi?id=357222 David Edmundson changed: What|Removed |Added CC||paulolieuth...@gmail.com --- Comment #2 from David Edmundson --- *** Bug 370576 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370996] New: Plain text mail viewer: Copy/Pasting quoted parts introduced lots of empty lines
https://bugs.kde.org/show_bug.cgi?id=370996 Bug ID: 370996 Summary: Plain text mail viewer: Copy/Pasting quoted parts introduced lots of empty lines Product: kmail2 Version: 5.3.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: kdeb...@customcdrom.de Send yourself an email with the following content: Am Montag, 19. September 2016, 21:01:11 CEST schrieb Gunter Ohrner: > Am Montag, 19. September 2016, 21:00:44 CEST schrieb Gunter Ohrner: > > Am Montag, 19. September 2016, 21:00:25 CEST schrieb Gunter Ohrner: > > > Text Level 1 > > > > Text Level 2 > > Text Level 3 Text Level 4 If you copy the displayed content from this mail and paste it into a text editor (or a new plain text mail editor), the result will be as follows: Am Montag, 19. September 2016, 21:01:11 CEST schrieb Gunter Ohrner:  > Am Montag, 19. September 2016, 21:00:44 CEST schrieb Gunter Ohrner:  > > Am Montag, 19. September 2016, 21:00:25 CEST schrieb Gunter Ohrner:  > > > Text Level 1  > > > > Text Level 2  > > Text Level 3 Text Level 4 There are several empty lines which are not supposed to be there. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added
https://bugs.kde.org/show_bug.cgi?id=369172 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from David Edmundson --- *** This bug has been marked as a duplicate of bug 357222 *** -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 367499] usability regression: GTK+>3.16.x results in too small GTK3 app UI fonts when logical DPI>96
https://bugs.kde.org/show_bug.cgi?id=367499 Felix Miata changed: What|Removed |Added Keywords||accessibility, usability -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 370997] New: Include text files in the "Documents" category (e.g. for Dolphin-"Find" or for Krunner or for launchers/dashboard)
https://bugs.kde.org/show_bug.cgi?id=370997
Bug ID: 370997
Summary: Include text files in the "Documents" category (e.g.
for Dolphin-"Find" or for Krunner or for
launchers/dashboard)
Product: BalooWidgets
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: pinak.ah...@gmail.com
Reporter: pitloc...@gmx.net
Currently the "Documents" category does not include text files, I use many
plain-text files and suggest that they should be considered a Document.
In 2014 this bug was supposedly (?) been fixed, see
https://bugs.kde.org/show_bug.cgi?id=332021.
I am filing it again because the old one's location is now obsolete (there is
no "baloo" product anymore), but also because there has been no reaction to
existing reports of it not being fixed on forum.kde:
https://forum.kde.org/viewtopic.php?f=154&t=133468#p363638
Perhaps this results from
if (mimeType.contains(QLatin1String("text")))
types << Type::Text;
in line 141-142 of
https://quickgit.kde.org/?p=baloo.git&a=blob&h=88bb59a01e5592abb74b1ab345bfc6765d35db57&hb=e6bd357153a790ef66dc803cd3451270e9311134&f=src%2Ffile%2Fbasicindexingjob.cpp
It would be even better, if the user could whitelist what should be defined as
document (other users would choose even .tex or .html or whatever files). It
would be best if one could adjust this in settings->Plasma Search->Document.
baloo 5.27.0-1 baloo-widgets 16.08.2-1 plasma 5.8.1
Reproducible: Always
Steps to Reproduce:
1. create text/plain file, which is used as a document
2. let baloo update index
3. baloosearch or "Dolphin->Find->Any" finds it
4. "Dophin->Find->Documents" or Krunner or Launcher or Dashboard doesn't find
it (as it isn't in the "Document" category)
Expected Results:
Should find a text/plain file, which is used as a document. Or offer an option
which filetypes are interpreted as documents.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 370993] KDevelop crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=370993 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #1 from Kevin Funk --- [KCrash Handler] #5 0x7f91de462f30 in () at /usr/lib/libclang.so.3.8 #6 0x7f91de6a230c in () at /usr/lib/libclang.so.3.8 => You're getting a SIGSEGV in libclang. This isn't necessarily critical, libclang likely can recover from a SIGSEGV. You need to continue debugging in order to find out the real issue for crashing. If GDB is paused, with a backtrace like this, enter the following: signal SIGSEGV continue This will make GDB re-raise the signal and continue debugging (Note you might have to re-enter those commands multiple times, in case KDevelop crashes again inside libclang.) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 357222] Crash Plasma while I put an object
https://bugs.kde.org/show_bug.cgi?id=357222 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- I'm not sure that commit in comment #1 did anything we still have 2 reports on newer Plasma with the exact same trace. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 357222] Crash Plasma while I put an object
https://bugs.kde.org/show_bug.cgi?id=357222 David Edmundson changed: What|Removed |Added CC||sam...@ton-kunst.ch --- Comment #3 from David Edmundson --- *** Bug 369172 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 370998] New: the python interfaces to KApplication and KConfigSkeleton stopped working with sip 4.18
https://bugs.kde.org/show_bug.cgi?id=370998 Bug ID: 370998 Summary: the python interfaces to KApplication and KConfigSkeleton stopped working with sip 4.18 Product: bindings Version: 4.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: pykde Assignee: kde-bindi...@kde.org Reporter: wolfg...@rohdewald.de The attached scripts work fine with Kubuntu 16.04 but not with 16.10. They crash but drkonqi does not give useful information. I am attaching part of valgrind output. If I install the packages python-qt4 and python-sip from 16.04 on 16.10, they work. If I install the packages python-qt4 and python-sip from 16.10 on 16.04, they do not work. But I cannot reproduce any bugs without using pykde. This means kajongg does no longer run on Kubuntu using PyKDE4. However it can emulate most of what it needs from PyKDE4 when started with --nokde. I will have to commit a change which lets kajongg always run with --nokde until this bug is fixed. Reproducible: Always Steps to Reproduce: 1. python2 bug2.py ; python2 bug3.py Actual Results: segfault Expected Results: no segfault -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 370998] the python interfaces to KApplication and KConfigSkeleton stopped working with sip 4.18
https://bugs.kde.org/show_bug.cgi?id=370998 Wolfgang Rohdewald changed: What|Removed |Added CC||wolfg...@rohdewald.de --- Comment #1 from Wolfgang Rohdewald --- Created attachment 101598 --> https://bugs.kde.org/attachment.cgi?id=101598&action=edit bug2 -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 370998] the python interfaces to KApplication and KConfigSkeleton stopped working with sip 4.18
https://bugs.kde.org/show_bug.cgi?id=370998 --- Comment #2 from Wolfgang Rohdewald --- Created attachment 101599 --> https://bugs.kde.org/attachment.cgi?id=101599&action=edit bug3 -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 370998] the python interfaces to KApplication and KConfigSkeleton stopped working with sip 4.18
https://bugs.kde.org/show_bug.cgi?id=370998 --- Comment #3 from Wolfgang Rohdewald --- Created attachment 101600 --> https://bugs.kde.org/attachment.cgi?id=101600&action=edit valgrind output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370999] New: Kwin crashes sometimes when opening windows
https://bugs.kde.org/show_bug.cgi?id=370999 Bug ID: 370999 Summary: Kwin crashes sometimes when opening windows Product: kwin Version: 5.8.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: alexandre.nu...@gmail.com Application: kwin_x11 (5.8.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.6.7 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: Google chrome opened a window in form of popup (i.e. with specific dimensions). The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3e92506e00 (LWP 4245))] Thread 6 (Thread 0x7f3e89885700 (LWP 4905)): #0 0x0037dace1253 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x0037e7ed6d3f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x0037e7ed87e4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x0037e7ed8cfa in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x0037e7e8319a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x0037e7ca8e53 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x0038008c8a55 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x0037e7cadd78 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x0037db407464 in start_thread (arg=0x7f3e89885700) at pthread_create.c:333 #9 0x0037dace897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f3e772bb700 (LWP 4266)): #0 0x0037db40d18f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003802f7c574 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x003802f7c5b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x0037db407464 in start_thread (arg=0x7f3e772bb700) at pthread_create.c:333 #4 0x0037dace897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f3e7830c700 (LWP 4265)): #0 0x0037dace1253 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x0037e7ed6d3f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x0037e7ed87e4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x0037e7ed8cfa in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x0037e7e8319a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x0037e7ca8e53 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x0038008c8a55 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x0037e7cadd78 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x0037db407464 in start_thread (arg=0x7f3e7830c700) at pthread_create.c:333 #9 0x0037dace897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f3e8bb6c700 (LWP 4254)): #0 0x0037dace1253 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x0037e7ed6d3f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x0037e7ed87e4 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x0037e7ed8cfa in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x0037e7e8319a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x0037e7ca8e53 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x0037ec415525 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x0037e7cadd78 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x0037db407464 in start_thread (arg=0x7f3e8bb6c700) at pthread_create.c:333 #9 0x0037dace897f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f3e9177f700 (LWP 4248)): #0 0x0037dacdf50d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x0037de00c150 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x0037de00dee9 in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f3e92224a79 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x0037e7cadd78 in () at /usr/lib/x86_64-linux-gn
[plasma-integration] [Bug 371000] New: qtbase-abi conflicts with the current qtcreator package
https://bugs.kde.org/show_bug.cgi?id=371000 Bug ID: 371000 Summary: qtbase-abi conflicts with the current qtcreator package Product: plasma-integration Version: 5.8.0 Platform: Neon Packages URL: https://snag.gy/kSl6C5.jpg OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: yunusemre.sent...@pardus.org.tr I simple cannot install qt-sdk via any package manager, because of that i believe there is a conflict in qt-creator package depends on qtbase-abi 5.3 Reproducible: Always Steps to Reproduce: 1.Fresh KDE-neon (nothing installed since the system is installed from iso) 2.Konsole 3.sudo apt-get install qt-sdk Actual Results: apt-get output: Broken qt-sdk:amd64 dependencies on qtcreator [ amd64 ] < none -> 3.5.1+dfsg-2ubuntu2 > ( universe/devel ) Considering qtcreator:amd64 1 as a solution to qt-sdk:amd64 Re-Instated qtcreator-data:amd64 Re-Instated libbotan-1.10-1:amd64 Re-Instated libllvm3.6v5:amd64 Re-Instated libobjc4:amd64 Re-Instated libobjc-5-dev:amd64 Re-Instated libclang1-3.6:amd64 Re-Instated libqbscore1:amd64 Re-Instated libqbsqtprofilesetup1:amd64 Reinst Failed early because of qtbase-abi-5-5-1:amd64 Done Expected Results: qt-sdk should have been installed I know it is related ubuntu package management system, but i also know that it cannot be hold sb has to have a look at this qt abi issue -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 371000] qtbase-abi conflicts with the current qtcreator package
https://bugs.kde.org/show_bug.cgi?id=371000 Yunusemre Şentürk changed: What|Removed |Added CC||yunusemre.sent...@pardus.or ||g.tr -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 --- Comment #3 from Marc --- i use hp scanjet 3300c get same result with grey or color mode -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 --- Comment #4 from Kåre Särs --- The thing is that Digikam and Showfoto use the same library as Skanlite... Can you attach a screen-shot of the settings? Both "Basic Options" and "Scanner Specific Options"? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 366793] Regression in Konsole's handling of command line parameters
https://bugs.kde.org/show_bug.cgi?id=366793 Aki Koskinen changed: What|Removed |Added CC||k...@akikoskinen.info -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 265669] where is Super User Mode
https://bugs.kde.org/show_bug.cgi?id=265669 --- Comment #5 from stu109...@mail.uni-kiel.de --- Now there is dolphin-as-root which is an additional program and can be used from dolphins context menu. Although this has issues at the moment (Bug 365444), I guess this ticket can be closed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361694] The search (Find) function in Dolphin is useless, doesn't return results as it should
https://bugs.kde.org/show_bug.cgi?id=361694 --- Comment #9 from stu109...@mail.uni-kiel.de --- (In reply to stu109382 from comment #8) > I don't get it. Why was this baloo stuff introduced in the first place? > What is the expected benefit? > Wouldn't it be way simpler (and more stable) to implement the dolphin search > as a fontend for the "find" command? > Something like "find . -iname *mysearchterm*" and the result is just > displayed by dolphin. One might look into this post: http://www.ryananddebi.com/2015/07/13/linux-getting-find-working-in-dolphin-on-kde-linux-mint-and-kubuntu/ It works much better for me now. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 371001] New: Kate opens new window rather than tab if on different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=371001 Bug ID: 371001 Summary: Kate opens new window rather than tab if on different virtual desktop Product: kate Version: Git Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: nortex...@gmail.com Kate used to always open documents in a tab from e.g. Dolphin, no matter which virtual desktop it was on. Now it will open a new window/instance on the desktop from where it's opened. Kate version 16.08.2 Reproducible: Always Steps to Reproduce: 1. Have only one instance of Kate open on virtual desktop x 2. Open a document in kate from e.g. Dolphin on virtual desktop y Actual Results: Document opens in a new instance of kate on desktop y (assuming y and x are distinct) Expected Results: Document opens in the preexisting instance on desktop x -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369185] Launchers (add as launcher) and symbols (add to panel) behave inconsistently, no jump list for app symbols
https://bugs.kde.org/show_bug.cgi?id=369185 --- Comment #5 from stu109...@mail.uni-kiel.de --- It would also be great to have jumps lists for dolphin, i.e., showing the recent folders in which I browsed. I think it would make sense to add to this folders list when closing dolphin, so that I can directly open the folder again using the jump list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm
https://bugs.kde.org/show_bug.cgi?id=368660 --- Comment #43 from Wolfgang Bauer --- (In reply to pinheiro from comment #42) > Wolfgang Bauer, you are absolutely right, looks horrible there not > exactly my fault, the air icons are supposed to be minimalist wen > applications mix oxygen icons in plasma are things can go wrong. Like an svg > that is part of plasma theme having oxygen icons that cant even be well > rendered by QT-SVG. I'm not sure we are talking about the same thing here. The new SVG is rendered fine, but as I understand it, those minimalist/monochromic icons are only to be used in the system tray, aren't they? But view-history is used by the application launcher, and the other icons are colorful as can be seen in my screenshot (exactly like they were in KDE4). That's the only thing I mean here. If Kickoff looks "horrible" to you, it may be because of bug#365204, in short some of the icons are "broken" currently and Plasma falls back to the icon theme then. Should not be a problem if you use the "Oxygen" icon theme though (that's what I did in my screenshot). My doubt is whether it's a good idea to replace view-history with a simplicistic version though instead of just keeping the old one. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370181] partitionmanager crashes while opening and scanning device /dev/sda
https://bugs.kde.org/show_bug.cgi?id=370181 --- Comment #6 from Andrius Štikonas --- No, I don't think we need any hard drive space except for tiny bit for storing settings. But I guess running out of space can make system perform unpredictably and something else goes wrong. I guess 20 seconds is still ok. It depends on the speed of drives. There might be some improvements in newer versions. Both Kubuntu and Mint ship not too new 1.2.1... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 370857] WiFi is always connecting and never stop
https://bugs.kde.org/show_bug.cgi?id=370857 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 352326 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 --- Comment #45 from Martin Gräßlin --- *** Bug 370999 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 352326] Plasma nm applet keeps spinning even after wifi network is connected
https://bugs.kde.org/show_bug.cgi?id=352326 Jan Grulich changed: What|Removed |Added CC||guoyunhebr...@gmail.com --- Comment #61 from Jan Grulich --- *** Bug 370857 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370999] Kwin crashes sometimes when opening windows
https://bugs.kde.org/show_bug.cgi?id=370999 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- As a workaround use breeze window decoration. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 Allan changed: What|Removed |Added CC||kdeb...@metalight.dk --- Comment #45 from Allan --- Woohoo, I figured out why this happens. :D -Single click initiates the "double click". ..Ages pass; -User tries to doubleclick, -BUT the first of these clicks is part of the previously initiated double click.. You're welcome. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM
https://bugs.kde.org/show_bug.cgi?id=359327 --- Comment #8 from Shawn --- (In reply to Martin Gräßlin from comment #7) > Which window is having focus when the game exits? The steam overlay still has focus. It is still fullscreen, too. But the panel is now visible on top. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371000] qtbase-abi conflicts with the current qtcreator package
https://bugs.kde.org/show_bug.cgi?id=371000 Martin Gräßlin changed: What|Removed |Added Product|plasma-integration |neon Version|5.8.0 |unspecified Assignee|mgraess...@kde.org |neon-b...@kde.org Component|general |general CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370953] plasma folder view: icon labels corrupted using nvidia binary driver
https://bugs.kde.org/show_bug.cgi?id=370953 --- Comment #5 from Jason A. Donenfeld --- Alright, I posted it over at the NVIDIA form, then: https://devtalk.nvidia.com/default/topic/971972/linux/icon-text-label-corruption-with-kde-plasma-5-desktop-folder-view/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369191] Crash if I use next/previous key frame quickly (back and forth) and draw at the same time
https://bugs.kde.org/show_bug.cgi?id=369191 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/krit ||a/7ade2d46b4c7e6411d0175c4c ||f8621c83b01a06e Status|CONFIRMED |RESOLVED Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/7ade2d46b4c7e6411d0175c4c |a/4ae6ff72311d9b1a97f7e71f4 |f8621c83b01a06e |a0adf0d1127064e --- Comment #7 from Dmitry Kazakov --- Git commit 7ade2d46b4c7e6411d0175c4cf8621c83b01a06e by Dmitry Kazakov. Committed on 17/10/2016 at 12:21. Pushed by dkazakov into branch 'master'. Fix switching frames when painting at the same time Fixes T3930 M +1-0libs/image/CMakeLists.txt M +5-5libs/image/commands_new/kis_switch_current_time_command.cpp M +4-2libs/image/commands_new/kis_switch_current_time_command.h M +62 -34 libs/image/kis_image_animation_interface.cpp M +7-4libs/image/kis_image_animation_interface.h A +78 -0libs/image/kis_switch_time_stroke_strategy.cpp [License: GPL (v2+)] A +53 -0libs/image/kis_switch_time_stroke_strategy.h [License: GPL (v2+)] M +37 -0libs/image/tests/kis_image_animation_interface_test.cpp M +1-1libs/image/tests/kis_image_animation_interface_test.h M +1-1plugins/dockers/animation/animation_docker.cpp M +1-1plugins/dockers/animation/kis_time_based_item_model.cpp M +1-1plugins/dockers/animation/tests/timeline_model_test.cpp M +1-1plugins/dockers/defaultdockers/kis_layer_box.cpp http://commits.kde.org/krita/7ade2d46b4c7e6411d0175c4cf8621c83b01a06e --- Comment #8 from Dmitry Kazakov --- Git commit 4ae6ff72311d9b1a97f7e71f4a0adf0d1127064e by Dmitry Kazakov. Committed on 17/10/2016 at 12:21. Pushed by dkazakov into branch 'master'. Make the frame switch stroke a barrier Now the frame cannot switch until all the background strokes are finished. Basically, we had this behavior from the very beginning, though I wanted to get out of it, but it didn't work. Fixes T3930 M +3-5libs/image/kis_image_animation_interface.cpp M +9-4libs/image/kis_switch_time_stroke_strategy.cpp http://commits.kde.org/krita/4ae6ff72311d9b1a97f7e71f4a0adf0d1127064e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369191] Crash if I use next/previous key frame quickly (back and forth) and draw at the same time
https://bugs.kde.org/show_bug.cgi?id=369191 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/krit ||a/7ade2d46b4c7e6411d0175c4c ||f8621c83b01a06e Status|CONFIRMED |RESOLVED Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/7ade2d46b4c7e6411d0175c4c |a/4ae6ff72311d9b1a97f7e71f4 |f8621c83b01a06e |a0adf0d1127064e --- Comment #7 from Dmitry Kazakov --- Git commit 7ade2d46b4c7e6411d0175c4cf8621c83b01a06e by Dmitry Kazakov. Committed on 17/10/2016 at 12:21. Pushed by dkazakov into branch 'master'. Fix switching frames when painting at the same time Fixes T3930 M +1-0libs/image/CMakeLists.txt M +5-5libs/image/commands_new/kis_switch_current_time_command.cpp M +4-2libs/image/commands_new/kis_switch_current_time_command.h M +62 -34 libs/image/kis_image_animation_interface.cpp M +7-4libs/image/kis_image_animation_interface.h A +78 -0libs/image/kis_switch_time_stroke_strategy.cpp [License: GPL (v2+)] A +53 -0libs/image/kis_switch_time_stroke_strategy.h [License: GPL (v2+)] M +37 -0libs/image/tests/kis_image_animation_interface_test.cpp M +1-1libs/image/tests/kis_image_animation_interface_test.h M +1-1plugins/dockers/animation/animation_docker.cpp M +1-1plugins/dockers/animation/kis_time_based_item_model.cpp M +1-1plugins/dockers/animation/tests/timeline_model_test.cpp M +1-1plugins/dockers/defaultdockers/kis_layer_box.cpp http://commits.kde.org/krita/7ade2d46b4c7e6411d0175c4cf8621c83b01a06e --- Comment #8 from Dmitry Kazakov --- Git commit 4ae6ff72311d9b1a97f7e71f4a0adf0d1127064e by Dmitry Kazakov. Committed on 17/10/2016 at 12:21. Pushed by dkazakov into branch 'master'. Make the frame switch stroke a barrier Now the frame cannot switch until all the background strokes are finished. Basically, we had this behavior from the very beginning, though I wanted to get out of it, but it didn't work. Fixes T3930 M +3-5libs/image/kis_image_animation_interface.cpp M +9-4libs/image/kis_switch_time_stroke_strategy.cpp http://commits.kde.org/krita/4ae6ff72311d9b1a97f7e71f4a0adf0d1127064e -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371002] White text selection in Chrome when browser window loses focus
https://bugs.kde.org/show_bug.cgi?id=371002 Janek Bevendorff changed: What|Removed |Added Version|5.7.95 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371002] New: White text selection in Chrome when browser window loses focus
https://bugs.kde.org/show_bug.cgi?id=371002 Bug ID: 371002 Summary: White text selection in Chrome when browser window loses focus Product: Breeze Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: jbev_kdebugs...@refining-linux.org When I select text in Chrome and then click somewhere else on my desktop so that the Chrome window loses the focus, the formerly blue text selection becomes almost white which makes it impossible to read the selected (and also white) text. Other applications are not affected (although their inactive selection color is also brighter than the active selection color). For some reason, bugs.kde.org is one of the few websites that don't have this problem with text selection. However, the problem does appear with selection input fields (such as the Component and the Version fields in the guided editor or the advanced search). When they lose focus, the selection becomes unreadable. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368370] Dolphin crash copying folder from SMB LAN server
https://bugs.kde.org/show_bug.cgi?id=368370 --- Comment #1 from Samuel Zarza Fernández --- Created attachment 101601 --> https://bugs.kde.org/attachment.cgi?id=101601&action=edit New crash information added by DrKonqi dolphin (15.12.3) using Qt 5.5.1 - What I was doing when the application crashed: Accesing a DFS resource under a SMB shared resource -- Backtrace (Reduced): #9 KDialogJobUiDelegate::Private::next (this=0x2e35b20) at ../../src/kdialogjobuidelegate.cpp:82 #10 0x7f5a45a0aea1 in QObject::event (this=0x2e35b20, e=) at kernel/qobject.cpp:1239 #11 0x7f5a464de05c in QApplicationPrivate::notify_helper (this=this@entry=0x255c3e0, receiver=receiver@entry=0x2e35b20, e=e@entry=0x2f086c0) at kernel/qapplication.cpp:3716 #12 0x7f5a464e3516 in QApplication::notify (this=0x7ffe25ce6ff0, receiver=0x2e35b20, e=0x2f086c0) at kernel/qapplication.cpp:3499 #13 0x7f5a459db62b in QCoreApplication::notifyInternal (this=0x7ffe25ce6ff0, receiver=0x2e35b20, event=event@entry=0x2f086c0) at kernel/qcoreapplication.cpp:965 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368370] Dolphin crash copying folder from SMB LAN server
https://bugs.kde.org/show_bug.cgi?id=368370 Samuel Zarza Fernández changed: What|Removed |Added CC||djava...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]
https://bugs.kde.org/show_bug.cgi?id=370516 --- Comment #21 from Eike Hein --- Backtrace: #0 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=2, this_=0x8c22e0, r=0x0, a=0x0, ret=0x7fffd1af) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:152 #1 0x75248d54 in QtPrivate::QSlotObjectBase::compare (a=0x0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:129 #2 QObjectPrivate::connectImpl (sender=sender@entry=0x8bd7b0, signal_index=4, receiver=receiver@entry=0x8bc2e0, slot=slot@entry=0x0, slotObj=slotObj@entry=0x8e9a40, type=Qt::UniqueConnection, types=0x0, senderMetaObject=0x7fffcabb5800 ) at kernel/qobject.cpp:4709 #3 0x75248f82 in QObject::connectImpl (sender=sender@entry=0x8bd7b0, signal=signal@entry=0x7fffd3c0, receiver=receiver@entry=0x8bc2e0, slot=slot@entry=0x0, slotObj=0x8e9a40, type=Qt::UniqueConnection, types=0x0, senderMetaObject=0x7fffcabb5800 ) at kernel/qobject.cpp:4674 #4 0x7fffcabbfcbf in QObject::connect > (type=Qt::UniqueConnection, slot=..., context=0x8bc2e0, signal=(void (TaskManager::ActivityInfo::*)(const TaskManager::ActivityInfo * const)) 0x7fffca9a0ea0 , sender=0x8bd7b0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:347 #5 PagerModel::Private::refreshDataSource (this=0x8bc760) at /workspace/build/applets/pager/plugin/pagermodel.cpp:174 #6 0x7fffcabc0cff in PagerModel::refresh (this=0x8bc2e0) at /workspace/build/applets/pager/plugin/pagermodel.cpp:395 #7 0x76e56cdc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x76de795a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 ---Type to continue, or q to quit--- #9 0x76de85b4 in QQmlIncubationController::incubateFor(int) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x73cd36ac in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Declarative.so.5 #11 0x76de83c2 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x76de35bb in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x73cd00c5 in KDeclarative::QmlObject::completeInitialization(QHash const&) () from /usr/lib/x86_64-linux-gnu/libKF5Declarative.so.5 #14 0x77ba2574 in PlasmaQuick::AppletQuickItem::init() () from /usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #15 0x7fffd0abcf84 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]
https://bugs.kde.org/show_bug.cgi?id=370516 --- Comment #22 from Eike Hein --- This is actually a Qt bug, fixed by https://codereview.qt-project.org/#/c/160760/ Which explains why it didn't crash in my Qt 5.8. We'll work around the Qt bug in our code, so 5.8.2 will work with broken older Qt versions. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #13 from Janek Bevendorff ---
I downloaded a KDE Neon ISO to test this in KWrite and make sure it's
reproducible on other systems. I can indeed reproduce both issues:
C++/boost inserting {; instead of {} and C unindenting the line.
BTW C indenter also indents incorrectly in if statements when you want
the brace to be in its own line.
When I have this code
class X
{
private:
void foo()
{
if (true) |
}
};
and press enter, I get
class X
{
private:
void foo()
{
if (true)
|
}
};
which is okay. But when I type an opening brace, I get
class X
{
private:
void foo()
{
if (true)
{|}
}
};
This can't even be corrected by pressing Ctrl+Z. The unindentation for
the method foo() can be corrected this way, but when I press Ctrl+Z
here, I end up with
class X
{
private:
void foo()
{
if (true)
{|}
}
};
When I have the opening braces on the same line as the method or if
condition header, indentation works as expected.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]
https://bugs.kde.org/show_bug.cgi?id=370516 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-desktop/d888c454192ee5c5 ||683c42f40be1193692376ef5 Resolution|--- |FIXED --- Comment #23 from Eike Hein --- Git commit d888c454192ee5c5683c42f40be1193692376ef5 by Eike Hein. Committed on 17/10/2016 at 12:53. Pushed by hein into branch 'Plasma/5.8'. Test the QMetaObject::Connection instead of using Qt::UniqueConnection. Avoids a crash in deployed versions of Qt. Upstream bugfix: https://codereview.qt-project.org/#/c/160760/ M +5-3applets/pager/plugin/pagermodel.cpp http://commits.kde.org/plasma-desktop/d888c454192ee5c5683c42f40be1193692376ef5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371003] New: Plasma crashes when start application via "Kickoff Application Launcher"
https://bugs.kde.org/show_bug.cgi?id=371003 Bug ID: 371003 Summary: Plasma crashes when start application via "Kickoff Application Launcher" Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aw...@yandex.by CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Open "Kickoff Application Launcher". Enter "kcalc". Launch kcalc. Plasma crash. kcalc not launched. I suppose that it happens when there is little free RAM. Used 2.9 out of 3.9 GB RAM (at the time of the crash). The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f76f2e677c0 (LWP 1300))] Thread 17 (Thread 0x7f760cff9700 (LWP 4865)): #0 0x7f76ebb7e03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76eca6c34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7631b7b65f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7631b7f43a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7631b7f481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7631b7d005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f76eca6b32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f76ebb7a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f76ec37902d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f760d7fa700 (LWP 4864)): #0 0x7f76ebb7e03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76eca6c34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7631b7b65f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7631b7f43a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7631b7f481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7631b7f481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f7631b7f481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f7631b7d005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f76eca6b32f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f76ebb7a0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f76ec37902d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f760dffb700 (LWP 4863)): #0 0x7f76ebb7e03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76eca6c34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7631b7b65f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7631b7f43a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7631b7f481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7631b796cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7631b7d005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f76eca6b32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f76ebb7a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f76ec37902d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f760e7fc700 (LWP 4862)): #0 0x7f76ebb7e03f in pthread_cond_wait@@GLIBC_2.3.2
[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM
https://bugs.kde.org/show_bug.cgi?id=359327 --- Comment #9 from Martin Gräßlin --- (In reply to Shawn from comment #8) > (In reply to Martin Gräßlin from comment #7) > > Which window is having focus when the game exits? > > The steam overlay still has focus. It is still fullscreen, too. But the > panel is now visible on top. are you sure it's having focus. That would not be like how KWin handles fullscreen windows. An active fullscreen window is above the panel. Only non-active fullscreen windows are below panel. -- You are receiving this mail because: You are watching all bug changes.
