[kdenlive] [Bug 449946] New: Guides locked doesn't work as expected

2022-02-10 Thread mau
https://bugs.kde.org/show_bug.cgi?id=449946

Bug ID: 449946
   Summary: Guides locked doesn't work as expected
   Product: kdenlive
   Version: 21.12.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

Two observations:

1. Spacer tool:
If Timeline -> Guides -> Guides locked is ticked, they do not move around while
using the spacer tool.
If Timeline -> Guides -> Guides locked is NOT ticked, they do move around while
using the spacer tool.
I would it expected just the other way.

The same is true when using right click on timeline -> Remove space in all
tracks.

2. When inserting space, guides lock doesn't work at all.
If I add space using right click on timeline -> Insert space, then I select
"Insert space in all tracks", then guides are not moved correspondingly, and if
Timeline -> Guides -> Guides locked is ticked or not doesn't change the
behaviour at all.
I would it expect just as with removing space.

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

[kdenlive] [Bug 450454] New: Crash when previewing online resource from Freesound

2022-02-17 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450454

Bug ID: 450454
   Summary: Crash when previewing online resource from Freesound
   Product: kdenlive
   Version: 21.12.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

I tried:
- Online Resources: Freesound
- Search for something (e.g. Vélo)
- Select first result
- Click on Preview
=> kdenlive is crashing

Output in konsole:

https protocol not found, recompile FFmpeg with openssl, gnutls or
securetransport enabled.
https protocol not found, recompile FFmpeg with openssl, gnutls or
securetransport enabled.
/tmp/.mount_kdenliz96jEP/AppRun: line 42: 24537 Segmentation fault 
kdenlive --config kdenlive-appimagerc $@

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

[kdenlive] [Bug 450556] New: Color scheme Breeze Dark: some effect icons invisible

2022-02-19 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450556

Bug ID: 450556
   Summary: Color scheme Breeze Dark: some effect icons invisible
   Product: kdenlive
   Version: 21.12.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

Created attachment 146928
  --> https://bugs.kde.org/attachment.cgi?id=146928&action=edit
Color Scheme

As shown in the screenshot, some icons are rather invisible; hovering with the
mouse helps but I think the color scheme should be adjusted a bit.

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

[kdenlive] [Bug 450556] Color scheme Breeze Dark: some effect icons invisible

2022-02-20 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450556

--- Comment #2 from mau  ---
Well, I activated "Force Breeze Icon Theme" and after the required restart it
looks much better: former dark icons are now bright and so my problem is
solved.

The question is: I updated to the latest appimage some days ago and I removed
all kdenlive settings a few weeks ago, so why did this happen? Is there some
interdependance with my KDE Plasma settings although it's an appimage?

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

[kdenlive] [Bug 416795] Whitebalance keyframes do not keep/store the white balance color

2022-02-21 Thread mau
https://bugs.kde.org/show_bug.cgi?id=416795

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

--- Comment #2 from mau  ---
Would be nice to have; in the meantime, it would be great to see that color is
not relative to keyframes (took me some minutes to find out...).

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

[kdenlive] [Bug 450691] New: Draw Box-effect corrupted by changing Preview Resolution

2022-02-21 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450691

Bug ID: 450691
   Summary: Draw Box-effect corrupted by changing Preview
Resolution
   Product: kdenlive
   Version: 21.12.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

STEPS TO REPRODUCE
1. Draw a box using the Draw Box effect
2. Modify the preview resolution

OBSERVED RESULT
Box is changed in size -> not the intended size anymore.

EXPECTED RESULT
Box should stay the same, no matter which preview resolution is used.

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

[kdenlive] [Bug 450692] New: Vectorscope manual page has invalid links

2022-02-21 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450692

Bug ID: 450692
   Summary: Vectorscope manual page has invalid links
   Product: kdenlive
   Version: 21.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Documentation
  Assignee: ttg...@gmail.com
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

On
https://docs.kdenlive.org/de/user_interface/menu/view_menu/vectorscope.html#vectorscope
there are two links to more detailed descriptions, but both are invalid:

http://kdenlive.org/users/granjow/introducing-color-scopes-vectorscope
http://kdenlive.org/users/granjow/vectorscope-what-i-and-q-lines-are-good

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

[kdenlive] [Bug 450743] New: Rendering "stalled" when disk full

2022-02-23 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450743

Bug ID: 450743
   Summary: Rendering "stalled" when disk full
   Product: kdenlive
   Version: 21.12.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

More an idea for improvement than a bug:
When the disk gets full during rendering, there is no "feedback" at all,
rendering gets stalled, that's all. Well, of course one can argue that it's not
kdenlive's / mlt's problem, but it cost me about 2 hours... I just didn't
expect that this partition is completely filled... I'd like to get some
feedback in the rendering window (Job queue / lower sub window about errors).

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

[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing when using Libinput driver

2022-05-26 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=415364

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kmymoney] [Bug 465587] New: Report Budgeted vs. Actual doesn't aggregate by category as in Budgets

2023-02-11 Thread mau
https://bugs.kde.org/show_bug.cgi?id=465587

Bug ID: 465587
   Summary: Report Budgeted vs. Actual doesn't aggregate by
category as in Budgets
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

In my file, I use a category tree like:
main category 1
  subcategory 1.1
  subcategory 1.2
main category 2
  subcategory 2.1
  subcategory 2.2

When setting budgets for these categories, values get summed up in the category
tree, e.g.
main category 1: 250
  subcategory 1.1: 100
  subcategory 1.2: 150
main category 2
  subcategory 2.1
  subcategory 2.2

When I use a report Budgeted vs. Actual, values do not get summed up in the
tree, i.e. in my example I get:
main category 1: 0
  subcategory 1.1: 100
  subcategory 1.2: 150
main category 2
  subcategory 2.1
  subcategory 2.2
which seems to be not only inconsistent but rather wrong to me.

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

[okular] [Bug 467642] New: Okular crashes on quit

2023-03-21 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=467642

Bug ID: 467642
   Summary: Okular crashes on quit
Classification: Applications
   Product: okular
   Version: 22.12.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: mav...@gmail.com
  Target Milestone: ---

Application: okular (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.7-x64v4+amdnative-xanmod1 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
It seems related to signed PDF documents and the presence of
/usr/local/lib/libcie-pkcs11.so, the library for italian electronic identity
card (CIE); this library also makes LibreOffice crash at every application
quit. The crash seems to happen every time regardless of whether the card
reader and the smart card are connected or not. Thanks.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#5  0x7f5bbbca9d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#6  0x7f5bbbc5aef2 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7  0x7f5bbbc45472 in __GI_abort () at ./stdlib/abort.c:79
#8  0x7f5bbbc9e2d0 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f5bbbdb8459 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#9  0x7f5bbbcb364a in malloc_printerr (str=str@entry=0x7f5bbbdbb0d0 "double
free or corruption (fasttop)") at ./malloc/malloc.c:5660
#10 0x7f5bbbcb5362 in _int_free (av=0x7f5bbbdf1c60 ,
p=0x561b2af2c7e0, have_lock=have_lock@entry=0) at ./malloc/malloc.c:4535
#11 0x7f5bbbcb7d2f in __GI___libc_free (mem=) at
./malloc/malloc.c:3385
#12 0x7f5b772abecf in CLog::~CLog (this=0x7f5b77e4e2a0 ,
__in_chrg=) at ../cie-pkcs11/Util/log.cpp:120
#13 0x7f5bbbc5d435 in __run_exit_handlers (status=0, listp=0x7f5bbbdf1820
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:113
#14 0x7f5bbbc5d5aa in __GI_exit (status=) at
./stdlib/exit.c:143
#15 0x7f5bbbc46191 in __libc_start_call_main
(main=main@entry=0x561b2a498a50, argc=argc@entry=2,
argv=argv@entry=0x7ffd8aadae68) at ../sysdeps/nptl/libc_start_call_main.h:74
#16 0x7f5bbbc46245 in __libc_start_main_impl (main=0x561b2a498a50, argc=2,
argv=0x7ffd8aadae68, init=, fini=,
rtld_fini=, stack_end=0x7ffd8aadae58) at ../csu/libc-start.c:381
#17 0x561b2a49a1f1 in ?? ()
[Inferior 1 (process 7992) detached]

Reported using DrKonqi

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

[KScreen] [Bug 466674] Wayland: various apps crash in DpmsManager::addScreen() when display enters sleep

2023-03-24 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=466674

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kmymoney] [Bug 440452] Suppress categories which are no longer used.

2022-09-23 Thread mau
https://bugs.kde.org/show_bug.cgi?id=440452

mau  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||b-m...@gmx.ch

--- Comment #1 from mau  ---
I don't know of a way to "close and hide" categories similar to how accounts
can be closed. But I'm also very interested in this feature.

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

[kmymoney] [Bug 464636] New: "Organize by account" if several accounts share the same name

2023-01-22 Thread mau
https://bugs.kde.org/show_bug.cgi?id=464636

Bug ID: 464636
   Summary: "Organize by account" if several accounts share the
same name
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

I have an account tree like:
health insurance
 |-- person 1
   |-- 2022
   |-- 2023
 |-- person 2
   |-- 2022
   |-- 2023

I use this yearly sub-accounts because reports using tags are completely broken
at the moment and don't work at all for me (see my other bug reports for them).

Unfortunately, if there are several different account with the same name (here:
2022, 2023), their transactions get aggregated into one account (named 2022 or
2023 resp.). So I'm forced to rename them to something like "2022 (person1 )",
"2022 (person 2)" and so on.

I'd expect different accounts to not get aggregated into one, even if they
share the same name. Technically spoken, I don't expect a "group by account
name" but a "group by account id".

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

[kmymoney] [Bug 464636] "Organize by account" if several accounts share the same name

2023-01-22 Thread mau
https://bugs.kde.org/show_bug.cgi?id=464636

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 464636] "Organize by account" if several accounts share the same name

2023-02-06 Thread mau
https://bugs.kde.org/show_bug.cgi?id=464636

--- Comment #3 from mau  ---
Using the full hierarchy sounds like a very valid fix, since it would solve the
issue. The point is, it doesn't make sense to aggregate accounts with the same
name, if they are not the same, and I'm indeed interested in the sum for each
account separately.

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

[kmymoney] [Bug 464636] "Organize by account" if several accounts share the same name

2023-02-06 Thread mau
https://bugs.kde.org/show_bug.cgi?id=464636

--- Comment #4 from mau  ---
OK, I just checked and it's correct that the transactions of accounts sharing
the same name are reported like "first account", "second account", so a human
can split them by analyzing the transaction dates. But I think that's not the
intention of reports grouped by account. So as I stated before, it would make
sense to use kind of the full hierarchy (but without getting names extremely
long, I don't know how that's solved for categories).

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

[kdenlive] [Bug 450692] Vectorscope manual page has invalid links

2022-02-27 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450692

--- Comment #2 from mau  ---
Second link ("here") is working fine, but there is still the first one ("See
Granjow’s blog here") which is pointing to the page itself (doesn't make
sense).

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

[kdenlive] [Bug 450454] Crash when previewing online resource from Freesound

2022-02-27 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450454

--- Comment #2 from mau  ---
Works again (tested with first link), thank you.

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

[kdenlive] [Bug 450692] Vectorscope manual page has invalid links

2022-03-03 Thread mau
https://bugs.kde.org/show_bug.cgi?id=450692

--- Comment #4 from mau  ---
Well, it works, but: since both links are now pointing towards other pages in
the kdenlive manual and not an external blog anymore their naming doesn't look
professional, I'd rename them.

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

[kdenlive] [Bug 451936] New: Rendering with chapters

2022-03-26 Thread mau
https://bugs.kde.org/show_bug.cgi?id=451936

Bug ID: 451936
   Summary: Rendering with chapters
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

As far as I know, there is currently no way to render the final movie with
guides as chapters. So I'm forced to follow this workflow:
1. add guides to projects
2. render film to one file (I use mp4 as the output format)
3. use ffmpeg to extract metadata: ffmpeg -i film.mp4 -f ffmetadata
FFMETADATAFILE
4. add chapter timestamps to FFMETADATAFILE
5. use ffmpeg to add chapters: ffmpeg -i film.mp4 -i FFMETADATAFILE
-map_metadata 1 -codec copy film_meta.mp4
(6. add cover image using ffmpeg... but that's a different story)

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

[kwin] [Bug 439332] Ghost windows and popups

2021-11-04 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=439332

--- Comment #18 from Mau  ---
I confirm that disabling the "translucent windows" effect solves this issue.

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

[kwin] [Bug 439135] Color management on Wayland

2021-10-21 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=439135

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kwin] [Bug 439332] Ghost windows and popups

2021-10-21 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=439332

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kwin] [Bug 439332] Ghost windows and popups

2021-10-21 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=439332

--- Comment #16 from Mau  ---
Same here since last update from v5.21.5 to v5.23.0

Debian testing
KDE Plasma 5.23.0
KDE Frameworks 5.86.0
QT 5.15.2
Platform X11 v1.20.11
AMD Phenom II X4 965, 8GiB RAM
Nvidia GF106 (GeForce GTS 450) + nvidia-legacy-390xx-driver v390.144-2

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

[xdg-desktop-portal-kde] [Bug 474746] New: All Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

Bug ID: 474746
   Summary: All Gnome apps fonts are rendered without
anti-aliasing
Classification: Plasma
   Product: xdg-desktop-portal-kde
   Version: 5.27.8
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mav...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
  Target Milestone: ---

SUMMARY
Since xdg-desktop-portal-kde v5.27.8 in Wayland sessions all GTK3 applications
have ugly fonts without anti-aliasing and badly scaled; when launched in the
Gnome DE, the same applications' fonts look perfect.

STEPS TO REPRODUCE
1. launch startplasma-wayland
2. open a GTK3 app such as Unison or Evolution

OBSERVED RESULT
Fonts in the GTK3 app appear badly scaled and not anti-aliased at all.

EXPECTED RESULT
Fonts should appear smooth, correctly anti-aliased and well scaled.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian up-to-date Testing
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
I found 3 possible solutions:
- switch to Plasma/X11: this is a Wayland-specific issue
- revert to xdg-desktop-portal-kde v5.27.7
- in the "[preferred]" group in the
/usr/share/xdg-desktop-portal/kde-portals.conf file, change "default" key's
value 
  from "kde" to "kde;gtk;"

Thanks

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

[xdg-desktop-portal-kde] [Bug 474746] All Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

--- Comment #1 from Mau  ---
Created attachment 161762
  --> https://bugs.kde.org/attachment.cgi?id=161762&action=edit
Evolution - Example of the issue

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

[xdg-desktop-portal-kde] [Bug 474746] All Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

--- Comment #2 from Mau  ---
Created attachment 161763
  --> https://bugs.kde.org/attachment.cgi?id=161763&action=edit
Evolution - Issue fixed by adding "gtk" to the default key in kde-portals.conf

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

[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

Mau  changed:

   What|Removed |Added

Summary|All Gnome apps fonts are|Wayland: all Gnome apps
   |rendered without|fonts are rendered without
   |anti-aliasing   |anti-aliasing

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

[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

--- Comment #5 from Mau  ---
(In reply to David Edmundson from comment #3)
> Install the GTK portal.
> It's a bit unintuitive, but changes are happening elsewhere to address this.

It's already installed, it doesn't help.

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

[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing

2023-09-20 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

Mau  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

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

[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing

2023-09-22 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=474746

--- Comment #7 from Mau  ---
(In reply to Timothée Ravier from comment #6)
> This might be: https://bugzilla.redhat.com/show_bug.cgi?id=2240211

Very likely, and that points to
https://github.com/flatpak/xdg-desktop-portal/issues/1017 where the
GTK_USE_PORTAL env variable is cited, and I found I had it set to 1: unsetting
that solved the issue even with just 'default=kde' in kde-portals.conf.

What remains unclear to me is why that didn't cause the problem in a X11
session.

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

[kwin] [Bug 476733] New: KWIN crashes when viewing image sliding, opening applications and switching between desktops

2023-11-08 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=476733

Bug ID: 476733
   Summary: KWIN crashes when viewing image sliding, opening
applications and switching between desktops
Classification: Plasma
   Product: kwin
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mtrigo1...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-11-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
On X11 I faced multiple screen crashes or bugs. 
Suddenly the entire system gets stucked and I can't do anything so need to hard
reset pressing the tower reset button
I use debian for software development, so I have multiple "heavy" applications
like IDEs, DB Managers, docker containers, editors, etc. 
Also I work on 4 desktops switching between them using F1, F2, F3, F4.
When the issue happened I was: 
- Viewing a Image slideshow in fullscreen
- Opened Spotify
- Switching between desktops
- Adjusting memory resources to docker containers
- Watching local video files in fullscreen

I switched from Wayland to X11 because on Wayland I can't share my screen on
videocalls.

Also I have to say that sometimes I can't hibernate the system, normally it
works, but sometimes it takes some time to try to hibernate but it only locks
the screen.

My set:
- ASUS TUF Gaming z490 PLUS
- 48 GB RAM
- SSD 520GB
- Nvidia GTX 1660Ti
- Core i5 11th gen
- Two monitors

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted

   PID: 3086 (kwin_x11)
   UID: 1000 (mauudev)
   GID: 1000 (mauudev)
Signal: 6 (ABRT)
 Timestamp: Wed 2023-11-08 21:11:24 -04 (1min 9s ago)
  Command Line: /usr/bin/kwin_x11 --replace
Executable: /usr/bin/kwin_x11
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service
  Unit: user@1000.service
 User Unit: plasma-kwin_x11.service
 Slice: user-1000.slice
 Owner UID: 1000 (mauudev)
   Boot ID: a6a4f1952cd148b1aae1ab669e7336d3
Machine ID: 7549d6dfb3944fe9840a6cf9f6af35e4
  Hostname: debian
   Storage:
/var/lib/systemd/coredump/core.kwin_x11.1000.a6a4f1952cd148b1aae1ab669e7336d3.3086.169949228400.zst
(present)
  Size on Disk: 6.2M
   Message: Process 3086 (kwin_x11) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64
Stack trace of thread 3086:
#0  0x7f91736aec24 pthread_sigmask (libc.so.6 + 0x8fc24)
#1  0x7f917365b1b9 sigprocmask (libc.so.6 + 0x3c1b9)
#2  0x7f91768e8e9b _ZN6KCrash15setCrashHandlerEPFviE
(libKF5Crash.so.5 + 0x4e9b)
#3  0x7f91768e9b3e _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b3e)
#4  0x7f917365afd0 n/a (libc.so.6 + 0x3bfd0)
#5  0x7f91736a9d3c n/a (libc.so.6 + 0x8ad3c)
#6  0x7f917365af32 raise (libc.so.6 + 0x3bf32)
#7  0x7f9173645472 abort (libc.so.6 + 0x26472)
#8  0x7f9173645395 n/a (libc.so.6 + 0x26395)
#9  0x7f9173653e32 __assert_fail (libc.so.6 + 0x34e32)
#10 0x7f916dce57ff nouveau_pushbuf_data
(libdrm_nouveau.so.2 + 0x47ff)
#11 0x7f916dce5763 nouveau_pushbuf_data
(libdrm_nouveau.so.2 + 0x4763)
#12 0x7f916dce587c n/a (libdrm_nouveau.so.2 + 0x487c)
#13 0x7f916dce5af7 n/a (libdrm_nouveau.so.2 + 0x4af7)
#14 0x7f916dce6559 n/a (libdrm_nouveau.so.2 + 0x5559)
#15 0x7f9166d60f29 n/a (nouveau_dri.so + 0x960f29)
#16 0x7f9166dc4b83 n/a (nouveau_dri.so + 0x9c4b83)
#17 0x7f9166dc9356 n/a (nouveau_dri.so + 0x9c9356)
#18 0x7f9166dc9527 n/a (nouveau_dri.so + 0x9c9527)
#19 0x7f9166dcb1b9 n/a (nouveau_dri.so + 0x9cb1b9)
#20 0x7f91b125 n/a (nouveau_dri.so + 0x26b125)
#21 0x7f91764ac2fe
_ZN4KWin18ItemRendererOpenGL10renderItemEPNS_4ItemEiRK7QRegionRKNS_15WindowPaintDataE
(libkwin.so.5 + 0x2ac2fe)
#22 0x7f917641cd6d
_ZN4KWin18EffectsHandlerImpl10drawWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE
(libkwin.so.5 + 0x21cd6d)
#23 0x7f917641cd6d
_ZN4KWin18EffectsHandlerImpl10drawWindowEPNS_12EffectWindowEiRK7QRegionRNS_15WindowPaintDataE
(libkwin.so.5 + 

[kwin] [Bug 467574] kwin_screencast: Dropping a screencast frame because the compositor is slow

2023-07-13 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=467574

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[plasmashell] [Bug 451529] Task manager tooltip window thumbnails sometimes do not appear

2022-11-04 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=451529

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

--- Comment #2 from Mau  ---
Same here, but I could never see a single window thumbnail/miniature on task
manager tooltips when running under Wayland. The animated content of the
windows can be seen in the task switcher though.

KDE Plasma v5.26.0
KDE Frameworks v5.98.0
QT v5.15.6
Wayland

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

[plasmashell] [Bug 451529] Task manager tooltip window thumbnails sometimes do not appear

2022-11-04 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=451529

--- Comment #4 from Mau  ---
(In reply to Nate Graham from comment #3)
> D you have the kpipewire package installed?

No: in Debian the such package doesn't exist, not even in sid or experimental
(testing here).
Is it required to have the miniatures?

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

[plasmashell] [Bug 451529] Task manager tooltip window thumbnails sometimes do not appear

2022-11-04 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=451529

--- Comment #6 from Mau  ---
(In reply to Nate Graham from comment #5)
> Yep. That would be the problem, then.
> 
> You could point the packagers at
> https://community.kde.org/Distributions/Packaging_Recommendations (kpipewire
> is a Plasma package, and as such, we recommend installing it by default).

Thanks Nate, it worked! I remembered that there is a kpipewire _source_ package
(https://tracker.debian.org/pkg/kpipewire), which entered one week ago in the
repositories: by installing the qml-module-org-kde-pipewire package along with
the libraries it depends on I got the miniatures. Notice that no KDE Plasma
package depends on those packages.

Could you please clarify why are those libraries needed for the task manager,
while the task switcher can display the miniatures without?

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

[kdenlive] [Bug 448713] New: Project Bin: Focus on hidden clip (when working with keyboard)

2022-01-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=448713

Bug ID: 448713
   Summary: Project Bin: Focus on hidden clip (when working with
keyboard)
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

When adding clips to the timeline for the first time with a new project, I do
the following:
- select first clip in project bin
- use keyboard only: use j,k,l-keys to play and i,o-keys for in- and outpoints
and v-key to insert it into the timeline
- use arrow down to select next clip in project bin

Problem: the project bin doesn't follow the selected clip, i.e. it doesn't
"scroll", so after a few clips the selected clip isn't shown anymore. I have to
use the mouse to scroll down in the project bin, so I'm forced to switch
between keyboard and mouse.

Solution: scroll in project bin such that there's at least always one or two
clips shown to both sides of the selected clip, i.e. up and down.

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

[kdenlive] [Bug 448716] New: Deleting clips and proxy clips when removing clip from project bin

2022-01-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=448716

Bug ID: 448716
   Summary: Deleting clips and proxy clips when removing clip from
project bin
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

When working with large projects, at least for my workflow it would be great to
be able to delete clips from the disk (i.e. not only removing them from the
project) in order to free up space.

Also it would be nice to be able to "manage" proxy clips on disk:
- either by being able to delete "unreferenced" proxy clips from disk (i.e.
proxy clips for clips which are not part of the project anymore)
- or by being able to delete proxy clips, when clips are deleted (as described
above).

Since proxy clip file names consist only of a (presumably) file hash, there is
no easy way to remove them, when corresponding clips are deleted.

Currently, I
- remove unused clips from the project bin
- use a file manager to compare the list of the remaining clips in the project
bin to the clips in my Clip Material folder
- delete unused clips in the file manager
If I have to free more disk space, I additionally
- remove all proxy clips
- re-open the project and re-generate all proxy clips.

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

[kdenlive] [Bug 448713] Project Bin: Focus on hidden clip (when working with keyboard)

2022-01-24 Thread mau
https://bugs.kde.org/show_bug.cgi?id=448713

mau  changed:

   What|Removed |Added

   Platform|Other   |Appimage
Version|unspecified |21.12.1

--- Comment #2 from mau  ---
I'm using an Appimage of 21.12.1 under Linux.

Well, the behaviour isn't new for me, I experienced it for several years but
never reported it.

Following your reply, I just tried it again and have to state more precisely:
I open a project with several folders in the project bin and many clips under
at least on of them. I select one clip with the mouse, than I use Arrow Down to
select the next clip. As long as this clip is currently shown in the project
window sub window, I see it selected (blue background). Now when the last
visible clip is selected and I continue to select the next one by pressing
Arrow Down, the highlighted "line" disappears, i.e. a clip is selected which is
below the lower sub window border. If I continue pressing Arrow Down, the next
clip is also "hidden" (second clip), but if I continue again to select the
third clip, the view is updated, i.e. it scrolls down.

Since I usually just continue to the next clip and use my mouse to scroll when
the highlighted line drops out of the project bin window, I never found out
that is "self corrects" itself after a few more clips.

If I select clips up instead of down, the problem doesn't exist, i.e. it
scrolls just fine. If I go down again, the same pattern does apply: 1st and 2nd
clip are "hidden", for the 3rd clip the view is updated correctly.

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

[systemsettings] [Bug 397228] kcm_keyboard crash

2020-11-29 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=397228

--- Comment #2 from Mau  ---
Hi there

pressing "OK" no longer causes module crash. Thanks.

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

[systemsettings] [Bug 397228] kcm_keyboard crash

2020-11-29 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=397228

Mau  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[kwin] [Bug 461903] LibreOffice does not receive pasted data from Klipper correctly

2022-12-12 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=461903

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kmail2] [Bug 28261] Option to store decrypted GPG email unencrypted locally.

2018-10-30 Thread mau
https://bugs.kde.org/show_bug.cgi?id=28261

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kdeconnect] [Bug 405847] SFTP transfer corrupts all files

2019-10-10 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=405847

--- Comment #39 from Mau  ---
Let's vote this bug in order to rise severity. I'm not updating since v1.10.1.

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

[kdeconnect] [Bug 405847] SFTP corrupts DNG files

2019-04-21 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=405847

--- Comment #10 from Mau  ---
(In reply to Yuriy Vidineev from comment #7)
> [...]
> sshfs: 3.2
> 
> Probably it could be related to https://bugs.kde.org/show_bug.cgi?id=383069
> and -o writeback_cache=no
> 
> I didn't see this issue with previous kdeconnect version

Can this issue be related to sshfs if downgrading the Android app solves it?
Downgraded app to v1.10.1, no issues at all as always.

sshfs v2.10 here (Debian Buster), anyways.

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

[kdeconnect] [Bug 405847] SFTP corrupts DNG files

2019-04-23 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=405847

--- Comment #12 from Mau  ---
(In reply to Yuriy Vidineev from comment #11)
> Mau, I didn't know that downgrade of Android app helped. In that case
> probably it's not sshfs issue. But where have you got 1.10 version? I want
> to try it as well

F-Droid (by installing the app more old versions will be available; please note
that, by my experience, the first somewhat working after 1.10.1 is 1.12.6):

https://f-droid.org/en/packages/org.kde.kdeconnect_tp/

Let us know your findings, thanks

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

[kdeconnect] [Bug 405847] SFTP corrupts DNG files

2019-04-23 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=405847

--- Comment #14 from Mau  ---
(In reply to Yuriy Vidineev from comment #13)
> Thanks, Mau.
> But oldest available version on F-Droid that I see is 
> Version 1.12 (11200) - Added on 2019-03-10
> 
> It doesn't show 1.10.1 even in a F-Droid app
> I'll try to search other sources for 1.10

Sorry Yuriy, I forgot to mention you have to enable the "F-Droid Archive"
repository.

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

[kdeconnect] [Bug 405847] SFTP corrupts DNG files

2019-04-07 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=405847

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

--- Comment #6 from Mau  ---
I can confirm that files get corrupted quite often during transfer with Android
app v1.12.6.

I already lost a mp4 video file and some jpgs.

Same config as above: Debian testing (kdeconnect desktop v1.3.3) and Android
app v1.12.6 (f-droid). This issue doesn't happen at all with former last
working version v1.10.1: the transfer can be slow, but I never got anything
corrupted with that version.

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

[Discover] [Bug 420142] New: segmentation fault

2020-04-15 Thread mau
https://bugs.kde.org/show_bug.cgi?id=420142

Bug ID: 420142
   Summary: segmentation fault
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: maus...@libero.it
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 127587
  --> https://bugs.kde.org/attachment.cgi?id=127587&action=edit
It is a file with a bug report

SUMMARY

see attached file

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: kubuntu 19.4
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 417513] New: Report: organize by payees doesn't filter split transactions correctly

2020-02-12 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417513

Bug ID: 417513
   Summary: Report: organize by payees doesn't filter split
transactions correctly
   Product: kmymoney
   Version: 5.0.8
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

SUMMARY
If I create a report on transactions and select Organize by: Payees in the
Rows/Columns tab, transaction splits are not filtered correctly, i.e. all parts
of the split are shown and used to calculate the balance, so it is incorrect.


STEPS TO REPRODUCE
In my case, I have a kmy file with lots of transactions and accounts in it
(which I cannot share). But the main steps (in my case) are:
1. Create a liability account (shouldn't matter at all), called
Nebenkostenabrechnung
2. Create a transaction from Cash to that account with two splits: one is
against category Mieteinnahmen with e.g. 100.-, one is against this liability
account with e.g. 200.-

OBSERVED RESULT
1. Create a transaction report, filter for only the liability account and
select Organize by Payees: the report will show both parts of the transaction
which is wrong
2. Select Organize by Month instead: filtering is now correct.


SOFTWARE/OS VERSIONS
Latest AppImage (5.0.8, as of 2020-02-11)

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

[kmymoney] [Bug 417513] Report: organize by payees doesn't filter split transactions correctly

2020-02-12 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417513

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 417513] Report: organize by payees doesn't filter split transactions correctly

2020-02-12 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417513

--- Comment #1 from mau  ---
Additional info: I selected "Include transfers"; if I don't, there is only the
"wrong" transaction shown (at least in my case, i.e. the Mieteinnahmen
transaction).

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

[kmymoney] [Bug 417513] Report: organize by payees doesn't filter split transactions correctly

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417513

--- Comment #2 from mau  ---
Created attachment 126118
  --> https://bugs.kde.org/attachment.cgi?id=126118&action=edit
Test file with one transaction and two reports

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

[kmymoney] [Bug 417513] Report: organize by payees doesn't filter split transactions correctly

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417513

--- Comment #3 from mau  ---
I created an attachment showing the problem:

1. I created two accounts: Cash and Incidental Costs (Miet-Nebenkosten)
2. I added the category Rental Income
3. I added the transaction: 1000.- Cash against Rental Income, 200.- Cash
against Incidental costs, paid by the tenant to us (we are the landlord in this
case)
4. I modified the report Transactions by Payee (comment: REPORT 1): Filters:
deselect the cash account
5. I duplicated the report and changed it to Transactions by Month (comment:
REPORT 2).

Observed result
Report 1 shows a total of 800 for Tenant, which is 1000.- - 200.-, which is
wrong, since we filtered for only Incidental Costs. As Account, both splits
show Incidental Costs, which is also not correct, since only the 200.- split is
booked against Incidental Costs.
Report 2 shows a total of 200.-, which is correct.

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

[kmymoney] [Bug 417826] New: Report transactions by categories: tag column is empty

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417826

Bug ID: 417826
   Summary: Report transactions by categories: tag column is empty
   Product: kmymoney
   Version: 5.0.8
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

SUMMARY
I just added some tags to my transactions. Then I created a new report:
transactions by categories and modified it to include the column "tag". It's
shown, but completely empty.

STEPS TO REPRODUCE
1. Add tag to some transactions
2. Create report as described above

OBSERVED RESULT
Tags are not shown, even if column "tag" is checked in report configuration.
If I modify the report and select "organize by: tags", tags are shown and the
report is grouped by tags correctly.

EXPECTED RESULT
Tags should be shown correctly.

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

[kmymoney] [Bug 417826] Report transactions by categories: tag column is empty

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417826

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 417827] New: Report transactions by tag: splits with tag are not shown

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417827

Bug ID: 417827
   Summary: Report transactions by tag: splits with tag are not
shown
   Product: kmymoney
   Version: 5.0.8
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

SUMMARY
If I assign a tag to the splits of a transaction, they are not included in the
report filtered by that tag.

STEPS TO REPRODUCE
1. Create a tag and a transaction with splits
2. Create a new report: transactions by tag, select the new tag

OBSERVED RESULT
The transaction splits are not included in the report.

EXPECTED RESULT
The transaction splits should be shown in the report.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 417827] Report transactions by tag: splits with tag are not shown

2020-02-18 Thread mau
https://bugs.kde.org/show_bug.cgi?id=417827

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 403196] Displaying the ledger for a category shows the wrong account

2020-02-20 Thread mau
https://bugs.kde.org/show_bug.cgi?id=403196

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from mau  ---
I can confirm that behaviour and would see the proposed change as an
improvement as well.

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

[kmymoney] [Bug 418248] Add new category: always added on top level

2020-02-27 Thread mau
https://bugs.kde.org/show_bug.cgi?id=418248

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 418248] New: Add new category: always added on top level

2020-02-27 Thread mau
https://bugs.kde.org/show_bug.cgi?id=418248

Bug ID: 418248
   Summary: Add new category: always added on top level
   Product: kmymoney
   Version: 5.0.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

SUMMARY
If I select an existing category and do right click - select New category...,
the new category is going to be added on the top level, i.e. the hierarchy tab
of the Create a new Category window the existing category is not pre-selected
as the parent account (category).

OBSERVED RESULT
No category is pre-selected in the hierarchy tab.

EXPECTED RESULT
I'd prefer the existing category being pre-selected in the hierarchy tab. If
the user doesn't select an existing category for the right click, the existing
behavior can stay unchanged.

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

[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated

2020-03-02 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=417787

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[kde] [Bug 397228] New: kcm_keyboard crash

2018-08-06 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=397228

Bug ID: 397228
   Summary: kcm_keyboard crash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mav...@gmail.com
  Target Milestone: ---

Application: kdeinit5 (5.13.1)

Qt Version: 5.10.1
Frameworks Version: 5.47.0
Operating System: Linux 4.17.0-12.slh.1-aptosid-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

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

closing with "OK" the kcm module after deselecting "spare mappings" (4 mappings
set: Italian, Russian, Croatian and Serbian).

I also noticed that after applying some change the process "kcmshell5
[kdeinit5] --args=--tab=layouts kcm_keyboard" didn't exit and prevented opening
the kcm module again, therefore I killed it manually.

-- Backtrace:
Application: Modulo delle impostazioni di sistema (kdeinit5), signal:
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa8a82a4780 (LWP 3096))]

Thread 3 (Thread 0x7fa890f1b700 (LWP 3102)):
[KCrash Handler]
#5  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#6  0x7fa8af6b72f1 in __GI_abort () at abort.c:79
#7  0x7fa8af6f8867 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7fa8af802273 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#8  0x7fa8af6fee0a in malloc_printerr (str=str@entry=0x7fa8af803b30
"malloc_consolidate(): invalid chunk size") at malloc.c:5350
#9  0x7fa8af6ff10e in malloc_consolidate (av=av@entry=0x7fa88020) at
malloc.c:4441
#10 0x7fa8af701dad in _int_malloc (av=av@entry=0x7fa88020,
bytes=bytes@entry=2032) at malloc.c:3703
#11 0x7fa8af704321 in __libc_calloc (n=,
elem_size=) at malloc.c:3436
#12 0x7fa8ac3d23e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-tls.so.390.77
#13 0x7fa8aca468b1 in g_malloc0 () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fa8aca5ee1d in g_slice_free1 () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fa8ae1e6058 in __nptl_deallocate_tsd () at pthread_create.c:300
#16 0x7fa8ae1e707c in __nptl_deallocate_tsd () at
../sysdeps/nptl/futex-internal.h:200
#17 start_thread (arg=0x7fa890f1b700) at pthread_create.c:473
#18 0x7fa8af777edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fa893fff700 (LWP 3098)):
#0  0x7fa8af76d739 in __GI___poll (fds=0x7fa88c0029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa8aca41439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8aca4154c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa8afb2e1bb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8afad1b6a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8af8e77ea in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa8a69b1df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fa8af8ecb4f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8ae1e6f2a in start_thread (arg=0x7fa893fff700) at
pthread_create.c:463
#9  0x7fa8af777edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fa8a82a4780 (LWP 3096)):
[KCrash Handler]
#6  0x7fa8aa3c3310 in XextRemoveDisplay () from
/usr/lib/x86_64-linux-gnu/libXext.so.6
#7  0x7fa8adf27884 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#8  0x7fa8b0b6e3d2 in XCloseDisplay () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#9  0x7fa89d8dcc14 in QXcbConnection::~QXcbConnection() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x7fa89d8dccb9 in QXcbConnection::~QXcbConnection() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x7fa89d8de956 in QXcbIntegration::~QXcbIntegration() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#12 0x7fa89d8dea59 in QXcbIntegration::~QXcbIntegration() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#13 0x7fa8b00375ad in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#14 0x7fa8ae55bf89 in QApplicationPrivate::~QApplicationPrivate() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fa8afb0a693 in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fa8afad5e96 in QCoreApplication::~QCoreApplication() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fa8ae55e129 in QApplication::~QApplication() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fa89f7d5f7f in kdemain () from
/usr/lib/x86_6

[kde] [Bug 397228] kcm_keyboard crash

2018-08-06 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=397228

Mau  changed:

   What|Removed |Added

   Platform|unspecified |Debian testing

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

[digikam] [Bug 386959] Properties view: wrong creation date [patch]

2018-04-23 Thread mau
https://bugs.kde.org/show_bug.cgi?id=386959

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

--- Comment #15 from mau  ---
Hmm, for me it looks like we have two different problems here:

First one is the mapping:

The Metadata Working Group (MWG) [1] recommends

for Tag Name "CreateDate"

Composite:SubSecCreateDate 
EXIF:CreateDate 
IPTC:DigitalCreationDate 
IPTC:DigitalCreationTime 
XMP-xmp:CreateDate 
CurrentIPTCDigest 
IPTCDigest

which is the "creation date of the digital representation" (MWG),

and for Tag Name "DateTimeOriginal"

Composite:SubSecDateTimeOriginal 
EXIF:DateTimeOriginal 
IPTC:DateCreated 
IPTC:TimeCreated 
XMP-photoshop:DateCreated 
CurrentIPTCDigest 
IPTCDigest

which is the "creation date of the intellectual content being shown" (MWG).

So apparently a photoshop-named tag should be used for DateTime information -
at least as a fallback if no other field contains the DateTime information.


Second problem is: Resolution (time information included or not).

Since there seem to be cases when Xmp.photoshop.DateCreated does only contain
the date and not the time (and that could at least theoretically be the case
for all DateTime fields), I'd propose to prefer fields wich contain both date
and time over fields which contain only the date part. So I'd use two priority
rankings:
First go through all DateTime fields in the defined order, if a valid value for
Date and Time is found -> use that and exit.
If no entry is found, go through all DateTime fields again, in the same order,
and accept the first date value (withouth time) -> use that and exit.

Another way of handling all the different fields would be to group them (just
as MWG does) and check for and report any inconsistencies found (like different
dates / times or different resolution (missing time)). That would allow to
correct them, but the resulting question would be which cases of inconsistent
information could be corrected silently and which cases would require human /
user intervention.


[1] https://sno.phy.queensu.ca/~phil/exiftool/TagNames/MWG.html

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

[kdenlive] [Bug 388065] New: Audio out of sync (sampling frequency)

2017-12-20 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388065

Bug ID: 388065
   Summary: Audio out of sync (sampling frequency)
   Product: kdenlive
   Version: 17.08.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

Hi

I guess I've found a bug in kdenlive, using the 17.08.3 AppImage.

In my project most of the clips have audio with 48000 Hz sampling frequency,
but some of them have only 44100 Hz. In the timeline everything is shown and
played back correctly, but when I render my project I get audio and video
significantly out of sync.

I could trace it back to the different sampling frequencies. If I convert these
44100 Hz files to 48000 Hz and replace them in the timeline, I can render my
project correctly, audio and video are in sync.

Reproducible: always

Steps required:
1. mix 44100 Hz and 48000 Hz audio files in project
2. find that audio and video are in sync in the timeline
3. render project
4. find that audio and video are not in sync in the rendered file
5. replace 44100 Hz files by 48000 Hz variants, render and find result in sync

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

[kdenlive] [Bug 388065] Audio out of sync (sampling frequency)

2017-12-20 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388065

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kdenlive] [Bug 388065] Audio out of sync (sampling frequency)

2017-12-20 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388065

--- Comment #1 from mau  ---
Additional info:
The 44100 Hz clip begins correctly, but runs too fast so it ends before it
should. But note as well that all subsequent audio will be moved towards the
beginning as well, yielding to video and audio out of sync for the remainder of
the movie.

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

[kdenlive] [Bug 388065] Audio out of sync (sampling frequency)

2017-12-30 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388065

mau  changed:

   What|Removed |Added

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

--- Comment #2 from mau  ---
Problem is fixed with 17.12 release, probably related to the drop of avresample
(Bug 386932).

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

[kdenlive] [Bug 388385] New: Rendering as parts: lost frames

2017-12-31 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388385

Bug ID: 388385
   Summary: Rendering as parts: lost frames
   Product: kdenlive
   Version: 17.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

Description:
Create a new project and add several clips to the timeline (seamless).
Export the complete project and export it clip-by-clip.
Concatenate the clip-by-clip version using ffmpeg (ffmpeg -f concat -i
 -c copy ).
Compare the complete project-render and the concatenated one: the latter one is
shorter, missing exactly one frame per clip (you can also compare the length of
the rendered clips and the original ones it you use them completely).

Reason why this is a bug:
This behaviour is problematic if you render your project's video split in
several parts (e.g. to because of render time or memory usage) and merge it
with the project's audio afterwards, with the audio rendered completely in one
step.

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

[kdenlive] [Bug 388415] New: vidstab: Cannot remove or mute audio

2017-12-31 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388415

Bug ID: 388415
   Summary: vidstab: Cannot remove or mute audio
   Product: kdenlive
   Version: 17.12.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

Using vidstab for a clip to stabilize the image works great, but there is a
negative side effect: I cannot remove the clip's audio.

Split audio seems to work, but if I remove the split audio, it still gets
exported (but is not present if I play the timeline).
Applying the mute effect doesn't work either: the audio gets exported as well,
but is not present if I play the timeline.

Workaround: render the render zone related to the clip, import the new clip to
the project, replace the old clip (.mlt version of the original clip, with
vidstab applied) and remove it's audio.

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

[kdenlive] [Bug 388416] New: vidstab: Crash if two clips are stabilized at the same time

2018-01-01 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388416

Bug ID: 388416
   Summary: vidstab: Crash if two clips are stabilized at the same
time
   Product: kdenlive
   Version: 17.12.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: b-m...@gmx.ch
  Target Milestone: ---

If I create the stabilized version of two different clips at the same time,
kdenlive crashes when the faster stabilization finishes and the clip gets added
to the project bin, while the slower stabilization is still running.

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

[kdenlive] [Bug 388416] vidstab: Crash if two clips are stabilized at the same time

2018-01-01 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388416

--- Comment #1 from mau  ---
Additional info: proxy clips are enabled, maybe the crash happens when the
first proxy clip creation starts.

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

[kdenlive] [Bug 388416] vidstab: Crash if two clips are stabilized at the same time

2018-01-01 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388416

--- Comment #2 from mau  ---
Now a crash also occurred only creating one vidstab clip - but normally
kdenlive didn't crash then, while creating several vidstab clips at the same
time let it crash every time.

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

[kdenlive] [Bug 388416] vidstab: Crash if two clips are stabilized at the same time

2018-01-01 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388416

--- Comment #3 from mau  ---
Several clips and crashes later I think I can state the following:
Crashes happen after the mlt file has been created and when the new clip gets
added to the project bin; I can see it being added just before kdenlive
crashes.

If I deactivate "Add clip to project" in the vidstab dialog, kdenlive doesn't
crash.

Adding the vidstab-clips manually to the project bin never yielded a crash.

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

[kdenlive] [Bug 388415] vidstab: Cannot remove or mute audio

2018-01-01 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388415

--- Comment #1 from mau  ---
There problem is even more complicated:
If I compare the original clip, the vidstab clip and the muted vidstab clip,
original and muted vidstab clip have the same audio while the vidstab clip
audio is louder.

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

[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index

2018-01-23 Thread mau
https://bugs.kde.org/show_bug.cgi?id=353874

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kmymoney] [Bug 341589] Cannot assign tag to a split

2019-01-27 Thread mau
https://bugs.kde.org/show_bug.cgi?id=341589

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

--- Comment #1 from mau  ---
Any news on this feature? I'd appreciate it as well :-)

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

[kmail2] [Bug 388036] Include support for autocrypt

2018-10-04 Thread mau
https://bugs.kde.org/show_bug.cgi?id=388036

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

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

[kdeconnect] [Bug 402136] New: Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non esiste.

2018-12-14 Thread mau
https://bugs.kde.org/show_bug.cgi?id=402136

Bug ID: 402136
   Summary: Il file o la cartella
/run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non
esiste.
   Product: kdeconnect
   Version: 1.3.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: maurizio.lunar...@gmail.com
  Target Milestone: ---

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

SUMMARY


STEPS TO REPRODUCE
1. open dolphin
2. try to open files in the Smartphone
3. failed to see because the volume doen not exist

OBSERVED RESULT

Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non
esiste.
EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
kubuntu 18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux

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

[kdeconnect] [Bug 402136] Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non esiste.

2018-12-14 Thread mau
https://bugs.kde.org/show_bug.cgi?id=402136

mau  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[kdeconnect] [Bug 402136] Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non esiste.

2018-12-14 Thread mau
https://bugs.kde.org/show_bug.cgi?id=402136

mau  changed:

   What|Removed |Added

URL||https://forum.ubuntu-it.org
   ||/viewtopic.php?f=35&t=63136
   ||5

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

[kdeconnect] [Bug 402136] Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non esiste.

2018-12-14 Thread mau
https://bugs.kde.org/show_bug.cgi?id=402136

--- Comment #1 from mau  ---
same problem on Kubuntu 18.04.1 LTS and Kubuntu 18.10

No problem on kde plasma all work properly

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

[kdeconnect] [Bug 402136] Il file o la cartella /run/user/1000/84dd2afcbc291814/storage/EED9-18E8 non esiste.

2018-12-15 Thread mau
https://bugs.kde.org/show_bug.cgi?id=402136

--- Comment #3 from mau  ---
Many thanks
1.3.3 version installed and all work fine!

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

[kwin] [Bug 484015] SDDM Wayland does not go into monitor powersave timeout with no user logged in

2024-12-14 Thread Mau
https://bugs.kde.org/show_bug.cgi?id=484015

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[digikam] [Bug 229010] No support to resync GPS data from digikams database into into jpg files

2016-02-29 Thread mau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=229010

mau  changed:

   What|Removed |Added

 CC||b-m...@gmx.ch

--- Comment #5 from mau  ---
Yesterday I ran into the same problem:
In the past I had geo-located many but not all photos and yesterday I began
correcting some wrong geo tags and setting missing ones. For the initial test
as well as most images that seemed to work fine, but at some point in time I
realized, that there are images where digikam shows the corrected gps data, but
the xmp files are not updated correctly. Furthermore there might be a bug that
gps data is written into the jpg although I've set it to write to metadata
only.

I tried to get the gps data in the sidecar files by both Write Metadata to File
and by using the Maintenance Tool, but neither of them worked.

Now I wonder how I can check that all gps tags are written correctly to the
xmp's - yesterday I loaded test files into darktable, but that's not perfect
and doesn't scale that well... And the fact that gps coordinates can be
specified in different formats doesn't help either, converting them isn't that
much fun...

Is there a way to force digikam to write the gps data into the xmp files, maybe
on the command line? Another idea for a workaround?

Do you need more info or is there another way I can help?

My settings: write all metadata to sidecar files only.
My version: digikam 4.4 on Debian Jessie (4.14 in jessie-backports misses gps
support completely, but that's a different problem).

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