[krita] [Bug 386476] First mouse click after drawing with pen is ignored when using Pointer Input API

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=386476

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
reminds me of https://bugs.kde.org/show_bug.cgi?id=387807 ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 387807] First brush stamp is 100% opaque if some pop-up is open

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=387807

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Severity|wishlist|normal
 CC||b...@valdyas.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387822] New: Don't make the updates

[ruiamar]

https://bugs.kde.org/show_bug.cgi?id=387822

Bug ID: 387822
   Summary: Don't make the updates
   Product: Discover
   Version: 5.11.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: rui...@gmail.com
  Target Milestone: ---

Hi guys

Don't make the updates shown in the tray. The number doesn't correspond. I make
update enter pw and than all the apps disappeared and the icon in the tray
stays. I try to make the updates with Muon and with Synaptic, but they said
that another package manager is running and have to wait.

Anybody can help?
Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387821] Face Recognition and Finding crashs after reaching 50%

[Gerome Meyer]

https://bugs.kde.org/show_bug.cgi?id=387821

Gerome Meyer  changed:

   What|Removed |Added

   Keywords||reproducible

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387821] New: Face Recognition and Finding crashs after reaching 50%

[Gerome Meyer]

https://bugs.kde.org/show_bug.cgi?id=387821

Bug ID: 387821
   Summary: Face Recognition and Finding crashs after reaching 50%
   Product: digikam
   Version: 5.8.0
  Platform: Homebrew (Mac OS X)
OS: OS X
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: bte...@gmail.com
  Target Milestone: ---

On MAC and Windows 10 I have Problems with the Face Detection and Management
System...

I have checked "Lazy Sync" on both platforms, but in Windows it changes the
file immediately...
(Because of that and the "dont reacting" after every change I made, I cannot
really use DigiKam in Windows)

On MAC it works with that option but it crashes everytime when I want to find
or recognize new faces...

I want to see and send a crash log but I cannot find any...

Thanks in Advance!

Gerome

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 387820] New: KConfigGui misbehave at runtime when link time optimizations are enabled

[Emmanuel Lepage Vallée]

https://bugs.kde.org/show_bug.cgi?id=387820

Bug ID: 387820
   Summary: KConfigGui misbehave at runtime when link time
optimizations are enabled
   Product: frameworks-kconfig
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: elv1...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

## Context

In the past few months, I have been fixing all frameworks to support static
linking, link time optimizations and profile guided optimizations. So far the
patches are a little crude and are not in mergeable shape. Since yesterday I
cleaned up a few of them to begin the upstreaming process. There's already an
elv13/fix_static branch for 2 frameworks to discuss the changes. LTO and static
mode enables KDE apps to be built in a single binary that's about ~10mb for
most applications, 20mb for big ones due to the assets, making it small enough
for even low end mobile devices. It's also starting much faster thanks to the
PGOs.

Most frameworks "work" after some boring build system patches such as fixing
common "there is a cmake macro/variable for that, don't write your own code"
type of bugs. There's also the need to make QtTest optional everywhere to avoid
having hundreds of gigabytes worth of tests being built (and it takes a
long time to link). However some frameworks are really broken such as the
ones with plugins and those abusing of undefined behavior or static
initialization behavior, such as KConfigGui.

## The bug

This warning is hit and kcolorsheme fail to load, rendering all applications
black on black (invalid QColor).

 372 case QMetaType::QColor:
 373 case QMetaType::QFont:
 374 qWarning() << "KConfigGroup::readEntry was passed GUI type '"
 375<< aDefault.typeName()
 376<< "' but KConfigGui isn't linked! If it is linked to
your program, "
 377"this is a platform bug. Please inform the KDE
developers";
 378 break;

This is due to several C++ broken features used together.

1) The visitor KConfig uses to have types provided by KConfigGui and not
KConfigCore is using static initialization in the form of:

193 static int initKConfigGroupGui()
194 {
195 _kde_internal_KConfigGroupGui.readEntryGui = readEntryGui;
196 _kde_internal_KConfigGroupGui.writeEntryGui = writeEntryGui;
197 return 42;  // because 42 is nicer than 1 or 0
198 }
199 
200 #ifdef Q_CONSTRUCTOR_FUNCTION
201 Q_CONSTRUCTOR_FUNCTION(initKConfigGroupGui)
202 #else
203 static int dummyKConfigGroupGui = initKConfigGroupGui();
204 #endif

In a CPP file. This is problematic for several reasons:

1) Static initialization order is undefined behavior and changes from compilers
to compilers and the level of optimizations used. Having fixed "most" common
scenarios with "most" common compilers does not make it predictable. In this
case it isn't called at all (and this is actually valid, not a bug due to point
1, 2 and 3 being combined)

2) This is implemented as a `static` variable in a `cpp` file. Static elements
in a compilation units are never exported (as defined in the C standard). Even
adding __attribute(used), volatile or an EXPORT macro in front wont export it.
The compiler is free to apply dead code elimination on these variables if it
thinks they are unused or used in UB ways only.

3) The macro is in a cpp file with no header and no exported symbols at all.
The link time optimizer uses a reacheability tree purge unused compilation
units and sections. There is nothing at all pointing to this CU, it's
eliminated from the final executable in GCC and probably all other compilers.

## Is it a compiler bug?

No. It is a certain interpretation of the standard where GCC takes some extra
liberty to purge code even if it does "something". It probably fail to resolve
that the code actually affects static initialization of other CUs. Given that's
undefined anyway, then so be it.

## How can it be fixed

My crude hack is to put `int dummyKConfigGroupGui` in a dummy class and
exporting it then print dummyKConfigGroupGui from main.cpp. It fixes the
framework and applications are no longer black on black. Obviously it's a bad
hack.

The proper way to fix this would be to share createColorEntry in a private
KConfigGui header and turn the int into a `static std::atomic_flag
KCongigGui::init_flag {ATOMIC_FLAG_INIT};`. Then, in KConfigSkeleton
constructor, check the flag and initialize it if it's not already initialized.

This would provide an internal reachability path for `dummyKConfigGroupGui`
from the outside of `src/gui/kconfiggroupgui.cpp` and avoid it from being
dead-code-eliminated by the compiler.

## tl;dr

Q_CONSTRUCTOR_FUNCTION can't be used in a .cpp file that 

[dolphin] [Bug 387809] Scrolling while renaming file doesn't scroll renaming textbox

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387809

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 378786 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 378786] inline rename: scrolling causes rename of wrong file

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=378786

Nate Graham  changed:

   What|Removed |Added

 CC||linus.kardell+kdebugs@gmail
   ||.com

--- Comment #7 from Nate Graham  ---
*** Bug 387809 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387814] KWin does not focus windows when they are moved with alt-mouse

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=387814

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Martin Flöser  ---
It's exactly like Ivan says.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387812] [X11 and Wayland] KWin remembers window maximized state across program launches, but not tiled state

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=387812

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Flöser  ---


*** This bug has been marked as a duplicate of bug 325566 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 325566] KWin should export the tiling state for clients which should restore either tiling or the pre-tiled size

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=325566

Martin Flöser  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #5 from Martin Flöser  ---
*** Bug 387812 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387789] Discover crashed during search with Flatpak backend installed

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387789

--- Comment #5 from Nate Graham  ---
I managed to hit this again by doing the following:

1. Search for "battle of wesnoth"
2. Click on the top entry (from Flatpak)
3. Go back and click on the duplicate entry (from Ubuntu packaging, since the
appstream ID differs)
3. Delete "of wesnoth" from the search query
4. Start typing "tanks" (intending to make the search query into "Battle tanks"

Discover crashes with this backtrace before I can finish typing the word
"Tanks". Here's the backtrace. Not much better even with the extra dev
packages, sorry...

#6  0x562a0a50bcd0 in  ()
#7  0x7f09f9791b4d in QObjectData::dynamicMetaObject() const () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f09f976ea39 in QMetaObject::cast(QObject const*) const () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f09fd0d68bf in  () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#10 0x7f09f976597c in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f09fad654a8 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f09fc7b9265 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f09fc7c4f3a in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7f09fc7c52c5 in QQuickItem::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x7f09fad6546c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f09fc7b9265 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#21 0x7f09fc7c4f3a in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#22 0x7f09fc7c52c5 in QQuickItem::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#23 0x7f09fad6546c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f09fc7b9265 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#27 0x7f09fc7c4f3a in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#28 0x7f09fc7c52c5 in QQuickItem::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#29 0x7f09fad6546c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#31 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f09fc7b9265 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#33 0x7f09fc7c4f3a in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#34 0x7f09fc7c52c5 in QQuickItem::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#35 0x7f09fad6546c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#37 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x7f09fc7d65a8 in QQuickWindow::sendEvent(QQuickItem*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#39 0x7f09fc7d68bf in QQuickWindow::keyReleaseEvent(QKeyEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#40 0x7f09fa5b5d35 in QWindow::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#41 0x7f09fc7ddd05 in QQuickWindow::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#42 0x7f09fad6546c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#43 0x7f09fad6cd34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#44 0x7f09f9765de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

[Discover] [Bug 387819] New: Screenshot pop-up has an extra margin on the side or top if window dimensions aren't just right

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387819

Bug ID: 387819
   Summary: Screenshot pop-up has an extra margin on the side or
top if window dimensions aren't just right
   Product: Discover
   Version: 5.11.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Created attachment 109330
  --> https://bugs.kde.org/attachment.cgi?id=109330=edit
Extra margin on side and top when window is very wide or somewhat tall

When the screenshot pop-up is open, if the window dimensions aren't exactly
right, there is an extra margin on either the side or the top. The screen
recording I've attached illustrates the problem better than I can explain it.

This is pretty easy to see if the window is taller than it is wide, since most
screenshots are in the landscape orientation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 387779] Allow reload to open previously opened file

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387779

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 387762] Keyboard shortcut for Create Text file

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387762

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 385040] Discover crashes in QQuickItem::isVisible() when attempting to go to home page

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=385040

--- Comment #1 from Nate Graham  ---
I hit this once tonight while trying to reproduce
https://bugs.kde.org/show_bug.cgi?id=387789 by repeatedly searching for things.
At one point it sent me back to the home page and crashed. The backtrace was
identical to what's already below.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 386347] Discover crashes in QCoreApplication::notifyInternal2() while searching

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=386347

--- Comment #3 from Nate Graham  ---
I can reproduce this one fairly frequently when I repeatedly search for things,
click on them, and start a new search.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387818] New: Discover can fairly easily be made to hang forever after repeatedly searching with the Flatpak backend installed

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387818

Bug ID: 387818
   Summary: Discover can fairly easily be made to hang forever
after repeatedly searching with the Flatpak backend
installed
   Product: Discover
   Version: 5.11.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Created attachment 109329
  --> https://bugs.kde.org/attachment.cgi?id=109329=edit
Full console output, including backtrace

I can get Discover to hang forever pretty reliably by doing the following:
1. Install the Flatpak backend
2. Repeatedly search, clear the search, and start another search using the
following terms: "Lollypop" "GIMP" "Endless Sky" "HexChat" "Blender"

After enough of this, Discover will permanently hang while fetching results.
The backtrace always shows the following, or something very similar:

(gdb) bt
#0  0x734cb9f9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x73bc68c5 in QBasicMutex::lockInternal() ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x73de3fc0 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x73de0193 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x73de0838 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fff83915d4c in  () at
/usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0
#6  0x73de2f92 in QObject::~QObject() ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x769f5cb9 in ResultsStream::~ResultsStream() ()
at /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
#8  0x73ddc470 in QObject::event(QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x753ac46c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x753b3d34 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x73dacde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x73daf55d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x73e05e53 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fffede77fb7 in g_main_context_dispatch ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fffede781f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7fffede7827c in g_main_context_iteration ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x73e0547f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x73daae3a in
QEventLoop::exec(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x73db3da4 in QCoreApplication::exec() ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x55566c38 in  ()
#21 0x733de1c1 in __libc_start_main (main=
0x55566360, argc=1, argv=0x7fffdef8, init=,
fini=, rtld_fini=, stack_end=0x7fffdee8) at
../csu/libc-start.c:308
#22 0x55566e1a in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387817] New: Discover crashes when repeatedly searching for different things with the Flatpak backend installed

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387817

Bug ID: 387817
   Summary: Discover crashes when repeatedly searching for
different things with the Flatpak backend installed
   Product: Discover
   Version: 5.11.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Application: plasma-discover (5.11.4)

Qt Version: 5.9.1
Frameworks Version: 5.40.0
Operating System: Linux 4.13.0-19-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed:

I was trying to reproduce https://bugs.kde.org/show_bug.cgi?id=387789 by
repeatedly searching for "Endless Sky" "Lollypop" and "GIMP" with the Flatpak
backend installed. Instead, I hit this! I can't reproduce it 100% of the time,
but I have now seen it three times when performing the above search spam.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc325541d80 (LWP 15815))]

Thread 17 (Thread 0x7fc2aeffd700 (LWP 15900)):
#0  0x7fc320a6cffd in __GI___libc_read (fd=20, buf=0x7fc2aeffca90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7fc31b468280 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc31b423c4b in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc31b424110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc31b42427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc3213b149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc321356e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc3211763ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc32117b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc32054d7fc in start_thread (arg=0x7fc2aeffd700) at
pthread_create.c:465
#10 0x7fc320a7db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fc2af7fe700 (LWP 15899)):
#0  0x7fc31b4235e4 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc31b42409b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc31b42427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc3213b149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc321356e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc3211763ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc32117b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc32054d7fc in start_thread (arg=0x7fc2af7fe700) at
pthread_create.c:465
#8  0x7fc320a7db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fc2ae7fc700 (LWP 15840)):
#0  0x7fc320a71901 in __GI___poll (fds=0x7fc298001de0, nfds=1,
timeout=119720) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc31b424169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc31b42427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc3213b149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc321356e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc3211763ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc32117b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc32054d7fc in start_thread (arg=0x7fc2ae7fc700) at
pthread_create.c:465
#8  0x7fc320a7db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7fc2c3fff700 (LWP 15831)):
#0  0x7fc32055464b in futex_reltimed_wait_cancelable (private=, reltime=0x7fc2c3ffeb50, expected=0, futex_word=0x5603e7ba7ad0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fc32055464b in __pthread_cond_wait_common (abstime=0x7fc2c3ffec10,
mutex=0x5603e7ba7a80, cond=0x5603e7ba7aa8) at pthread_cond_wait.c:533
#2  0x7fc32055464b in __pthread_cond_timedwait (cond=0x5603e7ba7aa8,
mutex=0x5603e7ba7a80, abstime=0x7fc2c3ffec10) at pthread_cond_wait.c:667
#3  0x7fc32117c588 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc3211777cc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc32117b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc32054d7fc in 

[Discover] [Bug 387718] Add Flathub by default with Flatpak backend

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387718

--- Comment #12 from Nate Graham  ---
Distro bug reports:
- Ubuntu:  
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1737645
- Fedora:   https://bugzilla.redhat.com/show_bug.cgi?id=1524756
- Manjaro:  https://bugs.manjaro.org/#ticket/zoom/17870
- openSUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1072285

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387816] New: Screenshot pop-up should allow navigation between pictures when there are more than one

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387816

Bug ID: 387816
   Summary: Screenshot pop-up should allow navigation between
pictures when there are more than one
   Product: Discover
   Version: 5.11.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

When you click on a screenshot, it opens in a pop-up. If there are multiple
screenshots, there's no way to navigate between them from the pop-up. You need
to close it and open it again for the next one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387815] New: Screenshot popup lacks close button

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387815

Bug ID: 387815
   Summary: Screenshot popup lacks close button
   Product: Discover
   Version: 5.11.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

When you click on a screenshot, it opens in a pop-up that lacks any visible
means of closing it. It should have a close button in the corner or something.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387814] KWin does not focus windows when they are moved with alt-mouse

[Ivan S]

https://bugs.kde.org/show_bug.cgi?id=387814

Ivan S  changed:

   What|Removed |Added

 CC||northivanas...@gmail.com

--- Comment #1 from Ivan S  ---
Seems to me that the whole purpose of alt-click is to move a window w/o
focusing it.
Recommend change to resolved-invalid.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 387750] TV frame rate too low

[Mauro Carvalho Chehab]

https://bugs.kde.org/show_bug.cgi?id=387750

--- Comment #6 from Mauro Carvalho Chehab  ---
(In reply to nolli111 from comment #5)
> My GPU is nVIDIA GTX1070

Ok. You should then be sure that libVLC will use GPU for video codec.
This link could be helpful:
   https://wiki.videolan.org/VLC_GPU_Decoding/

You'll likely need to install some Ubuntu packages (if you didn't yet), in
order for video accel to happen, using vdpau. You'll need to install them with
something like:
   $ sudo apt install mesa-vdpau-drivers vdpau-driver-all

VLC version 2.2 and upper should use it automatically. Ubuntu 17.10 comes with
vlc 3.0-git. So, it should automatically detect it.

Eventually, you might need to install the nvidia proprietary driver.
personally, I don't like it. I stopped using it (and nvidia boards) years ago,
because it used to be painful to make it work right. So, if I were you, I would
try to make it work with the opensource nouveau driver first.

> 
> Where do I find the logs or how do I retrieve those in Kaffeine that started
> with --debug to provide them to you? I have been working with UBUNTU 17.10
> and have no idea about Linux.

Just call:
$ kaffeine --debug

> In reality, I can not speak English. I write all the texts in German and
> translate them with the Google translator. I then copy these into my emails.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdialog] [Bug 382437] Regression in kdialog causes wrong file extension

[Egor Y . Egorov]

https://bugs.kde.org/show_bug.cgi?id=382437

Egor Y. Egorov  changed:

   What|Removed |Added

 CC||egorov_e...@bk.ru

-- 
You are receiving this mail because:
You are watching all bug changes.

[choqok] [Bug 386436] choqok finds emojis where there are none

[Ivan S]

https://bugs.kde.org/show_bug.cgi?id=386436

--- Comment #3 from Ivan S  ---
This is due to Choqok obeying KDE's emoji detection patterns; D: is a pattern
recognized as sadface.
This should be trivial to fix - another thing to bring up which would also be
fixed by this bug is that patterns should be sent to Twitter as the special
unicode characters for emoticons - :D vs .

-- 
You are receiving this mail because:
You are watching all bug changes.

[choqok] [Bug 386436] choqok finds emojis where there are none

[Ivan S]

https://bugs.kde.org/show_bug.cgi?id=386436

Ivan S  changed:

   What|Removed |Added

 CC||northivanas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387814] New: KWin does not focus windows when they are moved with alt-mouse

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387814

Bug ID: 387814
   Summary: KWin does not focus windows when they are moved with
alt-mouse
   Product: kwin
   Version: 5.11.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@happyjack.org
  Target Milestone: ---

To reproduce, have two windows open.  Focus one of the windows.  Move the mouse
over the other window, and move that window by holding alt and dragging with
the mouse.

My expectation is that the window will be focused, but it is not.  I'm using
focus follows mouse with a delayed raise, so I find it confusing that even
though my mouse is over the window for an extended period of time, the window
is not raised.

This also happens with click to focus.  I suppose it can be interpreted that
the click is not making it through to the window so it shouldn't be raised in
that case, but it feels to me that the window is being interacted with, and
ought to receive focus at that point.  As a supporting point, clicking on the
titlebar to move *does* raise the window, so the current behavior seems to
special-case the alt-pointer method of moving windows.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch

[Bruno Baumgartner]

https://bugs.kde.org/show_bug.cgi?id=381975

Bruno Baumgartner  changed:

   What|Removed |Added

 CC||m...@wossc.org

--- Comment #3 from Bruno Baumgartner  ---
Kubuntu 14.04-5
I do not have at all the «Always on Top» feature. But it is very necessary now
since I have become a professional Desktop Publisher. It would make live much
easier.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387718] Add Flathub by default with Flatpak backend

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387718

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REOPENED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kruler] [Bug 385122] Color picker feature is not available

[Bruno Baumgartner]

https://bugs.kde.org/show_bug.cgi?id=385122

Bruno Baumgartner  changed:

   What|Removed |Added

 CC||m...@wossc.org

--- Comment #1 from Bruno Baumgartner  ---
I do strongly support this, I am missing it as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387718] Add Flathub by default with Flatpak backend

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387718

--- Comment #11 from Nate Graham  ---
Sorry, wasn't trying to nitpick. I don't think it's like your LibreOffice
example; there are plenty of people who would use a computer without
libreoffice. But what's the use case for someone to install the Flatpak backend
without Flathub?

Still, if this has to be a downstream matter, that's fine. I'll make my case to
the distros.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387041] "Reason" and "Change Log" are frequently identical

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387041

--- Comment #7 from Nate Graham  ---
Conclusion upstream is that we'll need to do this ourselves. I'll try to put
something together.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387812] [X11 and Wayland] KWin remembers window maximized state across program launches, but not tiled state

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387812

Nate Graham  changed:

   What|Removed |Added

Summary|[x11] KWin remembers window |[X11 and Wayland] KWin
   |maximized state across  |remembers window maximized
   |program launches, but not   |state across program
   |tiled state |launches, but not tiled
   ||state
  Flags||Wayland+, X11+

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmix] [Bug 387813] New: error

[Ari Santana]

https://bugs.kde.org/show_bug.cgi?id=387813

Bug ID: 387813
   Summary: error
   Product: kmix
   Version: 4.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: ea8...@gmail.com
  Target Milestone: ---

Application: kmix (4.5)
KDE Platform Version: 4.14.32
Qt Version: 4.8.7
Operating System: Linux 4.9.68-wifislax64 x86_64

-- Information about the crash:
- What I was doing when the application crashed:
Cambiando de aplicacion en el panel, siento no poder aportar mas

-- Backtrace:
Application: KMix (kmix), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6bb8e36780 (LWP 2466))]

Thread 2 (Thread 0x7f6b8d26d700 (LWP 2547)):
#0  0x7ffd0ffa29dd in clock_gettime ()
#1  0x7f6bb5990386 in clock_gettime () at /lib64/libc.so.6
#2  0x7f6bb7732645 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#3  0x7f6bb780fe55 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#4  0x7f6bb780e7dc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#5  0x7f6bb780e885 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#6  0x7f6bb2098f8d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f6bb2099893 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f6bb2099a6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f6bb780f0ce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#10 0x7f6bb77df5d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#11 0x7f6bb77df8e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#12 0x7f6bb76d8c39 in QThread::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#13 0x7f6bb77c0733 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#14 0x7f6bb76db3bc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#15 0x7f6bb743a684 in start_thread () at /lib64/libpthread.so.0
#16 0x7f6bb5981eed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6bb8e36780 (LWP 2466)):
[KCrash Handler]
#6  0x7f6bb8012684 in  () at /usr/lib64/libkdecore.so.5
#7  0x7f6bb800a8f4 in KSharedDataCache::find(QString const&, QByteArray*)
const () at /usr/lib64/libkdecore.so.5
#8  0x7f6bb87f468e in  () at /usr/lib64/libkdeui.so.5
#9  0x7f6bb87f4a69 in KIconLoader::loadIcon(QString const&,
KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () at
/usr/lib64/libkdeui.so.5
#10 0x7f6ba1fbb48c in  () at /usr/lib64/libkdeinit4_kmix.so
#11 0x7f6ba1fbedd9 in  () at /usr/lib64/libkdeinit4_kmix.so
#12 0x7f6ba1fbf178 in  () at /usr/lib64/libkdeinit4_kmix.so
#13 0x7f6ba1fbfee4 in  () at /usr/lib64/libkdeinit4_kmix.so
#14 0x7f6ba1fc06d3 in  () at /usr/lib64/libkdeinit4_kmix.so
#15 0x7f6ba1fb6945 in  () at /usr/lib64/libkdeinit4_kmix.so
#16 0x7f6ba1fb2961 in  () at /usr/lib64/libkdeinit4_kmix.so
#17 0x7f6ba1fb84f4 in  () at /usr/lib64/libkdeinit4_kmix.so
#18 0x7f6bb77e8da1 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () at
/usr/lib64/qt/lib/libQtCore.so.4
#19 0x7f6bb77eb156 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at
/usr/lib64/qt/lib/libQtCore.so.4
#20 0x7f6ba1fd8ce3 in  () at /usr/lib64/libkdeinit4_kmix.so
#21 0x7f6ba1f9969b in  () at /usr/lib64/libkdeinit4_kmix.so
#22 0x7f6ba1f99886 in  () at /usr/lib64/libkdeinit4_kmix.so
#23 0x7f6bb77f9921 in QObject::event(QEvent*) () at
/usr/lib64/qt/lib/libQtCore.so.4
#24 0x7f6bb693648c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#25 0x7f6bb693cf5c in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#26 0x7f6bb883f8aa in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#27 0x7f6bb77e0c0d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#28 0x7f6bb77e3e6e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/qt/lib/libQtCore.so.4
#29 0x7f6bb780ef3e in  () at /usr/lib64/qt/lib/libQtCore.so.4
#30 0x7f6bb2099797 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#31 0x7f6bb20999c8 in  () at /usr/lib64/libglib-2.0.so.0
#32 0x7f6bb2099a6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#33 0x7f6bb780f0ae in

[kwin] [Bug 387812] New: [x11] KWin remembers window maximized state across program launches, but not tiled state

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387812

Bug ID: 387812
   Summary: [x11] KWin remembers window maximized state across
program launches, but not tiled state
   Product: kwin
   Version: 5.11.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Plasma & KWin 5.11.4 in Kubuntu 17.10 with KDE Backports PPA


STEPS TO REPRODUCE:
1. Open window any app
2. Maximize its window
3. Close the program
4. Open the program again
[observe that the window is opened in the maximized state, just as it was when
you closed it]
5. Tile the window to a corner or edge
6. Close the program
7. Open the program again


EXPECTED RESULTS:
The window is re-opened in the tiled state that it was in when it was closed


ACTUAL RESULTS:
The window opens with the same dimensions that it had before, but not in the
same location or in the tiled state.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 387686] valgrind-3.13.0 tests on Gentoo fail with glibc-2.26 (work with glibc-2.25).

[Austin English]

https://bugs.kde.org/show_bug.cgi?id=387686

Austin English  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #2 from Austin English  ---
Closing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368097] Kdevelop5 contains GPL-3.0 files

[Sven Brauch]

https://bugs.kde.org/show_bug.cgi?id=368097

--- Comment #3 from Sven Brauch  ---
In my eyes this section of the GPL FAQ is relatively questionable. Just because
it's part of the FAQ doesn't mean it's what law will actually do. According to
my recent research about a similar issue, a GPL plugin "infecting" its base
application to require it being GPL as well has never been tested in court, and
the typical lawyer is very sceptical that this concept would withstand a trial.

To be honest, I think these whole debates are causing only headaches and are
not useful for anything ... I would look into this if it is really required,
but if nobody forces me to I will just leave it at the status quo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387718] Add Flathub by default with Flatpak backend

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=387718

--- Comment #10 from Aleix Pol  ---
Well, what we can't do is modify the user's system just because.
Also please don't nitpick on my wording when I'm trying to convey an idea.

Adding it automatically would be something like "install libreoffice
automatically on the first Discover run, because it's the only stable office
suit in linux".

We won't go modifying stuff because the distribution didn't bother. Instead, we
should advocate for a vision on how users will adopt their software on their
systems while making it easy for users of distros that didn't care to have the
minimal features at reach.

I'm open to adding actions, buttons, notifications but I don't consider
acceptable to add a source automatically.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 384925] Window decoration missing

[Henrik Fehlauer]

https://bugs.kde.org/show_bug.cgi?id=384925

--- Comment #10 from Henrik Fehlauer  ---
> This issue occurs all the time in my system using Cinnamon.
Not sure what you mean with "all the time", without specifying specific steps
this is hard to follow.

As for Cinnamon, their window manager is apparently called "cinnamon" nowadays.
"compiz --replace" and "cinnamon --replace" give exactly the same behaviour as
for "marco", so please ask over at Cinnamon about this bug (which might even
have some relation to marco?). Same thing for "muffin".

Regarding GNOME, Cinnamon is a former fork of an older version of that, which
might explain was you saw. However, with GNOME 3 this problem is not present
for me when testing on Ubuntu 16.04.3.

Testing with Kate's fullscreen mode, you can observe exactly the same problem.
I think it is best if the window manager developers of the affected desktop
environments could comment at this point. It might turn out that KDE Frameworks
is handling things incorrectly or works only for some window managers, but
let's wait and see before we blindly open a new bug for this. I suspect they
are missing features we expect them to have. In any case this is not a problem
we can solve from Gwenview's side.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 373178] Blurry scaling on HiDPI

[Henrik Fehlauer]

https://bugs.kde.org/show_bug.cgi?id=373178

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||rk...@lab12.net

--- Comment #17 from Henrik Fehlauer  ---
The fix won't be in 17.12, the patches are not even ready yet. If you are
adventurous, you could compile Gwenview by yourself and apply
https://phabricator.kde.org/D7581 and https://phabricator.kde.org/D9078.

Also note that this does not relate to DigiKam at all. Please search for or
file a separate bug for that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 387811] New: Curly and colored underlines

[Egmont Koblinger]

https://bugs.kde.org/show_bug.cgi?id=387811

Bug ID: 387811
   Summary: Curly and colored underlines
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: egm...@gmail.com
  Target Milestone: ---

This is originally a feature of Kitty [1], now also adopted by VTE (GNOME
Terminal and friends). Technically two separate features, but they mostly make
sense together, e.g. for spell checking.

Apparently vim and neovim have already / are about to support these, see e.g.
vim undercurl [2], vim color [3], neovim [4].

---

The new SGR 4:3 (\e[4:3m) attribute, strictly with a colon as separator, was
introduced to start a curly underline.

In the mean time, 4:0, 4:1 and 4:2 were also added as aliases for the standard
24 (turn off all kinds of underlining), 4 (single underline) and 21 (double
underline), respectively.

At some point in the future, probably 4:4 and 4:5 could also stand for dotted
and dashed underlines in some order (these are the five types of underlining
supported by HTML/CSS).

---

The new SGR 58 and 59 sequences specify the color of the underline, following
the pattern of 38 and 39. That is, 58;5;idx for an entry of the 256-color
palette, or 58;2;r;g;b for direct RGB. There's no shortcut notation for the
first 16 entries (corresponding to SGR 30-37 and 90-97), use the 256-color mode
with indices of 0-15 instead.

59 reverts to the default, that is, the underline's color auto-following the
text color.

In case you're short of bits, I believe it's okay to drop some precision, e.g.
store only 4 bits per color channel. We were also considering this in the VTE
bug [5].

[1]
https://github.com/kovidgoyal/kitty/blob/master/protocol-extensions.asciidoc
[2] https://github.com/vim/vim/issues/1306
[3] https://github.com/vim/vim/pull/2405
[4] https://github.com/neovim/neovim/issues/7479
[5] https://bugzilla.gnome.org/show_bug.cgi?id=721761

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 380269] [PATCH] No multithreading in macOS Sierra (10.12)

[Louis Brunner]

https://bugs.kde.org/show_bug.cgi?id=380269

--- Comment #6 from Louis Brunner  ---
Rhys,

No problem, here are the results before the patch (but with
https://bugs.kde.org/show_bug.cgi?id=385279 applied):
== 655 tests, 335 stderr failures, 85 stdout failures, 8 stderrB failures, 8
stdoutB failures, 31 post failures ==

And after:
== 655 tests, 322 stderr failures, 74 stdout failures, 8 stderrB failures, 8
stdoutB failures, 31 post failures ==

Note that some tests block the test runner in both case (mcwatchpoints) and
some tests block after the patch (pselect_alarm and pth_term_signal). This is
due to the tests previously crashing because of pthread, and now some issues
with signals is preventing them to complete.

Here is the difference between the failures:
$ diff tests_pre.txt tests_post.txt
49,50d48
< memcheck/tests/err_disable3  (stderr)
< memcheck/tests/err_disable4  (stderr)
99d96
< memcheck/tests/threadname(stderr)
150,151d146
< callgrind/tests/threads-use  (stderr)
< callgrind/tests/threads  (stderr)
210,216d204
< none/tests/pselect_alarm (stderr)
< none/tests/pth_2sig  (stderr)
< none/tests/pth_atfork1   (stdout)
< none/tests/pth_atfork1   (stderr)
< none/tests/pth_blockedsig(stdout)
< none/tests/pth_blockedsig(stderr)
< none/tests/pth_cancel1   (stdout)
219,221d206
< none/tests/pth_cvsimple  (stdout)
< none/tests/pth_cvsimple  (stderr)
< none/tests/pth_exit  (stderr)
224,225d208
< none/tests/pth_stackalign(stdout)
< none/tests/pth_stackalign(stderr)
229d211
< none/tests/sigsusp   (stderr)
234d215
< none/tests/threaded-fork (stdout)
330d310
< helgrind/tests/pth_destroy_cond  (stdout)
342d321
< helgrind/tests/tc07_hbl1 (stdout)
344d322
< helgrind/tests/tc08_hbl2 (stdout)
348d325
< helgrind/tests/tc11_XCHG (stdout)
358d334
< helgrind/tests/tc21_pthonce  (stdout)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387744] Plasma Discover doesn't honour pinned packages

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387744

--- Comment #4 from tomhut...@aim.com ---
I have apt pinning still intact:

$ cat /etc/apt/preferences.d/firefox.pref
Package: *
Pin: release o=Debian,a=buster
Pin-Priority: 900

Package: firefox
Pin: release o=Debian,a=sid
Pin-Priority: 1000


Now I disabled the sid repo:

$ cat /etc/apt/sources.list.d/sid.list
#deb http://debian.mirror.iphh.net/debian/ sid contrib non-free main

$ apt-get update
$ apt-get -s dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ pkcon get-updates
Getting updates   [=]
Loading cache [=]
Finished  [=]
There are no updates available at this time.

Then I reenabled the sid repo:

$ cat /etc/apt/sources.list.d/sid.list
deb http://debian.mirror.iphh.net/debian/ sid contrib non-free main

$ apt-get update
$ apt-get -s dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ pkcon get-updates  
Getting updates   [=] 
Loading cache [=] 
Finished  [=] 
Normal  apparmor-2.11.1-4.amd64 (debian-unstable-main) 
user-space parser utility for AppArmor
Normal  apparmor-notify-2.11.1-4.all (debian-unstable-main)
AppArmor notification system
Normal  apparmor-profiles-2.11.1-4.all (debian-unstable-main)  
profiles for AppArmor Security policies
Normal  at-spi2-core-2.26.2-2.amd64 (debian-unstable-main) 
Assistive Technology Service Provider Interface (dbus core)


$pkcon get-updates | grep "^Normal" | wc -l
134

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 387692] Seg fault when opening CMake file as project

[Roman Gilg]

https://bugs.kde.org/show_bug.cgi?id=387692

Roman Gilg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #5 from Roman Gilg  ---
The change back to llvm-4.0 solved the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 387657] Folders panel does not auto scroll vertically

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387657

pawel.wa...@o2.pl changed:

   What|Removed |Added

 CC||pawel.wa...@o2.pl

--- Comment #5 from pawel.wa...@o2.pl ---
I can confirm the same issue with Dolphin 17.08.3 on ArchLinux.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KDb] [Bug 387798] Referencing column aliases in SELECT and WHERE does not work in PostgreSQL

[Jarosław Staniek]

https://bugs.kde.org/show_bug.cgi?id=387798

--- Comment #4 from Jarosław Staniek  ---
Dev info for the record in KDb 9f68694395b (master):

in selectStatementInternal() we are kind of using the SOLUTION #2, see the code
where s_where_sub is set (it is computed without aliases).

KEXI visual query designer offers setting aliases for fields but not for tables
so WHERE section can't be controlled from this view. Relations between  are
properly generated.

So the problem would be mostly reproducible in KDb API and Kexi SQL view.

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[now-im]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #7 from now-im  ---
Alright. Ping me if any further info is needed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[now-im]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #6 from now-im  ---
Alright. Ping me if you need any further info. I appreciate your work. KDE
badly needs audio and video player based on latest codecs and qt5.

From: Matthieu Gallien 
Sent: Tuesday, December 12, 2017 3:42:24 AM
To: now.im@gmail.com
Subject: [elisa] [Bug 387772] Stuck at configuring

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #5 from Matthieu Gallien  ---
I believe the package has all needed dependencies either directly or
indirectly. I believe the problem may be that scanning is taking a very long
time to provide user visible feedback. Let me check that and see what I can do.

--
You are receiving this mail because:
You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[Matthieu Gallien]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #5 from Matthieu Gallien  ---
I believe the package has all needed dependencies either directly or
indirectly. I believe the problem may be that scanning is taking a very long
time to provide user visible feedback. Let me check that and see what I can do.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 387686] valgrind-3.13.0 tests on Gentoo fail with glibc-2.26 (work with glibc-2.25).

[Austin English]

https://bugs.kde.org/show_bug.cgi?id=387686

Austin English  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Austin English  ---
My fault for not testing git first. This was already fixed, by:
2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626
Author: Mark Wielaard 
Date:   Thu Jun 29 15:26:30 2017 +

memcheck/tests: Use ucontext_t instead of struct ucontext

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387790] When PackageKit and Flatpak backends are both installed, apps present in both are shown twice

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387790

--- Comment #5 from Nate Graham  ---
There's a LOT of upstream work to do here, then...

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[now-im]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #4 from now-im  ---
NO, configuration dialog is showing and I could select my custom path. Has the
arch package lisgted all dependencies correctly?
This is the list:

baloo
kcmutils
qt5-quickcontrols
qt5-quickcontrols2
upnp-player-qt
extra-cmake-modules (make)
kdoctools (make)

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[Matthieu Gallien]

https://bugs.kde.org/show_bug.cgi?id=387772

Matthieu Gallien  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Matthieu Gallien  ---
Thanks for the snapshot.
If I understand correctly, the configuration dialog is not showing when
pressing the button. Is it correct ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[now-im]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #2 from now-im  ---
Created attachment 109327
  --> https://bugs.kde.org/attachment.cgi?id=109327=edit
Image showing the dialog box.

This is where I am stuck. No progress nothing. If I try to drag-drop or
double-click to open a file, nothing happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[elisa] [Bug 387772] Stuck at configuring

[Matthieu Gallien]

https://bugs.kde.org/show_bug.cgi?id=387772

--- Comment #1 from Matthieu Gallien  ---
Thanks for your report.
I am trying to reproduce your situation but I am not sure.
Are you getting some sort of notifications about tracks not being found or just
the spinner ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 387810] New: arm: unhandled instruction: 0xEBAD 0x1AC8

[balaret]

https://bugs.kde.org/show_bug.cgi?id=387810

Bug ID: 387810
   Summary: arm: unhandled instruction: 0xEBAD 0x1AC8
   Product: valgrind
   Version: 3.13.0
  Platform: Android
OS: other
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: bala...@gmail.com
  Target Milestone: ---

This crash happens every time when I touch any part of app's UI:

disInstr(thumb): unhandled instruction: 0xEBAD 0x1AC8
==7003== valgrind: Unrecognised instruction at address 0x60eb69d.
==7003==at 0x60EB69C:
android::InputConsumer::initializeMotionEvent(android::MotionEvent*,
android::InputMessage const*) (in /system/lib/libinput.so)
==7003==by 0x60EB0CF:
android::InputConsumer::consume(android::InputEventFactoryInterface*, bool,
long long, unsigned int*, android::InputEvent**) (in /system/lib/libinput.so)
==7003==by 0x4F4F4AB:
android::NativeInputEventReceiver::consumeEvents(_JNIEnv*, bool, long long,
bool*) (in /system/lib/libandroid_runtime.so)
==7003==by 0x4F4F6C7: android::NativeInputEventReceiver::handleEvent(int,
int, void*) (in /system/lib/libandroid_runtime.so)
==7003==by 0x4FF9F2F: android::Looper::pollInner(int) (in
/system/lib/libutils.so)
==7003==by 0x4FF9C3D: android::Looper::pollOnce(int, int*, int*, void**)
(in /system/lib/libutils.so)
==7003==by 0x4F5B797: android::NativeMessageQueue::pollOnce(_JNIEnv*,
_jobject*, int) (in /system/lib/libandroid_runtime.so)
==7003==by 0x73BEA45D: ??? (in
/data/dalvik-cache/arm/system@framew...@boot.oat)
==7003== Your program just tried to execute an instruction that Valgrind did
not recognise

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 383514] Provide a way to see dependencies (can be well-hidden)

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=383514

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
Actually that was about calculating their sizes, not showing them in the UI.

This is mostly relevant to the PackageKit backend, but I suppose it could be
useful for other backends too; you could see what Flatpak runtimes a package
was going to pull in, for example.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 387809] New: Scrolling while renaming file doesn't scroll renaming textbox

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387809

Bug ID: 387809
   Summary: Scrolling while renaming file doesn't scroll renaming
textbox
   Product: dolphin
   Version: 17.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: linus.kardell+kdeb...@gmail.com
  Target Milestone: ---

If you start renaming a file (e.g. by clicking f2 with it highlighted), and
scroll, the textbox for entering entering does not scroll along with the file
list, instead remaining in the same spot in the window.

I supposed something like this would be required if you scroll enough that the
file you're renaming goes outside the window though, so it's not entirely
avoidable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 387808] New: When session is restored, hidden menubars become visible

[Christopher Neufeld]

https://bugs.kde.org/show_bug.cgi?id=387808

Bug ID: 387808
   Summary: When session is restored, hidden menubars become
visible
   Product: konsole
   Version: 17.08.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: kdeb...@cneufeld.ca
  Target Milestone: ---

I typically have several konsole windows open in my work, opened with
--hide-menubar.  When I log out, and then log in again, the windows are
restored in their previous locations, but the menubars are no longer hidden,
and all have to be hidden by hand after the login.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krusader] [Bug 381905] The key sequence 'Home' is ambiguous

[Toni Asensi Esteve]

https://bugs.kde.org/show_bug.cgi?id=381905

Toni Asensi Esteve  changed:

   What|Removed |Added

 CC||toni.ase...@kdemail.net

--- Comment #5 from Toni Asensi Esteve  ---
> Krusader 2.5.0
> (from the Kubuntu packages)
> Versions of KDE components:
> plasma version 5.9.4
> framework  5.31.0-0ubuntu1

I suppose that you are using Kubuntu 17.04.

> When I try to open a text file for editing (F4 shortcut) and then press Home, 
>  
> I get the following message box: [...]

I tried it, too, but everything went all right.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 387807] New: First brush stamp is 100% opaque if some pop-up is open

[radian]

https://bugs.kde.org/show_bug.cgi?id=387807

Bug ID: 387807
   Summary: First brush stamp is 100% opaque if some pop-up is
open
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: xe...@e1.ru
  Target Milestone: ---

Created attachment 109326
  --> https://bugs.kde.org/attachment.cgi?id=109326=edit
example of wrong first stamps

If there is some pop-up open (brush editor, brush preset list pop-up, tool
options) and you starting to draw on canvas first stamp of the brush will look
like with 100% pressure (see pic).
It's annoying and I feel ~70% of my undos is this thing.

Pop-up pallette seems to lock canvas while it open so clicking on canvas just
hide pallette and doesn't create these stamps. I suggest to do same for brush
editor and brush preset pop-up.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 387657] Folders panel does not auto scroll vertically

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387657

zaqan...@pokemail.net changed:

   What|Removed |Added

 CC||zaqan...@pokemail.net

--- Comment #4 from zaqan...@pokemail.net ---
I can confirm the same. Very annoying.
Arch Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 387806] New: Task bar of secondary screen is empty when there is no primary screen

[Alberto Torres Ruiz]

https://bugs.kde.org/show_bug.cgi?id=387806

Bug ID: 387806
   Summary: Task bar of secondary screen is empty when there is no
primary screen
   Product: plasmashell
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: kungfoo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Have two screens, two taskbars, each with setting "show windows only in current
screen".

Disconnect the primary screen (or in my case, close the laptop lid by mistake).
Reconnect it.

Now the task bar of the secondary screen is empty, but the screen is still full
of windows. Moving them around doesn't fix the problem.

It took me a while to notice there is no active screen in display settings, and
when setting an active screen it works again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387799] Kwin intermittently crashes

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=387799

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Martin Flöser  ---
Crash in proprietary nvidia driver. Please report to NVIDIA.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 348746] Background color in fullscreen mode should be pure black or else somehow user-customizable

[Thomas Meiner]

https://bugs.kde.org/show_bug.cgi?id=348746

--- Comment #9 from Thomas Meiner  ---
This bug isn't fixed since 2015.

Since a few versions, the image background is black. But the surrounding
backgrund still isn't

See the attached images!
I opened the image "red_text.png" in Gwenview 16.12.3 in full screen mode. The
second image shows a shreenshot of Gwenview-full screen mode. 
There you can see the grayish background outside of the image. I shuld be as
back as the image backgrund itself. 
"red_text.png" contains on back at all. Most of it is transparent.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 348746] Background color in fullscreen mode should be pure black or else somehow user-customizable

[Thomas Meiner]

https://bugs.kde.org/show_bug.cgi?id=348746

--- Comment #8 from Thomas Meiner  ---
Created attachment 109325
  --> https://bugs.kde.org/attachment.cgi?id=109325=edit
Screenshot of Gewnview, mith loaded image red_text.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 348746] Background color in fullscreen mode should be pure black or else somehow user-customizable

[Thomas Meiner]

https://bugs.kde.org/show_bug.cgi?id=348746

--- Comment #7 from Thomas Meiner  ---
Created attachment 109324
  --> https://bugs.kde.org/attachment.cgi?id=109324=edit
Image to laod in Gwenview.

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 387656] Error dialog is displayed when enter Dashboard and Conjugations were practiced before

[Hartmut Riesenbeck]

https://bugs.kde.org/show_bug.cgi?id=387656

Hartmut Riesenbeck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/par
   ||ley/c931d920049395f17e84b0e
   ||b3ea7edeb35bdd085
 Resolution|--- |FIXED

--- Comment #1 from Hartmut Riesenbeck  ---
Git commit c931d920049395f17e84b0eb3ea7edeb35bdd085 by Hartmut Riesenbeck.
Committed on 11/12/2017 at 20:13.
Pushed by hriesenbeck into branch 'master'.

[Parley] Fix false error message when entering dashboard

Summary:
When entering dashboard with conjugations as current practice mode, an
error message box is shown when no entries are due for practice. It
says: "The vocabulary document contains no entries that can be used for
the chosen type of practice."
For determining the word count of the collection widgets, the
EntryFilter class is used. A missing test for the showDialg flag was
added in the conjugation entries evaluation.

Reviewers: #kde_edu, apol

Reviewed By: apol

Subscribers: apol

Tags: #kde_edu

Differential Revision: https://phabricator.kde.org/D9246

M  +1-1src/collection/entryfilter.cpp

https://commits.kde.org/parley/c931d920049395f17e84b0eb3ea7edeb35bdd085

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 330192] Unable to open video files in common players (VLC, MPV, etc) over smb://

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=330192

--- Comment #10 from Nate Graham  ---
The above VLC tickets are now resolved in VLC 3.0 (unreleased as of this
writing). 

We now have a workaround for folks needing to access videos on Samba shares
from within a KDE Plasma environment: use VLC 3.0. Potentially unstable nightly
builds of VLC 3.0 can be found at https://nightlies.videolan.org/ until the
formal release of VLC 3.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387805] Multiple additional sort options based on popularity, ratings, and quality

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387805

Nate Graham  changed:

   What|Removed |Added

 Depends on||383518


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=383518
[Bug 383518] Discover should let you change the sort order of app lists
-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 383518] Discover should let you change the sort order of app lists

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=383518

Nate Graham  changed:

   What|Removed |Added

 Blocks||387805


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=387805
[Bug 387805] Multiple additional sort options based on popularity, ratings, and
quality
-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 387805] New: Multiple additional sort options based on popularity, ratings, and quality

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387805

Bug ID: 387805
   Summary: Multiple additional sort options based on popularity,
ratings, and quality
   Product: Discover
   Version: 5.11.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

This idea got a positive reception in the discover-design Telegram room, so I
thought I'd promote it to a feature request.

When browsing and searching, KDE discover should have additional sort options
designed to delight different types of people:

1. Recommended (for people who trust experts)
2. Most popular (current default; for people who believe in the wisdom of
crowds)
3. Overlooked gems (high rated but infrequently downloaded; for people who like
to discover hidden value)
4. Controversial (ratings are all over the map; for people who like to argue)
5. Alphabetical (for people who want "Just The Facts Ma'am" without any
filtering of the data)

The last-used view should be remembered across app launches.


Discover's Current UX implements rough versions of #1 (on the home screen, in a
limited form) and #2 (the browse lists, though the order isn't made clear).
With this, we could actually get rid of the Home screen entirely and have
Discover open to an app list with a sort order determined by a visible UI
control like a dropdown menu or something.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 387366] Energy consumption statistics not available

[wincak]

https://bugs.kde.org/show_bug.cgi?id=387366

--- Comment #4 from wincak  ---
Any progress on the issue? Or a hint as to where to look for an error if it is
not caused by wrong library search path?
I can access some battery history data through UPower D-Bus, so there should be
at least something visible.
I tried building kinfocenter from source and debugging, but it's a bit tricky
since the program built this way doesn't contain all the components (e.g. QML
GUI) and calls system libraries instead of the built ones.
Just a note: it would be nice it there was some building/debugging guide, even
if it was short.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaddressbook] [Bug 387804] New: Create folder in KAddressBook fails

[Ricardo Garos]

https://bugs.kde.org/show_bug.cgi?id=387804

Bug ID: 387804
   Summary: Create folder in KAddressBook fails
   Product: kaddressbook
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: stickytoepa...@outlook.com
CC: to...@kde.org
  Target Milestone: ---

Created attachment 109323
  --> https://bugs.kde.org/attachment.cgi?id=109323=edit
Screenshot of KAddressBook create folder error message.

I've tried to create a subfolder in the Address book (called "Personal
Contacts"), however this gives an error message everytime:

'Could not create address book folder: Unable to append mimetype for collection
new resourceId: 4'

It is possible to Add another 'Address Book', and rename the new entry, however
if you delete something from one of them it also deletes the data in the other
books?

So I want to create a folder instead, however this does not work either.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 348746] Background color in fullscreen mode should be pure black or else somehow user-customizable

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=348746

Nate Graham  changed:

   What|Removed |Added

 CC||rburgstah...@freenet.de

--- Comment #6 from Nate Graham  ---
*** Bug 387801 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 387801] Gwenview - backgrond color not black

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387801

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
I'm a multi-decade-long former Mac user myself. Come on in, the water's fine!
:) IMHO KDE Plasma is rapidly becoming the haven for Apple refugees like us.

*** This bug has been marked as a duplicate of bug 348746 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 348746] Background color in fullscreen mode should be pure black or else somehow user-customizable

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=348746

Nate Graham  changed:

   What|Removed |Added

Summary|Background color in |Background color in
   |fullscreen mode should use  |fullscreen mode should be
   |System Settings > Colors >  |pure black or else somehow
   |Tooltip Background color|user-customizable

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[dherman]

https://bugs.kde.org/show_bug.cgi?id=341143

dherman  changed:

   What|Removed |Added

 CC|dher...@southseattle.edu|

-- 
You are receiving this mail because:
You are watching all bug changes.

[KDb] [Bug 387798] Referencing column aliases in SELECT and WHERE does not work in PostgreSQL

[Jarosław Staniek]

https://bugs.kde.org/show_bug.cgi?id=387798

--- Comment #3 from Jarosław Staniek  ---
> How about being standards compliant, and generating valid SQL?

No implementation is compliant, as someone noted in the stackoverflow thread
even PostgreSQL has deviations for convenience of users. Notable convenience
additions started to appear in our functions:
https://community.kde.org/Kexi/Plugins/Queries/SQL_Functions.

Lack of support described in this thread is rather unfortunate for me as in
practice it's nothing more than inconvenience, if one wants portability to
MySQL and SQLite for example, this standard compliance is a step backward.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 387796] wrong layering of the completion drop down list on Mac

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=387796

RJVB  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D9289

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 387792] Action "Views" exists but does nothing

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=387792

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.8.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/ee0ba776e13968a35556ae
   ||e327a64749c1d0bcfb

--- Comment #1 from Maik Qualmann  ---
Git commit ee0ba776e13968a35556aee327a64749c1d0bcfb by Maik Qualmann.
Committed on 11/12/2017 at 19:20.
Pushed by mqualmann into branch 'master'.

remove imageViewSelectionAction from the KActionCollection
FIXED-IN: 5.8.0

M  +2-1NEWS
M  +1-2app/main/digikamapp.cpp

https://commits.kde.org/digikam/ee0ba776e13968a35556aee327a64749c1d0bcfb

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 387803] New: Plasma crashes when closing a Kwrite file when there are many Kwrite files open

[Ouissal Benameur]

https://bugs.kde.org/show_bug.cgi?id=387803

Bug ID: 387803
   Summary: Plasma crashes when closing a Kwrite file when there
are many Kwrite files open
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ouissalbenam...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.87-18.29-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I tried closing a Kwrite file (right click => close) while a few other Kwrites
were open.
It crashes also when trying to close multiple Kwrite files at once, but this
time I only closed one, that's why I didn't mark it as a duplicate.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05fc7d1900 (LWP 2783))]

Thread 7 (Thread 0x7f0531fe5700 (LWP 3173)):
#0  0x7f05f23ab8f0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f05f23ac230 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f05f23ac42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f05f65f133b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f052c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f05f659efeb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0531fe4c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f05f63d9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f053340e8f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f05f63de9e9 in QThreadPrivate::start(void*) (arg=0x58f0450) at
thread/qthread_unix.cpp:341
#8  0x7f05f54ed744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f05f5cecaad in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f054410b700 (LWP 3011)):
#0  0x7f05f5ce420d in poll () at /lib64/libc.so.6
#1  0x7f05f23ac314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f05f23ac42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f05f65f133b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f053c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f05f659efeb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f054410ac70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f05f63d9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f05fa26a632 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f05f63de9e9 in QThreadPrivate::start(void*) (arg=0x2d50bd0) at
thread/qthread_unix.cpp:341
#8  0x7f05f54ed744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f05f5cecaad in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f05d2da6700 (LWP 2910)):
#0  0x7f05f54f20bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f05fbeb193b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f05fbeb1969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f05f54ed744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f05f5cecaad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f05d8a7a700 (LWP 2897)):
#0  0x7f05f65f1840 in timerSourceCheck(GSource*) (source=)
at kernel/qeventdispatcher_glib.cpp:168
#1  0x7f05f23abda1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f05f23ac2a8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f05f23ac42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f05f65f133b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f05cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f05f659efeb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f05d8a79cb0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f05f63d9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7f05f96e79d8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f05f63de9e9 in QThreadPrivate::start(void*) (arg=0x251e600) at
thread/qthread_unix.cpp:341
#9  0x7f05f54ed744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f05f5cecaad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f05da454700 (LWP 2867)):
#0  0x7f05f5ce420d in poll () at /lib64/libc.so.6
#1  0x7f05f23ac314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f05f23ac42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f05f65f133b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f05d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f05f659efeb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f05da453cb0, flags=..., 

[KDb] [Bug 387798] Referencing column aliases in SELECT and WHERE does not work in PostgreSQL

[Adam Pigg]

https://bugs.kde.org/show_bug.cgi?id=387798

Adam Pigg  changed:

   What|Removed |Added

 CC||a...@piggz.co.uk

--- Comment #2 from Adam Pigg  ---
How about being standards compliant, and generating valid SQL?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 387750] TV frame rate too low

[nolli111]

https://bugs.kde.org/show_bug.cgi?id=387750

--- Comment #5 from nolli111  ---
My GPU is nVIDIA GTX1070

Where do I find the logs or how do I retrieve those in Kaffeine that started
with --debug to provide them to you? I have been working with UBUNTU 17.10 and
have no idea about Linux.

In reality, I can not speak English. I write all the texts in German and
translate them with the Google translator. I then copy these into my emails.


Von: Mauro Carvalho Chehab 
Gesendet: Montag, 11. Dezember 2017 15:53:18
An: gerhard.arn...@live.de
Betreff: [kaffeine] [Bug 387750] TV frame rate too low

https://bugs.kde.org/show_bug.cgi?id=387750

--- Comment #4 from Mauro Carvalho Chehab  ---
(In reply to nolli111 from comment #3)
> Created attachment 109314 [details]
> attachment-31108-0.html
>
> I'm talking about the jerkiness in Kaffeine TV
>
> Television pictures do not run smoothly

As I said, it is very likely due to either hardware issues or GPU driver.
Can you provide some logs with Kaffeine started with --debug?

What's your GPU?

> my English is not good

English is not my native language either. Yet, you English is very likely
better that my German, as I don't know more than a few words in German :-)

Also, we use English on BZ and discussions, as that makes easier for people to
understand each other.

--
You are receiving this mail because:
You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 369563] No option to hide timezone completely

[Alexander Mentyu]

https://bugs.kde.org/show_bug.cgi?id=369563

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #3 from Alexander Mentyu  ---
There can be additional option for showing or not any time zone in the settings
- currently there is option for toggling displaying of local time zone only

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 377733] Vertical spacing

[Alexander Mentyu]

https://bugs.kde.org/show_bug.cgi?id=377733

--- Comment #3 from Alexander Mentyu  ---
seems related to https://bugs.kde.org/show_bug.cgi?id=367809

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 387802] New: monitor

[Ari Santana]

https://bugs.kde.org/show_bug.cgi?id=387802

Bug ID: 387802
   Summary: monitor
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ea8...@gmail.com
  Target Milestone: ---

Application: plasma-desktop (4.11.22)
KDE Platform Version: 4.14.32
Qt Version: 4.8.7
Operating System: Linux 4.9.68-wifislax64 x86_64

-- Information about the crash:
I was using Bleachbit and I opened the Dolphin and I do not know what else to
write because I was not doing anything else.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Shell de escritorio Plasma (plasma-desktop), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f35be321780 (LWP 2400))]

Thread 3 (Thread 0x7f35051cd700 (LWP 2404)):
#0  0x7f35bae612fd in poll () at /lib64/libc.so.6
#1  0x7f35b7584964 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f35b7584a6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f35bccfa0ce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#4  0x7f35bccca5d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#5  0x7f35bccca8e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#6  0x7f35bcbc3c39 in QThread::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#7  0x7f35bccab733 in  () at /usr/lib64/qt/lib/libQtCore.so.4
#8  0x7f35bcbc63bc in  () at /usr/lib64/qt/lib/libQtCore.so.4
#9  0x7f35bc925684 in start_thread () at /lib64/libpthread.so.0
#10 0x7f35bae6ceed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f359346b700 (LWP 2401)):
#0  0x7f35bc92b36f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f35ae8c95aa in  () at /usr/lib64/qt/lib/libQtScript.so.4
#2  0x7f35ae8c95d9 in  () at /usr/lib64/qt/lib/libQtScript.so.4
#3  0x7f35bc925684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f35bae6ceed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f35be321780 (LWP 2400)):
[KCrash Handler]
#6  0x7f35bae050e0 in __memcpy_sse2_unaligned () at /lib64/libc.so.6
#7  0x7f35bcc3ef82 in QBuffer::readData(char*, long long) () at
/usr/lib64/qt/lib/libQtCore.so.4
#8  0x7f35bcc57436 in QIODevice::read(char*, long long) () at
/usr/lib64/qt/lib/libQtCore.so.4
#9  0x7f35bcc3fea5 in QDataStream::operator>>(int&) () at
/usr/lib64/qt/lib/libQtCore.so.4
#10 0x7f35bd4c4683 in KSycocaDict::Private::offsetForKey(QString const&)
const () at /usr/lib64/libkdecore.so.5
#11 0x7f35bd4c47e8 in KSycocaDict::find_string(QString const&) const () at
/usr/lib64/libkdecore.so.5
#12 0x7f35bd424cee in KMimeTypeTrader::query(QString const&, QString
const&, QString const&) const () at /usr/lib64/libkdecore.so.5
#13 0x7f35b3777d20 in KFileItemActions::associatedApplications(QStringList
const&, QString const&) () at /usr/lib64/libkio.so.5
#14 0x7f35b37791ed in KFileItemActions::preferredOpenWithAction(QString
const&) () at /usr/lib64/libkio.so.5
#15 0x7f359b6b0b93 in  () at /usr/lib64/kde4/plasma_applet_folderview.so
#16 0x7f3595ac315f in  () at
/usr/lib64/kde4/plasma_containmentactions_contextmenu.so
#17 0x7f35b11bbaf0 in  () at /usr/lib64/libplasma.so.3
#18 0x7f35b11bbd8e in  () at /usr/lib64/libplasma.so.3
#19 0x7f35b11c419b in
Plasma::Containment::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () at
/usr/lib64/libplasma.so.3
#20 0x7f35bc3dc2b1 in QGraphicsItem::sceneEvent(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#21 0x7f35bc4022ea in
QGraphicsScene::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#22 0x7f35bc41753c in QGraphicsScene::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#23 0x7f35bbe2148c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#24 0x7f35bbe27f5c in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#25 0x7f35bdd2a8aa in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#26 0x7f35bcccbc0d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#27 0x7f35bc42f207 in QGraphicsView::contextMenuEvent(QContextMenuEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#28 0x7f35bbe744d0 in QWidget::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#29 0x7f35bc21bfae in QFrame::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#30 0x7f35bc42ecbf in QGraphicsView::viewportEvent(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#31 0x7f35bcccbd76 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at

[gwenview] [Bug 387801] New: Gwenview - backgrond color not black

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=387801

Bug ID: 387801
   Summary: Gwenview - backgrond color not black
   Product: gwenview
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: rburgstah...@freenet.de
  Target Milestone: ---

Dear Friends,
Gwenview is a great program and I use it sporadically when I present slide
shows on my ACER Netbook (Xubuntu).
Is there a possibility to get a completely black background in full screen
slide show mode? With some beamers (depends on the quality) the background
during projection is a tick too light. In full screen mode (browser, slide
show) on my netbook the background looks like a dithered dark grey but not as
black.
If there is a trick, please let me know.

Some extra words:
Despite the fact, colleagues from Microsoft have detailed information about the
build in netbook GPU (which means that their programming libraries should work
well for all developers - the Ubuntu developers had no information for a long
time), there was no suitable slide show program on Windows 7 Starter that was
capable of showing movies from different cameras smoothly - KDE Gwenview did
that job! Esteem!!
Originally, I am now a MAC user for decades, but as Apple sets the focus on
Bluetooth speakers, maybe the time has come to switch to Linux.
Regards,
Ralf

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387791] Kmail & Kontact crash every time try to open

[Ivan S]

https://bugs.kde.org/show_bug.cgi?id=387791

--- Comment #3 from Ivan S  ---
(In reply to rana from comment #2)
> (In reply to Ivan S from comment #1)
> > I see that "sonnet was unable to load trigrams for languages" - this is
> > likely either not a bug or a bug in Sonnet.
> > Try deleting ~/.config/kmailrc
> > If that works, then it's a problem with your configuration and not a bug.
> 
> you are right.
> I did delete the config file and its working properly now...thanks..

You are welcome. In the future, please put issues like this on forum.kde.org
first, then bugs.kde.org if you find no solution.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387791] Kmail & Kontact crash every time try to open

[rana]

https://bugs.kde.org/show_bug.cgi?id=387791

--- Comment #2 from rana  ---
(In reply to Ivan S from comment #1)
> I see that "sonnet was unable to load trigrams for languages" - this is
> likely either not a bug or a bug in Sonnet.
> Try deleting ~/.config/kmailrc
> If that works, then it's a problem with your configuration and not a bug.

you are right.
I did delete the config file and its working properly now...thanks..

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 387800] "Configure launches" -> "Project target" drop-down list is not sorted

[Maciej Mrozowski]

https://bugs.kde.org/show_bug.cgi?id=387800

Maciej Mrozowski  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 387800] New: "Configure launches" -> "Project target" drop-down list is not sorted

[Maciej Mrozowski]

https://bugs.kde.org/show_bug.cgi?id=387800

Bug ID: 387800
   Summary: "Configure launches" -> "Project target" drop-down
list is not sorted
   Product: kdevelop
   Version: 5.2.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: reave...@gmail.com
  Target Milestone: ---

Created attachment 109320
  --> https://bugs.kde.org/attachment.cgi?id=109320=edit
targets not sorted

Steps to reproduce:
1. Open some project with supported project target discovery (in ex any CMake
project).
2. Run -> Configure Launches -> Add (any variant, the point is just to get to
project target selection).
3. Expand 'Project target' drop-down list.

'Project target' drop down list is not sorted in any useful way.
With a few items, it can work, but with more than 100+ targets, unsorted drop
down list is practically useless.
Other way would be to have some UI element that allows quick search.

There is also related problem with not perfectly handling quick expanded menu
with project targets - they do not fit the screen if there are too many of
them:

1. Open some project with supported project target discovery (in ex any CMake
project) that has a lot of targets (over 400 system component tests in my
case).
2. Run -> Configure Launches -> Add -> (select sub-menu with directory, where
targets are defined)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 387800] "Configure launches" -> "Project target" drop-down list is not sorted

[Maciej Mrozowski]

https://bugs.kde.org/show_bug.cgi?id=387800

--- Comment #1 from Maciej Mrozowski  ---
Created attachment 109321
  --> https://bugs.kde.org/attachment.cgi?id=109321=edit
targets do not fit the screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 387797] Applications list scrolls down some pixels on mouseover

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387797

--- Comment #5 from Nate Graham  ---
Thanks Ivan. Yeah, that's bit of a strange user experience and I agree that we
should change/fix it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 387797] Applications list scrolls down some pixels on mouseover

[Ivan S]

https://bugs.kde.org/show_bug.cgi?id=387797

--- Comment #4 from Ivan S  ---
Created attachment 109319
  --> https://bugs.kde.org/attachment.cgi?id=109319=edit
Video demo

Added an alternate video in WEBM format for Graham and others who have issues
w/ MP4

-- 
You are receiving this mail because:
You are watching all bug changes.

[ark] [Bug 387794] Support merge and split to .001, .002, etc files

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387794

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 387797] Applications list scrolls down some pixels on mouseover

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387797

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #3 from Nate Graham  ---
I can't open the video in any app on macOS. In the future, please attach videos
in the webm format.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387799] Kwin intermittently crashes

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387799

Nate Graham  changed:

   What|Removed |Added

Summary|Discover spontaneously  |Kwin intermittently crashes
   |crashes while open  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387799] Discover spontaneously crashes while open

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=387799

Nate Graham  changed:

   What|Removed |Added

Summary|Error con barra tareas y|Discover spontaneously
   |decoración ventanas |crashes while open

-- 
You are receiving this mail because:
You are watching all bug changes.