date:20170210

[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5

2017-02-10 Thread Ural

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

--- Comment #5 from Ural  ---
The update 16.12.2 also failed, until I enabled -fPIC.
without PIE with fPIC all compiled fine.

Thanks

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

[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5

2017-02-10 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #4 from Laurent Montel  ---
As to gentoo :)
It compiles fine here.

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

[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts

2017-02-10 Thread Martin Gräßlin

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

--- Comment #3 from Martin Gräßlin  ---
Am 10. Februar 2017 21:01:10 MEZ schrieb Igor Poboiko
:
>https://bugs.kde.org/show_bug.cgi?id=375518
>
>Igor Poboiko  changed:
>
>   What|Removed |Added
>
> CC||igor.pobo...@gmail.com
>
>--- Comment #2 from Igor Poboiko  ---
>Same here with russian layout (which is obviously completely different
>from
>english).
>
>(In reply to Martin Gräßlin from comment #1)
>> Now the problem is tricky. Do you know whether there is a key in the
>layout
>> which renders a "k"? Or whether the k key actually generates multiple
>> keysyms? If it generated kappa and k, we could change the code to
>support
>> all syms.
>
>I suppose Greek layout just doesn't have a "k" symbol at all. Does such
>layouts
>even exist (where the same symbol is placed on the some place in one
>layout and
>on another place on second layout)? 
>
>Can we just bind it not to the symbol but to key ("scan code") instead?

Unfortunately not. It's all keysym based.

>(however, it might break if user attaches another keyboard...)
>Or just map everything to English layout? (it might be weird if user
>isn't
>familiar with latin alphabet)

Requires the English layout to be part of the Keymap. So not a general
solution.
>Or maybe iterate over all configured layouts and check if pressed key
>code
>corresponds to a shortcut on any of it?

In general I like this idea, but I fear it's technically not possible.

I think the best solution would be to start translating the shortcuts.

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

[plasmashell] [Bug 376328] Plasma crashes when i click the activity button on the desktop

2017-02-10 Thread Punky

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

Punky  changed:

   What|Removed |Added

 CC||pyn...@gmail.com

--- Comment #1 from Punky  ---
Same or similar to my bug report:

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

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

[kmymoney] [Bug 376339] New: frameworks branch: Press ENTER on manual price entry does not save the new price

2017-02-10 Thread Robby Engelmann

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

Bug ID: 376339
   Summary: frameworks branch: Press ENTER on manual price entry
does not save the new price
   Product: kmymoney
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: robby.engelm...@igfs-ev.de
  Target Milestone: ---

As stated in the summary.:

-->Prices -->New -->Enter new price -->hit ENTER --> old price is kept
-->Prices -->New -->Enter new price  -->click OK --> new price is taken

Expected: New price taken on ENTER and OK-Click.

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

[plasmashell] [Bug 376000] Cannot download look and feel themes

2017-02-10 Thread Samim Pezeshki

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

--- Comment #3 from Samim Pezeshki  ---
(In reply to Tony from comment #2)
> (In reply to Samim Pezeshki from comment #0)
> > Hi,
> > 
> > In "Look and Feel" system settings I click on "Get New Looks". I install one
> > of the new look and feel themes for KDE 5.9. The "Install" button becomes
> > "Installing" and then "Uninstall" meaning the theme is downloaded and
> > installed. But the new theme is not added to my look and feel themes.
> > 
> > If I go and install it again, it asks "Overwrite existing file in /tmp/***
> > ?" And the same thing happens.
> > 
> > Thanks
> 
> If the file you are about to download is not hosted in
> https://store.kde.org, installing this way may encounter issues.
> 
> Click on the name of the theme so it opens in your browser, hit the "file"
> tab then "?" right to the "install" bottom and fallow the instructions.
> 
> This may help you for the specific theme you want to install.

I did as you said, in the "?" button it was told to insall xdgurl. I installed
xdgurl and clicked on the "install" button as instructed. A dialog opened "Do
you want to install XXX?". I clicked OK, download finished and a dialog
appeared "Installation successful". I clicked on "Open".  It opened
"~/.local/share/plasma/look-and-feel/", but the directory is empty and the
theme is not in my "Look and Feel" themes. Even by downloading and manually
unzipping the theme to its place it is not shown.

After some tinkering it seems that I have problems only with some themes using
xdgurl. Can themes be platform specific or something?

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

2017-02-10 Thread rbugman28

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

--- Comment #5 from rbugma...@yahoo.com  ---
Created attachment 103966
  --> https://bugs.kde.org/attachment.cgi?id=103966=edit
1.png

--- Comment #6 from rbugma...@yahoo.com  ---
Created attachment 103967
  --> https://bugs.kde.org/attachment.cgi?id=103967=edit
digikam54.txt

--- Comment #7 from rbugma...@yahoo.com  ---
Created attachment 103968
  --> https://bugs.kde.org/attachment.cgi?id=103968=edit
2.png

--- Comment #8 from rbugma...@yahoo.com  ---
Created attachment 103969
  --> https://bugs.kde.org/attachment.cgi?id=103969=edit
3.png

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

2017-02-10 Thread rbugman28

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

--- Comment #4 from rbugma...@yahoo.com  ---
Ok,3.5 works great,I will continue to use, fine product, I rave to anyone who
listens, very nice!
*3.5  opening 5.4 database ( I expected this - no worries)
get error 1 and see 35.txt
*5.4 opening 3.5 databasesorry, not sure how to run appimage using console see
54.txtset database: /media/bugman/USB20FD, scan collections start (wait 20
min)all albums are there-check, all digikam tags are there-check
open Album=Vehicles note tag 'mustang' see 2
set tagview = mustang ; no folders , no images see 3, error: storage location
of image is not available

possibilities:    1.) 3.5 db is corrupt  - how do I fix it? (without losing
data?)

How can I help?Thanks, Rick














On Thursday, February 9, 2017 6:28 AM, Maik Qualmann
 wrote:


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

Maik Qualmann  changed:

          What    |Removed                    |Added

                CC|                            |metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
Can you make a screenshot or screencast? We had a similar behavior (is fixed) a
long time ago when the thumbnail view was sorted by date. The problem I have
never seen here again and is also not to reproduce.

Maik

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

[krunner] [Bug 376338] New: The new plasma 5.9 Krunner and application launcher unable to find a number of applications.

2017-02-10 Thread bugzilla_noreply

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

Bug ID: 376338
   Summary: The new plasma 5.9 Krunner and application launcher
unable to find a number of applications.
   Product: krunner
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: kzho...@gmail.com
  Target Milestone: ---

After upgrading to the new plasma 5.9, Krunner and application launcher unable
to find a number of applications. For example, when I type `system` or `system
setting` in the search dialog, system setting does not pop up. However, system
setting is in the applications menu and launching from terminal also works.

Moreover, I can confirm the `.destop` files are also intact in the
`/usr/share/applications` directory.

Initially I got very frustrated because I mainly search the app when I want to
run it. Recently I investigated a bit more into the issue and took a closer
look at the folder these `.desktop` files belong. It turns out that all
applications that are unsearchable in the launcher or krunner have more than
one `.desktop` files in the `\usr\share\applications` directory. For example,
the system setting application can be launched from both
`kdesystemsettings.desktop' file and 'systemsettings.desktop' file, i.e., both
point to the same thing application if you take a look at the
`Exec=balabalabla` part. Now, if I delete one of them, the issue goes away.
Okular also exhibit similar issues, there are quite a few of `.desktop` files
with different file names pointing to the same app. Since I only encountered
this in plasma 5.9 and have never really looked at the directory as carefully,
I am not sure whether the bug belongs to Krunner or the fact that there are
multiple `.desktop` files pointing to the same application in the
`/usr/share/applications` directory is itself a bug. Just want to point it out
there since it was really a quite frustrating bug :) Feel free to rebrand this
bug as I am not entirely sure which part of KDE it belongs.

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

[plasmashell] [Bug 375937] regression: task manager group menu no longer shows all windows

2017-02-10 Thread bugzilla_noreply

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

--- Comment #4 from n...@leippe.com ---
Just updated to 5.9.1 and there is still no scroll bar for me.

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

[krunner] [Bug 376337] New: KRunner crash on startup

2017-02-10 Thread Michael

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

Bug ID: 376337
   Summary: KRunner crash on startup
   Product: krunner
   Version: 5.7.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: jordan.mym...@gmail.com
  Target Milestone: ---

Application: krunner (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-37-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
Fresh install of Kubuntu, installed VLC, now the system boots to a black screen

The crash can be reproduced every time.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcfd8a558c0 (LWP 1439))]

Thread 3 (Thread 0x7fcfbf373700 (LWP 1446)):
#0  0x7fcfd51dec8d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fcfd268ec80 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcfd264a485 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcfd264a974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcfd264aaec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fcfd5b114ab in QEventDispatcherGlib::processEvents
(this=0x7fcfb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#6  0x7fcfd5ab90fa in QEventLoop::exec (this=this@entry=0x7fcfbf372cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fcfd58ded43 in QThread::exec (this=this@entry=0x7fcfd8bebd60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#8  0x7fcfd8b77575 in QDBusConnectionManager::run (this=0x7fcfd8bebd60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:171
#9  0x7fcfd58e3c68 in QThreadPrivate::start (arg=0x7fcfd8bebd60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#10 0x7fcfd2fbd6ca in start_thread (arg=0x7fcfbf373700) at
pthread_create.c:333
#11 0x7fcfd51ef0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fcfc541c700 (LWP 1445)):
#0  0x7fcfd51e30bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fcfd46cbc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fcfd46cd8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fcfc7da2299 in QXcbEventReader::run (this=0x5556e904c750) at
qxcbconnection.cpp:1325
#4  0x7fcfd58e3c68 in QThreadPrivate::start (arg=0x5556e904c750) at
thread/qthread_unix.cpp:341
#5  0x7fcfd2fbd6ca in start_thread (arg=0x7fcfc541c700) at
pthread_create.c:333
#6  0x7fcfd51ef0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fcfd8a558c0 (LWP 1439)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x7fcfd511e3ea in __GI_abort () at abort.c:89
#8  0x7fcfd58cacc1 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1648
#9  QMessageLogger::fatal (this=this@entry=0x7ffde58da170,
msg=msg@entry=0x7fcfd8a4d8a4 "Could not initialize GLX") at
global/qlogging.cpp:790
#10 0x7fcfd8a4aca9 in QGLXContext::init (this=0x5556e9090b80,
screen=0x5556e904ee60, share=) at qglxintegration.cpp:309
#11 0x7fcfd8a488fb in QXcbGlxIntegration::createPlatformOpenGLContext
(this=, context=0x7ffde58da2c0) at qxcbglxintegration.cpp:187
#12 0x7fcfc7da8be1 in QXcbIntegration::createPlatformOpenGLContext
(this=, context=0x7ffde58da2c0) at qxcbintegration.cpp:224
#13 0x7fcfd5e4d02d in QOpenGLContext::create
(this=this@entry=0x7ffde58da2c0) at kernel/qopenglcontext.cpp:606
#14 0x7fcfd8a4b4e6 in QGLXContext::queryDummyContext () at
qglxintegration.cpp:675
#15 0x7fcfd8a4b6c1 in QGLXContext::supportsThreading () at
qglxintegration.cpp:706
#16 0x7fcfd7c56b2b in QSGRenderLoop::instance() () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x7fcfd7c899f5 in QQuickWindowPrivate::init(QQuickWindow*,
QQuickRenderControl*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#18 0x7fcfd87c026c in PlasmaQuick::Dialog::Dialog(QQuickItem*) () from
/usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5
#19 0x5556e73560ae in View::View (this=0x7ffde58da7c0) at
./krunner/view.cpp:57
#20 0x5556e735497b in main (argc=, argv=) at
./krunner/main.cpp:83

Possible duplicates by query: bug 373371, bug 372178, bug 364721, bug 364342,
bug 362777.

Reported using DrKonqi

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

[digikam] [Bug 376331] Path when saving/opening presentation files should be remebered

2017-02-10 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|SlideShow   |Presentation
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 376330] "Move to bottom/top" buttons, d and "Print title" for presentation

2017-02-10 Thread bugzilla_noreply

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|SlideShow   |Presentation

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

[dolphin] [Bug 376336] New: no icons as root user

2017-02-10 Thread Bronson

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

Bug ID: 376336
   Summary: no icons as root user
   Product: dolphin
   Version: 16.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bronsonmath...@gmail.com
  Target Milestone: ---

No folders or icons appear in dolphin when using as root user.
Sometimes its handy to load dolphin as root user to make some quick file
changes. But without icons or folders, its a bit awkward to navigate.

To test:
sudo dolphin

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

[plasmashell] [Bug 376000] Cannot download look and feel themes

2017-02-10 Thread Tony

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #2 from Tony  ---
(In reply to Samim Pezeshki from comment #0)
> Hi,
> 
> In "Look and Feel" system settings I click on "Get New Looks". I install one
> of the new look and feel themes for KDE 5.9. The "Install" button becomes
> "Installing" and then "Uninstall" meaning the theme is downloaded and
> installed. But the new theme is not added to my look and feel themes.
> 
> If I go and install it again, it asks "Overwrite existing file in /tmp/***
> ?" And the same thing happens.
> 
> Thanks

If the file you are about to download is not hosted in https://store.kde.org,
installing this way may encounter issues.

Click on the name of the theme so it opens in your browser, hit the "file" tab
then "?" right to the "install" bottom and fallow the instructions.

This may help you for the specific theme you want to install.

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

[plasmashell] [Bug 376332] global keyboard shortcut for dolphin doesnt work

2017-02-10 Thread Bronson

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

Bronson  changed:

   What|Removed |Added

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

--- Comment #1 from Bronson  ---
this started working after a reboot!

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

[yakuake] [Bug 376335] New: Yakuake crashes with custom key assignment

2017-02-10 Thread Ertugrul Karademir

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

Bug ID: 376335
   Summary: Yakuake crashes with custom key assignment
   Product: yakuake
   Version: 3.0.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: ekarade...@gmail.com
  Target Milestone: ---

Application: yakuake (3.0.2)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.33-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I am using Manjaro with Gnome-Boxes on Ubuntu Gnome 16.04. In oder to release
the conflict with Ctrl+Alt combinations, I assigned Meta+Alt+Down for growing
the Yakuake window. However the application crashes when I execute the shorcut.

Manjaro Linux on Gnome-Boxes
KernelVersion 4.4.33-1-MANJARO

- Custom settings of the application:
Assigned Meta+Alt+Down (Also Up, Left, and Right) instead of Ctrl+Alt+Down (Up,
Left, and Right)

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f12433cc7c0 (LWP 817))]

Thread 7 (Thread 0x7f1218452700 (LWP 917)):
#0  0x7f123a3a210f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f121df5aec3 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f121df5ad27 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f1218c53700 (LWP 916)):
#0  0x7f123a3a210f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f121df5aec3 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f121df5ad27 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1219454700 (LWP 915)):
#0  0x7f123a3a210f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f121df5aec3 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f121df5ad27 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1219c55700 (LWP 914)):
#0  0x7f123a3a210f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f121df5aec3 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f121df5ad27 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1227fff700 (LWP 857)):
#0  0x7f123deb848d in poll () from /usr/lib/libc.so.6
#1  0x7f1238ad1786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f1238ad189c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f123e7da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f123e78423a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f123e5a70f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f1240372e55 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f123e5abd78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f122ecb0700 (LWP 846)):
#0  0x7f123deb848d in poll () from /usr/lib/libc.so.6
#1  0x7f123c1818e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f123c183679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f1230bf1449 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f123e5abd78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f123a39c454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f123dec17df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f12433cc7c0 (LWP 817)):
[KCrash Handler]
#6  0x7f123f5f1c2b in QSplitter::indexOf(QWidget*) const () from
/usr/lib/libQt5Widgets.so.5
#7  0x004334b8 in ?? ()
#8  0x00416d69 in ?? ()
#9  0x7f123e7b1659 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#10 0x7f123f45f442 in QAction::triggered(bool) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f123f461e30 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQt5Widgets.so.5
#12 0x7f123f4627ac in QAction::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f123f465e0c in

[kwin] [Bug 375993] The 'Show Desktop' action doesn't restore focus

2017-02-10 Thread Tony

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #1 from Tony  ---
I have the same setup as you, cn't reproduce on neon unstable. Maybe is already
fixed?

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

[www.kde.org] [Bug 376334] The images in the slideshow on the main page display incorrectly at high resolutions

2017-02-10 Thread Beer

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

--- Comment #1 from Beer  ---
Forgot to mention.. Chrome 57.0.2987.37 beta (64-bit).  Same exact thing
happens in Firefox.

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

[www.kde.org] [Bug 376334] New: The images in the slideshow on the main page display incorrectly at high resolutions

2017-02-10 Thread Beer

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

Bug ID: 376334
   Summary: The images in the slideshow on the main page display
incorrectly at high resolutions
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: arco...@gmail.com
  Target Milestone: ---

At 2560x1440, the images on the slideshow get offset incorrectly. It's probably
much worse at 4k

Group photo shifted down too low: http://i.imgur.com/KyMv4xQ.png
KDE Slimbook shifted up too high: http://i.imgur.com/CLC1xFu.jpg

All of the images have inconsistencies but those are the two most noticeable.  

New site looks great, nice job.

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

[kmail2] [Bug 376333] New: KMail crashed while opening on KDE Neon distribution (fresh install)

2017-02-10 Thread bugzilla_noreply

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

Bug ID: 376333
   Summary: KMail crashed while opening on KDE Neon distribution
(fresh install)
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: mhdmath...@gmail.com
  Target Milestone: ---

Application: kmail (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

-- Information about the crash:
- What I was doing when the application crashed:
After installing KMail and MySQL, KMail crashes every time when opened.

- Unusual behavior I noticed:
When opening from terminal, these lines printed out:

~$: kmail
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.
Could not find QtWebEngineProcess
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/bin pid = 6550
KCrash: Arguments: /usr/bin/kmail 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...

[1]+  Stopped kmail
~$:

- Custom settings of the application:
I haven't changed any setting of the application. Just changed the couple of
plasma themes. But I guess that's not the problem.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0335973a00 (LWP 6172))]

Thread 5 (Thread 0x7f0329dec700 (LWP 6181)):
#0  0x7f0365279b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0359cde38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0359cde49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0365daf75b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0365d5a0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0365b89f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f035ba376ba in start_thread (arg=0x7f0329dec700) at
pthread_create.c:333
#8  0x7f036528582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f032a5ed700 (LWP 6177)):
#0  0x7f0365dad3d0 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f0365dad945 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0365daed0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0359cdd91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0359cde2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f0359cde49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f0365daf75b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0365d5a0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0365b89f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f035ba376ba in start_thread (arg=0x7f032a5ed700) at
pthread_create.c:333
#11 0x7f036528582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f032adee700 (LWP 6176)):
#0  0x7f0365279b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0359cde38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0359cde49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0365daf75b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0365d5a0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0365b89f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f035ba376ba in start_thread (arg=0x7f032adee700) at
pthread_create.c:333
#8  0x7f036528582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f032bfff700 (LWP 6175)):
#0

[digikam] [Bug 150531] SCHEMA : add album password-protect feature

2017-02-10 Thread Bill Goodman

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

Bill Goodman  changed:

   What|Removed |Added

 CC||bg+k...@cyclos.com

--- Comment #25 from Bill Goodman  ---
I have a related but somewhat different request.

I would like to be able to launch digikam for a friend or child to browse
without allowing them to make any modifications. Digikam is a great tool for
searching for interesting photos in many different ways using tags, etc. But I
would never allow a child to access the system this way because they could do
massive damage to the tags, captions and other info in the database and photos.

I would like to have a protected mode where after "locking" digiKam, no changes
to the database or photos would be allowed until a password was supplied.

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

[plasmashell] [Bug 376332] New: global keyboard shortcut for dolphin doesnt work

2017-02-10 Thread Bronson

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

Bug ID: 376332
   Summary: global keyboard shortcut for dolphin doesnt work
   Product: plasmashell
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bronsonmath...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Adding a global keyboard shortcut for Dolphin doesnt launch it. Ive tried
various combination of shortcuts without luck. 

Doing the same for the konsole app has no issue with this, so it looks to be
related to dolphin only?

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

[digikam] [Bug 376331] New: Path when saving/opening presentation files should be remebered

2017-02-10 Thread Wolfgang Scheffner

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

Bug ID: 376331
   Summary: Path when saving/opening presentation files should be
remebered
   Product: digikam
   Version: 5.5.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: SlideShow
  Assignee: digikam-de...@kde.org
  Reporter: wscheffn...@gmail.com
  Target Milestone: ---

Currently when saving or opening a presentation file in the presentation editor
the dialog comes up with /home/~/documents/, which is not very useful. At least
I don't wont to use that directory for things like this because it would become
a mess. I have the slideshows in a subfolder of the (my) pictures folder.
Remembering the path would be better, would save you a lot of clicks when
working on an extensive slideshow since one will hardly do it in one go - at
least not me :-)
In cases like this another solution might be to have default path settings
somewhere in Configure digiKam.

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

[digikam] [Bug 376330] New: "Move to bottom/top" buttons, d and "Print title" for presentation

2017-02-10 Thread Wolfgang Scheffner

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

Bug ID: 376330
   Summary: "Move to bottom/top" buttons, d and "Print title"
for presentation
   Product: digikam
   Version: 5.5.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: SlideShow
  Assignee: digikam-de...@kde.org
  Reporter: wscheffn...@gmail.com
  Target Milestone: ---

When working on slideshows in the presentation editor there are "move to top"
and "move to bottom" buttons missing in the Main Settings tab. The possibility
to d images into the editor from the main digiKam window would improve the
editing process (which is nasty enough anyway) even more.
And in the "Content" section of this tab there is "Print title" missing which
is possible in the non-presentation slideshows. And when the title is printed
is should appear on top of the caption, not below. This applies also to the
non-presentation slideshows.

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

[ktorrent] [Bug 376329] New: KTorrent quits unexpectly

2017-02-10 Thread bugzilla_noreply

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

Bug ID: 376329
   Summary: KTorrent quits unexpectly
   Product: ktorrent
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: kzho...@gmail.com
  Target Milestone: ---

Application: ktorrent (5.0.1)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was downloading Arch Linux ISO using the official torrent, to be more
specific: I clicked on the torrent and the download seem to start, at least an
empty file with the `*.iso` name is placed into the download directly, five
seconds later, it crashes. This is a brand new Arch Linux install, never
installed anything weried and not customizations. The package is from Arch
Linux official repo.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f73e9545840 (LWP 29904))]

Thread 25 (Thread 0x7f735d7fa700 (LWP 29937)):
#0  0x7f73e3574f19 in syscall () at /usr/lib/libc.so.6
#1  0x7f73e4176865 in QBasicMutex::lockInternal() () at
/usr/lib/libQt5Core.so.5
#2  0x7f73e4176922 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#3  0x7f73e8e11d3c in  () at /usr/lib/libktorrent.so.6
#4  0x7f73e8e12589 in  () at /usr/lib/libktorrent.so.6
#5  0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 24 (Thread 0x7f735dffb700 (LWP 29936)):
[KCrash Handler]
#6  0x7f73e4200eac in QString::indexOf(QChar, int, Qt::CaseSensitivity)
const () at /usr/lib/libQt5Core.so.5
#7  0x7f73e8e55f66 in  () at /usr/lib/libktorrent.so.6
#8  0x7f73e8e56d94 in  () at /usr/lib/libktorrent.so.6
#9  0x7f73e8e54508 in  () at /usr/lib/libktorrent.so.6
#10 0x7f73e8e552a3 in  () at /usr/lib/libktorrent.so.6
#11 0x7f73e8e1787f in  () at /usr/lib/libktorrent.so.6
#12 0x7f73e8e13a24 in  () at /usr/lib/libktorrent.so.6
#13 0x7f73e8e129ca in  () at /usr/lib/libktorrent.so.6
#14 0x7f73e8e12551 in  () at /usr/lib/libktorrent.so.6
#15 0x7f73e8e12589 in  () at /usr/lib/libktorrent.so.6
#16 0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#18 0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7f735e7fc700 (LWP 29935)):
#0  0x7f73deb764b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73e41804c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f73e417bbc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f735effd700 (LWP 29934)):
#0  0x7f73deb764b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73e41804c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f73e417bbc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f735f7fe700 (LWP 29933)):
#0  0x7f73deb764b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73e41804c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f73e417bbc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f735700 (LWP 29932)):
#0  0x7f73deb764b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73e41804c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f73e417bbc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f73e417f6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f73deb70454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f73e35797df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f737cff9700 (LWP 29931)):
#0  0x7f73deb764b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f73e41804c6 in QWaitCondition::wait(QMutex*, unsigned long) () at

[ksshaskpass] [Bug 376318] Regression: passwords no longer remembered, asks every time I open a shell

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
This is a regression in 5.9.1. There is a patch posted to bug 376228.

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

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

[ksshaskpass] [Bug 376228] git fails with "Unable to extract keyFile from phrase"

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||deve...@fuchsnet.ch

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

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

[plasmashell] [Bug 376328] New: Plasma crashes when i click the activity button on the desktop

2017-02-10 Thread Younes ERRATI

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

Bug ID: 376328
   Summary: Plasma crashes when i click the activity button on the
desktop
   Product: plasmashell
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: err...@hotmail.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.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I just click the button on the destop and Plasma crashes everytime.

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7fe69b5ef700 (LWP 7066)):
#0  0x7fe76ac8c999 in g_private_get () at /usr/lib/libglib-2.0.so.0
#1  0x7fe76ac6f5d0 in g_thread_self () at /usr/lib/libglib-2.0.so.0
#2  0x7fe76ac4665c in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe76ac47635 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe76ac4789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fe77074c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fe7706f589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fe770517a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fe773653025 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fe77051c6d8 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fe76f3e7454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fe76fe317df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fe6ae9c3700 (LWP 1170)):
#0  0x7fe76ac44777 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fe76ac46c2b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fe76ac476ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe76ac4789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fe77074c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fe7706f589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fe770517a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fe77051c6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe76f3e7454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe76fe317df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fe6c132f700 (LWP 1140)):
#0  0x7fe76ac8cdb0 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe76ac46c95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fe76ac476ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe76ac4789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fe77074c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fe7706f589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fe770517a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fe774207fd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7fe77051c6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe76f3e7454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe76fe317df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fe74bfff700 (LWP 1139)):
#0  0x7fe76f3ed10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe775efd234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fe775efd279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fe76f3e7454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fe76fe317df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fe756177700 (LWP 1133)):
#0  0x7fe76ac8cdd2 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe76ac4762d in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe76ac4789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe77074c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe7706f589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe770517a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe773653025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fe77051c6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe76f3e7454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe76fe317df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fe757fff700 (LWP 1008)):
#0  0x7fe76fe3e02f in __libc_enable_asynccancel () at /usr/lib/libc.so.6
#1  0x7fe76fe28482 in poll () at /usr/lib/libc.so.6

[kdenlive] [Bug 375186] Add Clip: Clip is invalid

2017-02-10 Thread Nicholas Sushkin

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

Nicholas Sushkin  changed:

   What|Removed |Added

 CC||nsush...@sushkins.net

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

[krita] [Bug 376327] Hue adjustment with spectrum zones

2017-02-10 Thread Alex

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

Alex  changed:

   What|Removed |Added

Summary|Hue adjustment on part of   |Hue adjustment with
   |spectrum|spectrum zones

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

[krita] [Bug 376327] New: Hue adjustment on part of spectrum

2017-02-10 Thread Alex

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

Bug ID: 376327
   Summary: Hue adjustment on part of spectrum
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: adjustment layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: ene...@gmail.com
  Target Milestone: ---

Is is useful when adjusting colors.

PS gives options inside hue/saturation tool to adjust 6 color zones
individually using slider with 4 control bars, 2 for zone and 2 for falloff:
http://www.entheosweb.com/photoshop/images/autumn_colors/autumn2-2b.jpg

Gimp can select zone but it's not possible to adjust zone itself:
https://docs.gimp.org/en/gimp-tool-hue-saturation.html
...similar to ps 2.5 tool:
https://en.wikipedia.org/wiki/File:PS_2.5_hue-saturation_tool.png

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

[Discover] [Bug 376241] software centre is empty

2017-02-10 Thread Matthias K .

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

Matthias K.  changed:

   What|Removed |Added

 CC||matth...@tenstral.net

--- Comment #5 from Matthias K.  ---
Please run `appstreamcli status` and attach the output.
You might also want to attach the output of
`sudo appstreamcli refresh --force --verbose`.

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

[plasmashell] [Bug 376324] Plasma crash when click on plasma 3 dots (named "Default" by default activitie)

2017-02-10 Thread Punky

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

--- Comment #2 from Punky  ---
Comment on attachment 103964
  --> https://bugs.kde.org/attachment.cgi?id=103964
Picture of "3 dot menu"

This is "3 dot menu" on which I click , plasmashell crashes.

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

[plasmashell] [Bug 376324] Plasma crash when click on plasma 3 dots (named "Default" by default activitie)

2017-02-10 Thread Punky

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

--- Comment #1 from Punky  ---
Created attachment 103964
  --> https://bugs.kde.org/attachment.cgi?id=103964=edit
Picture of "3 dot menu"

On this "3 dot menu" when click, plasma crashes. :)

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

[plasmashell] [Bug 376326] New: Plasma crashed while viewing Application Menu

2017-02-10 Thread bugzilla_noreply

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

Bug ID: 376326
   Summary: Plasma crashed while viewing Application Menu
   Product: plasmashell
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: destroyer2...@aim.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.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: I was browsing the Application
Menu attached to a panel on the top of my screen. 

Suddenly, all panels disappeared and aside from that, everything functioned
normally. After a few seconds, the panels reappeared.

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

Thread 21 (Thread 0x7ef887fff700 (LWP 11197)):
#0  0x7f39e58f948d in poll () at /usr/lib/libc.so.6
#1  0x7f39e0718786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f39e071889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f39e621d06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f39e61c689a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f39e5fe8a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f39e9124025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f39e5fed6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f39e4eb8454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f39e59027df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f38eddc5700 (LWP 11169)):
#0  0x7f39e07182e2 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#1  0x7f39e07187f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f39e071889c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f39e621d06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f39e61c689a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f39e5fe8a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f39e9124025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f39e5fed6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f39e4eb8454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f39e59027df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f38f1da2700 (LWP 1748)):
#0  0x7f39e4ebe10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f39e5fee58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f39347bc1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f39347c0988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7f39347c09e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7f39347bb263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7f39347be1f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#20 0x7f39e5fed6d8 in  () at /usr/lib/libQt5Core.so.5
#21 0x7f39e4eb8454 in start_thread () at /usr/lib/libpthread.so.0
#22 0x7f39e59027df in clone () at /usr/lib/libc.so.6

Thread 18

[frameworks-kdoctools] [Bug 376246] compilation requires xmllint but CMake doesnt' check for it

2017-02-10 Thread Luigi Toscano

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

Luigi Toscano  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #3 from Luigi Toscano  ---
Confirmed, see the proposed review https://phabricator.kde.org/D4558 .

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

[krita] [Bug 376325] New: Krita will not function with Astropad

2017-02-10 Thread AR

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

Bug ID: 376325
   Summary: Krita will not function with Astropad
   Product: krita
   Version: 3.1.2
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: ensignr...@gmail.com
  Target Milestone: ---

Created attachment 103963
  --> https://bugs.kde.org/attachment.cgi?id=103963=edit
Screenshot during bug

I am a Mac/iPad user and I use the Astropad App to draw into PS and other
illustration programs. However, Astropad doesn't seem to function with Krita. I
open the program, create a new document (it doesn't matter what type) I can
draw a line with my mouse but as soon as I switch to Astropad the function
changes to "grab" and all I can do is move the document around. Typically
Astropad functions exactly as a mouse but in Krita I only get this hand icon
moving the canvas around.

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

[kde-gtk-config] [Bug 376273] GTK 2.0 runtime message failed to retrieve property `gtk-primary-button-warps-slider'

2017-02-10 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||-gtk-config/4a06c4d34f2dd88
   ||59058618b1dbe9dbd6df9e9b8
   Version Fixed In||5.8.6
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Elvis Angelaccio  ---
Git commit 4a06c4d34f2dd8859058618b1dbe9dbd6df9e9b8 by Elvis Angelaccio.
Committed on 10/02/2017 at 22:49.
Pushed by elvisangelaccio into branch 'Plasma/5.8'.

Fix gtk-primary-button-warps-slider with GTK 2

Summary:
Replace true/false with 1/0. The former works only with GTK 3, but
breaks with GTK 2 apps.
FIXED-IN: 5.8.6

Test Plan: Tested with inkscape (which is gtk2); still works with gtk3 apps.

Reviewers: apol, broulik

Subscribers: plasma-devel

Tags: #plasma

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

M  +2-2src/abstractappearance.cpp

https://commits.kde.org/kde-gtk-config/4a06c4d34f2dd8859058618b1dbe9dbd6df9e9b8

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

[plasmashell] [Bug 376324] New: Plasma crash when click on plasma 3 dots (named "Default" by default activitie)

2017-02-10 Thread Punky

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

Bug ID: 376324
   Summary: Plasma crash when click on plasma 3 dots (named
"Default" by default activitie)
   Product: plasmashell
   Version: 5.9.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pyn...@gmail.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.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

When I click on "3 dots" menu in Plasma, plasma crash. This is not happening
every time when I click on that 3 dots (3 lines, or what is name of that menu
in plasma? ), but it happens often.

I am using Arch x64, Plasma 5.9.1

The crash can be reproduced sometimes.

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

Thread 14 (Thread 0x7f732183d700 (LWP 626)):
#0  0x7f73d3dc5dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f73d3d7fd60 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f73d3d806ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f73d3d8089c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f73d98eb06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f73d989489a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f73d96b6a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f73dd3fafd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f73d96bb6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f73d8fce7df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f7323f34700 (LWP 625)):
#0  0x7f73d8fc14ed in read () at /usr/lib/libc.so.6
#1  0x7f73d3dc4a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f73d3d80235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f73d3d80724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f73d3d8089c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f73d98eb06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f73d989489a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f73d96b6a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f73d96bb6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f73d8fce7df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f7324765700 (LWP 624)):
#0  0x7f73d3dc5dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f73d3d8069e in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f73d3d8089c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f73d98eb06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f73d989489a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f73d96b6a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f7325232385 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#7  0x7f73d96bb6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f73d8fce7df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f7329ca2700 (LWP 622)):
#0  0x7f73d857b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f732f64c9eb in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f732f64c847 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d8fce7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f732a4a3700 (LWP 621)):
#0  0x7f73d857b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f732f64c9eb in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f732f64c847 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d8fce7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f732aca4700 (LWP 620)):
#0  0x7f73d857b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f732f64c9eb in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f732f64c847 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f73d8575454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f73d8fce7df in

[kde-gtk-config] [Bug 376273] GTK 2.0 runtime message failed to retrieve property `gtk-primary-button-warps-slider'

2017-02-10 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||abouv...@student.42.fr

--- Comment #2 from Elvis Angelaccio  ---
*** Bug 374948 has been marked as a duplicate of this bug. ***

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

[kde-gtk-config] [Bug 374948] kde-gtk-config puts unknown property in ~/.gtkrc-2.0

2017-02-10 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---


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

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

[kde-gtk-config] [Bug 376273] GTK 2.0 runtime message failed to retrieve property `gtk-primary-button-warps-slider'

2017-02-10 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org
Version|5.9.0   |5.8.5

--- Comment #1 from Elvis Angelaccio  ---
Thanks for reporting

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

[systemsettings] [Bug 376323] New: Crash after setting GTK Theme and closing

2017-02-10 Thread Ravi Kumar Sharma

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

Bug ID: 376323
   Summary: Crash after setting GTK Theme and closing
   Product: systemsettings
   Version: 5.9.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ravisharma1...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.9.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:
Crash after setting GTK Theme and closing the system settings.

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70669fe8c0 (LWP 19010))]

Thread 4 (Thread 0x7f703cbd4700 (LWP 19020)):
#0  0x7f7063130b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f705e28638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f705e28649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7063a5075b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f70639fb0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f706382af64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7062187bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f706382fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f70603416ba in start_thread (arg=0x7f703cbd4700) at
pthread_create.c:333
#9  0x7f706313c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f704cdfa700 (LWP 19013)):
#0  0x7f705e2caa79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f705e285929 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f705e2862bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f705e28649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f7063a5075b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f70639fb0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f706382af64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7066b55735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f706382fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f70603416ba in start_thread (arg=0x7f704cdfa700) at
pthread_create.c:333
#10 0x7f706313c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f70553ec700 (LWP 19012)):
#0  0x7f7063130b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7060bb7c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f7060bb98d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f7057944d79 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f706382fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f70603416ba in start_thread (arg=0x7f70553ec700) at
pthread_create.c:333
#6  0x7f706313c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f70669fe8c0 (LWP 19010)):
[KCrash Handler]
#6  0x7f7062062025 in QV4::WeakValue::free() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f70620cecd9 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f7061f6874c in QV4::MemoryManager::sweep(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f7061f6a28c in QV4::MemoryManager::~MemoryManager() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f70620526f2 in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f7062189648 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f7062189769 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f7061fe7686 in QJSEngine::~QJSEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f70620f8265 in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7f70620f8319 in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#16 0x7f7063a26663 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f7063a2f814 in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18

[frameworks-plasma] [Bug 376322] New: krunner does not use colors from selected color scheme

2017-02-10 Thread Martin Koller

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

Bug ID: 376322
   Summary: krunner does not use colors from selected color scheme
   Product: frameworks-plasma
   Version: 5.27.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: kol...@aon.at
  Target Milestone: ---

Created attachment 103961
  --> https://bugs.kde.org/attachment.cgi?id=103961=edit
screenshot of colors kcm and krunner

Whatever colorscheme I select in the colors kcm, krunner (Alt-F2 search input
textfield) does not honor my settings.

See attached screenshot.
I selected Honeycomb and applied. It is used when I e.g. click the configure
button on the krunner (Alt-F2 and Left tool button), but it is not used inside
the text entry field.

The main problem I have here is also that it uses blue highlight color as
background and black as text color, although the selected-text color is white
to have good contrast. I don't know from where krunner takes that colors but
it's not from the selected scheme.

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

[Breeze] [Bug 376263] Color leak in title bar

2017-02-10 Thread bugzilla_noreply

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

--- Comment #4 from kzho...@gmail.com ---
(In reply to Hugo Pereira Da Costa from comment #3)
> (In reply to Christoph Feck from comment #2)
> > The problem described in comment #0 is with the active System Settings
> > window. Between the blue title bar and the gray window surface an orange
> > line is visible which should not be there.
> 
> If this is the issue, then this is not a bug, it is a feature.
> With all colour schemes, we use the "selection color" (here orange) as a
> separator line between the active window title bar, and the window content. 
> With the default breeze color scheme, this is the "blue" line you see
> between the dark title bar and the grey content.
> 
> ...
> But i too though this was more about the chrome window (which i then believe
> is more of a compositing bug/display driver, than window decoration bug),
> but then let us wait for the reporter to clarify what really is the bug.

Thanks for the reply. Yes, I meant the separator line between the active window
title bar. It is invisible when (In reply to Hugo Pereira Da Costa from comment
#3)
> (In reply to Christoph Feck from comment #2)
> > The problem described in comment #0 is with the active System Settings
> > window. Between the blue title bar and the gray window surface an orange
> > line is visible which should not be there.
> 
> If this is the issue, then this is not a bug, it is a feature.
> With all colour schemes, we use the "selection color" (here orange) as a
> separator line between the active window title bar, and the window content. 
> With the default breeze color scheme, this is the "blue" line you see
> between the dark title bar and the grey content.
> 
> ...
> But i too though this was more about the chrome window (which i then believe
> is more of a compositing bug/display driver, than window decoration bug),
> but then let us wait for the reporter to clarify what really is the bug.

Thank you for the reply. Yes, it is the issue with the pinkish separator. Thank
you for letting me know this is not a bug, I shall just change the selection
color then :)

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

[plasmashell] [Bug 376321] Action overlays are unintuitive

2017-02-10 Thread Kai Uwe Broulik

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

--- Comment #2 from Kai Uwe Broulik  ---
Created attachment 103962
  --> https://bugs.kde.org/attachment.cgi?id=103962=edit
Dolphin overlay vs Plasma FolderView

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

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

2017-02-10 Thread Cade Robinson

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

--- Comment #21 from Cade Robinson  ---
I think I was able to compile konsole 16.12.2 via the arch ABS system with the
new tab patch and the -e patch.
Assuming I did it correctly the new tab patch still opens a new window unless
you have "Run all Konsole windows in a single process" checked. So not sure
that is fixed?

With "Run all Konsole windows in a single process" checked and running
konsole --hold --new-tab -e ssh cadetest
will open a new tab and will run the command passed in -e

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

[digikam] [Bug 374450] DATA LOSS: Saving a file can overwrite other file

2017-02-10 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #11 from Maik Qualmann  ---
Git commit adef76d645d9ec1bac093fe4cf46e151eeff8572 by Maik Qualmann.
Committed on 10/02/2017 at 22:26.
Pushed by mqualmann into branch 'master'.

this must fix the possible wrong save url
FIXED-IN: 5.5.0

M  +2-1NEWS
M  +4-7showfoto/main/showfoto.cpp

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

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

[ktorrent] [Bug 361931] KTorrent immediately segfaults when starting download from .torrent file

2017-02-10 Thread Daimonion

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

Daimonion  changed:

   What|Removed |Added

 CC||de...@krutt.org

--- Comment #1 from Daimonion  ---
I can confirm this.

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

[kdevelop] [Bug 354444] Let user set the C++ standard version globally

2017-02-10 Thread Sven Brauch

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #3 from Sven Brauch  ---
Shouldn't this be set automatically by the project manager? e.g. cmake knows
about the C++ standard required by the project via CMAKE_CXX_STANDARD.

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

[plasmashell] [Bug 376321] Action overlays are unintuitive

2017-02-10 Thread Andres Betts

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

Andres Betts  changed:

   What|Removed |Added

 CC||anditosan1...@gmail.com

--- Comment #1 from Andres Betts  ---
Kai, do you have some images to show this behavior?

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

[plasmashell] [Bug 376321] Action overlays are unintuitive

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||kain...@gmail.com

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

[plasmashell] [Bug 376321] New: Action overlays are unintuitive

2017-02-10 Thread Kai Uwe Broulik

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

Bug ID: 376321
   Summary: Action overlays are unintuitive
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Theme - Breeze
  Assignee: visual-des...@kde.org
  Reporter: k...@privat.broulik.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

The overlays in FolderView (select, deselect, "open cascading folder popup")
are just circles and not easily recognized as such (user testing showed).

They are also inconsistent with Dolphin which uses plus/minus icons for that.
This icons in action-overlays.svgz in "widgets" of Plasma's Breeze theme should
be changed to more recognizable ones.

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

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

2017-02-10 Thread Cade Robinson

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

--- Comment #20 from Cade Robinson  ---
to clarify comment 16 when I say "running uname" and running echo I mean as the
-e param

konsole --hold --new-tab -e uname
and
konsole --hold --new-tab -e 'echo $0'

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

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

2017-02-10 Thread Cade Robinson

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

--- Comment #19 from Cade Robinson  ---
With the option "Run all Konsole windows in a single process" running these
exact commands:
konsole --hold --new-tab -e ssh cadetest
and
konsole --hold --new-tab -e ssh root@cadetest

Will open a new tab BUT:
both give the error in the new tab:
ssh: Could not resolve hostname konsole: Name or service not known

Also the tab name is "() konsole"

The server cadetest exists and I can ssh to it normally.

If I disable "Run all Konsole windows in a single process" and run:
konsole --hold --new-tab -e ssh cadetest

It will open a new window and ssh to cadetest server normally BUT not be a new
tab.

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

[kdevplatform] [Bug 374458] Crash when dragging launches in Launch Configuration

2017-02-10 Thread Aetf

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

--- Comment #9 from Aetf <7437...@gmail.com> ---
Francis could you try https://phabricator.kde.org/D4555 and see if it works for
you?

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

[plasmashell] [Bug 376320] New: Task switcher themes not working under wayland

2017-02-10 Thread Michael D

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

Bug ID: 376320
   Summary: Task switcher themes not working under wayland
   Product: plasmashell
   Version: 5.9.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: nortex...@gmail.com
  Target Milestone: 1.0

Cover/Flip switch and Breeze work, but most others don't. They sometimes
activate properly, but most times nothing shows and the apps are simply
switched by alt-tabbing.

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

[rekonq] [Bug 320386] Rekonq crashes everytime while browsing specific pages, one tab open

2017-02-10 Thread Christoph Feck

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

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

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

[rekonq] [Bug 376271] Crash on excite

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[rekonq] [Bug 368690] konqueror crashed accessing excite search page

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[rekonq] [Bug 320386] Rekonq crashes everytime while browsing specific pages, one tab open

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||azhc...@gmx.us

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

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

[rekonq] [Bug 320386] Rekonq crashes everytime while browsing specific pages, one tab open

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mar...@gmx.de

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

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

[rekonq] [Bug 365858] Rekonq crashes when opening a site

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[Breeze] [Bug 376263] Color leak in title bar

2017-02-10 Thread Hugo Pereira Da Costa

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #3 from Hugo Pereira Da Costa  ---
(In reply to Christoph Feck from comment #2)
> The problem described in comment #0 is with the active System Settings
> window. Between the blue title bar and the gray window surface an orange
> line is visible which should not be there.

If this is the issue, then this is not a bug, it is a feature.
With all colour schemes, we use the "selection color" (here orange) as a
separator line between the active window title bar, and the window content. 
With the default breeze color scheme, this is the "blue" line you see between
the dark title bar and the grey content.

...
But i too though this was more about the chrome window (which i then believe is
more of a compositing bug/display driver, than window decoration bug), but then
let us wait for the reporter to clarify what really is the bug.

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

[kde] [Bug 376310] KDE crash when computer was awaking from sleep mode

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[plasmashell] [Bug 360506] Crash in XIQueryDevice

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||frtorr...@gmail.com

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

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

[Breeze] [Bug 376263] Color leak in title bar

2017-02-10 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #2 from Christoph Feck  ---
The problem described in comment #0 is with the active System Settings window.
Between the blue title bar and the gray window surface an orange line is
visible which should not be there.

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

[kdeplasma-addons] [Bug 376315] applets opened in windows don't have a reasonable minimum size

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 376316] New: Regression: manual sorting seems to be ignored?

2017-02-10 Thread Fuchs

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

Bug ID: 376316
   Summary: Regression: manual sorting seems to be ignored?
   Product: plasmashell
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org
  Target Milestone: 1.0

(Could also be a 5.9 regression, didn't test it back then): 

When adding a new (existing ones work) pinned task and then manually sort it
(drag it to a different place), it returns to the end of the list after a new
window has been opened  (or that application closed and re-opened) 

To reproduce: 

create a new pinned application (e.g. open system settings and pin it, I pinned
it for "all activities"), then move it to a different place  (e.g. to the
left). Close and re-open the application, and it will move back to the end of
the list (right, by default in a bottom panel)

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

[plasmashell] [Bug 376317] New: Active screen corners/edges don't work on wayland

2017-02-10 Thread Michael D

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

Bug ID: 376317
   Summary: Active screen corners/edges don't work on wayland
   Product: plasmashell
   Version: 5.9.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: nortex...@gmail.com
  Target Milestone: 1.0

I have my left-most top and bottom corners set to active present windows
(current desktop) and desktop grid, both of which work in an x11 session, but
not in a wayland one.

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

[kdevelop] [Bug 376319] New: Projects base directory not saved

2017-02-10 Thread Wouter Haffmans

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

Bug ID: 376319
   Summary: Projects base directory not saved
   Product: kdevelop
   Version: 5.0.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: wou...@simply-life.net
  Target Milestone: ---

The "Projects base directory" setting is not saved correctly. Every time
KDevelop is restarted, it resets to $HOME/projects instead of whatever I picked
before.

To reproduce:
- Go to Settings->Configure KDevelop->Projects
- Change the "Projects base directory" setting
- Quit and restart KDevelop

Expected:
Setting is remembered and used when creating a new/opening an existing project

Actual:
Setting is reset after restart.

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

[kate] [Bug 330843] Support .editorconfig config files

2017-02-10 Thread Simon Andric

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[ksshaskpass] [Bug 376318] New: Regression: passwords no longer remembered, asks every time I open a shell

2017-02-10 Thread Fuchs

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

Bug ID: 376318
   Summary: Regression: passwords no longer remembered, asks every
time I open a shell
   Product: ksshaskpass
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jpwhit...@kde.org
  Reporter: deve...@fuchsnet.ch
  Target Milestone: ---

Since upgrading to ksshaskpass 5.9.1 I get a password prompt every single time
I open a new instance of my shell. 

Downgrading to 5.9.0 works, the passwords are read out of kwallet again. 

Let me know what kind of debug information I can provide.

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

[plasmashell] [Bug 376315] Plasma windowed doesn't enforce a reasonable minimum size

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

Summary|applets opened in windows   |Plasma windowed doesn't
   |don't have a reasonable |enforce a reasonable
   |minimum size|minimum size

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

[plasmashell] [Bug 376315] applets opened in windows don't have a reasonable minimum size

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org
   Target Milestone|--- |1.0
Product|kdeplasma-addons|plasmashell
  Component|General |general

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

[kdeplasma-addons] [Bug 376315] New: applets opened in windows don't have a reasonable minimum size

2017-02-10 Thread Lukas

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

Bug ID: 376315
   Summary: applets opened in windows don't have a reasonable
minimum size
   Product: kdeplasma-addons
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: k...@web.de
  Target Milestone: ---

Open an applet in krunner such that it shows in its own window.
Shrink the window by resizing until it is <10 pixels wide. Now not even the
close, minimize, etc. buttons are visible anymore, let alone the window
contents.
This shouldn't be possible, there should be a reasonable minimum size set for
the window.

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

[kdevplatform] [Bug 374458] Crash when dragging launches in Launch Configuration

2017-02-10 Thread Aetf

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

--- Comment #8 from Aetf <7437...@gmail.com> ---
Oh I see. Didn't know much about git describe before. ;P

Now I can finally reproduce the crash. Launcher items are in fact not
draggable. But the crash happens when you click & hold the cursor, then move
from a top-level item to its child item, e.g. Debug mode. And it only happens
under the following condition:

1. The top-level item must have a child. (Compiled binary, Plasmoid launcher)
2. The child item must be a debug configuration with GDB selected. LLDB won't
trigger the crash

The crash happens because the code tries to set 'gdb' as launch configuration
type on the wrong item. However this is before
`LaunchConfiguration::launcherForMode` got called.

I don't know how the 'gdb' type string was generated yet. I'm still tracing
down the logic when changing pages in the dialog.

Will report back with more info later.

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

[kdeplasma-addons] [Bug 376314] New: timer, no notification shown when timer finishes if started in window

2017-02-10 Thread Lukas

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

Bug ID: 376314
   Summary: timer, no notification shown when timer finishes if
started in window
   Product: kdeplasma-addons
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: timer
  Assignee: plasma-b...@kde.org
  Reporter: k...@web.de
  Target Milestone: ---

Start the timer applet from krunner such that it opens in its own window.
When the timer finishes, no notification is shown.
The notification is shown if the applet was placed on the desktop, but not
shown if it was opened in a window.

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

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

2017-02-10 Thread Wolfgang Bauer

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #18 from Wolfgang Bauer  ---
(In reply to Cade Robinson from comment #16)
> Using --hold I get errors like this:
> running a ssh root@server:
> ssh: Could not resolve hostname konsole: Name or service not known

And what command exactly did you run?
Just to be clear, that is what I meant:
konsole --hold --new-tab -e ssh HOST

(In reply to Cade Robinson from comment #17)
> Still happening in konsole 16.12.2

Both fixes (for the --new-tab and the -e option) are not in 16.12.2.

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

[plasmashell] [Bug 376313] New: Add edge resistance to show hidden panels

2017-02-10 Thread Bjarne Wichmann Bagge Petersen

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

Bug ID: 376313
   Summary: Add edge resistance to show hidden panels
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: nospam.nos...@mekanix.dk
  Target Milestone: 1.0

When using Chrome with no title and global menus with auto hiding I find myself
doing the same pointer movement over and over again when I want to switch tab:

 ->  ->  -> 
->  -> 

A little resistance to the screen edges to not accidentally show hidden panels
would be wonderful. 

Some related issues. Appears this feature have been present in KDE4.
https://bugs.kde.org/show_bug.cgi?id=188272
https://bugs.kde.org/show_bug.cgi?id=367763

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

[Breeze] [Bug 376312] New: Confusing Akregator and Wifi icons in systray

2017-02-10 Thread Tore Havn

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

Bug ID: 376312
   Summary: Confusing Akregator and Wifi icons in systray
   Product: Breeze
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: v...@veqz.net
CC: kain...@gmail.com
  Target Milestone: ---

This isn't a big thing, but I've noticed that I constantly click on the
Akregator icon when I intend to click on the Wifi icon in the systray.

Perhaps one of them should be modified a bit so they are less interchangable?

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

[krita] [Bug 376311] New: Krita crashes when trying to open the settings

2017-02-10 Thread Heiko Becker

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

Bug ID: 376311
   Summary: Krita crashes when trying to open the settings
   Product: krita
   Version: 3.1.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: heire...@exherbo.org
  Target Milestone: ---

Application: krita (3.1.2)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.9 x86_64
Distribution (Platform): Exherbo Packages

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

Just clicking on Settings | Configure Krita...

Krita 3.1.2, Qt 5.8.0 and KF 5.31.0.

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library
"/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7278abb800 (LWP 25390))]

Thread 10 (Thread 0x7f722fc6a700 (LWP 25413)):
#0  0x7f726ff1802f in pthread_cond_wait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f72761bce7b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x7e45fd0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x7e45c10,
mutex=mutex@entry=0x7e45c08, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f72772496c1 in QFileInfoGatherer::run (this=0x7e45bf8) at
dialogs/qfileinfogatherer.cpp:217
#4  0x7f72761bc0d9 in QThreadPrivate::start (arg=0x7e45bf8) at
thread/qthread_unix.cpp:368
#5  0x7f726ff123d4 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#6  0x7f7275ad3e5f in clone () from
/usr/x86_64-pc-linux-gnu/lib64/libc.so.6

Thread 9 (Thread 0x7f723046b700 (LWP 25403)):
#0  0x7f726ff1802f in pthread_cond_wait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f72761bce7b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x6fdd3c0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=mutex@entry=0x6fd6b00,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f72761b65e6 in QSemaphore::tryAcquire (this=0x6fdd1a0, n=n@entry=1,
timeout=timeout@entry=-1) at thread/qsemaphore.cpp:220
#4  0x7f7273f3fe63 in KisTileDataSwapper::waitForWork
(this=this@entry=0x7f72743ff8e0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
/var/tmp/paludis/build/media-gfx-krita-3.1.2.1/work/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#5  0x7f7273f4006a in KisTileDataSwapper::run (this=0x7f72743ff8e0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
/var/tmp/paludis/build/media-gfx-krita-3.1.2.1/work/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#6  0x7f72761bc0d9 in QThreadPrivate::start (arg=0x7f72743ff8e0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
thread/qthread_unix.cpp:368
#7  0x7f726ff123d4 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#8  0x7f7275ad3e5f in clone () from
/usr/x86_64-pc-linux-gnu/lib64/libc.so.6

Thread 8 (Thread 0x7f7230c6c700 (LWP 25402)):
#0  0x7f726ff1802f in pthread_cond_wait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f72761bce7b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x6fdd100) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x6fd6ae8,
mutex=mutex@entry=0x6fd6ae0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f72761b6313 in QSemaphore::acquire (this=this@entry=0x7f72743ff8b0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+16>,
n=n@entry=1) at thread/qsemaphore.cpp:143
#4  0x7f7273f2645e in KisTileDataPooler::waitForWork (this=0x7f72743ff8a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/var/tmp/paludis/build/media-gfx-krita-3.1.2.1/work/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:165
#5  0x7f7273f26baa in KisTileDataPooler::run (this=0x7f72743ff8a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
/var/tmp/paludis/build/media-gfx-krita-3.1.2.1/work/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:187
#6  0x7f72761bc0d9 in QThreadPrivate::start (arg=0x7f72743ff8a0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at
thread/qthread_unix.cpp:368
#7  0x7f726ff123d4 in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#8  0x7f7275ad3e5f in clone () from
/usr/x86_64-pc-linux-gnu/lib64/libc.so.6

Thread 7 (Thread 0x7f7243fff700 (LWP 25401)):
#0  0x7f726ff183d8 in pthread_cond_timedwait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f72761bcdc6 in

[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts

2017-02-10 Thread Igor Poboiko

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

Igor Poboiko  changed:

   What|Removed |Added

 CC||igor.pobo...@gmail.com

--- Comment #2 from Igor Poboiko  ---
Same here with russian layout (which is obviously completely different from
english).

(In reply to Martin Gräßlin from comment #1)
> Now the problem is tricky. Do you know whether there is a key in the layout
> which renders a "k"? Or whether the k key actually generates multiple
> keysyms? If it generated kappa and k, we could change the code to support
> all syms.

I suppose Greek layout just doesn't have a "k" symbol at all. Does such layouts
even exist (where the same symbol is placed on the some place in one layout and
on another place on second layout)? 

Can we just bind it not to the symbol but to key ("scan code") instead?
(however, it might break if user attaches another keyboard...)
Or just map everything to English layout? (it might be weird if user isn't
familiar with latin alphabet)
Or maybe iterate over all configured layouts and check if pressed key code
corresponds to a shortcut on any of it?

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

[krita] [Bug 376147] Krita 3.1.2 Print Botton and Print option is missing

2017-02-10 Thread Patrick Dreier

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

Patrick Dreier  changed:

   What|Removed |Added

 Resolution|LATER   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #7 from Patrick Dreier  ---
Hello!

I dos'nt nessary install Scribus. Scribus is an other category of Programs.

With king regards!

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

[krusader] [Bug 372966] Some icons are not seen using a plain Ubuntu (not Kubuntu) 16.04

2017-02-10 Thread Wladimir Palant

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

--- Comment #19 from Wladimir Palant  ---
(In reply to Wladimir Palant from comment #14)
> I have to revise the previous comment. After installing Ubuntu 16.10 from
> scratch changing the global icon theme no longer helps, Krusader stays stuck
> without icons - no idea what changed.

Got it: I forgot installing qt5-appmenu. So the instructions for getting icons
on Ubuntu seem to be: install breeze-icon-theme, qt5-appmenu, unity-tweak-tool.
Log out and log in again (qt5-appmenu environment variable won't be set
otherwise). Run unity-tweak-tool to change the global icon theme to Breeze.

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

[dolphin] [Bug 372003] WM_CLASS issue in dolphin 15

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||k...@privat.broulik.de

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

[kde] [Bug 376310] New: KDE crash when computer was awaking from sleep mode

2017-02-10 Thread raul

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

Bug ID: 376310
   Summary: KDE crash when computer was awaking from sleep mode
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: frtorr...@gmail.com
  Target Milestone: ---

Application: kdeinit5 ()
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
KDE crashed when the compunter was awoken from sleep mode.
This does happen some times

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

Thread 6 (Thread 0x7f657176e700 (LWP 1349)):
#0  0x7f65970b8506 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f65970b8d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f65970b8f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f659a904d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f659a8abd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f659a36402d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f6573fff700 (LWP 1264)):
#0  0x7f659a357ccd in read () from /lib64/libc.so.6
#1  0x7f65970f9b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f65970b8999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f65970b8df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f65970b8f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f659a904d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f659a8abd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f659a36402d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f6578e29700 (LWP 1263)):
#0  0x7f659a35bbfd in poll () from /lib64/libc.so.6
#1  0x7f65970b8e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f65970b8f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f659a904d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f659a8abd53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f657b4aecf7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f659a36402d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f657c0f5700 (LWP 1250)):
#0  0x7f65970facf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f65970b8d55 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f65970b919a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7f657cc30426 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x7f65970ddf65 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f659a36402d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f6586d2a700 (LWP 1240)):
#0  0x7f659a35bbfd in poll () from /lib64/libc.so.6
#1  0x7f659b680422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f659b68200f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f658907f3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f659a36402d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f659c20a780 (LWP 1238)):
[KCrash Handler]
#6  0x7f659a2faf54 in free () from /lib64/libc.so.6
#7  0x7f6588e393f1 in XIQueryDevice () from /usr/lib64/libXi.so.6
#8  0x7f65890a00bf in
QXcbConnection::handleEnterEvent(xcb_enter_notify_event_t const*) () from
/usr/lib64/libQt5XcbQpa.so.5
#9  0x7f65890917df in
QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () from
/usr/lib64/libQt5XcbQpa.so.5
#10 0x7f658907d515 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib64/libQt5XcbQpa.so.5
#11 0x7f658907f01b in

[kmail2] [Bug 376309] New: kmail2 locked on imap mails migration (5.4.2)

2017-02-10 Thread Fabio Coatti

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

Bug ID: 376309
   Summary: kmail2 locked on imap mails migration (5.4.2)
   Product: kmail2
   Version: 5.4.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: fabio.coa...@gmail.com
  Target Milestone: ---

Kmail locks when moving several emails from local folder to remote IMAP server

Scenario:
I have several local folders that I want to move to remote imap folders.
If I move only some messages (say, < 10-20), the operation is completed. Moving
more messages (no exact number though) the process seems to get stuck forever.
The progress bar on sx bottom remains open and nothing happens; even waiting
for hours does not allow the operation to complete. Please note that looking at
the size of messages moved, it would take only some minutes to move them, not
hours. One suspect is that at somepoint the network gets slow (I'm trying in
some location with poor connectivity), the upload gets hogged and kmail is not
able to recover.

I'd rather prefer kmail to throw an error, if really is not able to complete
the operation, that should be the ideal situation :).
In the same network, other mail clients are able to complete a similar
operation. (tested thunderbird/mac, outlook/mac-win)

Distro: gentoo
Kmail: 5.4.2
akonadi 16.12.2
Plasma 5.9.1

Gcc 5.4.0

I can perform tests and give more info, just let me know

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

[dolphin] [Bug 368951] custom SVG icons not working for folders

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 376307] Font size of a date in the Digital Clock applet is too big

2017-02-10 Thread Pauline Emily

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

--- Comment #2 from Pauline Emily  ---
(In reply to Kai Uwe Broulik from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 375966 ***
Don’t think it is really a duplicate – #375966 is about font size of displayed
time with display of the date turned off. Mine is about font size of displayed
date with display of the date (obviously) turned on.

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

[dolphin] [Bug 368951] custom SVG icons not working for folders

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||tesfab...@gmail.com

--- Comment #3 from Kai Uwe Broulik  ---
*** Bug 371835 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 371835] Folder icon not working with local svg files

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---


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

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

[krusader] [Bug 372966] Some icons are not seen using a plain Ubuntu (not Kubuntu) 16.04

2017-02-10 Thread Wladimir Palant

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

--- Comment #18 from Wladimir Palant  ---
For me as an end user the problem is really that Krusader looks broken on
Ubuntu out of the box and there is no obvious way to fix that. Your question is
actually about the desired solution:

(1) Krusader only works properly with the Breeze theme so it should just force
that theme to be enabled for itself (what I've done in my local build right
now).
(2) KDE apps missing icons on Ubuntu is just the way it is, so nothing needs to
be done about that.
(3) Expecting icons that the theme might no have is wrong, so Krusader should
have fallbacks for the non-standard icons (in my understanding, Krusader 2.4.0
was doing just that but you don't consider that a good solution).

There are also some variants of the above solutions that I can think of:

(1a) Krusader should only force Breeze theme if it somehow detects that the
globally selected theme is incomplete. This can be as trivial as blacklisting
ubuntu-mono-* and Adwaita, with the assumption that people who changed the
default icon theme know what they are doing.
(1b) Krusader could fall back to Breeze for missing icons only (not sure
whether this can be done).
(2a) Krusader could warn on missing icons with instructions on how to switch to
Breeze, similarly to how it suggests installing konsole.

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

[plasmashell] [Bug 375966] Digital Clock font is too large

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||vil...@posteo.net

--- Comment #8 from Kai Uwe Broulik  ---
*** Bug 376307 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 376308] New: KDevelop crashed opening a CMake project

2017-02-10 Thread Nicolas Bigaouette

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

Bug ID: 376308
   Summary: KDevelop crashed opening a CMake project
   Product: kdevelop
   Version: 5.0.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: nbigaoue...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.0.3)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Opened KDevelop, opening a CMake project (CMakeLists.txt). I selected the build
folder where cmake has previously been called. KDevelop then crashed.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f630be6cc80 (LWP 24939))]

Thread 23 (Thread 0x7f629178b700 (LWP 25228)):
#0  0x7f62cf3f22d4 in  () at /usr/lib/libclang.so.3.9
#1  0x7f62cf3f8b7a in  () at /usr/lib/libclang.so.3.9
#2  0x7f62cf9c5aa8 in  () at /usr/lib/libclang.so.3.9
#3  0x7f62cf9c6395 in  () at /usr/lib/libclang.so.3.9
#4  0x7f62cf792130 in  () at /usr/lib/libclang.so.3.9
#5  0x7f62cf79de8d in  () at /usr/lib/libclang.so.3.9
#6  0x7f62cf9825a3 in  () at /usr/lib/libclang.so.3.9
#7  0x7f62cf9756f5 in  () at /usr/lib/libclang.so.3.9
#8  0x7f62cf9921dd in  () at /usr/lib/libclang.so.3.9
#9  0x7f62cf99452c in  () at /usr/lib/libclang.so.3.9
#10 0x7f62cf992575 in  () at /usr/lib/libclang.so.3.9
#11 0x7f62cf994544 in  () at /usr/lib/libclang.so.3.9
#12 0x7f62cf992575 in  () at /usr/lib/libclang.so.3.9
#13 0x7f62cf9939fb in  () at /usr/lib/libclang.so.3.9
#14 0x7f62cf993b2b in  () at /usr/lib/libclang.so.3.9
#15 0x7f62cf9925f5 in  () at /usr/lib/libclang.so.3.9
#16 0x7f62cf996d3f in  () at /usr/lib/libclang.so.3.9
#17 0x7f62cf9aa843 in  () at /usr/lib/libclang.so.3.9
#18 0x7f62cf9a8c83 in  () at /usr/lib/libclang.so.3.9
#19 0x7f62cf9aa4cd in  () at /usr/lib/libclang.so.3.9
#20 0x7f62cf9a8c83 in  () at /usr/lib/libclang.so.3.9
#21 0x7f62cf9aa4cd in  () at /usr/lib/libclang.so.3.9
#22 0x7f62cf9a8c83 in  () at /usr/lib/libclang.so.3.9
#23 0x7f62cf60c5fa in  () at /usr/lib/libclang.so.3.9
#24 0x7f62cfd70da1 in  () at /usr/lib/libclang.so.3.9
#25 0x7f62cfd641b3 in  () at /usr/lib/libclang.so.3.9
#26 0x7f62cf4fface in  () at /usr/lib/libclang.so.3.9
#27 0x7f62cf4bb497 in  () at /usr/lib/libclang.so.3.9
#28 0x7f62cf4be89b in  () at /usr/lib/libclang.so.3.9
#29 0x7f62cf4c2497 in  () at /usr/lib/libclang.so.3.9
#30 0x7f62cf29c0f0 in  () at /usr/lib/libclang.so.3.9
#31 0x7f62cc76e539 in
llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) () at
/usr/lib/../lib/libLLVM-3.9.so
#32 0x7f62cc76e5a4 in  () at /usr/lib/../lib/libLLVM-3.9.so
#33 0x7f62cc7e8bdd in  () at /usr/lib/../lib/libLLVM-3.9.so
#34 0x7f630184b454 in start_thread () at /usr/lib/libpthread.so.0
#35 0x7f6308c817df in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f6291fed700 (LWP 25227)):
#0  0x7f6308c7848d in poll () at /usr/lib/libc.so.6
#1  0x7f62ff626786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f62ff62689c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f630959c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f630954589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f6309367a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f6306e9bb4f in  () at /usr/lib/libKDevPlatformLanguage.so.10
#7  0x7f630936c6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f630184b454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f6308c817df in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f6292b96700 (LWP 25226)):
#0  0x7f63018514b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f630936d4c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f6309368bc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f630936c6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f630184b454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f6308c817df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f6293397700 (LWP 25216)):
#0  0x7f630185110f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f630936d58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f62fda8d1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f62fda91988 in  ()

[plasmashell] [Bug 376307] Font size of a date in the Digital Clock applet is too big

2017-02-10 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---


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

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

[kaffeine] [Bug 376206] Kaffeine partly not translated

2017-02-10 Thread bugzilla_noreply

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

--- Comment #5 from yuli...@mailbox.org ---
(In reply to Burkhard Lueck from comment #4)
> Installing translations for an application using Qt like kaffeine, but not
> installing the Qt translations is obviously a packaging bug.
I reported the bug in the RPMFusion bugtracker.


> I have no clue about your translation issue with the "Open File" dialog, as
> stated in comment #1 the dialog is fully translated here.
I have also no idea.

> I cannot check if "enabled/disabled" is translated in the "Recording
> Schedule" window due to missing hardware, but dvbrecordingdialog.cpp has
> return QString("Enabled"); and return QString("Disabled"); and this probably
> needs i18n() calls?
Probably. But as this parameter cannot be changed by hand anyway and the
meaning is not really explained, this is not that important. Would be nice
nonetheless.

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

[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back

2017-02-10 Thread Jaak Ristioja

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

Jaak Ristioja  changed:

   What|Removed |Added

 CC|j...@ristioja.ee|

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

[kwin] [Bug 374867] Impossible to reach screen edge if mouse cursor is moving fast

2017-02-10 Thread Igor Poboiko

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

--- Comment #3 from Igor Poboiko  ---
Still an issue in Plasma 5.9.1. It makes "Active Screen Edge Actions" feature
(almost) useless in Wayland :(

It behaves in a following manner: when I'm moving cursor, each time it jumps by
some vector (dx, dy), which depends on the speed of cursor movement. It seems
like there is a following check: if (x+dx, y+dy) is outside the visible area,
just ignore that move, and thus make the cursor stuck at some position away
from the border.
If I move slowly, then (dx, dy) is small, which allows me to come closer to the
border and eventually touch it (thus triggering the edge action). But if I keep
moving fast, the cursor is stuck. 
The proper behavior would be to move cursor exactly at the border instead.

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

1 2 3 >

1 - 100 of 262 matches

Mail list logo