[kdenlive] [Bug 377999] Wrong media paths when opening project from archive
https://bugs.kde.org/show_bug.cgi?id=377999 --- Comment #2 from Jean-Baptiste Mardelle --- Sorry, I mean extract the .kdenlive file from the archived .tar.gz file -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377999] Wrong media paths when opening project from archive
https://bugs.kde.org/show_bug.cgi?id=377999 --- Comment #1 from Jean-Baptiste Mardelle --- Thanks for your report. Could you extract the .kdenlive project file and attach it here or mail it to me ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #83 from caulier.gil...@gmail.com --- Anyway, yesterday i recompiled the AppImage. It do not have teh last commit from Maik, but all the rest is already inside. It's at usual place in GDrive repository. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #82 from caulier.gil...@gmail.com --- I will recompile the AppImage this week end as well... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #6 from Martin Gräßlin --- > I'll wait for Plasma 5.9 then and come back with the results then. any news? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377990] Desktop Grid + Present Windows Effect: Non maximized windows disappear during movement
https://bugs.kde.org/show_bug.cgi?id=377990 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 364509 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364509] Applications window disappears while dragging them through Desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=364509 Martin Gräßlin changed: What|Removed |Added CC||qb...@ungmedms.com --- Comment #10 from Martin Gräßlin --- *** Bug 377990 has been marked as a duplicate of this bug. *** -- 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 Martin Gräßlin changed: What|Removed |Added Target Milestone|--- |1.0 Component|wayland-generic |generic-wayland Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Product|kwin|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor
https://bugs.kde.org/show_bug.cgi?id=372417 --- Comment #3 from Quincy --- At least I found a workaround: When Gwenview window is not maximized on that screen going to fullscreen mode works. It only jumps to the other screen if it is already maximized. Additionally I am not sure if this is connected to having two screens of different resolutions: First screen always catching window: 1440x900 and second screen 1600x1200 in my case -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #81 from Jens --- I would really like to see/review this change. Is there a chance to replace 1-2 compiled files in the appimage (libraries etc) or will you compile new appimages anyway in a few days? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.
https://bugs.kde.org/show_bug.cgi?id=377526 --- Comment #11 from tonny sofijan --- Sure! :) OS: Opensuse Argon x86_64 Config #1: systemsettings > icons > panel > set to 48 > apply. [attch#!] Config #2: task manager > right click > properties > set icon size to large. [attch#2] Result: still have quite large padding top and bottom, icon not resizing [attch#3] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.
https://bugs.kde.org/show_bug.cgi?id=377526 --- Comment #10 from tonny sofijan --- Created attachment 104710 --> https://bugs.kde.org/attachment.cgi?id=104710&action=edit attch#3 Result: still have quite large padding top and bottom, icon not resizing [attch#3] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.
https://bugs.kde.org/show_bug.cgi?id=377526 --- Comment #9 from tonny sofijan --- Created attachment 104709 --> https://bugs.kde.org/attachment.cgi?id=104709&action=edit attch#2 Config #2: task manager > right click > properties > set icon size to large. [attch#2] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.
https://bugs.kde.org/show_bug.cgi?id=377526 --- Comment #8 from tonny sofijan --- Created attachment 104708 --> https://bugs.kde.org/attachment.cgi?id=104708&action=edit attch#1 Config #1: systemsettings > icons > panel > set to 48 > apply. [attch#!] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377969] Screen blink
https://bugs.kde.org/show_bug.cgi?id=377969 Christoph Feck changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|general |general Product|systemsettings |kwin -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377943] systemsettings5 crash every time kcm_sddm was opened
https://bugs.kde.org/show_bug.cgi?id=377943 Christoph Feck changed: What|Removed |Added Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk Component|general |kcm_sddm -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 350205] System Setting close
https://bugs.kde.org/show_bug.cgi?id=350205 Christoph Feck changed: What|Removed |Added CC||johnkoulianos060101@gmail.c ||om --- Comment #7 from Christoph Feck --- *** Bug 377904 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377904] System Settings Crash Every Time I Attempt To Open 'Desktop Theme' in System Settings/Workspace Theme, and Can't Reset Theme Through Terminal
https://bugs.kde.org/show_bug.cgi?id=377904 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 350205 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377937] Keypad enter key is not recognized
https://bugs.kde.org/show_bug.cgi?id=377937 Christoph Feck changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376168] Vertical panels impedes dragging windows in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=376168 Bogdan Olar changed: What|Removed |Added CC||olar.bogdan@gmail.com --- Comment #4 from Bogdan Olar --- Same issue here. Here is a video demonstrating the issue: https://youtu.be/z4e5ttrpkZs Info: OS: KDE neon 5.9 KDE Plasma: 5.9.4 KDE Frameworks: 5.32.0 QT: 5.7.1 Kernel: 4.4.0-67-generic -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session
https://bugs.kde.org/show_bug.cgi?id=372597 Christoph Feck changed: What|Removed |Added Component|kcm_accessibility |general Assignee|gun...@schmi-dt.de |mgraess...@kde.org Product|systemsettings |frameworks-kwayland --- Comment #20 from Christoph Feck --- This seems to be caused by global objects in KWayland integration, which get deleted by __run_exit_handlers, probably after the wayland connection has been shutdown. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377962] kate crashes after closing a file with long lines / wayland [Backtrace with debug symbols attached]
https://bugs.kde.org/show_bug.cgi?id=377962 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 372597 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session
https://bugs.kde.org/show_bug.cgi?id=372597 --- Comment #19 from Christoph Feck --- *** Bug 377962 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377796] Segmentation fault when closing application
https://bugs.kde.org/show_bug.cgi?id=377796 --- Comment #1 from Christoph Feck --- Could you please test a more recent version, 15.12 is quite old already. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 376959] Core dump when closing Kate
https://bugs.kde.org/show_bug.cgi?id=376959 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |INVALID Status|NEEDSINFO |RESOLVED --- Comment #4 from Christoph Feck --- No response, changing status. If you have new information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377978] Unable to create new folder named "~" without using escape character
https://bugs.kde.org/show_bug.cgi?id=377978 --- Comment #1 from Christoph Feck --- This is consistent with POSIX behavior. In a bash shell, doing "mkdir ~" within a directory also says "mkdir: cannot create directory ‘/home/user’: File exists", while "mkdir \~" works. ~ in Unix is your home folder (and ~user is /home/user), so we probably should not silently allow creating directory names that start with a tilde character, but warn instead. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 378003] All packages: qt incompletely upgraded (qtbase-abi-5-5-1
https://bugs.kde.org/show_bug.cgi?id=378003 Unreal Name <2112...@jeffcoschools.us> changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 378003] New: All packages: qt incompletely upgraded (qtbase-abi-5-5-1
https://bugs.kde.org/show_bug.cgi?id=378003 Bug ID: 378003 Summary: All packages: qt incompletely upgraded (qtbase-abi-5-5-1 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: 2112...@jeffcoschools.us CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Only parts of Qt that are required for KDE are upgraded in KDE neon. This causes some serious issues. Musescore and Calibre can only be installed via the developers' AppImages and installers, respectively, due to an error with qtbase-abi-5-5-1 being a virtual package with no candidate providers. This is minor because as I said, there are workarounds. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files
https://bugs.kde.org/show_bug.cgi?id=346403
bchrist...@gmail.com changed:
What|Removed |Added
CC||bchrist...@gmail.com
--- Comment #12 from bchrist...@gmail.com ---
I would like to help get this bug's status changed to confirmed. The following
is enough to cause the bug to manifest:
$ mkdir ~/test
$ touch ~/test/{000..999}.txt
$ kdialog --getsavefilename ~/test/
Observations:
1) This causes a slowdown of 22–29 seconds on my i7 + SSD laptop while kdialog
eats up 100% of a core. If you are not seeing the slowdown, you can of course
add a few nines ;)
2) Subsequent runs of the kdialog line are always slow.
3) The slowdown is always present, regardless of whether or not the "Show
Previews" button is pressed.
4) Toggling the "Show Previews" button after the dialog becomes responsive does
NOT cause any additional delay (this is not just because my example involves
only empty files—it happens in real directories, too).
5) I can also confirm that another aspect of the bug is still present: If we
instead run
$ kdialog --getsavefilename ~/
...THEN navigate to ~/test/ via the GUI, there is no slowdown whatsoever. I
feel that this is a key point because it shows that there is nothing inherently
slow about displaying a large number of files in kdialog.
Please take another look at this bug.
Arch Linux / Plasma 5.9.4 / Frameworks 5.32.0 / QT 5.8.0 / kdialog 1.0
--
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 --- Comment #31 from Christoph Feck --- Created attachment 104707 --> https://bugs.kde.org/attachment.cgi?id=104707&action=edit Change the meaning of the Close button Yes, it is KDE, a community of volunteers. Adding more comments to a feature request won't magically change code, especially when there was no consensus. Here is a patch. It changes the meaning of the "Close Split View" toolbar button from "Close Active Split View" to "Close Inactive Split View". I did not search for descriptive texts, so these might be wrong now. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377991] Change color scheme for editor in KDevelop also changes color in other instances of Kate/KWrite
https://bugs.kde.org/show_bug.cgi?id=377991 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #2 from Sven Brauch --- IIRC we discussed shared settings on kwrite-devel a while back and there was some consensus that it wasn't such a great idea to have all the settings shared among all applications after all. I could imagine it gets changed back (it wasn't like this in 4.x) in the future. For the time being, I guess it just is like it is though ... -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 378002] New: Kde crashes on certain folder
https://bugs.kde.org/show_bug.cgi?id=378002 Bug ID: 378002 Summary: Kde crashes on certain folder Product: konqueror Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jerobarr...@yahoo.com.ar Target Milestone: --- Application: konqueror (4.14.16) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-67-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: downloaded something, and now it crashes when i open that folder but i have no idea what causes it The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b3729e900 (LWP 3843))] Thread 3 (Thread 0x7f7b137ce700 (LWP 3847)): #0 0x7f7b36b99b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b2fdb138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b2fdb149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b336da2ce in QEventDispatcherGlib::processEvents (this=0x7f7b0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f7b336a818f in QEventLoop::processEvents (this=this@entry=0x7f7b137cdc80, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f7b336a84f5 in QEventLoop::exec (this=this@entry=0x7f7b137cdc80, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f7b33597549 in QThread::exec (this=this@entry=0x19403f0) at thread/qthread.cpp:538 #7 0x7f7b33688223 in QInotifyFileSystemWatcherEngine::run (this=0x19403f0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f7b33599e3c in QThreadPrivate::start (arg=0x19403f0) at thread/qthread_unix.cpp:352 #9 0x7f7b302a66ba in start_thread (arg=0x7f7b137ce700) at pthread_create.c:333 #10 0x7f7b36ba582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f7b193ee700 (LWP 3846)): #0 0x7f7b36b9569d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b2fdf46f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b2fdb0e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b2fdb1330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7b2fdb149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7b336da2ce in QEventDispatcherGlib::processEvents (this=0x7f7b140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f7b336a818f in QEventLoop::processEvents (this=this@entry=0x7f7b193edcd0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f7b336a84f5 in QEventLoop::exec (this=this@entry=0x7f7b193edcd0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f7b33597549 in QThread::exec (this=) at thread/qthread.cpp:538 #9 0x7f7b33599e3c in QThreadPrivate::start (arg=0x17527b0) at thread/qthread_unix.cpp:352 #10 0x7f7b302a66ba in start_thread (arg=0x7f7b193ee700) at pthread_create.c:333 #11 0x7f7b36ba582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7b3729e900 (LWP 3843)): [KCrash Handler] #6 0x7f7b36ad4428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f7b36ad602a in __GI_abort () at abort.c:89 #8 0x7f7b3358ef15 in qt_message_output (msgType=, buf=0x1eead38 "konqueror(3843): Programming error in KMimeType XML loading, please create a bug report on http://bugs.kde.org and attach the file \"/usr/share/mime/application/vnd.android.package-archive.xml\" ") at global/qglobal.cpp:2447 #9 0x7f7b33b7fafa in QDebug::~QDebug (this=0x7ffdf2117e50, __in_chrg=) at /usr/include/qt4/QtCore/qdebug.h:85 #10 KMimeTypePrivate::ensureXmlDataLoaded (this=this@entry=0x17a77d0) at /build/kde4libs-oFCmS0/kde4libs-4.14.16/kdecore/services/kmimetype.cpp:689 #11 0x7f7b33b800c8 in KMimeTypePrivate::iconName (this=0x17a77d0) at /build/kde4libs-oFCmS0/kde4libs-4.14.16/kdecore/services/kmimetype.cpp:792 #12 0x7f7b33b7ba32 in KMimeType::iconName (this=this@entry=0x1aa8220, url=...) at /build/kde4libs-oFCmS0/kde4libs-4.14.16/kdecore/services/kmimetype.cpp:607 #13 0x7f7b355f2f86 in KFileItem::iconName (this=this@entry=0x7ffdf21181e0) at /build/kde4libs-oFCmS0/kde4libs-4.14.16/kio/kio/kfileitem.cpp:921 #14 0x7f7b355f3574 in KFileItem::determineMimeType (this=0x7ffdf21181e0) at /build/kde4libs-oFCmS0/kde4libs-4.14.16/kio/kio/kfileitem.cpp:798 #15 0x7f7b21c98dca in KFileItemModelRolesUpdater::startPreviewJob() () from /usr/lib/libdolphinprivate4.so.4 #16 0x7f7b21c9e3a5 in ?? () from /usr/lib/libdolphinprivate4.so.4 #17 0x7f7b336be010 in QMetaObject::a
[dolphin] [Bug 158090] show the size of the folder in the "size" column
https://bugs.kde.org/show_bug.cgi?id=158090 --- Comment #16 from Nate Graham --- Right, I understand the trade-offs involved. Personally I'm willing to accept those trade-offs, but obviously not everyone would. In the macOS Finder, turning on this feature is optional, probably for the same reasons. It could be similarly optional here, too. Turn it on if you like it, don't if you don't. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 158090] show the size of the folder in the "size" column
https://bugs.kde.org/show_bug.cgi?id=158090 --- Comment #15 from Christoph Feck --- > calculating folder size is instantaneous ... but pollutes kernel caches with data that you may not need. > simple cache this information Cache where? How to decide if the information in the cache is still valid? If it was simple, the Linux kernel would provide this information. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376522] longer usage crash
https://bugs.kde.org/show_bug.cgi?id=376522 --- Comment #7 from Aram --- I tried to reproduce again... but i failed... will be using the app to see if it will crash again... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376549] Discover freezes on search
https://bugs.kde.org/show_bug.cgi?id=376549 --- Comment #4 from Christoph Feck --- If you can provide the information requested in comment #3, please add it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376522] longer usage crash
https://bugs.kde.org/show_bug.cgi?id=376522 --- Comment #6 from Christoph Feck --- If this is reproducible, please ask in a forum of your distribution how to install the missing debuginfo packages for discover. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378001] New: Plasma crash while exploring digital clock settings
https://bugs.kde.org/show_bug.cgi?id=378001 Bug ID: 378001 Summary: Plasma crash while exploring digital clock settings Product: plasmashell Version: 5.9.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bryan.j.don...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Looking at the different options to configure digital clock settings. I first changed the format to show date and 24-hour clock. I applied changes, then looked through the other tabs on the left side. The application crashed specifically after looking at calendar. - Unusual behavior I noticed: Before the crash, I had no calendars under "PIM Events Plugin" and no options under "Calendar." After the crash, I was unable to reproduce the error, but I noticed that I have access to the default calendars under PIM Events Plugin (Birthdays & Anniversaries, Personal Calendar) and I have checkboxes available under Calendar. I wonder if this bug is related to me not having set up Kontact or my PIM yet. - Custom settings of the application: Kontact/PIM not yet set up. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3732e48580 (LWP 2225))] Thread 9 (Thread 0x7f36520b4700 (LWP 4168)): #0 0x7f372c4fb7bd in poll () from /lib64/libc.so.6 #1 0x7f372730c896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f372730c9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f372ce1e18b in QEventDispatcherGlib::processEvents (this=0x7f364c0013d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f372cdc7aea in QEventLoop::exec (this=this@entry=0x7f36520b3cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f372cbf5813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f372cbfa4c8 in QThreadPrivate::start (arg=0x555f660) at thread/qthread_unix.cpp:368 #7 0x7f372baab537 in start_thread () from /lib64/libpthread.so.0 #8 0x7f372c50504f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f36518b3700 (LWP 4164)): #0 0x7f3727351f49 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f372730b760 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7f372730c745 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f372730c9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f372ce1e18b in QEventDispatcherGlib::processEvents (this=0x7f3644002c00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f372cdc7aea in QEventLoop::exec (this=this@entry=0x7f36518b2cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f372cbf5813 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f372fce7305 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f372cbfa4c8 in QThreadPrivate::start (arg=0x3615500) at thread/qthread_unix.cpp:368 #9 0x7f372baab537 in start_thread () from /lib64/libpthread.so.0 #10 0x7f372c50504f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f3664bfc700 (LWP 2947)): #0 0x7f372730bfd4 in g_main_context_query () from /usr/lib64/libglib-2.0.so.0 #1 0x7f372730c808 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f372730c9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f372ce1e18b in QEventDispatcherGlib::processEvents (this=0x7f3668c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f372cdc7aea in QEventLoop::exec (this=this@entry=0x7f3664bfbcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f372cbf5813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f36674b5df7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7f372cbfa4c8 in QThreadPrivate::start (arg=0x45c8f60) at thread/qthread_unix.cpp:368 #8 0x7f372baab537 in start_thread () from /lib64/libpthread.so.0 #9 0x7f372c50504f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f3679fa8700 (LWP 2424)): #0 0x7f3727351f49 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f372730bd89 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f372730c7bb in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f372730c9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f372ce1e18b in QEventDispatcherGlib::processEvents (this=0x7f36740
[kdenlive] [Bug 378000] New: When creating archive, slideshow images are not included
https://bugs.kde.org/show_bug.cgi?id=378000 Bug ID: 378000 Summary: When creating archive, slideshow images are not included Product: kdenlive Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: f...@fuxoft.cz Target Milestone: --- Created attachment 104706 --> https://bugs.kde.org/attachment.cgi?id=104706&action=edit Screenshotof the archive creation window When creating archive, the slideshow images are not included in the resulting .tar.gz file at all. Before creating the archive, you are warned that there are "missing clips in your project" but there is no indication what these are. In the attached screenshot, one of those image sequences is highlighted by me manually. When archiving your project, this can have catastrophic consequences. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377999] New: Wrong media paths when opening project from archive
https://bugs.kde.org/show_bug.cgi?id=377999 Bug ID: 377999 Summary: Wrong media paths when opening project from archive Product: kdenlive Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: f...@fuxoft.cz Target Milestone: --- Created attachment 104705 --> https://bugs.kde.org/attachment.cgi?id=104705&action=edit Screenshot When attempting to open project from complete archive (zipped with all media), the clips cannot be opened because Kdenlive attempts to open the media from invalid paths. See the screenshot. Those paths point neither to the video files in the unpacked archive (/home/fuxoft/Downloads/unpack/test1/videos/...) as they should, nor to the original media file locations (/home/fuxoft/Videos/fukafutokyu/...). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377991] Change color scheme for editor in KDevelop also changes color in other instances of Kate/KWrite
https://bugs.kde.org/show_bug.cgi?id=377991 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #1 from Francis Herne --- All the ktexteditor settings are shared; usually people prefer to have their editor behave consistently and not have subtle differences between applications. Perhaps it would make sense for the colour scheme to be an exception now that the main UI scheme can be set differently in KDevelop. You can temporarily set the colour of an editor window with View -> Schema, which won't be saved anywhere and doesn't affect other applications. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 339533] libvncserver/rfbregion.c:754: possible bad compound assignment
https://bugs.kde.org/show_bug.cgi?id=339533 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- We don't ship libvncserver anymore -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 356782] krfb stops sending updates after the first frame
https://bugs.kde.org/show_bug.cgi?id=356782 Albert Astals Cid changed: What|Removed |Added CC||t.ki...@gmail.com --- Comment #14 from Albert Astals Cid --- *** Bug 363217 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 363217] VNC connection to KDE5 is not possible
https://bugs.kde.org/show_bug.cgi?id=363217 Albert Astals Cid changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||aa...@kde.org --- Comment #6 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 356782 *** -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 356782] krfb stops sending updates after the first frame
https://bugs.kde.org/show_bug.cgi?id=356782 Albert Astals Cid changed: What|Removed |Added CC||ermschmi...@yahoo.com --- Comment #13 from Albert Astals Cid --- *** Bug 376614 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 376614] VNC viewer frozen desktop cursor moves Remote desktop sees cursor
https://bugs.kde.org/show_bug.cgi?id=376614 Albert Astals Cid changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 356782 *** -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 377998] x11 plugin needs porting/rewriting to xcb
https://bugs.kde.org/show_bug.cgi?id=377998 --- Comment #1 from Albert Astals Cid --- Alexei kind of volunteered to try to fix it :) -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 377998] x11 plugin needs porting/rewriting to xcb
https://bugs.kde.org/show_bug.cgi?id=377998 Albert Astals Cid changed: What|Removed |Added CC||alexey@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 377998] New: x11 plugin needs porting/rewriting to xcb
https://bugs.kde.org/show_bug.cgi?id=377998 Bug ID: 377998 Summary: x11 plugin needs porting/rewriting to xcb Product: krfb Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: aa...@kde.org Target Milestone: --- It's broken as it is right now and we're using the less optimal Qt plugin -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 356782] krfb stops sending updates after the first frame
https://bugs.kde.org/show_bug.cgi?id=356782 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #12 from Albert Astals Cid --- The fix was by Alexey, i forgot to give him credit when doing the git commit, very sorry about that :/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI
https://bugs.kde.org/show_bug.cgi?id=377698 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Ivo Raisr --- Committed in SVN r16285. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 356782] krfb stops sending updates after the first frame
https://bugs.kde.org/show_bug.cgi?id=356782 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/krf ||b/c0ceb8a83de5d5a2be0f842ea ||fd84024bfeea6ed Status|CONFIRMED |RESOLVED --- Comment #11 from Albert Astals Cid --- Git commit c0ceb8a83de5d5a2be0f842eafd84024bfeea6ed by Albert Astals Cid. Committed on 23/03/2017 at 23:20. Pushed by aacid into branch 'Applications/17.04'. Set default framebuffer plugin to "qt" instead of "x11" Make default "qt" framebuffer plugin instead of "x11". Workaround for bug https://bugs.kde.org/show_bug.cgi?id=356782 Not a proper fix, ideally "x11" plugin needs to be fixed. REVIEW: 129721 M +1-1krfb/krfb.kcfg https://commits.kde.org/krfb/c0ceb8a83de5d5a2be0f842eafd84024bfeea6ed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377997] New: support for movement interpolation (animated background)
https://bugs.kde.org/show_bug.cgi?id=377997 Bug ID: 377997 Summary: support for movement interpolation (animated background) Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: muz...@gmail.com Target Milestone: --- It would be great to have a tool to create simple background movement. In krita documentation there's a perfect example: https://docs.krita.org/File:Introduction_to_animation_walkcycle_02.gif ideally we should create a layer with an image bigger than the canvas and give a start and end point, then krita should create all intermediate steps. in this video you can see the concept: https://www.youtube.com/watch?v=wttkDsaZMFA -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 361723] kdf in kf5 does not show all mounted compared to kdf in kde4
https://bugs.kde.org/show_bug.cgi?id=361723 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377652] Some Kicker icons should be highlighted while hovering cursor over them (like in Kickoff)
https://bugs.kde.org/show_bug.cgi?id=377652 --- Comment #10 from Fincer --- Just tested the patches. Highlighting works as expected with them. Thank you so much for your trouble and fast response! Finally after these years Kicker can be used as a perfect replacement for Kickoff without suffering from any of these little annoyances. Hopefully your patches will be implemented soon. I consider the issue as fixed. Thank you again! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377995] Crash when turning off breakpoint in editor window
https://bugs.kde.org/show_bug.cgi?id=377995 Piotr Mierzwinski changed: What|Removed |Added Component|general |CPP Debugger CC||niko.s...@gmail.com, ||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377996] New: Discover crashes when starting
https://bugs.kde.org/show_bug.cgi?id=377996 Bug ID: 377996 Summary: Discover crashes when starting Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: funkyafro...@gmail.com Target Milestone: --- Application: plasma-discover (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-42-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: Trying to start Discover either from the update icon in the system tray or directly from the launcher The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94f343bd40 (LWP 143470))] Thread 5 (Thread 0x7f94de22c700 (LWP 143474)): #0 0x7f94fa9f3042 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f94fa9acecc in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f94fa9ad8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f94fa9adaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f94fe3644ab in QEventDispatcherGlib::processEvents (this=0x7f94d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f94fe30c0fa in QEventLoop::exec (this=this@entry=0x7f94de22bd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f94fe131d43 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f94fe136c68 in QThreadPrivate::start (arg=0x55c7cead7c50) at thread/qthread_unix.cpp:341 #8 0x7f94faed16ca in start_thread (arg=0x7f94de22c700) at pthread_create.c:333 #9 0x7f94fd7390af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f94e6958700 (LWP 143473)): #0 0x7f94fa9f3029 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f94fa9acee5 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f94fa9ad8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f94fa9adaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f94fe3644ab in QEventDispatcherGlib::processEvents (this=0x7f94d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f94fe30c0fa in QEventLoop::exec (this=this@entry=0x7f94e6957ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f94fe131d43 in QThread::exec (this=this@entry=0x55c7ce6c2d30) at thread/qthread.cpp:500 #7 0x7f95002f6c65 in QQmlThreadPrivate::run (this=0x55c7ce6c2d30) at qml/ftw/qqmlthread.cpp:141 #8 0x7f94fe136c68 in QThreadPrivate::start (arg=0x55c7ce6c2d30) at thread/qthread_unix.cpp:341 #9 0x7f94faed16ca in start_thread (arg=0x7f94e6958700) at pthread_create.c:333 #10 0x7f94fd7390af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f94e7b69700 (LWP 143472)): #0 0x7f94fd728c8d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f94fa9f1c80 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f94fa9ad485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f94fa9ad974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f94fa9adaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f94fe3644ab in QEventDispatcherGlib::processEvents (this=0x7f94e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #6 0x7f94fe30c0fa in QEventLoop::exec (this=this@entry=0x7f94e7b68cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f94fe131d43 in QThread::exec (this=this@entry=0x7f94fb7ddd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #8 0x7f94fb769575 in QDBusConnectionManager::run (this=0x7f94fb7ddd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:171 #9 0x7f94fe136c68 in QThreadPrivate::start (arg=0x7f94fb7ddd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #10 0x7f94faed16ca in start_thread (arg=0x7f94e7b69700) at pthread_create.c:333 #11 0x7f94fd7390af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f94f04dd700 (LWP 143471)): #0 0x7f94fd72d0bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f94f8b37c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f94f8b398d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f94f3067299 in QXcbEventReader::run (this=0x55c7ce6293f0) at
[kdevelop] [Bug 377995] New: Crash when turning off breakpoint in editor window
https://bugs.kde.org/show_bug.cgi?id=377995 Bug ID: 377995 Summary: Crash when turning off breakpoint in editor window Product: kdevelop Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Application: kdevelop (5.1.0) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.4-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have set breakpoint in line N. I run debugging for application, debugger stopped on set breakpoint and I continue running application. I closed application, and back to code when breakpoint was set. About 10 rows before breakpoint I paseted 4 new lines of code, so in place N-10 lines I inserted new code. Previously set breakpoint has multiplicated. I mean was present in two places - in original line and 4 lines above this place. I wanted turn off this breakpoint or second - original (sorry I don't remember well which was it), so I clicked on breakpointer placed on left bar in editor window. After first time nothing happened, but after second application crashed. I used debugger dbg (version: 7.12.1) Above bug I also met in version 5.0.x The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f933ee5e600 (LWP 9988))] Thread 17 (Thread 0x7f92ccff9700 (LWP 13422)): #0 0x7f9335668756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f932d3bf234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f932d3bf279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f93356622e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f933bc5554f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f92ce7fc700 (LWP 10027)): #0 0x7f933bc4b67d in poll () at /usr/lib/libc.so.6 #1 0x7f93334157a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93334158bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f933c57206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f933c51b89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f933c33da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f933c3426d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f93356622e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f933bc5554f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f92c700 (LWP 10020)): #0 0x7f9335668756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f933c34358b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9330a251d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f9330a299d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f9330a29a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f9330a29a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f9330a29a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f9330a29a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f9330a29a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f9330a24263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f9330a27249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f933c3426d8 in () at /usr/lib/libQt5Core.so.5 #17 0x7f93356622e7 in start_thread () at /usr/lib/libpthread.so.0 #18 0x7f933bc5554f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f92f0ff9700 (LWP 10019)): #0 0x7f9335668756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f933c34358b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9330a251d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeav
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Garry Williams changed: What|Removed |Added CC||gtwilli...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 377994] KInfocenter should read plasma version from a KDE-provided resource, not a distro-provided file
https://bugs.kde.org/show_bug.cgi?id=377994 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 377994] New: KInfocenter should read plasma version from a KDE-provided resource, not a distro-provided file
https://bugs.kde.org/show_bug.cgi?id=377994 Bug ID: 377994 Summary: KInfocenter should read plasma version from a KDE-provided resource, not a distro-provided file Product: kinfocenter Version: 5.9.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: pointedst...@zoho.com Target Milestone: --- I have Plasma 5.9.3. Due to a SUSE packaging error (https://bugzilla.opensuse.org/show_bug.cgi?id=1030559), I wound up with mismatched package-versions: zypper info plasma5-session plasma5-desktop | grep -B 1 Version Name : plasma5-session Version: 5.9.2-1.1 -- Name : plasma5-desktop Version: 5.9.3-2.1 plasma5-session provides the .desktop file that KInfocenter reads to determine the Plasma version, and therefore KInfocenter inappropriately says I have Plasma 5.9.2. KInfoCenter should read this information from a KDE-provided resource, not a distro-provided one. Perhaps `plasmashell --version`? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377952] Assistant Tool cursor follow does not draw
https://bugs.kde.org/show_bug.cgi?id=377952 --- Comment #11 from flibbertigibbet...@gmail.com --- https://youtu.be/IWvH61Bfcjc Created video to demonstrate the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377993] New: Closing laptop lid no longer blocks session if second screen is connected
https://bugs.kde.org/show_bug.cgi?id=377993 Bug ID: 377993 Summary: Closing laptop lid no longer blocks session if second screen is connected Product: plasmashell Version: 5.8.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: germano.massu...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 When you close the laptop screen lid, Plasma blocks the user session. If I plug a second (HDMI in my case) screen/projector in "extend" (not screen cloning) mode then I close the laptop lid, Plasma will simply switch off the laptop screen and move all applications to second screen. No user session block will be applied. plasma-desktop-5.8.6-3.fc25.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377652] Some Kicker icons should be highlighted while hovering cursor over them (like in Kickoff)
https://bugs.kde.org/show_bug.cgi?id=377652 --- Comment #9 from Eike Hein --- Patches to plasma-framework and Kicker under review: https://phabricator.kde.org/D5160 https://phabricator.kde.org/D5162 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)
https://bugs.kde.org/show_bug.cgi?id=340777 --- Comment #12 from Luiz Angelo De Luca --- > Can you pass the following lines to gbd and rerun the executable? > > set heuristic-fence-post 99 > handle SIGSEGV noprint nostop pass > > Keep running (w/ "continue") GDB until it fails. If I use both, gdb goes until valgrind quits with 'Child terminated with signal = 0xb (SIGSEGV)' If I use only heuristic-fence-post (before first cont), nothing changes. I also tried to use it after sigsegv hit, but then, gdb never returned. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI
https://bugs.kde.org/show_bug.cgi?id=377698 --- Comment #8 from Diane M --- Created attachment 104704 --> https://bugs.kde.org/attachment.cgi?id=104704&action=edit updated patch I hope this patch works better. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377197] Customize grouping behaviour [patch]
https://bugs.kde.org/show_bug.cgi?id=377197 --- Comment #24 from Maik Qualmann --- Simon, "Move To Album..." does not work. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #80 from Maik Qualmann --- Git commit 5cd5b23b6ddb9eab927f1e7a68e593c138c7c538 by Maik Qualmann. Committed on 23/03/2017 at 20:18. Pushed by mqualmann into branch 'master'. draw grouped border only if the group closed M +4-1app/items/imagedelegate.cpp https://commits.kde.org/digikam/5cd5b23b6ddb9eab927f1e7a68e593c138c7c538 -- You are receiving this mail because: You are watching all bug changes.
[picmi] [Bug 377992] New: The default theme could use some tuneup
https://bugs.kde.org/show_bug.cgi?id=377992 Bug ID: 377992 Summary: The default theme could use some tuneup Product: picmi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jakob.gru...@gmail.com Reporter: andr...@ubuntu.si Target Milestone: --- Created attachment 104703 --> https://bugs.kde.org/attachment.cgi?id=104703&action=edit KSudoku Scribble Dear Maintainer, currently the appearance of the default theme is not optimal: - the border around each cell is currently too thick, which causes Hermann grid illusion (dots appear on intersections) at certain zoom levels - the division between 5x5 blocks is relatively hard too see - the solved numbers could be crossed over instead of just turning gray For 1 and 2, please have a look at KSudoku theme Scribble. The cell borders in that theme could be slightly thicker, but overall it looks really nice. Best Regards, Andrej Mernik -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377991] Change color scheme for editor in KDevelop also changes color in other instances of Kate/KWrite
https://bugs.kde.org/show_bug.cgi?id=377991 Piotr Mierzwinski changed: What|Removed |Added Summary|Change color scheme for |Change color scheme for |editor in KDevelop also |editor in KDevelop also |changes color in other |changes color in other |instance of Kate/KWrite |instances of Kate/KWrite CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377991] New: Change color scheme for editor in KDevelop also changes color in other instance of Kate/KWrite
https://bugs.kde.org/show_bug.cgi?id=377991 Bug ID: 377991 Summary: Change color scheme for editor in KDevelop also changes color in other instance of Kate/KWrite Product: kdevelop Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- As in title. When I changed default color scheme for editor in KDevelop I discovered that in all new instances of Kate/KWrite I have the same colors :/. Why editor color scheme in KDevelop shares the same settings with Kate/KWrite? Isn't possible to separate it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377990] New: Desktop Grid + Present Windows Effect: Non maximized windows disappear during movement
https://bugs.kde.org/show_bug.cgi?id=377990 Bug ID: 377990 Summary: Desktop Grid + Present Windows Effect: Non maximized windows disappear during movement Product: kwin Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: qb...@ungmedms.com Target Milestone: --- Reproducible: Always Steps to Reproduce: 1. Enable Desktop Grid + Present Windows Effect 2. Check the "Use Present Windows Effect to layout the windows" 3. Show the Desktop Grid 4. Drag a non maximized window Actual Results: The window disappear during movement. Expected Results: The window follows the mouse pointer the same way as for maximized windows (or when "Use Present Windows Effect to layout the windows" is unchecked). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 266154] Bogofilter doesn't work with KMail anymore
https://bugs.kde.org/show_bug.cgi?id=266154 Matija Šuklje changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #20 from Matija Šuklje --- No idea what caused it, but I found it and here’s a fix/workaround… Actual problem: `~/.kde4/share/config/akonadi_mailfilter_agentrc` suddenly prepends my home directory to the bogofilter line. e.g. it says: `action-args-1=/home/hook/bogofilter -s` …which is obviously wrong. Fix/workaround: change all such lines in the file (or via the KMail Filter dialog) to point to the actual command, which can be easily found by running `which bogofilter` in the console. Most likely this will be: `action-args-1=/usr/bin/bogofilter -s` Side-note: The same applies for the antivirus scan filter and the `kmail_clamav.sh` line. Closing the bug again, as it seems it’s somewhat different and the workaround is stated above. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377906] Meta key no longer works after switching to tty1 with Ctrl+Alt+F1
https://bugs.kde.org/show_bug.cgi?id=377906 b...@ancilla.ca changed: What|Removed |Added CC||b...@ancilla.ca --- Comment #2 from b...@ancilla.ca --- All the affected machines are using libinput; I can try switching to evdev and see if that fixes it as a stopgap until the fix in master lands here, but I think I switched from evdev to libinput in the first place because other stuff didn't work in evdev. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur
https://bugs.kde.org/show_bug.cgi?id=241557 Qbert changed: What|Removed |Added CC||qb...@ungmedms.com --- Comment #21 from Qbert --- This bug is still present, and annoying, in 5.9.3. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377928] kwallet fails to build under macOS
https://bugs.kde.org/show_bug.cgi?id=377928 --- Comment #2 from Yurii Kolesnykov --- $ brew uninstall gpgme solves problem -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377928] kwallet fails to build under macOS
https://bugs.kde.org/show_bug.cgi?id=377928 --- Comment #1 from Yurii Kolesnykov --- The most interesting part is: make[2]: *** No rule to make target `/usr/local/Cellar/gpgme/1.7.0/lib/libgpgme.so', needed by `src/runtime/kwalletd/backend/libkwalletbackend5.5.32.0.dylib'. Stop. -- 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 --- Comment #30 from Ettore Atalan --- (In reply to fgf from comment #28) > I do not understand, why a behaviour that annoys and frustrates many people > is apparently ignored or even defended for no good reason. It's KDE ... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377988] The text of some buttons are not readable using kde environment (KDE Plasma 5.8)
https://bugs.kde.org/show_bug.cgi?id=377988 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Fixed in the current release. 2.9 is ancient history. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 377584] libgetdata update from 0.9.4-0~28~ubuntu12.04.1 to 0.10.0-0~32~ubuntu12.04.1 broke kst on Ubuntu 12.04 LTS
https://bugs.kde.org/show_bug.cgi?id=377584 --- Comment #2 from Michael Brewer --- (In reply to Christoph Feck from comment #1) > I suggest to report this to Ubuntu developers, who maintain the LTS support. The problem is that libgetdata 0.10.0-0~32 is not compatible with the latest version of kst (2.0.8.3~3098~35) available in the kst-plot ppa for ubuntu 12.04 LTS. I see that an attempt was made to compile kst version 2.0.8.3~3175~38 for ubuntu 12.04 at the kst-plot ppa which would presumably be compatible, but it failed. Until you are able to compile this newer version of kst, you should revert to version 0.9.4.0~28 of the libgetdata package in the ppa for 12.04. I see this as a ppa issue rather than an Ubuntu issue. Please correct me if I am wrong here. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377989] New: Dicover crashes when browsing
https://bugs.kde.org/show_bug.cgi?id=377989 Bug ID: 377989 Summary: Dicover crashes when browsing Product: Discover Version: 5.9.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: erik.itl...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.3) Qt Version: 5.7.1 Frameworks Version: 5.32.0 Operating System: Linux 4.4.0-66-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: Browsing around, searching, then clicking on packages. I restarted and continued browsing only to see it crash again. - Unusual behavior I noticed: After crashing and while I was restarting I got a message that Package Deamon had crashed. This happened at least twice. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2547a498c0 (LWP 11894))] Thread 7 (Thread 0x7f25158fc700 (LWP 11918)): #0 0x7f2543d7fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f253f15638c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f24ec0acfc0, timeout=, context=0x7f24ec000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f253f15638c in g_main_context_iterate (context=context@entry=0x7f24ec000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f253f15649c in g_main_context_iteration (context=0x7f24ec000990, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f25449a875b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25449530ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2544782f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2544787b48 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f25412116ba in start_thread (arg=0x7f25158fc700) at pthread_create.c:333 #9 0x7f2543d8b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f25177ac700 (LWP 11915)): #0 0x7f2543d7fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f253f15638c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f2510001670, timeout=, context=0x7f251990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f253f15638c in g_main_context_iterate (context=context@entry=0x7f251990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f253f15649c in g_main_context_iteration (context=0x7f251990, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f25449a875b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25449530ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2544782f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2544787b48 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f25412116ba in start_thread (arg=0x7f25177ac700) at pthread_create.c:333 #9 0x7f2543d8b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2526c82700 (LWP 11899)): #0 0x7f253f153407 in g_source_iter_next (iter=iter@entry=0x7f2526c81ad0, source=source@entry=0x7f2526c81ac8) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:952 #1 0x7f253f155cea in g_main_context_check (context=context@entry=0x7f251c002ed0, max_priority=2147483647, fds=fds@entry=0x7f251c01b4c0, n_fds=n_fds@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3661 #2 0x7f253f156330 in g_main_context_iterate (context=context@entry=0x7f251c002ed0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837 #3 0x7f253f15649c in g_main_context_iteration (context=0x7f251c002ed0, may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f25449a875b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f25449530ba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2544782f64 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f25470c9fc6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f2544787b48 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f25412116ba in start_thread (arg=0x7f2526
[krita] [Bug 377988] New: The text of some buttons are not readable using kde environment (KDE Plasma 5.8)
https://bugs.kde.org/show_bug.cgi?id=377988 Bug ID: 377988 Summary: The text of some buttons are not readable using kde environment (KDE Plasma 5.8) Product: krita Version: 2.9.7 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: imor...@gmail.com Target Milestone: --- Created attachment 104702 --> https://bugs.kde.org/attachment.cgi?id=104702&action=edit This picture shows the error Some of the button have unreadable text in it, it looks like the color of the text is same with the button. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 377987] New: Show tooltips with more information when hovering the mouse cursor over the search results
https://bugs.kde.org/show_bug.cgi?id=377987 Bug ID: 377987 Summary: Show tooltips with more information when hovering the mouse cursor over the search results Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: cyberan...@gmail.com Target Milestone: --- I use krunner for pretty much everything on my desktop. Launching and killing apps, searching files, as a calculator, defining words etc. However, there are cases that the results could benefit from some added information that is quickly accessible before choosing the suitable result for each search. The main case I have in mind is file searching. Most of the times I need to know the location of a file before I decide which is the file that I am looking for. I know that currently when you hover the mouse over the results you get some additional information in the empty space beside each result. Specifically when you are getting file search results you get the file location, but either most of the times the filename will be long enough that the location (if not the filename itself as well) is trimmed, or the location itself will be long enough so again the location is trimmed. Eventually I have to click the "Open Containing Folder" button in order to see the location of the file and if I am not satisfied I have to close the file browser that I just opened by clicking the "Open Containing Folder" button and search again. The result is decreased productivity, which counters the main point why I (and I guess everyone else) use krunner. If we had tooltips that would show this extra precious information that doesn't fit in the empty space beside each result this problem could be solved. Another example is when using the dictionary plugin. In the current form the dictionary plugin is almost useless, because the definition of a word doesn't fit in the search result most of the times. A tooltip could provide the complete definition to the user without any trimming. So just to make the story short: this wishlist asks for tooltips that will provide more info for each search result whenever the additional info that is provided already in the empty space beside the search result doesn't fit. Currently this additional info is trimmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377469] Applet pops up when clicking on Audio Volume settings
https://bugs.kde.org/show_bug.cgi?id=377469 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #2 from Marco Martin --- (In reply to David Rosca from comment #1) > That's a bug in plasmashell and it is only affected when using with Qt 5.8. do you have more informations on what the bug is? i can reproduce the bug even if i disable all the qml in the config view, but it seems to happen only with this plasmoid and nothing else -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 Jonathan Riddell changed: What|Removed |Added CC||j...@jriddell.org --- Comment #5 from Jonathan Riddell --- apt install libqt5core5a-dbgsym -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 377986] New: Discover crushed after click on 'Установить' button from update system packages dialog from icon in system tray
https://bugs.kde.org/show_bug.cgi?id=377986 Bug ID: 377986 Summary: Discover crushed after click on 'Установить' button from update system packages dialog from icon in system tray Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: greysha...@gmail.com Target Milestone: --- Application: plasma-discover (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-41-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: 1. In System tray in buttom System notifier was notified me about new updates 2. I was click on update icon 3. packege update dialog appared 4. I have clicked on INstall button 5. Discover tried render main window but crushed The crash can be reproduced every time. -- Backtrace: Application: Центр приложений Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ebb8eed40 (LWP 3838))] Thread 7 (Thread 0x7f1e8f934700 (LWP 3844)): #0 0x7f1ec5bdc0bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1ec2e5c9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ec2e5cd62 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1e995284e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f1ec2e84325 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1ec33806ca in start_thread (arg=0x7f1e8f934700) at pthread_create.c:333 #6 0x7f1ec5be80af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f1e98135700 (LWP 3843)): #0 0x7f1ec2ea2044 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1ec2e5bfb0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ec2e5c8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1ec2e5caec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1ec2e5cb31 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1ec2e84325 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1ec33806ca in start_thread (arg=0x7f1e98135700) at pthread_create.c:333 #7 0x7f1ec5be80af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f1eac84d700 (LWP 3842)): #0 0x7f1ec6691726 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f1ec6811039 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f1ec6812d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1ec2e5c3c9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1ec2e5c974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1ec2e5caec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1ec68134ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1ec67bb0fa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1ec65e0d43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1ec65e5c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1ec33806ca in start_thread (arg=0x7f1eac84d700) at pthread_create.c:333 #11 0x7f1ec5be80af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f1eaee4d700 (LWP 3841)): #0 0x7f1ec2e6c820 in g_poll () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1ec2e5c9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ec2e5caec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1ec68134ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1ec67bb0fa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1ec65e0d43 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1ec87a5c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1ec65e5c68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1ec33806ca in start_thread (arg=0x7f1eaee4d700) at pthread_create.c:333 #9 0x7f1ec5be80af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f1eb005e700 (LWP 3840)): #0 0x7f1ec5bdc0bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1ec2e5c9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ec2e5caec in g_main_context_iteration
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 --- Comment #4 from Kamil M --- (In reply to Eike Hein from comment #3) > Thanks! Unfortunately the backtrace lacks symbols for QtCore and KDE > Frameworks 5. Could you install those and get a new backtrace? Please could you tell how can I do it? I am a novice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 --- Comment #3 from Eike Hein --- Thanks! Unfortunately the backtrace lacks symbols for QtCore and KDE Frameworks 5. Could you install those and get a new backtrace? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 --- Comment #2 from Marco Martin --- maybe related with https://bugs.kde.org/show_bug.cgi?id=377588 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377561] Panels switched after screen switched off
https://bugs.kde.org/show_bug.cgi?id=377561 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- is the screen that's switched off marked as "primary"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 --- Comment #2 from Kamil M --- Created attachment 104701 --> https://bugs.kde.org/attachment.cgi?id=104701&action=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377588] plasma panels not shown after reboot
https://bugs.kde.org/show_bug.cgi?id=377588 --- Comment #3 from Marco Martin --- indeed wrong.. is the system multimonitor? perhaps a second screen that has been attached and detached in the past? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 Eike Hein changed: What|Removed |Added Severity|major |crash Keywords|usability | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Eike Hein --- Please add a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 Alex Bikadorov changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377526] Plasma Task Manager Widget Use Too Much Space when Screen Edging to Left or Right.
https://bugs.kde.org/show_bug.cgi?id=377526 --- Comment #7 from Eike Hein --- The icon size option is in fact only available for left / right, since they make no sense otherwise. Could you attach a screenshot of your config dialog so we can be sure we're talking about the same thing perhaps? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 Kamil M changed: What|Removed |Added Severity|crash |major Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377984] plasmashell crashes when some window closed on right click
https://bugs.kde.org/show_bug.cgi?id=377984 Kamil M changed: What|Removed |Added CC||kamilmro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377985] New: I have 2 emails in outbox that I cannot delete
https://bugs.kde.org/show_bug.cgi?id=377985 Bug ID: 377985 Summary: I have 2 emails in outbox that I cannot delete Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mixed Maildir resource Assignee: kdepim-b...@kde.org Reporter: sgr...@redhat.com CC: kram...@kde.org Target Milestone: --- I have 2 emails in my outbox that I cannot delete. Trying to delete them causes these messages in syslog: Mar 23 13:01:37 x2 akonadi_mixedmaildir_resource: "Given item identifier is empty" Mar 23 13:01:38 x2 akonadi_mixedmaildir_resource: Item(remoteId= "" , mimeType= "message/rfc822" , parentCollection= "outbox" ) Mar 23 13:01:38 x2 akonadi_mixedmaildir_resource: log_mixedmaildirresource: "Given item identifier is empty" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377799] Plasmashell crash due to invalid receiver in posted event
https://bugs.kde.org/show_bug.cgi?id=377799 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- pasting inline Thread 1 "plasmashell" received signal SIGSTOP, Stopped (signal). 0x7156a42d in nanosleep () from /usr/lib/libc.so.6 The program is not being run. Argument list to give program being debugged when it is started is "-n". Starting program: /usr/bin/plasmashell -n [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe1cb7700 (LWP 8978)] [New Thread 0x7fffdbb61700 (LWP 8979)] [New Thread 0x7fffda119700 (LWP 8980)] [New Thread 0x7fffd3fff700 (LWP 8981)] [New Thread 0x7fffd1f9a700 (LWP 8982)] [New Thread 0x7fff4001b700 (LWP 8983)] [New Thread 0x7fff2e84c700 (LWP 9021)] [New Thread 0x7fff27fff700 (LWP 9025)] [New Thread 0x7fff277fe700 (LWP 9026)] [New Thread 0x7fff26ffd700 (LWP 9027)] [New Thread 0x7fff267fc700 (LWP 9028)] [New Thread 0x7fff25ffb700 (LWP 9029)] [New Thread 0x7fff257fa700 (LWP 9030)] [New Thread 0x7fff24ff9700 (LWP 9031)] [New Thread 0x7fff07fff700 (LWP 9032)] [New Thread 0x7fff077fe700 (LWP 9033)] [New Thread 0x7fff06ffd700 (LWP 9034)] [New Thread 0x7fff067fc700 (LWP 9035)] [New Thread 0x7fff05ffb700 (LWP 9036)] [New Thread 0x7fff057fa700 (LWP 9037)] [New Thread 0x7fff04ff9700 (LWP 9038)] [New Thread 0x7ffee7fff700 (LWP 9039)] [New Thread 0x7ffee77fe700 (LWP 9040)] [Thread 0x7fff2e84c700 (LWP 9021) exited] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x6b2880) at kernel/qcoreapplication.cpp:1630 1630--r->d_func()->postedEvents; Thread 24 (Thread 0x7ffee77fe700 (LWP 9040)): #0 0x70b44756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x71c8c5fb in QWaitConditionPrivate::wait(unsigned long) (time=18446744073709551615, this=0x36f0840) at thread/qwaitcondition_unix.cpp:143 #2 0x71c8c5fb in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x364f920, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fff3c0dc1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fff3c0e09d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fff3c0e0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fff3c0e0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fff3c0e0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fff3c0de249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x71c8b748 in QThreadPrivate::start(void*) (arg=0x7ffefc002b90) at thread/qthread_unix.cpp:368 #14 0x70b3e2e7 in start_thread () at /usr/lib/libpthread.so.0 #15 0x7159c54f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7ffee7fff700 (LWP 9039)): #0 0x70b44756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x71c8c5fb in QWaitConditionPrivate::wait(unsigned long) (time=18446744073709551615, this=0x36f0840) at thread/qwaitcondition_unix.cpp:143 #2 0x71c8c5fb in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x364f920, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fff3c0dc1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fff3c0e09d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fff3c0e0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fff3c0db263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fff3c0de249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x71c8b748 in QThreadPrivate::start(void*) (arg=0x7ffeec003190) at thread/qthread_unix.cpp:368 #10 0x70b3e2e7 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7159c54f in clone () at /usr/lib/libc.so.6 Threa
