[digikam] [Bug 376661] When importing ~200,000 video files Digikam crashes in about 2-5 seconds of starting.
https://bugs.kde.org/show_bug.cgi?id=376661 --- Comment #11 from caulier.gil...@gmail.com --- The xmp warning is not the problem. But it's know that Exiv2 have many problem with video files. I recommend to not try to scan your huge collection in one time. Start with a fresh database and add video files by chunks step by step until crash appear. To goal is to isolate the file which introduce the dysfunction. After that, report the problem to Exiv2 bugzilla with the identified video file for investigations. As DK windows installer include current Exiv2 source code, we can rebuild a DK for windows with last fix from Exiv2. For your problem with GDB under Windows, if command line version won't to start digiKam (even if it work on my VM with Windows 7), you need to open a console and go to the directory where gdb and digikam excutable are installed (it's the same dir). After that it's simple. Look the generic page for details : http://stackoverflow.com/questions/4671900/how-do-i-use-the-mingw-gdb-debugger-to-debug-a-c-program-in-windows Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376832] New: Plasmashell Crashed
https://bugs.kde.org/show_bug.cgi?id=376832 Bug ID: 376832 Summary: Plasmashell Crashed Product: plasmashell Version: 5.9.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kananichandr...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.4.48-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I clicked on Default button from Desktop and the plasmashell crashed The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa040714800 (LWP 4647))] Thread 8 (Thread 0x7f9f74540700 (LWP 10405)): #0 0x7fa039de86b4 in clock_gettime () at /usr/lib/libc.so.6 #1 0x7fa03a6f5201 in () at /usr/lib/libQt5Core.so.5 #2 0x7fa03a6f39c9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #3 0x7fa03a6f59c5 in () at /usr/lib/libQt5Core.so.5 #4 0x7fa034bf0179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #5 0x7fa034bf0724 in () at /usr/lib/libglib-2.0.so.0 #6 0x7fa034bf089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #7 0x7fa03a6f606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7fa03a69f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #9 0x7fa03a4c1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #10 0x7f9f76e120a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #11 0x7fa03a4c66d8 in () at /usr/lib/libQt5Core.so.5 #12 0x7fa039391454 in start_thread () at /usr/lib/libpthread.so.0 #13 0x7fa039ddb7df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f9f8824f700 (LWP 8740)): #0 0x7fa039dce4ed in read () at /usr/lib/libc.so.6 #1 0x7fa034c34a10 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa034bf0235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fa034bf0724 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fa034bf089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fa03a6f606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa03a69f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fa03a4c1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fa03e1aefd6 in () at /usr/lib/libQt5Quick.so.5 #9 0x7fa03a4c66d8 in () at /usr/lib/libQt5Core.so.5 #10 0x7fa039391454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fa039ddb7df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fa012a54700 (LWP 8049)): #0 0x7fa03939710f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa03fea3234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fa03fea3279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa039391454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa039ddb7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fa0208c3700 (LWP 8003)): #0 0x7fa034c35db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fa034bf076b in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa034bf089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa03a6f606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa03a69f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa03a4c1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa03d5fb025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fa03a4c66d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fa039391454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa039ddb7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa022323700 (LWP 6099)): #0 0x7fa03a4bdc75 in QMutex::unlock() () at /usr/lib/libQt5Core.so.5 #1 0x7fa03a6f57f1 in () at /usr/lib/libQt5Core.so.5 #2 0x7fa034befc89 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fa034bf06ab in () at /usr/lib/libglib-2.0.so.0 #4 0x7fa034bf089c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fa03a6f606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa03a69f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fa03a4c1a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fa03d5fb025 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fa03a4c66d8 in () at /usr/lib/libQt5Core.so.5 #10 0x7fa039391454 in start_thread () at /usr/lib/libp
[plasmashell] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 --- Comment #5 from manciul...@yahoo.com --- I have worked around this issue by switching to the modesetting driver instead of Intel's driver. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 376831] New: Chat Window do not open correctly
https://bugs.kde.org/show_bug.cgi?id=376831 Bug ID: 376831 Summary: Chat Window do not open correctly Product: telepathy Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: text-ui Assignee: kde-telepathy-b...@kde.org Reporter: m...@phill93.de Target Milestone: Future Created attachment 104180 --> https://bugs.kde.org/attachment.cgi?id=104180&action=edit Logfile KDE-Telepathy Version: 15.12.3 Hi when i open a new Chat Window the Window is empty, only the Menu Bar exists and dbus reports an error. But if i leave this open and retry to open a chat window, the first window gets the chat ui. See attached logfile -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376815] Restore from Trash works incorrectly
https://bugs.kde.org/show_bug.cgi?id=376815 Maik Qualmann changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Version Fixed In|5.5.0 | CC||metzping...@gmail.com Ever confirmed|0 |1 Latest Commit|https://commits.kde.org/dig | |ikam/f528f24b54894b271a4bee | |44a850b1ac46c10cc9 | -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 376795] No login after locked the screen
https://bugs.kde.org/show_bug.cgi?id=376795 --- Comment #4 from Patrik Gustafsson --- Yes, that works to unlock the screen. Br Patrik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376827] task bar highlight for progress bar shows up on all windows from same app
https://bugs.kde.org/show_bug.cgi?id=376827 Aranjedeath changed: What|Removed |Added Component|Panel |Task Manager CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376830] smb share in dolphin is very broken
https://bugs.kde.org/show_bug.cgi?id=376830 Bronson changed: What|Removed |Added Summary|no share option in dolphin |smb share in dolphin is ||very broken -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376830] no share option in dolphin
https://bugs.kde.org/show_bug.cgi?id=376830 --- Comment #1 from Bronson --- ok i found i need to install: kdenetwork as well as samba a few issues with the sharing under kde via dolphin: - can create a share only after changing permissions > others > can view & modify content - then the share doesn't actually work across the network - the settings in the share tab are about 9 attempts out of 10 not saved Overall its a very broken mess at the moment. Would love to see this better supported. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376830] New: no share option in dolphin
https://bugs.kde.org/show_bug.cgi?id=376830 Bug ID: 376830 Summary: no share option in dolphin Product: dolphin Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bronsonmath...@gmail.com Target Milestone: --- Under kde neon. dolphin 16.12.2. I expect when i right click > properties for there to be a sharing tab. But its not there on any of my machines running kde neon. I have samba installed. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 376829] New: Crash on startup
https://bugs.kde.org/show_bug.cgi?id=376829 Bug ID: 376829 Summary: Crash on startup Product: kamoso Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: aleix...@gmail.com Reporter: vishal...@gmail.com Target Milestone: --- Running neon dev unstable edition (git master) and running kamoso from commandline (I have kamoso-dbgsym installed too) results in the following output: Playing device changed "/dev/video0" Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") new gamma 105 new gamma 106 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Slider.qml:204:5: QML RangeModel: Binding loop detected for property "value" New saturation 100 New contrast 100 terminate called after throwing an instance of 'QGlib::Error' what(): no property "video-direction" in element "videoflip0" Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 376829] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=376829 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 365777] add-on installer will not load
https://bugs.kde.org/show_bug.cgi?id=365777 Prajith changed: What|Removed |Added CC||prajithpalakk...@gmail.com --- Comment #3 from Prajith --- This is happening also on Mint 17.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375524] Ambiguous Shortcut - Ctrl+W
https://bugs.kde.org/show_bug.cgi?id=375524 --- Comment #2 from Dale --- Many shortcut keys fail to work in "photoshop emulation" mode. In default mode it is fine. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376661] When importing ~200,000 video files Digikam crashes in about 2-5 seconds of starting.
https://bugs.kde.org/show_bug.cgi?id=376661 --- Comment #10 from Poz --- Spent some more time trying to figure out how to provide more data. while running the debugger I also found this line: [11624] digikam.metaengine: Exiv2 ( 3 ) : Xmp.video.Metadata dataLength was found to be larger than 5000 entries considered invalid; not read. If there is anything else I can do to help debug this, let me know! Thank you. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376692] Search function fails to find phrases split over two lines
https://bugs.kde.org/show_bug.cgi?id=376692 --- Comment #2 from Tom Colley --- Created attachment 104179 --> https://bugs.kde.org/attachment.cgi?id=104179&action=edit The example text formatted as a PDF file. I've attached an example file/PDF, using the text previously given for example. The PDF contains this text: I love the United States. My friend said she loves the United States too but wouldn't want to live there. I live in the Unit- ed States. I revise my diagnosis. When searching for "United States", Okular will find the FIRST and THIRD instances of the phrase, but NOT the SECOND instance. The second instance involves two words in the same paragraph split only by a line break. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] Kde "Discover" crashing
https://bugs.kde.org/show_bug.cgi?id=375913 Christoph Feck changed: What|Removed |Added CC||ad...@rcstar.net --- Comment #3 from Christoph Feck --- *** Bug 375463 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375463] Plasma Discover crashed at launch
https://bugs.kde.org/show_bug.cgi?id=375463 --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 375913 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] Kde "Discover" crashing
https://bugs.kde.org/show_bug.cgi?id=375913 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- Please ask in a forum of your distribution how to fix the installation of the OpenGL drivers. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 376828] New: Krunner Crash (Opensuse Leap 42.2) Plasma 5.8.3
https://bugs.kde.org/show_bug.cgi?id=376828 Bug ID: 376828 Summary: Krunner Crash (Opensuse Leap 42.2) Plasma 5.8.3 Product: krunner Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: dev.dorr...@gmail.com Target Milestone: --- Application: krunner (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I was opening alt + f2, when typing what i was looking the app crash. The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff5be9d68c0 (LWP 2044))] Thread 12 (Thread 0x7ff567fff700 (LWP 7100)): #0 0x7ff5b7e260af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff5ba8de65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff598dd542f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7ff598dd8dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7ff598dd345b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7ff598dd6a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7ff5ba8dd9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff5b7e21734 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff5ba1f1d3d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7ff56700 (LWP 7099)): #0 0x7ff5b7e260af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff5ba8de65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff598dd542f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7ff598dd8dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7ff598dd345b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7ff598dd6a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7ff5ba8dd9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff5b7e21734 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff5ba1f1d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7ff584d7c700 (LWP 7098)): #0 0x7ff5b7e260af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff5ba8de65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff598dd542f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7ff598dd8dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7ff598dd345b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7ff598dd6a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7ff5ba8dd9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff5b7e21734 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff5ba1f1d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff58557d700 (LWP 7097)): #0 0x7ff5b7e260af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff5ba8de65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff598dd542f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7ff598dd8dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7ff598dd345b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7ff598dd8e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7ff598dd345b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7ff598dd6a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7ff5ba8dd9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff5b7e21734 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff5ba1f1d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff585d7e700 (LWP 7096)): #0 0x7ff5b7e260af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff5ba8de65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x00
[kontact] [Bug 376584] Action menu missing in addressbook
https://bugs.kde.org/show_bug.cgi?id=376584 --- Comment #4 from Knut Hildebrandt --- They are back. I had to edit ~/.config/kontactrc by hand and deleted in various sections the entry MenuBar=Disabled There was no way to enable the menu bars directly through the GUI. Thus I would call this rather a workaround than a solution. And anyhow there still is the problem that changing the Global Menu setting does not bring the menus back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376827] task bar highlight for progress bar shows up on all windows from same app
https://bugs.kde.org/show_bug.cgi?id=376827 --- Comment #1 from kishor...@gmail.com --- Component should be 'Task Manager'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376827] task bar highlight for progress bar shows up on all windows from same app
https://bugs.kde.org/show_bug.cgi?id=376827 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] Kde "Discover" crashing
https://bugs.kde.org/show_bug.cgi?id=375913 --- Comment #1 from Daniil Vasin --- Created attachment 104178 --> https://bugs.kde.org/attachment.cgi?id=104178&action=edit New crash information added by DrKonqi plasma-discover (5.9.2) using Qt 5.7.1 - What I was doing when the application crashed: Opening a deb package or to install updates from the updates icon in System Tray -- Backtrace (Reduced): #6 0x7efec0935428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7efec093702a in __GI_abort () at abort.c:89 #8 0x7efec13e9811 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7efec3dab0e3 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #12 0x7efec1fa4735 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375913] Kde "Discover" crashing
https://bugs.kde.org/show_bug.cgi?id=375913 Daniil Vasin changed: What|Removed |Added CC||danikva...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376404] KMail crashed after closing the program
https://bugs.kde.org/show_bug.cgi?id=376404 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in the fglrx OpenGL drivers. Please report this issue directly to fglrx developers. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376747] Kmail crashes on viewing attachement
https://bugs.kde.org/show_bug.cgi?id=376747 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Crash is in the nouveau OpenGL drivers. Please report this issue directly to nouveau developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372754] ksmserver-logout-greeter segfault with nvidia 375.10
https://bugs.kde.org/show_bug.cgi?id=372754 li...@alaya.net changed: What|Removed |Added CC||li...@alaya.net --- Comment #2 from li...@alaya.net --- I am seeing this to with nvidia-378 driver on Ubuntu 16.10. Not sure if it only occurs after updating nvidia driver or more frequently. "We are sorry, ksmserver-logout-greeter closed unexpectedly. You cannot report this error, because ksmserver-logout-greeter does not provide... " -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Already reported, and I am not going to search it again. Please update your software, we already released KMail 5.3 and KMail 5.4. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376763] crash
https://bugs.kde.org/show_bug.cgi?id=376763 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in the NVIDIA OpenGL drivers. Please report this issue directly to NVIDIA developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376827] New: task bar highlight for progress bar shows up on all windows from same app
https://bugs.kde.org/show_bug.cgi?id=376827 Bug ID: 376827 Summary: task bar highlight for progress bar shows up on all windows from same app Product: plasmashell Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: orangewi...@gmail.com Target Milestone: 1.0 Hi! I'm not sure if it's intended behavior, but it seems weird to me so I'll report as a bug: On the task bar (k button to left, system tray to right) where programs sit, when for example an app has a download happening, a file transfer progresses in Dolphin, things like that where the bar for the app lights up as a horizontal progress indicator for the event... Why does it light up as a progress bar all windows for that application, instead of just the one registering the progress? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376827] task bar highlight for progress bar shows up on all windows from same app
https://bugs.kde.org/show_bug.cgi?id=376827 Aranjedeath changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 240487] Color settings for overdue todo is not honored
https://bugs.kde.org/show_bug.cgi?id=240487 Christoph Feck changed: What|Removed |Added Version|unspecified |5.4.1 Resolution|UNMAINTAINED|--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376420] kmail crash while starting
https://bugs.kde.org/show_bug.cgi?id=376420 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 376396 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376396] Kmail crashes when starting it
https://bugs.kde.org/show_bug.cgi?id=376396 Christoph Feck changed: What|Removed |Added CC||th...@gmx.de --- Comment #2 from Christoph Feck --- *** Bug 376420 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376584] Action menu missing in addressbook
https://bugs.kde.org/show_bug.cgi?id=376584 Knut Hildebrandt changed: What|Removed |Added CC||knut.hildebra...@gmx.de --- Comment #3 from Knut Hildebrandt --- The same here. And it's not only KAddressbook. All other applications like Akregator, KMail, KOrganizer do not show menus anymore when used in Kontact. Started separately they have menus. This happened after update to Plasma 5.9. When I tried out Global Menus and switched to "Title Bar Button" menus disappeared but no button ever appeared in title bar. But it even came worse, the menus did not reappear in Kontact after switching back to the original setting. I'm using Chakra Linux with Plasma 5.9.2, Applications 16.12.2 and Framworks 5.31.0. Knut -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376254] Taskbar/transparency glitches with SDL2 programs running
https://bugs.kde.org/show_bug.cgi?id=376254 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment #4. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 376228] git fails with "Unable to extract keyFile from phrase"
https://bugs.kde.org/show_bug.cgi?id=376228 Christoph Feck changed: What|Removed |Added CC||kurt_seeba...@yahoo.de --- Comment #5 from Christoph Feck --- *** Bug 376775 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 376775] ksshaskpass fails to get password for "git pull" to bitbucket repository
https://bugs.kde.org/show_bug.cgi?id=376775 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 376228 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 376630] Bold font rendering is broken after changing font via kcm_fonts
https://bugs.kde.org/show_bug.cgi?id=376630 --- Comment #4 from Pulfer --- (In reply to Pulfer from comment #2) > Maybe it makes sense to drop only some style names from QFont save string. > Like Regular, Bold and Italic. Just because they are already covered by > numeric values. On the other hand, fonts like Arial save localized style name ("Обычный" instead of "Regular"). And switching to Medium style (see #348066) for Ubuntu font likely will break bold font rendering anyway in many applications. So either font style should be ignored or all Qt/KDE applications should be fixed handle it properly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 376771] KPatience
https://bugs.kde.org/show_bug.cgi?id=376771 Christoph Feck changed: What|Removed |Added CC||kdelibs-b...@kde.org Assignee|co...@kde.org |mp...@kde.org Component|general |general Version|3.6 |5.29.0 Product|kpat|frameworks-kcoreaddons -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349088] Down arrow (and other arrows) characters display wrong width
https://bugs.kde.org/show_bug.cgi?id=349088 --- Comment #9 from Christoph Feck --- Konsole uses QPainter::drawText() for the complete line, which handles the pixel advances the fonts provide. The only way I see to fix this is to call QPainter::drawText() for each cell character individually, so that the characters are always aligned to grid, regardless how wide they are in the fallback fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 261649] Allow to assign windows to Activities in taskbar similar to the window menu
https://bugs.kde.org/show_bug.cgi?id=261649 --- Comment #13 from achat1...@free.fr --- New ticket here https://bugs.kde.org/show_bug.cgi?id=376826 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376826] New: assign windows to Activities in task manager unriable
https://bugs.kde.org/show_bug.cgi?id=376826 Bug ID: 376826 Summary: assign windows to Activities in task manager unriable Product: plasmashell Version: 5.9.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: achat1...@free.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Hello, Very glad to see that feature has been added, however it is not as reliable at as it is from the window menu. When trying move move windows to a different activity from task manager, it only works sometimes, whereas it always works from the window menu. Most of the time if I use the activity manager to switch a window to a different activity (say I'm on activity 1 and I want to switch one window to activity 2), nothing happens and when I go back again to the activity menu from task manager nothing has changed (activity 2 is not ticked). Sometimes it does work though but I couldn't establish a pattern of when it does/doesn't work to provide more details. This bug was present in Plasma 5.8.x and still present in 5.9.0. Sorry I should have reported it before. Best Gauthier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 261649] Allow to assign windows to Activities in taskbar similar to the window menu
https://bugs.kde.org/show_bug.cgi?id=261649 --- Comment #12 from achat1...@free.fr --- Ok will do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375924] Cannot rearrange pinned applications
https://bugs.kde.org/show_bug.cgi?id=375924 --- Comment #10 from Francisco Cribari --- Antergos + KDE Plasma 5.9.2 and Manjaro + KDE Plasma 5.9.2. The bug persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375924] Cannot rearrange pinned applications
https://bugs.kde.org/show_bug.cgi?id=375924 Tyler Brown changed: What|Removed |Added CC||ty...@condoulo.com --- Comment #9 from Tyler Brown --- I'm on OpenSUSE Tumbleweed with Plasma 5.9.2 and I am still experiencing this bug with the icons only task manager. It is frustrating that I cannot arrange my pinned icons the way I want. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 376671] Folder select dialog doesn't show start folder
https://bugs.kde.org/show_bug.cgi?id=376671 --- Comment #1 from Christoph Feck --- Cannot reproduce with kdialog/master and kio/master. The specified folder is displayed. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 376751] Filepicker causing Firefox crash
https://bugs.kde.org/show_bug.cgi?id=376751 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Christoph Feck --- We need the backtrace of the crash to decide if this is caused by KDE components. Since Firefox has no DrKonqi integration, you probably have to use 'gdb' to get the backtrace. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 340399] Allow setting output format for --getcolor
https://bugs.kde.org/show_bug.cgi?id=340399 --- Comment #4 from Christoph Feck --- Please read comment #2. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 344237] Export geo: URI
https://bugs.kde.org/show_bug.cgi?id=344237 dllud changed: What|Removed |Added CC||dl...@riseup.net --- Comment #19 from dllud --- Any plans to add this feature anytime soon? It would be really handy to share locations with friends. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 376662] kstart5: Unknown option 'windowclass'.
https://bugs.kde.org/show_bug.cgi?id=376662 --- Comment #5 from Christoph Feck --- Markus, if you can provide the information requested in comment #4, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 376812] Kdenlive crashes when play a colated video in preview
https://bugs.kde.org/show_bug.cgi?id=376812 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- It is the same crash as in bug 376810. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376810] Kdenlive crash when playin 2 merged clips
https://bugs.kde.org/show_bug.cgi?id=376810 Christoph Feck changed: What|Removed |Added Version|unspecified |16.12.2 Product|kde |kdenlive Assignee|unassigned-b...@kde.org |j...@kdenlive.org Component|general |Video Display & Export -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376792] chrashed
https://bugs.kde.org/show_bug.cgi?id=376792 Christoph Feck changed: What|Removed |Added Version|unspecified |5.7.2 Product|kde |Discover Assignee|unassigned-b...@kde.org |aleix...@kde.org Component|general |discover -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 376678] Fonts system settings crash when apply is clicked
https://bugs.kde.org/show_bug.cgi?id=376678 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 --- Comment #9 from Wolfgang Scheffner --- Gilles, I know that Nicofo is absolutely right blamimg this tool for not being intuitive (because it took me quite some time getting into it) and his suggestions would be a start at least. For sure there would be more improvements if one would take the time to think about it. So what are we going to do with this issue? Leaving this bug open and change it to wishlist or open a new one as wishlist? Or something else? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"
https://bugs.kde.org/show_bug.cgi?id=37 Mav changed: What|Removed |Added CC||elenskiy.i...@gmail.com --- Comment #13 from Mav --- I'm an Arch user and had this one since an update too. A search inside .config turned out lines like: "Forward=Alt+Right; Forward; Alt+Right; Forward" inside "~/.config/kdeglobals". The duplication seemed weird, removing kdeglobals and loging out and back in fixed the issue (of course the removed settings like the desktop theme needed to be configured afterwards). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376825] New: Tag displays do not display correctly after new database is selected
https://bugs.kde.org/show_bug.cgi?id=376825 Bug ID: 376825 Summary: Tag displays do not display correctly after new database is selected Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- Two different sequences cause the tags browser pane and the tags edit pane to not display existing tags correctly. First sequence -- Launch digiKam with an existing database. In Settings>Configure digiKam>Database select a different database which already exists. When prompted, choose to "Use Existing File". Tags browser pane and Tags edit pane are missing some tags which exist in the 2nd database. Quit digiKam and re-launch. Tags now appear correctly in both panes. Second sequence --- Launch digiKam with an existing database. In Settings>Configure digiKam>Database select a location for a new, non-existing database. When prompted, choose to "Create New Database". Add a collection which contains some photos. Select a photo in the thumbnails view. Create a new tag in the tags edit pane. Tag is not displayed in the edit pane or in the tags browser pane. (However, if you try to create the tag again, you will get an error that the "tag already exists" even though it is not displayed) Quit and re-launch digiKam and new tag appears. --- Note that this problem does not occur consistently for all databases and photos. However, when it does occur, it is completely repeatable. I have a database with 200 tags and it consistently displays 197 tags after I switch databases. Quit and relaunch will correctly display all 200 tags. I have not been able to determine a rule for which tags are not displayed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375149] Kmail deletes emails from folder after switching to folder
https://bugs.kde.org/show_bug.cgi?id=375149 tick...@tsiboboka.de changed: What|Removed |Added CC||tick...@tsiboboka.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376633] Pager moves windows without user request.
https://bugs.kde.org/show_bug.cgi?id=376633 --- Comment #8 from Mateusz --- I added dragging = false to my main.qml and it works. Thank you. I will let you know if I find anything suspicious about Pager;) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376824] New: Safely Remove (eject) USB media doesn't work
https://bugs.kde.org/show_bug.cgi?id=376824 Bug ID: 376824 Summary: Safely Remove (eject) USB media doesn't work Product: krusader Version: 2.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: ices...@inbox.ru Target Milestone: --- The "Safely Remove" command is available from the drop down menu which opens when you click on the icon on the very left side of the location bar and only when you're actually in the file tree of media device. When you try to click the option to eject the device it's reported to be in use by another application and can not be safely removed. Also would be cool to have a shortcut for that command to eject a media without using mouse. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376815] Restore from Trash works incorrectly
https://bugs.kde.org/show_bug.cgi?id=376815 Maik Qualmann changed: What|Removed |Added Version Fixed In||5.5.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/f528f24b54894b271a4bee ||44a850b1ac46c10cc9 --- Comment #2 from Maik Qualmann --- Git commit f528f24b54894b271a4bee44a850b1ac46c10cc9 by Maik Qualmann. Committed on 22/02/2017 at 22:10. Pushed by mqualmann into branch 'master'. add random string to the trash filename to prevent another thread use the filename already FIXED-IN: 5.5.0 M +2-1NEWS M +10 -0libs/dtrash/dtrash.cpp https://commits.kde.org/digikam/f528f24b54894b271a4bee44a850b1ac46c10cc9 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 176650] KDE doesn’t respect country chosen in user’s locale
https://bugs.kde.org/show_bug.cgi?id=176650 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 336138] Do not use localized date
https://bugs.kde.org/show_bug.cgi?id=336138 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373467] Cannot display date in iso8601 YYYY-MM-DDTHH:MM:SSZ format
https://bugs.kde.org/show_bug.cgi?id=373467 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- 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 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376490] KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale
https://bugs.kde.org/show_bug.cgi?id=376490 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 360643] Dolphin doesn't obey time/date settings in "Formats" (Sys settings)
https://bugs.kde.org/show_bug.cgi?id=360643 Elmo R changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376241] software centre is empty
https://bugs.kde.org/show_bug.cgi?id=376241 --- Comment #18 from Jochen --- https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1577918 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten
https://bugs.kde.org/show_bug.cgi?id=370464 --- Comment #13 from davidblunkett --- I can also confirm that the background reverts to some default KDE pattern on reboot or logout/login every time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten
https://bugs.kde.org/show_bug.cgi?id=370464 --- Comment #12 from davidblunkett --- Created attachment 104177 --> https://bugs.kde.org/attachment.cgi?id=104177&action=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten
https://bugs.kde.org/show_bug.cgi?id=370464 --- Comment #11 from davidblunkett --- cat ~/.config/plasmashellrc [KFileDialog Settings] Recent Files[$e]=file://$HOME/photos/screen/m1.jpg,file://$HOME/photos/screen/m2.jpg Recent URLs[$e]=file://$HOME/photos/,file://$HOME/photos/screen/ [PlasmaRunnerManager] LaunchCounts=1 services_kde4-amarok.desktop,8 services_org.kde.kmail.desktop,3 services_org.kde.korganizer.desktop,1 services_org.kde.konsole.desktop,1 services_org.kde.kcalc.desktop pluginWhiteList=services,places,shell,bookmarks,recentdocuments,locations,baloosearch [PlasmaViews][Panel 1][Horizontal1600] thickness=54 [ScreenConnectors] 0=DVI-I-1 1=DP-0 [Updates] performed=/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/obsolete_kickoffrc.js -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370464] On reboot desktop wallpaper settings are forgotten
https://bugs.kde.org/show_bug.cgi?id=370464 --- Comment #10 from davidblunkett --- xrandr -q Screen 0: minimum 8 x 8, current 3200 x 1200, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.00*+ 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 DP-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.00*+ 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 DP-1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376823] Video preview renderer working on a very limited range of video parameters.
https://bugs.kde.org/show_bug.cgi?id=376823 thealchemist...@gmail.com changed: What|Removed |Added Severity|normal |grave -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376823] New: Video preview renderer working on a very limited range of video parameters.
https://bugs.kde.org/show_bug.cgi?id=376823 Bug ID: 376823 Summary: Video preview renderer working on a very limited range of video parameters. Product: kdenlive Version: 16.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: thealchemist...@gmail.com Target Milestone: --- Problems that affect productivity on kdenlive due to preview renderer working on a limited range of video profiles, error output: [dnxhd @ 0x7ff86400c1e0] video parameters incompatible with DNxHD. Valid DNxHD profiles: [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 6/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 3/1001 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1 [dnxhd @ 0x7ff86400c1e0] Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate
[kwin] [Bug 376813] Does not render non-BMP characters in window titles
https://bugs.kde.org/show_bug.cgi?id=376813 Martin Gräßlin changed: What|Removed |Added Flags||Wayland-, X11+ --- Comment #3 from Martin Gräßlin --- For X11 windows I can confirm. For further investigation xprop output: _NET_WM_USER_TIME(CARDINAL) = 5889445 _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE _KDE_NET_WM_FRAME_STRUT(CARDINAL) = 4, 4, 29, 4 _NET_FRAME_EXTENTS(CARDINAL) = 4, 4, 29, 4 _NET_WM_DESKTOP(CARDINAL) = 0 _KDE_NET_WM_ACTIVITIES(STRING) = "24635a97-5872-486c-a356-f3951f014844" WM_STATE(WM_STATE): window state: Normal icon window: 0x0 _NET_WM_STATE(ATOM) = WM_WINDOW_ROLE(STRING) = "MainWindow#1" _KDE_NET_WM_APPMENU_OBJECT_PATH(STRING) = "/MenuBar/1" _KDE_NET_WM_APPMENU_SERVICE_NAME(STRING) = ":1.57" _NET_WM_ICON_NAME(UTF8_STRING) = _KDE_NET_WM_DESKTOP_FILE(UTF8_STRING) = "org.kde.kwrite" _NET_WM_ICON(CARDINAL) =Icon (16 x 16): ░ ░ ░ ░ ░ ░ ░ ░░ ░░ ░░ ░ ░ ░ Icon (22 x 22): ░ ░ ░ ░ ░ ░ ░ ░ ░ ░ ░░ ░░ ░░ ░░ ░░ ░ ░ ░ ░░ Icon (32 x 32): ░ ░ ░ ░ ░ ░░░ ░░ ░ ░ ░ ░ ░ ░░ ░░░ ░ ░ ░ ░ ░ ░ ░░ ░░░ ░ ░░ ░ ░ ░░ ░░░░ ░ ░░ ░░ ░░ ░░ ░░ ░░ Icon (48 x 48): ░ ░░ ░░ ░ ░ ░░ ░░ ░░░ ░░░ ░░ ░░ ░ ░░ ░░ ░░ ░░░ ░░░░░ ░░ ░░░ ░░ ░░ ░░ ░░ ░░ ░ ░░░░ ░░ ░░ ░░ ░░░ ░░░░░ ░░ ░░░░ ░░░░ ░░ ░░ ░░░░░ ░░░░ ░░ ░░░ ░░░░ ░░░░ ░░ ░░ ░░░░ ░░ ░░░ ░░░░░ ░░░░ ░░
[kwin] [Bug 376813] Does not render non-BMP characters in window titles
https://bugs.kde.org/show_bug.cgi?id=376813 --- Comment #2 from Martin Gräßlin --- Created attachment 104176 --> https://bugs.kde.org/attachment.cgi?id=104176&action=edit Works fine on Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #5 from Martin Gräßlin --- > some suggestion on how to get more debug messages? Unfortunately not. We have had the NVIDIA driver also break in the past for Quadro (only Quadro) cards in the self test and we didn't find any way to properly debug this. A few ideas I have is to experiment with various settings. E.g. switch between OpenGL 2 and 3 in the compositor settings. Try using OpenGL ES. Switch between EGL and GLX. For the last things we only have env variables. https://community.kde.org/KWin/Environment_Variables -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #4 from Martin Gräßlin --- > however I got this error message by setting KWIN_GL_DEBUG 1 unrelated, that's just a bug in the shader generator. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373201] Message List Threading Intermittently Breaks
https://bugs.kde.org/show_bug.cgi?id=373201 --- Comment #1 from Garry Williams --- It's getting worse. Now there's no way that I see to restore proper threading. Later E-mail messages that are part of a prior thread are not sorted properly. This looks like it's permanent -- no way to get the message list window to sort threaded any more. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 --- Comment #8 from Nicofo --- Hello Wolfgang, thanks for investigating this. I agree with your observations. It is indeed necessary to first select an area (by rectangle for instance) and only then it is possible to select pictures inside the rectangle selection. For me, knowing that, the bug could be closed, but I would like to add these comments: 1) the fact you need first to use a 'search by area' tool is not intuitive. I think some easy cosmetic adaptations could be made, like: - Move the icons "Search by area" above the other icons could already help because it is the first action to do. - add information that "Select images" button cannot be used if no rectangle selection is made. Example: by modifying the tooltip - OR - disabling that button if no selection made - OR - adding a message (in the notification toolbar) - OR - ... 2) the rectangle selection could (should ?) be changed: as you mentioned, pressing and holding doesn't work: you need to click to initiate the rectangle and re-click elsewhere to finish the rectangle. 3) (same comments as yours about the mouse pointer) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 Nicofo changed: What|Removed |Added Version|5.3.0 |5.5.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376822] New: empty trash or all trash on imap account akonadi doesn't continue
https://bugs.kde.org/show_bug.cgi?id=376822 Bug ID: 376822 Summary: empty trash or all trash on imap account akonadi doesn't continue Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: akonadiserver (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: select menu empty all trash on imap mail account. Several hours later nothing changed on the account. close kmail & korganizer. do a akonadictl stop crash occur at that time from .xsession-error log org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_newmailnotifier_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_archivemail_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_archivemail_agent' crashed. No restart! org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_davgroupware_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_akonotes_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_sendlater_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_notes_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_ical_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_maildispatcher_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_birthdays_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_davgroupware_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_followupreminder_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_mailfilter_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_migration_agent' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_maildir_resource' exited normally... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' exited normally... KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1502/kdeinit5__0 QSocketNotifier: Invalid socket 60 and type 'Read', disabling... QSocketNotifier: Invalid socket 195 and type 'Read', disabling... QSocketNotifier: Invalid socket 27 and type 'Read', disabling... QSocketNotifier: Invalid socket 196 and type 'Read', disabling... QSocketNotifier: Invalid socket 200 and type 'Read', disabling... QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 143 and type 'Read', disabling... QSocketNotifier: Invalid socket 123 and type 'Read', disabling... QSocketNotifier: Invalid socket 69 and type 'Read', disabling... QSocketNotifier: Invalid socket 189 and type 'Read', disabling... QSocketNotifier: Invalid socket 187 and type 'Read', disabling... terminate called without an active exception Unable to start Dr. Konqi Re-raising signal for core dump handling. org.kde.pim.akonadicontrol: ProcessControl: Application "akonadiserver" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application 'akonadiserver' crashed. No restart! The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 [Current thread is 1 (Thread 0x7f16d74728c0 (LWP 25721))] Thread 19 (Thread 0x7f1672ffd700 (LWP 24884)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f16d5afd2b6 in QWaitConditionPrivate::wait_relative
[plasmashell] [Bug 376821] New: On Wayland, menu shows up in wrong place when menubar style is set to "title bar button"
https://bugs.kde.org/show_bug.cgi?id=376821 Bug ID: 376821 Summary: On Wayland, menu shows up in wrong place when menubar style is set to "title bar button" Product: plasmashell Version: 5.9.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: nortex...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Running a wayland session, I have the menubar style set to "title bar button", and when I click on the button, the menu shows up somewhere far away from the button on my 1080p 15.6" monitor. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 326522] allow to disable automatic search while typing in okulars search field
https://bugs.kde.org/show_bug.cgi?id=326522 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376820] Make mime type settings GUI more consistent
https://bugs.kde.org/show_bug.cgi?id=376820 --- Comment #2 from Jan Wolter --- Created attachment 104175 --> https://bugs.kde.org/attachment.cgi?id=104175&action=edit patch -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 Aetf <7437...@gmail.com> changed: What|Removed |Added Status|VERIFIED|CLOSED --- Comment #27 from Aetf <7437...@gmail.com> --- Thank you for reporting! I've also added a link pointing back to this bug in their bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376820] Make mime type settings GUI more consistent
https://bugs.kde.org/show_bug.cgi?id=376820 --- Comment #1 from Jan Wolter --- Created attachment 104174 --> https://bugs.kde.org/attachment.cgi?id=104174&action=edit mime type gui AFTER -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376820] New: Make mime type settings GUI more consistent
https://bugs.kde.org/show_bug.cgi?id=376820 Bug ID: 376820 Summary: Make mime type settings GUI more consistent Product: digikam Version: 5.5.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: onl...@wolter.re Target Milestone: --- Created attachment 104173 --> https://bugs.kde.org/attachment.cgi?id=104173&action=edit mime type gui BEFORE In mime type settings GUI there are explicit revert buttons whereas in other settings setClearButtonEnabled from class QLineEdit are used. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376819] New: Message List doesn't stay scrolled to top
https://bugs.kde.org/show_bug.cgi?id=376819 Bug ID: 376819 Summary: Message List doesn't stay scrolled to top Product: kmail2 Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: chrismcc...@gmail.com Target Milestone: --- Everytime I change message folders( or open up Kmail ), my message list scroll bar doesn't stay at the top( most recent messages first ). Rather, it always starts scrolled down and I have to scroll back to the top every single time. Kubuntu 16.10 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 343796] Most of operations are disabled when opening files from remote url.
https://bugs.kde.org/show_bug.cgi?id=343796 --- Comment #12 from Vadim A. Misbakh-Soloviov (mva) --- And, btw, your patch seems to work in conditions mentioned by you :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376818] New: Unread message - single click pops up new window.
https://bugs.kde.org/show_bug.cgi?id=376818 Bug ID: 376818 Summary: Unread message - single click pops up new window. Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: chrismcc...@gmail.com Target Milestone: --- Every time I single click on an unread message in the message list( using Gmail IMAP ), it pops up a new window for me to read the message rather than display the message in the preview pane. If I single click on an already read message, it works as expected. In other words, selecting unread messages with a single click in the message list behaves like double clicking. #annoying Kubuntu 16.10 Using 5.2.3 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365723] Disconnected pulseaudio outputs not hidden in drop-down list
https://bugs.kde.org/show_bug.cgi?id=365723 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376817] New: some applications are pinned when started
https://bugs.kde.org/show_bug.cgi?id=376817 Bug ID: 376817 Summary: some applications are pinned when started Product: plasmashell Version: 5.9.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: os-...@jacraig.com CC: plasma-b...@kde.org Target Milestone: 1.0 Since the 5.9.2 Plasma update landed the other day, many applications are starting up as pinned to the task manager. It is strangely arbitrary; I haven't yet been able to pinpoint what makes them start as pinned or not. For example, KRDC, Firefox and Thunderbird have all started as pinned but it is not every time I start them, and it is not every application I start. For example, I don't believe Konsole or Dolphin have started pinned (yet). It appears that it will only happen the first time I start the particular application after a fresh boot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 --- Comment #4 from David Rosca --- It's not fixed. The problem is that the QMenu's don't receive aboutToHide signals when global menu is enabled (at least with global menu in window titlebars). I didn't look into global menu code, so this may also be bug in Qt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 David Rosca changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 CC||now...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375215] "Cannot Create Embedded Terminal"
https://bugs.kde.org/show_bug.cgi?id=375215 Geo Chura changed: What|Removed |Added CC||n...@sfu.ca --- Comment #5 from Geo Chura --- Hi Alex ... I've installed the version from the Krusader website and it seems to work fine. I see that v2.5 is supposed to come out in Fedora 26 and so I didn't bother to enable Rawhide. I should say, with the embedded Konsole, I really like Krusader ... absolutely the best file manager out there. Thanks for the help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375346] Many tags disappeared from database
https://bugs.kde.org/show_bug.cgi?id=375346 --- Comment #5 from wildcowboy --- (In reply to caulier.gilles from comment #4) > So A mysql server, not Mysql internal. Right ? > > Can you try with a fresh database using sqlite instead, to see if problem is > reproducible ? > > Gilles Caulier Everything seems to work fine after switching to sqlite. I will keep you posted if it pops up again though. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 343796] Most of operations are disabled when opening files from remote url.
https://bugs.kde.org/show_bug.cgi?id=343796 --- Comment #11 from Vadim A. Misbakh-Soloviov (mva) --- > That should work, provided that the remote URL filename has the correct file > type suffix. Unfortunatelly, it is not always the case. Some image hostings always tell ".jpg" filename, while real file (Content-Type) can be png and even gif. And some others like akamai (probably in use by facebook and google) gives the url that ends like directory name (with slash ("/")). -- You are receiving this mail because: You are watching all bug changes.