[plasmashell] [Bug 362836] New: "Short date" option in clock is not short
https://bugs.kde.org/show_bug.cgi?id=362836 Bug ID: 362836 Summary: "Short date" option in clock is not short Product: plasmashell Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pas...@dhermilly.dk CC: bhus...@gmail.com, plasma-b...@kde.org The "short date" option for displaying dates by the clock in the panel is the same lenght as ISO. It would be really nice to have a basics date. For example it writes out the year which is unnecessary for most and it prepends month and day with zeros if below 10. Having an option with a 3-letter month and a date without zeros prepended would be perfect. E.g. "Sep 4" or "15 Jan" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 362837] New: the auto hide function in the panel is no longer working
https://bugs.kde.org/show_bug.cgi?id=362837 Bug ID: 362837 Summary: the auto hide function in the panel is no longer working Product: plasma4 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: containment-panel Assignee: plasma-b...@kde.org Reporter: myl...@ihug.co.nz Since the latest upgrade the panel auto hide does not work Reproducible: Always Steps to Reproduce: 1. panel settings -> Auto Hide 2. 3. Actual Results: Nothing happens Expected Results: Panel should drop from view exposing area panel occupies -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 362838] New: KDE Krash
https://bugs.kde.org/show_bug.cgi?id=362838 Bug ID: 362838 Summary: KDE Krash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nk0...@yahoo.fr Application: plasma-desktop (4.11.16) KDE Platform Version: 4.14.19 Qt Version: 4.8.7 Operating System: Linux 4.6.0-desktop-0.rc6.2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: In the Stopping sequence of the Computer KDE krassh The crash can be reproduced every time. -- Backtrace: Application: Outil de gestion de fenêtres Plasma (plasma-desktop), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f38bb854800 (LWP 2381))] Thread 3 (Thread 0x7f3807998700 (LWP 2389)): #0 0x7f38b8e5d16d in poll () at /lib64/libc.so.6 #1 0x7f38b5f62324 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f38b5f6242c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f38ba523dde in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #4 0x7f38ba4f42d1 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #5 0x7f38ba4f45e5 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #6 0x7f38ba3ed289 in QThread::exec() () at /lib64/libQtCore.so.4 #7 0x7f38ba4d53c3 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4 #8 0x7f38ba3efa6c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #9 0x7f38ba16065d in start_thread () at /lib64/libpthread.so.0 #10 0x7f38b8e68fbd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f388f040700 (LWP 2383)): #0 0x7f38ba165c3f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f38ab5e7cba in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQtScript.so.4 #2 0x7f38ab5e7ce9 in () at /lib64/libQtScript.so.4 #3 0x7f38ba16065d in start_thread () at /lib64/libpthread.so.0 #4 0x7f38b8e68fbd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f38bb854800 (LWP 2381)): [KCrash Handler] #6 0x7f38b8da6828 in raise () at /lib64/libc.so.6 #7 0x7f38b8da7f3a in abort () at /lib64/libc.so.6 #8 0x7f38922cbd02 in apng_probe () at /lib64/libavformat.so.56 #9 0x7f3892680074 in probe_format(AVProbeData*, int*) () at /usr/lib64/strigi/strigiea_ffmpeg.so #10 0x7f3892680340 in FFMPEGEndAnalyzer::analyze(Strigi::AnalysisResult&, Strigi::StreamBase*) () at /usr/lib64/strigi/strigiea_ffmpeg.so #11 0x7f38af936176 in Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&, Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0 #12 0x7f38af91197e in Strigi::AnalysisResult::indexChild(std::__cxx11::basic_string, std::allocator > const&, long, Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0 #13 0x7f38af94ba30 in OdfEndAnalyzer::analyze(Strigi::AnalysisResult&, Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0 #14 0x7f38af936176 in Strigi::StreamAnalyzerPrivate::analyze(Strigi::AnalysisResult&, Strigi::StreamBase*) () at /lib64/libstreamanalyzer.so.0 #15 0x7f38afcc8c88 in KFileMetaInfoPrivate::init(QIODevice&, KUrl const&, long, QFlags) () at /usr/lib64/libkio.so.5 #16 0x7f38afcc904a in KFileMetaInfo::KFileMetaInfo(QString const&, QString const&, QFlags) () at /usr/lib64/libkio.so.5 #17 0x7f38afcb4e7f in KFileItem::metaInfo(bool, int) const () at /usr/lib64/libkio.so.5 #18 0x7f38975d0f6c in ToolTipWidget::metaInfo() const () at /usr/lib64/kde4/plasma_applet_folderview.so #19 0x7f38975d37fb in ToolTipWidget::setContent() () at /usr/lib64/kde4/plasma_applet_folderview.so #20 0x7f38975d3aee in ToolTipWidget::toolTipAboutToShow() () at /usr/lib64/kde4/plasma_applet_folderview.so #21 0x7f38ba4fda81 in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () at /lib64/libQtCore.so.4 #22 0x7f38ba4ffe5e in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at /lib64/libQtCore.so.4 #23 0x7f38adfad94a in Plasma::ToolTipManagerPrivate::showToolTip() () at /usr/lib64/libplasma.so.3 #24 0x7f38adfade09 in Plasma::ToolTipManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.25] () at /usr/lib64/libplasma.so.3 #25 0x7f38ba508b50 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #93 from madc...@atlas.cz --- I cannot confirm that the initial position of the mouse cursor has any effect on the placement of the panel. Just this morning I started my laptop with the external monitor already plugged in. When I logged into Plasma, the cursor was on the laptop's built-in screen but the panel moved *correctly* to the external display. Is there any chance that the X.org drivers could be at fault here somehow? I do remember installing two updates for my Intel GPU and Plasma seems to place the panel correctly since then. Unfortunately I was out of the office when the updates landed in Arch Linux repos so I cannot know for sure if they had any effect... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 321535] Kdevelop freezes on specific c++ code
https://bugs.kde.org/show_bug.cgi?id=321535 Akshay changed: What|Removed |Added CC||ajos...@mail.csuchico.edu --- Comment #2 from Akshay --- Created attachment 98852 --> https://bugs.kde.org/attachment.cgi?id=98852&action=edit bug fixed The bug is solved and it does not reproduce anymore. I guess we can close this bug now. Review the attached file. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 351913] since version 15.08 some file types previews no longer available (pdf for instance)
https://bugs.kde.org/show_bug.cgi?id=351913 --- Comment #26 from alexander --- I can confirm that sudo ln -s /usr/lib/x86_64-linux-gnu/plugins/* /usr/lib/x86_64-linux-gnu/qt5/plugins/ fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 337276] fully-qualified audio notifications no longer play
https://bugs.kde.org/show_bug.cgi?id=337276 --- Comment #17 from Harald Sitter --- Git commit 4832f7d9f2f3bd0fa8ab9b9162bf50e855efc448 by Harald Sitter. Committed on 09/05/2016 at 07:27. Pushed by sitter into branch 'master'. use QUrl::fromUserInput to construct sound url QUrl() would treats it as a parsable uri, but they aren't e.g. # in a uri separates segments in a local file path it simply is a #. This "accidentally" worked in Phonon < 4.9 as Phonon obtained string representations in a way that would bypass internal QUrl checks for fileyness and URI ambiguity. Since 4.9 Phonon expects scheme-less URLs to be local files, but QUrl() would most of the time not do that since it would honestly think the soundfilename is a random (i.e. not necessarily local) uri. To fix this use QUrl::fromUserInput which behaves exactly like what we need to properly resolve relative names, urls, paths, full URIs. This now works with input of the type: - Oxygen-Sys-Special.ogg - /usr/share/sounds/Oxygen-Sys-Special.ogg - file:///usr/share/sounds/Oxygen-Sys-Special.ogg - /usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - file:///usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - http://people.ubuntu.com/~apachelogger/sounds/sounds-3.5/KDE_Glass_Break.ogg (yes, we can have http notifications https://xkcd.com/1172/) REVIEW: 127829 M +13 -8src/knotifyconfigactionswidget.cpp http://commits.kde.org/knotifyconfig/4832f7d9f2f3bd0fa8ab9b9162bf50e855efc448 --- Comment #18 from Harald Sitter --- Git commit 9db06adc8114163f401417064b07772139bc36bc by Harald Sitter. Committed on 09/05/2016 at 07:27. Pushed by sitter into branch 'master'. use QUrl::fromUserInput to construct sound url QUrl() would treats it as a parsable uri, but they aren't e.g. # in a uri separates segments in a local file path it simply is a #. This "accidentally" worked in Phonon < 4.9 as Phonon obtained string representations in a way that would bypass internal QUrl checks for fileyness and URI ambiguity. Since 4.9 Phonon expects scheme-less URLs to be local files, but QUrl() would most of the time not do that since it would honestly think the soundfilename is a random (i.e. not necessarily local) uri. To fix this use QUrl::fromUserInput which behaves exactly like what we need to properly resolve relative names, urls, paths, full URIs. This now works with input of the type: - Oxygen-Sys-Special.ogg - /usr/share/sounds/Oxygen-Sys-Special.ogg - file:///usr/share/sounds/Oxygen-Sys-Special.ogg - /usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - file:///usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - http://people.ubuntu.com/~apachelogger/sounds/sounds-3.5/KDE_Glass_Break.ogg (yes, we can have http notifications https://xkcd.com/1172/) REVIEW: 127830 M +16 -9src/notifybyaudio.cpp http://commits.kde.org/knotifications/9db06adc8114163f401417064b07772139bc36bc -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 337276] fully-qualified audio notifications no longer play
https://bugs.kde.org/show_bug.cgi?id=337276 --- Comment #17 from Harald Sitter --- Git commit 4832f7d9f2f3bd0fa8ab9b9162bf50e855efc448 by Harald Sitter. Committed on 09/05/2016 at 07:27. Pushed by sitter into branch 'master'. use QUrl::fromUserInput to construct sound url QUrl() would treats it as a parsable uri, but they aren't e.g. # in a uri separates segments in a local file path it simply is a #. This "accidentally" worked in Phonon < 4.9 as Phonon obtained string representations in a way that would bypass internal QUrl checks for fileyness and URI ambiguity. Since 4.9 Phonon expects scheme-less URLs to be local files, but QUrl() would most of the time not do that since it would honestly think the soundfilename is a random (i.e. not necessarily local) uri. To fix this use QUrl::fromUserInput which behaves exactly like what we need to properly resolve relative names, urls, paths, full URIs. This now works with input of the type: - Oxygen-Sys-Special.ogg - /usr/share/sounds/Oxygen-Sys-Special.ogg - file:///usr/share/sounds/Oxygen-Sys-Special.ogg - /usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - file:///usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - http://people.ubuntu.com/~apachelogger/sounds/sounds-3.5/KDE_Glass_Break.ogg (yes, we can have http notifications https://xkcd.com/1172/) REVIEW: 127829 M +13 -8src/knotifyconfigactionswidget.cpp http://commits.kde.org/knotifyconfig/4832f7d9f2f3bd0fa8ab9b9162bf50e855efc448 --- Comment #18 from Harald Sitter --- Git commit 9db06adc8114163f401417064b07772139bc36bc by Harald Sitter. Committed on 09/05/2016 at 07:27. Pushed by sitter into branch 'master'. use QUrl::fromUserInput to construct sound url QUrl() would treats it as a parsable uri, but they aren't e.g. # in a uri separates segments in a local file path it simply is a #. This "accidentally" worked in Phonon < 4.9 as Phonon obtained string representations in a way that would bypass internal QUrl checks for fileyness and URI ambiguity. Since 4.9 Phonon expects scheme-less URLs to be local files, but QUrl() would most of the time not do that since it would honestly think the soundfilename is a random (i.e. not necessarily local) uri. To fix this use QUrl::fromUserInput which behaves exactly like what we need to properly resolve relative names, urls, paths, full URIs. This now works with input of the type: - Oxygen-Sys-Special.ogg - /usr/share/sounds/Oxygen-Sys-Special.ogg - file:///usr/share/sounds/Oxygen-Sys-Special.ogg - /usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - file:///usr/share/sounds/#KDE-Im-Cant-#Connect.ogg - http://people.ubuntu.com/~apachelogger/sounds/sounds-3.5/KDE_Glass_Break.ogg (yes, we can have http notifications https://xkcd.com/1172/) REVIEW: 127830 M +16 -9src/notifybyaudio.cpp http://commits.kde.org/knotifications/9db06adc8114163f401417064b07772139bc36bc -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362839] New: Nice option for disabling akonadi on non-PIM computers
https://bugs.kde.org/show_bug.cgi?id=362839 Bug ID: 362839 Summary: Nice option for disabling akonadi on non-PIM computers Product: Akonadi Version: 15.12 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: pas...@dhermilly.dk It would be really nice if it there was a UI where you can disable Akonadi on computers where it's not in use. Because being in use or not, it always seem to start a large mysql process (around 130MB of RAM). In KDE4 there was an module called akonadiserverconfig (or something like that) where if you knew it you could set it to use a non-existing seperate database server. This effectively disabled the process. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362803] Can't change KMail Message List font size with custom font settings.
https://bugs.kde.org/show_bug.cgi?id=362803 --- Comment #3 from l...@llpmail.com --- (In reply to Maurice Batey from comment #2) > P.S. > > I have the same problem with KDE 5.2.0: > -In Mageia-6-sta1 I downgraded to kubutu 15.10 which has KDE 5.4.2 & Kmail version 4:15.08.2-0ubuntu1. It works fine. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362062] Kdevelop crashes when on 4.7.1 when we try to open it with memory leak checking application valgrind
https://bugs.kde.org/show_bug.cgi?id=362062 --- Comment #10 from Akshay --- Memcheck, a memory error detector ==12613== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==12613== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==12613== Command: kdevelop ==12613== ==12604== Conditional jump or move depends on uninitialised value(s) ==12604==at 0x23B2548D: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0xECAE243: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC8A45: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC95F4: g_signal_emit_by_name (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECB5967: g_object_set_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECB603B: g_object_set (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0x68886E5: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12604==by 0x680CFAC: QStyleFactory::create(QString const&) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12604==by 0x67AA704: QApplication::style() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12604==by 0x67AAAEC: QApplicationPrivate::initialize() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12604==by 0x67AAB3E: QApplicationPrivate::construct() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12604==by 0x41BAE3: KDevelopApplication::KDevelopApplication(int&, char**, bool) (in /home/akshayjoshi/kde-5/bin/kdevelop) ==12604== ==12604== Conditional jump or move depends on uninitialised value(s) ==12604==at 0xEF6A1D8: g_utf8_offset_to_pointer (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.2) ==12604==by 0x23B28A94: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B29098: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B293CE: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0xECAE014: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECBFB9B: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC8DFB: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC912E: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0x23CB7F53: gtk_widget_realize (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23CB9267: gtk_widget_set_parent (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B57CD2: gtk_fixed_put (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0xECB1116: g_cclosure_marshal_VOID__OBJECTv (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604== ==12604== Conditional jump or move depends on uninitialised value(s) ==12604==at 0xEF6A205: g_utf8_offset_to_pointer (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.2) ==12604==by 0x23B28A94: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B29098: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B293CE: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0xECAE014: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECBFB9B: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC8DFB: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0xECC912E: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604==by 0x23CB7F53: gtk_widget_realize (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23CB9267: gtk_widget_set_parent (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0x23B57CD2: gtk_fixed_put (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12604==by 0xECB1116: g_cclosure_marshal_VOID__OBJECTv (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12604== ==12613== Conditional jump or move depends on uninitialised value(s) ==12613==at 0x23B2548D: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.28) ==12613==by 0xECAE243: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12613==by 0xECC8A45: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12613==by 0xECC95F4: g_signal_emit_by_name (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12613==by 0xECB5967: g_object_set_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12613==by 0xECB603B: g_object_set (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4600.2) ==12613==by 0x68886E5: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.4.2) ==12613==by 0x680CFAC: QStyleF
[kdevelop] [Bug 362062] Kdevelop crashes when on 4.7.1 when we try to open it with memory leak checking application valgrind
https://bugs.kde.org/show_bug.cgi?id=362062 --- Comment #11 from Akshay --- --12593:0: aspacem 1276: 080dac1000-080dac3fff 12288 --12593:0: aspacem 1277: ANON 080dac4000-080df27fff 4603904 rwx-- --12593:0: aspacem 1278: 080df28000-080df29fff8192 --12593:0: aspacem 1279: ANON 080df2a000-080df61fff 229376 rwx-- --12593:0: aspacem 1280: 080df62000-080df64fff 12288 --12593:0: aspacem 1281: ANON 080df65000-0810984fff 42m rwx-- --12593:0: aspacem 1282: 0810985000-0810987fff 12288 --12593:0: aspacem 1283: ANON 0810988000-0810a47fff 786432 rwx-- --12593:0: aspacem 1284: 0810a48000-0810a48fff4096 --12593:0: aspacem 1285: ANON 0810a49000-08135e8fff 43m rwx-- --12593:0: aspacem 1286: 08135e9000-08135ebfff 12288 --12593:0: aspacem 1287: ANON 08135ec000-08137f 2179072 rwx-- --12593:0: aspacem 1288: 081380-0813800fff4096 --12593:0: aspacem 1289: ANON 0813801000-0818538fff 77m rwx-- --12593:0: aspacem 1290: ANON 0818539000-081853afff8192 - --12593:0: aspacem 1291: ANON 081853b000-081863afff 1048576 rwx-- --12593:0: aspacem 1292: ANON 081863b000-081863efff 16384 - --12593:0: aspacem 1293: ANON 081863f000-081873efff 1048576 rwx-- --12593:0: aspacem 1294: ANON 081873f000-0818740fff8192 - --12593:0: aspacem 1295: ANON 0818741000-0818ef0fff 8060928 rwx-- --12593:0: aspacem 1296: 0818ef1000-0818ef3fff 12288 --12593:0: aspacem 1297: ANON 0818ef4000-0818ff3fff 1048576 rwx-- --12593:0: aspacem 1298: ANON 0818ff4000-0818ff5fff8192 - --12593:0: aspacem 1299: ANON 0818ff6000-08190f5fff 1048576 rwx-- --12593:0: aspacem 1300: ANON 08190f6000-08190f7fff8192 - --12593:0: aspacem 1301: 08190f8000-0819198fff 659456 --12593:0: aspacem 1302: ANON 0819199000-08198d0fff 7569408 rwx-- --12593:0: aspacem 1303: ANON 08198d1000-08198d2fff8192 - --12593:0: aspacem 1304: ANON 08198d3000-08199d2fff 1048576 rwx-- --12593:0: aspacem 1305: ANON 08199d3000-08199d4fff8192 - --12593:0: aspacem 1306: ANON 08199d5000-0819ac5fff 987136 rwx-- --12593:0: aspacem 1307: 0819ac6000-0ffe800fff 32333m --12593:0: aspacem 1308: RSVN 0ffe801000-0ffefc 8187904 - SmUpper --12593:0: aspacem 1309: anon 0ffefd-0fff000fff 200704 rw--- --12593:0: aspacem 1310: 0fff001000-0f 15m --12593:0: aspacem 1311: RSVN 10-7ffd382f7fff 130996g - SmFixed --12593:0: aspacem 1312: ANON 7ffd382f8000-7ffd38318fff 135168 rw--- --12593:0: aspacem 1313: RSVN 7ffd38319000-7ffd3839afff 532480 - SmFixed --12593:0: aspacem 1314: ANON 7ffd3839b000-7ffd3839cfff8192 r --12593:0: aspacem 1315: RSVN 7ffd3839d000-ff5f 16383e - SmFixed --12593:0: aspacem 1316: ANON ff60-ff600fff4096 r-x-- --12593:0: aspacem 1317: RSVN ff601000- 9m - SmFixed --12593:0: aspacem >>> --12593-- core:46,137,344/ 46,137,344 max/curr mmap'd, 0/1 unsplit/split sb unmmap'd, 40,304,872/ 39,556,208 max/curr, 2179578/ 908101712 totalloc-blocks/bytes, 2011233 searches 8 rzB --12593-- dinfo :71,725,056/ 65,409,024 max/curr mmap'd, 25/16 unsplit/split sb unmmap'd, 69,054,864/ 62,017,008 max/curr, 1022499/ 408515760 totalloc-blocks/bytes, 1039219 searches 8 rzB --12593-- client :92,274,688/ 92,274,688 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 54,868,768/ 54,425,600 max/curr, 1251457/ 258195504 totalloc-blocks/bytes, 1324564 searches 24 rzB --12593-- demangle:65,536/ 65,536 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 5,888/1,696 max/curr, 99/ 45616 totalloc-blocks/bytes, 98 searches 8 rzB --12593-- ttaux : 9,732,096/9,072,640 max/curr mmap'd, 42/3 unsplit/split sb unmmap'd, 9,333,008/8,683,808 max/curr, 25872/ 24778624 totalloc-blocks/bytes, 25793 searches 8 rzB --12593-- translate:fast SP updates identified: 452,269 (93.3%) --12593-- translate: generic_known SP updates identified: 25,026 (5.2%) --12593-- translate: generic_unknown SP updates identified: 7,655 (1.6%) --12593-- translate: PX: SPonly 0, UnwRegs 298,152, AllRegs 0, AllRegsAllInsns 0 --12593-- tt/tc: 948,169 tt lookups requiring 8,440,395 probes --12593-- tt/tc: 724,952 fast-cache updates, 11 flushes --12593-- transtab: new298,130 (7,875,837 -> 126,930,792; ratio 16.1) [569 scs] avg tce size 425 --12593-- transtab: dumped 0 (0 -> ??) (sectors recycled 0) --12593-- transtab: discarded 13 (431 -> ??) --12593-- scheduler: 109,672,019 event checks. --12593-- scheduler: 38,943,550 indir transfers, 413,491 misses (1 in 94) --12593-- scheduler: 1,094/2,916,704 major/minor sched events. --12593--sanity: 1094 cheap, 29 expensive checks. --12593--exectx: 196,613 lists, 175,907 contexts (avg 0.89 per list) (avg 10.73 IP per context) --12593--exectx: 2,353,296 searches, 2,328,148 full compares (989 pe
[kdevelop] [Bug 362062] Kdevelop crashes when on 4.7.1 when we try to open it with memory leak checking application valgrind
https://bugs.kde.org/show_bug.cgi?id=362062 Akshay changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362839] Nice option for disabling akonadi on non-PIM computers
https://bugs.kde.org/show_bug.cgi?id=362839 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- Is this configuration not available in the current version of akonadiconsole? - it was in KDE4. menu bar - Server - Configure Server... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Samuel changed: What|Removed |Added CC||sbc_hates_s...@yahoo.com.au --- Comment #94 from Samuel --- Created attachment 98853 --> https://bugs.kde.org/attachment.cgi?id=98853&action=edit Location of Panels after booting system This image illustrates the location of panels on the external display after startup. Note that the external display is on the LEFT of the Laptop screen. Both panels where on the Laptop screen before shutting down. When the side panel is on the Laptop. the More Settings > Visibility Settings are ineffective. THESE PROBLEMS DO NOT OCCUR WHEN THE EXTERNAL DISPLAY IS ON THE RIGHT OF THE LAPTOP SCREEN. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362840] New: Dolphin crashed after failing to copy a directory
https://bugs.kde.org/show_bug.cgi?id=362840 Bug ID: 362840 Summary: Dolphin crashed after failing to copy a directory Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pedron.alexan...@gmail.com Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Dolphin crashed after failing to copy a directory. Error message was "a file was expected, a folder came instead" -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd783a8c8c0 (LWP 4471))] Thread 2 (Thread 0x7fd7771ed700 (LWP 4473)): #0 0x7fd7968ace8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd78d0a131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd78d0a142c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd7916b5a9b in QEventDispatcherGlib::processEvents (this=0x7fd778c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fd79165cdea in QEventLoop::exec (this=this@entry=0x7fd7771ecd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd7914798a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fd79147e84e in QThreadPrivate::start (arg=0x2afe850) at thread/qthread_unix.cpp:331 #7 0x7fd78dc2c6fa in start_thread (arg=0x7fd7771ed700) at pthread_create.c:333 #8 0x7fd7968b8b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd783a8c8c0 (LWP 4471)): [KCrash Handler] #6 QBasicAtomicOps<4>::deref (_q_value=@0x1: ) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_x86.h:219 #7 QBasicAtomicInteger::deref (this=0x1) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:128 #8 QSharedDataPointer::~QSharedDataPointer (this=0x35b0ac0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:80 #9 KFileItem::~KFileItem (this=0x35b0ac0, __in_chrg=) at ../../../src/core/kfileitem.cpp:491 #10 0x7fd7914e1c89 in QHashData::free_helper (this=0x30225d0, node_delete=0x7fd79650b230 ::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:491 #11 0x7fd79650332a in QHash::freeData (this=0x2c885b0, x=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:621 #12 QHash::~QHash (this=0x2c885b0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:342 #13 QSet::~QSet (this=0x2c885b0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qset.h:46 #14 KFileItemModelRolesUpdater::~KFileItemModelRolesUpdater (this=0x2c88590, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/kitemviews/kfileitemmodelrolesupdater.cpp:149 #15 0x7fd796503429 in KFileItemModelRolesUpdater::~KFileItemModelRolesUpdater (this=0x2c88590, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/kitemviews/kfileitemmodelrolesupdater.cpp:152 #16 0x7fd79168c52b in QObjectPrivate::deleteChildren (this=this@entry=0x2c86320) at kernel/qobject.cpp:1946 #17 0x7fd791695da0 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1024 #18 0x7fd7924b99b5 in QGraphicsWidget::~QGraphicsWidget (this=0x2c85f70, __in_chrg=) at graphicsview/qgraphicswidget.cpp:225 #19 0x7fd796548879 in DolphinItemListView::~DolphinItemListView (this=0x2c85f70, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/views/dolphinitemlistview.cpp:50 #20 0x7fd79168c52b in QObjectPrivate::deleteChildren (this=this@entry=0x2c87900) at kernel/qobject.cpp:1946 #21 0x7fd791695da0 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1024 #22 0x7fd796512229 in KItemListController::~KItemListController (this=0x2c87880, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/kitemviews/kitemlistcontroller.cpp:83 #23 0x7fd79650c86b in KItemListContainer::~KItemListContainer (this=0x2c8d2b0, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/kitemviews/kitemlistcontainer.cpp:100 #24 0x7fd79650c899 in KItemListContainer::~KItemListContainer (this=0x2c8d2b0, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/kitemviews/kitemlistcontainer.cpp:102 #25 0x7fd79168c52b in QObjectPrivate::deleteChildren (this=this@entry=0x2c84510) at kernel/qobject.cpp:1946 #26 0x7fd7921a06c8 in QWidget::~QWidget (this=0x2c84450, __in_chrg=) at kernel/qwidget.cpp:1658 #27 0x7fd79654d189 in DolphinView::~DolphinView (this=0x2c84450, __in_chrg=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/views/dolphinview.cpp:203 #28 0x7fd79168c52b in QObjectPrivate::deleteChildren (this=this@entry=0x2f2e280) at kernel/qobject.cpp:
[kdevelop] [Bug 202419] "Declaration not found" reported when accessing typedefed parent class in init list of ctor
https://bugs.kde.org/show_bug.cgi?id=202419 Kevin Funk changed: What|Removed |Added Version Fixed In||5.0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Kevin Funk --- Appears resolved under KDevelop 5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 280720] wrong datatype if a cast is used in Array declaration
https://bugs.kde.org/show_bug.cgi?id=280720 Kevin Funk changed: What|Removed |Added Version Fixed In||5.0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Kevin Funk --- Appears fixed under KDevelop 5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362062] Kdevelop crashes when on 4.7.1 when we try to open it with memory leak checking application valgrind
https://bugs.kde.org/show_bug.cgi?id=362062 --- Comment #12 from Kevin Funk --- ==12593== Valgrind's memory management: out of memory: ==12593==initialiseSector(TC)'s request for 27597024 bytes failed. ==12593== 629,841,920 bytes have already been mmap-ed ANONYMOUS. ==12593== Valgrind cannot continue. Sorry. ^ Are you just running out of memory? -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 362825] Error in { : task 1 failed - "could not find function "trellis.last.object""
https://bugs.kde.org/show_bug.cgi?id=362825
Thomas Friedrichsmeier changed:
What|Removed |Added
CC||thomas.friedrichsmeier@ruhr
||-uni-bochum.de
--- Comment #2 from Thomas Friedrichsmeier
---
Thanks for reporting. I'll try to look into this, soon, but very distracted,
ATM.
Could you add the output of
getAnywhere ("trellis.last.object")
to this report (after the error)?
For the time being, you should be able to work around this by disabling the
plot history feature, either for this call, only (rk.without.plot.history()) or
entirely (Settings->Onscreen Graphics->Screen device history).
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 329089] automatically unlock screen at home
https://bugs.kde.org/show_bug.cgi?id=329089 --- Comment #6 from hb_...@brueningserver.de --- I think we are talking about nuances of the same idea. But Olaf, you are right. It is a slightly a different feature. But I suppose the one who hopefully implements this some day will be aware of the consequences and finds a nice solution. For instance leaving my home with a computer that is not locked, could be a security risk. So, perhaps inhibiting the locking is more dangerous than unlocking by SSID. But having a computer outside my home that has no auto locking after x minutes is also a security risk. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362841] New: Dolphin crashes after repartitining and reformatting (FAT32) external USB driver
https://bugs.kde.org/show_bug.cgi?id=362841 Bug ID: 362841 Summary: Dolphin crashes after repartitining and reformatting (FAT32) external USB driver Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tvanenge...@victronenergy.com Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Using KDE Partition Manager I was repartitioning (removed some ntfs partitions and created a FAT32 one) an external USB drive. The drive was not mounted. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63911948c0 (LWP 2564))] Thread 3 (Thread 0x7f638ea92700 (LWP 2565)): #0 0x7f63a3fabe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6398738c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f639873a8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6390de4629 in QXcbEventReader::run (this=0x1d21d00) at qxcbconnection.cpp:1253 #4 0x7f639eb7d84e in QThreadPrivate::start (arg=0x1d21d00) at thread/qthread_unix.cpp:331 #5 0x7f639b32c6fa in start_thread (arg=0x7f638ea92700) at pthread_create.c:333 #6 0x7f63a3fb7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6384b09700 (LWP 2566)): #0 0x7f63a3fabe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f639a7a131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f639a7a142c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f639edb4a9b in QEventDispatcherGlib::processEvents (this=0x7f6388c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f639ed5bdea in QEventLoop::exec (this=this@entry=0x7f6384b08d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f639eb788a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f639eb7d84e in QThreadPrivate::start (arg=0x21ca860) at thread/qthread_unix.cpp:331 #7 0x7f639b32c6fa in start_thread (arg=0x7f6384b09700) at pthread_create.c:333 #8 0x7f63a3fb7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f63911948c0 (LWP 2564)): [KCrash Handler] #6 0x7f63a3ee6418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f63a3ee801a in __GI_abort () at abort.c:89 #8 0x7f639eb6aff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578 #9 QMessageLogger::fatal (this=this@entry=0x7fff72eea080, msg=msg@entry=0x7f63a46edd28 "Cannot construct placeholder type QDBusRawType") at global/qlogging.cpp:781 #10 0x7f63a46ca552 in QDBusRawTypeHandler::construct () at qdbusmetaobject.cpp:133 #11 0x7f639ed9e9c0 in QMetaType::construct (copy=0x0, where=0x7fff72eea1a0, this=0x7fff72eea0e0) at ../../include/QtCore/../../src/corelib/kernel/qmetatype.h:2141 #12 (anonymous namespace)::customConstruct (d=0x7fff72eea1a0, copy=0x0) at kernel/qvariant.cpp:1019 #13 0x7f639ed9f8bf in QVariant::QVariant (this=0x7fff72eea1a0, typeId=, copy=) at kernel/qvariant.cpp:1660 #14 0x7f639ed6bcf2 in QMetaProperty::read (this=this@entry=0x7fff72eea240, object=object@entry=0x286efc0) at kernel/qmetaobject.cpp:3010 #15 0x7f639ed8bb0f in QObject::property (this=0x286efc0, name=0x2b29678 "MountPoints") at kernel/qobject.cpp:3893 #16 0x7f63a1b92664 in Solid::Backends::UDisks2::DeviceBackend::checkCache (this=0x2667260, key=...) at ../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185 #17 0x7f63a1b92883 in Solid::Backends::UDisks2::DeviceBackend::propertyExists (this=0x2667260, key=...) at ../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132 #18 0x7f63a1b8a5be in Solid::Backends::UDisks2::Device::propertyExists (this=this@entry=0x2b296b0, key=...) at ../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:126 #19 0x7f63a1b8c37f in Solid::Backends::UDisks2::Device::isMounted (this=0x2b296b0) at ../../../src/solid/devices/backends/udisks2/udisksdevice.cpp:818 #20 0x7f63a1ba5711 in Solid::Backends::UDisks2::StorageAccess::isAccessible (this=0x2c768e0) at ../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:75 #21 0x7f63a1ba5944 in Solid::Backends::UDisks2::StorageAccess::updateCache (this=0x2c768e0) at ../../../src/solid/devices/backends/udisks2/udisksstorageaccess.cpp:138 #22 Solid::Backends::UDisks2::StorageAccess::StorageAccess (this=0x2c768e0, device=0x2b296b0, __in_chrg=, __vtt_parm
[frameworks-kwallet] [Bug 362842] New: Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 Bug ID: 362842 Summary: Error code -8 after attempting to open wallet Product: frameworks-kwallet Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: christophe.cail...@gmail.com CC: kdelibs-b...@kde.org After attempting to authenticate for opening the wallet I have a dialog box with Error code -8 after typing my password Reproducible: Always Steps to Reproduce: 1. Log in to my session 2. Waiting for allet dialog to open 3. Typing my password 4. Having the error dialog box Actual Results: Looping on Error code -8 dialog box for typing again my wallet password Expected Results: Wallet is opened and all apps can access to it build URL : http://build.neon.kde.org/job/xenial_unstable_frameworks_kwallet/9/ with reference 87e774825b779ba846315a8b2ffe6479dd9f9814 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362843] New: Show user sftp warnings
https://bugs.kde.org/show_bug.cgi?id=362843 Bug ID: 362843 Summary: Show user sftp warnings Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pas...@dhermilly.dk I was getting really weird connection problems using sftp:// When I finally tried to connect with commandline ssh to debug I got this warning: @@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@ Permissions 0644 for '/home/pascal/.ssh/id_rsa' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Load key "/home/pascal/.ssh/id_rsa": bad permissions When I fixed it the problems where resolved. It would be really nice if Dolphin would show the user messages like this. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 Harald Sitter changed: What|Removed |Added Severity|normal |major CC||sit...@kde.org, ||win...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 360490] Crash after closing "DCC status" tab
https://bugs.kde.org/show_bug.cgi?id=360490 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/konv ||ersation/6130f4f0501f4e9db5 ||6619317f07e2f637160505 --- Comment #4 from Eike Hein --- Git commit 6130f4f0501f4e9db56619317f07e2f637160505 by Eike Hein. Committed on 09/05/2016 at 08:42. Pushed by hein into branch '1.6'. Don't crash when closing the DCC Status tab. M +8-1src/viewer/viewcontainer.cpp http://commits.kde.org/konversation/6130f4f0501f4e9db56619317f07e2f637160505 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 --- Comment #1 from Harald Sitter --- FWIW, after downgrading to a build from May 4 this is not a problem and the only changes between May 4 and the broken build are b3a95ba0540e01a9bb10db53fc449cc49ce9a9e8 and 87e774825b779ba846315a8b2ffe6479dd9f9814 regarding Q_BYTE_ORDER. I've CC'd Allen since 87e774825b779ba846315a8b2ffe6479dd9f9814 is meant to fix the blowfish backend, but apparently it doesn't for existing wallets :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358990] Make possible to move desktop icons freely again
https://bugs.kde.org/show_bug.cgi?id=358990 --- Comment #5 from Nick Stefanov --- One more vote for this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362844] New: Drag and Drop in Present windows
https://bugs.kde.org/show_bug.cgi?id=362844 Bug ID: 362844 Summary: Drag and Drop in Present windows Product: kwin Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: martin.tlus...@gmail.com I would like to be ablet do drag a file from dolphin to kmail to create an attachment via the "present windows" effect. Right now I can drag the file into the activated corner, and the windows will be presented, but I can not drop it onto another window. It copies the file to the original folder insted, presenting me with a dialog to change the file name. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] New: sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 Bug ID: 362845 Summary: sddm shows empty space instead of several "0" digits for system time in login prompt Product: user-manager Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcontrol module Assignee: afies...@kde.org Reporter: renda.kr...@gmail.com Only after reboot, sddm often shows empty space instead of the digt of the system time. This happened for digits which have been set to "0", they appeared whe never switching to "1". After logout it seems to be ok from what I have seen. Reproducible: Sometimes Steps to Reproduce: 1. Reboot computer and wait for sddm login prompt Actual Results: Empty "0" digits in system time display (see screenshot) -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #1 from René Krell --- Created attachment 98854 --> https://bugs.kde.org/attachment.cgi?id=98854&action=edit Screenshot of SDDM logon prompt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302527] TEMPLATE : metadata editing not possible (copyright, city, ...)
https://bugs.kde.org/show_bug.cgi?id=302527 widil...@gmail.com changed: What|Removed |Added CC||widil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com --- Comment #37 from Elvis Stansvik --- Is anyone looking into this? It's an almost 3 year old "major" bug. It's highly irritating because many applications have a statusbar or other elements at the bottom which gets hidden if maximized. So I have to manually adjust the height of the window to see it. But if I do that, the window gets "de-maximized", making it impossible to just slam my mouse cursor to the top-right and click to close it (breaking Fittz law). -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 362846] New: kaddressbook 5.1.3: drag and drop a contact to a google subgroup to add category
https://bugs.kde.org/show_bug.cgi?id=362846 Bug ID: 362846 Summary: kaddressbook 5.1.3: drag and drop a contact to a google subgroup to add category Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: martin.tlus...@gmail.com CC: to...@kde.org I would like to be able to drag and drop a google contact to a subgroup to add it to the corresponding category. Also, I would like to be able to delete a category from a contact, either via deleting it in the subgroup or dragging it from the subgroup to the main contacts list (that would need to be documented, though, as it is not exaclty intiutive behavior... ;-) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362847] New: Cannot create any VPN connection
https://bugs.kde.org/show_bug.cgi?id=362847 Bug ID: 362847 Summary: Cannot create any VPN connection Product: plasma-nm Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: lu...@kde.org Reporter: ovidiu@gmail.com CC: jgrul...@redhat.com When creating a VPN connection and typing anything in the gateway field longer than one letter, when I click OK, I'm presented with this notification and the connection is not created: «connection.gateway-ping-timeout: can not set property: value "18454592" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint'» I've tested with PPTP mostly, but SSH also fails. I've also tested with importing a connection, and it fails with the same message. Reproducible: Always Steps to Reproduce: 1. Open NetworkManager (plasma GUI) 2. create new VPN connection (try PPTP) 3. add anything longer than one character in the gateway field 4. save the connection Actual Results: Notification is shown and creation of the connection fails. Expected Results: Connection to be created. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 --- Comment #38 from Elvis Stansvik --- Btw, the monitor/screen layout I'm using is: xrandr --output DP2-2 --mode 2560x1440 --primary --output eDP1 --mode 1920x1080 --left-of DP2-2 That is, the laptop panel (eDP1) to the left of my external monitor (DP2-2), which is my primary output. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 362846] kaddressbook 5.1.3: drag and drop a contact to a google subgroup to add category
https://bugs.kde.org/show_bug.cgi?id=362846 Martin Tlustos changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362847] Cannot create any VPN connection
https://bugs.kde.org/show_bug.cgi?id=362847 Jan Grulich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 362141 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 362141] Can not fully create or edit Connection
https://bugs.kde.org/show_bug.cgi?id=362141 Jan Grulich changed: What|Removed |Added CC||pirko...@gmail.com CC||ovidiu@gmail.com --- Comment #4 from Jan Grulich --- *** Bug 362443 has been marked as a duplicate of this bug. *** --- Comment #5 from Christoph Feck --- *** Bug 362423 has been marked as a duplicate of this bug. *** --- Comment #6 from Jan Grulich --- *** Bug 362847 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #2 from René Krell --- This has been present already in previous versions. Using the nvidia native graphics driver, if this is important here. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362848] New: packagekit gets angry about amount of transactions
https://bugs.kde.org/show_bug.cgi?id=362848 Bug ID: 362848 Summary: packagekit gets angry about amount of transactions Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org If I go to the updates page (with 272 updates), packagekit gets angry with discover and starts shouting muondiscover(26943)/(default) PackageKitResource::fetchDetails()::
[digikam] [Bug 302527] TEMPLATE : metadata editing not possible (copyright, city, ...)
https://bugs.kde.org/show_bug.cgi?id=302527 --- Comment #16 from widil...@gmail.com --- I really like digikam and use it for quite some time now, but this is the one big flaw of digikam that ever since annoys me. I find it very unintuitive that the fields of the "Information" tab are not directly editable. Having templates is nice as an additional tool but it is not a replacement for being able to edit fields directly. Further, according to this old mail from the malinglist, it indeed was once possible to do it (https://mail.kde.org/pipermail/digikam-users/2012-January/015668.html). As this bugreport is really old now, I would like to know: are there intentions to eventually fix this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 362141] Can not fully create or edit Connection
https://bugs.kde.org/show_bug.cgi?id=362141 --- Comment #7 from Ovidiu-Florin BOGDAN --- What is the frameworks version we should expect this fix to be in? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361711] can't close discover after update
https://bugs.kde.org/show_bug.cgi?id=361711 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Harald Sitter --- Can't manage to reproduce it. Closing for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362844] Drag and Drop in Present windows
https://bugs.kde.org/show_bug.cgi?id=362844 --- Comment #1 from Thomas Lübking --- https://git.reviewboard.kde.org/r/105341/ the patch was supposed to keep window selection possible. you'd have to exit the effect by keyboard then (and have the desired window focused) you can forget about direct dnd on x11 because there's no input redirection, ie. we cannot reasonably map the drop event -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #3 from René Krell --- Compiled and running in Qt 5.5.1 when reporting this. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 362762] Unable to create io-slave: Could not find the 'kio_kamera' plugin.
https://bugs.kde.org/show_bug.cgi?id=362762 Ruben Decrop changed: What|Removed |Added CC||ru...@decrop.net --- Comment #1 from Ruben Decrop --- Same with me with an iPhone -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 --- Comment #2 from Christophe Caillet --- root@mithrandir:~# zgrep --no-filename 'install ' $(ls -rt /var/log/dpkg*) | tail 2016-05-04 16:32:58 install libntlm0:amd64 1.4-7 2016-05-04 16:32:58 install gkrellm:amd64 2.3.6~rc1-1build1 2016-05-09 09:24:57 install mesa-utils:amd64 8.3.0-1 2016-05-09 09:24:59 install libxcb-xinerama0:amd64 1.11.1-1ubuntu1 2016-05-09 09:25:43 install plasma-discover-private:amd64 5.6.2-1ubuntu1 5.6.3+p16.04+git20160506.1330-0 2016-05-09 09:26:17 install linux-image-4.4.0-22-generic:amd64 4.4.0-22.39 2016-05-09 09:26:19 install linux-image-extra-4.4.0-22-generic:amd64 4.4.0-22.39 2016-05-09 09:26:25 install linux-signed-image-4.4.0-22-generic:amd64 4.4.0-22.39 2016-05-09 09:26:26 install linux-headers-4.4.0-22:all 4.4.0-22.39 2016-05-09 09:26:30 install linux-headers-4.4.0-22-generic:amd64 4.4.0-22.39 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 362849] New: meinproc5.exe searches the wrong path for kdoctools
https://bugs.kde.org/show_bug.cgi?id=362849
Bug ID: 362849
Summary: meinproc5.exe searches the wrong path for kdoctools
Product: frameworks-kdoctools
Version: unspecified
Platform: Compiled Sources
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kde-doc-engl...@kde.org
Reporter: mutla...@ikarustech.com
CC: kdelibs-b...@kde.org
OS: Win10 64bit, using Powershell, Qt 5.6 with MSVS2015 compiler (Qt not
emerged).
I emerged frameworks and I encountered the following error:
jom 1.0.16 - empower your cores
D:\k\dev-utils\bin\cmake.exe -HD:\k\download\git\kpackage
-BD:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master
--check-build-system CMakeFiles\Makefile.cmake 0
D:\k\dev-utils\bin\cmake.exe -E cmake_progress_start
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\CMakeFiles
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\CMakeFiles\progress.marks
D:\k\dev-utils\bin\jom.exe -f CMakeFiles\Makefile2 /nologo - all
D:\k\dev-utils\bin\jom.exe -f
docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\build.make
/nologo -L
docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\depend
D:\k\dev-utils\bin\cmake.exe -E cmake_depends "NMake Makefiles"
D:\k\download\git\kpackage D:\k\download\git\kpackage\docs\kpackagetool
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-
master\docs\kpackagetool
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\DependInfo.cmake
--color=
Dependee
"D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\DependInfo.cmake"
is newer than depender
"D:/k/build/frameworks/kpackage/work/msvc2015-RelWithDebInfo-master/docs/kpackagetool/
CMakeFiles/docs-kpackagetool-kpackagetool5-1.dir/depend.internal".
Dependee
"D:/k/build/frameworks/kpackage/work/msvc2015-RelWithDebInfo-master/docs/kpackagetool/CMakeFiles/CMakeDirectoryInformation.cmake"
is newer than depender
"D:/k/build/frameworks/kpackage/work/msvc2015-RelWithDebInfo-master/docs/kpackagetool/CMakeFiles/docs-kpackag
etool-kpackagetool5-1.dir/depend.internal".
Scanning dependencies of target docs-kpackagetool-kpackagetool5-1
D:\k\dev-utils\bin\jom.exe -f
docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\build.make
/nologo -L
docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\build
[ 2%] Generating kpackagetool5.1
cd
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\docs\kpackagetool
D:\k\bin\meinproc5.exe --stylesheet
D:/k/share/kf5/kdoctools/customization/kde-include-man.xsl --check
D:/k/download/git/kpackage/docs/kpackagetool/man-kpackagetool5.1.docbook
Could not locate file "kf5/kdoctools/customization" in
("C:/Users/Jasem/AppData/Local", "C:/ProgramData", "D:/k/bin", "D:/k/bin/data")
Could not locate file "kf5/kdoctools/customization" in
("C:/Users/Jasem/AppData/Local", "C:/ProgramData", "D:/k/bin", "D:/k/bin/data")
Error: Could not find kdoctools catalogs
jom:
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\build.make
[docs\kpackagetool\kpackagetool5.1] Error 1
jom:
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\CMakeFiles\Makefile2
[docs\kpackagetool\CMakeFiles\docs-kpackagetool-kpackagetool5-1.dir\all] Error
2
jom:
D:\k\build\frameworks\kpackage\work\msvc2015-RelWithDebInfo-master\Makefile
[all] Error 2
*** Emerge all failed: all of frameworks/kpackage failed after 0:00:05 ***
emerge error: fatal error: package frameworks/kpackage all failed
PS D:\k> D:\k\bin\meinproc5.exe --stylesheet
D:/k/share/kf5/kdoctools/customization/kde-include-man.xsl --check
D:/k/download/git/kpackage/docs/kpackagetool/man-kpackagetool5.1.docbook
Could not locate file "kf5/kdoctools/customization" in
("C:/Users/Jasem/AppData/Local", "C:/ProgramData", "D:/k/bin", "D:/k/bin/data")
Could not locate file "kf5/kdoctools/customization" in
("C:/Users/Jasem/AppData/Local", "C:/ProgramData", "D:/k/bin", "D:/k/bin/data")
Error: Could not find kdoctools catalogs
Why is meinproc5.exe looking in k/bin and k/bin/data ?!
kf5/kdoctools/customization is located under k/share
How to solve this problem?
Reproducible: Always
Steps to Reproduce:
1. emerge frameworks
2.
3.
Actual Results:
emerge frameworks fails to build
Expected Results:
emerge frameworks continues to build. meinproc5.exe finds kdoctools
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Harald Sitter --- I poked rebuilds of plasma-workspace and kwin as kwin should have compile-time ifdefs for Qt 5.6. Please check back when build 18 here is done and confirm that this fixes the issue: http://build.neon.kde.org/view/stable/job/xenial_stable_plasma_plasma-workspace/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 362850] New: Monitor Settings window not shows buttons
https://bugs.kde.org/show_bug.cgi?id=362850 Bug ID: 362850 Summary: Monitor Settings window not shows buttons Product: kde Version: unspecified Platform: Kubuntu Packages URL: http://s32.postimg.org/ksp0dl2kl/Screenshot_20160509_1 24506.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hesedie...@gmail.com When i open the monitor settings as in the attached image, putting it on full screen i cant always see the buttons like ok, cancel, apply. i have to move the window up with alt+mouse to see the buttons Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 362850] Monitor Settings window not shows buttons
https://bugs.kde.org/show_bug.cgi?id=362850 hesediel changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.
https://bugs.kde.org/show_bug.cgi?id=360963 --- Comment #2 from Tom Mittelstädt --- Does not work at all in 5.1.3 The selected identity is always the last one I've selected manually. expected behavior: I have one account "account@domain" and an alias for it "account\+*@domain". If I receive a mail for "account+project123@domain" I'd like kmail to automatically select the "account@domain" identity and use "account+project123@domain" as from/sender. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 --- Comment #5 from David Edmundson --- For Case #1: - qt now scales up font DPI for some reason, you can counter that by explicitly also setting QT_FONT_DPI to be half/double (not sure which way round it is) For Case #3 Since Plasma 5.5 we do have code to disable internal high DPI managing on Qt5.6 However, it requires kwin/plasma also be *compiled* with Qt5.6 #if (QT_VERSION >= QT_VERSION_CHECK(5, 6, 0)) QCoreApplication::setAttribute(Qt::AA_DisableHighDpiScaling); #endif -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362839] Nice option for disabling akonadi on non-PIM computers
https://bugs.kde.org/show_bug.cgi?id=362839 --- Comment #2 from Pascal d'Hermilly --- I installed akonadiconsole (not installed by default) and it comes with a pretty hefty warning upon opening: "Akonadi Console is purely a development tool. It allows you to view and change internal data structures of Akonadi. You should only change data in here if you know what you are doing, otherwise you risk damaging or losing your personal information management data. Use at your own risk!" When started: the menu bar -> server -> [does not contain configure server. Only start/stop/restart server] I don't think this option matches "A nice UI" :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358990] Make possible to move desktop icons freely again
https://bugs.kde.org/show_bug.cgi?id=358990 Aurélien Murith changed: What|Removed |Added Platform|Chakra |unspecified OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 Kai Uwe Broulik changed: What|Removed |Added CC||wen...@gmail.com --- Comment #6 from Kai Uwe Broulik --- Qt still takes into account QT_DEVICE_PIXEL_RATIO in 5.6 and does not merge it with the new one because the new one is in the core whereas the old is in the QPA and so both scale at the same time, a bugreport I opened was (of course...) closed as invalid because how dare we use this feature in the first place. Also I recall Qt still doing weird things even if the app opts out of scaling, so perhaps we need to go down the qunsetenv route there as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 358813] kdeinit5 crash after logout
https://bugs.kde.org/show_bug.cgi?id=358813 --- Comment #3 from Alexander Miroshnichenko --- crash dialog was open whole time and new dialog was created while every logout. I had updated to: KDE plasma 5.6.3 KDE Frameworks 5.21 Qt 5.6.0 Currently I does not see crash any more. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 --- Comment #7 from Harald Sitter --- list of AA_DisableHighDpiScaling usage for the record https://lxr.kde.org/search?_filestring=&_string=Qt%3A%3AAA_DisableHighDpiScaling -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 362141] Can not fully create or edit Connection
https://bugs.kde.org/show_bug.cgi?id=362141 --- Comment #8 from Jan Grulich --- It should be already in KDE Frameworks 5.21 and if not then definitely in 5.22 which is going to be released this week. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360031] KMail sometimes crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360031 Maurice Batey changed: What|Removed |Added CC||maur...@bcs.org.uk --- Comment #1 from Maurice Batey --- Similar problem here with Kmail 5.2.0 on 64-bit Mgeia-6-sta1 Plasma login. At first use after login, Kmail starts normally, but if exited then re-started, it immediately exits without a Kmail window appearing. But after doing logout/Login, it again starts normally. Will try to attach the result of an strace on such an occasion. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360031] KMail sometimes crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360031 --- Comment #2 from Maurice Batey --- Created attachment 98855 --> https://bugs.kde.org/attachment.cgi?id=98855&action=edit strace of Kmail failing to start normally strace of Kmail failing to start normally -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 360029] Kopete sometimes crashes on exit
https://bugs.kde.org/show_bug.cgi?id=360029 Vojtěch Zeisek changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Vojtěch Zeisek --- I wasn't able to reproduce the problem since then. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 346466] Akregator sometimes crashes
https://bugs.kde.org/show_bug.cgi?id=346466 Vojtěch Zeisek changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Vojtěch Zeisek --- I wasn't able to reproduce the bug again with the latest version. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 321535] Kdevelop freezes on specific c++ code
https://bugs.kde.org/show_bug.cgi?id=321535 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 338506] image wallpapers are blurry in scaled and scaled and cropped mode
https://bugs.kde.org/show_bug.cgi?id=338506 chermnykh2...@gmail.com changed: What|Removed |Added CC||chermnykh2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.
https://bugs.kde.org/show_bug.cgi?id=356326 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Rex Dieter --- The code in question clearly does not comply with project licensing policy, https://community.kde.org/Policies/Licensing_Policy Options include: * relicensing (of course) * removing the code (since it apparently unused) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362851] New: Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=362851 Bug ID: 362851 Summary: Plasma Crash Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jameschambers...@yahoo.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic i686 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I'd left my computer alone for ~30 mins, when I returned I pressed "Build & Run" on QtCreator and suddenly Plasma crashed. This has happend a few times before. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1b51800 (LWP 1624))] Thread 10 (Thread 0xb1717b40 (LWP 1628)): #0 0xb7782c31 in __kernel_vsyscall () #1 0xb4dadf8f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb712441d in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #3 0xb712659b in xcb_wait_for_event () from /usr/lib/i386-linux-gnu/libxcb.so.1 #4 0xb1858273 in QXcbEventReader::run (this=0x9faab08) at qxcbconnection.cpp:1253 #5 0xb508b43b in QThreadPrivate::start (arg=0x9faab08) at thread/qthread_unix.cpp:331 #6 0xb4c602b5 in start_thread (arg=0xb1717b40) at pthread_create.c:333 #7 0xb4db816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 9 (Thread 0xb01d0b40 (LWP 1659)): #0 0xb7782c31 in __kernel_vsyscall () #1 0xb4da6c4f in read () at ../sysdeps/unix/syscall-template.S:84 #2 0xb4492035 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb444caea in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb444cff1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb444d194 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb52bab14 in QEventDispatcherGlib::processEvents (this=0xaf800470, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0xb525f953 in QEventLoop::processEvents (this=0xb01d01d4, flags=...) at kernel/qeventloop.cpp:128 #8 0xb525fdaa in QEventLoop::exec (this=0xb01d01d4, flags=...) at kernel/qeventloop.cpp:204 #9 0xb5085f1d in QThread::exec (this=0xa046a98) at thread/qthread.cpp:503 #10 0xb68f6aff in QQmlThreadPrivate::run (this=0xa046a98) at qml/ftw/qqmlthread.cpp:141 #11 0xb508b43b in QThreadPrivate::start (arg=0xa046a98) at thread/qthread_unix.cpp:331 #12 0xb4c602b5 in start_thread (arg=0xb01d0b40) at pthread_create.c:333 #13 0xb4db816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 8 (Thread 0xab53fb40 (LWP 1664)): #0 0xb7782c31 in __kernel_vsyscall () #1 0xb4c65a8c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb4dc48cd in __pthread_cond_wait (cond=0xa146dd8, mutex=0xa146dc0) at forward.c:149 #3 0xae7cc80a in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so #4 0xae7cc675 in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so #5 0xb4c602b5 in start_thread (arg=0xab53fb40) at pthread_create.c:333 #6 0xb4db816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xaad3eb40 (LWP 1665)): #0 0xb7782c31 in __kernel_vsyscall () #1 0xb4c65a8c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb4dc48cd in __pthread_cond_wait (cond=0xa146ed4, mutex=0xa146ebc) at forward.c:149 #3 0xae7cc80a in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so #4 0xae7cc675 in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so #5 0xb4c602b5 in start_thread (arg=0xaad3eb40) at pthread_create.c:333 #6 0xb4db816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xa8e5ab40 (LWP 1668)): #0 0xb7782c31 in __kernel_vsyscall () #1 0xb7782888 in __vdso_clock_gettime () #2 0xb4dc53c2 in __GI___clock_gettime (clock_id=1, tp=0xa8e59f24) at ../sysdeps/unix/clock_gettime.c:115 #3 0xb5129338 in qt_clock_gettime (ts=0xa8e59f24, clock=) at tools/qelapsedtimer_unix.cpp:105 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #6 0xb52b83e2 in QTimerInfoList::updateCurrentTime (this=0xa850289c) at kernel/qtimerinfo_unix.cpp:84 #7 0xb52b8904 in QTimerInfoList::timerWait (this=0xa850289c, tm=...) at kernel/qtimerinfo_unix.cpp:381 #8 0xb52b9ec9 in timerSourcePrepareHelper (timeout=0xa8e5a038, src=0xa8502868) at kernel/qeventdispatcher_glib.cpp:127 #9 timerSourcePrepare (source=0xa8502868, timeout=0xa8e5a038) at kernel/qeventdispatcher_glib.cpp:160 #10 0xb444c51b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #11 0xb444cf64 in ?? () from /l
[frameworks-kdoctools] [Bug 362849] meinproc5.exe searches the wrong path for kdoctools
https://bugs.kde.org/show_bug.cgi?id=362849 Luigi Toscano changed: What|Removed |Added CC||kde-wind...@kde.org, ||luigi.tosc...@tiscali.it --- Comment #1 from Luigi Toscano --- This was tested and it should definitely work, but I need help from windows developers. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 --- Comment #3 from Allen Winter --- I'm at a loss to explain it. I suppose we roll back before b3a95ba0540e01a9bb10db53fc449cc49ce9a9e8 then. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 362842] Error code -8 after attempting to open wallet
https://bugs.kde.org/show_bug.cgi?id=362842 Allen Winter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Allen Winter --- rolled back in commit 0d56c68d7a2204a987a5255096d004d5a696c0e5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 269367] There is no way to search in hidden folders now.
https://bugs.kde.org/show_bug.cgi?id=269367 haoxian.z...@gmail.com changed: What|Removed |Added CC||haoxian.z...@gmail.com --- Comment #13 from haoxian.z...@gmail.com --- Can confirm this problem still exists in KDE 15.12.3, with, KDE Frameworks 5.21.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362852] New: Maximized window goes beyond desktop bounds
https://bugs.kde.org/show_bug.cgi?id=362852 Bug ID: 362852 Summary: Maximized window goes beyond desktop bounds Product: krita Version: 3.0 Beta Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: haigpet...@gmail.com When maximizing the application window in Mint 17.3 KDE edition, the title bar goes a few pixels beyond the topmost screen/desktop edge. Qt4 bug? Can't test on Qt5 to really tell. Reproducible: Always Steps to Reproduce: 1. Laumch Krita 3.0 beta 2. Maximize window 3. Top edge goes out of bounds Actual Results: Top application title bar goes several pixels out of bounds. Expected Results: All application edges should respect the desktop boundaries on maximize. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351897] Plasma Shell freezes/hangs on file operations
https://bugs.kde.org/show_bug.cgi?id=351897 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 348686] knetwalk 3.3.0 does not update network node icons
https://bugs.kde.org/show_bug.cgi?id=348686 dmatt changed: What|Removed |Added CC||xdarkmat...@gmail.com --- Comment #2 from dmatt --- I confirm this bug is also present in knetwalk on Kubuntu 16.04. Sound of turning on/off is present, icon does not update. Version 3.3.0 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 362791] recorded video file corrupted
https://bugs.kde.org/show_bug.cgi?id=362791 --- Comment #2 from RJ --- Created attachment 98856 --> https://bugs.kde.org/attachment.cgi?id=98856&action=edit recorded video with marble -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358990] Make possible to move desktop icons freely again
https://bugs.kde.org/show_bug.cgi?id=358990 RJ changed: What|Removed |Added CC||ogldel...@mail.ru --- Comment #6 from RJ --- Yes, I vote from me. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 362825] Error in { : task 1 failed - "could not find function "trellis.last.object""
https://bugs.kde.org/show_bug.cgi?id=362825
--- Comment #3 from Michael ---
Error in { :
task 1 failed - "could not find function "trellis.last.object""
> getAnywhere("trellis.last.object")
A single object matching ‘trellis.last.object’ was found
It was found in the following places
namespace:lattice
with value
function (..., prefix = lattice.getStatus("current.prefix"))
{
if (!lattice.getStatus("current.plot.saved", prefix = prefix)) {
warning("Requested 'trellis' object was not saved")
return(invisible(NULL))
}
ans <- lattice.getStatus("last.object", prefix = prefix)
update(ans, ...)
}
Thank You.
On 05/09/2016 12:46 AM, Thomas Friedrichsmeier via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=362825
>
> Thomas Friedrichsmeier changed:
>
> What|Removed |Added
>
> CC||thomas.friedrichsmeier@ruhr
> ||-uni-bochum.de
>
> --- Comment #2 from Thomas Friedrichsmeier
> ---
> Thanks for reporting. I'll try to look into this, soon, but very distracted,
> ATM.
>
> Could you add the output of
> getAnywhere ("trellis.last.object")
> to this report (after the error)?
>
> For the time being, you should be able to work around this by disabling the
> plot history feature, either for this call, only (rk.without.plot.history())
> or
> entirely (Settings->Onscreen Graphics->Screen device history).
>
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 362852] Maximized window goes beyond desktop bounds
https://bugs.kde.org/show_bug.cgi?id=362852 --- Comment #1 from Boudewijn Rempt --- It's a bug in Qt that happens when the left-hand toolbox is too high. If you make it wider, then reset the window size it'll fit again. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9
https://bugs.kde.org/show_bug.cgi?id=362805 Gabriel C changed: What|Removed |Added CC||nix.or@gmail.com --- Comment #13 from Gabriel C --- Hello Allen , well I cannot see how this can work .. from my tests this breaks kwallet <=5.21.0. meaning 5.21.0 -> master is broken always gives you a -9 error master setup and back to 5.21.0 is broken gives always -9 error The Q_BYTE_ORDER == .. in code was right just br0ken by missing header files on <=5.21.0 so I cannot see how this can be fixed to keep compatibility.. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 362853] New: Driver for WLan, Audio, Bluetooth not aviable
https://bugs.kde.org/show_bug.cgi?id=362853 Bug ID: 362853 Summary: Driver for WLan, Audio, Bluetooth not aviable Product: plasma-integration Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: hel...@goebel-shg.de After Updating Kubuntu last Week, Audio-Hardware, Bluetooth, WLan will be not supported of Kubuntu-system. in further Version all funktions are OK. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Alexander Schlarb changed: What|Removed |Added CC||alexander-...@xmine128.tk --- Comment #19 from Alexander Schlarb --- The best solution for everybody is probably this: https://wiki.gnome.org/Projects/KioGioBridge Aside from the fact that the development stalled after KDE 4.1, of course… -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 362854] New: Success of the `CLOSE` command is not enough and the subsequent SELECT fails because of a missing [CLOSED] response code
https://bugs.kde.org/show_bug.cgi?id=362854 Bug ID: 362854 Summary: Success of the `CLOSE` command is not enough and the subsequent SELECT fails because of a missing [CLOSED] response code Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: j...@kde.org 16:44:25.460 >>> y23 SELECT INBOX (QRESYNC (1457558562 1))␍␊ 16:44:25.511 <<< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)␍␊ 16:44:25.511 <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.␍␊ 16:44:25.511 <<< * 0 EXISTS␍␊ 16:44:25.511 <<< * 0 RECENT␍␊ 16:44:25.511 <<< * OK [UIDVALIDITY 1457558562] UIDs valid␍␊ 16:44:25.511 <<< * OK [UIDNEXT 1] Predicted next UID␍␊ 16:44:25.511 <<< * OK [HIGHESTMODSEQ 1] Highest␍␊ 16:44:25.512 <<< y23 OK [READ-WRITE] Select completed.␍␊ 16:44:25.512 conn Synchronizing mailbox... 16:44:25.513 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX First interesting message at 0 () 16:44:25.513 conn Mailbox opened. 16:44:25.514 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX Completed 16:44:25.514 Imap::Mailbox::KeepMailboxOpenTask attached to INBOX Activated 16:44:29.942 >>> y24 CLOSE␍␊ 16:44:29.984 <<< y24 OK Close completed.␍␊ 16:44:29.984 Imap::Mailbox::DeleteMailboxTask Activated 16:44:29.985 >>> y25 DELETE INBOX␍␊ 16:44:30.022 <<< y25 NO INBOX can't be deleted.␍␊ 16:44:30.022 Imap::Mailbox::DeleteMailboxTask Failed: Couldn't delete mailbox 16:44:33.690 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_WAIT_FOR_CONN dev.gentoo Activated 16:44:33.691 conn Waiting for another mailbox... 16:44:33.694 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING dev.gentoo Synchronizing mailbox 16:44:33.709 >>> y26 SELECT "dev.gentoo" (QRESYNC (1457558573 61 (33,50,58,62,64 83,100,108,112,114)))␍␊ 16:44:33.839 <<< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)␍␊ 16:44:33.839 <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.␍␊ 16:44:33.839 <<< * 64 EXISTS␍␊ 16:44:33.839 <<< * 0 RECENT␍␊ 16:44:33.839 <<< * OK [UIDVALIDITY 1457558573] UIDs valid␍␊ 16:44:33.839 <<< * OK [UIDNEXT 115] Predicted next UID␍␊ 16:44:33.839 <<< * OK [HIGHESTMODSEQ 61] Highest␍␊ 16:44:33.839 <<< y26 OK [READ-WRITE] Select completed.␍␊ 16:44:33.840 Imap::Mailbox::KeepMailboxOpenTask attached to dev.gentoo Failed: The connection is being killed for unspecified reason 16:44:33.840 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING dev.gentoo Failed: The connection is being killed for unspecified reason 16:44:33.840 *** Connection killed. 16:44:33.840 UnexpectedResponseReceived Server did not send the CLOSED response code to notify us that the previous mailbox was successfully closed. Stopping the sync to prevent data loss.␊␊ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362743] Conflicting shortcuts don't get solved with 'reassign'
https://bugs.kde.org/show_bug.cgi?id=362743 Michael changed: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- Should be fixed here: https://phabricator.kde.org/rKRITA8b2567b4d186cd188f47c4b1aa20311b4f22728e -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 362855] New: Baloo File Indexing Daemon closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=362855 Bug ID: 362855 Summary: Baloo File Indexing Daemon closed unexpectedly Product: Baloo Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: dmudhi...@yahoo.com CC: pinak.ah...@gmail.com Application: baloo_file (5.18.0) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: We're sorry, Baloo File Indexing Daemon closed unexpectedly Details: Executable: baloo_file PID: 1402 Signal: Aborted (6) Time: 2016-05-09 20:09:41 - What I was doing when the application crashed: Downloaded file with uget download manager Backtrace - Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_robust_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevelrobustlock.S:85 [Current thread is 1 (Thread 0x7f65afab18c0 (LWP 1402))] Thread 2 (Thread 0x7f64649f9700 (LWP 2580)): [KCrash Handler] #6 0x7f65adaf4418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f65adaf601a in __GI_abort () at abort.c:89 #8 0x7f65ac2f9002 in mdb_assert_fail (env=0xd03110, expr_txt=expr_txt@entry=0x7f65ac2faa5f "rc == 0", func=func@entry=0x7f65ac2fb398 <__func__.7098> "mdb_page_dirty", line=line@entry=2065, file=0x7f65ac2faa40 "mdb.c") at mdb.c:1481 #9 0x7f65ac2ee6a5 in mdb_page_dirty (txn=0xd45460, mp=) at mdb.c:2065 #10 0x7f65ac2ef863 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f64649f80d8, mc=0x7f64649f8610) at mdb.c:2246 #11 0x7f65ac2efac9 in mdb_page_touch (mc=mc@entry=0x7f64649f8610) at mdb.c:2364 #12 0x7f65ac2f1704 in mdb_cursor_touch (mc=mc@entry=0x7f64649f8610) at mdb.c:6267 #13 0x7f65ac2f4805 in mdb_cursor_put (mc=0x7f64649f8610, key=0x7f64649f89f0, data=0x7f64649f8a00, flags=) at mdb.c:6401 #14 0x7f65ac2f7260 in mdb_put (txn=0xd45460, dbi=2, key=key@entry=0x7f64649f89f0, data=data@entry=0x7f64649f8a00, flags=flags@entry=0) at mdb.c:8759 #15 0x7f65aec8e71a in Baloo::PostingDB::put (this=this@entry=0x7f64649f8ad0, term=..., list=...) at ../../../src/engine/postingdb.cpp:78 #16 0x7f65aec9fb31 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:307 #17 0x7f65aec97032 in Baloo::Transaction::commit (this=this@entry=0x7f64649f8bd0) at ../../../src/engine/transaction.cpp:262 #18 0x0041c8e0 in Baloo::NewFileIndexer::run (this=0xd48990) at ../../../src/file/newfileindexer.cpp:75 #19 0x7f65ae5b5343 in QThreadPoolThread::run (this=0xd38f40) at thread/qthreadpool.cpp:93 #20 0x7f65ae5b884e in QThreadPrivate::start (arg=0xd38f40) at thread/qthread_unix.cpp:331 #21 0x7f65ad21c6fa in start_thread (arg=0x7f64649f9700) at pthread_create.c:333 #22 0x7f65adbc5b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f65afab18c0 (LWP 1402)): #0 __lll_robust_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevelrobustlock.S:85 #1 0x7f65ad21ea28 in __pthread_mutex_lock_full (mutex=0x7f65afc58040) at ../nptl/pthread_mutex_lock.c:256 #2 0x7f65ac2edc32 in mdb_txn_renew0 (txn=txn@entry=0xd45460) at mdb.c:2692 #3 0x7f65ac2eef14 in mdb_txn_begin (env=0xd03110, parent=parent@entry=0x0, flags=flags@entry=0, ret=ret@entry=0x791bc808) at mdb.c:2850 #4 0x7f65aec9699b in Baloo::Transaction::Transaction (this=0x791bc800, db=..., type=Baloo::Transaction::ReadWrite) at ../../../src/engine/transaction.cpp:53 #5 0x004296bf in Baloo::MetadataMover::removeFileMetadata (this=0xc5ca50, file=...) at ../../../src/file/metadatamover.cpp:65 #6 0x7f65ae7c7e4f in QtPrivate::QSlotObjectBase::call (a=0x791bc950, r=0xc5ca50, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #7 QMetaObject::activate (sender=sender@entry=0xced9e0, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x791bc950) at kernel/qobject.cpp:3698 #8 0x7f65ae7c87d7 in QMetaObject::activate (sender=sender@entry=0xced9e0, m=m@entry=0x645940 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x791bc950) at kernel/qobject.cpp:3578 #9 0x00432f05 in Baloo::PendingFileQueue::removeFileIndex (this=this@entry=0xced9e0, _t1=...) at moc_pendingfilequeue.cpp:217 #10 0x00427856 in Baloo::PendingFileQueue::processCache (this=0xced9e0) at ../../../src/file/pendingfilequeue.cpp:89 #11 0x7f65ae7c7e4f in QtPrivate::QSlotObjectBase::call (a=0x791bcad0, r=0xced9e0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #12 QMetaObject::activate (sender=sender@entry=0xced9f8, si
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 Freddie Chopin changed: What|Removed |Added CC||freddie_cho...@op.pl -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 205349] Amarok skips next track in playlist if it is shorter than current one
https://bugs.kde.org/show_bug.cgi?id=205349 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 --- Comment #8 from Greg Varsanyi --- (In reply to David Edmundson from comment #5) > For Case #1: > - qt now scales up font DPI for some reason, you can counter that by > explicitly also setting > QT_FONT_DPI to be half/double (not sure which way round it is) > > For Case #3 > > Since Plasma 5.5 we do have code to disable internal high DPI managing on > Qt5.6 > > However, it requires kwin/plasma also be *compiled* with Qt5.6 > > #if (QT_VERSION >= QT_VERSION_CHECK(5, 6, 0)) > QCoreApplication::setAttribute(Qt::AA_DisableHighDpiScaling); > #endif playing with QT_FONT_DPI gets me the closest. a combination of QT_FONT_DPI=96 and QT_DEVICE_PIXEL_RATIO=2 (and not setting/unsetting any new Qt 5.6 env vars) gives me consistent look and feel across the *apps*, but not plasmashell and kwin - they go half sized. it would seem that plasmashell and kwin read the font dpi value and apply that literally as pixels. that can also be mitigated by starting these two (and only these two) with QT_FONT_DPI=192. So, using a deprecated and a falsified env var - with some exception handling - mostly gets us there. -- i wonder why did you guys decided to disable the native scaling. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 swpal...@gmail.com changed: What|Removed |Added CC||swpal...@gmail.com --- Comment #5 from swpal...@gmail.com --- Bad user experience? Doesn't that pretty much define Linux and the UI-impaired people that maintain it? Yes, this is a significant issue. An embarrassment really. But on Linux, everyone has to be a sysadmin. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 347976] Rotated ps(.gz)
https://bugs.kde.org/show_bug.cgi?id=347976 --- Comment #1 from Antony Lee --- Kindly bumping the issue. Anything I can do to help? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362767] High DPI is messed up after Qt 5.6 update
https://bugs.kde.org/show_bug.cgi?id=362767 --- Comment #9 from Weng Xuetian --- IIRC, though QT_DEVICE_PIXEL_RATIO is still there, it's not doing the exact same thing as it is in 5.5 . For now I'm using a combination of QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS to achieve the same effect. And kwin/plasma shouldn't be affected since they are not using it anyway, if you found kwin/plasma is scaled, probably your distro need to compile kwin/plasma against Qt 5.6 to make some qt5.6 compile time specific check work. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 361114] Map-window with OSM - scroll-wheel changes coordinates
https://bugs.kde.org/show_bug.cgi?id=361114 --- Comment #3 from Albrecht Will --- I was wrong it is no bug. I saw the cross as a marker for the coordinates. A pan in the window changes normally the coordinates. To save them it is necessarry to leave the form without saving. Sorry! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 347976] Rotated ps(.gz)
https://bugs.kde.org/show_bug.cgi?id=347976 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #2 from Luigi Toscano --- Evince, after uncompressing the gz file (which can't be open directly) behaves the same, but it uses libspectre like Okular. gv, which uses ghostscript directly, also shows the document upside-down. But ps2pdf belongs to ghostscript too, so maybe there is a flag somewhere which is not used; anyway, it is likely that it could be fixed in libspectre. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9
https://bugs.kde.org/show_bug.cgi?id=362805 --- Comment #14 from Gabriel C --- Allen , this commit : https://quickgit.kde.org/?p=kwallet.git&a=commitdiff&h=0d56c68d7a2204a987a5255096d004d5a696c0e5&hp=87e774825b779ba846315a8b2ffe6479dd9f9814 is not really right.. It does not matter how close one will look at it right now you get BIG ENDIAN algo on LITTLE ENDIAN becuase you are missing to include the header file.. the build has now again lots : warning: "Q_BIG_ENDIAN" is not defined [-Wundef] #if Q_BYTE_ORDER == Q_BIG_ENDIAN ^ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362105] Taskbar options 'autohide'/'windows can cover' not functional
https://bugs.kde.org/show_bug.cgi?id=362105 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #7 from Darin Miller --- My 5.6.3 in Kubuntu (plasma staging ppa) also suffers from autohide/window can cover issue. Removing/re-adding fresh panel has same behvior. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9
https://bugs.kde.org/show_bug.cgi?id=362805 --- Comment #15 from Allen Winter --- that's exactly what I was trying to fix that got us into this mess in the first place. The code is now rolled-back to what it was before I messed with it. well, except for a new comment. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] New: [Frameworks] Wrong render resolution, possibly caused by KDE 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Bug ID: 362856 Summary: [Frameworks] Wrong render resolution, possibly caused by KDE 5 "Scale Display" Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ahyan...@gmail.com KDE 5 includes a new feature, "scale display", for better support for high resolution screens. To enable it, go to settings > Display and Monitor > Display Configuration > Scale Display. I use a 4K screen and I enabled 1.5x scale display. I noticed that all PDFs are rendered in a way that looks extremely bad. A closer look reveals that the PDF is somehow rendered in a way, so that the rendered bitmap consists of 2x2 regions of the same color. In other words, Okular rendered PDFs with 1/2 of actual resolution. I tried to dive into the source code. Apparently, the render resolution is decided then sent to the PDF module via a PixmapRequest. Therefore, I guess this is not only a PDF problem, but a global one, hence the general component instead of PDF backend in this bug report. The geometry sent in PixmapRequest comes from uncroppedWidth() & uncroppedHeight(), which in turn come from m_uncroppedGeometry. The calculation of m_uncroppedGeometry looks somewhat magical, which is where I stop looking at the code and decide to write a bug report instead... The KDE5 Scale display feature is the most possible cause of this problem. However, I'll happily give you more information if that's needed for diagnosing this bug. Reproducible: Always Steps to Reproduce: 1. Enable KDE 5 scale display. 2. Open Okular, open a PDF. 3. Look at how text is rendered (other things are also affected, but text is more important and ubiquitous) Actual Results: Okular renders at half of actual resolution, then scale the result, producing poor results. Expected Results: Okular renders at actual resolution. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it Summary|[Frameworks] Wrong render |[Frameworks] Wrong render |resolution, possibly caused |resolution, possibly caused |by KDE 5 "Scale Display"|by Plasma 5 "Scale Display" --- Comment #1 from Luigi Toscano --- You set [Frameworks] in the topic, is this the Frameworks version of Okular? What happens with the supported version (kdelibs4)? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 362253] git master: deleting bottommost video track leaves next higher track with opaque/transparent button
https://bugs.kde.org/show_bug.cgi?id=362253 --- Comment #2 from wegwerf-1-...@gmx.de --- Jean-Baptiste, thank you very much, that fixes this glitch. I also tried deleting video tracks until there was only one left and it was correctly disabled. But ... I've found another one this way: after deleting the last video track and then adding a new video track, you end up with the opaque/transparent button again... :) -- You are receiving this mail because: You are watching all bug changes.
