[gwenview] [Bug 345980] File name and other info lost from titlebar after image modification

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
  Latest Commit||https://commits.kde.org/gwe
   ||nview/5a7d105ae9dead6214953
   ||bfcb3f184c0399be42b
 Resolution|--- |FIXED

--- Comment #7 from Henrik Fehlauer  ---
Git commit 5a7d105ae9dead6214953bfcb3f184c0399be42b by Henrik Fehlauer, on
behalf of Peter Mühlenpfordt.
Committed on 17/12/2017 at 07:25.
Pushed by rkflx into branch 'Applications/17.12'.

Update titlebar after image modification

Summary:
In some cases the titlebar information (filename, size, zoom) is lost after an
image has been modified.
This patch fixes the caption update and thereby also the missing `*` on
modified images.

Test Plan:
Case 1:
1. Open image in view mode, which fits in window (100% zoom)
2. Scale (Shift-R) or crop (Shift-C) image
-> Titlebar info is lost

Case 2:
1. Open big image in view mode, which is zoomed to fit in window
2. Scale image with Shift-R (do not save)
3. Go to another big image (zoomed to fit)
3. Scale image with Shift-R
-> Titlebar info is lost

Reviewers: rkflx

Reviewed By: rkflx

Subscribers: ngraham

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

M  +9-6app/mainwindow.cpp
M  +1-0app/mainwindow.h

https://commits.kde.org/gwenview/5a7d105ae9dead6214953bfcb3f184c0399be42b

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

[plasmashell] [Bug 387982] Artifacts when resuming from suspend

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

   Assignee|kwin-bugs-n...@kde.org  |k...@davidedmundson.co.uk
  Component|general |general
 CC||plasma-b...@kde.org
   Target Milestone|--- |1.0
Product|kwin|plasmashell

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

[digikam] [Bug 387976] Remember aspect ratio

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
Yes, the problem is also fixed with non-default aspect ratio. Keep in mind,
however, that the tool's setting will save the settings depending on the
orientation of the image.

Maik

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

[digikam] [Bug 387976] Remember aspect ratio

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Some fixes have been introduced in this tool with next 5.8.0. Please test with
current pre release bundle if the problem is reproducible :

https://files.kde.org/digikam/

Gilles Caulier

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

[digikam] [Bug 387975] Just after ugrade to 5.7.0 version, none pictures are shown

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.8.0
 CC||caulier.gil...@gmail.com
  Component|general |Database-Albums
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---
This due to update to Qt 5.9.3. 

This problem is solved in next DK 5.8.0 planed for next week.

Turn around : use current Linux AppImage bundle instead system based
application :

https://files.kde.org/digikam/

Gilles Caulier

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

[digikam] [Bug 387977] No icon only view of "Extras sidebar": sidebar taking up a lot of space

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|ImageEditor |Usability-Ergonomy

--- Comment #1 from caulier.gil...@gmail.com ---
This is typically a problem with i18n. All icon item strings in this view come
from menu and must be translated shortly. 

Try to switch in English to see the difference.

Note : i'm not agree to be able to switch the view in icon only mode. The view
must be explicit.

Gilles Caulier

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

[digikam] [Bug 277502] All versions of version set always displayed in Album view

[bugzilla_noreply]

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

--- Comment #17 from caulier.gil...@gmail.com ---
Please check if with currrent 5.8.0 pre release bundle the problem is
reproducible :

https://files.kde.org/digikam/

Gilles Caulier

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

[digikam] [Bug 277502] All versions of version set always displayed in Album view

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|2.0.0   |5.4.0
   Version Fixed In|2.0.0   |

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

[digikam] [Bug 387960] Failed build Calendar tool with kcalcore 17.12

[bugzilla_noreply]

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

--- Comment #5 from caulier.gil...@gmail.com ---
next week

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

[kmail2] [Bug 378315] KMail crash on logout

[bugzilla_noreply]

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

patrickrif...@yandex.com changed:

   What|Removed |Added

 CC||patrickrif...@yandex.com

--- Comment #18 from patrickrif...@yandex.com ---
I can confirm that with Qt 5.10.0 the issues does indeed appear to be resolved.
Current system is:
OS: Arch Linux x64
KDE Plasma Version: 5.11.4
KDE Frameworks Version: 5.41.0
KMail Version: 5.6.3

I have also tested this on two other systems with the same specifications as
above.

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

[frameworks-kxmlgui] [Bug 337491] KDEPlatformTheme plugin causes text artifacts in Qt 5 application

[michael]

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

michael  changed:

   What|Removed |Added

 CC||reeves...@gmail.com

--- Comment #28 from michael  ---
Just confirmed this behavior breaks custom actions in QGit 3.7.

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

[kinfocenter] [Bug 387479] wayland: kinfocenter still crashing when clicking on Graphical Information

[bugzilla_noreply]

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

amirs...@gmail.com changed:

   What|Removed |Added

 CC||amirs...@gmail.com

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

[kinfocenter] [Bug 387479] wayland: kinfocenter still crashing when clicking on Graphical Information

[bugzilla_noreply]

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

--- Comment #2 from amirs...@gmail.com ---
Created attachment 109425
  --> https://bugs.kde.org/attachment.cgi?id=109425=edit
New crash information added by DrKonqi

kinfocenter (5.11.4) using Qt 5.10.0

- What I was doing when the application crashed:

- Custom settings of the application:
Running on archlinux synced and updated on intel hardware.

-- Backtrace (Reduced):
#6  0x7f34cc98d7e7 in wl_proxy_destroy () from
/usr/lib/libwayland-client.so.0
#7  0x7f34cb0fa606 in KWayland::Client::Registry::release() () from
/usr/lib/libKF5WaylandClient.so.5
#8  0x7f34cb0fa62f in KWayland::Client::Registry::~Registry() () from
/usr/lib/libKF5WaylandClient.so.5
#9  0x7f34cb0fa71a in KWayland::Client::Registry::~Registry() () from
/usr/lib/libKF5WaylandClient.so.5
#10 0x7f34da0a254d in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5

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

[kwin] [Bug 387982] Artifacts when resuming from suspend

[Isaac]

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

Isaac  changed:

   What|Removed |Added

 CC||isaacalich8...@gmail.com

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

[kwin] [Bug 387982] New: Artifacts when resuming from suspend

[Isaac]

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

Bug ID: 387982
   Summary: Artifacts when resuming from suspend
   Product: kwin
   Version: 5.11.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: isaacalich8...@gmail.com
  Target Milestone: ---

Created attachment 109424
  --> https://bugs.kde.org/attachment.cgi?id=109424=edit
Picture of artifacts

When going into suspend on Plasma 5.11.4 and resuming, I've been getting
strange artifacts in Latte Dock and my desktop icons that are resolved when
wiggling them with the mouse cursor a bit, or hovering over the dock icons. It
does not seem to be compositor render type specific.

Using Manjaro Linux KDE & NVIDIA Proprietary drivers.

Apologies if I posted this in the wrong place, I'm pretty sure it's an issue
with the compositor though.

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

[kstars] [Bug 387981] Summary Capture screen is not incrementing the capture progress count

[Paul]

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

--- Comment #1 from Paul  ---
Created attachment 109423
  --> https://bugs.kde.org/attachment.cgi?id=109423=edit
Showing the progress from the capture module

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

[kstars] [Bug 387981] New: Summary Capture screen is not incrementing the capture progress count

[Paul]

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

Bug ID: 387981
   Summary: Summary Capture screen is not incrementing the capture
progress count
   Product: kstars
   Version: 2.8.9
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: phome...@bigpond.net.au
  Target Milestone: ---

Created attachment 109422
  --> https://bugs.kde.org/attachment.cgi?id=109422=edit
Hightlighting the progress counter

I have a single job running from the capture module to take darks and it
correctly updates the summary page for everything but the progress counter.

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

[plasmashell] [Bug 387980] New: Plasma crash while closing dolphin

[Voni]

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

Bug ID: 387980
   Summary: Plasma crash while closing dolphin
   Product: plasmashell
   Version: 5.9.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: marme...@web.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-42-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
- What I was doing when the application crashed:
I closed one of some dolphin instances, which (if i remember right) had open a
directory of an nfs4 mount.

The crash can be reproduced sometimes.

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

Thread 21 (Thread 0x7f115d6f1700 (LWP 4820)):
#0  0x7f1279470510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f127a5d8aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f127e0bf495 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f127e0bfd8a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f127a5d7c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f127946a6da in start_thread (arg=0x7f115d6f1700) at
pthread_create.c:456
#6  0x7f1279ee3d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 20 (Thread 0x7f115e6f2700 (LWP 4819)):
#0  0x7f1279ed38ad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f12720d5073 in  () at
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.90
#2  0x7f1274a11b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f12749cd042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f12749cd514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f12749cd68c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f127a7fb0bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f127a7a4bea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f127a5d2f83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f127d4bddf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f127a5d7c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f127946a6da in start_thread (arg=0x7f115e6f2700) at
pthread_create.c:456
#12 0x7f1279ee3d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7f1172592700 (LWP 4316)):
#0  0x7f1279470510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f127a5d8aeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f127e0bf495 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f127e0bfd8a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f127a5d7c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f127946a6da in start_thread (arg=0x7f1172592700) at
pthread_create.c:456
#6  0x7f1279ee3d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7f1170b82700 (LWP 4221)):
#0  0x7f1279ed7d8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f126e0e4df1 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f126e0d6601 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f126e0d6c9e in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f126e0d6d50 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f126e0e4d39 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f126d3247d8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#7  0x7f127946a6da in start_thread (arg=0x7f1170b82700) at
pthread_create.c:456
#8  0x7f1279ee3d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f115f7fa700 (LWP 4210)):
#0  0x7f1274a12ed9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f12749cd532 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f12749cd68c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f127a7fb0bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f127a7a4bea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f127a5d2f83 in 

[kactivitymanagerd] [Bug 387979] New: Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd

[Ivan Bordoni]

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

Bug ID: 387979
   Summary: Plasmashell and latte dock crashes due abnormal
behavior of kactivitymanagerd
   Product: kactivitymanagerd
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: ivan.m...@fastwebnet.it
CC: plasma-b...@kde.org
  Target Milestone: ---

Hi Guys
https://user-images.githubusercontent.com/24593950/33776466-c067c948-dc41-11e7-88cc-fb6dc88b92e0.png

After the log-in I found plasma with the docks that show themselves and hide in
an endless loop
and there is no way to normalize the situation even by restarting the laptop
please follow the discussion about the issue
https://github.com/psifidotos/Latte-Dock/issues/798

Now I find myself with unstable plasmashell how can I do to fix the activity
daemon?
For this, is there the possibility to delete some configuration files?
in that case, I guess, do I have to re-create all the activities from scratch
or can I repair any corrupt file?

regards,
Ivan

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

[k3b] [Bug 382776] Enable "apply" button only when some setting is changed

[Leslie Zhai]

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

--- Comment #7 from Leslie Zhai  ---
(In reply to Nate Graham from comment #6)
> Sorry, I'm afraid I can't contribute much to K3b as I don't have any
> hardware with a disc drive.

Never mind :) I don't have any hardware neither but use CDEmu instead
https://www.leetcode.cn/2016/08/k3b.html#test

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

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

[Leslie Zhai]

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

--- Comment #12 from Leslie Zhai  ---
(In reply to Nate Graham from comment #11)
> Also, Leslie, if K3b is distributed through KDE Applications, then you
> should work with the release team to write the release notes for each
> release.

Thanks for your advise! but I don't have received notification email or should
I follow which mailinglist?

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

[kleopatra] [Bug 387978] First time use Key generation Error

[John McMahon]

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

--- Comment #1 from John McMahon  ---
First-time installation of Kleopatra on HP Pavillion laptop. Entered info into
fields and completed passphrase field. Next box told me it could take some time
to generate a key pair. But an error box appeared very quickly afterward that a
general error occurred creating the key pair. I tried Changin info, even
different passphrases were tried but to no avail.

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

[digikam] [Bug 277502] All versions of version set always displayed in Album view

[bugzilla_noreply]

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

s.pfei...@posteo.de changed:

   What|Removed |Added

 CC||s.pfei...@posteo.de

--- Comment #16 from s.pfei...@posteo.de ---
Any updates on this? The album view gets cluttered pretty quickly if you edit
your photos a lot with versioning.

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

[kleopatra] [Bug 387978] New: First time use Key generation Error

[John McMahon]

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

Bug ID: 387978
   Summary: First time use Key generation Error
   Product: kleopatra
   Version: 3.0.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: monty...@hotmail.com
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

Initial installation of Kleopatra 3.0.2 on Win 10 HP Pavillion laptop. Tried to
generate new key pair. After entering parameters and completing passphrase. The
error is generated no matter the length nor content of Passphrase. The message
says this could take time to complete but very soon after passphrase is entered
the error occurs.
Box presented says general error and not much more. Tried different data
combinations for the key generation but nothing changed, the error or the
quickness of error notification.

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

[digikam] [Bug 387977] New: No icon only view of "Extras sidebar": sidebar taking up a lot of space

[bugzilla_noreply]

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

Bug ID: 387977
   Summary: No icon only view of "Extras sidebar": sidebar taking
up a lot of space
   Product: digikam
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: ImageEditor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: s.pfei...@posteo.de
  Target Milestone: ---

Created attachment 109421
  --> https://bugs.kde.org/attachment.cgi?id=109421=edit
Extras Sidebar

The "Extras"-Sidebar has no icon-only view, very large padding and no way to
further narrow the sidebar so that there is a huge waste of space. See
attachment.

I would like to see an icon-only sidebar if possible.

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

[digikam] [Bug 387976] New: Remember aspect ratio

[bugzilla_noreply]

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

Bug ID: 387976
   Summary: Remember aspect ratio
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: ImageEditor-Tool-Crop
  Assignee: digikam-bugs-n...@kde.org
  Reporter: s.pfei...@posteo.de
  Target Milestone: ---

Once I select another, non-default aspect ratio, undo my crop and then crop
again with a different selection I will have to to select my non-default aspect
ratio again. Would be helping to have that saved on a per-photo basis if
possible.

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

[print-manager] [Bug 377498] Add a new printer and set to to default requires root password multiple times

[bugzilla_noreply]

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

s.pfei...@posteo.de changed:

   What|Removed |Added

 CC||s.pfei...@posteo.de

--- Comment #1 from s.pfei...@posteo.de ---
I'm seeing this on Opensuse Leap 42.3.

Seems to be restricted to Opensuse?

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

[frameworks-syntax-highlighting] [Bug 387705] Highlight PKGBUILD files as bash files

[Ashark]

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

--- Comment #8 from Ashark  ---
Dominik Haumann, great! Thanks for perfect suggestion.

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

[digikam] [Bug 387960] Failed build Calendar tool with kcalcore 17.12

[younker . dl]

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

--- Comment #4 from younker...@gmail.com  ---
(In reply to caulier.gilles from comment #3)
> No problem to build digiKam 5.8.0 with libkalcore 17.12 under Linux
> 
> Gilles Caulier

when will 5.8.0 will be officially released?

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

[kscreenlocker] [Bug 387972] Power management suppressing prevents screen from locking

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
Not sure what we can do here. We generally trust the browser, and coming up
with a list of exceptions doesn't seem sustainable.

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

[digikam] [Bug 387975] Just after ugrade to 5.7.0 version, none pictures are shown

[Floreal]

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

Floreal  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages

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

[digikam] [Bug 387975] Just after ugrade to 5.7.0 version, none pictures are shown

[Floreal]

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

Floreal  changed:

   What|Removed |Added

   Severity|normal  |critical

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

[digikam] [Bug 387975] New: Just after ugrade to 5.7.0 version, none pictures are shown

[Floreal]

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

Bug ID: 387975
   Summary: Just after ugrade to 5.7.0 version, none pictures are
shown
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: floreal@flo-art.fr
  Target Milestone: ---

I upgraded digikam from 5.6 to 5.7.0.

When I open it, there is no pictures shown. If I select show subfolders in
album, all pictures of the library are shown, independently of what folder I
select in the sidebar.

I'm on KDE Neon (user edition) with plasma 5.11.4, Qt 5.9.3 and KF5 5.41.0

I'm not alone with this problem:
https://www.facebook.com/groups/931803210238672/permalink/1542905992461721/?comment_id=154307889231

Is there a fix for it? Digikam is not usable as it anymore...

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

[dolphin] [Bug 387974] Allow Dolphin to be launched when logged in as root user

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
One came up in https://bugs.kde.org/show_bug.cgi?id=179678: penetration
testing.

Besides, that's an argument for distros to disable the root account, not for
DEs to selectively disallow certain pieces of software from running in a root
user session.

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

[dolphin] [Bug 387974] Allow Dolphin to be launched when logged in as root user

[林博仁]

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

林博仁  changed:

   What|Removed |Added

 CC||buo.ren@gmail.com

--- Comment #1 from 林博仁  ---
There's literally no usecases of running a session as root in the first place.

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

[digikam] [Bug 387957] Image Editor Launches without Image

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.8.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/529f5c96103ab6d8a96d65
   ||12719155a0c73aa79e

--- Comment #11 from caulier.gil...@gmail.com ---
Git commit 529f5c96103ab6d8a96d6512719155a0c73aa79e by Gilles Caulier.
Committed on 16/12/2017 at 23:21.
Pushed by cgilles into branch 'master'.

if loading item failed in editor, show a passive popup message box over the
canvas.
FIXED-IN: 5.8.0

M  +8-8libs/notificationmanager/dnotificationpopup.h
M  +7-1utilities/imageeditor/editor/editorwindow.cpp
M  +3-27   utilities/imageeditor/editor/editorwindow_p.h

https://commits.kde.org/digikam/529f5c96103ab6d8a96d6512719155a0c73aa79e

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Nate Graham]

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

--- Comment #39 from Nate Graham  ---
Thanks for working with me and digging deep here. In the end, this was all just
a big misunderstanding, not some kind of conspiracy. :) 

Bugs for Dolphin and Kate:
- https://bugs.kde.org/show_bug.cgi?id=387974
- https://bugs.kde.org/show_bug.cgi?id=387973

Are there any other apps that gained PolKit support but stopped launching when
you're logged in as the root user?

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

[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing

[Simonas]

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

Simonas  changed:

   What|Removed |Added

 CC||obuol...@gmail.com

--- Comment #17 from Simonas  ---
I can confirm the same issue on my dell xps 15 4k, when i set scaling to non
integer value (2.2 in my case) i get the same fuzzy looking fonts. Im also
running qt 5.10, and it didnt solve any issues.

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

[dolphin] [Bug 387973] Allow Kate to be launched when logged in as the root user

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Allow Kate to be launched   |Allow Kate to be launched
   |by the root user|when logged in as the root
   ||user

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

[dolphin] [Bug 387974] New: Allow Dolphin to be launched when logged in as root user

[Nate Graham]

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

Bug ID: 387974
   Summary: Allow Dolphin to be launched when logged in as root
user
   Product: dolphin
   Version: 17.08.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

This came up in https://bugs.kde.org/show_bug.cgi?id=179678#c37

As a part of implementing PolKit support, Dolphin was prevented from running
with root privileges via sudo, which is fine. Unfortunately, now Dolphin also
doesn't launch when you're actually logged in as the root user. This is
probably not necessary since if you're already the root user, privileges aren't
really an issue anymore.

It's worth mentioning that this isn't a Wayland or PolKit restriction; GNOME's
Nautilus can be launched when logged in as the root user, even in a Wayland
session.

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

[dolphin] [Bug 387973] New: Allow Kate to be launched by the root user

[Nate Graham]

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

Bug ID: 387973
   Summary: Allow Kate to be launched by the root user
   Product: dolphin
   Version: 17.08.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

This came up in https://bugs.kde.org/show_bug.cgi?id=179678#c37

As a part of implementing PolKit support, Kate was prevented from running with
root privileges via sudo, which is fine. Unfortunately, now Kate also doesn't
launch when you're actually logged in as the root user. This is probably not
necessary since if you're already the root user, privileges aren't really an
issue anymore.

It's worth mentioning that this isn't a Wayland or PolKit restriction; GNOME's
Gedit can be launched when logged in as the root user, even in a Wayland
session.

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

[qca] [Bug 379810] qca compilation fails with openssl 1.1

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de

--- Comment #5 from Fabian Vogt  ---
Created attachment 109420
  --> https://bugs.kde.org/attachment.cgi?id=109420=edit
Patch for OpenSSL 1.1.0 support

If OpenSSL is built with namespacing enabled, it's not an issue to use Qt4/Qt5
with OpenSSL 1.1.0 in a program together.
However, as OpenSSL < 1.1.0 will be EOL soon, I made a patch that adds support
for both. Except for the rsa_sign method which I do not understand the purpose
of, it should be complete.
All unit tests pass with OpenSSL 1.1.0g and 1.0.2j.

What's the right place to upload this patch for review?

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

[kipiplugins] [Bug 112515] Image Selection Dialog for Kipi-plugins not good for multiple image selection

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|LATER   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
File fixed since a very long time. Closed...

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work

[RJVB]

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

--- Comment #33 from RJVB  ---
(In reply to Christoph Feck from comment #32)
> A good fix would be in KFontRequester.

Indeed, that's one central place where a workaround/fix can be implement.
However,

> There is no need to workaround it in widget styles or even applications.

I don't think that can be guaranteed. Applications can use Qt's native font
dialog for instance (that might even be the default behaviour when not running
under a Plasma setting). And widget styles can be used in "pure Qt"
applications.

> Unfortunately I have no development environment right now, but I can review
> any patches made to KFontRequester::nearestExistingFont().

Would the function I added to QtCurve be appropriate?

QFont Style::FontHelper::fontStripStyleName(const QFont ) const
{
const QString  = f.styleName();
if (styleName.isEmpty()) {
// we can simply return the input font
return f;
} else {
// Check for a mismatch between styleString and styleName; when
// found the font probably had a style name set directly instead of
// receiving it e.g. via the FontDialog. This means its attributes
// may still correspond to the original font, not to the current style.
// Do a database lookup to get a consistent QFont instance to work
with,
// so that methods like setWeight(), setStyle() will work as expected.
QFont g = (m_fntDB->styleString(f) != styleName) ?
m_fntDB->font(f.family(), styleName, f.pointSize())
: QFont(f.family(), f.pointSize(), f.weight());
if (auto s = f.pixelSize() > 0) {
g.setPixelSize(s);
}
g.setStyleHint(f.styleHint(), f.styleStrategy());
g.setStyle(f.style());
if (f.underline()) {
g.setUnderline(true);
}
if (f.strikeOut()) {
g.setStrikeOut(true);
}
if (f.fixedPitch()) {
g.setFixedPitch(true);
}
return g;
}
}

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Bo Weaver]

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

--- Comment #38 from Bo Weaver  ---
(In reply to Bo Weaver from comment #37)
> (In reply to Nate Graham from comment #36)
> > Let me make sure I understand:
> > 
> > - With GNOME, you log in as the root user with a Wayland session OR an X
> > session and in both cases you can run Gedit and Dolphin as the root user
> 
> Yep with Gnome running a X session Gedit and their File Manager (Natulius)
> (Spelled wrong)  work just fine when logged in as root.  By default Kali is
> set up with only a root account.
> 
> > 
> > - With KDE Plasma, you log in as the root user with a Wayland session OR an
> > X session and in both cases you can't run Kate or Dolphin
> 
> Yep they just "don't work" no error no nothing.  Since I am an advance user
> I did know to run the executable from the command line and then got the
> error can't run as root.  Breaks your heart when you click on Dolphin like
> you have 10,000 times and after an update nothing happens.
> 
> Even in KDE when logged in as root LeafPad and Gedit will open an run and
> change files just fine.  This is my point you haven't stopped editing files
> you've only stopped me from using Kate.  Midnight Commander also works just
> fine.  I just don't like going back to 1980.  
> 
> Yep just checked Gnome on both Wayland and Xorg the default text editors and
> file manager work fine when logged in as root.  This is a KDE problem.
> 
> > 
> > If that is the case, then I think we have found the actual bug and I agree
> > that it should be fixed. This ticket just tracks general Polkit adoption, so
> > we should track that issue with a new bug report.
> 
> Thank you!  yes this is a bug.  When logged in as root there should be no
> restrictions on anything.  That's the reason for the root account.  Now days
> this account is locked and rightly so.  Really Polkit from what I have read
> is for system changes from a normal user account like of like sudo to
> elevate privileges for a single action (good thing)  Such as changing a
> configuration file.  I'm all for this.  What I am saying is when an advanced
> user enables the root account and logs in there should be no restrictions on
> anything.  You guys are in control of the desktop not the underlying OS. 
> The PolicyKit should have no control when logged in as root.  Your root.
> 
> If you want to restrict Kate and Dolphin from a normal user account go right
> ahead but leave the root account alone.


BTW I just tried Kate and Dolphin from a normal user account on a Kali machine.
 When I went to edit a system file it did give me a proper password prompt. 
Kate worked just fine in this manner.  It appears this problem is when only
logged in as root.  This is fine from the normal user account.  Kate won't fire
at all from root.

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Bo Weaver]

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

--- Comment #37 from Bo Weaver  ---
(In reply to Nate Graham from comment #36)
> Let me make sure I understand:
> 
> - With GNOME, you log in as the root user with a Wayland session OR an X
> session and in both cases you can run Gedit and Dolphin as the root user

Yep with Gnome running a X session Gedit and their File Manager (Natulius)
(Spelled wrong)  work just fine when logged in as root.  By default Kali is set
up with only a root account.

> 
> - With KDE Plasma, you log in as the root user with a Wayland session OR an
> X session and in both cases you can't run Kate or Dolphin

Yep they just "don't work" no error no nothing.  Since I am an advance user I
did know to run the executable from the command line and then got the error
can't run as root.  Breaks your heart when you click on Dolphin like you have
10,000 times and after an update nothing happens.

Even in KDE when logged in as root LeafPad and Gedit will open an run and
change files just fine.  This is my point you haven't stopped editing files
you've only stopped me from using Kate.  Midnight Commander also works just
fine.  I just don't like going back to 1980.  

Yep just checked Gnome on both Wayland and Xorg the default text editors and
file manager work fine when logged in as root.  This is a KDE problem.

> 
> If that is the case, then I think we have found the actual bug and I agree
> that it should be fixed. This ticket just tracks general Polkit adoption, so
> we should track that issue with a new bug report.

Thank you!  yes this is a bug.  When logged in as root there should be no
restrictions on anything.  That's the reason for the root account.  Now days
this account is locked and rightly so.  Really Polkit from what I have read is
for system changes from a normal user account like of like sudo to elevate
privileges for a single action (good thing)  Such as changing a configuration
file.  I'm all for this.  What I am saying is when an advanced user enables the
root account and logs in there should be no restrictions on anything.  You guys
are in control of the desktop not the underlying OS.  The PolicyKit should have
no control when logged in as root.  Your root.

If you want to restrict Kate and Dolphin from a normal user account go right
ahead but leave the root account alone.

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

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Christos Gourdoupis]

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

--- Comment #14 from Christos Gourdoupis  ---
I have been trying to debug this and have now reached a point where I can
reproduce it every time under the debugger (kdevelop). This is what happens:
1. akregator starts with a healthy feeds.opml and creates a similar feeds.opml~
2. I do some stuff and then close the window and terminate the program from the
system tray icon.
3. In MainWidget::slotOnShutdown(), setFeedList is called with an empty list.
4. Upon setFeedList() exit a QSharedPointer oldList which holds the
feedlist is deleted.
5. In ~FeedList() destructor, setRootNode(0) is called.
6. In setRootNode(0), delete d->rootNode truncates feeds.opml to length of 1
byte.
7. The program exits NORMALLY. At this point feeds.opml~ contains a good
backup.
8. On next program start, feeds.opml is "saved" to feeds.opml~ effectively
destroying it. The program complains for an invalid feed list and saves an
equally useless feeds.opml-backup.*

Does that help at all? Is there anything I can do?

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work

[Christoph Feck]

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

--- Comment #32 from Christoph Feck  ---
A good fix would be in KFontRequester. It should clear the styleName after
database lookup, if the same font is found when only using the family, weight
and style attributes, possibly by doing two such lookups.

There is no need to workaround it in widget styles or even applications.

Unfortunately I have no development environment right now, but I can review any
patches made to KFontRequester::nearestExistingFont().

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

[kscreenlocker] [Bug 387972] New: Power management suppressing prevents screen from locking

[Dmitry]

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

Bug ID: 387972
   Summary: Power management suppressing prevents screen from
locking
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dmitriyval...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Created attachment 109419
  --> https://bugs.kde.org/attachment.cgi?id=109419=edit
WebRTC in Chromium suppressing power management

KDE ignores lockscreen timeout when power management is suppressed (e.g. by
Chromium playing audio or showing some websites like Aliexpress).
It may be a critical security issue for someone eho rely on auto locking screen
Behavour is the same on:
Latest unstable/developer Neon, Latest OpenSUSE Tumbleweed, Fedora 26, and, I'm
sure, on some other distributions

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

[dolphin] [Bug 387950] Dolphin no longer works under root

[Bo Weaver]

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

--- Comment #2 from Bo Weaver  ---
(In reply to Elvis Angelaccio from comment #1)
> (In reply to Bo Weaver from comment #0)
> > Today I updated my system and found that Dolphin and Kate no longer run
> > under root.  I look and saw that this is considered a security issue.  As a
> > Pen Tester I run under root during testing.  I do understand that normally
> > you would never run under root.  When you logged in as root then why is it a
> > problem accessing files with dolphin?  If the problem is these is a security
> > hole from a normal user account because root can access files with Dolphin
> > then fix the problem don't just break it and turn it off this doesn't "fix"
> > anything.
> 
> No, the problem is that Xorg is not secure. See
> https://cgit.kde.org/kate.git/commit/
> ?id=9adcebd3c2e476c8a32e9b455cc99f46b0e12a7e
> 

I did check out the link and according to the link the problem is "simple bugs
in either kate/kwrite itself or in the underlying libraries such as Qt, XLib or
xcb."  Wouldn't the correct path be fix the bugs in the underlying libraries
not just kill the application?  If these are shared libraries then they could
be also exploited when say the Systems Manager is opened or the Update Manager
is ran.  Killing Kate wouldn't fix an issue with shared libraries.



> 
> > Dear developers people need to access system files from time to time and
> > change those files.  
> 
> Kate already prompts for the root password whenever you edit a system file.
> Dolphin will soon, hopefully.

I don't "see" a prompt I can't open a file.  Kate just doesn't run at all. 
Only when starting kate from the command line am I given an error response.

You missed my point.  I am logged in as root.  Everything I'm doing is
dangerous.  I know this an assume all responsibility for this.  I need this
function for my job.  Just killing access to Kate and Dolphin will not protect
anything when logged in as root.  I'm not talking about sudo or running Kate
"as root" from a users account.  The only thing that is accomplished is I have
to LeafPad to edit a file.  Kate has been my favorite text editor for years.

I do understand that on most machines the root account is and should be locked
by default.  When I set up a Linux box for a normal person I leave it this way
your right they don't need full access in the same manner I do.  Still they're
are some of us that need that level of access and are advanced enough to use a
system in that mode and are willing to assume responsibility for any actions
taking my the themselves.  If your application is not secure enough to be run
by a root user it should not even be on the system.

Basically you're saying don't run KDE on Kali Linux.  Is this right?

> 
> *** This bug has been marked as a duplicate of bug 152150 ***

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

[plasmashell] [Bug 375395] Plasma consumes all memory when showing calendar popup

[Jure Repinc]

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

--- Comment #6 from Jure Repinc  ---
Yeah looks like bug 377160 is the same bug. Thanks to the comments there I
found a workaround: set the start date of all TODOs and the problem described
here is gone for me too. Remove the start date and it is back.

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

[kmail2] [Bug 323900] Page-margins in KDE-printer-settings

[matthias]

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

matth...@hiltpold.ch  changed:

   What|Removed |Added

 CC||matth...@hiltpold.ch

--- Comment #1 from matth...@hiltpold.ch  ---
Hello

my wish is, that Marco's 'ideal thing' 

"set the margins for printing e-mails and other things to work with to 10 mm at
the top, the bottom an the right/outer margin. The left/inner margin should be
20 mm by default, because the pages get perforated."

is soon accepted and realized.

Thank you

Matthias

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

[krusader] [Bug 381905] The key sequence 'Home' is ambiguous

[DimanNe]

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

DimanNe  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from DimanNe  ---
Well, I reinstalled Kubuntu and the bug is not being reproduced anymore, so, I
suppose, it can be closed.

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[bugzilla_noreply]

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

skycoder42...@gmx.de changed:

   What|Removed |Added

 CC||skycoder42...@gmx.de

--- Comment #45 from skycoder42...@gmx.de ---
Any updates on this. As of today the problem still exists with Plasma 5.11.4
and kdepim-addons 17.08.3

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

[plasmashell] [Bug 377160] Calendar popup freezes on show when calendar with vtodo (+end-date and no start-date) is enabled

[bugzilla_noreply]

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

skycoder42...@gmx.de changed:

   What|Removed |Added

 CC||skycoder42...@gmx.de

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

[digikam] [Bug 387960] Failed build Calendar tool with kcalcore 17.12

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
No problem to build digiKam 5.8.0 with libkalcore 17.12 under Linux

Gilles Caulier

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

[digikam] [Bug 387960] Failed build Calendar tool with kcalcore 17.12

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
digiKam 5.8.0 and libkcalcore 17.12.0 can be build without any problem under
MacoOS through Macports.

Gilles Caulier

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

[kdenlive] [Bug 387236] Library "sequences" not correctly rendered.

[igor]

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

igor  changed:

   What|Removed |Added

 CC||igor...@visi1.org

--- Comment #1 from igor  ---
In my case is video FadeIN, FadeOUT

Tested in kdenlive version: 
- Win7 Pro sp1 64bit
  - Kdenlive-17.04.3-w64
  - Kdenlive-17.08.2-2-w64
  - Kdenlive-17.12.0-w64
Linux Mint 18.1 mate 64bit "serena"
  - kdenlive-17.08.1-x86_64.AppImage
  - kdenlive-17.12-x86_64.AppImage

About my video: 1280x720px 25fps MOV --> video fade-In-OUT

1) In only one video track "Video1" I insert two clips of a trim video: clip_01
(6 sec) + clip_02 (7sec).
2) Insert the effects "Fade from Black" (FFB) and "Fade to Black" (FTB) into
start and end of the two clips: FFB=2sec, FTB=2sec.

This is a view in Timeline:
[##][###]

2.1) In "Project Monitor" play is OK.
3) In Timeline select all: the two clips and effects
4) In "Library" tab I click on "Add Timeline Section To Library" icon, and
insert the name: "seq1_fade-IN_fade-OUT"(.mlt).
5) In "Library" tab I click on "Add clip To Project" icon.
6) In "Project Bin" I see my sequence "seq1_fade-IN_fade-OUT.mlt" and drag and
drop in Timeline.
7) In "Project Monitor" player I see only the "Fade from Black" and "Fade to
Black" relative at first clip (clip_01);
 the second clip (clip_02) haven't fade.

This is a play:
[##][###]

8) In a text editor I open the "seq1_fade-IN_fade-OUT.mlt" file by the Library
folder and I try to read/understand.

/* *** */
/* *** SOURCE from Library  (part of file) *** */
/* *** */

  
 /* OK */
  1
  brightness
  fade_to_black
  brightness
  2
  0
  

/* OK */
  0
  brightness
  fade_from_black
  brightness
  3
  1

  
  
/* MISTAKE_01 ??? */
  1
  brightness
  fade_to_black
  brightness
  2
  0
  

/* MISTAKE_02 ??? */
  0
  brightness
  fade_from_black
  brightness
  3
  1
  

  


/* * */
/* *** MODIFIED with text editor by me and OK (part of file) *** */
/* * */

  
/* OK */
  1
  brightness
  fade_to_black
  brightness
  2
  0
  

   /* OK */
  0
  brightness
  fade_from_black
  brightness
  3
  1

  
  
  /* MODIFIED by me */
  1
  brightness
  fade_to_black
  brightness
  2
  0
  

 /* MODIFIED by me */
  0
  brightness
  fade_from_black
  brightness
  3
  1
  
  

  


9) After modified the file "seq1_fade-IN_fade-OUT.mlt" I used it in Timeline.
Now I can also expand the clip sequence; before with original Library clip I
can't.

I don't know if these changes are align with the mlt/kdenlive code.
I hope it can be help developers to fix the issue.
Thanks so much.

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

[krunner] [Bug 387971] New: krunner crashes

[Anton]

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

Bug ID: 387971
   Summary: krunner crashes
   Product: krunner
   Version: 5.11.3
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: mail.aerma...@gmail.com
  Target Milestone: ---

Application: krunner (5.11.3)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.9.67 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
Right mouse click on the desktop, choise run command, then trying to type a
text in it.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f2d9e594700 (LWP 31287)):
#0  0x7f2dc54f998b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2dca21c54b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f2dcd835008 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f2dcd83543a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f2dca21b22e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2dc54f3565 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2dc95bf31f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f2dab5ef700 (LWP 31286)):
#0  0x7ffc4cb8c9ae in clock_gettime ()
#1  0x7f2dc95ce1e6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f2dca44a7d1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2dca449099 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2dca449615 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2dca44ab6e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f2dc1432ba0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f2dc1433523 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f2dc14336fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f2dca44adbb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f2dca3f310a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f2dca21663a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f2dcd378625 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7f2dca21b22e in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f2dc54f3565 in start_thread () at /lib64/libpthread.so.0
#15 0x7f2dc95bf31f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2db3447700 (LWP 31285)):
#0  0x7ffc4cb8c9ae in clock_gettime ()
#1  0x7f2dc95ce1e6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f2dca44a7d1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2dca449099 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2dca449615 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2dca44ab6e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f2dc1432ba0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f2dc1433523 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f2dc14336fc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f2dca44adbb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f2dca3f310a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f2dca21663a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f2dcc093c55 in  () at /usr/lib64/libQt5DBus.so.5
#13 0x7f2dca21b22e in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f2dc54f3565 in start_thread () at /lib64/libpthread.so.0
#15 0x7f2dc95bf31f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f2db9aec700 (LWP 31284)):
#0  0x7f2dc95b368b in poll () at /lib64/libc.so.6
#1  0x7f2dc8616f32 in  () at /usr/lib64/libxcb.so.1
#2  0x7f2dc8618c47 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f2dbbf8da39 in  () at
/usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5
#4  0x7f2dca21b22e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2dc54f3565 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2dc95bf31f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2dcec517c0 (LWP 31283)):
[KCrash Handler]
#6  0xaad0 in  ()
#7  0x7f2d955ee8d6 in  () at /usr/lib64/libgobject-2.0.so.0
#8  0x7f2d94309878 in  () at /usr/lib64/qt5/plugins/plasma_runner_marble.so
#9  0x002e in  ()
#10 0x0001 in  ()
#11 0x7f2d955bd3c4 in _init () at /usr/lib64/libgobject-2.0.so.0
#12 0x7f2d9430a058 in  () at /usr/lib64/qt5/plugins/plasma_runner_marble.so
#13 0x7f2dceacb7dc in _dl_init () at /lib64/ld-linux-x86-64.so.2

[kmymoney] [Bug 387970] Drill down backwards (via link) from a report to all transactions that support the report's number

[Robin Gross]

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

--- Comment #2 from Robin Gross  ---
I have just converted from Quicken to KMM; this is a Quicken feature, and a
very handy one. 

Upon entering a report, if you want to see the detailed transactions that make
up any number shown on the report you click the number and all transactions
become available. Via hyperlink, you can go back into the ledger at which time
you can make changes to the ledger. 

This is particularly useful at year-end. For example, adjustments to 'category'
are not common.

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

[skrooge] [Bug 387682] Confirm Changes Request When Closing App EVERY TIME

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

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

--- Comment #8 from Stephane MANKOWSKI  ---
Confirmation message is due to "Update modified pages on close" set to
"Always".

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

[kmymoney] [Bug 387970] Drill down backwards (via link) from a report to all transactions that support the report's number

[Robin Gross]

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

Robin Gross  changed:

   What|Removed |Added

Summary|WISH: drill down backwards  |Drill down backwards (via
   |(via link) from a report to |link) from a report to all
   |all transactions that   |transactions that support
   |support the report's number |the report's number

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Nate Graham]

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

--- Comment #36 from Nate Graham  ---
Let me make sure I understand:

- With GNOME, you log in as the root user with a Wayland session OR an X
session and in both cases you can run Gedit and Dolphin as the root user

- With KDE Plasma, you log in as the root user with a Wayland session OR an X
session and in both cases you can't run Kate or Dolphin

If that is the case, then I think we have found the actual bug and I agree that
it should be fixed. This ticket just tracks general Polkit adoption, so we
should track that issue with a new bug report.

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

[dolphin] [Bug 352296] Going back to home folder selects multiple files

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #6 from Dr. Chapatin  ---
Reproducible with dolphin 17.12 on Arch Linux.

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Bo Weaver]

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

--- Comment #35 from Bo Weaver  ---
(In reply to Nate Graham from comment #34)
Thanks for the reply Nate.  Your reply does answer some questions and your
reply is more open to discussion instead of just WONTFIX.  thank you.

> Bo, you're not really arguing against a decision made here, but rather
> against the whole direction that our industry is going in. As has been
> mentioned, Wayland disallows running GUI apps as root. As a penetration
> tester, this may make your life more difficult, but you're not the user that
> the Wayland folks are targeting. 

I didn't know that about Wayland.  True I don't stay on top of desktop coding
I'm a pen tester I just "use" the desktop.  You are right for pen testing I
guess this means going back to 1970 and not even install a desktop.

Yes the way the industry it appears is everything will be a phone one day. 
What about those of us that need a REAL computing system?  We're not all
lusers.  I don't even own a smart phone for this reason.

> They are trying to make computers more
> secure for ordinary users (who have difficulty with the concepts we're
> discussing), not more convenient for security researchers. I would recommend
> you take your case to the Wayland folks, though I doubt you'll get very far
> because this is an architectural design decision that doesn't really seem
> open for debate.

I know that is the party line about ordinary users, but this isn't the case I
have seen in the "real world".  I have a lot of friends that now use Linux
because of me.  Normal people truck drivers, Ironworkers, 83 year old
Grandmothers.  People you have no clue on how it all works and they don't care
they use want it to work and it works fine for them.  They never need to go
into root.  Lately most distros the root account is locked its there but locked
and can be easily unlocked if needed.  This works fine and is secure.  When
sometime breaks they call me and I do the root work.

I know what you are saying about the Wayland team is true from what I have
followed about Wayland on the net they do have their head up their a_s and it
is their way of the highway.  Much like systemd got crammed down our throats. 
At least they didn't cut out root access to systemd.  

This is the real problem here developers are always trying to fix non-problems
and think they know better than the actual users.  Gnome totally destroyed
their desktop with thinking like this.  I wonder how any developers on this
team use Macs or other systems to write code everyday?  Does everyone use KDE
for their day to day computing?  I do.

Question here:  Gnome runs on Wayland yet their file manager and text editor
work just fine with the desktop running under root.  Kali's default desktop is
Gnome and Kali is set up to run under root.  So why not KDE?

> 
> Instead, you're in the same boat we are: given that currently (or in the
> near future), we won't be able to open GUI apps as root, how can we avoid
> losing existing functionality? So far the answer seems to be PolKit
> adoption, which lets you open apps using normal user permissions and only
> request elevated permissions when necessary. Again this isn't really our
> decision; the world evolves and we need to evolve along with it or else our
> software will stop working.
> 
> > Well it seems that you all screwing with KIO broke kate so why report it to 
> > the
> > kate team?  BTW what you said about opening a root owned file is wrong.  
> > Kate
> > will not open AT ALL under root.  you said I can see the file how?? Kate 
> > won't
> > even open.  It doesn't "work like a charm" it doesn't work AT ALL.
> 
> You don't open Kate as root anymore. You open it with normal permissions and
> edit your root-owned file, either by opening it with the File > Open dialog,
> or via `kate /path/to/root/owned/file.txt`. When you save, you should get
> prompted for credentials to complete the save operation.

I'm running IN root.  3 days ago Kate worked just fine under root after an
update 2 days ago it will not open at all.  I'm not attempting a sudo action. 
I am root.

> 
> Both of those use cases work for me with KDE Frameworks 5.40 and Kate 17.12,
> and they have worked for quite a while. If either of those use cases do not
> work for you, please let us know.

No this doesn't work and this does breaks the consecpt of root access.  Root is
to have FULL access to everything.  This means a file manager or a text editor
or any other application or process.

In engineering we have a saying "If it ain't broke don't f_ck with it".  I
think you developers should take heed to that.

A security note here.  as someone who hacks Linux system regularly.  This is a
security non-issue.  I've hacked 1000's of machines and have yet to use an X11
exploit to gain root access their are too many other and easier ways to gain
this access.  Most Linux machines I have pwned don't even have a GUI.  So all
this chaos and 

[kmymoney] [Bug 387970] WISH: drill down backwards (via link) from a report to all transactions that support the report's number

[Jack]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
I'm not sure if 261849 is different or not.  It is specifically requesting
drill down to a similar or more detailed report, where this is requesting
drilling down to the numbers which contributed to the number you click on. 
Eventually that does go to a specific transaction in the ledger, but it is not
clear how you get there.  If you click on a number which represents the total
monthly income, do you first go to some list of transactions, where each can
take you to that one in the ledger, or do you go directly to the ledger, with
all contributing transactions selected?  I'm just a bit concerned that if the
report shows a total of $750, it gets that by adding the transactions that
contribute to that item - I'm not sure how they could be different, but it is
still useful to be able to easily identify them in the ledger.

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

[plasmashell] [Bug 387961] Device action disappears from device notifier when its description is edited

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

Summary|Device action disappears|Device action disappears
   |from device notifier when   |from device notifier when
   |its descrption is edited|its description is edited

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

[ark] [Bug 387969] Sort files like dolphin ("1 file, 2 file", etc instead "1 file, 10 file, 11 file", etc)

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

Product|aki |ark
 CC||rthoms...@gmail.com
  Component|general |general
   Assignee|xzekeco...@gmail.com|elvis.angelac...@kde.org
   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 208383] Add "Properties" to the context menu of Kickoff/Kicker items

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|wish: add "Properties" to   |Add "Properties" to the
   |the context menu of Kickoff |context menu of
   |items   |Kickoff/Kicker items
   Target Milestone|--- |1.0
   Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk
Version|unspecified |5.11.4
 CC||plasma-b...@kde.org,
   ||pointedst...@zoho.com
Product|plasma4 |plasmashell
  Component|widget-kickoff  |Application Launcher
   ||(Kickoff)

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

[plasma4] [Bug 339907] classic style kde4 start menu lacks most frequently used applications

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
The Plasma 5 version does now!

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

[plasmashell] [Bug 106900] Icons on desktop can't be zoomed

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Assignee|i.semenov@gmail.com |se...@kde.org
   Target Milestone|--- |1.0
Product|plasma4 |plasmashell
 CC||pointedst...@zoho.com
  Component|widget-folderview   |Desktop Containment
Version|unspecified |5.11.4

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

[okular] [Bug 387882] Presentation mode only ever uses non-continuous single page view

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Okular Display mode |Presentation mode only ever
   |displays two .pdf music |uses non-continuous single
   |sheets side by side instead |page view
   |of one page at a time   |

--- Comment #5 from Nate Graham  ---
The bug seems to be that Presentation mode only uses non-continuous single page
mode; it doesn't either keep using the current mode, or have options to change
the mode.

Here's a potential workaround for you: full screen mode respects the current
view mode, so perhaps you can use that instead for now.

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

[kmymoney] [Bug 387970] New: WISH: drill down backwards (via link) from a report to all transactions that support the report's number

[Robin Gross]

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

Bug ID: 387970
   Summary: WISH: drill down backwards (via link) from a report to
all transactions that support the report's number
   Product: kmymoney
   Version: unspecified
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: ro...@fafagallery.info
  Target Milestone: ---

WISHLIST: to be able to drill down backwards (via link) from a report to all
the detailed transactions that make up the number shown on the report.

For example: in an exp/inc report, I have a number that is not supported by the
transactions - how do I go about understanding where the error is? [In other
words: the report shows income of $750 when the income transactions for that
month total $500].

And now, do I need to go through all other transactions to make sure the
numbers in the report are accurate? (Which I did do... yikes).

This is different from bug: 261849 (as I read it).

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

[frameworks-baloo] [Bug 387672] Baloo File Extraction Error

[marty]

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

--- Comment #3 from marty  ---
Created attachment 109418
  --> https://bugs.kde.org/attachment.cgi?id=109418=edit
New crash information added by DrKonqi

baloo_file_extractor (5.40.0) using Qt 5.9.2

- What I was doing when the application crashed:
Happens right after powering up and logging into my laptop.

- Unusual behavior I noticed: When I try to restart this process the fan (and
maybe the hard drive) begin running at noticably higher revs, and my laptop
gets much warmer than normal operation under light processing loads.

-- Backtrace (Reduced):
#8  0x7f2f6cc41b22 in mdb_assert_fail.constprop () from
/lib64/liblmdb.so.0.0.0
#9  0x7f2f6cc36b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0
#10 0x7f2f6cc37d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0
#11 0x7f2f6cc37ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0
#12 0x7f2f6cc39c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0

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

[kdevelop] [Bug 343935] Consider adding support for Meson build system

[OlafLostViking]

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

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

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

[frameworks-syntax-highlighting] [Bug 387705] Highlight PKGBUILD files as bash files

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #7 from Dominik Haumann  ---
@Nate: I was just about to change this. But meanwhile, I think it would be
better to not change this.

Instead, please configure your Kate and change PKGBUILD for Bash to PKGBUILD*
yourself in the settings dialog, "Open/Save" -> "Modes & Filetypes".

See: https://i.imgur.com/4Mwr9nF.png

Therefore, I will change this as fixed, since the original request is already
fixed.

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Nate Graham]

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

--- Comment #34 from Nate Graham  ---
Bo, you're not really arguing against a decision made here, but rather against
the whole direction that our industry is going in. As has been mentioned,
Wayland disallows running GUI apps as root. As a penetration tester, this may
make your life more difficult, but you're not the user that the Wayland folks
are targeting. They are trying to make computers more secure for ordinary users
(who have difficulty with the concepts we're discussing), not more convenient
for security researchers. I would recommend you take your case to the Wayland
folks, though I doubt you'll get very far because this is an architectural
design decision that doesn't really seem open for debate.

Instead, you're in the same boat we are: given that currently (or in the near
future), we won't be able to open GUI apps as root, how can we avoid losing
existing functionality? So far the answer seems to be PolKit adoption, which
lets you open apps using normal user permissions and only request elevated
permissions when necessary. Again this isn't really our decision; the world
evolves and we need to evolve along with it or else our software will stop
working.

> Well it seems that you all screwing with KIO broke kate so why report it to 
> the
> kate team?  BTW what you said about opening a root owned file is wrong.  Kate
> will not open AT ALL under root.  you said I can see the file how?? Kate won't
> even open.  It doesn't "work like a charm" it doesn't work AT ALL.

You don't open Kate as root anymore. You open it with normal permissions and
edit your root-owned file, either by opening it with the File > Open dialog, or
via `kate /path/to/root/owned/file.txt`. When you save, you should get prompted
for credentials to complete the save operation.

Both of those use cases work for me with KDE Frameworks 5.40 and Kate 17.12,
and they have worked for quite a while. If either of those use cases do not
work for you, please let us know.

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

[aki] [Bug 387969] Sort files like dolphin ("1 file, 2 file", etc instead "1 file, 10 file, 11 file", etc)

[Dr . Chapatin]

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

--- Comment #1 from Dr. Chapatin  ---
Created attachment 109417
  --> https://bugs.kde.org/attachment.cgi?id=109417=edit
sorting in ark

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

[aki] [Bug 387969] New: Sort files like dolphin ("1 file, 2 file", etc instead "1 file, 10 file, 11 file", etc)

[Dr . Chapatin]

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

Bug ID: 387969
   Summary: Sort files like dolphin ("1 file, 2 file", etc instead
"1 file, 10 file, 11 file", etc)
   Product: aki
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: xzekeco...@gmail.com
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Created attachment 109416
  --> https://bugs.kde.org/attachment.cgi?id=109416=edit
sorting in dolphin

Ark and Dolphin use different methods to sort the files, compare my
screenshots.

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Bo Weaver]

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

Bo Weaver  changed:

   What|Removed |Added

 CC||b...@boweaver.com

--- Comment #33 from Bo Weaver  ---
(In reply to Nate Graham from comment #25)
> Nobody is dumbing anything down. 
Yes you are.  I know when I am in root I know the dangers.  I don't need you
killing applications to make me safe.  Did you all forget the meaning of "root"
in Linux?  Actually you are screwing with access to something out of your
control.  Root is a system function not a desktop function.

> Basic security involves running with the
> lowest permissions possible. That's why you selectively use sudo when you
> need to edit something as root, rather than using into the root account 100%
> of the time. This is simply a further extension of the principle: run with
> normal permissions until the software requests an action demanding elevated
> permissions, and only then do we ask for those permissions.

Actually there are Use Cases that a user must run under root 100% such as Pen
Testing.  When pen testing you need full access to your OS.  OK you say use
sudo yet "sudo kate" doesn't work.  Yet when in root Gedit, nano, LeafPad Vi
and Emacs all run under root so explain how have you so called "protected" file
access??


> 
> If some part of the new system doesn't work properly, that's a bug, and we
> should--and will--fix it. 

Well it broken SO fix it!

> But note that this particular bug report concerns
> KIO, not Kate. Anyone who's having an issue with Kate should file a new bug
> against the Kate product. And FWIW, Kate's PolKit support has been working
> just fine for me. You can open a root-owned file and then only when you save
> it are you prompted for credentials. Works like a charm, no "dumbing down"
> involved.

Well it seems that you all screwing with KIO broke kate so why report it to the
kate team?  BTW what you said about opening a root owned file is wrong.  Kate
will not open AT ALL under root.  you said I can see the file how?? Kate won't
even open.  It doesn't "work like a charm" it doesn't work AT ALL.

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work

[Nate Graham]

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

--- Comment #31 from Nate Graham  ---
So should we patch Breeze and Oxygen in the same way? Or is there no real way
for us to avoid app-specific patches like https://phabricator.kde.org/D8610?

FWIW I've noticed that as of Plasma 5.11 and Qt 5.9.1, Bold text appears
correctly in Dolphin and Gwenview's URL bars.

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

[digikam] [Bug 385653] non handled sqlite exception because of lack of space

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
or perhaps you have a problem with cmake cache to clean and reconfigure...

Gilles Caulier

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

[digikam] [Bug 385653] non handled sqlite exception because of lack of space

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
To compile with OPenCV3, you need to turn on a cmake flag at configure time :
-DENABLE_OPENCV3=ON

Gilles Caulier

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

[digikam] [Bug 385653] non handled sqlite exception because of lack of space

[Jaime Torres]

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

--- Comment #2 from Jaime Torres  ---
I can't test the development version because I can't compile it.

I get the following error:
g++: error: opencv_core-NOTFOUND: No existe el fichero o el directorio
g++: error: opencv_objdetect-NOTFOUND: No existe el fichero o el directorio
g++: error: opencv_imgproc-NOTFOUND: No existe el fichero o el directorio
g++: error: opencv_imgcodecs-NOTFOUND: No existe el fichero o el directorio

even when the cmake output contains:
-- Found OpenCV: /usr (found version "3.3.1") found components:  core objdetect
imgproc imgcodecs 
-- OpenCV Root directory is: /usr/share/OpenCV
-- OpenCV: Found version 3.3.1 (required: 3.1.0)
-- OpenCV headers: /usr/include;/usr/include/opencv
-- OpenCV libs   : opencv_core;opencv_objdetect;opencv_imgproc;opencv_imgcodecs

But in the code, all the SQL exceptions are handled, so it should be fixed.

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

[kwin] [Bug 320704] Lagging mouse cursor

[Angel]

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

Angel  changed:

   What|Removed |Added

 CC||gibbsan...@yahoo.com

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

[digikam] [Bug 387960] Failed build Calendar tool with kcalcore 17.12

[bugzilla_noreply]

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

--- Comment #1 from caulier.gil...@gmail.com ---
Here no problem to compile current digiKam Calendar tool with libkcalcore 17.12
under MXE cross compiler for Windows :

[gilles@localhost calendar]$ make
[  0%] Automatic MOC for target calendar_src
Generating MOC source calendar_src_autogen/MYTF2TZHEE/moc_calpainter.cpp
Generating MOC source calendar_src_autogen/MYTF2TZHEE/moc_calprinter.cpp
Generating MOC source calendar_src_autogen/MYTF2TZHEE/moc_calsettings.cpp
Generating MOC source calendar_src_autogen/WNPF3WE3L6/moc_calmonthwidget.cpp
Generating MOC source calendar_src_autogen/WNPF3WE3L6/moc_caltemplate.cpp
Generating MOC source calendar_src_autogen/WNPF3WE3L6/moc_calwidget.cpp
Generating MOC source calendar_src_autogen/WNPF3WE3L6/moc_calwizard.cpp
Generating MOC compilation calendar_src_autogen/moc_compilation.cpp
[  0%] Built target calendar_src_autogen
[  0%] Generating ui_calprogress.h
[  0%] Generating ui_caltemplate.h
[  0%] Generating ui_calevents.h
Scanning dependencies of target calendar_src
[  0%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/print/calsettings.cpp.obj
[  0%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/print/calpainter.cpp.obj
[  0%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/print/calprinter.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/print/calsystem.cpp.obj
/mnt/devel/GIT/5.x/core/utilities/assistants/calendar/print/calsystem.cpp: In
member function 'int Digikam::CalSystemPrivate::quarter(int) const':
/mnt/devel/GIT/5.x/core/utilities/assistants/calendar/print/calsystem.cpp:459:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
 [[fallthrough]];
 ^
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/wizard/calintropage.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/wizard/calmonthwidget.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/wizard/caltemplate.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/wizard/calwidget.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/wizard/calwizard.cpp.obj
[100%] Building CXX object
core/utilities/assistants/calendar/CMakeFiles/calendar_src.dir/calendar_src_autogen/moc_compilation.cpp.obj
[100%] Built target calendar_src
[gilles@localhost calendar]$ 

Gilles Caulier

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

[kmymoney] [Bug 361078] Stock Price Updater Fails on Windows 10, worked until approx. week ago.

[HJH]

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

--- Comment #3 from HJH  ---
Sehr geehrter Herr Baumgart,
vielen Dank für Ihre schnelle Reaktion und den Tipp. Ich habe in der Folge noch
mehr oder weniger zeitaufwendig und mühsam eine ganze Reihe von Einstellungen
und Quellen probiert. Letzten Endes war für mich erfolgreich:

URL: https://finance.google.com/finance?q=%1
Symbol: %1
Preis: \s+content="((\d+|\d{1,3}(?:[,]\d{3})).\d+)
Datum: \s+content="(\d{4}-\d{2}-\d{2})T
Datumsformat: %y-%m-%d

Dabei müssen die alten Yahoo Symbole für die Wertpapiere weiter verwendet
werden. Das hat bis auf eine Position geklappt. Damit kann ich gut leben.

Bei dieser Gelegenheit ein großes Lob für KMyMoney. Das Programm ist für meine
Zwecke optimal geeignet, in der Handhabung einfacher als z.B. GnuCash und
insgesamt wesentlich besser als alles was ich im Microsoft Store gesehen habe. 

Freundliche Grüße
Hans-Jürgen Hoppe

Gesendet von Mail für Windows 10

Von: Thomas Baumgart
Gesendet: Montag, 4. Dezember 2017 13:01
An: hansjuergenhop...@web.de
Betreff: [kmymoney] [Bug 361078] Stock Price Updater Fails on Windows 10,
worked until approx. week ago.

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

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #2 from Thomas Baumgart  ---
The question is which quote source the original poster uses. In case it was
Yahoo, then it won't work anymore.

@HJH: Please see #386462 that Yahoo shutdown the services and find possible
workarounds in that bug entry.

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

[dolphin] [Bug 152150] Cannot 'Open as Root' files/directories

[Bo Weaver]

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

--- Comment #12 from Bo Weaver  ---
So this is a WONTFIX.  This is the first time in over 20 years I have seen KDE
get stupid.  So it is dangerous to open system files and to edit system files
and "I" might make a mistake.  Dude I have been using Linux since the 1990's
sure I've done some stupid things and have borked my system doing stupid
things.  Did I blame it on you?  Of course not.  My fault.  What you are doing
is removing my control of MY operating system.  You are cutting off my control
of the OS.  Your a desktop and this really shouldn't be your decision.  In
other posts is was said that you are going the way of Gnome which you are.  At
one time Gnome was a nice desktop but due to self-center developers it is the
Windows 8.1 desktop for Linux and totally unable with more than two monitors. 
Seems you guys have went down the same trail.

I have work in systems/network security for over 20 years and let me tell you
your reasons are WRONG.  Sure logged in as root is dangerous but at times a
person must have access to the system killing access doesn't fix anything.  You
guys are developers and you are not security engineers.  Even with this broken
fix there are still methods to drop to root if you are hacking the system.  You
haven't "fixed" anything. you have only broken access.

You even say a text editor is dangerous. WTF!! Oh you might break your system
with Kate yet Gedit, LeafPad, Nano, Vi and Emacs ALL work under root.  So
killing access of Kate doesn't keep a person from Editing or changing files. 
YOU HAVEN"T "FIXED" ANYTHING.

I can access and delete system files from the command line what next breaking
access to system files from Konsole?  What's next when I run "ls /etc" in
Konsole will I soon get an error "Your too stupid to see these files"

One thing I have always like about KDE is it is highly configurable.  You can
change just about anything with the desktop except of now.

I guess after 20 years of use I'll just find something else to use.  Sad...  I
know you all write the code but you are not God and you clearly don't
understand to use case of users.

I read one article that this is for "Joe User" I hate to tell you this but Joe
Luser doesn't use KDE the more advanced user uses KDE or did and advanced users
want access to the friggin system.

Hell even Windows will give you access to the OS when needed.

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work

[RJVB]

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

--- Comment #30 from RJVB  ---
I think your guess is as good as mine. There appears to be a consensus among
the Qt devs that the style name will continue to work as it does currently,
despite some disagreement on the details (like whether the font dialog should
always set a style name).

Some day there may be API to unset attributes. That's not currently possible,
for instance, QFont::setBold(false) will tell the font engine that you want a
font that's not bold. That's not necessarily the font you started out with
after you called setBold(true).

Until that time we'll need some kind(s) of workaround (like the function to
recreate a font without stylename I committed to QtCurve) and KDE code should
probably aim to avoid using the style name as far as possible. This would have
been easier if there were a KFont class...

It could be very useful to have a more capable (geeky) font explorer that
exposes some more of the information that Qt uses internally, like a font's
PANOSE data. I keep reading that style names aren't needed for fonts that can
be represented in that system, but AFAIK I have only fonts that are in that
category (and wouldn't know how to identify a font that isn't). That makes it
hard to test the workarounds and to figure out if code can determine reliably
when a style name can NOT be avoided.

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

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

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
Sorry, I'm afraid I can't contribute much to K3b as I don't have any hardware
with a disc drive.

Also, Leslie, if K3b is distributed through KDE Applications, then you should
work with the release team to write the release notes for each release.

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

[k3b] [Bug 382776] Enable "apply" button only when some setting is changed

[Nate Graham]

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

--- Comment #6 from Nate Graham  ---
Sorry, I'm afraid I can't contribute much to K3b as I don't have any hardware
with a disc drive.

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

[krita] [Bug 383601] Auto activate and select tools if user clicks on corresponding presets

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|[Wishbug] Auto activate and |Auto activate and select
   |select tools if user clicks |tools if user clicks on
   |on corresponding presets|corresponding presets

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

[krita] [Bug 364167] Make it possible to adjust letter spacing and line spacing in Mutipleline text tool

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Layers/Vector   |Tool/Text

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

[elisa] [Bug 387772] Stuck at configuring

[now-im]

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

--- Comment #12 from now-im  ---
okay, I left elisa open and after some time it stopped searching for track but
every time I open the app, same configure thing. 
Right now there is no option to add track path. I could not open any AAC file,
thus tried to open a MP3 file. I could not open that either.
Most of my music files are in AAC format. So, it is vital that elisa can open
that.

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

[dolphin] [Bug 387968] Glitches when zoom in/out details view

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
   Severity|normal  |minor

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

[digikam] [Bug 387957] Image Editor Launches without Image

[bugzilla_noreply]

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

--- Comment #10 from caulier.gil...@gmail.com ---
The automount request by application under Windows is another problem that i
don't know a solution (if there is one of course).

The second problem is to show an error message when image cannot be loaded in
editor. This one can be solved.

Gilles Caulier

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

[dolphin] [Bug 387968] New: Glitches when zoom in/out details view

[Dr . Chapatin]

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

Bug ID: 387968
   Summary: Glitches when zoom in/out details view
   Product: dolphin
   Version: 17.08.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Created attachment 109414
  --> https://bugs.kde.org/attachment.cgi?id=109414=edit
demonstration

Use ctrl+mouse wheel to zoom in/out. See my gif.

dolphin 17.12, frameworks 5.41 and qt5.10 on Arch linux

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

[digikam] [Bug 374302] MYSQL : all Images with Geoinfo seem to be at (0°, 0°)

[Lukas Winkler]

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

--- Comment #28 from Lukas Winkler  ---
Now that Bug 387958 is solved, I have tested this again, but nothing did change
since 5.7

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work

[Nate Graham]

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

--- Comment #29 from Nate Graham  ---
RJVB, I really appreciate all the work you've done on this multifaceted issue.
What's the current status and what's our path forward?

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

[digikam] [Bug 374302] MYSQL : all Images with Geoinfo seem to be at (0°, 0°)

[Lukas Winkler]

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

Lukas Winkler  changed:

   What|Removed |Added

Version|5.6.0   |5.8.0

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