[umbrello] [Bug 376304] MSVCR This application has requested the runtime to terminate in an unusual way

[Ralf Habacker]

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

--- Comment #3 from Ralf Habacker  ---
To be able to get some more informations it would be nice if you would download
and install drmingw from https://github.com/jrfonseca/drmingw. 

Additional to get symbols it is required to download umbrello debug symbols
with the same architecture as installed umbrello from
http://download.kde.org/stable/umbrello/2.21.2/win32/ (debug symbols are in the
*debug.7z packages) and unpack them in the umbrello install root e.g. the
directory where the bin dir is located)

Now you can run umbrello and if it crashes drmingw will open a related windows.
Please copy and paste this content to this bug.

To get even more informations you can download dbgview from 
https://download.sysinternals.com/files/DebugView.zip. Unpack the file and
start dbgview before starting umbrello. It will reports umbrello's internal
debug messages.

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

[umbrello] [Bug 376304] MSVCR This application has requested the runtime to terminate in an unusual way

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

Version|2.21.0 (KDE Applications|2.21.1 (KDE Applications
   |16.12.0)|16.12.1)

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

[kate] [Bug 369138] Regex no longer available

[Kåre Särs]

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

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi

--- Comment #9 from Kåre Särs  ---
I think this might be a problem with iconsets. If you select Breeze or Oxygen
in Gnome it probably will work there too, but this is a problem that does need
a fix.

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

[kwin] [Bug 376507] Moving window between virtual desktops doesn't raise them

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

--- Comment #3 from Martin Gräßlin  ---
If we change it we get bug reports about it now raising the window.

What you can do is using a KWin script to raise a window when switching
desktops.

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

[plasmashell] [Bug 376529] The panel is placed over the desktop icons, when both are located to the right.

[Nibaldo]

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

Nibaldo  changed:

   What|Removed |Added

URL|desktop panel icons |

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

[plasmashell] [Bug 376529] The panel is placed over the desktop icons, when both are located to the right.

[Nibaldo]

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

Nibaldo  changed:

   What|Removed |Added

URL||desktop panel icons

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

[plasmashell] [Bug 376529] New: The panel is placed over the desktop icons, when both are located to the right.

[Nibaldo]

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

Bug ID: 376529
   Summary: The panel is placed over the desktop icons, when both
are located to the right.
   Product: plasmashell
   Version: 5.9.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: nib...@live.cl
  Target Milestone: 1.0

The desktop panel is located above, covering the desktop icons (the icons
should be on the side of the panel, not below).

The bug occurs only if:
- The desktop panel is set to the right of the screen.
- The desktop has the "Folder View" layout and the icons are aligned to the
right.

The bug does not occurs if the panel is up, down or left the screen, or the
icons are aligned to the left of the desktop.

The bug appeared in Plasma 5.9.1 (before it did not happen).

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

[kate] [Bug 369138] Regex no longer available

[bugzilla_noreply]

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

--- Comment #8 from daobr...@redhat.com ---
I tried this on several different desktops/window managers (Gnome, Gnome
Classic, xfce) and it only works when I use the KDE desktop. Then I see the
icons. In all other cases the buttons are invisible when off.

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

[plasmashell] [Bug 375824] Wallpaper image size choice is not optimal

[Nibaldo]

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

--- Comment #1 from Nibaldo  ---
I was just going to report this bug and I found it. I noticed that the
wallpapers look rather blurry.

As an example, if we choose this wallpaper image on a regular monitor, the bug
is notorious:
https://kbdevstorage1.blob.core.windows.net/asset-blobs/19027_en_1

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

[digikam] [Bug 376489] Pentax K-5

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |MS Windows

--- Comment #5 from caulier.gil...@gmail.com ---
No problem to open it into digiKam 5.5.0 pre version under MacOS :

https://www.flickr.com/photos/digikam/32803742471/in/dateposted-public/

Metadata can be reas and DNG open in Editor.

It's know a problem with Exiv2 about non latin1 char used in file path. Check
this point, especially under Windows.

If you want to try 5.5.0 windows version it's here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[systemsettings] [Bug 376513] Crash for "Desktop Effects" and "Workspace Theme", possible dup of 350205

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[plasmashell] [Bug 376528] New: Spotify SSL Error crashed plasma?

[Ryan Swart]

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

Bug ID: 376528
   Summary: Spotify SSL Error crashed plasma?
   Product: plasmashell
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: serjndest...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.45-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Listening to Spotify whilst browsing the web

- Unusual behavior I noticed:
A prompt-window appeared stating that Spotify is using an invalid SSL
certificate, clicking through to more details produced a normal window with
overlapping text, at which point Plasma crashed.

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

Thread 11 (Thread 0x7f9a07fff700 (LWP 26304)):
#0  0x7f9ae6f3ddb9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9ae6ef7c95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f9ae6ef86ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9ae6ef889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f9aec58d48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f9aec536e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f9aec359053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f9aec35dce8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9aeb46d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9aebc737df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f99f6ebf700 (LWP 24165)):
#0  0x7f9adeea398c in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#1  0x7f9adeea420a in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#2  0x7f9adf51599c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0
#3  0x7f9adf515d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f9adf515e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f9adf523e29 in  () at /usr/lib/libpulse.so.0
#6  0x7f9adeeb3fe8 in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#7  0x7f9aeb46d454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9aebc737df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f9a0f24e700 (LWP 24164)):
#0  0x7f9aebc6a48d in poll () at /usr/lib/libc.so.6
#1  0x7f9ae6ef8786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9ae6ef889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9aec58d48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9aec536e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9aec359053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9aef6c0e75 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f9aec35dce8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9aeb46d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9aebc737df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f9a21485700 (LWP 3034)):
#0  0x7f9aebc6a48d in poll () at /usr/lib/libc.so.6
#1  0x7f9ae6ef8786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9ae6ef889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9aec58d48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9aec536e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9aec359053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9a23d570a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f9aec35dce8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9aeb46d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9aebc737df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f9a396a0700 (LWP 2841)):
#0  0x7f9aebc6a48d in poll () at /usr/lib/libc.so.6
#1  0x7f9ae6ef8786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9ae6ef889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9aec58d48b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9aec536e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9aed68ba37 in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5
#6  0x7f9aea3208f3 in
KIO::JobUiDelegate::requestMessageBox(KIO::JobUiDelegateExtension::MessageBoxType,
QString const&, QString const&, QString const&, QString const&, QString const&,
QString const&, QString const&, KIO::MetaData const&) () at

[plasmashell] [Bug 376527] New: menu button at top left causes crash when widgets are locked and button is clicked

[bugzilla_noreply]

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

Bug ID: 376527
   Summary: menu button at top left causes crash when widgets are
locked and button is clicked
   Product: plasmashell
   Version: 5.9.1
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: somnia...@hushmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.1)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.8.15-1 x86_64
Distribution: "KaOS"

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

Widgets were locked. I clicked the menu button at the top left of desktop (icon
with 3 horizontal bars). Screen went black and plasma crashed. Occurred every
time I clicked the menu button. I have a panel at the top with a taskbar
widget. I have a panel at the bottom with app shortcuts, system tray and k
menu.

I use the KaOS distribution.

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7f1f6bfff700 (LWP 23331)):
#0  0x7f2042423c2d in poll () at /lib/libc.so.6
#1  0x7f203635df21 in  () at /usr/lib/libpulse.so.0
#2  0x7f203634fba1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7f20363501de in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f2036350290 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f203635de86 in  () at /usr/lib/libpulse.so.0
#6  0x7f2035cef6c8 in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#7  0x7f20419e6424 in start_thread () at /lib/libpthread.so.0
#8  0x7f204242ccad in clone () at /lib/libc.so.6

Thread 8 (Thread 0x7f1f7f3b1700 (LWP 609)):
#0  0x7f2042d287b4 in  () at /usr/lib/libQt5Core.so.5
#1  0x7f203bdbe441 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f203bdbe9a8 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f203bdbeb0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f2042d28ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f2042cd6bba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f2042b0bd7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f1f81c74347 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#8  0x7f2042b106e9 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f20419e6424 in start_thread () at /lib/libpthread.so.0
#10 0x7f204242ccad in clone () at /lib/libc.so.6

Thread 7 (Thread 0x7f1f9279d700 (LWP 602)):
#0  0x7f204241fbfd in read () at /lib/libc.so.6
#1  0x7f203be021c0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f203bdbe50e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f203bdbe9a8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f203bdbeb0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f2042d28ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f2042cd6bba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f2042b0bd7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f2045ae51b2 in  () at /usr/lib/libQt5Quick.so.5
#9  0x7f2042b106e9 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f20419e6424 in start_thread () at /lib/libpthread.so.0
#11 0x7f204242ccad in clone () at /lib/libc.so.6

Thread 6 (Thread 0x7f201bfff700 (LWP 601)):
#0  0x7f20419ec03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7f204759c934 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f204759c979 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f20419e6424 in start_thread () at /lib/libpthread.so.0
#4  0x7f204242ccad in clone () at /lib/libc.so.6

Thread 5 (Thread 0x7f2022385700 (LWP 597)):
#0  0x7f203bd1 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f203bdbe38a in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f203bdbe9a8 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f203bdbeb0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f2042d28ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f2042cd6bba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f2042b0bd7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f204513b3a5 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f2042b106e9 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f20419e6424 in start_thread () at /lib/libpthread.so.0
#10 0x7f204242ccad in clone () at /lib/libc.so.6

Thread 4 (Thread 0x7f2023fff700 (LWP 596)):
#0  0x7f204241fbfd 

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #71 from Christoph Feck  ---
Reopening.

Are there certain steps or specific setups needed to reproduce?

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

[akregator] [Bug 376275] akregator crash while fetching all feeds

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Already reported as bug 375743.

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

[neon] [Bug 376468] Upgrade Qt to 5.8

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||idmresettr...@gmail.com

--- Comment #2 from Christoph Feck  ---
*** Bug 376357 has been marked as a duplicate of this bug. ***

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

[neon] [Bug 376357] Is there anyway to update libqt5core5a?

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---


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

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

[i18n] [Bug 358054] konsole: Ctrl+Shift+F, input the string I want to search, the chinese translation of search up and down button is wrong

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Summary|Ctrl+Shift+F, input the |konsole: Ctrl+Shift+F,
   |string I want to search,|input the string I want to
   |the chinese translation of  |search, the chinese
   |search up and down button   |translation of search up
   |is wrong|and down button is wrong

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

[gwenview] [Bug 375752] Gwenview not working in Linux Mint 18.1 - Cinnamon 64-bit

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |INVALID

--- Comment #3 from Christoph Feck  ---
No response, changing status. If you have new information, please add a
comment.

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

[kate] [Bug 369138] Regex no longer available

[bugzilla_noreply]

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

--- Comment #7 from daobr...@redhat.com ---
When I get the opportunity I'll try using KDE and see what happens.
Thanks for looking.

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

[kate] [Bug 369138] Regex no longer available

[Nikolaos Kakouros]

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

--- Comment #6 from Nikolaos Kakouros  ---
The buttons do have icons. I cant help on why gnome cant find them, sorry!

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

[plasmashell] [Bug 376517] Problems with global menu

[Christian González]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[kate] [Bug 353747] Icon from toolbar opens only when holding mouse click for short period of time

[Nikolaos Kakouros]

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

Nikolaos Kakouros  changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from Nikolaos Kakouros  ---
Still valid on kate 16.12.2. Seems like the button has an empty (or
non-obvious) action assigned to it. When you click it fast this action gets
triggered but nothing happens. If you long click on it then it shows the menu
to select secondary items.

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

[kate] [Bug 360241] Snippet repo shown twice in list, must not delete one

[Nikolaos Kakouros]

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

Nikolaos Kakouros  changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from Nikolaos Kakouros  ---
Cannot reproduce on kate 16.12.2 on arch linux

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

[kate] [Bug 364788] "Show menu bar" button/menu entry toggles status bar instead of menu bar

[Nikolaos Kakouros]

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

Nikolaos Kakouros  changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from Nikolaos Kakouros  ---
Works fine here too (Kate 16.08.3-KF5.28 (32bit) on windows 10)

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

[kate] [Bug 369138] Regex no longer available

[bugzilla_noreply]

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

daobr...@redhat.com changed:

   What|Removed |Added

 CC||daobr...@redhat.com

--- Comment #5 from daobr...@redhat.com ---
Created attachment 104047
  --> https://bugs.kde.org/attachment.cgi?id=104047=edit
Image of missing buttons

Screen shot of where the buttons are. Visible when enabled, but otherwise
completely invisible.

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

[Discover] [Bug 376522] longer usage crash

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Aleix Pol  ---
Can you maybe try to reproduce with debug symbols enabled?

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

[kate] [Bug 333464] Share configuration easily

[Nikolaos Kakouros]

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

Nikolaos Kakouros  changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from Nikolaos Kakouros  ---
EditorConfig is currently being implemented. I don't think that share other
configuration would be possible since each editor uses its own format and
features.

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

[Discover] [Bug 376241] software centre is empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||pablothe...@yahoo.co.uk

--- Comment #12 from Aleix Pol  ---
*** Bug 376181 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 376181] Discover is not showing any available software up dates nor available software in any of the categories.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 376424] discover becomes empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[kate] [Bug 369138] Regex no longer available

[bugzilla_noreply]

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

--- Comment #4 from daobr...@redhat.com ---
Current packages:

$ rpm -qa | grep -i kate
kate4-part-4.14.3-16.fc24.x86_64
libkate-0.4.1-7.fc24.x86_64
kate-16.08.3-1.fc24.x86_64
kate-plugins-16.08.3-1.fc24.x86_64
perl-Syntax-Highlight-Engine-Kate-0.10-2.fc24.noarch

The regex and case-sensitive search options now appear as buttons, not check
boxes. I forgot to update the bug, sorry.

But (and probably unrelated) the buttons have no labels or icons, although they
do have tooltips. These and some other buttons (e.g., the button to hide the
search bar) are completely invisible until you mouse over them. I found them by
accident.


I'm running Kate on top of gnome, so maybe there are some required packages
missing?

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

[Discover] [Bug 376241] software centre is empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||gerard.sel...@wanadoo.fr

--- Comment #11 from Aleix Pol  ---
*** Bug 376424 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 375975] Discover 5.9.0 completely broken on NEON

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DOWNSTREAM
 Status|NEEDSINFO   |RESOLVED

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

[Discover] [Bug 375975] Discover 5.9.0 completely broken on NEON

[Aleix Pol]

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

--- Comment #5 from Aleix Pol  ---
This is an issue in PackageKit upstream. Please make sure your distribution has
an up to date PackageKit.

See https://github.com/hughsie/PackageKit/pull/180

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

[Discover] [Bug 375975] Discover 5.9.0 completely broken on NEON

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||stevlo...@gmail.com

--- Comment #4 from Aleix Pol  ---
*** Bug 376354 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 376354] Discover keeps crashing while trying to install apps

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #3 from Aleix Pol  ---


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

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

[apper] [Bug 373044] The last time, apper before finish updating packages, returned an Update Error

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||aleix...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #6 from Aleix Pol  ---
I have this same bug report for Discover. I suggest you report it to PackageKit
upstream, as it's PackageKit crashing in fact.

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

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

[Discover] [Bug 375975] Discover 5.9.0 completely broken on NEON

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||tomaz...@otenet.gr

--- Comment #3 from Aleix Pol  ---
*** Bug 373044 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 368377] Add shortcut for Search and Replace

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #1 from tterrani...@gmail.com ---
You can assign the shortcut you wish for the Search and Replace panel. Also,
Ctrl+R will show the simple Replace.

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

[kate] [Bug 364239] Snippet keyboard shortcut doesn't work

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #3 from tterrani...@gmail.com ---
In kate 16.2.2, the shortcut will work after a restart of kate.

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

[kscreenlocker] [Bug 376526] New: Clipboard text available for pastingwhen lock screen visible

[bugzilla_noreply]

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

Bug ID: 376526
   Summary: Clipboard text available for pastingwhen lock screen
visible
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: bluescreenaven...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Inspired by
https://hexatomium.github.io/2017/02/15/windows10-clipboard-lockscreen/
I decided to see if this works in KDE. While it seems with the greeter, there
is no way to see the contents in plain text, the password field does get filled
with the contents of the clipboard.

With this I guess, could allow someone to unlock the screen in the unlikely and
ill advisable scenario that the user copies their password, then locks the
screen

This is under X11, I have not tested Wayland yet.

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

[kate] [Bug 369138] Regex no longer available

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #3 from tterrani...@gmail.com ---
Maybe there was a problem with those packages? Is it resolved?

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

[plasmashell] [Bug 376525] New: Plasma crash with clean profile

[Solerman Kaplon]

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

Bug ID: 376525
   Summary: Plasma crash with clean profile
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: solerman.kap...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
I shutdown the sddm service and cleared all things kde and baloo in .local and
.cache. Other reports suggests this might be a database corruption, but this
one I got with a new-ish profile

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__pthread_self () at pthread_self.c:27
[Current thread is 1 (Thread 0x7effe97748c0 (LWP 1701))]

Thread 16 (Thread 0x7eff097fa700 (LWP 2132)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7effe457fa5b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x49acb70) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x4d31290,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7eff2cd9850b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x4e02b50, th=) at ../../src/weaver.cpp:594
#4  0x7eff2cd992bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x4e02b50,
th=th@entry=0x7eff04002f90, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554
#5  0x7eff2cd9d4e8 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:66
#6  0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#7  0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:73
#8  0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#9  0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:73
#10 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#11 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:73
#12 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#13 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:73
#14 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#15 0x7eff2cd9d542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x4e02cd0, th=0x7eff04002f90, wasBusy=) at
../../src/workinghardstate.cpp:73
#16 0x7eff2cd9846d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7eff04002f90, wasBusy=) at ../../src/weaver.cpp:568
#17 0x7eff2cd9b353 in ThreadWeaver::Thread::run (this=0x7eff04002f90) at
../../src/thread.cpp:103
#18 0x7effe457e7be in QThreadPrivate::start (arg=0x7eff04002f90) at
thread/qthread_unix.cpp:331
#19 0x7effe366b6ba in start_thread (arg=0x7eff097fa700) at
pthread_create.c:333
#20 0x7effe3e9482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7eff09ffb700 (LWP 2131)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7effe457fa5b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x49acb70) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x4d31290,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7eff2cd9850b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x4e02b50, th=) at ../../src/weaver.cpp:594
#4  0x7eff2cd992bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x4e02b50,
th=th@entry=0x7eff3190, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554
#5  0x7eff2cd9d4e8 in 

[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #15 from tterrani...@gmail.com ---
So is this resolved?

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

[kate] [Bug 369008] Kate crashes when doing lookoup

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from tterrani...@gmail.com ---
Seems to work fine on Kate 16.12.2

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

[kwin] [Bug 376507] Moving window between virtual desktops doesn't raise them

[bugzilla_noreply]

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

pfannenwen...@googlemail.com changed:

   What|Removed |Added

 Resolution|INVALID |FIXED

--- Comment #2 from pfannenwen...@googlemail.com ---
(In reply to Martin Gräßlin from comment #1)
> The behavior seems correct to me. The stacking order includes all desktops
> and the opening of application b gets it raised above application a. Thus
> the stacking order looks correct to me.

If you put it like this it seems coherent, but very counterintuitive.
This behaviour results in having to use alt+tab twice to actually have the
application visible when you switch it over to another desktop. Is there any
hope that this could be changed, or do you feel that the current behaviour is
favourable?

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

[kate] [Bug 366568] when dragging & dropping folders, contained files are opened as blank / new.

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #5 from tterrani...@gmail.com ---
This works correct on latest kate (16.6.2).

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

[kate] [Bug 156532] Go to previous/next place

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #5 from tterrani...@gmail.com ---
This feature exists in kate (16.12.2) with the actions "Go to previous editing
line" and "Go to next editing line".

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

[kate] [Bug 328184] Kate (Windows) crashes when user presses Ctrl+C on the parent Command Prompt

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #1 from tterrani...@gmail.com ---
Cannot reproduce this on Windows 10 with Kate 16.08.3-KF5.28 (32bit).

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

[kate] [Bug 315141] kate chooses the wrong color for text from the KDE color scheme

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #2 from tterrani...@gmail.com ---
Is this bug even relevant today?

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

[kate] [Bug 376306] Kate does not remember color scheme after restart

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #4 from tterrani...@gmail.com ---
(In reply to darktori from comment #3)
> ll /home/tori/.config/kwriterc
> -rwxrwxrwx 1 tori tori 324 lut 10 19:33 /home/tori/.config/kwriterc*
> 
> No change, still doesn't remember, but now I'm not getting the error while
> starting kwrite

I think you have wrong permissions still or sth. Can you delete kwriterc? What
is the asterisk in your output above? Is it from the -F flag of ls? Can you
also show the output of "ls -d ~/.config"?

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

[kate] [Bug 374912] Some suggestions

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #1 from tterrani...@gmail.com ---
(In reply to Жељко Симић from comment #0)
> It will be nice if you update some features in this editor.
> 1. when I want to use keyboard shortcut ctrl + (left/right) to point on text
> pointer does not stops on before '_'. It's a problem because of
> this_kind_of_notations.
> 2. When I'm pull in some code and press HOME key it goes on the starting end
> of line and if i want to select something I must to correctly select just
> text to avoid tabulators in selection, it takes time and it's stupid thing
> and annoying. 
> 
> Bye!

You should break this into two bug reports.

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

[kate] [Bug 375594] Automatic save

[bugzilla_noreply]

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

tterrani...@gmail.com changed:

   What|Removed |Added

 CC||tterrani...@gmail.com

--- Comment #1 from tterrani...@gmail.com ---
I think this is a duplicate of bug 353654.

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

[systemsettings] [Bug 376524] New: KDE systemsettings crash if i click overview

[Patrick Kasper]

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

Bug ID: 376524
   Summary: KDE systemsettings crash if i click overview
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_desktoppath
  Assignee: unassigned-b...@kde.org
  Reporter: patkasper.linuxfreakg...@gmail.com
  Target Milestone: ---

Created attachment 104046
  --> https://bugs.kde.org/attachment.cgi?id=104046=edit
Xorg Log

If I click on desktop behavior then click screen lock and then back to the
overview, crashes system settings without error message.

Plasma Version 5.9.1
KDE Frameworks Version 5.30.0
QT Version 5.8.0
Arch Linux
64 Bit

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

[kdevelop] [Bug 376523] New: Assertion failure when discarding changes in Custom BuildSystem settings.

[Francis Herne]

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

Bug ID: 376523
   Summary: Assertion failure when discarding changes in Custom
BuildSystem settings.
   Product: kdevelop
   Version: 5.1.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: BuildSystem: Custom BuildSystems
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@flherne.uk
  Target Milestone: ---

Using recent 5.1 branches, compiled from source on Arch Linux:

 - Create a Custom BuildSystem project.
 - Go to Project -> Open Configuration -> Custom BuildSystem
 - Make some config change, but don't apply it.
 - Switch to another config page.
 - A dialog will appear asking whether to Apply or Discard changes.
 - Select 'Discard'.

KDevelop will crash with the following backtrace. This doesn't occur if
selecting 'Apply', or with other build plugins (at least Make, CMake).

-
ASSERT: "ui->currentConfig->count() == configs.count()" in file
/home/flh/projects/kdevelop/projectmanagers/custom-buildsystem/custombuildsystemconfigwidget.cpp,
line 196

Thread 1 "kdevelop" received signal SIGABRT, Aborted.
0x702d904f in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x702d904f in raise () at /usr/lib/libc.so.6
#1  0x702da47a in abort () at /usr/lib/libc.so.6
#2  0x70f7ae21 in  () at /usr/lib/libQt5Core.so.5
#3  0x70f763de in  () at /usr/lib/libQt5Core.so.5
#4  0x7fffb3006cc9 in CustomBuildSystemConfigWidget::verify()
(this=0x2aa8790) at
/home/flh/projects/kdevelop/projectmanagers/custom-buildsystem/custombuildsystemconfigwidget.cpp:196
#5  0x7fffb3009d85 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (CustomBuildSystemConfigWidget::*)()>::call(void
(CustomBuildSystemConfigWidget::*)(), CustomBuildSystemConfigWidget*, void**)
(f=(void (CustomBuildSystemConfigWidget::*)(CustomBuildSystemConfigWidget *
const)) 0x7fffb3006c7a , o=0x2aa8790,
arg=0x7fff9ae0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:143
#6  0x7fffb3009b4e in QtPrivate::FunctionPointer::call, void>(void
(CustomBuildSystemConfigWidget::*)(), CustomBuildSystemConfigWidget*, void**)
(f=(void (CustomBuildSystemConfigWidget::*)(CustomBuildSystemConfigWidget *
const)) 0x7fffb3006c7a , o=0x2aa8790,
arg=0x7fff9ae0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:162
#7  0x7fffb300980d in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x2a5e810, r=0x2aa8790, a=0x7fff9ae0, ret=0x0) at
/usr/include/qt/QtCore/qobject_impl.h:120
#8  0x7119b0be in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#9  0x7fffb300b2c3 in CustomBuildSystemConfigWidget::changed()
(this=0x2aa8790)
at
/home/flh/projects/kdevelop/build/projectmanagers/custom-buildsystem/kdevcustombuildsystem_automoc.dir/moc_custombuildsys_6N7SPIMYBDOOYP.cpp:156
#10 0x7fffb3006df3 in
CustomBuildSystemConfigWidget::renameCurrentConfig(QString const&)
(this=0x2aa8790, name=...)
at
/home/flh/projects/kdevelop/projectmanagers/custom-buildsystem/custombuildsystemconfigwidget.cpp:212
#11 0x7fffb3009e17 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(CustomBuildSystemConfigWidget::*)(QString const&)>::call(void
(CustomBuildSystemConfigWidget::*)(QString const&),
CustomBuildSystemConfigWidget*, void**) (f=
(void (CustomBuildSystemConfigWidget::*)(CustomBuildSystemConfigWidget *
const, const QString &)) 0x7fffb3006d78
,
o=0x2aa8790, arg=0x7fff9d40) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:143
#12 0x7fffb3009b93 in QtPrivate::FunctionPointer::call(void
(CustomBuildSystemConfigWidget::*)(QString const&),
CustomBuildSystemConfigWidget*, void**) (f=
(void (CustomBuildSystemConfigWidget::*)(CustomBuildSystemConfigWidget *
const, const QString &)) 0x7fffb3006d78
,
o=0x2aa8790, arg=0x7fff9d40) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:162
#13 0x7fffb30098e9 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=1, this_=0x2b5c310, r=0x2aa8790, a=0x7fff9d40, ret=0x0) at
/usr/include/qt/QtCore/qobject_impl.h:120
#14 0x7119b0be in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#15 0x71f4f352 in QComboBox::editTextChanged(QString const&) () at
/usr/lib/libQt5Widgets.so.5
#16 0x71f59101 in  () at /usr/lib/libQt5Widgets.so.5
#17 0x7119ad49 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#18 

[kdevelop] [Bug 245902] Find Uses Keyboard Support

[Milian Wolff]

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

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||vplatform/0ed19a87cef4872d9
   ||bf7e50dc89db8895428bb40
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Milian Wolff  ---
Git commit 0ed19a87cef4872d9bf7e50dc89db8895428bb40 by Milian Wolff, on behalf
of Damir Porobic.
Committed on 15/02/2017 at 22:29.
Pushed by mwolff into branch 'master'.

Keyboard shortcuts for Uses in Code Browser

Fix for bug/wish 245902. Use the IToolActionViewer to implement
this feature: When the code browser is open and shows uses you can
now navigate through all uses by pressing F4 and Shift+F4. The Use
that is selected will also be opened, just like clicking on it.

Test Plan: Manual Testing
Reviewed By: mwolff
Differential Revision: https://phabricator.kde.org/D4483

M  +39   -3language/duchain/navigation/useswidget.cpp
M  +5-0language/duchain/navigation/useswidget.h
M  +85   -0plugins/contextbrowser/contextbrowserview.cpp
M  +5-1plugins/contextbrowser/contextbrowserview.h

https://commits.kde.org/kdevplatform/0ed19a87cef4872d9bf7e50dc89db8895428bb40

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

[plasmashell] [Bug 376517] Problems with global menu

[Nikita Skovoroda]

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

--- Comment #4 from Nikita Skovoroda  ---
Probably you should have filed two separate bugreports for two separate issues,
not one for both of them.

For the item 1 — this is an Electron issue, and it has a workaround described
in the linked Electron bugreport.

As for the item 2,
 * The bad behaviour is observed when: switch to «menu button in title bar»,
open kate, switch to «menu inside window», close kate, open kate — no menu.
 * The bad behaviour is not observed when: switch to «menu button in title
bar», open kate,  close kate, switch to «menu inside window», open kate — the
menu is present.

What plays an effect here is whether the app in question was opened when the
setting did change to «menu inside window», the bug is reproducable only for
those apps that were open at that moment — restarting them doesn't help, the
menu is still hidden.

Workaround: press ctrl+m _two_ times to «hide» and show the menu.

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

[digikam] [Bug 376489] Pentax K-5

[Gustav]

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

--- Comment #4 from Gustav  ---
Hello,

I want to try it. How can i do that, I am a beginner at digikam. And
sorry for my english. Greatings from Berlin Stephan


Am 15.02.2017 um 22:00 schrieb bugzilla_nore...@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=376489
>
> --- Comment #2 from caulier.gil...@gmail.com ---
> Note : read metadata is done by Exiv2 shared lib in background. Can you
> reproduce the crash with Exiv2 command line tool when you read a KF5 Raw file 
> ?
>
> Gilles Caulier
>



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[Ahmed Badr]

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

Ahmed Badr  changed:

   What|Removed |Added

 CC||a...@111virtual.com

--- Comment #4 from Ahmed Badr  ---
I'm having this problem as well with Kubuntu, Neon and OpenSUSE.
I have 2 sessions running with different user accounts, and this problem occurs
most of the time I switch between them.

Searching online some reported that this might be a problem with:
- a full root partition - tested and not the case
- a full tmp partition - tested and not the case
- a root btrfs partition reporting wrong space info - tested with both btrfs
and ext4 and not the case

I would appreciate it if you could confirm this issue and try to resolve it.

A workaround is to disable the screen locker but I can only do that at home not
in an office environment.

Thanks.

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

[digikam] [Bug 376489] Pentax K-5

[Gustav]

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

--- Comment #3 from Gustav  ---
Hello,

Yes, I'm sending some files, JPG and DNG. (via Zeta-Uploader) Stephan


Am 15.02.2017 um 21:59 schrieb bugzilla_nore...@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=376489
>
> caulier.gil...@gmail.com changed:
>
> What|Removed |Added
> 
>   CC||caulier.gil...@gmail.com
>
> --- Comment #1 from caulier.gil...@gmail.com ---
> Can you share some K5 RAW files through the cloud to reproduce the dysfunction
> ?
>
> Gilles Caulier
>



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

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

[kdevelop] [Bug 372888] Kdevelop crashes when using sudo ninja install

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Kevin Funk  ---
Confirmed

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

[plasmashell] [Bug 376444] Crash in NotificationAction::start() when triggering notification action

[Martin Klapetek]

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

--- Comment #5 from Martin Klapetek  ---
You have to use ` ` quotes, not ' '. `command` in bash actually executes the
command in between those quotes.

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[bugzilla_noreply]

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

jlhyo...@bigpond.com changed:

   What|Removed |Added

 CC||jlhyo...@bigpond.com

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

[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.5.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/aa084a182beef888ae6015
   ||06550c89b2d7a74610

--- Comment #7 from Maik Qualmann  ---
Git commit aa084a182beef888ae601506550c89b2d7a74610 by Maik Qualmann.
Committed on 15/02/2017 at 21:31.
Pushed by mqualmann into branch 'master'.

fix inconsistent item activation with Enter key after mouse actions
FIXED-IN: 5.5.0

M  +2-1NEWS
M  +2-1libs/widgets/itemview/itemviewcategorized.cpp

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

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

[plasmashell] [Bug 376444] Crash in NotificationAction::start() when triggering notification action

[Tony]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #4 from Tony  ---
No crash when i ran dolphin & kill -6 'pidof dolphin'

It complains about "bash: kill: pidof dolphin: arguments must be process or job
IDs"

I launched a dolphin instance and ran dolphin & kill -6 'pidof dolphin'
again no crash. Using the PID of dolphin still does not trigger the crash.

Now running it without '' it does every-time.

dolphin & kill -6 pidof [pid of dolphin here]

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

[digikam] [Bug 376463] Improve keyboard assignment and useage of tags

[Kusi]

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

Kusi  changed:

   What|Removed |Added

 CC||k...@forum.titlis.org

--- Comment #1 from Kusi  ---

1)
pressing enter after having selected a tag will keep the the focus on the tag
edit box. Pressing enter a second time moves the focus back to the main window
and advances to the next image.

See the commit message in
https://cgit.kde.org/digikam.git/commit/?id=d13f94a8c5cf18a7c3c19c522fa484e5b7fb1bd9

Unfortunately, the sorting-by-history is broken since the DK5 port.

2)
up/down is needed for navigation in the main view in my opinion

3)
you can assign a single key shortcut to a tag via detour: you add a
Ctrl+ shortcut via tag properties. The tag then appears in
settings->shortcuts, where you can add a custom single letter shortcut. This is
indeed more complicated than it should be

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

[Discover] [Bug 376522] New: longer usage crash

[Aram]

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

Bug ID: 376522
   Summary: longer usage crash
   Product: Discover
   Version: 5.9.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: aramgrigor...@protonmail.ch
  Target Milestone: ---

Application: plasma-discover (5.9.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.9-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Just browsing, going to plasma addons, then cursors,, installed some stuff
there... got back to application addons, clicked on one application and crashed
the software

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6c0ffe88c0 (LWP 14313))]

Thread 10 (Thread 0x7f6bdae7a700 (LWP 14536)):
#0  0x7f6c080d14b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6c0beef2b6 in QWaitCondition::wait(QMutex*, unsigned long)
(time=3, this=0x7f6bbc00bbe0) at thread/qwaitcondition_unix.cpp:133
#2  0x7f6c0beef2b6 in QWaitCondition::wait(QMutex*, unsigned long)
(time=3, this=0x7f6bbc00bbe0) at thread/qwaitcondition_unix.cpp:141
#3  0x7f6c0beef2b6 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x7f6bbc00b850, mutex=mutex@entry=0x7f6bcc004c50, time=3)
at thread/qwaitcondition_unix.cpp:215
#4  0x7f6c0beeaae2 in QThreadPoolThread::run() (this=0x7f6bbc00b840) at
thread/qthreadpool.cpp:133
#5  0x7f6c0beee4c8 in QThreadPrivate::start(void*) (arg=0x7f6bbc00b840) at
thread/qthread_unix.cpp:368
#6  0x7f6c080cb454 in start_thread () at /lib64/libpthread.so.0
#7  0x7f6c0b4f737f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f6b5b7fe700 (LWP 14356)):
#0  0x7f6c0b4ea6dd in read () at /lib64/libc.so.6
#1  0x7f6c061bdab0 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6c0617934e in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6c06179824 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f6c06179c12 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#5  0x7f6b98530246 in  () at /usr/lib64/libgio-2.0.so.0
#6  0x7f6c061a11d5 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f6c080cb454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6c0b4f737f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f6b5bfff700 (LWP 14355)):
#0  0x7f6c06178fd2 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f6c061797f8 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6c0617999c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6c061799e1 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f6c061a11d5 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f6c080cb454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f6c0b4f737f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f6bd9677700 (LWP 14325)):
#0  0x7f6c0b4ee66d in poll () at /lib64/libc.so.6
#1  0x7f6c06179886 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6c0617999c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6c0c11218b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6bbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6c0c0bbaea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6bd9676d00, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f6c0bee9813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f6c0beee4c8 in QThreadPrivate::start(void*) (arg=0x2a05e10) at
thread/qthread_unix.cpp:368
#7  0x7f6c080cb454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6c0b4f737f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f6bdc50b700 (LWP 14320)):
#0  0x7f6c0b4ee66d in poll () at /lib64/libc.so.6
#1  0x7f6c06179886 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6c0617999c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6c0c11218b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6bd40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6c0c0bbaea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6bdc50ad00, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f6c0bee9813 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f6c0beee4c8 in QThreadPrivate::start(void*) (arg=0x29844a0) at
thread/qthread_unix.cpp:368
#7  0x7f6c080cb454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6c0b4f737f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f6bebfff700 (LWP 14318)):
#0  0x7f6c0b4ee66d in poll () at /lib64/libc.so.6
#1  0x7f6c06179886 in  () at 

[plasmashell] [Bug 376517] Problems with global menu

[Francisco Cribari]

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

--- Comment #3 from Francisco Cribari  ---
As for item 2), that also happened to okular. After reverting back to "In
application", okular (just a kate) displayed no menus at all. I had to do a 

rm ~/.config/okul*

and restart okular to get the menus back.

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

[kdevelop] [Bug 376521] New: Rename does not show leading white space, but still applies it.

[bugzilla_noreply]

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

Bug ID: 376521
   Summary: Rename does not show leading white space, but still
applies it.
   Product: kdevelop
   Version: 5.0.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: documentview
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: gustavo.goretkin+kde...@gmail.com
  Target Milestone: ---

steps to reproduce

1. copy to the clipboard an identifier at the beginning of an indented line.
select the indentation as well.
2. select another identifier and right-click and `Rename`.
3. paste into the `New name` field. notice that leading white space is not
shown.
4. click `Rename`

Observe that white space is added to renamed identifiers.

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

[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view

[Maik Qualmann]

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

--- Comment #6 from Maik Qualmann  ---
The cause I have found, it comes from the item activation. We save the last
mouse event and check the click area. This is bad with the Enter key. I am
looking for a clean solution...

Maik

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

[digikam] [Bug 376489] Pentax K-5

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|Metadata|Metadata-Engine

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

[digikam] [Bug 376489] Pentax K-5

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
Note : read metadata is done by Exiv2 shared lib in background. Can you
reproduce the crash with Exiv2 command line tool when you read a KF5 Raw file ?

Gilles Caulier

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

[digikam] [Bug 376489] Pentax K-5

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Can you share some K5 RAW files through the cloud to reproduce the dysfunction
?

Gilles Caulier

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

[kmail2] [Bug 376520] New: KMail forget to display html mail and fetch pics set in global settings

[Francois Terblanche]

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

Bug ID: 376520
   Summary: KMail forget to display html mail and fetch pics set
in global settings
   Product: kmail2
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: f...@global.co.za
  Target Milestone: ---

When selecting a mail in the list, the message view pane is showing the plain
text mail and not loading html and remote content as set in the global
settings.
When I open the settings and un-select and re-select the ¨Prefer HTML to plain
text" and ¨Allow messages to load external references from the Internet¨ the
html message is displayed.
rpm is kmail5-16.08.2-1.1.x86_64 (opensuse leap 42.2)

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

[Martin Gräßlin]

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

--- Comment #8 from Martin Gräßlin  ---
The screen locks before the suspend. From my investigation the issues seems to
be in the graphics driver. It just shows the wrong buffer on wake up.

If you are on Intel make sure to use the xorg-modesettings driver!

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

[konsole] [Bug 376456] deleting history should delete the history file

[LtWorf]

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

Salvo "LtWorf" Tomaselli  changed:

   What|Removed |Added

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

--- Comment #2 from Salvo "LtWorf" Tomaselli  ---
Hm, I have been having this issue for a while on yakuake, but I can't seem to
reproduce. I'll close this and make a new one if it happens again.

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

[kdevelop] [Bug 375849] Show annotate on current document doesn't work in a git worktree

[Sven Brauch]

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

--- Comment #4 from Sven Brauch  ---
Seems a bit strange, first you check whether the file does not exist, then you
open it? ;)
But otherwise looks good, it'd be great if you could test it and put it on
phabricator.kde.org.

Having a development setup is actually quite simple, you can either just use
the KDevelop you work on for working as well (that works fine with
--pick-session) or use the AppImage we provide on kdevelop.org/download.

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

[plasmashell] [Bug 376517] Problems with global menu

[Nikita Skovoroda]

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

Nikita Skovoroda  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

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

[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view

[bugzilla_noreply]

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

--- Comment #5 from caulier.gil...@gmail.com ---
Maik,

If i remember, the Enter key must be catch by Captions/Tags right sidebar.
There is an event handler about keys.

Gilles

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

[plasmashell] [Bug 376517] Problems with global menu

[Nikita Skovoroda]

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

Nikita Skovoroda  changed:

   What|Removed |Added

 CC||chalk...@gmail.com

--- Comment #2 from Nikita Skovoroda  ---
As I already mentioned in https://github.com/electron/electron/issues/8455, Kai
Uwe Broulik told me that the issue is on the Electron side, and that it
shouldn't emit LayoutUpdated signals when nothing was actually changed.

I don't feel entitled to close this issue, though, so lets wait for someone
else to respond.

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

[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view

[Bill Goodman]

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

--- Comment #4 from Bill Goodman  ---
There is a configuration setting (Views>Icons>Thumbnail click action) which
selects either preview or image editor. This seems to be for a "double-click"
action in spite of the name saying "click".

It seems natural to me for the ENTER key to do the same action that
double-click does in this context.

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

[plasmashell] [Bug 376517] Problems with global menu

[Francisco Cribari]

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

--- Comment #1 from Francisco Cribari  ---
See also https://github.com/electron/electron/issues/8455

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

[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
I can confirm the behavior from the Enter key on Linux. Actually, the F3 key is
to call the preview. There is really no code that prompts the Enter key for the
preview. I look at it.

Maik

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

[valgrind] [Bug 376518] Solaris: unhandled fast trap getlgrp(6)

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

 CC||iv...@ivosh.net
   Assignee|jsew...@acm.org |iv...@ivosh.net
Summary|solaris 11.3 : unhandled|Solaris: unhandled fast
   |amd64-solaris syscall:  |trap getlgrp(6)
   |fast:6  |

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[bugzilla_noreply]

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

--- Comment #59 from caulier.gil...@gmail.com ---
Excelent. Thanks a lot Jan.

I will have plenty of time while this week end to review this patch for next
5.5.0 release.

Gilles

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[Jan Wolter]

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

Jan Wolter  changed:

   What|Removed |Added

 Attachment #103660|0   |1
is obsolete||

--- Comment #58 from Jan Wolter  ---
Created attachment 104043
  --> https://bugs.kde.org/attachment.cgi?id=104043=edit
Reworked patch

Hi Gilles,
attached is the reworked patch, which behaves exactly as the mime config now.
The settings are directly stored in SQLite DB. The @eaDir is now ignored by
default, but users are able to include it by prefixing it with a minus (the
same behaviour as in mime config).

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

[cantor] [Bug 354772] Cantor: hardcoded include of luajit-2.0/lua.hpp

[Filipe Saraiva]

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

Filipe Saraiva  changed:

   What|Removed |Added

 Status|VERIFIED|RESOLVED
 Resolution|REMIND  |FIXED
  Latest Commit||https://commits.kde.org/can
   ||tor/0b6f7a5721e779dc6f67bc2
   ||2d5b2511d010f19da

--- Comment #6 from Filipe Saraiva  ---
Git commit 0b6f7a5721e779dc6f67bc22d5b2511d010f19da by Filipe Saraiva, on
behalf of Vadim A. Misbakh-Soloviov.
Committed on 15/02/2017 at 18:21.
Pushed by filipesaraiva into branch 'master'.

Fix the hardcoded include for lua backend

Currently Cantor has a hardcoded include to get lua.hpp library.
This patch fix the search to include different versions of lua
library. The hardcoded solution is no more necessary.
Differential Revision: https://phabricator.kde.org/D4588

M  +10   -11   cmake/FindLuaJIT.cmake
M  +1-1src/backends/lua/luaexpression.cpp
M  +1-1src/backends/lua/luahelper.cpp
M  +1-1src/backends/lua/luasession.h

https://commits.kde.org/cantor/0b6f7a5721e779dc6f67bc22d5b2511d010f19da

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

[konsole] [Bug 373440] konsole --new-tab opens window instead

[Wolfgang Bauer]

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

--- Comment #26 from Wolfgang Bauer  ---
(In reply to Martin Sandsmark from comment #25)
> My personal opinion is that the potential data loss that can result from a
> single konsole window crashing and taking all the other instances with it is
> a bigger problem than --new-tab not working.
Ok, fair enough.
I was just thinking out loud.

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

[bugzilla_noreply]

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

--- Comment #7 from m...@etruscott.co.uk ---
I forgot to add that it happens when I close the lid and the laptop suspends
rather than when it suspends through a command or a time out.

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

[bugzilla_noreply]

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

m...@etruscott.co.uk changed:

   What|Removed |Added

 CC||m...@etruscott.co.uk

--- Comment #6 from m...@etruscott.co.uk ---
I still have this issue on 5.9.2 running on a lenovo yoga laptop with intel
integrated graphics.  does the computer suspend before the screen can lock? If
so can this be modified as it is clearly a terrible confidentiality issue.

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

[krusader] [Bug 375639] Quick search only let type one vocal with accent mark at first place

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kru
   ||sader/210ca94555bd8d6213f11
   ||a605456c8895da34fe3
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Alex Bikadorov  ---
Git commit 210ca94555bd8d6213f11a605456c8895da34fe3 by Alexander Bikadorov.
Committed on 14/02/2017 at 15:52.
Pushed by abikadorov into branch 'master'.

Panel: don't switch focus to panel view when typing in search bar

FIXED: [ 375639 ] Allow typing special characters (e.g. with accent or acute)
in search bar

M  +21   -26   krusader/Panel/krsearchbar.cpp

https://commits.kde.org/krusader/210ca94555bd8d6213f11a605456c8895da34fe3

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

[konsole] [Bug 373440] konsole --new-tab opens window instead

[Martin Sandsmark]

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

--- Comment #25 from Martin Sandsmark  ---
My personal opinion is that the potential data loss that can result from a
single konsole window crashing and taking all the other instances with it is a
bigger problem than --new-tab not working.

Anyhow, it seems like this is an issue with KDBusService. It doesn't notice the
existing Konsole process if that one was launched with KDBusService::Multiple.
We could do like Okular and implement the single application functionality
ourselves, or do the same as Okular in KDBusService. I'm not sure what is
appropriate for KDBusService.

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

[kmail2] [Bug 376519] New: Check Mail on Startup does not work

[bugzilla_noreply]

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

Bug ID: 376519
   Summary: Check Mail on Startup does not work
   Product: kmail2
   Version: 5.4.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ianse...@btinternet.com
  Target Milestone: ---

I have configured it to happen on my email accounts and it does not work.  It
does work when using accounts that i have been using for a long time.
This has started to happen on a new user with a blank database to which i added
an account i use for mailing lists only. The database populated with some of
the latest emails in the mailing lists. 
I had to create a new user with a empty email database because i could no
longer use kmail without getting "Retrieving folders.." hang on a current user.

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Yichao Yu]

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

--- Comment #10 from Yichao Yu  ---
I assume by that you mean https://phabricator.kde.org/D3602 ?
I didn't want to comment on a merged pull request so I opened a bug report.
I'll comment there instead.

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

[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"

[bugzilla_noreply]

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

ianse...@btinternet.com changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[konsole] [Bug 373440] konsole --new-tab opens window instead

[Wolfgang Bauer]

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

--- Comment #24 from Wolfgang Bauer  ---
I made an interesting observation (I think):
"konsole --new-tab" only opens a new window when the existing one has been
started "normally".

If you run "konsole --new-tab" again (or start the first konsole with
"--new-tab" already), it will indeed open a new tab as expected (with the fix
from comment#12 that is, without it it will still open a new window).

OTOH, maybe it would be a good idea to revert the change to use separate
processes or at least enable "Run all Konsole windows in a single process" by
default until the problems are fixed?
(dragging and dropping tabs between windows doesn't work either with separate
processes)
Just wondering...

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

[valgrind] [Bug 376455] Solaris: unhandled syscall lgrpsys(180)

[Ivo Raisr]

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

--- Comment #8 from Ivo Raisr  ---
Please do 'svn update' so your source tree gets also revision r16226.
Then do './autogen.sh && ./configure && make --quiet check' again.

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

[valgrind] [Bug 376518] New: solaris 11.3 : unhandled amd64-solaris syscall: fast:6

[Matthieu Longo]

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

Bug ID: 376518
   Summary: solaris 11.3 : unhandled amd64-solaris syscall: fast:6
   Product: valgrind
   Version: 3.13 SVN
  Platform: Other
OS: Solaris
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: mlo...@murex.com
  Target Milestone: ---

Platform:
SunOS dell747srv 5.11 11.3 i86pc i386 i86pc Solaris

--00:00:06:20.881 8667-- WARNING: unhandled amd64-solaris syscall: fast:6
--00:00:06:20.881 8667-- You may be able to write your own handler.
--00:00:06:20.881 8667-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--00:00:06:20.881 8667-- Nevertheless we consider this a bug.  Please report
--00:00:06:20.881 8667-- it at http://valgrind.org/support/bug_reports.html.

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

[frameworks-knotifications] [Bug 375130] the sound settings are ignored and restored back to defaults

[bugzilla_noreply]

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

thomas.ro...@t-online.de changed:

   What|Removed |Added

 CC||thomas.ro...@t-online.de

--- Comment #4 from thomas.ro...@t-online.de ---
when I press Shift-Delete in Dolphin, or use the context-menu, to delete some
file, the confirmation dialog appears and Sound is played at 100%;
Sound settings appear unchanged to me;
In Gwenview Shift-Delete doesnt work( misconf? ), with context-menu no Sound.
In sysconf->notifications found no matching entry

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