[frameworks-kglobalaccel] [Bug 385536] global shortcuts do not work with keys that have been mapped with keyboard options

[Stefan Majewsky]

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

--- Comment #2 from Stefan Majewsky  ---
After restarting kglobalaccel5 with `killall kglobalaccel5 && sleep 3 &&
kglobalaccel5 &`, the affected shortcuts start working.

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

[dolphin] [Bug 385513] Dolphin don't browse network.

[SinClaus]

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

--- Comment #7 from SinClaus  ---
OK, adding vers=2.0 to the mount string resolve problem with mount, but Dolphin
don't browse network...

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

[frameworks-kglobalaccel] [Bug 385536] global shortcuts do not work with keys that have been mapped with keyboard options

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
Does the problem persist after restarting kglobalacceld5?

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

[kdenlive] [Bug 385542] New: Clips with Speed effect reset when moved back with other clips

[MJ Vilches]

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

Bug ID: 385542
   Summary: Clips with Speed effect reset when moved back with
other clips
   Product: kdenlive
   Version: 17.04.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: mjvilchesf...@gmail.com
  Target Milestone: ---

Created attachment 108262
  --> https://bugs.kde.org/attachment.cgi?id=108262=edit
A video showing the bug

I was editing a timelapse video. I each clips in the video a Speed Effect. One
of the clips was cut in many portions, and I added more clips after it with
speed effect as well. Later, I saw a portion of the previous clip that I want
to remove, so I trimmed it and deleted it, leaving a space. I selected all the
clips after the space through Shift+drag mouse over the clips to  move them,
all at once, back to fill in the space. But after doing that, the first clip
from the selected clips(after the removed portion) along with every clip after
it, resets to it's normal speed, removing the speed effect and making every
clips start from the beginning of the raw clip.

A workaround that I did to prevent this is, instead of moving the clips all at
once, I move them one by one. But I do hope this bug get's fixed on future
updates.

Anyways. Thanks to the Kdenlive dev team for providing a nice free video
editing software!

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

[kwin] [Bug 366255] Add "Operations Menu" option to Window Actions list

[Martin Flöser]

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

--- Comment #5 from Martin Flöser  ---
It's a problem with the grab. Probably KWin holds a grab from the moment when
you click. Then Qt tries to perform a grab when the menu opens, that fails and
so Qt doesn't listen for the release.

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

[plasmashell] [Bug 385541] New: Plasmashell crashes

[John Salatas]

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

Bug ID: 385541
   Summary: Plasmashell crashes
   Product: plasmashell
   Version: 5.10.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jsala...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.10.0-33-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
I'm not doing something special. More or less the usual stuff: I have 1-2
firefox windows open, kate, jetbrains intelij (doing some programming) and
maybe a couple more applications. 

At random times plasmashell crashes and restarts and I really cannot tell why.
It just crashes out of the blue

I have 2 monitors connected in an AMD  GPU
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Device [1002:67ef] (rev cf) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device [1458:22dd]
Flags: bus master, fast devsel, latency 0, IRQ 125
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=2M]
I/O ports at e000 [size=256]
Memory at dfe0 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010

Capabilities: [150] Advanced Error Reporting
Capabilities: [200] #15
Capabilities: [270] #19
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] #13
Capabilities: [2d0] #1b
Capabilities: [320] Latency Tolerance Reporting
Capabilities: [328] Alternative Routing-ID Interpretation (ARI)
Capabilities: [370] L1 PM Substates
Kernel driver in use: amdgpu
Kernel modules: amdgpu

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
[Current thread is 1 (Thread 0x7fa5ead7d8c0 (LWP 1327))]

Thread 16 (Thread 0x7fa4dfefe700 (LWP 7143)):
#0  __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7fa5e555f2bd in _int_free (av=0x7fa4d820, p=0x7fa4d80033f0,
have_lock=0) at malloc.c:3962
#2  0x7fa5e556353c in __GI___libc_free (mem=) at
malloc.c:2968
#3  0x7fa5e0f7428a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa5e5f02e52 in QEventDispatcherGlib::~QEventDispatcherGlib
(this=0x7fa4d80013d0, __in_chrg=) at
kernel/qeventdispatcher_glib.cpp:374
#5  0x7fa5e5f03059 in QEventDispatcherGlib::~QEventDispatcherGlib
(this=0x7fa4d80013d0, __in_chrg=) at
kernel/qeventdispatcher_glib.cpp:402
#6  0x7fa5e5cd8b1f in QThreadPrivate::finish (arg=arg@entry=0x408f3f0) at
thread/qthread_unix.cpp:396
#7  0x7fa5e5cd9991 in __pthread_cleanup_class::~__pthread_cleanup_class
(this=, __in_chrg=) at
/usr/include/pthread.h:561
#8  QThreadPrivate::start (arg=0x408f3f0) at thread/qthread_unix.cpp:325
#9  0x7fa5e4b7f6ba in start_thread (arg=0x7fa4dfefe700) at
pthread_create.c:333
#10 0x7fa5e55e63dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fa4f4a09700 (LWP 2255)):
#0  0x7fa5e55d624d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa5e0fba6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5e0f76e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5e0f77330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa5e0f7749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa5e5f0294b in QEventDispatcherGlib::processEvents
(this=0x7fa4e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fa5e5eab7ca in QEventLoop::exec (this=this@entry=0x7fa4f4a08cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fa5e5cd4cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#8  0x7fa4f5c20517 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#9  0x7fa5e5cd9989 in QThreadPrivate::start (arg=0x3eb56d0) at
thread/qthread_unix.cpp:368
#10 0x7fa5e4b7f6ba in start_thread (arg=0x7fa4f4a09700) at
pthread_create.c:333
#11 0x7fa5e55e63dd in clone () 

[Powerdevil] [Bug 385540] New: windows out of range

[bugzilla_noreply]

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

Bug ID: 385540
   Summary: windows out of range
   Product: Powerdevil
   Version: 5.10.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: capitaine.k...@hotmail.fr
  Target Milestone: ---

Created attachment 108261
  --> https://bugs.kde.org/attachment.cgi?id=108261=edit
power management window out of range

the energy saving windows is out of range when accessed by clicking on the
battery icon, therefore it's impossible to save the new settings. however
accessing the window by the start menu, system settings, power management works
properly.

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

[plasma-browser-integration] [Bug 385531] Visual feedback when download starts

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
I agree, but these are really issues with Firefox, not Plasma.

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

[k3b] [Bug 385367] K3b uses "/tmp" as default path to save VCD rips

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Nate Graham  ---
Patch available at https://phabricator.kde.org/D8231

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

[frameworks-kio] [Bug 382419] Krusader (sometimes) crashes when moving file from ext4 partition to fat32 partition

[bugzilla_noreply]

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

--- Comment #8 from linn...@gmail.com ---
(In reply to Christoph Feck from comment #7)
> No response, changing status. If you have new information, please add a
> comment.

Really sorry for late replying, I don't check email often.
After have had many problems with Plasma 5 (at least with version Mageia
offer), I downgraded to the KDE4.

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

[konsole] [Bug 385454] konsole becomes uninteractive after running any bash script

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Nate Graham  ---
Can you provide the script in question?

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

[dolphin] [Bug 385513] Dolphin don't browse network.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from Nate Graham  ---
OK, if you can get to the shares in Dolphin by entering the full path, buit
browsing is bustes, then this is a duplicate of
https://bugs.kde.org/show_bug.cgi?id=369850

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

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

[kio-extras] [Bug 369850] Can't browse samba workgroups

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||tomsk_interf...@vtomske.ru

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

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

[dolphin] [Bug 385513] Dolphin don't browse network.

[SinClaus]

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

--- Comment #5 from SinClaus  ---
OK, munt.cifs say

mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

but smbclient connects to the srvers shares and dolphin can browse this shares
if say them to connect with full address, i.e. smb://server.domain.xx/C$.

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

[konsole] [Bug 385454] konsole becomes uninteractive after running any bash script

[Kurt Hindenburg]

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

--- Comment #3 from Kurt Hindenburg  ---
Ok but without the script, I have no way of debugging this

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

[krita] [Bug 385539] New: Only the first brush stroke gets registered

[no]

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

Bug ID: 385539
   Summary: Only the first brush stroke gets registered
   Product: krita
   Version: 3.3.0
  Platform: Homebrew (Mac OS X)
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: grocerygho...@gmail.com
  Target Milestone: ---

Overview (This bug started after I messed around with my preferences) 
When I open a new canvas and try to draw on it, my brush doesn't work. Only
after I undo the (invisible) brush stroke does it allow me to draw. Even then,
it only works for the first brush stroke. Once I complete the first brush
stroke, the brush circle disappears and stops showing my brush strokes. 

Steps to Reproduce 
1. Open Preferences 
2. Go to general > Cursor 
3. Select "Tool Icon" for Cursor Shape and "Preview Outline" for Outline Shape. 
4. Go to Miscellaneous 
5. Change autosave time to 10 minutes
6. Uncheck "Create backup file" 
7. Change Undo Stack Size to 40 
8. Go to "Canvas Input Settings" > Zoom Canvas 
9. Delete krita's original zoom in shortcut
10. Replace zoom in shortcut (=) with (+) 
11. (I forgot what this belonged under) Delete action that had the default
shortcut "Middle button" for the mouse 
12. Go to Alternate Invocation
13. Add Mouse button - Left Button - Primary Mode 
14. Press "OK" and save the settings

Results
You won't be able to draw? 

Expected Results
Amount of undos increase 
Autosaves every ten minutes
Zoom in and zoom out are assigned to + and - 

Build Date & Platform
I don't know how to find the build date, but I downloaded the most recent
version yesterday. Krita version 3.3.0 (Today: Oct. 9, 2017) on Mac 10.12.6


* I was going to add an attachment of the brush circle disappearing, but it
seems to be working fine now? I'll update this if the problem resurfaces.

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

[frameworks-kirigami] [Bug 380511] Kirigami 2.2.0 scrolling doesn't work properly for scroll wheels, touchpads, or touchscreens

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

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

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

[Discover] [Bug 385534] Scrolling via touch does not work

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---


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

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

[kwin] [Bug 366255] Add "Operations Menu" option to Window Actions list

[Marcos Luiz Cassarini Taranta]

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

--- Comment #4 from Marcos Luiz Cassarini Taranta  ---
(In reply to Martin Flöser from comment #3)
> @Marcos: could you add the backtrace? Then I might be able to give you a
> hint where the problem is.

My bad, I don't get the SIGSEGV, maybe it was something that happened one time
for whatever reason

But when you invoke the operations menu by the mouse, you are stuck with the
menu open but can't click anywhere outside the menu, also you can't close it by
pressing esc or invoking another operations menu. The way that I use to get
back to control my DE by mouse, is by invoking the krunner using alt+f2.

I'm looking at the code in the meantime to figure out what is the problem here.

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

[krusader] [Bug 384653] [zip kioslave] Journal spammed with “kf5.kio.core: error() called twice! Please fix the KIO slave.”

[Martin Kostolný]

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

--- Comment #15 from Martin Kostolný  ---
Thanks for test archive and info! Unfortunately I still cannot replicate the
issue. I even downgraded KIO to version 5.37 but no KIO error showed up in
journal. What distribution are you testing on?

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

[kdeconnect] [Bug 385538] New: Plasmoid Notifications stop happening in favor of KNotify notifications

[Bucky]

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

Bug ID: 385538
   Summary: Plasmoid Notifications stop happening in favor of
KNotify notifications
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: bu...@mightytikigod.com
  Target Milestone: ---

I'm using an up-to-date installation of Fedora 26:

plasma-workspace-5.10.5-3.fc26.x86_64
kde-connect-1.0.3-2.fc26.x86_64
kf5-knotifications-5.36.0-1.fc26.x86_64
libnotify-0.7.7-2.fc26.x86_64

I noticed that at no particular point in the day, notifications stop appearing
as translucent, dark gray popups in the bottom right-hand corner, and begin
appearing top center, in a large popup with a light gray background, and a
heavy black border.

My Googling leads me to believe the big popup is a KNotify notification, while
the little one is a plasmoid notification.

It wouldn't bother me, except you can press the "Reply" button in the plasmoid
notification and you will get a reply dialog. Pressing "Reply" in the KNotify
window just cancels the notification. Also, the KNotify window's title is
overlayed on top of the notification text.

No error messages pop up on my screen.

I read that errors should appear in .xsession-errors, except

(1) that file is months old, and
(2) I believe KDE now uses Wayland, and
(3) I have no idea where to find the error log for the Wayland session to
include in this report ("find . -name wayland" in my home directory produces no
results).

I realize this is precious little to go on.

I will be happy to add more clues if I know what to look for.

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

[kalarm] [Bug 385378] Summer time 1 hour off

[bugzilla_noreply]

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

--- Comment #1 from hoit...@gmail.com ---
The problem disappeared! Solved for me.

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

[kile] [Bug 385537] New: Opening a project opens all files, regardless of last state

[bugzilla_noreply]

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

Bug ID: 385537
   Summary: Opening a project opens all files, regardless of last
state
   Product: kile
   Version: 2.9.91
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: ree...@gmail.com
  Target Milestone: ---

When I open a project, Kile now opens every file in the project, regardless of
the last state of that project. Since there is no 'close all' option, this
requires manually closing several tens of files.

This is a regression. Kile did not used to do this.

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

[plasmashell] [Bug 381608] Plasmashell use 100% cpu

[dmidge]

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

dmidge  changed:

   What|Removed |Added

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

--- Comment #14 from dmidge  ---
Hi again,

I am re-opening this ticket because I have some new information to provide.
I used to have a widget that displayed every second or so, the use of the CPU,
the RAM and the network. Thus, I guess it made a lot of refresh.

Removing that on the tray bar, I still have my CPU usage growing to 100% with
plasmashell, but it is growing slowly. I can work with my computer for more
than one hour without killing plasmashell just because I removed this widget.
Before that, I needed to kill plasmashell under 5 minutes. So I guess there is
something going on with the widget that refreshes a lot the display of the tray
bar and the increasing CPU usage of plasmashell.
(Because now, the CPU usage of plasmashell grows linearly over time, until I
kill it and restart it. It was probably the case before but I didn't have time
to notice it.)

Funny thing is: it used not to happen to me with the plasmashell and nouveau
version that were 1 year old.
Now, my plasma-workspace version is 5.10.5-4 and xf86-video-nouveau is
1.0.15-2.

Please ask me if you need further information. :o)

Cheers!

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

[okular] [Bug 384147] Hovering over annotations no longer shows contents in tooltip

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Version Fixed In|17.08.1 |17.08.2

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

[kde] [Bug 325265] Desktop windows will become unresponsive at random

[z]

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

z  changed:

   What|Removed |Added

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

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

[digikam] [Bug 385368] digiKam causes my machine to blue screen (crash) during installation on Windows 10 while check process in memory

[Rich]

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

Rich  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #15 from Rich  ---
This latest build installed without any issues what-so-ever.

Thank you very much for you continued effort on this!


Rich

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

[konsole] [Bug 384620] Broken ncurses box() rendering with new terminfo for TERM=xterm (no rep?)

[Evangelos Foutras]

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

Evangelos Foutras  changed:

   What|Removed |Added

 CC||evange...@foutrelis.com

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

[dolphin] [Bug 385523] Link current location into the "places"

[Elvis Angelaccio]

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

--- Comment #2 from Elvis Angelaccio  ---
What about: right-click on the view -> Add to places?

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

[kmail2] [Bug 383807] Doubled mail after filtering

[Eugen Albiker]

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

Eugen Albiker  changed:

   What|Removed |Added

 CC||eu...@eugenalbiker.de

--- Comment #2 from Eugen Albiker  ---
Hi,
same problem here.

KMail 5.5.3
KDE Frameworks 5.38.0
Qt 5.9.1 (kompiliert gegen 5.9.1)

It happens only with filtered mail - sometimes
Fix is: clearing caches by using he Akonadi Console

Greetings
Eugen

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

[krunner] [Bug 379700] Krunner crashes on start of typing / directly after calling it

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
That's good, it's probably fixed now. A lot of KRunner crashing bugs have been
fixed since Ubuntu 16.10 was packaged.

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

[digikam] [Bug 385467] Cannot Add Or Edit Bookmarks / No plugins loaded

[bugzilla_noreply]

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

--- Comment #14 from caulier.gil...@gmail.com ---
I remember somebody report this problem and Maik fix something few weeks ago.

I suspect a reverse geocoding process with an Internet service. There are a
lots of plugins available in Marble, that we don't use in fact. It's time to
cleanup the bundle install to prevent this problem.

Yes, another issue is the way to go.

Gilles Caulier

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

[krunner] [Bug 379700] Krunner crashes on start of typing / directly after calling it

[Stefan Krüger]

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

--- Comment #3 from Stefan Krüger  ---
@(In reply to Christoph Feck from comment #2)

i have update my system to 17.04 some time ago.
currently i can not reproduce this behavior.
so eventually we could just close this?
if it helps - i think i have a backup image/disc of the old system some where -
i could try to put it back in and check if i can reproduce it then. do you have
a good tutorial / getting-started information on valgrind logs? (i currently
don't know what it is / how to perform this kind of logs..)

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

[digikam] [Bug 385368] digiKam causes my machine to blue screen (crash) during installation on Windows 10 while check process in memory

[bugzilla_noreply]

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

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

   What|Removed |Added

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

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

[frameworks-kglobalaccel] [Bug 385536] New: global shortcuts do not work with keys that have been mapped with keyboard options

[Stefan Majewsky]

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

Bug ID: 385536
   Summary: global shortcuts do not work with keys that have been
mapped with keyboard options
   Product: frameworks-kglobalaccel
   Version: 5.38.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: majew...@gmx.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

To reproduce:

1. Open the "Advanced" tab of `kcmshell5 kcm_keyboard`.
2. Enable "Configure keyboard options", and select (for example) "Caps Lock
behavior > Make Caps Lock an additional Esc". Press "Apply".
3. Use a shortcut that involves the Esc key (e.g. Ctrl-Alt-Esc for xkill).

The shortcut works when the actual Esc key is used, but not when the Caps Lock
key is pressed, even though it should work like Esc.

This is the instance where I first observed this. I've found another instance
of the same problem where, after remapping Esc to F13, a global shortcut that
is set to F13 is not triggered when I press the correct key.

In `kcmshell5 keys`, the mapping is applied correctly. For example, if I click
on one of the recording button and press the Esc key, it fills in "F13" as
desired. Same for the Caps Lock key, which produces "Esc" in the input field.

One noteworthy detail: This problem only happens when I use the keyboard
options that kcm_keyboard presents, i.e. the symbols options from
/usr/share/X11/xkb/rules/evdev et al. When I do not use keyboard options and
instead employ an Xmodmap like below, everything works correctly.

  $ cat .Xmodmap
  clear Lock
  keycode 0x42 = Escape
  keycode 0x09 = F13

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

[plasmashell] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Nate Graham]

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

--- Comment #7 from Nate Graham  ---
You don't need my permission; patches are always welcome!

My preference would be to not lighten or darken windows at all, and use
something else to show selection, like how macOS does it. Then we don't even
need to add a new user-facing setting.

But it's your patch, so you get to choose. :) Once you have something working,
please submit it on https://phabricator.kde.org/

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

[plasmashell] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Salva Corts]

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

--- Comment #6 from Salva Corts  ---
Exactly, you are actually having the same feedback when you select a windows
with dark windows as with fully bright windows. I would like to help you
implementing that feature. Do I have green light?

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

[digikam] [Bug 385368] digiKam causes my machine to blue screen (crash) during installation on Windows 10 while check process in memory

[Michael Preschnofsky]

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

--- Comment #14 from Michael Preschnofsky  ---
Dear Gilles,
thank´s a lot. 
The Installation process worked perfect with this build.
Kind regards from Vienna/Austria.
Michael

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Christoph Feck]

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

--- Comment #40 from Christoph Feck  ---
It looks like bug 385535 says this (or a related crash) is still happening with
KF5 5.38 and Plasma 5.11.

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

[plasmashell] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
Summary|Present Windows: Do not |Present Windows: Don't
   |hardcode brightness on  |darken all windows and
   |presentwindows.cpp  |denote selection some other
   ||way than restoring original
   ||lightness

--- Comment #5 from Nate Graham  ---
The idea is that when you mouse over a window, it becomes bright, to show that
it's selected.

But I see what you mean, it's a bit dim. And not only Windows 10 that keeps
them bright all the time; macOSalso keeps then un-darkened during a Present
Windows operation. In macOS, selection is denoted by a blue border and the a
floating box showing the window title.

While a user-facing option would resolve this issue, it may be worth revisiting
the default state as well, so that people don't feel like they have to tweak
anything.

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

[plasmashell] [Bug 385522] Present Windows: Do not hardcode brightness on presentwindows.cpp

[Salva Corts]

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

--- Comment #4 from Salva Corts  ---
No, I don see any kind of glitch. It's just for aesthetics.

I can think about three main reasons:
 1) Dark windows make difficult to see whats inside that window.
 2) Not everybody likes how does it fit with their desktop design
 3) Thinkig about how tweakable is KDE; it shoud have this feature implemented.

I have attached two images to compare how does it look on Windows 10 and how
does it on KDE. I would be fantastic to be able to choose between them.

Thanks you!

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

[frameworks-kded] [Bug 385535] New: kded5: Crash when logging out of Plasma-Wayland

[Rainer Finke]

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

Bug ID: 385535
   Summary: kded5: Crash when logging out of Plasma-Wayland
   Product: frameworks-kded
   Version: 5.38.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: m...@rainer-finke.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

When logging out Plamsa-Wayland (Plasma 5.11 beta), kded5 is always crashing.
Tested several times without running any application.

Crash Log:
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: Shutdown called with confirm  -1
 type  0  and mode  -1
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: After modifications confirm is 
-1  type is  0  and mode  3
Okt 09 21:26:49 pc org_kde_powerdevil[2613]: powerdevil: Scheduling inhibition
from ":1.19" "ksmserver" with cookie 1 and reason "Shutting down system"
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: saveSession is  false
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: Saving legacy session apps
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: Done saving  0  legacy session
apps
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: clients should be empty,  false
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: completeShutdownOrCheckpoint
called
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: completeShutdownOrCheckpoint
called
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: state is  7
Okt 09 21:26:49 pc ksmserver[2566]: Error loading text-to-speech plug-in
"flite"
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: Starting killing clients
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: startKilling: client 
"pulseaudio" ( 101661911671180001507577180002566 )
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: startKilling: client 
"/usr/bin/xembedsniproxy" ( 1016619116711800015075771800025660001 )
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver:  We killed all clients. We have
now clients.count()= 2
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: KSMServer::completeKilling
clients.count()= 2
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: KSMServer::completeKilling
clients.count()= 1
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: KSMServer::completeKilling
clients.count()= 0
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: Starting killing WM
Okt 09 21:26:49 pc ksmserver[2566]: ksmserver: KSMServer::completeKillingWM
clients.count()= 0
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc polkitd[707]: Unregistered Authentication Agent for
unix-session:c8 (system bus name :1.229, object path
/org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from
bus)
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 21:26:49 pc kdeinit5[2534]: QDBusAbstractAdaptor: Cannot relay 

[kwin] [Bug 385499] Crash in Wayland when using Kate

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #1 from Martin Flöser  ---
@David: I just stared half an hour at the backtrace and I don't see anything
which could crash there. Could you please have a look whether you see
something?

The crash happens with an X11 Kate after a recent upgrade of X on debian
testing.

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

[gwenview] [Bug 333958] When a movie plays during slideshow, the playback controls are visible until you move the cursor

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
Summary|Control panel is visible|When a movie plays during
   |when playing a movie|slideshow, the playback
   ||controls are visible until
   ||you move the cursor

--- Comment #7 from Nate Graham  ---
I see what you mean now. That's definitely a bug.

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

[plasmashell] [Bug 385522] Present Windows: Do not hardcode brightness on presentwindows.cpp

[Salva Corts]

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

--- Comment #3 from Salva Corts  ---
Created attachment 108260
  --> https://bugs.kde.org/attachment.cgi?id=108260=edit
Present Windows on KDE

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

[plasmashell] [Bug 385522] Present Windows: Do not hardcode brightness on presentwindows.cpp

[Salva Corts]

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

--- Comment #2 from Salva Corts  ---
Created attachment 108259
  --> https://bugs.kde.org/attachment.cgi?id=108259=edit
Present Windows on Windows 10

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

[Discover] [Bug 385534] Scrolling via touch does not work

[Thomas Pfeiffer]

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

--- Comment #1 from Thomas Pfeiffer  ---
I also reproduced it both in 5.10.5 and Git.

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

[Discover] [Bug 385534] New: Scrolling via touch does not work

[Thomas Pfeiffer]

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

Bug ID: 385534
   Summary: Scrolling via touch does not work
   Product: Discover
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: thomas.pfeif...@kde.org
  Target Milestone: ---

In Discover, scrolling via touch is currently broken.
Sliding horizontally between pages works with touch, but neither the list of
applications nor the sidebar nor the details page scroll via touch.

I reproduced it under both X11 and Wayland, under Manjaro and neon. In other
Kirigami apps, scrolling works just fine, it's only broken in Discover.

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

[digikam] [Bug 385467] Cannot Add Or Edit Bookmarks / No plugins loaded

[bugzilla_noreply]

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

--- Comment #13 from hardy.pub...@gmail.com ---
More accuratetely, the 30s delay is only on the first use of Geo Editor after
digiKam launch. Thereafter there is no delay.

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

[digikam] [Bug 385467] Cannot Add Or Edit Bookmarks / No plugins loaded

[bugzilla_noreply]

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

--- Comment #12 from hardy.pub...@gmail.com ---
Created attachment 108258
  --> https://bugs.kde.org/attachment.cgi?id=108258=edit
5.8.0 GeoEditor Window

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

[digikam] [Bug 385467] Cannot Add Or Edit Bookmarks / No plugins loaded

[bugzilla_noreply]

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

--- Comment #11 from hardy.pub...@gmail.com ---
Thank you plugin problem gone.

Maybe it is a coincidence but now it takes 30s for the Geolocation Editor
window to be usable. For 30s it's just a white block. See image attached.

Shall I raise a another ticket?

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

[kactivitymanagerd] [Bug 385533] New: kactivitymanagerd: Crash when logging out of Plasma

[Rainer Finke]

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

Bug ID: 385533
   Summary: kactivitymanagerd: Crash when logging out of Plasma
   Product: kactivitymanagerd
   Version: 5.10.95
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: m...@rainer-finke.de
CC: plasma-b...@kde.org
  Target Milestone: ---

When I loggout of Plasma 5.11 beta (5.10.95) on X11 and I have a applicatiob
like Konsole open, there is always a crash of kactivitymagerd.

Crash log:
Okt 09 20:54:35 pc sddm-helper[6687]: [PAM] Closing session
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc sddm-helper[6687]: pam_unix(sddm:session): session closed
for user username
Okt 09 20:54:35 pc dbus-daemon[1082]: Activating service
name='org.kde.kglobalaccel'
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc sddm-helper[6687]: pam_kwallet5(sddm:session): pam_kwallet5:
pam_sm_close_session
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc sddm-helper[6687]: pam_kwallet5(sddm:setcred): pam_kwallet5:
pam_sm_setcred
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc kdeinit5[6732]: bluedevil: Destroyed
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc sddm-helper[6687]: [PAM] Ended.
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc sddm[1689]: Auth: sddm-helper exited successfully
Okt 09 20:54:35 pc sddm[1689]: Socket server stopping...
Okt 09 20:54:35 pc sddm[1689]: Socket server stopped.
Okt 09 20:54:35 pc sddm[1689]: Display server stopping...
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc kglobalaccel5[6749]: The X11 connection broke (error 1). Did
the X11 server die?
Okt 09 20:54:35 pc kactivitymanagerd[6835]: The X11 connection broke (error 1).
Did the X11 server die?
Okt 09 20:54:35 pc kactivitymanagerd[6835]: QThread: Destroyed while thread is
still running
Okt 09 20:54:35 pc kactivitymanagerd[6839]: The X11 connection broke (error 1).
Did the X11 server die?
Okt 09 20:54:35 pc kiod5[7280]: The X11 connection broke (error 1). Did the X11
server die?
Okt 09 20:54:35 pc kscreen_backend_launcher[6762]: The X11 connection broke
(error 1). Did the X11 server die?
Okt 09 20:54:35 pc kuiserver5[7084]: The X11 connection broke (error 1). Did
the X11 server die?
Okt 09 20:54:35 pc kiod5[7280]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc kdeinit5[6732]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Okt 09 20:54:35 pc systemd-logind[502]: Removed session c20.
Okt 09 20:54:35 pc kdeconnectd[7334]: The X11 connection broke (error 1). Did
the X11 server die?
Okt 09 20:54:35 pc kdeinit5[6732]: The X11 connection broke: I/O error (code 1)
Okt 09 20:54:35 pc systemd[1]: Started Process Core Dump (PID 7349/UID 0).
Okt 09 20:54:35 pc org_kde_powerdevil[1115]: powerdevil: ACTIVE SESSION PATH
CHANGED: "/"
Okt 09 20:54:35 pc org_kde_powerdevil[1115]: powerdevil: Switched to inactive
session - leaving unchanged
Okt 09 20:54:36 pc systemd-coredump[7352]: Process 6835 (kactivitymanage) of
user 1000 dumped core.

Stack trace of thread
6835:
#0  0x7f914bbd08a0
raise (libc.so.6)
#1  0x7f914bbd1f09
abort (libc.so.6)
#2  0x7f914c370858
_ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
#3  0x7f914c38016e
_ZN7QThreadD2Ev (libQt5Core.so.5)
#4  0x7f9123bdea5c
n/a (kactivitymanagerd_plugin_sqlite.so)

[dolphin] [Bug 345906] Status bar: show drive capacity

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
Like kilbertphone, I would also like to see this information. I've submitted a
patch that adds it:

https://phabricator.kde.org/D8227

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

[kwin] [Bug 385372] Crash when changing compositing backend

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/47343fb8f75909f6491c05340
   ||04df56ee1e53737
   Version Fixed In||5.11.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Martin Flöser  ---
Git commit 47343fb8f75909f6491c0534004df56ee1e53737 by Martin Flöser.
Committed on 05/10/2017 at 19:32.
Pushed by graesslin into branch 'Plasma/5.11'.

[platforms/drm] Use a shared pointer for gbm_surface

Summary:
The gbm_surface is owned by the EglGbmBackend, but it's not the only one
using it. The DrmSurfaceBuffer is also using it and needs it to destroy
the gbm_bo. Now this can become a problem in the following situation:

* a page flip is still pending
* the EglGbmBackend destroys the gbm_surface

-> when the page flip happens the DrmSurfaceBuffer will try to destroy
the gbm_bo and crash as the gbm_surface is no longer valid. This
situation can happen when switching screens or when switching compositing
backend (OpenGL 2 -> OpenGL 3).

To address this problem a class GbmSurface is added which wrapps the
gbm_surface pointer. The EglGbmBackend creates and holds a shared pointer
to the GbmSurface and passes that one to the DrmSurfaceBuffer. So when
cleaning up the gbm_surface only the shared pointer is reset and in case
the DrmSurfaceBuffer still needs it, it can access it without problems.
FIXED-IN: 5.11.0

Test Plan: Not yet

Reviewers: #kwin, #plasma, subdiff

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +7-0autotests/CMakeLists.txt
A  +119  -0autotests/test_gbm_surface.cpp [License: GPL (v2)]
M  +1-1plugins/platforms/drm/CMakeLists.txt
M  +1-1plugins/platforms/drm/drm_backend.cpp
M  +4-1plugins/platforms/drm/drm_backend.h
M  +5-6plugins/platforms/drm/drm_buffer_gbm.cpp
M  +5-3plugins/platforms/drm/drm_buffer_gbm.h
M  +5-6plugins/platforms/drm/egl_gbm_backend.cpp
M  +4-1plugins/platforms/drm/egl_gbm_backend.h
C  +24   -30   plugins/platforms/drm/gbm_surface.cpp [from:
plugins/platforms/drm/drm_buffer_gbm.h - 052% similarity]
C  +17   -23   plugins/platforms/drm/gbm_surface.h [from:
plugins/platforms/drm/drm_buffer_gbm.h - 056% similarity]

https://commits.kde.org/kwin/47343fb8f75909f6491c0534004df56ee1e53737

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

[dolphin] [Bug 385503] Send as email attachment service menu not working

[Jonathan Dotson]

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

Jonathan Dotson  changed:

   What|Removed |Added

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

--- Comment #2 from Jonathan Dotson  ---
You are right. I just removed Kmail completely and now the service menu is
gone.

Sorry about that.

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

[kile] [Bug 373223] Window becomes very large

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Michel Ludwig  ---
Please try the Kile 2.9.91 and check whether this problem still occurs. Thanks!

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

[kile] [Bug 381390] Kile: schema menu entry grayed out

[Michel Ludwig]

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

Michel Ludwig  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #1 from Michel Ludwig  ---
Sorry, but I can't reproduce the problem that you describe.

Maybe you have some special set-up?

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

[frameworks-plasma] [Bug 385100] Moving window to another activity

[Joel]

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

Joel  changed:

   What|Removed |Added

 CC||joel.porq...@gmail.com

--- Comment #1 from Joel  ---
I've been encountering a similar behavior for a long time (maybe since I've
started using activities but I don't exactly remember). Moving a window from
Activity A to Activity B requires two steps:
- First, move it to All Activities (note that clicking on Activity B in the
menu moves the window to All Activities anyway)
- Second, move it to Activity B

I don't know if https://bugs.kde.org/show_bug.cgi?id=382802 is a duplicate of
this bug too.

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

[Akonadi] [Bug 385532] New: Rebuild of database results in kmail crash and infinte loop

[Axel Braun]

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

Bug ID: 385532
   Summary: Rebuild of database results in kmail crash and infinte
loop
   Product: Akonadi
   Version: 5.6.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

As for whatever reason the search database is messed up again (seems like
akonadi cant deal with frequent suspend/hibernate/wake-up activities), I
decided to go for a rebuild, this time using a postgres backend.

After I deleted ~/.local/share/akonadi and started akonadi again, from what I
saw so far - great. CPU temperatures much lower than under mysql.

But, after some time:

org.kde.pim.kimap: Connection to server lost 3 --> No idea - is this IMAP
resource 3?
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kimap: Connection to server lost 3
org.kde.pim.kimap: Connection to server lost 3
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kimap: Connection to server lost 3
org.kde.pim.kimap: Connection to server lost 3
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kimap: Connection to server lost 3

What does the '3' indicate? IMAP resource 3? Network still up, and I could
access all accounts via webmail

Now starting KMail:

org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "23505"
org.kde.pim.akonadiserver: DB error: "ERROR: duplicate key value violates
unique constraint \"collectiontable_parentandnameindex\"\nDETAIL: Key
(parentid, name)=(7, drafts) already exists.\n(23505)"
org.kde.pim.akonadiserver: Error text: "ERROR: duplicate key value violates
unique constraint \"collectiontable_parentandnameindex\"\nDETAIL: Key
(parentid, name)=(7, drafts) already exists.\n(23505) QPSQL: Es konnte keine
Abfrage erzeugt werden"
org.kde.pim.akonadiserver: Query: "INSERT INTO CollectionTable (remoteId,
remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref,
indexPref, cachePolicyInherit, cachePolicyCheckInterval,
cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts,
isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13,
:14) RETURNING id"
org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable"
"ERROR: duplicate key value violates unique constraint
\"collectiontable_parentandnameindex\"\nDETAIL: Key (parentid, name)=(7,
drafts) already exists.\n(23505) QPSQL: Es konnte keine Abfrage erzeugt werden"
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "23505"
org.kde.pim.akonadiserver: DB error: "ERROR: duplicate key value violates
unique constraint \"collectiontable_parentandnameindex\"\nDETAIL: Key
(parentid, name)=(7, drafts) already exists.\n(23505)"
org.kde.pim.akonadiserver: Error text: "ERROR: duplicate key value violates
unique constraint \"collectiontable_parentandnameindex\"\nDETAIL: Key
(parentid, name)=(7, drafts) already exists.\n(23505) QPSQL: Es konnte keine
Abfrage erzeugt werden"
org.kde.pim.akonadiserver: Query: "INSERT INTO CollectionTable (remoteId,
remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref,
indexPref, cachePolicyInherit, cachePolicyCheckInterval,
cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts,
isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13,
:14) RETURNING id"
org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable"
"ERROR: duplicate key value violates unique constraint
\"collectiontable_parentandnameindex\"\nDETAIL: Key (parentid, name)=(7,
drafts) already exists.\n(23505) QPSQL: Es konnte keine Abfrage erzeugt werden"

...and KMail crashed with this. The error message it was showing:

Im E-Mail-Programm ist ein schwerwiegender Fehler aufgetreten. Das Programm
wird beendet.
Die Fehlermeldung lautet: Could not create collection drafts, resourceId: 16

(Sorry for the german message)

But there is no such resource (16) in ~/.config/akonadi/ 

KMail crashed, but akonadi seems to run. It is issuing always the same
messages, as it looks for the same elements:

org.kde.pim.akonadiserver: processing retrieval request for item (77740) 
parts: ("RFC822")  of resource: "akonadi_maildir_resource_0"
org.kde.pim.akonadiserver: ItemRetrievalJob finished for request 0x7f6102c658d0
, error: ""
org.kde.pim.akonadiserver: posting retrieval request for items (77739)  there
are  0  queues and  0  items in mine
org.kde.pim.akonadiserver: ItemRetrievalJob
Akonadi::Server::ItemRetrievalJob(0x5562b06d97e0) started for request
0x7f6102c7cfe0
org.kde.pim.akonadiserver: processing retrieval request for item (77739) 
parts: ("RFC822")  of resource: "akonadi_maildir_resource_0"
org.kde.pim.akonadiserver: ItemRetrievalJob 

[partitionmanager] [Bug 385525] Entering root password doesn't grant root privs, when launched from kicker

[Eli MacKenzie]

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

Eli MacKenzie  changed:

   What|Removed |Added

 CC||argo...@gmail.com
Version|unspecified |3.1

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

[plasma-browser-integration] [Bug 385531] Visual feedback when download starts

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[plasma-browser-integration] [Bug 385531] New: Visual feedback when download starts

[Matthias]

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

Bug ID: 385531
   Summary: Visual feedback when download starts
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

The current FF 57 shows literally no significant feedback anymore, when a
download starts and I think a OSD notification is nice.

I am fine with a "disabled by default" status. ^^

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

[digikam] [Bug 385467] Cannot Add Or Edit Bookmarks / No plugins loaded

[bugzilla_noreply]

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

--- Comment #10 from caulier.gil...@gmail.com ---
hardy,

Just for info, i fixed the problem of missing plugin with the last 5.8.0 pre
release installer. Please test and report :

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

Gilles Caulier

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

[plasma-browser-integration] [Bug 385530] Error message when I cancel a download manual

[Kai Uwe Broulik]

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

--- Comment #1 from Kai Uwe Broulik  ---
>From what I can tell Firefox' API is identical to Chrome's here [1]. Need to
further investigate.

[1]
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/downloads/InterruptReason

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

[plasma-browser-integration] [Bug 385528] Chrome icon is shown in notification

[Matthias]

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

--- Comment #4 from Matthias  ---
Done: https://bugs.kde.org/show_bug.cgi?id=385530

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

[digikam] [Bug 385368] digiKam causes my machine to blue screen (crash) during installation on Windows 10 while check process in memory

[bugzilla_noreply]

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

--- Comment #13 from caulier.gil...@gmail.com ---
Michael,

I rebuild the windows installer 5.8.0 pre-release :

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

This must fix your problem. Please test and report...

Gilles Caulier

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

[plasma-browser-integration] [Bug 385530] New: Error message when I cancel a download manual

[Matthias]

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

Bug ID: 385530
   Summary: Error message when I cancel a download manual
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Firefox
  Assignee: k...@privat.broulik.de
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 108257
  --> https://bugs.kde.org/attachment.cgi?id=108257=edit
Notifications on manual interuption

I get error messages in FF 57, when I cancel a download. 
You also see a chrome error message, which is another issue.

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

[plasma-browser-integration] [Bug 385517] Wrong icon in downloading notification pop-up

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Kai Uwe Broulik  ---
Confirmed. Currently in main.cpp the application name and icon is hardcoded to
Chrome. Instead it should be set in settings.cpp once the browser identifies
itself to us.

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

[plasma-browser-integration] [Bug 385528] Chrome icon is shown in notification

[Matthias]

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

--- Comment #3 from Matthias  ---
Yes, i manually canceled them.

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

[amarok] [Bug 385529] New: Jamendo plugin doesnt work in Amarok 2.8

[ST]

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

Bug ID: 385529
   Summary: Jamendo plugin doesnt work in Amarok 2.8
   Product: amarok
   Version: 2.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Internet Services
  Assignee: amarok-bugs-d...@kde.org
  Reporter: tomilin.s...@gmail.com
  Target Milestone: 2.9

Created attachment 108256
  --> https://bugs.kde.org/attachment.cgi?id=108256=edit
nothing to select - list empty

Jamendo updating songs in database, but in selection list there is nothing but
Jumendo logo - nothing to select

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

[plasma-browser-integration] [Bug 385528] Chrome icon is shown in notification

[Matthias]

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

Matthias  changed:

   What|Removed |Added

 Attachment #108254|Chrome notifications|Chrome notifications in
description||Firefox for canceled
   ||downloads

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

[plasma-browser-integration] [Bug 385528] Chrome icon is shown in notification

[Matthias]

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

--- Comment #2 from Matthias  ---
Created attachment 108255
  --> https://bugs.kde.org/attachment.cgi?id=108255=edit
successful download

First screenshot shows the notfication about a cancelled screenshot
This second one shows the chrome logo in Firefox 57b4 for a successful
download.

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

[plasma-browser-integration] [Bug 385528] Chrome icon is shown in notification

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #1 from Kai Uwe Broulik  ---
Did you manually cancel those downloads in Firefox? They shouldn't spawn an
error notification in this case. If so, can you please file a bug report about
this :)

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

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

[plasma-browser-integration] [Bug 385517] Wrong icon in downloading notification pop-up

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||shaloksha...@protonmail.ch

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

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

[plasma-browser-integration] [Bug 385528] New: Chrome icon is shown in notification

[Matthias]

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

Bug ID: 385528
   Summary: Chrome icon is shown in notification
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Firefox
  Assignee: k...@privat.broulik.de
  Reporter: shaloksha...@protonmail.ch
  Target Milestone: ---

Created attachment 108254
  --> https://bugs.kde.org/attachment.cgi?id=108254=edit
Chrome notifications

See the screenshot

Firefox 57b4

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

[partitionmanager] [Bug 385525] Entering root password doesn't grant root privs, when launched from kicker

[Jonathan Wakely]

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

--- Comment #4 from Jonathan Wakely  ---
OK thanks

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

[partitionmanager] [Bug 385525] Entering root password doesn't grant root privs, when launched from kicker

[Andrius Štikonas]

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

--- Comment #3 from Andrius Štikonas  ---
Yeah, something is strange. It shouldn't just hang. Maybe try getting some help
from Fedora users. This might be configuration issue, so they might be able to
help more.

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

[partitionmanager] [Bug 385525] Entering root password doesn't grant root privs, when launched from kicker

[Jonathan Wakely]

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

--- Comment #2 from Jonathan Wakely  ---
(In reply to Andrius Štikonas from comment #1)
> Hmm, not sure what is hapenning. Is your kdesu configured to use su or sudo?

I have no idea.

I have no ~/.config/kdesurc file. I used kwriteconfig5 to tell it to use sudo,
and tried to start partitionmanager from kicker again. This time when I entered
my root password and pressed enter the dialog froze, and I had to kill it!
(Close the window, then confirm I wanted to terminate the non-responsive
application).

If I change back to using 'su' I get the original behaviour. So it looks like
using 'sudo' doesn't work either, but fails differently (I guess I need to edit
sudoers to allow it? but it shouldn't just hang).

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

[plasmashell] [Bug 385527] New: plasma crash on sub menu of systray

[Matthias]

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

Bug ID: 385527
   Summary: plasma crash on sub menu of systray
   Product: plasmashell
   Version: 5.10.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: shaloksha...@protonmail.ch
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.12.10-1 x86_64
Distribution: "KaOS"

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

The submenu, which is under the arrow in the systray, got left clicked. 
I saw by the deactivation and activation of Redshift, that plasma crashed and
restarted. 

Then opened this session of Dr. Konqi

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

Thread 8 (Thread 0x6440fa578700 (LWP 825)):
#0  0x6441b63f5eb9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x6441b63b1a18 in  () at /usr/lib/libglib-2.0.so.0
#2  0x6441b63b1c1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x6441bd518bcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x6441bd4c471a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x6441bd2f333b in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x6440fd149377 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x6441bd2f7e7a in  () at /usr/lib/libQt5Core.so.5
#8  0x6441bc1bf254 in start_thread () at /lib/libpthread.so.0
#9  0x6441bcc130ff in clone () at /lib/libc.so.6

Thread 7 (Thread 0x64410d1de700 (LWP 767)):
#0  0x6441bcc09a4d in poll () at /lib/libc.so.6
#1  0x6441b63b1b16 in  () at /usr/lib/libglib-2.0.so.0
#2  0x6441b63b1c1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x6441bd518bcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x6441bd4c471a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x6441bd2f333b in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x6441c03505c2 in  () at /usr/lib/libQt5Quick.so.5
#7  0x6441bd2f7e7a in  () at /usr/lib/libQt5Core.so.5
#8  0x6441bc1bf254 in start_thread () at /lib/libpthread.so.0
#9  0x6441bcc130ff in clone () at /lib/libc.so.6

Thread 6 (Thread 0x64419d946700 (LWP 725)):
#0  0x6441bc1c5473 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x6441c1e11784 in  () at /usr/lib/libQt5Script.so.5
#2  0x6441c1e117c9 in  () at /usr/lib/libQt5Script.so.5
#3  0x6441bc1bf254 in start_thread () at /lib/libpthread.so.0
#4  0x6441bcc130ff in clone () at /lib/libc.so.6

Thread 5 (Thread 0x64419f9a9700 (LWP 724)):
#0  0x6441bcc09a4d in poll () at /lib/libc.so.6
#1  0x6441b63b1b16 in  () at /usr/lib/libglib-2.0.so.0
#2  0x6441b63b1c1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x6441bd518bcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x6441bd4c471a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x6441bd2f333b in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x6441bf9a1955 in  () at /usr/lib/libQt5Qml.so.5
#7  0x6441bd2f7e7a in  () at /usr/lib/libQt5Core.so.5
#8  0x6441bc1bf254 in start_thread () at /lib/libpthread.so.0
#9  0x6441bcc130ff in clone () at /lib/libc.so.6

Thread 4 (Thread 0x6441a5bf4700 (LWP 715)):
#0  0x6441b63f5ed4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x6441b63b16ea in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#2  0x6441b63b1b78 in  () at /usr/lib/libglib-2.0.so.0
#3  0x6441b63b1c1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x6441bd518bcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x6441bd4c471a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x6441bd2f333b in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x6441bf9a1955 in  () at /usr/lib/libQt5Qml.so.5
#8  0x6441bd2f7e7a in  () at /usr/lib/libQt5Core.so.5
#9  0x6441bc1bf254 in start_thread () at /lib/libpthread.so.0
#10 0x6441bcc130ff in clone () at /lib/libc.so.6

Thread 3 (Thread 0x6441a763b700 (LWP 665)):
#0  0x6441bcc09a4d in poll () at /lib/libc.so.6
#1  0x6441b63b1b16 in  () at /usr/lib/libglib-2.0.so.0
#2  0x6441b63b1c1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x6441bd518bcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x6441bd4c471a in
QEventLoop::exec(QFlags) () at

[krita] [Bug 385519] Colors are displayed inverted when using ANGLE

[Alvin Wong]

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

--- Comment #4 from Alvin Wong  ---
The info does point towards the Parallels D3D driver, but I'm not certain. It
could also be an issue with the version of ANGLE that Qt 5.9.1 uses. (And
unlikely but still possible that I might've missed something when I wrote the
code...) Theoretically I can compile a test program to get a bit more data and
report a bug to upstream, but I don't have the energy for that now.

There is another report of this issue, but I haven't got any info on their
system, could be the same case.

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

[partitionmanager] [Bug 385525] Entering root password doesn't grant root privs, when launched from kicker

[Andrius Štikonas]

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

--- Comment #1 from Andrius Štikonas  ---
Hmm, not sure what is hapenning. Is your kdesu configured to use su or sudo?

In principle we want to move away from running KPM as root. kdesu is obsolete.
But porting to KAuth/Polkit will take time, as quite a lot of refactoring is
needed (e.g. need to port away from libparted). Once KPM runs rootless, this
should resolve anyway...

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

[kmail2] [Bug 385526] New: recent changes broke multipart display

[Martin Koller]

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

Bug ID: 385526
   Summary: recent changes broke multipart display
   Product: kmail2
   Version: Git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kol...@aon.at
  Target Milestone: ---

Created attachment 108253
  --> https://bugs.kde.org/attachment.cgi?id=108253=edit
test mail not showing html

I just updated to git master (previous version was from about 2-3 weeks ago).
Now multipart/alternative mails no longer show the HTML content.
In fact no body is shown at all and kmail says in the side-bar label "No HTML
Message"

Example mail attached.

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

[partitionmanager] [Bug 385524] Meaning of "Recreate existing file system" is unclear

[Jonathan Wakely]

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

--- Comment #4 from Jonathan Wakely  ---
Thanks!

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

[plasmashell] [Bug 385498] Kickoff doesn't show root menu items

[bugzilla_noreply]

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

--- Comment #1 from magis...@gmail.com ---
Same issue on OpenSUSE Tumbleweed 20171007, Plasma 5.10.5, Frameworks 5.38. Any
ideas?

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

[user-manager] [Bug 373558] Allowed User Names are Limited

[Eli MacKenzie]

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

Eli MacKenzie  changed:

   What|Removed |Added

 CC||argo...@gmail.com

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

[partitionmanager] [Bug 385525] New: Entering root password doesn't grant root privs, when launched from kicker

[Jonathan Wakely]

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

Bug ID: 385525
   Summary: Entering root password doesn't grant root privs, when
launched from kicker
   Product: partitionmanager
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: zi...@kayari.org
  Target Milestone: ---

kde-partitionmanager-3.1.2-1.fc26.x86_64

If I run KPM from the kicker menu as a normal user and enter the root password
when prompted, it doesn't get root privs.

I start paritionmanager form the kicker menu, which creates a prompt:

  The action you requested needs root privileges. Please enter root's password
  below, or click Ignore to continue with your current privileges.

  Command: KDE_FULL_SESSION=true XDG_RUNTIME_DIR=/run/user/1001
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus partitionmanager
  --dontsu

After entering the root password (and clicking OK, or pressing Enter) I get
another prompt, saying "Warning: You do not have adminstrative privileges. It
is possible to run KDE Partition Manager without these privileges. You will,
however, ..."

i.e. it makes no difference whether I enter the root password or choose
"Ignore", it always proceeds without root privs. If I choose to continue then I
get a crash that drkonqi tells me is a dup of Bug 383636. But I don't really
want to continue without root privs, I want entering the password to work.

If I run partitionmanager from the terminal, as a normal user, I get prompted
for the root password and it works properly, starting the application with root
privs. So the problem is only when run from the kicker menu.

When the prompt for the root password appears, the journal shows:


Oct 09 18:43:41 wraith.home kdesu[7938]: No X authentication info set for
display ":0"
Oct 09 18:43:42 wraith.home kdesu[7938]: No X authentication info set for
display ":0"


After I enter the root password I see:

Oct 09 18:43:51 wraith.home audit[7948]: USER_AUTH pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su"
hostname=wraith.home addr=? terminal=pts/13 res=success'
Oct 09 18:43:51 wraith.home audit[7948]: USER_ACCT pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="root"
exe="/usr/bin/su" hostname=wraith.home addr=? terminal=pts/13 res=success'
Oct 09 18:43:51 wraith.home audit[7948]: CRED_ACQ pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su"
hostname=wraith.home addr=? terminal=pts/13 res=success'
Oct 09 18:43:51 wraith.home su[7948]: (to root) jwakely on pts/13
Oct 09 18:43:51 wraith.home su[7948]: pam_systemd(su:session): Cannot create
session: Already running in a session
Oct 09 18:43:51 wraith.home su[7948]: pam_unix(su:session): session opened for
user root by (uid=1000)
Oct 09 18:43:51 wraith.home audit[7948]: USER_START pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="root" exe="/usr/bin/su" hostname=wraith.home addr=? terminal=pts/13
res=success'
Oct 09 18:43:51 wraith.home su[7948]: pam_unix(su:session): session closed for
user root
Oct 09 18:43:51 wraith.home audit[7948]: USER_END pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="root" exe="/usr/bin/su" hostname=wraith.home addr=? terminal=pts/13
res=success'
Oct 09 18:43:51 wraith.home audit[7948]: CRED_DISP pid=7948 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su"
hostname=wraith.home addr=? terminal=pts/13 res=success'
Oct 09 18:43:51 wraith.home kwin_x11[2011]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 7871, resource id: 104857615, major code: 18
(ChangeProperty), minor code: 0
Oct 09 18:43:51 wraith.home kdesu[7938]: No X authentication info set for
display ":0"
Oct 09 18:43:51 wraith.home audit[7955]: USER_AUTH pid=7955 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su"
hostname=wraith.home addr=? terminal=pts/13 res=success'
Oct 09 18:43:51 wraith.home audit[7955]: USER_ACCT pid=7955 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="root"
exe="/usr/bin/su" hostname=wraith.home addr=? 

[plasmashell] [Bug 385522] Present Windows: Do not hardcode brightness on presentwindows.cpp

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
Why shouldn't the brightness be hardcoded? Are you seeing some visual glitches
with any windows or something?

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

[Discover] [Bug 385482] Discover crashes immediately when scrolling through Games section with down arrow key

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
I also use Kubuntu 17.04 as my primary OS. Unfortunately the version of
Discover packaged with Kubnutu 17.04 is super rough and buggy. Frankly it's not
worth using at all, and most of the bugs you're likely to encounter have
already been fixed in newer versions that aren't available directly in Kubuntu
17.04 yet.

If you're feeling a bit adventurous, you can update to newer versions of KDE
software (which includes Discover) by adding the backports PPA to your system:
https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports

Executing the following commands should do it:
  sudo add-apt-repository ppa:kubuntu-ppa/backports
  sudo apt update

Then you can do the following to update to a newer version of Discover
  sudo apt install plasma-discover

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

[partitionmanager] [Bug 385524] Meaning of "Recreate existing file system" is unclear

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/par
   ||titionmanager/f30a3c999f225
   ||4521eda1a570ae3bfbf17081916
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andrius Štikonas  ---
Git commit f30a3c999f2254521eda1a570ae3bfbf17081916 by Andrius Štikonas.
Committed on 09/10/2017 at 17:42.
Pushed by stikonas into branch 'master'.

Add what's it entry to Recreate Existing File System checkbox.

M  +6-4src/gui/partpropswidgetbase.ui

https://commits.kde.org/partitionmanager/f30a3c999f2254521eda1a570ae3bfbf17081916

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

[Discover] [Bug 385482] Discover crashes immediately when scrolling through Games section with down arrow key

[david . m . greene]

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

--- Comment #2 from david.m.gre...@gmail.com  ---
> Hey, can you provide a backtrace? Also I'd need some more information,
> for example what Discover version are you using.
I can produce a backtrace eventually, but it will be a while before I get back
to the laptop where the problem occurred.  I'll check tonight on my own laptop
and see if the same crash happens there.

This is a first foray back into Linux for me after a gap of a few years, so
please don't expect any kind of expertise.

The version of Discover is whatever is packaged with the 64-bit Kubuntu 17.04
download (from https://kubuntu.org/getkubuntu/ ) -- I'll look and send an
update tonight.

I used the Universal Installer recommended here --

https://www.pendrivelinux.com/put-kubuntu-10-04-on-a-flash-drive-using-windows/

to put a Live CD-equivalent copy of Kubuntu on a USB drive.  It seemed to work
fine.  After a reboot, Kubuntu was running on the laptop with no apparent
errors.

I immediately tried to use Discover to look at what software packages are
available.  I didn't have a mouse-with-wheel plugged in, so I tried the down
arrow key as an alternative to scrolling with the track pad.  This worked fine
in some categories.  But in the Games and Graphics categories, Discover
immediately crashed.

I've done absolutely nothing else with Kubuntu yet.

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

[partitionmanager] [Bug 385524] Meaning of "Recreate existing file system" is unclear

[Jonathan Wakely]

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

--- Comment #2 from Jonathan Wakely  ---
Yes, I think saying reformat is clearer, but it would be fine if the help entry
just said "This will reformat the filesystem, losing all data, but keeping the
same filesystem type and options".

I see that once you select the checkbox you get a helpful dialog that warns you
it will destroy data, which is good (I'm not sure why I didn't see that last
time).

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

[dolphin] [Bug 385523] Link current location into the "places"

[Paul]

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

Paul  changed:

   What|Removed |Added

 CC||pip@gmx.com

--- Comment #1 from Paul  ---
The location bar, which can be found above Dolphin's view, displays the path to
the current folder, when this is in "Editable Mode" you can drag the folder
icon to the "Places Panel" to achieve what you require.

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

[partitionmanager] [Bug 385524] Meaning of "Recreate existing file system" is unclear

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

Version|unspecified |3.0

--- Comment #1 from Andrius Štikonas  ---
Hmm, do you think the label itself should be changed too? Like "Reformat
existing file system".

Any suggestions for help entries?

Typically it is indeed done using mkfs command.

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

[krita] [Bug 385519] Colors are displayed inverted when using ANGLE

[bugzilla_noreply]

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

--- Comment #3 from nestorantonio@gmail.com ---
You're right,  it could be a problem caused by parallels graphic driver.
Let me know if you need more information, or if there's something I could
help you with.

On Mon, Oct 9, 2017 at 1:16 PM, Nestor Antonio Zambrano <
nestorantonio@gmail.com> wrote:

>
> Hello Alvin, sure.
>  This is the output:
>
> 
>
> Krita
>   Version: 3.3.0
>
> OS Information
>   Build ABI: x86_64-little_endian-llp64
>   Build CPU: x86_64
>   CPU: x86_64
>   Kernel Type: winnt
>   Kernel Version: 6.1.7601
>   Pretty Productname: Windows 7 SP 1 (6.1)
>   Product Type: windows
>   Product Version: 7sp1
>
> OpenGL Info
>   Vendor:  Google Inc.
>   Renderer:  "ANGLE (Parallels Display Adapter (WDDM) Direct3D11 vs_4_1
> ps_4_1)"
>   Version:  "OpenGL ES 3.0 (ANGLE 2.1.0.8613f4946861)"
>   Shading language:  OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.8613f4946861)
>   Requested format:  QSurfaceFormat(version 3.0, options
> QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
> -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
>  QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
>   Current format:QSurfaceFormat(version 3.0, options
> QFlags(), depthBufferSize 24, redBufferSize
> 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
> stencilBufferSize 8, samples 0, swapBehavior 
> QSurfaceFormat::SwapBehavior(DefaultSwapBehavior),
> swapInterval 0, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile))
>  Version: 3.0
>  Supports deprecated functions false
>  is OpenGL ES: true
>
> QPA OpenGL Detection Info
>   supportsDesktopGL: true
>   supportsAngleD3D11: true
>   isQtPreferAngle: false
>   overridePreferAngle: false
> == log ==
>  createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
> QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
> -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
>  QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
> Basic wglCreateContext gives version 2.0
> OpenGL 2.0 entry points available
> GPU features: QSet()
> supportedRenderers GpuDescription(vendorId=0x1ab8, deviceId=0x4005,
> subSysId=0x4001ab8, revision=0, driver: "prl_umdd.dll",
> version=8.15.10.32581, "Parallels Display Adapter (WDDM)") renderer:
>  QFlags(0x1|0x2|0x4|0x8|0x20)
> Qt: Using WGL and OpenGL from "opengl32.dll"
> create OpenGL: "Parallels and Intel Inc.","Parallels using Intel Iris
> OpenGL Engine" default ContextFormat: v2.1 profile: QSurfaceFormat::
> OpenGLContextProfile(NoProfile) options: QFlags FormatOption>(DeprecatedFunctions),SampleBuffers
> Extensions: 105
> QWindowsGLContext 0x2cb9890 GDI  requested:  QSurfaceFormat(version 3.0,
> options QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
> -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
>  QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
> obtained # 8 GDI QSurfaceFormat(version 2.1, options
> QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
> alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile
>  QSurfaceFormat::OpenGLContextProfile(NoProfile))
>  PIXELFORMATDESCRIPTOR dwFlags=0x8425 PFD_DRAW_TO_WINDOW
> PFD_SUPPORT_OPENGL PFD_SUPPORT_COMPOSITION PFD_DOUBLEBUFFER iPixelType=0
> cColorBits=32 cRedBits=8 cRedShift=16 cGreenBits=8 cGreenShift=8
> cBlueBits=8 cBlueShift=0 cDepthBits=24 cStencilBits=8 iLayerType=0
> dwVisibleMask=65535 cAlphaBits=8 cAlphaShift=24 cAccumBits=64
> cAccumRedBits=16 cAccumGreenBits=16 cAccumBlueBits=16 cAccumAlphaBits=16
>  swap interval:  1
> default:  ContextFormat: v2.1 profile: QSurfaceFormat::
> OpenGLContextProfile(NoProfile) options: QFlags FormatOption>(DeprecatedFunctions)
> HGLRC= 0x3
> createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
> QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
> -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
>  QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
> QWindowsGLContext 0x2cb9930 GDI  requested:  QSurfaceFormat(version 3.0,
> options QFlags(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
> -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
>  

[krita] [Bug 385519] Colors are displayed inverted when using ANGLE

[bugzilla_noreply]

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

--- Comment #2 from nestorantonio@gmail.com ---
Hello Alvin, sure.
 This is the output:



Krita
  Version: 3.3.0

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.1.7601
  Pretty Productname: Windows 7 SP 1 (6.1)
  Product Type: windows
  Product Version: 7sp1

OpenGL Info
  Vendor:  Google Inc.
  Renderer:  "ANGLE (Parallels Display Adapter (WDDM) Direct3D11 vs_4_1
ps_4_1)"
  Version:  "OpenGL ES 3.0 (ANGLE 2.1.0.8613f4946861)"
  Shading language:  OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.8613f4946861)
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize
24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
  Current format:QSurfaceFormat(version 3.0, options
QFlags(), depthBufferSize 24, redBufferSize
8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples 0, swapBehavior
QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(NoProfile))
 Version: 3.0
 Supports deprecated functions false
 is OpenGL ES: true

QPA OpenGL Detection Info
  supportsDesktopGL: true
  supportsAngleD3D11: true
  isQtPreferAngle: false
  overridePreferAngle: false
== log ==
 createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize
24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Basic wglCreateContext gives version 2.0
OpenGL 2.0 entry points available
GPU features: QSet()
supportedRenderers GpuDescription(vendorId=0x1ab8, deviceId=0x4005,
subSysId=0x4001ab8, revision=0, driver: "prl_umdd.dll",
version=8.15.10.32581, "Parallels Display Adapter (WDDM)") renderer:
 QFlags(0x1|0x2|0x4|0x8|0x20)
Qt: Using WGL and OpenGL from "opengl32.dll"
create OpenGL: "Parallels and Intel Inc.","Parallels using Intel Iris
OpenGL Engine" default ContextFormat: v2.1 profile:
QSurfaceFormat::OpenGLContextProfile(NoProfile) options:
QFlags(DeprecatedFunctions),SampleBuffers
Extensions: 105
QWindowsGLContext 0x2cb9890 GDI  requested:  QSurfaceFormat(version 3.0,
options QFlags(DeprecatedFunctions),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
-1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
obtained # 8 GDI QSurfaceFormat(version 2.1, options
QFlags(DeprecatedFunctions), depthBufferSize
24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize
8, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile
 QSurfaceFormat::OpenGLContextProfile(NoProfile))
 PIXELFORMATDESCRIPTOR dwFlags=0x8425 PFD_DRAW_TO_WINDOW
PFD_SUPPORT_OPENGL PFD_SUPPORT_COMPOSITION PFD_DOUBLEBUFFER iPixelType=0
cColorBits=32 cRedBits=8 cRedShift=16 cGreenBits=8 cGreenShift=8
cBlueBits=8 cBlueShift=0 cDepthBits=24 cStencilBits=8 iLayerType=0
dwVisibleMask=65535 cAlphaBits=8 cAlphaShift=24 cAccumBits=64
cAccumRedBits=16 cAccumGreenBits=16 cAccumBlueBits=16 cAccumAlphaBits=16
 swap interval:  1
default:  ContextFormat: v2.1 profile:
QSurfaceFormat::OpenGLContextProfile(NoProfile) options:
QFlags(DeprecatedFunctions)
HGLRC= 0x3
createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize
24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
QWindowsGLContext 0x2cb9930 GDI  requested:  QSurfaceFormat(version 3.0,
options QFlags(DeprecatedFunctions),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
-1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile
 QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
obtained # 8 GDI QSurfaceFormat(version 2.1, options
QFlags(DeprecatedFunctions), depthBufferSize
24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize
8, stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile
 QSurfaceFormat::OpenGLContextProfile(NoProfile))
 PIXELFORMATDESCRIPTOR dwFlags=0x8425 PFD_DRAW_TO_WINDOW
PFD_SUPPORT_OPENGL 

[partitionmanager] [Bug 385524] New: Meaning of "Recreate existing file system" is unclear

[Jonathan Wakely]

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

Bug ID: 385524
   Summary: Meaning of "Recreate existing file system" is unclear
   Product: partitionmanager
   Version: unspecified
  Platform: Fedora RPMs
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: zi...@kayari.org
  Target Milestone: ---

I'm using kde-partitionmanager-3.1.2-1.fc26.x86_64 but I can't choose 3.1 in
the  Version field of this Bugzilla.

The label isn't really clear about exactly what the checkbox does, and
"recreate" doesn't necessarily mean "reformat". This has confused at least one
person before (see Bug 249818 which comes up in a web search for the label
text).

It is possible to interpret "recreate existing file system" to mean the
existing data is somehow preserved, which is definitely wrong.

The '?' help button in the window decorations doesn't have any info on the
checkbox. The handbook isn't very illuminating either (although does at least
say it destroys all existing data).

Would it be possible to improve the handbook, and add a help button entry?

It should make it clear that it formats the filesystem (N.B. it's "filesystem"
not "file system") i.e. creates a new filesystem of the same type, which
destroys existing data. If this is just done using mkfs.* then it might even be
useful to say something like "this is typically done using a mkfs command".

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

[dolphin] [Bug 385523] New: Link current location into the "places"

[Victor Porton]

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

Bug ID: 385523
   Summary: Link current location into the "places"
   Product: dolphin
   Version: 16.08.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: por...@narod.ru
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Please make it easy to store the current location in "places".

For instance, you can make a draggable icon near the address bar, which could
be dragged into places. And/or you can make a button "Add to places".

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

[frameworks-knewstuff] [Bug 385516] Loading Preview icon stuck

[Jasem Mutlaq]

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

--- Comment #1 from Jasem Mutlaq  ---
Created attachment 108250
  --> https://bugs.kde.org/attachment.cgi?id=108250=edit
Log file

Result from this:

QT_LOGGING_RULES="org.kde.knewstuff*=true" kstars

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

[kig] [Bug 360153] select among superposed objects as macro argument

[David E . Narvaez]

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

--- Comment #1 from David E. Narvaez  ---
Git commit f40deaf0c6f4256d2314f285773da23ab4a22920 by David E. Narváez.
Committed on 09/10/2017 at 14:36.
Pushed by narvaez into branch 'master'.

Check the ObjectHolder Pointer is Valid

One can get a null pointer from selecting two superimposed objects
(Shift + Left Click) and then canceling the popup menu by clicking
somewhere else.

M  +1-1modes/macro.cc

https://commits.kde.org/kig/f40deaf0c6f4256d2314f285773da23ab4a22920

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

[kig] [Bug 282916] Kig should abort a construction when right mouse is pressed

[David E . Narvaez]

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

--- Comment #2 from David E. Narvaez  ---
Git commit 27ac86d299d73dd1ae92d6b9f7c819515d6d6082 by David E. Narváez.
Committed on 09/10/2017 at 10:19.
Pushed by narvaez into branch 'master'.

Cancel Point Construction with Right-Click

This should have been part of 01eb87, but I guess the real thing to
evaluate is why doesn't PointConstructMode inherit BaseConstructMode.

M  +1-1modes/construct_mode.cc

https://commits.kde.org/kig/27ac86d299d73dd1ae92d6b9f7c819515d6d6082

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