[umbrello] [Bug 403808] Realization of ball-and-socket notation for simple ports like in UML 2 structured classifiers specification

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403808

Ralf Habacker  changed:

   What|Removed |Added

   Target Milestone|--- |2.29 (KDE Applications
   ||19.08)

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

[umbrello] [Bug 410937] Open file assigned to an artifact

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=410937

Ralf Habacker  changed:

   What|Removed |Added

   Target Milestone|--- |2.30 (KDE Applications
   ||19.12)

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

[umbrello] [Bug 414079] No unit tests for association available

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=414079

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In|2.29.90 (KDE Release|2.29.90 (KDE Applications
   |19.11.90)   |19.11.90)

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

[umbrello] [Bug 331655] auto-generated getters and setters to atributes are private in generated java classes

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=331655

Ralf Habacker  changed:

   What|Removed |Added

   Target Milestone|--- |2.30 (KDE Applications
   ||19.12)

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

[umbrello] [Bug 413569] C++ Code Generation Wizard generates wrong 'string' include statement

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=413569

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In|2.29.90 (KDE Release|2.29.90 (KDE Applications
   |19.11.90)   |19.11.90)

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

[umbrello] [Bug 413991] When creating code for attribute access, the C++ code generator produces unexpected code

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=413991

Ralf Habacker  changed:

   What|Removed |Added

   Target Milestone|--- |2.30 (KDE Applications
   ||19.12)

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

[umbrello] [Bug 57583] User settable member variable prefixes for code generation

2019-11-23 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=57583

Ralf Habacker  changed:

   What|Removed |Added

   Target Milestone|--- |2.30 (KDE Applications
   ||19.12)

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

[digikam] [Bug 414424] New: Wishlist: Item count for tag tree is not very intuitive. Maybe show number of total items and subtags separately?

2019-11-23 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=414424

Bug ID: 414424
   Summary: Wishlist: Item count for tag tree is not very
intuitive. Maybe show number of total items and
subtags separately?
   Product: digikam
   Version: 6.4.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Albums-TreeView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Ok, this is a suggestion based on bug #399338 that I reported myself a while
ago. 

When you enable the item count for the tree view, the total number of items
next to each Tag is not very intuitive. Apparently, it not only counts the
number of elements with that tag, but also the number of elements contained in
each sub-tag, regardless of the duplicates. Therefore, the total number is
usually higher than the total existing elements.

For example, I have a tag "Germany" with 6 subtags (and one of them, in turn,
contains 8 subtags). When collapsed, Germany shows the number 412, but in
reality, only 149 pictures exist in that tag structure. So 412 is the number of
pictures that contain that tag, plus the number of pictures that contain each
subtag. Apparently this is done on purpose, but I still find it a bit
counterintuitive. In some cases I have some very detailed tag trees with show
tens of thousands of pictures, when in reality they only contain 2000 pictures
at most.

So my proposal: Why not show only the total number of elements contained in the
tree structure (so, the same number at the bottom of the screen), and also
indicate the number of subtags? For instance "Germany (149, 14 subtags)"
instead of "Germany (412)". Or maybe even just the first number, if you don't
to clutter the interface. 

What do you think? I don't know if that has been previously discussed and there
is an consensus on this topic, but I wouldn't mind exploring other options.

Thanks for your time.

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

[digikam] [Bug 414424] Wishlist: Item count for tag tree is not very intuitive. Maybe show number of total items and subtags separately?

2019-11-23 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=414424

MarcP  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[kate] [Bug 414362] Old file changed dialog had some advantages over the current KMessageWidget-based UI

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414362

--- Comment #3 from nfx...@gmail.com ---
> [x] Warn about files modified by foreign processes

Of course this option was enabled in all of my tests. I suppose if it were
disabled, the new "popup" would not appear at all.

> I'm also not super happy with the new UI, but I didn't really like the old UI 
> either.

Yes, the old UI wasn't too great. But it was pretty functional. My claim is
that it had the following 2 non-cosmetic advantages:
1. A modal dialog that forces the user to intervene (and prevents making it
worse)
2. Handling all changed files at once

As far as non-cosmetic goes, I really dislike the way the "popup" is animated
and displaces the text.

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

[Discover] [Bug 414423] New: In the updates section in Discover, the pane showing the list of updates is cut off at the top of the screen

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414423

Bug ID: 414423
   Summary: In the updates section in Discover, the pane showing
the list of updates is cut off at the top of the
screen
   Product: Discover
   Version: 5.17.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: citriccactus+kdeb...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 124077
  --> https://bugs.kde.org/attachment.cgi?id=124077=edit
Screen recording

STEPS TO REPRODUCE
1. Open Discover when updates are available
2. Go to the updates section 

OBSERVED RESULT
The list of updates is cut off at the top, hiding the checkbox to
select/deselect all updates, the 'System updates' header and the top of the
first package's name.
It's impossible to see them via scrolling up using the scroll wheel (or
equivalent) but is possible to see them by going to pull down to refresh

EXPECTED RESULT
The header should not be cut off

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.3.0-23-generic
(available in About System)
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.4

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

[systemsettings] [Bug 414396] systemsettings5 miswrites sddm.conf

2019-11-23 Thread Ben
https://bugs.kde.org/show_bug.cgi?id=414396

--- Comment #8 from Ben  ---
Did you realize that I habe installed backports?

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

[docs] [Bug 392550] Feature to fetch Github and KDE projects should be explicitly documented

2019-11-23 Thread Yuri Chornoivan
https://bugs.kde.org/show_bug.cgi?id=392550

Yuri Chornoivan  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||kdevelop/commit/eb913c94d29
   ||cab3b03cf5e8bb84757554a315a
   ||a8
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Yuri Chornoivan  ---
Git commit eb913c94d29cab3b03cf5e8bb84757554a315aa8 by Yuri Chornoivan, on
behalf of Adrián Chaves.
Committed on 23/11/2019 at 12:17.
Pushed by yurchor into branch 'master'.

Mention all fetch project sources in the documentation
Differential Revision: https://phabricator.kde.org/D25342

M  +2-2doc/kdevelop/index.docbook

https://invent.kde.org/kde/kdevelop/commit/eb913c94d29cab3b03cf5e8bb84757554a315aa8

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

[systemsettings] [Bug 414396] systemsettings5 miswrites sddm.conf

2019-11-23 Thread Ben
https://bugs.kde.org/show_bug.cgi?id=414396

--- Comment #7 from Ben  ---
Okay. Again.

$ ls -l /etc/sddm.conf /etc/sddm.conf.d/kde_settings.conf 
-rw-r--r-- 1 root root   0 Nov 23 10:44 /etc/sddm.conf
-rw--- 1 root root 244 Nov 23 10:44 /etc/sddm.conf.d/kde_settings.conf
Open Systemsettings.
-> Start and Stop -> SDDM -> extend
There's nothing displayed as I configured it.
Sync. Make my settings again. Klick Use. Passwords were requested. Close
Systemsettings.
$ ls -l /etc/sddm.conf /etc/sddm.conf.d/kde_settings.conf 
-rw-r--r-- 1 root root   0 Nov 23 12:31 /etc/sddm.conf
-rw--- 1 root root 244 Nov 23 10:44 /etc/sddm.conf.d/kde_settings.conf
Open Systemsettings.
-> Start and Stop -> SDDM -> extend
There's nothing displayed as I configured it.

But my PC starts correct as I want.

Nothing was changed. No Updates. 2019-11-23 13:39 UTC

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

[docs] [Bug 379109] Update plasma doc to include new feature "Simplified Global Shortcuts" (ModifierOnlyShortcuts) - meta key only

2019-11-23 Thread Adrián Chaves
https://bugs.kde.org/show_bug.cgi?id=379109

Adrián Chaves (Gallaecio)  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Adrián Chaves (Gallaecio)  ---
https://phabricator.kde.org/D25341

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

[kdenlive] [Bug 414422] New: [Snap Package] Clicking "Render" results in D-Bus error on Ubuntu 18.04 an nothing is rendered

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414422

Bug ID: 414422
   Summary: [Snap Package] Clicking "Render" results in D-Bus
error on Ubuntu 18.04 an nothing is rendered
   Product: kdenlive
   Version: 19.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: kleinmeier.bened...@gmail.com
  Target Milestone: ---

Created attachment 124076
  --> https://bugs.kde.org/attachment.cgi?id=124076=edit
kdenlive.stderr

SUMMARY

Clicking "Render" results in D-Bus error and no message is shown to user and
nothing is rendered.

I followed the description on the official website:

STEPS TO REPRODUCE
1. I downloaded and installed Kdenlive 19.08.02 Snap package from [1].
2. I run through the quickstart tutorial [2].
3. I clicked on "Render" button in the symbol toolbar and chose "mp4" as export
format.

- [1]: https://snapcraft.io/kdenlive
- [2]: https://userbase.kde.org/Kdenlive/Manual

OBSERVED RESULT

- In GUI, no error message is shown at all and the rendering queue shows only
"Waiting..."
- On stderr following error message is printed:

* CREATED JOB WITH ARGS:  ("/snap/kdenlive/22/usr/bin/melt",
"/tmp/kdenlive-VwucRB.mlt",
"/home/benedikt/Downloads/kdenlive-quickstart/kdenlive-quickstart.mp4",
"-pid:6061")
starting kdenlive_render process using: 
"/snap/kdenlive/22/usr/bin/kdenlive_render"
dbus[6223]: arguments to dbus_message_new_method_call() were incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file
../../../dbus/dbus-message.c line 1366.
This is normally a bug in some application using the D-Bus library.

EXPECTED RESULT

At least, the (GUI) user should be informed with an error box. And above all,
kdenlive should render the video correctly by using D-Bus properly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.04.3 LTS/
The "About" dialog of the 19.08.2 snap package reports:
- KDE Frameworks 5.61.0
- Qt 5.12.3 (kompiliert gegen 5.12.3)
- Das xcb Fenstersystem

ADDITIONAL INFORMATION

stderr is attached.

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

[digikam] [Bug 414420] Date/time in sidecar files for Videos seems to be ignored by digikam

2019-11-23 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=414420

--- Comment #1 from MarcP  ---
Created attachment 124075
  --> https://bugs.kde.org/attachment.cgi?id=124075=edit
DSCN1382.MOV

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

[digikam] [Bug 414420] New: Date/time in sidecar files for Videos seems to be ignored by digikam

2019-11-23 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=414420

Bug ID: 414420
   Summary: Date/time in sidecar files for Videos seems to be
ignored by digikam
   Product: digikam
   Version: 6.4.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Metadata-Video
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 124074
  --> https://bugs.kde.org/attachment.cgi?id=124074=edit
DSCN1382.xmp

SUMMARY

Since metadata in video files cannot be directly written to files, I thought of
using XMP sidecar files for correcting their date and add some tags. I don't
know if that is a legitimate use of sidecars, but I guess it can't harm.

In any case, most of my video files, specially those from older cameras, have
wrong dates. Enabling the option to write to sidecar files in the settings, and
using the metadata editor, I can change the three XMP dates for the video files
(but not EXIF and IPTC, which are greyed out), and those changes are saved in
the sidecar. However, in digikam the video file still shows the older date.

Moreover, I found out that using the "Adjust Time Date" tool, I can also save
that date in the EXIF information in the sidecar. Now, I don't know if that
makes sense or not, but apparently that info is also saved in the sidecar. In
any case, digikam ignores that information as well, and still uses the old date
for the video file. 

However, I am pretty sure digikam actually reads the sidecar file, since there
is a Tag stored in it, and digikam sees it.

I have attached a sample video file and its sidecar. In digikam, the date reads
2003-01-01, but the real date should be 2004-04-08. If you check the sidecar,
you can see the 2004 date in several fields. There is also the tag "Andorra" in
the sidecar which digikam seems to read correctly.


STEPS TO REPRODUCE
1. Enable reading and writing to sidecar files in the settings.
2. Select a video file, use the metadata editor, and change the three XMP Dates
to some specific day (the three should be the same). Apply changes.
3. Observe how a sidecar has been created, and if you check the contents, the
new dates are there.

OBSERVED RESULT
Digikam still uses the old date for that video.

EXPECTED RESULT
Digikam should use the new XMP date for the video file.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Digikam 6.4.0 (stable) appimage in Ubuntu 18.04 LTS with
Unity DE.

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

[gwenview] [Bug 414421] New: Part of image was missing

2019-11-23 Thread David
https://bugs.kde.org/show_bug.cgi?id=414421

Bug ID: 414421
   Summary: Part of image was missing
   Product: gwenview
   Version: 19.08.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: epicskelet...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Download following picture:
https://github.com/st-tu-dresden-praktikum/swt19w36-videoshop/blob/master/src/main/asciidoc/diagrams/images/customer.svg
2. Open it with gwenview

OBSERVED RESULT
The Image was not shown completely. The right side (about 10% of image) was not
viewable. Resizing and scrolling didn't solve the problem


EXPECTED RESULT
The whole image or at least the possibility to scroll to the part.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux x86_64
(available in About System)
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

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

[digikam] [Bug 414420] Date/time in sidecar files for Videos seems to be ignored by digikam

2019-11-23 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=414420

MarcP  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[plasmashell] [Bug 414419] New: Plasma-wayland crash on login

2019-11-23 Thread Loïc Grobol
https://bugs.kde.org/show_bug.cgi?id=414419

Bug ID: 414419
   Summary: Plasma-wayland crash on login
   Product: plasmashell
   Version: 5.17.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: loic.gro...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.3)

Qt Version: 5.12.4
Frameworks Version: 5.64.0
Operating System: Linux 5.3.0-23-generic x86_64
Distribution: Ubuntu 19.10

-- Information about the crash:
- What I was doing when the application crashed: Logging in a plasma-wayland
session, waiting while my applications were being, restored. Plasma crashed,
then restarted.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x55ae9c5b3634) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
[Current thread is 1 (Thread 0x7fa8c2ae5800 (LWP 11456))]

Thread 11 (Thread 0x7fa86e3de700 (LWP 12665)):
[KCrash Handler]
#6  0x7fa8c5f5044a in wl_proxy_marshal_constructor () at
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#7  0x7fa8c21e385b in QtWaylandClient::QWaylandWindow::handleUpdate() () at
/usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x7fa8c00c0740 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so
#9  0x7fa8c6a9d7f1 in QOpenGLContext::swapBuffers(QSurface*) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x7fa8c816dcaa in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7fa8c81719d8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7fa8c64b1cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fa8c595b669 in start_thread (arg=) at
pthread_create.c:479
#14 0x7fa8c6134323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7fa894e73700 (LWP 11558)):
#0  0x7fa8c66d0a52 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa8c4d22fbf in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8c4d2396b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa8c4d23b73 in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa8c66d06c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8c667763b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa8c64b0a75 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa8c64b1cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8c595b669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7fa8c6134323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fa896f3a700 (LWP 11553)):
#0  0x7fa8c59622c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ae9b62b9a0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7fa8c59622c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ae9b62b950, cond=0x55ae9b62b978) at pthread_cond_wait.c:508
#2  0x7fa8c59622c6 in __pthread_cond_wait (cond=0x55ae9b62b978,
mutex=0x55ae9b62b950) at pthread_cond_wait.c:638
#3  0x7fa8c64b7def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8c64b7ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8c81717b9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fa8c8171a1a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7fa8c64b1cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8c595b669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7fa8c6134323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fa8a5666700 (LWP 11540)):
#0  0x7fa8c61232ac in __GI___libc_read (nbytes=16, buf=0x7fa8a5665b50,
fd=27) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7fa8c61232ac in __GI___libc_read (fd=27, buf=0x7fa8a5665b50,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fa8c4d6b63f in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa8c4d2358e in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa8c4d239e2 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa8c4d23b73 in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fa8c66d06c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa8c667763b in
QEventLoop::exec(QFlags) () at

[systemsettings] [Bug 414418] New: Truncated labels on Display and Monitor / Display Configuration page

2019-11-23 Thread Szczepan Hołyszewski
https://bugs.kde.org/show_bug.cgi?id=414418

Bug ID: 414418
   Summary: Truncated labels on Display and Monitor / Display
Configuration page
   Product: systemsettings
   Version: 5.17.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: rula...@wp.pl
  Target Milestone: ---

Created attachment 124073
  --> https://bugs.kde.org/attachment.cgi?id=124073=edit
Truncated labels, layout not using available space on Display and Monitor /
Display Configuration page

SUMMARY

Some checkbox labels on the Display and Monitor / Display Configuration page
are truncated. NOT an l10n issue, reproducible in en_US locale.

STEPS TO REPRODUCE

1. Open the Display and Monitor / Display Configuration page in
systemsettings5.

OBSERVED RESULT

Truncated labels next to checkboxes. Plenty of unused space where the layout of
the page could expand into but doesn't.

EXPECTED RESULT

Correct sizing of labels. Correct resizing of the whole page layout to make use
of the available space, and thus to make room for the labels.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.3.12-arch1-1
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor
Memory: 15,6 GiB

ADDITIONAL INFORMATION

See attached annotated screenshot. I initially thought it was an issue with
label widths being hardcoded for English locale and not accommodating longer
translated strings in the Polish locale. However when I restarted
systemsettings with LANG=en KDELANG=en LANGUAGE=en, I reproduced the problem
even in the en_US locale.

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

[systemsettings] [Bug 414396] systemsettings5 miswrites sddm.conf

2019-11-23 Thread Filip Fila
https://bugs.kde.org/show_bug.cgi?id=414396

--- Comment #6 from Filip Fila  ---
I can't reproduce that. I have an empty /etc/sddm.conf file, but the system
settings module is still reading the preferences from
etc/sddm.conf.d/kde_settings.conf. Do you have any extra steps on how to
reproduce the condition?

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

[systemsettings] [Bug 414417] New: current splash screen is not highlighted after I set global theme to breeze dark

2019-11-23 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=414417

Bug ID: 414417
   Summary: current splash screen is not highlighted after I set
global theme to breeze dark
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_splashscreen
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

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

STEPS TO REPRODUCE
1. set global theme to breeze dark in open system settings > global theme
2. open "Startup and shutdown" > "Splash screen" kcm
3. 

OBSERVED RESULT
As we can see in the attached screenshot, "Breeze" splash screen is not
highlighted.

EXPECTED RESULT
"Breeze" splash screen is highlighted.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2

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

[kate] [Bug 414408] Kate has rendering issues with Chinese characters: Half drawing lines

2019-11-23 Thread Postix
https://bugs.kde.org/show_bug.cgi?id=414408

Postix  changed:

   What|Removed |Added

Summary|Kate has rendering issues   |Kate has rendering issues
   |with Chinese characters.|with Chinese characters:
   ||Half drawing lines

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

[kate] [Bug 414408] Kate has rendering issues with Chinese characters.

2019-11-23 Thread Postix
https://bugs.kde.org/show_bug.cgi?id=414408

--- Comment #3 from Postix  ---
(In reply to Dominik Haumann from comment #2)
> This looks like the font is missing unicode characters. This is not a bug in
> Kate. If you try other fonts this will likely work.
> 
> Can you please test?

I am not talking about the rectangles but about the only half drawn lines: L38,
L55, L72.

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

[ksysguard] [Bug 414416] New: "Quick search" text is transparent

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414416

Bug ID: 414416
   Summary: "Quick search" text is transparent
   Product: ksysguard
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: pmarget...@gmail.com
  Target Milestone: ---

Created attachment 124071
  --> https://bugs.kde.org/attachment.cgi?id=124071=edit
Composite of Quick search over various backgrounds

SUMMARY
The helper hint text "Quick search" in ksysguard acts differently depending on
what kind of background it has. I'm running sway and QT_QPA_PLATFORM=wayland.

STEPS TO REPRODUCE
1. Open ksysguard over various backgrounds
2. Observe the transparent nature of the "Quick search" text
3. 

OBSERVED RESULT
Quick search text is transparent

EXPECTED RESULT
Quick search text is not transparent

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64
Qt Version: 5.14.0 beta 3

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 414396] systemsettings5 miswrites sddm.conf

2019-11-23 Thread Ben
https://bugs.kde.org/show_bug.cgi?id=414396

--- Comment #5 from Ben  ---
Next problem.

If /etc/sddm.conf is empty, also systemsettings5 displays nothing but the
default.

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

[kdenlive] [Bug 413469] Fit Zoom to Project do not change zoom level

2019-11-23 Thread Pierre Nerzic
https://bugs.kde.org/show_bug.cgi?id=413469

--- Comment #9 from Pierre Nerzic  ---
Hi all,
Good news, I checked the nightly build #365 and it looks like this bug has been
fixed. This ticket can be closed now.

Many thanks for your huge work on kdenlive

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

[partitionmanager] [Bug 413973] Editing partitions resets touchpad configuration

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=413973

--- Comment #22 from joey.joey...@gmail.com ---
I found what's causing the touchpad issue; if I run "udevadm trigger -s input"
the touchpad configuration resets back to defaults.

I've already posted the bug issue on github here:
https://github.com/systemd/systemd/issues/14123#issue-527534449

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

[systemsettings] [Bug 414396] systemsettings5 miswrites sddm.conf

2019-11-23 Thread Ben
https://bugs.kde.org/show_bug.cgi?id=414396

--- Comment #4 from Ben  ---
Okay, this works. Just tested.

But systemsettings5 set /etc/sddm.conf to zero. I think it's better to write
"#The configuration of SDDM you can find here:
 #/etc/sddm.conf.d/kde_settings.conf"
into it, if it is empty.

That's much better because for many years everybody is looking and writing into
/etc/sddm.conf and is wondering what nonsens systemsettings5 is doing.

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

[KScreen] [Bug 414415] Screen black w/ mouse pointer after unplugging closed-lid laptop from external monitor(s)

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414415

--- Comment #1 from p...@extreg.com ---
Disabling screen locking after sleep removes the problem. When screen locking
is disabled, the laptop wakes with a black screen but either moving the mouse
or CTRL+ALT+F2 + CTRL+ALT+F1 makes it normal.

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

[gwenview] [Bug 236059] Gwenview: use same sort order as current Dolphin view

2019-11-23 Thread Frederick Zhang
https://bugs.kde.org/show_bug.cgi?id=236059

Frederick Zhang  changed:

   What|Removed |Added

 CC||frederick...@tsundere.moe

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

[KScreen] [Bug 414415] New: Screen black w/ mouse pointer after unplugging closed-lid laptop from external monitor(s)

2019-11-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414415

Bug ID: 414415
   Summary: Screen black w/ mouse pointer after unplugging
closed-lid laptop from external monitor(s)
   Product: KScreen
   Version: 5.17.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: p...@extreg.com
  Target Milestone: ---

Please note: I'm not sure whether this bug is filed under the correct product.

SUMMARY
Disconnecting an external monitor from a *closed-lid* laptop and _trying_ to
continue work on the laptop causes the laptop screen to be black with the mouse
pointer. CTRL+ALT+F{2...9} + CTRL+ALT+F1 doesn't help. Only way to get the
laptop display working is to either re-connect the external monitor or reboot
the laptop.

There is NO problem if the laptop lid is open when the disconnection happens
which makes me think whether this could have something to do with sleep – when
the external monitor is disconnected the laptop goes to sleep, of course, since
the lid is closed. Or maybe it's not sleep but it's the lockscreen which is a
result of waking from sleep. No idea.

STEPS TO REPRODUCE
1. Use an external monitor, laptop lid closed
2. Disconnect the external monitor
3. Try to continue working on the laptop

OBSERVED RESULT
Screen is totally black with mouse pointer which can be moved

EXPECTED RESULT
Screen is normal and shows all the usual stuff

SOFTWARE/OS VERSIONS
Thinkpad T480s
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.4
Kernel Version: 5.3.12-050312-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 23,0 GiB of RAM


ADDITIONAL INFORMATION

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

[kate] [Bug 414362] Old file changed dialog had some advantages over the current KMessageWidget-based UI

2019-11-23 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=414362

--- Comment #2 from Dominik Haumann  ---
You should still get a dialog when you enable in Kate's general settings the
option [x] Warn about files modified by foreign processes, see:
https://docs.kde.org/stable5/en/applications/kate/configuring-kate-configdialog.html

Can you please try again?

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

[kate] [Bug 414408] Kate has rendering issues with Chinese characters.

2019-11-23 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=414408

--- Comment #2 from Dominik Haumann  ---
This looks like the font is missing unicode characters. This is not a bug in
Kate. If you try other fonts this will likely work.

Can you please test?

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

<    1   2