[krita] [Bug 356350] 2.9.9 Animation Beta - Duplicating animated layers only creates new static layer

2015-12-13 Thread wolthera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356350

wolthera  changed:

   What|Removed |Added

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

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


[krita] [Bug 356256] [Krita animation beta] Copying frame offsets the image to original position

2015-12-13 Thread wolthera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356256

wolthera  changed:

   What|Removed |Added

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

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


[krita] [Bug 356056] Krita Animation Beta - Ctrl+drag to Copy Single Animation Frame Not Working

2015-12-13 Thread wolthera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356056

wolthera  changed:

   What|Removed |Added

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

--- Comment #3 from wolthera  ---
It does work here, but it is indeed far more fiddly than you would like.

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


[plasmashell] [Bug 354950] Plasma crash on first start after upgrade from OpenSuSE 13.2

2015-12-13 Thread wow_joyce via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354950

--- Comment #2 from wow_joyce  ---
Created attachment 96041
  --> https://bugs.kde.org/attachment.cgi?id=96041=edit
Plasmashell crash log after failed openSUSE Tumbleweed install...

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


[plasma-pa] [Bug 356605] Audio applet not visible, only empty space with no reaction to mouse

2015-12-13 Thread Neros via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356605

Neros  changed:

   What|Removed |Added

 CC||cont...@neros.fr

--- Comment #2 from Neros  ---
I have the exact same bug.

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


[plasmashell] [Bug 354950] Plasma crash on first start after upgrade from OpenSuSE 13.2

2015-12-13 Thread wow_joyce via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354950

--- Comment #5 from wow_joyce  ---
Platform particulars:
NVIDIA GeForce 9800M GS [Display adapter]
Generic PnP Monitor (15.7"vis, October 2007)
Board: ASUSTeK Computer Inc. G50VT 1.0
Bus Clock: 267 megahertz
BIOS: American Megatrends Inc. 207 09/02/2008
4-Gigs of Memory...

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


[plasmashell] [Bug 356582] Moving icon from FolderView widget: all widget move with mouse

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356582

--- Comment #5 from opensuse.lietuviu.ka...@gmail.com ---
a) YES – Press and hold is enabled
b) NO

I can reproduce it always.

Actually, running system is openSUSE based appliance, made in SUSE Studio.
You can download it for testing youself
https://susestudio.com/a/CttYWz/lietukas-42-1-64-bit-english?version=42.1.12#appliance-downloads
or just run online
https://susestudio.com/a/CttYWz/lietukas-42-1-64-bit-english/start_testdrive?version=42.1.12

I run LiveCD ISO in VirtualBox. Make sure to change Screen resolution to higher
(otherwise folder is so big, that don't move)

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

[Baloo] [Bug 356602] Baloo has a confused configuration

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356602

--- Comment #1 from hotmusic...@mail.bg ---
Created attachment 96033
  --> https://bugs.kde.org/attachment.cgi?id=96033=edit
Baloo KCM configuration

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


[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=329697

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

   What|Removed |Added

 CC||meckis...@web.de

--- Comment #150 from caulier.gil...@gmail.com ---
*** Bug 356598 has been marked as a duplicate of this bug. ***

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


[digikam] [Bug 356598] change folder view

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356598

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

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---


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

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


[valgrind] [Bug 356611] New: vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC9 0x3 0x1D 0x0

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356611

Bug ID: 356611
   Summary: vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA
0xF8 0x10 0xC9 0x3 0x1D 0x0
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: muell...@gmx.net

This happens whenever libld is used to load a dynamically linked library.

Full output:

==10913== Memcheck, a memory error detector
==10913== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10913== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10913== Command: gdb
==10913== 
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC9 0x3 0x1D
0x0
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==10913== valgrind: Unrecognised instruction at address 0x4011d04.
==10913==at 0x4011D04: _dl_allocate_tls_storage (in /lib64/ld-2.22.so)
==10913==by 0x4000B9A: init_tls (in /lib64/ld-2.22.so)
==10913==by 0x40034AF: dl_main (in /lib64/ld-2.22.so)
==10913==by 0x4016978: _dl_sysdep_start (in /lib64/ld-2.22.so)
==10913==by 0x4004C28: _dl_start (in /lib64/ld-2.22.so)
==10913==by 0x4000C47: ??? (in /lib64/ld-2.22.so)
==10913== Your program just tried to execute an instruction that Valgrind
==10913== did not recognise.  There are two possible reasons for this.
==10913== 1. Your program has a bug and erroneously jumped to a non-code
==10913==location.  If you are running Memcheck and you just saw a
==10913==warning about a bad jump, it's probably your program's fault.
==10913== 2. The instruction is legitimate but Valgrind doesn't handle it,
==10913==i.e. it's Valgrind's fault.  If you think this is the case or
==10913==you are not sure, please let us know and we'll try to fix it.
==10913== Either way, Valgrind will now raise a SIGILL signal which will
==10913== probably kill your program.
==10913== 
==10913== Process terminating with default action of signal 4 (SIGILL)
==10913==  Illegal opcode at address 0x4011D04
==10913==at 0x4011D04: _dl_allocate_tls_storage (in /lib64/ld-2.22.so)
==10913==by 0x4000B9A: init_tls (in /lib64/ld-2.22.so)
==10913==by 0x40034AF: dl_main (in /lib64/ld-2.22.so)
==10913==by 0x4016978: _dl_sysdep_start (in /lib64/ld-2.22.so)
==10913==by 0x4004C28: _dl_start (in /lib64/ld-2.22.so)
==10913==by 0x4000C47: ??? (in /lib64/ld-2.22.so)
==10913== Jump to the invalid address stated on the next line
==10913==at 0x596: ???
==10913==  Address 0x596 is not stack'd, malloc'd or (recently) free'd
==10913== 
==10913== 
==10913== Process terminating with default action of signal 11 (SIGSEGV)
==10913==  Bad permissions for mapped region at address 0x596
==10913==at 0x596: ???
==10913== 
==10913== HEAP SUMMARY:
==10913== in use at exit: 0 bytes in 0 blocks
==10913==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==10913== 
==10913== All heap blocks were freed -- no leaks are possible
==10913== 
==10913== For counts of detected and suppressed errors, rerun with: -v
==10913== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault


Reproducible: Always

Steps to Reproduce:
1. valgrind gdb
2. crash



I am using Valgrind 3.11.0 and glibc-2.22 (compiled with -arch=native and -O2)

uname -a:
Linux localhost 4.3.0-gentoo #1 SMP Sat Dec 5 16:08:19 2015 x86_64 AMD A8-4500M
APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux

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


[kmail2] [Bug 355093] Crash if I click on new mail

2015-12-13 Thread Fabian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355093

Fabian  changed:

   What|Removed |Added

 CC||tonym...@gmail.com

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


[krita] [Bug 355933] Krita animation beta - crop tool moves drawings around on multiple frames

2015-12-13 Thread wolthera via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355933

wolthera  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from wolthera  ---
resolved in beta 2

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


[plasmashell] [Bug 356582] Moving icon from FolderView widget: all widget move with mouse

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356582

--- Comment #6 from opensuse.lietuviu.ka...@gmail.com ---
To be more presize: start to drag icon, but release it in same FolderView
widget. Then folder moves with mouse. It stops moving, if you click again.

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


[kwin] [Bug 356600] New: OSD desktop switch animation text could be bigger (and configurable)

2015-12-13 Thread Janet via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356600

Bug ID: 356600
   Summary: OSD desktop switch animation text could be bigger (and
configurable)
   Product: kwin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugzi...@kerridis.de

The font size used in the OSD desktop switch notification/animation has a fixed
and relatively small size compared to that it should be recognized in a very
short timeframe, especially on bigger displays (and very especially for people
with not so good eyes). Therefore it would be helpful if the font size would
make the notification a little more terse i.e. it could be bigger by default.
For example I feel comforable with a font size of 32.  But as there are people
with smaller displays it would be great it the font size would be configurable.

In Bug 316372 Comment 36 is mentioned a solution, a patched osd.qml file. Maybe
this could get the default one? 

It would be more convenient/obvious to alter the font size via GUI (where you
can choose to use the OSD and decide to use graphical or text only
notification) because only if a GUI element exists most of the users probably
will know that the option exists and will (dare to) use it I guess - but at
least officially *having* the option would be fine.

Reproducible: Always

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


[plasmashell] [Bug 354950] Plasma crash on first start after upgrade from OpenSuSE 13.2

2015-12-13 Thread wow_joyce via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354950

--- Comment #6 from wow_joyce  ---
~/.xsession-errors = 0 bits

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


[plasma-pa] [Bug 356605] Audio applet not visible, only empty space with no reaction to mouse

2015-12-13 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356605

--- Comment #1 from Wiktor  ---
As you can see here
https://www.reddit.com/r/kde/comments/3winhb/plasma_55_issues_broken_widget_frames_sound/cxwh41j
I'm not the only one that encountered this.

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


[plasmashell] [Bug 356582] Moving icon from FolderView widget: all widget move with mouse

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356582

--- Comment #2 from opensuse.lietuviu.ka...@gmail.com ---
Qt 5.5.0 (patched) – default version in latest openSUSE Leap 42.1

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

[plasmashell] [Bug 356582] Moving icon from FolderView widget: all widget move with mouse

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356582

opensuse.lietuviu.ka...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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


[plasmashell] [Bug 354950] Plasma crash on first start after upgrade from OpenSuSE 13.2

2015-12-13 Thread wow_joyce via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354950

wow_joyce  changed:

   What|Removed |Added

 CC||wow_jo...@yahoo.com

--- Comment #1 from wow_joyce  ---
Created attachment 96039
  --> https://bugs.kde.org/attachment.cgi?id=96039=edit
Plasmashell crash log during openSUSE Tumbleweed upgrade process...

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


[plasmashell] [Bug 354651] Perform click action to item cause highlight other

2015-12-13 Thread Anthony via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354651

Anthony  changed:

   What|Removed |Added

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

--- Comment #15 from Anthony  ---
I reopen, cause patch has a regression on Xcb, on Wayland works as expected. I
made new review request https://git.reviewboard.kde.org/r/126331/ it's need
more tests here, we don't want any regression.

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


[gwenview] [Bug 356599] New: 15.08.3 Crash in QGraphicsProxyWidget::focusNextPrevChild

2015-12-13 Thread Michał via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356599

Bug ID: 356599
   Summary: 15.08.3 Crash in
QGraphicsProxyWidget::focusNextPrevChild
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: m...@op.pl
CC: myr...@kde.org

Version is 15.08.3
Image attached (CR2 file)

Gwenview shows red message that it could not read Meta Information (kind of
expected).
What's unexpected is that when trying to navigate to the next image, Gwenview
crashes.

GDBed stack trace:
(gdb) run .
Starting program: /usr/bin/gwenview .
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1049700 (LWP 25188)]
[New Thread 0x7fffd7e6e700 (LWP 25191)]
QImageReader::read() using format hint "cr2" failed: "Unsupported image format"
QImageReader::read() without format hint failed: "Unsupported image format"
[New Thread 0x7fffd766d700 (LWP 25192)]
Could not generate thumbnail for file "file:///home/mcv/+gwenview
crash/IMG_7597.CR2"

Program received signal SIGSEGV, Segmentation fault.
0x748479b0 in ?? () from /usr/lib/libQt5Widgets.so.5
(gdb) whe
#0  0x748479b0 in ?? () from /usr/lib/libQt5Widgets.so.5
#1  0x7484cd8f in QGraphicsProxyWidget::focusNextPrevChild(bool) ()
from /usr/lib/libQt5Widgets.so.5
#2  0x74832c0b in QGraphicsItemPrivate::setVisibleHelper(bool, bool,
bool, bool) () from /usr/lib/libQt5Widgets.so.5
#3  0x7484b542 in QGraphicsProxyWidget::eventFilter(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#4  0x7332e75c in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#5  0x7452fffc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#6  0x745354f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#7  0x7332e96b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7456e0a3 in QWidgetPrivate::hide_helper() () from
/usr/lib/libQt5Widgets.so.5
#9  0x74572870 in QWidget::setVisible(bool) () from
/usr/lib/libQt5Widgets.so.5
#10 0x7456e271 in
QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7456e863 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#12 0x7456e939 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#13 0x7484725a in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from
/usr/lib/libQt5Widgets.so.5
#14 0x74847299 in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from
/usr/lib/libQt5Widgets.so.5
#15 0x74838876 in QGraphicsItem::~QGraphicsItem() () from
/usr/lib/libQt5Widgets.so.5
#16 0x74838b03 in QGraphicsObject::~QGraphicsObject() () from
/usr/lib/libQt5Widgets.so.5
#17 0x74888325 in QGraphicsWidget::~QGraphicsWidget() () from
/usr/lib/libQt5Widgets.so.5
#18 0x7768faf9 in Gwenview::DocumentView::~DocumentView() () from
/usr/lib/libgwenviewlib.so.5
#19 0x7335dfc0 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#20 0x7488980b in QGraphicsWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#21 0x7453001c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#22 0x745354f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#23 0x7332e96b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#24 0x73330d66 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#25 0x73384f03 in ?? () from /usr/lib/libQt5Core.so.5
#26 0x7fffec9d4dc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#27 0x7fffec9d5020 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x7fffec9d50cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#29 0x7338530f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#30 0x7332c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#31 0x733342fc in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#32 0x0043e570 in main ()

Reproducible: Always

Steps to Reproduce:
1. Open attached image
2. Try to navigate to another image in directory (by pressing space or arrows)



Can't attach the image right now, will do it soon (after I get better
connection).

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


[plasmashell] [Bug 354950] Plasma crash on first start after upgrade from OpenSuSE 13.2

2015-12-13 Thread wow_joyce via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354950

--- Comment #3 from wow_joyce  ---
Created attachment 96042
  --> https://bugs.kde.org/attachment.cgi?id=96042=edit
Accompanying KDE Init crash log after reboot...

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


[krita] [Bug 356057] Krita Animation Beta - First Frame Cannot Be Moved or Copied

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356057

--- Comment #3 from sayantan.chaudhuri+...@gmail.com ---
P.S: Bug #356056 [https://bugs.kde.org/show_bug.cgi?id=356056] where single
selected frames cannot be copied with ctrl+drag still remains for the first
frame. For the test that marked this issue as resolved, I selected multiple
frames alongside the first one and than ctrl+dragged to copy them, and this
behaved as expected.

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


[konsole] [Bug 189756] Konsole: High CPU caused by e.g. mplayer or mencoder status updates

2015-12-11 Thread Hello71 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=189756

Hello71  changed:

   What|Removed |Added

 CC||alex_y...@yahoo.ca

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


[kdenlive] [Bug 356536] Copzing Speed effect causes timeline-project inconsistency

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356536

--- Comment #1 from qubo...@gmail.com ---
The second upload was unsuccessful, here is the video that I wanted to link
second:
https://youtu.be/yECM0Sr6uuA

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


[krita] [Bug 356057] Krita Animation Beta - First Frame Cannot Be Moved or Copied

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356057

--- Comment #2 from sayantan.chaudhuri+...@gmail.com ---
As of the animation beta 2.9.10, the first frame can be moved and copied.

But moving the first frame leaves a blank frame on the original position,
instead of an empty frame, unlike every other frame.

I will make a new bug with the changed behavior, and am marking this as
resolved.

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


[krita] [Bug 356056] Krita Animation Beta - Ctrl+drag to Copy Single Animation Frame Not Working

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356056

--- Comment #2 from sayantan.chaudhuri+...@gmail.com ---
The behavior still remains in the animation beta 2.9.10

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


[krita] [Bug 356056] Krita Animation Beta - Ctrl+drag to Copy Single Animation Frame Not Working

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356056

sayantan.chaudhuri+...@gmail.com changed:

   What|Removed |Added

Version|2.9.9   |2.9.10

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


[krita] [Bug 356540] New: Krita Animation Beta - Moving First Frame Leaves Behind Blank Frame Instead of Empty

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356540

Bug ID: 356540
   Summary: Krita Animation Beta - Moving First Frame Leaves
Behind Blank Frame Instead of Empty
   Product: krita
   Version: 2.9.10
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: sayantan.chaudhuri+...@gmail.com

As of the 2.9.10 build of the animation beta, bug #356057
[https://bugs.kde.org/show_bug.cgi?id=356057] is resolved, and the first frame
of the animation can be moved and copied.

But now, moving the first frame leaves behind a blank frame instead of an empty
frame which moving any other frame leaves behind.

Reproducible: Always

Steps to Reproduce:
1. Create some frames
2. Draw something on the first frame.
3. Select and then drag the first frame to any other frame.

Actual Results:  
The destination frame is overwritten with the contents of the first frame. But
in the first frame's position a blank (white) frame is left behind.

Expected Results:  
The destination frame is overwritten with the contents of the first frame. And
in the first frame's position an empty (grey/blue) frame is left behind.

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


[krita] [Bug 356057] Krita Animation Beta - First Frame Cannot Be Moved or Copied

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356057

--- Comment #4 from sayantan.chaudhuri+...@gmail.com ---
Reported remaining behavior as bug #356540
[https://bugs.kde.org/show_bug.cgi?id=356540]

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


[krita] [Bug 356057] Krita Animation Beta - First Frame Cannot Be Moved or Copied

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356057

sayantan.chaudhuri+...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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


[kdenlive] [Bug 356536] New: Copzing Speed effect causes timeline-project inconsistency

2015-12-11 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356536

Bug ID: 356536
   Summary: Copzing Speed effect causes timeline-project
inconsistency
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: qubo...@gmail.com

kdenlive-git v15.11.90-76-gcb3c173 master
catalyst-libgl 15.11-1
ffmpeg 1:2.8.3-1
ffmpeg-compat 1:0.10.16-4
libx264 2:148.20150725-1
mlt-git r4145.v0.9.2.367.g0de91fe-1
mlt-python-bindings 0.9.8-3
movit-git r713.20c2ca7-1
qt5-base 5.5.1-3
x264 2:148.20150725-1
xorg-server 1.16.4-1

Copying the speed effect and then moving another clip seems to damage the
copied-from clip's position in the UI while the project remembers it (if you
save and reload it).

Steps to reproduce:
1. Start Kdenlive
2. Import a video
3. Drag video to timeline
4. Cut the video twice
5. Drag "Speed" effect to first clip, change to 1000%
6. Copy the clip
7. Rightclick->Paste the effect to the second clip
8. Leftclick-Drag the third clip

Expected result:
1. Third clip moves

Actual result:
1. Second and third clip move
2. After moving, the second clip can't be moved
3a. If you use undo quickly, sometimes Kdenlive will crash.
3b. If you save the project, close Kdenlive and re-open it, the second clip
will jump back to its position

Videos:
https://youtu.be/qXUjeJ1pZfw
https://youtu.be/woR-yeBEH0k

This might be related to https://bugs.kde.org/show_bug.cgi?id=355003 and/or
https://bugs.kde.org/show_bug.cgi?id=348148 .

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


[plasmashell] [Bug 356618] New: Taskbar indicator on screen edge also appears if taskbar is visible

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356618

Bug ID: 356618
   Summary: Taskbar indicator on screen edge also appears if
taskbar is visible
   Product: plasmashell
   Version: 5.5.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: slartibar...@gmail.com

If the taskbar is 'auto-hidden' (hamburger-menu >> More Settings >> Auto Hide)
and the mouse cursor reaches the lower screen edge - slowly(!), then a light
blue indicators glows along the lower screen edge. It increases in visibility
(from faint to visible) until the mouse finally reaches the lower screen edge
and then the formerly hidden taskbar pops in.

I'm fine with that (although this option should be switchable)
BUT, if you select the option 'windows can cover' the same glow appears on the
already visible taskbar (which was never hidden) - this is quite disturbing as
there is some 'noise' coming from nowhere without any reason...

Please fix this behaviour to 'glow' only for a hidden taskbar and make this
glow user-definable (on/off)



Reproducible: Always

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


[kaddressbook] [Bug 354594] Looking up an address online fails: Mapquest 'The AppKey submitted with this request is invalid.'

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354594

aux...@gmail.com changed:

   What|Removed |Added

 CC||aux...@gmail.com

--- Comment #7 from aux...@gmail.com ---
Running kaddressbook5-15.08.3 on openSUSE Leap 42.1, I have the same problem
exactly.

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


[kde] [Bug 356619] New: I miss the option that you can change the width of the "blinking cursor"

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356619

Bug ID: 356619
   Summary: I miss the option that you can change the width of the
"blinking cursor"
   Product: kde
   Version: 4.13.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: lisanne-wim...@exitweb.de

I miss the option that you can change the width of the "blinking cursor", so
that also people with eye problems can see the text-input-position for example
in Libre Office or KMail. In my opinion is this very necessary for the
accessibility.  (kde 4 / OpenSuse13.1)

Reproducible: Always

Steps to Reproduce:
1. Click with the mouse in a input field (like this)
2. The blinking cursor is very small and bad visible for people with eye
problems
3.

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


[kdenlive] [Bug 352489] Kdenlive 15.08.0 git20150908.0238 (re)positioning playhead does not work

2015-12-13 Thread Kubuntiac via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352489

--- Comment #9 from Kubuntiac  ---
I'm the reporter of 356185 and the description in this bug, as well as the
workaround (changing MLT threads from 3 to 1) match my experience precisely.

What suggests that they're different issues?

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


[kdenlive] [Bug 354940] Corrupted project after Video Profile change e.g. 1080p50 > 1080p25

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354940

qubo...@gmail.com changed:

   What|Removed |Added

 CC||qubo...@gmail.com

--- Comment #2 from qubo...@gmail.com ---
Changing to a profile with a different FPS while already having clips in the
timeline appears to have multiple side effects. Here is one in detail:

Fade effects' durations are changed to nonsense values.

Steps to reproduce:
1. Start kdenlive with a 1080p 30fps video default
2. Import 30 fps video
3. Drag video to timeline, cut it on left and right, remove all but the center
part
4. Add fade in and out effects to video
5. Change profile to 1080p 25fps
6. Refresh the clip's properties view (click in timeline, then on clip)

Expected result:
1a. The duration values remain the same OR
1b. The duration values are approximately scaled to have about the same
duration notwithstanding the change in frames per second

Actual result:
1. Both duration values are nonsensical (one is way too long, the other is 0)

Video:
https://youtu.be/pMNCAV9Q9Zg

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


[plasmashell] [Bug 356627] After login, greeted with black screen and empty taskbar

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356627

--- Comment #2 from gojunkma...@gmail.com ---
Sigh, 15 mins ago, I just started overwriting my fedora installation with
stable. I'll get back to you in a few hours once I get rawhide reinstalled.

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


[phonon-backend-gstreamer] [Bug 356527] Plasma Crash

2015-12-13 Thread Jeff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356527

--- Comment #1 from Jeff  ---
There at the end, I was having a total break down of KDE in Fedora 22.  So, I
wiped the drives and did a clean install to Fedora 23.  I'm not sure what the
problem was.  I think it was some data corruption.  It seemed to stem from
Akonadi.  From Gnome I couldn't access anything dependant upon MYSQL via
Akonadi.

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


[kde] [Bug 356620] New: KWin crashes after monitor stand-by in powersave mode

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356620

Bug ID: 356620
   Summary: KWin crashes after monitor stand-by in powersave 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: mich.delbia...@gmail.com

Application: kwin_x11 (5.2.2)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-39-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:
when some kind of input is given to the system, and the monitor turns on
- Custom settings of the application:
Ubuntu 15.04 Linux UX51VZ 3.19.0-39-generic #44-Ubuntu SMP Tue Dec 1 14:39:05
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
nVidia driver 352.63
X.Org 11.0

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5279a2e800 (LWP 1464))]

Thread 3 (Thread 0x7f525a03e700 (LWP 1502)):
#0  0x7f52794fb743 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f5277d45101 in qt_safe_select (nfds=16,
fdread=fdread@entry=0x7f525a98, fdwrite=fdwrite@entry=0x7f525d28,
fdexcept=fdexcept@entry=0x7f525fb8, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f5277d46cd2 in select (timeout=0x0, exceptfds=0x7f525fb8,
writefds=0x7f525d28, readfds=0x7f525a98, nfds=,
this=0x7f5258e0) at kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f525900,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f5277d47275 in QEventDispatcherUNIX::processEvents
(this=0x7f5258e0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f5277cee3e2 in QEventLoop::exec (this=this@entry=0x7f525a03dda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f5277aadb44 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f5271960f65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f5277ab2b0e in QThreadPrivate::start (arg=0x121bed0) at
thread/qthread_unix.cpp:337
#9  0x7f5270b2d6aa in start_thread (arg=0x7f525a03e700) at
pthread_create.c:333
#10 0x7f5279504eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f524bfff700 (LWP 1523)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f52768b7644 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f52768b7689 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f5270b2d6aa in start_thread (arg=0x7f524bfff700) at
pthread_create.c:333
#4  0x7f5279504eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5279a2e800 (LWP 1464)):
[KCrash Handler]
#6  KWin::ContrastEffect::uploadRegion (this=this@entry=0x1211400,
map=@0x7ffeafaa6398: 0x7f5258ad8070, region=...) at
../../effects/backgroundcontrast/contrast.cpp:219
#7  0x7f5276e6b6c5 in KWin::ContrastEffect::uploadGeometry
(this=this@entry=0x1211400, vbo=vbo@entry=0x1117450, region=...) at
../../effects/backgroundcontrast/contrast.cpp:235
#8  0x7f5276e6c04e in KWin::ContrastEffect::doContrast
(this=this@entry=0x1211400, shape=..., screen=..., opacity=3.94778981e-05) at
../../effects/backgroundcontrast/contrast.cpp:361
#9  0x7f5276e6c560 in KWin::ContrastEffect::drawWindow
(this=this@entry=0x1211400, w=w@entry=0xfa4900, mask=mask@entry=2, region=...,
data=...) at ../../effects/backgroundcontrast/contrast.cpp:340
#10 0x7f52790e40d1 in KWin::EffectsHandlerImpl::drawWindow (this=0x114f390,
w=w@entry=0xfa4900, mask=mask@entry=2, region=..., data=...) at
../effects.cpp:470
#11 0x7f5276de22db in KWin::BlurEffect::drawWindow
(this=this@entry=0x1139ae0, w=w@entry=0xfa4900, mask=mask@entry=2, region=...,
data=...) at ../../effects/blur/blur.cpp:415
#12 0x7f52790e40d1 in KWin::EffectsHandlerImpl::drawWindow (this=0x114f390,
w=w@entry=0xfa4900, mask=mask@entry=2, region=..., data=...) at
../effects.cpp:470
#13 0x7f52772be7c1 in KWin::Effect::drawWindow (this=this@entry=0x1211240,
w=w@entry=0xfa4900, mask=mask@entry=2, region=..., data=...) at
../../libkwineffects/kwineffects.cpp:580
#14 0x7f52790e40d1 in KWin::EffectsHandlerImpl::drawWindow (this=0x114f390,
w=w@entry=0xfa4900, mask=mask@entry=2, region=..., data=...) at
../effects.cpp:470
#15 0x7f52790ad841 in KWin::Scene::finalPaintWindow (this=,
w=w@entry=0xfa4900, mask=mask@entry=2, region=..., data=...) at
../scene.cpp:605
#16 0x7f52790e3f7a in KWin::EffectsHandlerImpl::paintWindow
(this=0x114f390, w=w@entry=0xfa4900, mask=mask@entry=2, 

[plasmashell] [Bug 355684] xembedsniproxy system tray icons are blank

2015-12-13 Thread Oleg via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355684

Oleg  changed:

   What|Removed |Added

 CC|mehanoid...@gmail.com   |

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


[kdenlive] [Bug 356536] Copying effect causes timeline-project inconsistency

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356536

qubo...@gmail.com changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from qubo...@gmail.com ---
Resolution confirmed working. Thank you very much!

Video:
https://youtu.be/SFD5p3TRy1E

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


[plasmashell] [Bug 356627] New: After login, greeted with black screen and empty taskbar

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356627

Bug ID: 356627
   Summary: After login, greeted with black screen and empty
taskbar
   Product: plasmashell
   Version: master
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gojunkma...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I am  on Fedora KDE rawhide and this has been driving me crazy for quite awhile
now (1 month or so). Since it hasn't been fixed yet, I'm reporting this bug.

It started happening around when you guys were updating icons for the taskbar.
Basically, after I login, I cannot right click the desktop (which is black with
no wallpaper) and the task bar is blank. I can still open programs by doing
Ctrl+Space and switch between them with Alt+Tab but it's really annoying. Hope
this can be fixed soon!

Reproducible: Always

Steps to Reproduce:
1. Upgrade to rawhide
(https://fedoraproject.org/wiki/Upgrading_Fedora_using_package_manager?rd=Upgrading_Fedora_using_yum).
2. dnf update
3. reboot

Actual Results:  
Black desktop, blank taskbar.

Expected Results:  
The normal desktop.

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


[klipper] [Bug 343519] Klipper systray widget is not closed automatically once a user has selected an item

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343519

--- Comment #5 from ric...@nakts.net ---
hmm, i'd disagree with middle-clicking to paste. haven't encountered many users
who use it for pasting, and there are way too many new mouses that do not even
have middle click ("clicking" mousewheel changes its rate, ugh - hate that).
thus most users, me including, use keyboard shortcuts to paste - be it ctrl+v
or shift+ins, and not closing klipper entry popup totally breaks this workflow.
it has the focus, thus i have to click an extra time in the window i want to
paste in.
normally it's just "click on the entry, hit keyboard shortcut" - now, besides
the extra click, i also have to identify the application, which is a nasty
break in the smooth workflow.

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


[plasmashell] [Bug 351425] Make the "windows" in taskbar smaller

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351425

--- Comment #24 from jeremy9...@gmail.com ---
I don't know it's not so bad now. A little bit smaller will be better perhaps ?

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


[kdenlive] [Bug 356629] weird gui problem

2015-12-13 Thread farid via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356629

--- Comment #1 from farid  ---
Created attachment 96049
  --> https://bugs.kde.org/attachment.cgi?id=96049=edit
weird gui behavior

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


[kdenlive] [Bug 356629] New: weird gui problem

2015-12-13 Thread farid via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356629

Bug ID: 356629
   Summary: weird gui problem
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: snd.no...@gmail.com

weird gui problem when double clicking on a clip in the bin. (see video)

Reproducible: Always

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


[gwenview] [Bug 356566] "move to trash" deletes in full-screen-mode

2015-12-13 Thread Leon via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356566

Leon  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Leon  ---
ok, seems a little strange: I have looked at the behaviour again today:
- until yesterday I had switched off the confirmation question in Dolphin: "Are
you sure, to move file to trash" (or similar...)
- today I have switched it back on and realized, that the image was moved to
trash only AFTER gwenview was closed.
- then I switched the confirmation question back to "off". But the error was
not reproducible. And even the images are moved to trash straight away (before
closing gwenview!)

Therefore I have set this report to solved...

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


[kde] [Bug 356619] I miss the option that you can change the width of the "blinking cursor" (=caret)

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356619

lisanne-wim...@exitweb.de changed:

   What|Removed |Added

Summary|I miss the option that you  |I miss the option that you
   |can change the width of the |can change the width of the
   |"blinking cursor"   |"blinking cursor" (=caret)

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


[kinfocenter] [Bug 356623] New: At application terminated

2015-12-13 Thread djynn via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356623

Bug ID: 356623
   Summary: At application terminated
   Product: kinfocenter
   Version: 5.4.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: johnny.vriesac...@orange.fr

Application: kinfocenter (5.4.2)

Qt Version: 5.5.0
Operating System: Linux 4.1.12-1-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
At closed (probably bug after instruction onclose... or ondestroy)

-- Backtrace:
Application: KDE Info Center (kinfocenter), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6d51c4d780 (LWP 6232))]

Thread 4 (Thread 0x7f6d3f925700 (LWP 6233)):
#0  0x7f6d4e762c1d in poll () at /lib64/libc.so.6
#1  0x7f6d47ceb422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f6d47ced00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f6d41c79c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f6d4ee5955f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f6d4b1240a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f6d4e76b04d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f6d2ad99700 (LWP 6234)):
#0  0x7f6d4b12805f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6d31815e53 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f6d318155d7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f6d4b1240a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6d4e76b04d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f6d29996700 (LWP 6239)):
#0  0x7f6d4a731d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f6d4a6ef538 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f6d4a6efd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f6d4a6eff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f6d4f08aa5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f6d4f031a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f6d4ee5484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f6d4db475f8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f6d4ee5955f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6d4b1240a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f6d4e76b04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6d51c4d780 (LWP 6232)):
[KCrash Handler]
#6  0x7f6d4e6bb187 in raise () at /lib64/libc.so.6
#7  0x7f6d4e6bc538 in abort () at /lib64/libc.so.6
#8  0x7f6d4ee4877e in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6d4f55e022 in  () at /usr/lib64/libQt5Gui.so.5
#10 0x7f6d4f5f4e66 in  () at /usr/lib64/libQt5Gui.so.5
#11 0x7f6d4f58e7ff in QCursor::QCursor(QCursor const&) () at
/usr/lib64/libQt5Gui.so.5
#12 0x7f6d4e029129 in QQuickItem::cursor() const () at
/usr/lib64/libQt5Quick.so.5
#13 0x7f6d4e0a937b in QQuickMouseArea::setCursorShape(Qt::CursorShape) ()
at /usr/lib64/libQt5Quick.so.5
#14 0x7f6d4e16ed5b in QQuickMouseArea::qt_metacall(QMetaObject::Call, int,
void**) () at /usr/lib64/libQt5Quick.so.5
#15 0x7f6d4dab0748 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int,
void**) () at /usr/lib64/libQt5Qml.so.5
#16 0x7f6d4daca790 in QQmlPropertyPrivate::writeBinding(QObject*,
QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#17 0x7f6d4db34053 in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#18 0x7f6d4db345de in
QQmlBinding::expressionChanged(QQmlJavaScriptExpression*) () at
/usr/lib64/libQt5Qml.so.5
#19 0x7f6d4db10c9f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /usr/lib64/libQt5Qml.so.5
#20 0x7f6d4dab8414 in QQmlData::signalEmitted(QAbstractDeclarativeData*,
QObject*, int, void**) () at /usr/lib64/libQt5Qml.so.5
#21 0x7f6d4f063213 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#22 0x7f6d4e030a38 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib64/libQt5Quick.so.5
#23 0x7f6d4e0309a5 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib64/libQt5Quick.so.5
#24 0x7f6d4e0309a5 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib64/libQt5Quick.so.5
#25 0x7f6d4e030ad6 in QQuickItem::setVisible(bool) () at
/usr/lib64/libQt5Quick.so.5
#26 0x7f6d4e032fed in  () at /usr/lib64/libQt5Quick.so.5
#27 0x7f6d4e033d7b in QQuickItem::qt_metacall(QMetaObject::Call, int,
void**) () at /usr/lib64/libQt5Quick.so.5
#28 0x7f6d4dab0748 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int,
void**) () at 

[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

2015-12-13 Thread jimbo1qaz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356592

--- Comment #2 from jimbo1qaz  ---
I'm using regular 2.9.10, but it identifies itself as 2.9.9. I originally
installed 2.9.9.1, upgraded, then un/reinstalled, and it still thinks it's
2.9.9. That is another bug.

If I delete the configuration, it still happens. I found this bug the very
first time I tried installing (2.9.9.1).

I'm a first-time (un)user, what's the animation beta?

I'm updating my Intel drivers.

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


[gwenview] [Bug 356630] New: wrong German translation for metadata/lens

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356630

Bug ID: 356630
   Summary: wrong German translation for metadata/lens
   Product: gwenview
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: rosena...@gmx.at
CC: myr...@kde.org

When selecting the image metadata (for JPG) to show, the dialog contains a
wrong translation for "lense" (Anglicism) and says "Linse" instead of
"Objektiv".

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


[frameworks-kio] [Bug 355390] Localized Dolphin crashes when I try to create new folder

2015-12-13 Thread Alex via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355390

Alex <2rb0a...@gmail.com> changed:

   What|Removed |Added

 CC||2rb0a...@gmail.com

--- Comment #17 from Alex <2rb0a...@gmail.com> ---
(In reply to David Faure from comment #14)
> Hmm, with 5.16 or 5.17 I don't get doubled entries in the Create New menu,
> when starting dolphin with LC_ALL=fr.
> 
> And I can't test LC_ALL=ru because... there's no [ru] translation in
> kio/src/new_file_templates/*.desktop. The string Папку appears nowhere in
> there.

The are some missing translation strings in
kio/src/new_file_templates/*.desktop. Adding those strings and rebuilding the
package solves the problem (i.e. there are no duplicate entries in menu any
more).
List of affected languages: [ar], [ast], [bs], [hi], [is], [ja], [ka], [km],
[ko], [lt], [lv], [ru], [se], [tr], [ug].

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread Blackpaw via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #19 from Blackpaw  ---
Its kinda depressing that such a basic usability feature has zero consideration
from the kde devs. Held the faith through the long KDE4 transition only to see
it tossed aside for new shiny.

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


[plasma-nm] [Bug 356622] Cannot change the group in the login form, and specifying it in the config results in not showing the login form (openconnect)

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356622

emele...@gmail.com changed:

   What|Removed |Added

Summary|Cannot change the group in  |Cannot change the group in
   |the login form, and |the login form, and
   |specifying it in the config |specifying it in the config
   |results in not showing the  |results in not showing the
   |login form  |login form (openconnect)
 CC||emele...@gmail.com

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


[kdenlive] [Bug 354940] Corrupted project after Video Profile change e.g. 1080p50 > 1080p25

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354940

--- Comment #3 from qubo...@gmail.com ---
One more issue:

Clips' starting position in the video file is changed to nonsense value while
duration remains the same.

Steps to reproduce:
1. Start kdenlive with a 1080p 30fps video default
2. Import 30 fps video
3. Drag video to timeline, cut it on left and right, remember what happens in
the scene, in particular how exactly it starts.
4. Move the clip to the left of the timeline.
5. Change profile to 1080p 25fps
6. Play back the project

Expected result:
1. The clip has approximately the duration and same start and end position
relative to its video file (depending on whether the positions/durations can be
divided evenly)

Actual result:
1. The duration appears to remain the same but the start position of the clip
relative to the video file's length appears to be different

Video:
https://youtu.be/9ZXmKGAG2l8

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


[kwalletmanager] [Bug 356624] New: KWalletManager - You are not allowed to save settings

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356624

Bug ID: 356624
   Summary: KWalletManager - You are not allowed to save settings
   Product: kwalletmanager
   Version: 2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: biholc...@l1049h.com

I found  Bug 353785 - kwalletmanager cannot save any settings which was marked
resolved - invalid so I filed a new report given that this problem does
definitely exist.

Centos 7 x64
QT 4.5
KDE Development Platform: 4.14.9
KDE Daemon: 4.14.9
KWalletManager info in Kwalletrc: [$Version]
update_info=kwallet-4.13.upd:kde4.13

I am running as my non-root user and when I open KWalletManger click settings
-> configure Wallet and try and change anything such as close when unused there
is a message at the top of the Configuration dialog that says "You are not
allowed to save the configuration".  This happens with the default or wallets I
create myself.  I modified the kwalletrc files settings to allow group (which
is same as the owner) to have write access.  Still did not work.

I was able to edit the kwallet.rc file and get the settings changed but I
should not have to.

I did searches and this problem goes back quite some time.  For some reason we
can not change settings through the GUI.  While I like the concept of KWallet
things like this make it hard to use.  I should be able to change my own
settings and not need sudo but I understand sudo doesn't work for this either.




Reproducible: Always

Steps to Reproduce:
1. Open KWalletManger and select a wallet
2. Click Settings -> Configure Wallet  There is the message "You are not
allowed to save the configuration"
3. Change a setting, say under Close Wallet.  The apply button is no longer
grayed out
4.  Click the Apply button.
5.  The apply button grays out but the OK does not become ungrayed. 
If you exit with cancel or the X no changes are made.  When you enter again the
values are the same as before the changes were made.

Actual Results:  
The changes did not take effect.

Expected Results:  
For the changes to be applied.

Editing the kwallet.rc file is not acceptable especially since there isn't much
documentation on what can be entered in it other than defaults.

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


[kde] [Bug 356628] New: Dependences kontact and Plasma

2015-12-13 Thread Christian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356628

Bug ID: 356628
   Summary: Dependences kontact and Plasma
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: cp.pia...@gmail.com

Application: plasma-desktop (4.11.16)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.13-desktop-2.mga5 x86_64
Distribution: "Mageia 5"

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

I delete kontact with Rpmdrake.
I think a problem with dependences

-- Backtrace:
Application: Shell del desktop di Plasma (plasma-desktop), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a2fd1d780 (LWP 2679))]

Thread 4 (Thread 0x7f1a06496700 (LWP 2681)):
#0  0x7f1a2e5b367f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1a20aed73a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQtScript.so.4
#2  0x7f1a20aed769 in  () at /lib64/libQtScript.so.4
#3  0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#4  0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f19810d2700 (LWP 2683)):
#0  0x7f1a2a444fe4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f1a2a4014d0 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f1a2a401de3 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f1a2a401fbc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f1a2e96be3e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#5  0x7f1a2e93d931 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f1a2e93dc45 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#7  0x7f1a2e83b899 in QThread::exec() () at /lib64/libQtCore.so.4
#8  0x7f1a2e91f3d3 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#9  0x7f1a2e83dfff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#10 0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#11 0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f197bbd6700 (LWP 2685)):
#0  0x7f1a2e5b367f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1a2e83e4f4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7f1a1fd41abc in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
() at /lib64/libthreadweaver.so.4
#3  0x7f1a1fd44623 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) () at /lib64/libthreadweaver.so.4
#4  0x7f1a1fd4329f in ThreadWeaver::Thread::run() () at
/lib64/libthreadweaver.so.4
#5  0x7f1a2e83dfff in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#6  0x7f1a2e5ae5bd in start_thread () at /lib64/libpthread.so.0
#7  0x7f1a2d3275cd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1a2fd1d780 (LWP 2679)):
[KCrash Handler]
#5  0x7f1a2e8390e6 in QReadWriteLock::~QReadWriteLock() () at
/lib64/libQtCore.so.4
#6  0x7f1a23484b6d in Plasma::QueryMatch::~QueryMatch() () at
/usr/lib64/libplasma.so.3
#7  0x7f1a23494af0 in
QList::removeAll(Plasma::QueryMatch const&) () at
/usr/lib64/libplasma.so.3
#8  0x7f1a23493708 in Plasma::RunnerContext::removeMatch(QString) () at
/usr/lib64/libplasma.so.3
#9  0x7f1980166674 in SolidRunner::refreshMatch(QString&) () at
/usr/lib64/kde4/krunner_solid.so
#10 0x7f1980166cf9 in SolidRunner::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/kde4/krunner_solid.so
#11 0x7f1a2e95288a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#12 0x7f198016856c in DeviceWrapper::dataUpdated(QString const&,
QHash) [clone .part.21] () at
/usr/lib64/kde4/krunner_solid.so
#13 0x7f1980169035 in DeviceWrapper::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /usr/lib64/kde4/krunner_solid.so
#14 0x7f1a2e95288a in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#15 0x7f1a234105d7 in Plasma::DataContainer::dataUpdated(QString const&,
QHash const&) () at /usr/lib64/libplasma.so.3
#16 0x7f1a23410f10 in Plasma::DataContainer::checkForUpdate() () at
/usr/lib64/libplasma.so.3
#17 0x7f1a23412e43 in Plasma::DataEngine::timerEvent(QTimerEvent*) () at
/usr/lib64/libplasma.so.3
#18 0x7f1a2e956c2b in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#19 0x7f1a2dab679c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#20 0x7f1a2dabce40 in 

[kdeplasma-addons] [Bug 355646] notes widget themes missing

2015-12-12 Thread wazyk via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355646

wazyk  changed:

   What|Removed |Added

 CC||eric.lemou...@gmail.com

--- Comment #1 from wazyk  ---
Same for me (Archlinux) since upgrade to plasma 5.5.

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


[kwin] [Bug 356557] New: Add "Fullscreen window" matching

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356557

Bug ID: 356557
   Summary: Add "Fullscreen window" matching
   Product: kwin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeremy9...@gmail.com

I think it's useful to provide a "Fullscreen window" matching in the "window
matching" tab of kwin rule to specify some rules only when the window is in
fullscreen.

Thanks.

Reproducible: Always

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


[Breeze] [Bug 356544] ktorrent icon

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356544

--- Comment #1 from tuk...@gmail.com ---
Just a correction: on the "Expected Results" I mention I was expecting the blue
arrow but I actually think that before the update an stylized black-and-white
arrow was being used.

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


[plasmashell] [Bug 356546] New: Another KDE Plasma 5.5.0 crash after removing panel

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356546

Bug ID: 356546
   Summary: Another KDE Plasma 5.5.0 crash after removing panel
   Product: plasmashell
   Version: 5.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: opensuse.lietuviu.ka...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution (Platform): openSUSE RPMs

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

Created new panel, moved to another edge of screen, added icons from desktop,
removed panel.

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

Thread 8 (Thread 0x7f018b0d8700 (LWP 32229)):
#0  0x7f019ab6fc1d in poll () from /lib64/libc.so.6
#1  0x7f019fa96422 in poll (__timeout=-1, __nfds=1, __fds=0x7f018b0d7d00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x16b6e80, cond=cond@entry=0x16b6ec0,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x7f019fa9800f in xcb_wait_for_event (c=0x16b6e80) at xcb_in.c:693
#4  0x7f018d228c29 in QXcbEventReader::run (this=0x16c53d0) at
qxcbconnection.cpp:1214
#5  0x7f019b26655f in QThreadPrivate::start (arg=0x16c53d0) at
thread/qthread_unix.cpp:331
#6  0x7f019a3790a4 in start_thread () from /lib64/libpthread.so.0
#7  0x7f019ab7804d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f018892a700 (LWP 32231)):
#0  0x7f01a1491700 in _dl_update_slotinfo () from
/lib64/ld-linux-x86-64.so.2
#1  0x7f01a148115f in update_get_addr () from /lib64/ld-linux-x86-64.so.2
#2  0x7f019b265582 in get_thread_data () at thread/qthread_unix.cpp:181
#3  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:212
#4  0x7f019b498541 in postEventSourcePrepare (timeout=0x0,
s=0x7f017c0012d0) at kernel/qeventdispatcher_glib.cpp:247
#5  postEventSourceCheck (source=0x7f017c0012d0) at
kernel/qeventdispatcher_glib.cpp:264
#6  0x7f01972508f1 in g_main_context_check
(context=context@entry=0x7f017c000990, max_priority=2147483647,
fds=fds@entry=0x7f017c003070, n_fds=n_fds@entry=1) at gmain.c:3649
#7  0x7f0197250df8 in g_main_context_iterate
(context=context@entry=0x7f017c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3805
#8  0x7f0197250f7c in g_main_context_iteration (context=0x7f017c000990,
may_block=1) at gmain.c:3869
#9  0x7f019b497a5b in QEventDispatcherGlib::processEvents
(this=0x7f017c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#10 0x7f019b43ea63 in QEventLoop::exec (this=this@entry=0x7f0188929df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#11 0x7f019b26184a in QThread::exec (this=this@entry=0x178dd00) at
thread/qthread.cpp:503
#12 0x7f019e54a5f8 in QQmlThreadPrivate::run (this=0x178dd00) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#13 0x7f019b26655f in QThreadPrivate::start (arg=0x178dd00) at
thread/qthread_unix.cpp:331
#14 0x7f019a3790a4 in start_thread () from /lib64/libpthread.so.0
#15 0x7f019ab7804d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f0171410700 (LWP 32235)):
#0  0x7f01972506b4 in g_main_context_query
(context=context@entry=0x7f016c000990, max_priority=2147483647,
timeout=timeout@entry=0x7f017140fcbc, fds=fds@entry=0x7f016c002e70,
n_fds=n_fds@entry=1) at gmain.c:3514
#1  0x7f0197250dcf in g_main_context_iterate
(context=context@entry=0x7f016c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3790
#2  0x7f0197250f7c in g_main_context_iteration (context=0x7f016c000990,
may_block=1) at gmain.c:3869
#3  0x7f019b497a5b in QEventDispatcherGlib::processEvents
(this=0x7f016c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f019b43ea63 in QEventLoop::exec (this=this@entry=0x7f017140fdf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f019b26184a in QThread::exec (this=this@entry=0x199bed0) at
thread/qthread.cpp:503
#6  0x7f019e54a5f8 in QQmlThreadPrivate::run (this=0x199bed0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7f019b26655f in QThreadPrivate::start (arg=0x199bed0) at
thread/qthread_unix.cpp:331
#8  0x7f019a3790a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f019ab7804d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f016baad700 (LWP 32236)):
#0  0x7f019a37d05f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  

[kde] [Bug 356552] New: Bluetooth file transfer crashes

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356552

Bug ID: 356552
   Summary: Bluetooth file transfer crashes
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jdiazg...@gmail.com

Application: kdeinit5 ()

Qt Version: 5.4.2
Operating System: Linux 4.2.0-19-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
I got this error while transfering files from Android device

-- Backtrace:
Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f90c413f780 (LWP 1250))]

Thread 7 (Thread 0x7f90ae83b700 (LWP 1253)):
#0  0x7f90c28d68dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f90c1fbcbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f90c1fbe74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f90b15d4a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f90c2c472be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f90c063e6aa in start_thread (arg=0x7f90ae83b700) at
pthread_create.c:333
#6  0x7f90c28e1eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f90a695a700 (LWP 1257)):
#0  0x7f90c28d249d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f90be585f75 in ?? () from
/usr/lib/nvidia-352/tls/libnvidia-tls.so.352.63
#2  0x7f90bf95b4e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f90bf917cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f90bf918190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f90bf9182fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f90bf918339 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f90bf93e965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f90c063e6aa in start_thread (arg=0x7f90a695a700) at
pthread_create.c:333
#9  0x7f90c28e1eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f90a6159700 (LWP 1258)):
#0  0x7f90c28d68dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f90bf9181ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f90bf918572 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f90a74e84c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f90bf93e965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f90c063e6aa in start_thread (arg=0x7f90a6159700) at
pthread_create.c:333
#6  0x7f90c28e1eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f90967ad700 (LWP 1287)):
#0  0x7f90c28d68dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f90bf9181ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f90bf9182fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f90c2e7e29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f90c2e2475a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f90c2c423d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f909fdc58f7 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7f90c2c472be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f90c063e6aa in start_thread (arg=0x7f90967ad700) at
pthread_create.c:333
#9  0x7f90c28e1eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f9095fac700 (LWP 1288)):
#0  0x7f90bf915267 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f90bf91771b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f90bf91811b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f90bf9182fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f90c2e7e29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f90c2e2475a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f90c2c423d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f90c2c472be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f90c063e6aa in start_thread (arg=0x7f9095fac700) at
pthread_create.c:333
#9  0x7f90c28e1eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f90870ff700 (LWP 1556)):
#0  0x7f90c28d68dd in poll () at 

[plasma-pa] [Bug 355925] The dropdown lists are at the wrong place

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355925

jeremy9...@gmail.com changed:

   What|Removed |Added

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

--- Comment #7 from jeremy9...@gmail.com ---
Sorry to reopen it but it's just to be sure that will be fixed by a new Qt
version like I said in my previous comment.
Thanks

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


[digikam] [Bug 353789] Add new tool to apply Lut3D on image [patch]

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353789

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

It miss versioning support with this 3D Lut filter. It's used by editor and BQM
to register filters order/parameters used while to apply on image. These
settings is pushed in XMP metadata.

Look like core/libs/dimg/filters/dimgfiltermanager.cpp do not register 3DLut.

In filter implementation readParameters() is not implemented...

Gilles

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


[Touchpad-KCM] [Bug 344958] No touchpad found

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=344958

d@byom.de changed:

   What|Removed |Added

 CC||d@byom.de

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


[Breeze] [Bug 356544] New: ktorrent icon

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356544

Bug ID: 356544
   Summary: ktorrent icon
   Product: Breeze
   Version: 5.4.3
  Platform: Debian testing
   URL: http://imgur.com/LphLUK0
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: uri_herr...@nitrux.in
  Reporter: tuk...@gmail.com
CC: kain...@gmail.com

Hello, I'm having an issue since updating Debian testing yesterday.

I'm not sure how icon sets work but it seems to me that there is a problem with
the icon for ktorrent . I have "breeze" selected as my KDE icon theme and even
though I can find appropriate icons on /usr/share/icons/breeze none of them are
being used on the tray area. You can see the URL I informed to confirm that. If
I hover the mouse over the icon then the pop-up ktorrent panel shows up (with
download/upload speeds/etc) and inside it is the correct icon - the blue,
downward-pointing arrow.

I know the BTS is "not a forum to share opinions on design" but the icon I have
on my system panel right now is so bad that I'm inclined to believe it's a bug.
It's a blank square with a tiny downwards-pointing arrow, it actually made me
think of a clipboard the first time I saw it, so I thought it was Klipper.
Especially considering there are appropriate icons on the /icons/ folder and
that this was not the icon being used before I updated the system.

The icon on the task manager bar and KDE "start menu" are the blue arrow too,
appropriately, just the tray icon is different.

Anyway thanks for the effort and great job on KDE's look and feel, I hope I am
helping and am sorry if this is inappropriate since I'm not sure about how
icons work and all.

Reproducible: Always

Steps to Reproduce:
1. Start KTorrent
2. Check tray icon
3. Quit and restart KTorrent for reproducibility

Actual Results:  
Wrong/inadequate icon shows up.

Expected Results:  
The blue arrow to be the tray icon, like in the task manager bar and KDE "start
menu".

My screen resolution is 1366x768, compositing is enabled (I noticed the when
disabled it tends to change tray icon size).

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


[drkonqi] [Bug 356250] Two "Help" buttons on crash reporting assistant, once helpful, one useless

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356250

opensuse.lietuviu.ka...@gmail.com changed:

   What|Removed |Added

 CC||opensuse.lietuviu.kalba@gma
   ||il.com

--- Comment #3 from opensuse.lietuviu.ka...@gmail.com ---
Created attachment 96005
  --> https://bugs.kde.org/attachment.cgi?id=96005=edit
Still in KDE Plasma 5.5.0

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


[plasmashell] [Bug 338506] image wallpapers are blurry in scaled and scaled and cropped mode

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=338506

--- Comment #33 from jeremy9...@gmail.com ---
> "if this important functionality is broken in Plasma 5 (despite it being a 
> solved problem for a long time, and working perfectly in every other 
> contemporary operating system and desktop environment), I wonder what else is 
> broken."

I agree with this feeling but I think it's not fair. A lot of work has been,
and is being made in Plasma 5, KF5 and KDE apps.

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


[systemsettings] [Bug 356551] Control Panel not showing when selecting 'external monitor only' in settings

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356551

le.t...@gmail.com changed:

   What|Removed |Added

Summary|Control Panel not showing   |Control Panel not showing
   |when selecting external |when selecting 'external
   |monitor only in settings|monitor only' in settings

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


[systemsettings] [Bug 356551] New: Control Panel not showing when selecting external monitor only in settings

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356551

Bug ID: 356551
   Summary: Control Panel not showing when selecting external
monitor only in settings
   Product: systemsettings
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: le.t...@gmail.com

When iterating through the different Monitor configurations available (only
Laptop, mirror, laptop main - external extend, internal main - laptop extend,
only external) for 'external only' the control panel does not show. Manually
choosing this configuration in settings yields the same result.

Reproducible: Always

Steps to Reproduce:
1. Have Laptop, external Monitor connected
2. Iterate by hotkey or choose external as main monitor and only active in
settings

Actual Results:  
Control panel is not visible.

Expected Results:  
Control panel is on the main screen.

System:Host: sumomo Kernel: 4.3.2-1-ck x86_64 (64 bit) Desktop: KDE Plasma
5.4.3
   Distro: ManjaroLinux 15.12-rc1 Capella
Machine:   System: LENOVO product: 6474BA1 v: ThinkPad T400
   Mobo: LENOVO model: 6474BA1 Bios: LENOVO v: 7UET94WW (3.24 ) date:
10/17/2012
CPU:   Dual core Intel Core2 Duo P8400 (-MCP-) cache: 3072 KB 
   clock speeds: max: 2267 MHz 1: 800 MHz 2: 2267 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
   Display Server: X.Org 1.17.4 driver: intel Resolution:
1920x1080@60.00hz
   GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1
Mesa 11.0.6
Audio: Card Intel 82801I (ICH9 Family) HD Audio Controller driver:
snd_hda_intel Sound: ALSA v: k4.3.2-1-ck
Network:   Card-1: Intel 82567LM Gigabit Network Connection driver: e1000e
   IF: enp0s25 state: down mac: 
   Card-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
   IF: wlp3s0 state: up mac: 
Drives:HDD Total Size: 160.0GB (28.4% used) ID-1: /dev/sda model:
INTEL_SSDSA2BW16 size: 160.0GB
Partition: ID-1: / size: 51G used: 43G (86%) fs: btrfs dev: /dev/sda4
   ID-2: /boot size: 1.2G used: 87M (9%) fs: btrfs dev: /dev/sda3
Sensors:   System Temperatures: cpu: 45.0C mobo: 44.0C
   Fan Speeds (in rpm): cpu: N/A fan-1: 1968
Info:  Processes: 186 Uptime: 12:22 Memory: 1543.5/7883.4MB Client: Shell
(bash) inxi: 2.2.31

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


[Oxygen] [Bug 356547] New: Missing icons for widgets

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356547

Bug ID: 356547
   Summary: Missing icons for widgets
   Product: Oxygen
   Version: 5.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: icons
  Assignee: n...@oxygen-icons.org
  Reporter: opensuse.lietuviu.ka...@gmail.com

Oxygen icon theme is not complete: widgets icons missing.

Reproducible: Always

Steps to Reproduce:
1. Remove Breeze icons theme
2. Remove all catch
3. relogin
4. try add new widgets

Actual Results:  
Some widgets has no icons

Expected Results:  
All widgets has all icons

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


[Oxygen] [Bug 356547] Missing icons for widgets

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356547

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
Created attachment 96006
  --> https://bugs.kde.org/attachment.cgi?id=96006=edit
Video

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


[plasmashell] [Bug 356549] New: Widgets don't want to show handles for manipulating

2015-12-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356549

Bug ID: 356549
   Summary: Widgets don't want to show handles for manipulating
   Product: plasmashell
   Version: 5.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: opensuse.lietuviu.ka...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Hover on widget, but it don't show handles. Widgets are unlocked.

Reproducible: Always

Steps to Reproduce:
1. Hover mouse over FolderView widget in Desktop

Actual Results:  
Handles don't appears

Expected Results:  
Handles  appears

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


[krita] [Bug 356369] Choose brush preset - update

2015-12-13 Thread eliotJ via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356369

--- Comment #5 from eliotJ  ---
Nice to see some progress of these things was already done...

After disscusing on IRC with Boud I write here:
I want point two things:
1. Save icon (these near tags text field - right down corner of the brush
selector window) is missed in these Krita 3.0 pre-alpha screenshot.

2. I have big hopes for these "Tag" text intead of "+" icon. Boud thinking
about some kind of icon describing better functionality of this button than
"+". IMHO it can be tricky to designing good icon... Text "Tag" can be also
temporairy solution (easy and fast to add until good icon would be designed).

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


[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

2015-12-13 Thread jimbo1qaz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356592

--- Comment #3 from jimbo1qaz  ---
Additionally, it occasionally crashes when creating new image. I've only
observed this when mactype is enabled???

I tried updating to latest Intel and AMD drivers and disabling MacType from
starting at system boot (no potential for hooks), but the crash still happens.

Does not happen on Safe Mode.

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


[plasmashell] [Bug 349547] Adwaita cursor theme does not change cursors at window borders

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=349547

slartibar...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from slartibar...@gmail.com ---
seems ok in 5.5.0 / fedora23

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


[kdenlive] [Bug 356626] Effects: Can't drag favorite effects when switching from all effects with active search

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356626

qubo...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|FIXED   |---

--- Comment #2 from qubo...@gmail.com ---
It seems to not work still in
kdenlive-git v15.11.90-85-g298c656 master
catalyst-libgl 15.11-1
ffmpeg 1:2.8.3-1
ffmpeg-compat 1:0.10.16-4
frei0r-plugins 1.4-3
libx264 2:148.20150725-1
mlt-git r4148.v0.9.2.370.g1065fda-1
mlt-python-bindings 0.9.8-4
movit-git r720.813bc3b-1
qt5-base 5.5.1-5
x264 2:148.20150725-1
xorg-server 1.16.4-1

I deleted the build directory in case some old compile results for some reason
blocked the fix from working. It didn't help.

Video:
https://youtu.be/XZwTANS0aPE

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


[plasmashell] [Bug 356618] KWin Sceen Edge effect appears when using Panel Windows can Cover

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356618

slartibar...@gmail.com changed:

   What|Removed |Added

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

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


[plasmashell] [Bug 356618] KWin Sceen Edge effect appears when using Panel Windows can Cover

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356618

--- Comment #2 from slartibar...@gmail.com ---
Thanks for the quick reply,

but i wouldn't call it 'resolved', because the combination of 
glowing screen edges 
and
visible taskbar, but option 'windows can cover' 

should NOT activate the edge glow

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread andy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #25 from andy  ---
Plasma is missing a few features kde4 had, maybe they come, but unity is like
for old woman, windows for ignorants, xfce ist nearly good but not very
intuitive, mate is much to simple, still plasma5 is the best desktop around
here.

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


[kdenlive] [Bug 356626] Effects: Can't drag favorite effects when switching from all effects with active search

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356626

--- Comment #4 from qubo...@gmail.com ---
Confirmed working in
kdenlive-git v15.11.90-86-gb03db93 master

Thanks!

Video:
https://youtu.be/Zep6prqk_E8

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


[kdenlive] [Bug 356642] New: FEATURE REQUEST - Allow to reduce timeline height

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356642

Bug ID: 356642
   Summary: FEATURE REQUEST - Allow to reduce timeline height
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: qubo...@gmail.com

As a user and producer of Kdenlive tutorials, I would like to be able to reduce
the height of the timeline, so I have more space for other elements while not
working with the timeline or in general in simple one-track projects.

Video showing the minimum size:
https://youtu.be/PjFgGrbw0Po

This is entirely a feature request and if it is approved, I would recommend to
wait until after the next release to include it, just in case it might trigger
not yet discovered bugs.

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


[gwenview] [Bug 356599] 15.08.3 Crash in QGraphicsProxyWidget::focusNextPrevChild

2015-12-13 Thread Michał via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356599

--- Comment #1 from Michał  ---
Hmm, I can't upload 22 MB file, beacuse of 4 MB size limit. But I think any CR2
file should do the trick…

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread Blackpaw via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #21 from Blackpaw  ---
Sums up the new attitude in KDE - basic usability is a "Pet" feature. I assume
the new low contrast flat borderless look, which is terrible for anyone with
less than perfect vision is not a pet feature. Its a crucial way fwd into the
future!

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread Blackpaw via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #22 from Blackpaw  ---
UX designers have killed kde.

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


[kdeconnect] [Bug 356637] New: Add Android Widget

2015-12-13 Thread sederic via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356637

Bug ID: 356637
   Summary: Add Android Widget
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 5.x
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: sebastian.end...@online.de

It would be nice if the Android App of KDE connect provides a Widget for Media
Control and maybe another one for other features.

And I'd be nice if the app would act like a media player on the smart phone so
that the lockscreen gets media control buttons and displays the songs image and
so on, but I think this does not work with Android's API...

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


[kdenlive] [Bug 356633] Enabling/disabling proxy clips makes clips in timeline forget/lose fade from/to black effects

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356633

qubo...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from qubo...@gmail.com ---
Thank you very much!

Video
https://youtu.be/xNUYhspt9pk

Note: in the video there is an unrelated crash (movit) and also the thumbnail
looks weird after the proxy has been generated but I'll have to take another
look and report it then if it's still present.

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


[plasmashell] [Bug 356640] New: Plasma crashes when importing comic into comics plasmoid

2015-12-13 Thread kisik21 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356640

Bug ID: 356640
   Summary: Plasma crashes when importing comic into comics
plasmoid
   Product: plasmashell
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kisik2...@live.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.0)

Qt Version: 5.5.1
Operating System: Linux 4.2.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I just installed Plasma and found a comic plasmoid. Then I tried to load XKCD
comic into it, and on saving settings... Plasma crashes!
- Custom settings of the application:
Tried to set up XKCD comic book

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Bus error
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4b12ac3800 (LWP 770))]

Thread 8 (Thread 0x7f4af8ed3700 (LWP 774)):
#0  0x7f4b0bf2c18d in poll () from /usr/lib/libc.so.6
#1  0x7f4b083cbfbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4b083cc0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4b0c86532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4b0c80c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4b0c6289d4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4b0f9f7a75 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f4b0c62d97e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4b0b7344a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4b0bf3513d in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f4af0c3e700 (LWP 776)):
#0  0x7f4b0b73a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4af1f71c5a in ?? () from /usr/lib/xorg/modules/dri/r600_dri.so
#2  0x7f4af1f71397 in ?? () from /usr/lib/xorg/modules/dri/r600_dri.so
#3  0x7f4b0b7344a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f4b0bf3513d in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f4ae7fdb700 (LWP 777)):
#0  0x7f4b0bf2816d in read () from /usr/lib/libc.so.6
#1  0x7f4b0840f270 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4b083cbaa4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4b083cbf60 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f4b083cc0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f4b0c86532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7f4b0c80c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7f4b0c6289d4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7f4b0f9f7a75 in ?? () from /usr/lib/libQt5Qml.so.5
#9  0x7f4b0c62d97e in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7f4b0b7344a4 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f4b0bf3513d in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f4ae63af700 (LWP 778)):
#0  0x7f4b08410614 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7f4b083cbe6d in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4b083cc0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4b0c86532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4b0c80c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4b0c6289d4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4b0f9f7a75 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f4b0c62d97e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4b0b7344a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4b0bf3513d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f4aded0e700 (LWP 779)):
#0  0x7f4b0b73a07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4b1223dfb4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f4b1223dff9 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f4b0b7344a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f4b0bf3513d in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f4adca98700 (LWP 780)):
#0  0x7f4b0bf2c18d in poll () from /usr/lib/libc.so.6
#1  0x7f4b083cbfbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4b083cc0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4b0c86532b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4b0c80c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4b0c6289d4 in QThread::exec() () from 

[kdenlive] [Bug 356642] FEATURE REQUEST - Allow to reduce timeline height

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356642

--- Comment #1 from qubo...@gmail.com ---
Created attachment 96051
  --> https://bugs.kde.org/attachment.cgi?id=96051=edit
screenshot of smallest possible UI element sizes

PS: I would like to allow the same for the clip monitor and the project monitor

For reference, I'm attaching a screenshot of all UI tabs with their minimum
window size in a window manager without borders (awesome wm).

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


[kdenlive] [Bug 356643] New: Clip properties shows properties for proxy instead of actual clip

2015-12-13 Thread Kubuntiac via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356643

Bug ID: 356643
   Summary: Clip properties shows properties for proxy instead of
actual clip
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: user...@xymail.info

When displaying clip properties, the properties that are displayed are actually
of the clips proxy, not the clip itself.

Reproducible: Always

Steps to Reproduce:
1. Right click a clip and choose Clip Properties
2. Note the properties shown
3. Right click that same clip and choose "Proxy clip"
4. Click on a different clip, and then click back on the original clip to
refresh what's shown in clip properties panel.

Actual Results:  
The properties shown in "Clip Properties" now reflect the properties of the
proxy

Expected Results:  
The properties continue to show the properties of the actual clip.

If proxy properties are shown, they're shown *in addition* to the original
clips properties underneath in a separate section. The most expected behavior
though, is that proxy properties aren't shown at all, just the properties of
the actual clip.

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


[kdenlive] [Bug 356643] "Clip Properties" shows properties for proxy instead of the clip, when clip is proxied

2015-12-13 Thread Kubuntiac via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356643

Kubuntiac  changed:

   What|Removed |Added

Summary|Clip properties shows   |"Clip Properties" shows
   |properties for proxy|properties for proxy
   |instead of actual clip  |instead of the clip, when
   ||clip is proxied

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


[kdenlive] [Bug 356644] "Manage profiles" button is missing from Project > Project Settings > Proxy clips

2015-12-13 Thread Kubuntiac via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356644

--- Comment #1 from Kubuntiac  ---
Created attachment 96052
  --> https://bugs.kde.org/attachment.cgi?id=96052=edit
The two proxy settings sections in the ui compared

In a nutshell, can we make the first operate the same as the second?

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread andy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #23 from andy  ---
the transition from kde3 to kde4 was also problematic,
since it was a total rework. Surely it is a whole lot of work
it has been done, we should also appreciate that, 
i could imagine that important features like
this and the desktop wallpaper issue will be solved some
day. Right now is the pin button solution practicable for
the time till then...tried xfce,  plasma is still the best :-)

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


[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable

2015-12-13 Thread andy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=332512

--- Comment #28 from andy  ---
here a request, maybe could the pin button implemented temporarily, since it
goes away everytime an update comes, i can live with that pin button for a
while  : - )

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


[plasmashell] [Bug 355592] Thumbnail icons in folder view layout desktop have wrong fixed 1:1 aspect ratio

2015-12-13 Thread Shiba via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355592

Shiba  changed:

   What|Removed |Added

 CC||shibo...@gmx.com

--- Comment #2 from Shiba  ---
Same for me

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


[plasmashell] [Bug 356627] After login, greeted with black screen and empty taskbar

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356627

--- Comment #3 from gojunkma...@gmail.com ---
Ok, I finally got everything up and running. Here is the .xsession_errors file:

startkde: Starting up...
Qt: Session management error: networkIdsList argument is NULL
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kf5.kded: found kded module "printmanager" by prepending 'kded_' to the library
path, please fix your metadata.
kf5.kded: found kded module "accounts" by prepending 'kded_' to the library
path, please fix your metadata.
Qt: Session management error: networkIdsList argument is NULL
kf5.kded: found kded module "colord" by prepending 'kded_' to the library path,
please fix your metadata.
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not
be saved or shared with other applications.
powerdevil: No outputs have backlight property
Service started, version: 
Service started, version: 
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
"/home/SUPERCILEX/.local/share/icc/." is not an ICC profile
"/home/SUPERCILEX/.local/share/icc/.." is not an ICC profile
kscreen: Failed to request backend: "org.freedesktop.DBus.Error.UnknownObject"
: "No such object path '/'"
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD RS880 (DRM 2.43.0,
LLVM 3.7.0)
OpenGL version string:  3.0 Mesa 11.2.0-devel (git-56aff6b)
OpenGL shading language version string: 1.30
Driver: R600G
GPU class:  R600
OpenGL version: 3.0
GLSL version:   1.30
Mesa version:   11.2
Linux kernel version:   4.4
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
Invalid service name "/org/kde/polkit-kde-authentication-agent-1" using:
"/org/kde/polkitkdeauthenticationagent1"
kcminit not running? If we are running with mobile profile or in another
platform other than X11 this is normal.
"/home/SUPERCILEX/.local/share/icc/." is not an ICC profile
"/home/SUPERCILEX/.local/share/icc/.." is not an ICC profile
kf5.kded: found kded module "ktp_integration_module" by prepending 'kded_' to
the library path, please fix your metadata.
kf5.kded: found kded module "ktp_approver" by prepending 'kded_' to the library
path, please fix your metadata.
EDID ICC Profile already exists
"/home/SUPERCILEX/.local/share/icc/edid-73bcd3f4519930481792d672523db468.icc"
Failed to register device: "device id 'xrandr-Seiko Epson Corporation' already
exists"
EDID ICC Profile already exists
"/home/SUPERCILEX/.local/share/icc/edid-73bcd3f4519930481792d672523db468.icc"
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
QMetaProperty::read: Unable to handle unregistered datatype
'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'
vmware-user: could not open /proc/fs/vmblock/dev
powerdevil: Handle button events action could not check for screen
configuration
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not
be saved or shared with other applications.
"Trying to convert empty KLocalizedString to QString."
"Trying to convert empty KLocalizedString to QString."
"Trying to convert empty KLocalizedString to QString."
Failed to open layout memory xml file for reading
"/home/SUPERCILEX/.local/share/kded5/keyboard/session/layout_memory.xml" error:
5
kf5.kded: found kded module "touchpad" by prepending 'kded_' to the library
path, please fix your metadata.
No metadata file in the package, expected it at:
"/usr/share/kde-settings/kde-profile/default/share/plasma/shells/org.kde.plasma.desktop//metadata.desktop"
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
kf5.kded: found kded module "kwrited" by prepending 'kded_' to the library
path, please fix your metadata.
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
No metadata file in the package, expected it at:
"/usr/share/kde-settings/kde-profile/default/share/plasma/shells/org.kde.plasma.desktop//metadata.desktop"
Constructing a KPluginInfo object from old style JSON. Please use
kcoreaddons_desktop_to_json() for "" instead of kservice_desktop_to_json() in
your CMake code.
Warning: corona package invalid
Constructing a KPluginInfo object from old style JSON. Please use
kcoreaddons_desktop_to_json() for "" instead of kservice_desktop_to_json() in
your CMake 

[plasmashell] [Bug 356631] New: Plasma crash

2015-12-13 Thread Ivan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356631

Bug ID: 356631
   Summary: Plasma crash
   Product: plasmashell
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: null.0.b...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Perform firefox closing, clementine player was running at this time

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

Thread 9 (Thread 0x7f1e8bb17700 (LWP 21972)):
#0  0x7f1e9b5eac1d in poll () at /lib64/libc.so.6
#1  0x7f1ea0511422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f1ea051300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f1e8dc67c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f1e9bce155f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f1e9adf40a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f1e9b5f304d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f1e88eef700 (LWP 21988)):
#0  0x7f1e9b5e6ced in read () at /lib64/libc.so.6
#1  0x7f1e97d0cb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e97ccb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e97ccbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f1e97ccbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f1e9bf12a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f1e9beb9a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f1e9bcdc84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f1e9efc55f8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f1e9bce155f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f1e9adf40a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f1e9b5f304d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f1e77f0c700 (LWP 21989)):
#0  0x7f1e9bf13438 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f1e97ccb8f1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f1e97ccbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f1e97ccbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f1e9bf12a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f1e9beb9a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f1e9bcdc84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f1e9efc55f8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f1e9bce155f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f1e9adf40a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f1e9b5f304d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f1e762bd700 (LWP 21992)):
#0  0x7f1e9b5e6ced in read () at /lib64/libc.so.6
#1  0x7f1e97d0cb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e97ccb999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e97ccbdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f1e97ccbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f1e9bf12a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f1e9beb9a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f1e9bcdc84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f1e9efc55f8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f1e9bce155f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f1e9adf40a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f1e9b5f304d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f1e7493c700 (LWP 21993)):
#0  0x7f1e9adf805f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1ea17787eb in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f1ea1778819 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f1e9adf40a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1e9b5f304d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f1de7fff700 (LWP 21998)):
#0  0x7f1e9b5eac1d in poll () at /lib64/libc.so.6
#1  0x7f1e97ccbe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e97ccbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e9bf12a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1e9beb9a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f1e9bcdc84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  

[kde-gtk-config] [Bug 356635] New: Wrong cursor theme in gtk applications (e.g. firefox)

2015-12-13 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356635

Bug ID: 356635
   Summary: Wrong cursor theme in gtk applications (e.g. firefox)
   Product: kde-gtk-config
   Version: 5.5.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: manutort...@chakra-project.org
  Reporter: slartibar...@gmail.com
CC: aleix...@kde.org

Selecting adwaita-cursor theme instead of breeze works fine in kde/qt
applications. But, in firefox, the breeze cursor theme  remains active, so
hovering over firefox you got the 'new' mouse icon, leaving firefox switches to
the adwaita mouse icons...


Reproducible: Always

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


<    2   3   4   5   6   7   8   9   10   11   >