[ksmserver] [Bug 346949] Shutdown scripts are not executed

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=346949

Soukyuu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.5.1
 Resolution|--- |FIXED

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


[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Bernd Steinhauser via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #8 from Bernd Steinhauser  ---
(In reply to Thomas Lübking from comment #6)
> Even gtk+ windows should just kick the NETWM moveresize in the WM
> 
> > kwin4_effect_translucency
> Try to disable this.
Will do.

> > electricBorderMaximize: true
> > electricBorderTiling: true
> and this
ok.

> Do you have autohiding panels on one of the edges?
No.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #42 from Thomas Lübking  ---
Yes, is. Stunning.

The xft image is RGB32 here, may depend on whether it's set to translucent
(though there ARGB32 instead of pre-multiplied is used)

We need this patch tested on all possible GPUs (notably intel/sna!)

diff --git a/kcms/kfontinst/lib/FcEngine.cpp b/kcms/kfontinst/lib/FcEngine.cpp
index 19b7206..6c731dc 100644
--- a/kcms/kfontinst/lib/FcEngine.cpp
+++ b/kcms/kfontinst/lib/FcEngine.cpp
@@ -537,7 +537,7 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
 if (!xImage) {
 return QImage();
 }
-return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_ARGB32_Premultiplied, , xImage);
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_RGB32, , xImage);
 }

 inline int point2Pixel(int point)

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

2016-01-09 Thread Martin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=274931

Martin  changed:

   What|Removed |Added

   Target Milestone|4.11|---
Version|unspecified |5.5.3

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


[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357577

--- Comment #16 from caulier.gil...@gmail.com ---
Qt said that QVector are used out on index. This is an internal use, not from
digiKam.

The Digikam::AbstractAlbumModel::slotAlbumAboutToBeAdded is called with these
arguments (this=0x1390690, album=0x21f7de0, parent=0x21f6410, prev=0x0)

prev = 0 wnat mean that a parent album must be registered in model. Code
relevant from digiKam is here :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/models/abstractalbummodel.cpp#L422

This call Qt like this QAbstractItemModel::beginInsertRows (this=0x1390690,
parent=..., first=0, last=0)

...and it crash. Note that first and last are null, which is fine with Qt API :

http://doc.qt.io/qt-5/qabstractitemmodel.html#beginInsertRows

Gilles Caulier

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


[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying

2016-01-09 Thread Johannes Pfrang via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357063

Johannes Pfrang  changed:

   What|Removed |Added

 CC||johannespfrang+...@gmail.co
   ||m

--- Comment #6 from Johannes Pfrang  ---
Duplicate of bug 357388

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


[konsole] [Bug 357573] Konsole freeze if executed on secondary dual-head (Nvidia Twinview) display

2016-01-09 Thread Johannes Pfrang via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357573

Johannes Pfrang  changed:

   What|Removed |Added

 CC||johannespfrang+...@gmail.co
   ||m

--- Comment #1 from Johannes Pfrang  ---
Duplicate of bug 357388.

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


[valgrind] [Bug 357734] New: "unhandled instruction 0x1AC12D8C" for ARM64/AARCH64

2016-01-09 Thread Jeffrey Walton via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357734

Bug ID: 357734
   Summary: "unhandled instruction 0x1AC12D8C" for ARM64/AARCH64
   Product: valgrind
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: noloa...@gmail.com

Please ignore this bug report. The issue below was fixed in Valgrind 3.11. It
will be experienced by Linaro users because the distro supplies Valgrind 3.10.
We are providing the report for others who experience the finding but receive 0
search results.

We are using a LeMaker HiKey for testing (http://www.amazon.com/dp/B019O3QTSA).
It runs Linaro/AARCH64. We experienced and illegal opcode:

disInstr(arm64): unhandled instruction 0x1AC12D8C
disInstr(arm64): 0001'1010 1100'0001 0010'1101 1000'1100

The offending line of code, rotlVariable, is a simple "rotate register" (as
opposed to a "rotate immediate").

*

It was experienced with 3.11:

$ /usr/bin/valgrind --version
valgrind-3.10.0

*

ARM64 front end: data_processing_register
disInstr(arm64): unhandled instruction 0x1AC12D8C
disInstr(arm64): 0001'1010 1100'0001 0010'1101 1000'1100
==8610== valgrind: Unrecognised instruction at address 0x542a90.
==8610==at 0x542A90: rotlVariable (misc.h:1224)
==8610==by 0x542A90: CryptoPP::CAST128::Enc::ProcessAndXorBlock(unsigned
char const*, unsigned char const*, unsigned char*) const (cast.cpp:43)
==8610==by 0x483E8B: ProcessBlock (cryptlib.h:726)
==8610==by 0x483E8B: BlockTransformationTest(CipherFactory const&,
CryptoPP::BufferedTransformation&, unsigned int) (validat1.cpp:1240)
==8610==by 0x4869EB: ValidateCAST() (validat1.cpp:2031)
==8610==by 0x48A4E3: ValidateAll(bool) (validat1.cpp:111)
==8610==by 0x47391F: Validate(int, bool, char const*) (test.cpp:870)
==8610==by 0x479B67: main (test.cpp:342)

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


[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-01-09 Thread Massimiliano Torromeo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354056

--- Comment #16 from Massimiliano Torromeo  ---
This also happens when connecting do an MDaemon IMAP server [1] (not my choice
of IMAP server but it is what is used at work)

[1] http://www.altn.com/Products/MDaemon-Email-Server-Windows/

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


[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

2016-01-09 Thread Jonathan Ringstad via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343803

--- Comment #41 from Jonathan Ringstad  ---
I had a look and found a bit of additional information:

- The hang occurs when the libc exit handler cleans up the shared libraries of
the program, so when the process starts to hang, no actual konsole code is
running anymore. So that seems to make it very unlikely that the fault is with
konsole
- the hang occurs inside _nv014tls in /usr/lib/libnvidia-tls.so.358.16 (nvidias
thread-local storage library used by GL, GLX et al), where the function falls
into an infinite loop. Injecting a debugger and forcing it to return, results
in konsole exiting normally.
- The libc exit handler calls /usr/lib/libGL.so.1's .fini section (I think)
which calls the problematic _nv014tls from the libnvidia-tls.so.
- libGL gets loaded because konsole (well, Qt, I think -- konsole does not
touch GLX directly) wants to do glX* calls such as glXChooseFBConfig,
glXGetFBConfigAttrib, glXGetVisualFromFBConfig. no GLX context is ever
initialized or destroyed from what I can tell, however (which is a bit strange,
but I think should be perfectly legal to do. All the functions that are called
do not require a GLX context to be present, from what I can tell.)
- Re-running the exact same sequence of GLX functions in a different process
does not lead to such a hang. Traceback: http://dpaste.com/0RWSDK7 I re-ran the
traceback a few thousand times without a hang. So there's probably at least one
more ingredient necessary to make the hang happen.

That's about as far as I got. As a workaround it might be possible to make Qt
not interact with GLX (if that's possible), since it's not used anyway. It
seems pretty likely to me at this point that the bug is in the nvidia client
driver, but I suppose there is still a chance the bug is in Qt. I think the bug
is definitely not in konsole.

I didn't manage to produce a minimal test-case, unfortunately. To get there, it
might be useful to check if konsole loads any other nvidia client drivers, and
if yes, how it interacts with them.

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


[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

2016-01-09 Thread Jonathan Ringstad via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343803

--- Comment #42 from Jonathan Ringstad  ---
I had a look and found a bit of additional information:

- The hang occurs when the libc exit handler cleans up the shared libraries of
the program, so when the process starts to hang, no actual konsole code is
running anymore. So that seems to make it very unlikely that the fault is with
konsole
- the hang occurs inside _nv014tls in /usr/lib/libnvidia-tls.so.358.16 (nvidias
thread-local storage library used by GL, GLX et al), where the function falls
into an infinite loop. Injecting a debugger and forcing it to return, results
in konsole exiting normally.
- The libc exit handler calls /usr/lib/libGL.so.1's .fini section (I think)
which calls the problematic _nv014tls from the libnvidia-tls.so.
- libGL gets loaded because konsole (well, Qt, I think -- konsole does not
touch GLX directly) wants to do glX* calls such as glXChooseFBConfig,
glXGetFBConfigAttrib, glXGetVisualFromFBConfig. no GLX context is ever
initialized or destroyed from what I can tell, however (which is a bit strange,
but I think should be perfectly legal to do. All the functions that are called
do not require a GLX context to be present, from what I can tell.)
- Re-running the exact same sequence of GLX functions in a different process
does not lead to such a hang. Traceback: http://dpaste.com/0RWSDK7 I re-ran the
traceback a few thousand times without a hang. So there's probably at least one
more ingredient necessary to make the hang happen.

That's about as far as I got. As a workaround it might be possible to make Qt
not interact with GLX (if that's possible), since it's not used anyway. It
seems pretty likely to me at this point that the bug is in the nvidia client
driver, but I suppose there is still a chance the bug is in Qt. I think the bug
is definitely not in konsole.

I didn't manage to produce a minimal test-case, unfortunately. To get there, it
might be useful to check if konsole loads any other nvidia client drivers, and
if yes, how it interacts with them.

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


[plasmashell] [Bug 357644] Plasma crashed affter delete new standart panel

2016-01-09 Thread David Edmundson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357644

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
I did fix a crash with removing panels for 5.5.3

Though the backtrace doesn't match yours exactly, so I'm not 100% convinced
it's the same. I checked out the code your trace points to, and everything is
in order; nothing there that could crash. 

I'm going to assume it's the same bug and your trace is corrupted (which
happens). 
Please reopen if you see this again with an up-to-date Plasma.

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


[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

2016-01-09 Thread Ben via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355195

--- Comment #3 from Ben  ---
(In reply to kolAflash from comment #2)
> Actually I'd prefer to see the timezone offset (e.g. +0800). Especially
> because I'm mailing with people in different timezones

> this seems to be the better way instead of recalculating everything to my 
> local timezone without
> any attached timezone information.

As i understand from reading the source in templateparser.cpp  this is actually
the desired behavior of the %OTIME and %OTIMELONG pattern. But somehow the
timezone information is passed either missing or passed incorrectly. I do not
see whether this is a problem with the KMime library, templateparser or
somewhere else in the kdepim infrastructure. Maybe it's Akonadi while providing
the message?

Someone with a working debug environment should look into it. I currently do
not have such a environment running.

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


[digikam] [Bug 354745] Thumbnails not shown in album view after startup

2016-01-09 Thread Milan Knížek via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354745

Milan Knížek  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WONTFIX

--- Comment #6 from Milan Knížek  ---
I eventually installed ver. 5 beta 2 rc and there the bug with "no images" does
not exhibit. Assuming that final release is not so far, I propose to close as
"won't fix".

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

[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #7 from Thomas Lübking  ---
PS: and HW acceleration in FF! ("about:config" iirc, filter for "accel")

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

[dolphin] [Bug 357731] New: Unable to copy files/folder from local fs to a remote sshfs mounted using afuse.

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357731

Bug ID: 357731
   Summary: Unable to copy files/folder from local fs to a remote
sshfs mounted using afuse.
   Product: dolphin
   Version: 15.12.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: xavier8...@yahoo.com

Unable to copy paste files/folder from local fs to a remote sshfs mounted using
afuse.
Using the following.

Afuse : https://github.com/pcarrier/afuse
Systemd unitfile : https://gist.github.com/xavier83/5a536805f9b65d62cdc9


Reproducible: Always

Steps to Reproduce:
1. mount afuse /usr/bin/afuse -f -o big_writes -o auto_unmount -o flushwrites
-o mount_template=sshfs -o ServerAliveInterval=10 -o reconnect %r:/ %m -o
unmount_template=fusermount -u -z %m /home/user/.mnt/ssh
2. Navigate to /home/user/.mnt/ssh/ using dolphin (automounts)
3. Navigate to  on another tab.
4. copy a file/folder from local fs tab and try to paste it on afuse tab.

Actual Results:  
files/folder not getting copied

Expected Results:  
files/folder to be copied

tested using cp and it copies the files. not working only on dolphin. strangely
creating new directory or file using context menu works.

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


[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

2016-01-09 Thread Johannes Pfrang via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357388

--- Comment #10 from Johannes Pfrang  ---
This could be a regression of bug 356343.

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


[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme

2016-01-09 Thread Mircea Kitsune via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356006

--- Comment #1 from Mircea Kitsune  ---
With news that Firefox and Thunderbird will soon be switching from gtk2 to
gtk3, I'd really like to see this being given some thought! As far as I'm
aware, it's primarily the background color and text color that need to be
respected in these themes.

oxygen-gtk (gtk2 only) offers a perfect example of how this is done. The Oxygen
widget style, just like the Breeze widget style, is meant to follow the
background and text colors of the color scheme.

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


[KScreen] [Bug 357736] New: Plasmoids places are not disturbed when using a external screen with a different resolution via Hdmi)

2016-01-09 Thread Benjamin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357736

Bug ID: 357736
   Summary: Plasmoids places are not disturbed when using a
external screen with a different resolution via Hdmi)
   Product: KScreen
   Version: 5.4.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: dvra...@kde.org
  Reporter: benjami...@gmx.at

When plug in my beamer which is offering a different resolution and use it, all
the plasma applets which i am using in my desktop are mixed up and resized
after i connect my old screen which has a higher resolution. It seems, that the
config is not applied to different resolutions.

Reproducible: Always

Steps to Reproduce:
1. Plug in beamer
2. Select beamer and switch off laptop screen
3. switch back to old setting

Actual Results:  
Mixed up desktop (applets).

Expected Results:  
Shwoing the plasmoids and applets in its former place.

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


[digikam] [Bug 357738] New: Item // Edit Geolocation window does not remember its size

2016-01-09 Thread Milan Knížek via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357738

Bug ID: 357738
   Summary: Item // Edit Geolocation window does not remember its
size
   Product: digikam
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation-Editor
  Assignee: digikam-de...@kde.org
  Reporter: kni...@volny.cz

Choosing menu Item // Edit Geolocation opens a new window in the middle of the
screen. The window does not have "minimise", "maximise" buttons in the window
frame, although manual resizing is possible.

After closing the window and opening it again, the window is sized and located
the same as before.

Proposal: add basic "mix", "max" buttons to the top bar of window frame and set
the frame to remember its last position.

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


[okular] [Bug 357741] New: After saving a PDF with a completed form, opening the original PDF also shows the completed form

2016-01-09 Thread Harald Brennich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357741

Bug ID: 357741
   Summary: After saving a PDF with a completed form, opening the
original PDF also shows the completed form
   Product: okular
   Version: 0.21.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: harald.brenn...@gmx.de

After entering data into a form and saving the file (with a new name), when
opening the original file the modified form is shown.

Reproducible: Always

Steps to Reproduce:
1. Download a PDF containing a form, for instance
"http://www.finanzamt.bayern.de/Informationen/Formulare/Weitere_Themen_A_bis_Z/Erbschaft-_und_Schenkungsteuer/Ab_2009/Erbschaftsteuererklarung-SEPA.pdf;
2. Open the PDF and enter some data into the form
3. Save the file with another name
4. Open the original file


Actual Results:  
 The modified form is shown

Expected Results:  
The original form should be shown

There is a workaround: Remove the the references to the original file from
.kde4/share/apps/okular/docdata/

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


[telepathy] [Bug 355415] Cannot connect to Google Hangouts

2016-01-09 Thread Tom Kijas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355415

Tom Kijas  changed:

   What|Removed |Added

 CC||t.ki...@gmail.com

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


[dolphin] [Bug 352100] Dolphin 15.08: drag to WINE apps not working

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352100

--- Comment #9 from Soukyuu  ---
Seem to have kind of missed the last reply, reported the bug now, see
https://bugreports.qt.io/browse/QTBUG-50372

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


[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Bernd Steinhauser via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #5 from Bernd Steinhauser  ---
Created attachment 96538
  --> https://bugs.kde.org/attachment.cgi?id=96538=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation with compositing
enabled

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


[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

2016-01-09 Thread Thomas Eschenbacher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=323431

--- Comment #5 from Thomas Eschenbacher  ---
I am affected by the same here:

> uname -a
Linux lisa 4.3.3-gentoo #1 SMP PREEMPT Fri Jan 8 07:01:39 CET 2016 x86_64 AMD
A10-7870K Radeon R7, 12 Compute Cores 4C+8G AuthenticAMD GNU/Linux

> cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 21
model   : 56
model name  : AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G
stepping: 1
cpu MHz : 1700.000
cache size  : 2048 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 16
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf
eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave
avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse
3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext
perfctr_core perfctr_nb bpext arat cpb hw_pstate proc_feedback npt lbrv
svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter
pfthreshold vmmcall fsgsbase bmi1 xsaveopt
bugs: fxsave_leak sysret_ss_attrs

Any news about this bug?

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


[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra, .ora, .psd files

2016-01-09 Thread Raghavendra kamath via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356227

--- Comment #8 from Raghavendra kamath  ---
the psd thumbnailing issue has a fix and it is in review, hopefully it gets
approved and shipped with next version , here is the review
https://git.reviewboard.kde.org/r/126684/

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


[valgrind] [Bug 323431] Unhandled AMD XOP instruction vpcmov VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

2016-01-09 Thread Mark Wielaard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=323431

Mark Wielaard  changed:

   What|Removed |Added

Summary|VEX: unhandled instruction  |Unhandled AMD XOP
   |bytevex amd64->IR:  0x8F|instruction vpcmov VEX:
   |0xE8 0x78 0xA2 0xC1 0x40|unhandled instruction
   |0xC5 0xFB   |bytevex amd64->IR:  0x8F
   ||0xE8 0x78 0xA2 0xC1 0x40
   ||0xC5 0xFB

--- Comment #7 from Mark Wielaard  ---
This is a AMD specific XOP instruction VPCMOV described in
http://support.amd.com/TechDocs/43479.pdf

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


[frameworks-kimageformats] [Bug 354413] psd thumbnails are not loading in dolphin

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354413

Soukyuu  changed:

   What|Removed |Added

 CC||chrno-sphe...@hotmail.com

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


[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

2016-01-09 Thread Frank Roscher via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343383

Frank Roscher  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/khot
   ||keys/57a0c4ecf98f973f2b7a7e
   ||eeb4e55213cbd22ec4
 Resolution|--- |FIXED

--- Comment #14 from Frank Roscher  ---
Git commit 57a0c4ecf98f973f2b7a7eeeb4e55213cbd22ec4 by Frank Roscher.
Committed on 09/01/2016 at 11:35.
Pushed by froscher into branch 'master'.

Port mouse gestures to QAbstractNativeEventFilter and reenable them
FEATURE:

M  +1-2kcm_hotkeys/hotkeys_context_menu.cpp
M  +37   -25   libkhotkeysprivate/triggers/gestures.cpp
M  +6-19   libkhotkeysprivate/triggers/gestures.h

http://commits.kde.org/khotkeys/57a0c4ecf98f973f2b7a7eeeb4e55213cbd22ec4

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


[kio] [Bug 350596] crypt_set_algorithms2 doesn't handle Ciphers as a list and fails connection prematurely

2016-01-09 Thread Robert G . Siebeck via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350596

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

--- Comment #3 from Robert G. Siebeck  ---
I had the same problem but could resolve it by updating libssh to version 0.7.1
(from 0.6.5).

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


[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-01-09 Thread Massimiliano Torromeo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354056

Massimiliano Torromeo  changed:

   What|Removed |Added

 CC||massimiliano.torromeo@gmail
   ||.com

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


[kwin] [Bug 342500] Rarely applications stop getting redrawn

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342500

--- Comment #23 from k...@karolherbst.de ---
I am always on dri3

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


[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

2016-01-09 Thread Luc Lalonde via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357388

Luc Lalonde  changed:

   What|Removed |Added

 CC||luc.lalo...@polymtl.ca

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


[kwin] [Bug 342500] Rarely applications stop getting redrawn

2016-01-09 Thread Lasse Liehu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342500

Lasse Liehu  changed:

   What|Removed |Added

 CC|lasse.li...@gmail.com   |

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


[Breeze] [Bug 356380] Regression on breeze dark theme in 5.17.0

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356380

hotmusic...@mail.bg changed:

   What|Removed |Added

 CC||hotmusic...@mail.bg

--- Comment #9 from hotmusic...@mail.bg ---
*** Bug 357661 has been marked as a duplicate of this bug. ***

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


[Breeze] [Bug 357661] Invisible monochrome icon in 'system tray'

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357661

hotmusic...@mail.bg changed:

   What|Removed |Added

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

--- Comment #3 from hotmusic...@mail.bg ---


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

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


[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Bernd Steinhauser via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #4 from Bernd Steinhauser  ---
(In reply to Thomas Lübking from comment #3)
> *cough*
> 
> > Compositing
> > ===
> > Compositing is not active
Hm, that's interesting, I didn't notice that. It seems like I can't enable
compositing with egl anymore.
This definitely worked before, but I can't tell when it stopped working.
However, yesterday when the problem occurred, I was using the glx interface. I
just switched to give egl another try, but didn't notice that the compositor
was inactive then.

> 
> > I think (but I'm not sure here), I've even tried with the compositor 
> > switched off.
> Wow.
Like I said, I'm not sure here, but will try again when I don't fear data loss.

> > I've seen this issue since the update from 5.4.x to 5.5.0.
> https://git.reviewboard.kde.org/r/126266/
> (A rather wild guess given the apparent GPU state - the grab should not be
> required and would not impact visual updates)
I can give it a try, although the application I see it the most with is gtk
(firefox).

> > This seems to be a complete lockup of the gpu
> dmesg tail (if you can, probably via ssh?)
I normally have ssh deactivated, but will activate and see if I can get
anything out of it.
I highly doubt that, though. journal seemed to work, kernel logging seemed to
work (it did log the sysrq sync message), I synced the file system, so any
message that would have been in dmesg should have ended up in the journal as
well.

Could use that to debug some program when the issue happens, but for that I
would require upfront information about what to do.

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

[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356006

mrl...@gmail.com changed:

   What|Removed |Added

 CC||mrl...@gmail.com

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


[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #10 from Thomas Lübking  ---
> layers.acceleration.disabled false
layers.acceleration.disabled true

Isn't double negation a pleasure for everyone? ;-)

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

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

2016-01-09 Thread Wolfgang Bauer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345234

--- Comment #15 from Wolfgang Bauer  ---
(In reply to Ongun Kanat from comment #14)
> Did you tried instaling fonts with the System
> option after the commit went upstream

Yes. The "Personal" option does not need root privileges and never had this
problem (as I mentioned myself in comment#5).

Maybe it's a more general problem with kauth in your case.

Do other actions work that require root privileges, like e.g. changing the
system time/date?

Do you get a root password dialog at all? If not, check that it's not hidden
behind another window e.g. (even kfontinstall's progress dialog)
As long as you don't enter the root password, kfontinstall obviously will not
continue (although it actually times out after a while here).

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


[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra, .ora, .psd files

2016-01-09 Thread Wolfgang Bauer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356227

--- Comment #10 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #9)
> .psd thumbnails are actually handled by the general image thumbnailer, part
> of kio-core.
Oops, sorry.
The general image thumbnailer is of course part of kio-extras, as mentioned by
rog131.

But it works fine AFAICT, and doesn't need to be fixed.

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


[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

2016-01-09 Thread Johannes Pfrang via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357388

Johannes Pfrang  changed:

   What|Removed |Added

 CC||hugo.pere...@free.fr

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


[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT

2016-01-09 Thread Johannes Pfrang via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356992

Johannes Pfrang  changed:

   What|Removed |Added

 CC||johannespfrang+...@gmail.co
   ||m

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


[Breeze] [Bug 344425] Cannot select fields using the mouse

2016-01-09 Thread Hugo Pereira Da Costa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=344425

--- Comment #21 from Hugo Pereira Da Costa  ---
(In reply to André Marcelo Alvarenga from comment #20)
> Please, reopen this bug report.
> I can reproduce this bug in Plasma 5.5.3 (Qt 5.5.1 and Frameworks 5.17).
> 
> Distro: Manjaro Linux 15.12

Yeah. The fix will appear in Plasma 5.6. No need to reopen

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

[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356938

--- Comment #43 from Thomas Lübking  ---
(In reply to AnAkkk from comment #42)

> Is there any thing new on merging this? :)


not been approved yet - i guess martin's still catching up x-mas vacancies.

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

[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread chepioq via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #44 from chepioq  ---
(In reply to Thomas Lübking from comment #43)
> Resp. this one (the ARGB32 translucency handling is uncritical, it's applied
> to the preconverted image. This should be the single point of failure)
> 
> diff --git a/kcms/kfontinst/lib/FcEngine.cpp
> b/kcms/kfontinst/lib/FcEngine.cpp
> index 19b7206..012a9d5 100644
> --- a/kcms/kfontinst/lib/FcEngine.cpp
> +++ b/kcms/kfontinst/lib/FcEngine.cpp
> @@ -537,7 +537,14 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
>  if (!xImage) {
>  return QImage();
>  }
> -return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, QImage::Format_ARGB32_Premultiplied, , xImage);
> +QImage::Format format = QImage::Format_RGB32;
> +switch (DefaultDepth(QX11Info::display(), 0)) {
> +case 32: format = QImage::Format_ARGB32_Premultiplied; break;
> +case 16: format = QImage::Format_RGB16; break;
> +case 8: format = QImage::Format_Grayscale8; break;
> +default: break;
> +}
> +return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, format, , xImage);
>  }
>  
>  inline int point2Pixel(int point)

I use Fedora 23 and I have same problem (see comment 9)

I rebuild the fedora's rpm with your patch
(plasma-desktop-5.5.3-2.fc23.x86_64.rpm), and now all work fine, I can see the
font in system settings.
Thank for that.

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

[systemsettings] [Bug 357735] New: KDE system control crashed , not everytime, somitimes. after setting changed.

2016-01-09 Thread gennmaiko via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357735

Bug ID: 357735
   Summary: KDE system control crashed , not everytime, somitimes.
after setting changed.
   Product: systemsettings
   Version: 5.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gennma...@gmail.com

Application: systemsettings5 (5.4.3)

Qt Version: 5.4.2
Operating System: Linux 4.2.6-localo x86_64
Distribution: Ubuntu 15.10

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

using KDE system control . 
after some settings done(random settings in KDE system control and randomly
crashes occured), crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE システム設定 (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f25e4d02800 (LWP 20639))]

Thread 4 (Thread 0x7f25d3799700 (LWP 20640)):
#0  0x7f25e14b18dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f25df1c1bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f25df1c374f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f25d5ce7a39 in QXcbEventReader::run (this=0x191dea0) at
qxcbconnection.cpp:1105
#4  0x7f25e1ba42be in QThreadPrivate::start (arg=0x191dea0) at
thread/qthread_unix.cpp:337
#5  0x7f25de94c6aa in start_thread (arg=0x7f25d3799700) at
pthread_create.c:333
#6  0x7f25e14bceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f25c6fe3700 (LWP 20641)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f25c7162114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f25c7162159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f25de94c6aa in start_thread (arg=0x7f25c6fe3700) at
pthread_create.c:333
#4  0x7f25e14bceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2542844700 (LWP 20642)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2545c6bfca in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f2545c6b707 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f25de94c6aa in start_thread (arg=0x7f2542844700) at
pthread_create.c:333
#4  0x7f25e14bceed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f25e4d02800 (LWP 20639)):
[KCrash Handler]
#6  0x7f25e0453637 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f25e03ff383 in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f25e052c1b1 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f25e052c3c9 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f25e0393e61 in QJSEngine::~QJSEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f25e0493365 in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f25e0493429 in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f25370a8152 in QScopedPointerDeleter::cleanup
(pointer=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:54
#14 QScopedPointer::reset
(other=0x0, this=0x7f2537332728 ) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:149
#15 Aurorae::Helper::unref (this=0x7f2537332720
) at
../../../../clients/aurorae/src/aurorae.cpp:112
#16 0x7f25370ac0b8 in Aurorae::Helper::unref (this=) at
../../../../clients/aurorae/src/aurorae.cpp:274
#17 Aurorae::Decoration::~Decoration (this=0x5773300, __in_chrg=) at ../../../../clients/aurorae/src/aurorae.cpp:269
#18 0x7f25370ac0d9 in Aurorae::Decoration::~Decoration (this=0x5773300,
__in_chrg=) at ../../../../clients/aurorae/src/aurorae.cpp:280
#19 0x7f25e1db5670 in QObject::event (this=0x5773300, e=) at
kernel/qobject.cpp:1236
#20 0x7f25e3207b8c in QApplicationPrivate::notify_helper
(this=this@entry=0x18fd800, receiver=receiver@entry=0x5773300,
e=e@entry=0x4fe9dd0) at kernel/qapplication.cpp:3720
#21 0x7f25e320d230 in QApplication::notify (this=0x7ffc9c001080,
receiver=0x5773300, e=0x4fe9dd0) at kernel/qapplication.cpp:3503
#22 0x7f25e1d83f1b in QCoreApplication::notifyInternal
(this=0x7ffc9c001080, receiver=0x5773300, event=event@entry=0x4fe9dd0) at
kernel/qcoreapplication.cpp:935
#23 0x7f25e1d86057 in QCoreApplication::sendEvent (event=0x4fe9dd0,
receiver=) at

[dolphin] [Bug 352097] Dolphin Version 15.08.0 trash strange behavior after deleting files.

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352097

--- Comment #12 from andreas.sturmlech...@gmail.com ---
See this commit:
https://quickgit.kde.org/?p=kio.git=commit=1d9681ee4fc35dd616f75e78ea8b47a7532d638e

(part of kio-5.18.0)

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


[kwin] [Bug 301447] Desktop grid effect changes activities

2016-01-09 Thread Sebastian Kuźlak via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=301447

--- Comment #8 from Sebastian Kuźlak  ---
this is still present in 5.5

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

[kaddressbook] [Bug 357370] German Umlaute are displayed wrong in different views

2016-01-09 Thread Allen Winter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357370

Allen Winter  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 CC||win...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Allen Winter  ---
resolving then

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


[muon] [Bug 357704] Muon notifier crashes on apt package list updates

2016-01-09 Thread David Edmundson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357704

David Edmundson  changed:

   What|Removed |Added

 CC||aleix...@kde.org,
   ||sit...@kde.org
   Target Milestone|1.0 |---
Product|plasmashell |muon
  Component|general |notifier
   Assignee|k...@davidedmundson.co.uk|echidna...@kubuntu.org

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


[krita] [Bug 357740] New: The pen never shows up on the canvas and is very slow

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357740

Bug ID: 357740
   Summary: The pen never shows up on the canvas and is very slow
   Product: krita
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: gothiggala...@gmail.com

I've reinstalled twice and it still won't work

Reproducible: Always

Steps to Reproduce:
1.Open krita
2.Try to draw
3.

Actual Results:  
My pen doesn't show up

Expected Results:  
My pen shows up like normal

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


[krita] [Bug 357739] New: The pen never shows up on the canvas and is very slow

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357739

Bug ID: 357739
   Summary: The pen never shows up on the canvas and is very slow
   Product: krita
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: gothiggala...@gmail.com

I've reinstalled twice and it still won't work

Reproducible: Always

Steps to Reproduce:
1.Open krita
2.Try to draw
3.

Actual Results:  
My pen doesn't show up

Expected Results:  
My pen shows up like normal

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


[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #6 from Thomas Lübking  ---
Even gtk+ windows should just kick the NETWM moveresize in the WM

> kwin4_effect_translucency
Try to disable this.

> electricBorderMaximize: true
> electricBorderTiling: true
and this

Do you have autohiding panels on one of the edges?

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

[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra, .ora, .psd files

2016-01-09 Thread Wolfgang Bauer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356227

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #9 from Wolfgang Bauer  ---
(In reply to Soukyuu from comment #7)
> For me, neither thumbnails nor opening with gwenview works with .psd files.

Yes, it's a general problem with kimageformats' PSD loader.
See Bug#354413.

As mentioned in comment#8, I uploaded a fix for review today.

> Is the mentioned fix for psd images already in 15.12? Am on arch linux x64
No.
All 3 thumbnailers are not part of KDE Applications at the moment.

The .kra and .ora thumbnailers might get moved there as indicated in comment#6,
but they aren't yet and this definitely won't happen in a bugfix release I
suppose, so 16.04.0 at the earliest.

.psd thumbnails are actually handled by the general image thumbnailer, part of
kio-core. It uses the Qt5 image plugins from kimageformats (a Framework) for
generating the thumbnails.
But again, AFAICT the thumbnailer works fine, it's the loading of .psd files
that's generally broken in KF5 at the moment. With my patch, it works fine
here.

If you mean https://git.reviewboard.kde.org/r/125790/, this is included in
kimageformats since Frameworks 5.16.0.

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


[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra and .ora files

2016-01-09 Thread Wolfgang Bauer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356227

Wolfgang Bauer  changed:

   What|Removed |Added

Summary|Dolphin in plasma 5 doesn't |Dolphin in plasma 5 doesn't
   |have thumbnails for .kra,   |have thumbnails for .kra
   |.ora, .psd files|and .ora files

--- Comment #11 from Wolfgang Bauer  ---
PS: I think we should reduce this bug report to .kra and .ora files, for which
a thumbnailer is only available in Krita at the moment, which hasn't been
released as KF5 version yet.

The problem with .psd files is handled in Bug#354413 anyway.

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


[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340982

ricar...@um.es changed:

   What|Removed |Added

 CC||ricar...@um.es

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


[konsole] [Bug 357737] New: Konsole ha crashato in chiusura

2016-01-09 Thread shishii via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357737

Bug ID: 357737
   Summary: Konsole ha crashato in chiusura
   Product: konsole
   Version: 15.08.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: shis...@tiscalinet.it

Application: konsole (15.08.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
Konsole ha prodotto un crash in chiusura dell'applicazione cliccando sulla X
della finestra.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a19f66940 (LWP 2524))]

Thread 2 (Thread 0x7f79f98c6700 (LWP 2525)):
[KCrash Handler]
#5  0x7f7a11fcaa98 in raise () at /lib64/libc.so.6
#6  0x7f7a11fcc69a in abort () at /lib64/libc.so.6
#7  0x7f7a1200ddaa in  () at /lib64/libc.so.6
#8  0x7f7a12014e23 in malloc_consolidate () at /lib64/libc.so.6
#9  0x7f7a120179a6 in _int_malloc () at /lib64/libc.so.6
#10 0x7f7a1201a4aa in calloc () at /lib64/libc.so.6
#11 0x7f7a0975a3e3 in  () at /usr/lib64/nvidia/tls/libnvidia-tls.so.358.16
#12 0x7f7a0d7a9531 in g_malloc0 () at /lib64/libglib-2.0.so.0
#13 0x7f7a0d7c0fcd in g_slice_free1 () at /lib64/libglib-2.0.so.0
#14 0x7f7a100123b9 in __nptl_deallocate_tsd.part.4 () at
/lib64/libpthread.so.0
#15 0x7f7a100137a9 in start_thread () at /lib64/libpthread.so.0
#16 0x7f7a12098a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7a19f66940 (LWP 2524)):
#0  0x7f7a120a64ec in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7f7a12016445 in _int_free () at /lib64/libc.so.6
#2  0x7f7a12019cac in free () at /lib64/libc.so.6
#3  0x7f79fc8a77b0 in QXcbEventReader::~QXcbEventReader() () at
/lib64/libQt5XcbQpa.so.5
#4  0x7f79fc87b62b in QXcbConnection::~QXcbConnection() () at
/lib64/libQt5XcbQpa.so.5
#5  0x7f79fc87bb69 in QXcbConnection::~QXcbConnection() () at
/lib64/libQt5XcbQpa.so.5
#6  0x7f79fc87d566 in QXcbIntegration::~QXcbIntegration() () at
/lib64/libQt5XcbQpa.so.5
#7  0x7f79fc87d679 in QXcbIntegration::~QXcbIntegration() () at
/lib64/libQt5XcbQpa.so.5
#8  0x7f7a133a9623 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /lib64/libQt5Gui.so.5
#9  0x7f7a13b56449 in QApplicationPrivate::~QApplicationPrivate() () at
/lib64/libQt5Widgets.so.5
#10 0x7f7a12ead0b8 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#11 0x7f7a13b58239 in QApplication::~QApplication() () at
/lib64/libQt5Widgets.so.5
#12 0x7f7a19c42990 in kdemain () at /lib64/libkdeinit5_konsole.so
#13 0x7f7a11fb6580 in __libc_start_main () at /lib64/libc.so.6
#14 0x563e1661aba9 in _start ()

Reported using DrKonqi

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


[plasmashell] [Bug 357730] New: Plasma crashed after Firefox and Remmina update

2016-01-09 Thread Lahoda Yaroslav via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357730

Bug ID: 357730
   Summary: Plasma crashed after Firefox and Remmina update
   Product: plasmashell
   Version: 5.4.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lagod...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)
 (Compiled from sources)
Qt Version: 5.4.2
Operating System: Linux 4.2.0-23-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
After successful update of Remmina and Mozulla Firefox I was restarted my
computer. When I was login to the system saw message that Plasma crash

-- Backtrace:
Application: Плазма (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faba2812800 (LWP 1041))]

Thread 8 (Thread 0x7fab8dcfa700 (LWP 1043)):
#0  0x7fab9cfbf8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7faba1006bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7faba100874f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fab90044a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7fab9d6b22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fab9c7a16aa in start_thread (arg=0x7fab8dcfa700) at
pthread_create.c:333
#6  0x7fab9cfcaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fab873ea700 (LWP 1070)):
#0  0x7fab99d69241 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fab99d6bb4a in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fab99d6c190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fab99d6c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fab9d8e929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fab9d88f75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fab9d6ad3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fab9fed5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fab9d6b22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fab9c7a16aa in start_thread (arg=0x7fab873ea700) at
pthread_create.c:333
#10 0x7fab9cfcaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fab7bf85700 (LWP 1071)):
#0  0x7fab99db0869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fab99d6b9a1 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fab99d6c167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fab99d6c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fab9d8e929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fab9d88f75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fab9d6ad3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fab9fed5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fab9d6b22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fab9c7a16aa in start_thread (arg=0x7fab7bf85700) at
pthread_create.c:333
#10 0x7fab9cfcaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fab796a7700 (LWP 1077)):
#0  0x7fab99db0869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fab99d6b180 in g_main_context_acquire () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fab99d6c0a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fab99d6c2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fab9d8e929b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fab9d88f75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fab9d6ad3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fab9fed5f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fab9d6b22be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fab9c7a16aa in start_thread (arg=0x7fab796a7700) at
pthread_create.c:333
#10 0x7fab9cfcaeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fab6bbd8700 (LWP 1085)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[kwin] [Bug 357728] Dragging window leads to display freeze

2016-01-09 Thread Bernd Steinhauser via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357728

--- Comment #9 from Bernd Steinhauser  ---
(In reply to Thomas Lübking from comment #7)
> PS: and HW acceleration in FF! ("about:config" iirc, filter for "accel")

apz.fling_accel_base_mult 1.0
apz.fling_accel_interval_ms 500
apz.fling_accel_supplemental_mult 1.0
layers.acceleration.disabled false
layers.acceleration.draw-fps false
layers.acceleration.force-enabled false

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

[kio] [Bug 356227] Dolphin in plasma 5 doesn't have thumbnails for .kra, .ora, .psd files

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356227

Soukyuu  changed:

   What|Removed |Added

 CC||chrno-sphe...@hotmail.com

--- Comment #7 from Soukyuu  ---
For me, neither thumbnails nor opening with gwenview works with .psd files. Is
the mentioned fix for psd images already in 15.12? Am on arch linux x64

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


[korganizer] [Bug 357732] New: Korganizer5

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357732

Bug ID: 357732
   Summary: Korganizer5
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: alain.quincerot_...@m4am.net

Application: korganizer ()

Qt Version: 5.5.1
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:
   start korganizer

- Custom settings of the application:
Yast migrated korganizer to korganizer5
version is 15.08.3-3.2-x86-64 from openSUSE-Leap-42.1-Update


log_kidentitymanagement: Store: "Signature Enabled" : QVariant(QString,
"false")
""
connectToServer "/tmp/akonadi-alain_.vGZScQ/akonadiserver.socket"
""
connectToServer "/tmp/akonadi-alain_.vGZScQ/akonadiserver.socket"
""
connectToServer "/tmp/akonadi-alain_.vGZScQ/akonadiserver.socket"
KServiceTypeTrader: serviceType "KOrganizer/Part" not found
log_korganizer: ""
done
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
log_korganizer: 
Socket error occurred: "QLocalSocket: Socket operation timed out"
terminate called after throwing an instance of 'Akonadi::ProtocolException'
  what():  Timeout while waiting for data
KCrash: Application 'korganizer' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1001/kdeinit5__0

The crash can be reproduced every time.

-- Backtrace:
Application: korganizer (korganizer), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd69c943800 (LWP 27813))]

Thread 2 (Thread 0x7fd677352700 (LWP 27814)):
#0  0x7fd698250c1d in poll () from /lib64/libc.so.6
#1  0x7fd68ca67422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fd68ca6900f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fd67907d3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fd698b5f32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7fd68eb290a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fd69825904d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fd69c943800 (LWP 27813)):
[KCrash Handler]
#6  0x7fd6981a9187 in raise () from /lib64/libc.so.6
#7  0x7fd6981aa538 in abort () from /lib64/libc.so.6
#8  0x7fd6987c8b8d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib64/libstdc++.so.6
#9  0x7fd6987c6bf6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x7fd6987c6c41 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x7fd6987c6e58 in __cxa_throw () from /usr/lib64/libstdc++.so.6
#12 0x7fd68a2397e1 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
#13 0x7fd68a24fa98 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
#14 0x7fd68a2643b4 in ?? () from /usr/lib64/libKF5AkonadiPrivate.so.5
#15 0x7fd68a2447c5 in Akonadi::Protocol::deserialize(QIODevice*) () from
/usr/lib64/libKF5AkonadiPrivate.so.5
#16 0x7fd69491e00b in Akonadi::SessionPrivate::dataReceived() () from
/usr/lib64/libKF5AkonadiCore.so.5
#17 0x7fd698d6acc6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#18 0x7fd698d6acc6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#19 0x7fd691d0a078 in ?? () from /usr/lib64/libQt5Network.so.5
#20 0x7fd691d16a11 in ?? () from /usr/lib64/libQt5Network.so.5
#21 0x7fd699edae7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#22 0x7fd699edfcc8 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#23 0x7fd698d3ae95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#24 0x7fd698d92ca5 in ?? () from /usr/lib64/libQt5Core.so.5
#25 0x7fd68e60cc84 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#26 0x7fd68e60ced8 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x7fd68e60cf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#28 0x7fd698d91d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#29 0x7fd698d38d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#30 0x7fd698d408f6 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#31 0x0040a6ef in main ()

Possible duplicates by query: bug 357364, bug 355966, bug 355473, bug 355239,
bug 355218.

Reported using DrKonqi

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


[kmymoney4] [Bug 357724] qif import defaults to UTF-8, need an option to choose other charsets

2016-01-09 Thread allan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357724

allan  changed:

   What|Removed |Added

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

--- Comment #1 from allan  ---
Are you having to download first, then save in ISO-8859-1 before import?

Might your bank have a CSV format option, sometimes called excel or
spreadsheet, as the CSV importer does allow you to select a character set?

Otherwise, I'm afraid there might be a wait for a fix, and for your distro to
pick it up.

Separately, 4.6.6 is pretty old-hat now and it might be worth looking for
4.7.2.  It won't help with your current problem, unfortunately, but numerous
bugs have been fixed.

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


[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #43 from Thomas Lübking  ---
Resp. this one (the ARGB32 translucency handling is uncritical, it's applied to
the preconverted image. This should be the single point of failure)

diff --git a/kcms/kfontinst/lib/FcEngine.cpp b/kcms/kfontinst/lib/FcEngine.cpp
index 19b7206..012a9d5 100644
--- a/kcms/kfontinst/lib/FcEngine.cpp
+++ b/kcms/kfontinst/lib/FcEngine.cpp
@@ -537,7 +537,14 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
 if (!xImage) {
 return QImage();
 }
-return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_ARGB32_Premultiplied, , xImage);
+QImage::Format format = QImage::Format_RGB32;
+switch (DefaultDepth(QX11Info::display(), 0)) {
+case 32: format = QImage::Format_ARGB32_Premultiplied; break;
+case 16: format = QImage::Format_RGB16; break;
+case 8: format = QImage::Format_Grayscale8; break;
+default: break;
+}
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
format, , xImage);
 }

 inline int point2Pixel(int point)

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

[dolphin] [Bug 357733] New: [plasma5] dolphin crash --- mark any file /right mouse click / hover the mouse cursor over 'activities' ---> crash!

2016-01-09 Thread Simon Andric via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357733

Bug ID: 357733
   Summary: [plasma5] dolphin crash --- mark any file /right mouse
click / hover the mouse cursor over 'activities' --->
crash!
   Product: dolphin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: simonandr...@gmail.com

Application: dolphin (15.11.80)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-0-generic x86_64
Distribution: Ubuntu Xenial Xerus (development branch)

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


Hello!

i have one activity (named "default" renamed "fani"). When in dolphin i right
click on any file and by accidetn my mouse cursor goes over the "activities"
the dolphin momentarily freezes as if it was searching for something, which it
cannot find and then dolphin closes and dr. konqi appears... happens every time
:)
i use the neewest packages... 

thank you!

nice day!

Simon :)

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fa6730968c0 (LWP 2616))]

Thread 5 (Thread 0x7fa6706ef700 (LWP 2621)):
#0  0x7fa685edc83d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa67a63bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa67a63d8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa672a3c4a9 in QXcbEventReader::run (this=0x143bb70) at
qxcbconnection.cpp:1229
#4  0x7fa680aa887e in QThreadPrivate::start (arg=0x143bb70) at
thread/qthread_unix.cpp:331
#5  0x7fa67d25766a in start_thread (arg=0x7fa6706ef700) at
pthread_create.c:333
#6  0x7fa685ee7e4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa66ccf0700 (LWP 2624)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa66e1c216a in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fa66e1c18a7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fa67d25766a in start_thread (arg=0x7fa66ccf0700) at
pthread_create.c:333
#4  0x7fa685ee7e4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa6631af700 (LWP 2627)):
#0  0x7fa67c70fa09 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa67c6ca8a9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa67c6cb23b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa67c6cb41c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa680ce02eb in QEventDispatcherGlib::processEvents
(this=0x7fa65c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fa680c872fa in QEventLoop::exec (this=this@entry=0x7fa6631aed00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fa680aa38d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fa680aa887e in QThreadPrivate::start (arg=0x1924bf0) at
thread/qthread_unix.cpp:331
#8  0x7fa67d25766a in start_thread (arg=0x7fa6631af700) at
pthread_create.c:333
#9  0x7fa685ee7e4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa660b1f700 (LWP 2797)):
[KCrash Handler]
#6  QBasicAtomicOps<8>::testAndSetRelaxed (currentValue=, newValue=0x1, expectedValue=0x0, _q_value=@0x81: ) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#7  QGenericAtomicOps >::testAndSetAcquire (currentValue=, newValue=,
expectedValue=0x0, _q_value=@0x81: ) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:166
#8  QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=this@entry=0x81) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:276
#9  QBasicMutex::fastTryLock (current=,
this=this@entry=0x81) at thread/qmutex.h:82
#10 QMutex::lock (this=this@entry=0x81) at thread/qmutex.cpp:212
#11 0x7fa680aa79db in QMutexLocker::QMutexLocker (m=0x81, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:128
#12 QThreadPrivate::finish (arg=arg@entry=0x1e6a3c0) at
thread/qthread_unix.cpp:343
#13 0x7fa680aa889f in __pthread_cleanup_class::~__pthread_cleanup_class
(this=, __in_chrg=) at
/usr/include/pthread.h:563
#14 QThreadPrivate::start (arg=0x1e6a3c0) at thread/qthread_unix.cpp:290
#15 0x7fa67d25766a in start_thread (arg=0x7fa660b1f700) at
pthread_create.c:333
#16 

[konsole] [Bug 357721] Fonts with different widths reset to normal width after re-launch.

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357721

--- Comment #1 from s...@hjkos.com ---
If you run Konsole from Konsole following can be seen in stdout:

`The font for use in the terminal has not been matched exactly. Perhaps it has
not been found properly.`

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


[KScreen] [Bug 357736] Plasmoids places are not disturbed when using a external screen with a different resolution via Hdmi)

2016-01-09 Thread Benjamin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357736

--- Comment #1 from Benjamin  ---
Sorry forgot to mention some specs:
opensuse 42.1. x64
Kernel version: 4.3.0-2-default

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


[kinfocenter] [Bug 348677] Crash on close

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348677

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

   What|Removed |Added

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

--- Comment #4 from opensuse.lietuviu.ka...@gmail.com ---
Still crash on exit in KDE Plasma 5.5.3 with Qt 5.5.1:
https://bugs.kde.org/show_bug.cgi?id=357718#c1

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


[kinfocenter] [Bug 357639] Crash upon exiting KInfoCenter

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357639

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

   What|Removed |Added

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

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
Still crash on exit in KDE Plasma 5.5.3 with Qt 5.5.1:
https://bugs.kde.org/show_bug.cgi?id=357718#c1

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


[kwin] [Bug 357754] Crash in eglCreateImageKHR

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357754

--- Comment #1 from Thomas Lübking  ---
Nope, EGL_NO_CONTEXT (ie. 0x0) is deliberate.
I assume this crashes in the driver for a simple OOM condition -> driver bug
(more or less)

@Martin, maybe we should have a sanity check here as well (ie. if it exceeds
the max texture size anyway, there's no point in loading it - I assume this
happens on glx, preventing the crash with a giant invalid texture)?

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

[Skanlite] [Bug 357759] New: Add report/setting for size of selection in preview

2016-01-09 Thread truf via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357759

Bug ID: 357759
   Summary: Add report/setting for size of selection in preview
   Product: Skanlite
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: trufano...@gmail.com

I'm using scanlite to scan book pages. 2 pages at once. After that the scanned
image is splitted in two pages in 3rd party app.
The easiest way to do that is to split image by equal halves.
Unfortunately scanlite doesn't report the size of selection that I made in
preview screen. Neither allows to set the selection by known parameters. That
means if I restart y laptop before I scan whole book I need to define selection
again. And it will be different as I don't know parameters of initial one. Thus
when I split scans in halves they will be different size. And this cause
inconveniences while scanning of a big books.

Reproducible: Always




Would be great if scnlite dysplays size ant top left point of preview selection
and allows to set it by these params.

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


[kdialog] [Bug 357761] New: PNG icons with transparency no longer displayed?

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357761

Bug ID: 357761
   Summary: PNG icons with transparency no longer displayed?
   Product: kdialog
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: chrno-sphe...@hotmail.com

Since 15.12, png icons that have transparency no longer display, while those
that don't have any transparency display just fine.

Reproducible: Always

Steps to Reproduce:
1. Set a PNG file with transparency as folder icon for a "Places" entry
2. Open KDialog (for example in chromium)


Actual Results:  
The respective "Places" entry has no icon at all

Expected Results:  
The respective "Places" entry shows the set icon

dolphin4 is affected as well, but not dolphin5, so maybe it's somehow related
to qt4 apps? 
The interesting thing is that the "edit entry..." dialog in Kdialog or the
folder's properties window in dolphin4 displays the icon just fine.

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


[dolphin] [Bug 357762] New: Opening root folder in Dolphin hangs entire system (Macbook 8,1) indefinitely.

2016-01-09 Thread Reece via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357762

Bug ID: 357762
   Summary: Opening root folder in Dolphin hangs entire system
(Macbook 8,1) indefinitely.
   Product: dolphin
   Version: 15.12.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: reece.d...@gmail.com

This is on a Macbook Pro 8,1 that I'm experiencing this issue. As you can
imagine it's quite important.

The entire system stops responding and the only thing you can do is reboot the
machine. The fans also speed up and the laptop gets very hot, so it's obviously
busy doing something.

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin file manager.
2. Click the root folder.
3. Wait or if the crash does not happen instantly, attempt to scroll to the
bottom.

Actual Results:  
As stated above the entire system crashes. The only thing that can be done is
rebooting the machine.

Expected Results:  
The root folder should open without crashing.

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


[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356006

scionicspec...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from scionicspec...@gmail.com ---
Just gonna' copy-paste this from my comment on the prior GTK2-related bug
357524:

"Unfortunately, this is going to be remain the case for some time, as we need
to polish and restructure the base theme before we rewrite the color generation
scripts for the GTKrc, CSS, and SVG files.

"That is, unless some enterprising artist and/or developer with some time on
their hands wants to take on the work. Even then, GTK 3's theming machinery is
being reworked so that themes don't need to be remade for each stable version
of GTK any longer, so it would be wise to delay this until that work is
complete to prevent duplication of effort.

"Until these kinks are worked out, it should be fairly straightforward for
someone to modify the SVGs, SCSS, and GTKrc files to match the color scheme of
their choice. I know that's no real solution, but it's probably the best we're
going to get in the immediate future."

All I can do is apologize for our slow progress as volunteers. I should also
mention that we can't use Oxygen's method for this as it doesn't work in GTK 3
at all in newer versions and the GTK 2 theme is based on the pixmap engine.
Rather than rebuilding the Breeze GTK 2 theme from Oxygen's engine and using
another method entirely for GTK 3, we'll be generating both at the same time.

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


[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

2016-01-09 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357577

--- Comment #17 from Maik Qualmann  ---
Created attachment 96548
  --> https://bugs.kde.org/attachment.cgi?id=96548=edit
albummanager.patch

Can you try this patch in the "core" subdirectory?

patch -p0 < albummanager.patch

Maik

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


[plasmashell] [Bug 357763] clipboard widget delete history button

2016-01-09 Thread andreas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357763

--- Comment #1 from andreas  ---
Created attachment 96549
  --> https://bugs.kde.org/attachment.cgi?id=96549=edit
main ui

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


[Akonadi] [Bug 356751] akonadi 4:15.08.2-0ubuntu1 fails to read updates from IMAP server, reporting "log_kimap: Socket timeout!"

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356751

robin.jesper...@yahoo.de changed:

   What|Removed |Added

 CC||robin.jesper...@yahoo.de

--- Comment #2 from robin.jesper...@yahoo.de ---
Hi, 
same problem here (Ubuntu 15.10).
Trying to load about 30.000 mails from yahoo imap server.

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


[plasmashell] [Bug 357764] New: application menus have only icon plasmoid view

2016-01-09 Thread andreas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357764

Bug ID: 357764
   Summary: application menus have only icon plasmoid view
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: kain...@gmail.com
CC: plasma-b...@kde.org

kicker, kickoff and the dashboard plasmoid only have an icon view mode BUT the
design goal was that every plasmoid has an icon view AND an desktop view
(larger size).
I think the application launchers could be useful on the desktop as well. So
the user want to add kicker to the desktop and search there after applications
or files. 

Reproducible: Always

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


[kwin] [Bug 357742] Crash in QV4::ExecutionEngine::newStringObject when opening window

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357742

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=351839,
   ||https://bugs.kde.org/show_b
   ||ug.cgi?id=351763

--- Comment #1 from Thomas Lübking  ---
Seems as if https://bugs.kde.org/show_bug.cgi?id=351763#c7 is voodoo and the
actual bug is somewhere else?

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351839

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=357742

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

[kwin] [Bug 351763] yet another segfault in QV4::ExecutionEngine::newStringObject

2016-01-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351763

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=357742

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

[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread Cor Blom via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #45 from Cor Blom  ---
(In reply to Thomas Lübking from comment #43)
> Resp. this one (the ARGB32 translucency handling is uncritical, it's applied
> to the preconverted image. This should be the single point of failure)
> 
> diff --git a/kcms/kfontinst/lib/FcEngine.cpp
> b/kcms/kfontinst/lib/FcEngine.cpp
> index 19b7206..012a9d5 100644
> --- a/kcms/kfontinst/lib/FcEngine.cpp
> +++ b/kcms/kfontinst/lib/FcEngine.cpp
> @@ -537,7 +537,14 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
>  if (!xImage) {
>  return QImage();
>  }
> -return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, QImage::Format_ARGB32_Premultiplied, , xImage);
> +QImage::Format format = QImage::Format_RGB32;
> +switch (DefaultDepth(QX11Info::display(), 0)) {
> +case 32: format = QImage::Format_ARGB32_Premultiplied; break;
> +case 16: format = QImage::Format_RGB16; break;
> +case 8: format = QImage::Format_Grayscale8; break;
> +default: break;
> +}
> +return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, format, , xImage);
>  }
>  
>  inline int point2Pixel(int point)

This patch solved the bug on openSUSE Leap 42.1 and nouveau (a NVD9 card)

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

[kgpg] [Bug 357746] New: The document could not been saved, as the selected codec is not supported.

2016-01-09 Thread Emma Atkinson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357746

Bug ID: 357746
   Summary: The document could not been saved, as the selected
codec is not supported.
   Product: kgpg
   Version: 2.14.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: emma.atkins...@gmail.com

Using symmetric encryption/decryption on a file on local drive.
I opened the file which used ASCII armour format.
Decrypted the file and edited the contents using the KGpg editing screen.
I successfully encrypted using symmetric encryption and a very long
pass-phrase.
When I used the Save function I get the error:
"The document could not been saved, as the selected codec is not supported."

If I use Save As and overwrite the original file I get no error message.
This looks like an unreported bug to me.

I am using 64 bit OpenSUSE 13.2 with latest package updates as of 7 Jan 2016.  
Linux (x86_64) release 3.16.7-29-desktop




Reproducible: Always

Steps to Reproduce:
1.  Create an ASCII encrypted text file (mine is about 10 KiB) on a local
drive, using a long pass-phrase.  It should have a filename something like
Testfile.asc   (I did not use Unicode, although I may have done so in the past
at some point in the past)
2.  Open the file using the KGpg Editor's Open function.
3.  Decrypt the file using KGpg using the
4.  Change the contents using the KGpg editor
5.  Encrypt the contents using symmetric encryption and the same long
pass-phrase as before.
6.  Click the Save button or use Ctrl-S or the save function from File >> Save.
7.  You should get an error message.
8.  Now try using the File >> Save As... function to overwrite the original
encrypted file.
9.  You should be successful this time. 

Actual Results:  
Step 7: a dialog box containing the following message, "The document could not
been saved, as the selected codec is not supported."

Step 9: no error and the encrypted contents displayed in the editor window as
normal.

Expected Results:  
Step 7: a dialog box asking if I want to overwrite the original encrypted file.
 Clicking yes to overwrite  should function correctly leaving the encrypted
contents displayed in the editor window as normal.

I will use the Save As.. function until the problem is resolved.  So a minor
severity bug.

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


[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

ham...@laposte.net changed:

   What|Removed |Added

 CC||ham...@laposte.net

--- Comment #46 from ham...@laposte.net ---
(In reply to Thomas Lübking from comment #42)
> We need this patch tested on all possible GPUs (notably intel/sna!)

Great !
You have killed this bug :)
My GPU : NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)
Driver : nvidia-340xx
Many thanks

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

[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread chepioq via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #47 from chepioq  ---
(In reply to Thomas Lübking from comment #42)
> We need this patch tested on all possible GPUs (notably intel/sna!)

I forgot that.
I test on laptop Toshiba Sattelite L775, nvidia card GeForce GT 525M and nvidia
drivers 358.16

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

[Touchpad-KCM] [Bug 357749] New: [libinput] Pointer acceleration cannot be set below 0

2016-01-09 Thread Cyril Yab via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357749

Bug ID: 357749
   Summary: [libinput] Pointer acceleration cannot be set below 0
   Product: Touchpad-KCM
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: rajeeshknamb...@gmail.com
  Reporter: cyril@gmail.com

When setting the acceleration to the minimum, it is set to 0, whereas the
minimum value accepted by libinput is -1. Since 0 is the default value anyway,
I cannot actually decrease the mouse acceleration speed.

Reproducible: Always

Steps to Reproduce:
1. Go to System settings > Input devices > Touchpad > Pointer Motion.
2. Set the acceleration to the minimum (maximum left).

Actual Results:  
$ sudo xinput list-props "DLL0704:01 06CB:76AD Touchpad" |grep "274"
libinput Accel Speed (274): 0.00


Expected Results:  
$ sudo xinput list-props "DLL0704:01 06CB:76AD Touchpad" |grep "274"
libinput Accel Speed (274): -1.00


Using Arch Linux (up-to-date), Touchpad KCM 5.5.3, libinput 1.1.4,
xf86-input-libinput 0.16.0, Xorg server 1.18.0.

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


[KScreen] [Bug 357751] New: Display Settings dialog too large on low resolution VGA projector

2016-01-09 Thread Gregor Mi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357751

Bug ID: 357751
   Summary: Display Settings dialog too large on low resolution
VGA projector
   Product: KScreen
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: dvra...@kde.org
  Reporter: codestr...@posteo.org

SETUP: Connect VGA projector via VGA projector (1080x768 pixels), open Display
Settings, choose Unify output.

CURRENT: the Ok, Apply, Cancel buttons are not accessible because the dialog is
too large and the dialog cannot be made smaller.

EXPECTED: It should be possible to access these buttons.

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


[dolphin] [Bug 357752] Incorrect color for hovered selected items with GTK+ Qt5 style

2016-01-09 Thread Pulfer via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357752

--- Comment #2 from Pulfer  ---
Created attachment 96543
  --> https://bugs.kde.org/attachment.cgi?id=96543=edit
Colors in Dolphin compared to colors in file open dialogs

This screenshot should be more helpful. I played with GTK2 theme colors and now
it's easy to see which color Dolphin uses for hovered items (the same color is
used for backgrounds in file dialogs).

I suggest to avoid changing text color and background color for hovered items.
It's enough to highlight icons for hovered items (like it works in KDE4-based
Dolphin and KF5-based file dialogs).

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


[kdenlive] [Bug 357756] New: 15.13.0: recent git: crop, scale & pos effect looses some of its settings

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357756

Bug ID: 357756
   Summary: 15.13.0: recent git: crop, scale & pos effect looses
some of its settings
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: wegwerf-1-...@gmx.de

Now this is a really crude bug, not easy to reproduce; I got bitten by it in a
recent project I'm working on. When using the "Crop, Scale and Position"
effect, the effect looses some of its parameters when the Curves effect is also
present. This may happen also when other effects are used, by I did not dig
into this direction. The parameters typically lost are "Clip top" and "Clip
bottom". Sometimes, also "Clip right" gets lost. Your mileage may vary.

Reproducible: Always

Steps to Reproduce:
1. Create new project and add a color clip to it.
2. Place color clip on timeline.
3. Add "Crop, Scale and Position" effect to clip in timeline. Set its clip
parameters, e.g. 12, 23, 34, 45.
4. Add a "Curves" effect too. Drag its curve points.
5. Save project.
6. New project (to get a clear situation).
7. Reload project.
8. Select color clip in timeline.
9. Check settings of the "Crop, Scale and Position" effect.

Actual Results:  
Often, effect settings have been changed. If not, try to change the Curves
effect, save, new, reload again. Most of the time some of the Crop, Scale and
Position effect's settings then will have been reset.

Expected Results:  
Effect parameter settings must not change, unless by user. Saving and reloading
a project must not change effect settings.

Please see attached example project.

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


[kde] [Bug 357533] Cannot load icon for activities

2016-01-09 Thread Marco Parillo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357533

--- Comment #3 from Marco Parillo  ---
I can confirm with the Kubuntu Daily Build running Plasma 5.5.3. In my case, if
I hit cancel, the Select Icon - KDE Control Module <2> File Dialog remains open
and neither cancel nor the X in the upper right can close it.

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


[kdenlive] [Bug 357758] New: kdenlive-git - New render widget: double-clicking profile header both opens save profile window and then expands list -- should do either or.

2016-01-09 Thread Jesse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357758

Bug ID: 357758
   Summary: kdenlive-git - New render widget: double-clicking
profile header both opens save profile window and then
expands list -- should do either or.
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

I think this could be an issue when running Kdenlive on non-KDE desktops in
general (I believe the effect widget does the same thing with its categories),
but in the new render widget, single-clicking the name of the render profile
header (containing all of the render profiles in its section) itself won't
expand the list; only single-clicking the "expand" arrow to the left of it.
Double-clicking the name, however, will open a "Save Profile" dialog box. When
I click cancel, the dialog box closes, and the list THEN expands.

Like I said, I think the effects widget does this also (in KDE, single-clicking
the name of the effect category will expand the list, in contrast to running
GNOME where you need to double-click it to expand the list).

SOLUTION: if possible, would suggest it so that single-clicking the render
profile names in the new widget will expand the list, and double-clicking will
open up the save profile dialog box.

Reproducible: Always

Steps to Reproduce:
1. Open render widget in Kdenlive

Actual Results:  
Single-clicking only highlights the render profile header name. Double-clicking
the render profile header name opens up the Save Profile dialog box, THEN
expands the list after the dialog box closes.

Expected Results:  
Single-clicking expands the list, while double-clicking opens the dialog box.

Tested with Kdenlive-git 15.13.0.r6880.0a36960-1 on Antergos Linux x64 running
GNOME 3.18.

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


[plasmashell] [Bug 351906] Auto hidden panels are not hidden on start

2016-01-09 Thread Marian Kyral via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351906

--- Comment #3 from Marian Kyral  ---
Any update on this? Latest Plasma 5.5.3 and still does not work correctly.

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


[kinfocenter] [Bug 357718] KInfoCenter Crashed When Closing

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357718

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

   What|Removed |Added

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

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
KinfoCenter still crash in KDE Plasma 5.5.3 with Qt 5.5.1:

Application: KDE Informacijos Centras (kinfocenter), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa6ba94b780 (LWP 6649))]

Thread 5 (Thread 0x7fa6a85c8700 (LWP 6650)):
#0  0x7fa6b7414c1d in poll () from /lib64/libc.so.6
#1  0x7fa6b099d422 in poll (__timeout=-1, __nfds=1, __fds=0x7fa6a85c7d40)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x1fd8370, cond=cond@entry=0x1fd83b0,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x7fa6b099f00f in xcb_wait_for_event (c=0x1fd8370) at xcb_in.c:693
#4  0x7fa6aa91d3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#5  0x7fa6b7b0c32f in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x7fa6b3dcb0a4 in start_thread () from /lib64/libpthread.so.0
#7  0x7fa6b741d04d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fa693128700 (LWP 6684)):
#0  0x7ffc3d1f0a90 in clock_gettime ()
#1  0x7fa6b7429c9d in clock_gettime () from /lib64/libc.so.6
#2  0x7fa6b7bbd7d6 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x7fa6b7d3d3b9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7fa6b7d3d945 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa6b7d3eb5e in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x7fa6b33964ad in g_main_context_prepare
(context=context@entry=0x7fa68c000990, priority=priority@entry=0x7fa693127cf8)
at gmain.c:3410
#7  0x7fa6b3396d80 in g_main_context_iterate
(context=context@entry=0x7fa68c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3788
#8  0x7fa6b3396f7c in g_main_context_iteration (context=0x7fa68c000990,
may_block=1) at gmain.c:3869
#9  0x7fa6b7d3ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#10 0x7fa6b7ce5d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#11 0x7fa6b7b0761a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#12 0x7fa6b67f7df8 in ?? () from /usr/lib64/libQt5Qml.so.5
#13 0x7fa6b7b0c32f in ?? () from /usr/lib64/libQt5Core.so.5
#14 0x7fa6b3dcb0a4 in start_thread () from /lib64/libpthread.so.0
#15 0x7fa6b741d04d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fa689244700 (LWP 6690)):
#0  0x7fa6b7d3f757 in ?? () from /usr/lib64/libQt5Core.so.5
#1  0x7fa6b33968f1 in g_main_context_check
(context=context@entry=0x7fa684000990, max_priority=2147483647,
fds=fds@entry=0x7fa684002e70, n_fds=n_fds@entry=1) at gmain.c:3649
#2  0x7fa6b3396df8 in g_main_context_iterate
(context=context@entry=0x7fa684000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3805
#3  0x7fa6b3396f7c in g_main_context_iteration (context=0x7fa684000990,
may_block=1) at gmain.c:3869
#4  0x7fa6b7d3ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7fa6b7ce5d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7fa6b7b0761a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7fa6b67f7df8 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7fa6b7b0c32f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7fa6b3dcb0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fa6b741d04d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa543602700 (LWP 6722)):
#0  0x7fa6b7414c1d in poll () from /lib64/libc.so.6
#1  0x7fa6b3396e64 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fa53c003070, timeout=-1, context=0x7fa53c000990) at gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7fa53c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3803
#3  0x7fa6b3396f7c in g_main_context_iteration (context=0x7fa53c000990,
may_block=1) at gmain.c:3869
#4  0x7fa6b7d3ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7fa6b7ce5d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7fa6b7b0761a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7fa6b67f7df8 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7fa6b7b0c32f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7fa6b3dcb0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fa6b741d04d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa6ba94b780 (LWP 6649)):
[KCrash Handler]
#6  0x7fa6b736d187 in raise () from /lib64/libc.so.6
#7  0x7fa6b736e538 in abort () from 

[plasmashell] [Bug 357760] Plasma 5.5.3 crash at start after update

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357760

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
I can not see window decorations, but I can open Firefox via drKonqi link to
this bug. Alt+F2 does not work...

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


[plasmashell] [Bug 357760] Plasma 5.5.3 crash at start after update

2016-01-09 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357760

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

   What|Removed |Added

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

--- Comment #2 from opensuse.lietuviu.ka...@gmail.com ---
The source of problem is mixture of Qt 5.5.0 and 5.5.1 packages.

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


[dolphin] [Bug 355310] Setting Custom Icon for Places Entry Impossible Due to Forced Window Focus

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355310

Soukyuu  changed:

   What|Removed |Added

 CC||chrno-sphe...@hotmail.com

--- Comment #6 from Soukyuu  ---
Still happens with 15.12

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


[plasmashell] [Bug 357763] New: clipboard widget delete history button

2016-01-09 Thread andreas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357763

Bug ID: 357763
   Summary: clipboard widget delete history button
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kain...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

in the main UI there is right to the search an delete button but in my point of
view delete the history could be e.g. in the preferences of the plasmoid but
should not be part of the MAIN ui. the standard setting has 7 clipboard entries
and you can delete every single entry so you have to click 7times the delete
button and the main UI is cleaner.

Reproducible: Always

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


[kdialog] [Bug 357761] Icons with spaces in path are not displayed

2016-01-09 Thread Soukyuu via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357761

Soukyuu  changed:

   What|Removed |Added

Summary|PNG icons with transparency |Icons with spaces in path
   |no longer displayed?|are not displayed

--- Comment #1 from Soukyuu  ---
Actually, it's not related to PNGs or anything, it seems that in some cases
(namely displaying the Places panel) the parsing of the user-places.xbel fails
due to spaces in icon path.

So, "/some/path/to/icon.png" will work, but "/some/path to/icon.png" will not.
It used to work in all cases before, though.

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


[plasmashell] [Bug 357764] application menus have only icon plasmoid view

2016-01-09 Thread andreas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357764

andreas  changed:

   What|Removed |Added

 CC||h...@kde.org

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


[digikam] [Bug 357753] Picture preview in geotagging window is possibily rotated

2016-01-09 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357753

--- Comment #3 from Maik Qualmann  ---
Created attachment 96550
  --> https://bugs.kde.org/attachment.cgi?id=96550=edit
geolocation.png

With digiKam-5.0.0-beta3, seems the problem does not exist anymore. See the
screenshot.

Maik

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


  1   2   3   >