Bug 486865 - Unable to create new profiles, Profile name exceeded max length (-9)
Summary: Unable to create new profiles, Profile name exceeded max length (-9)
Status: RESOLVED DUPLICATE of bug 486475
Alias: None
Product: yakuake
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-10 18:17 UTC by link2003.2013
Modified: 2024-08-11 03:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description link2003.2013 2024-05-10 18:17:32 UTC
SUMMARY
Attempting to create a new profile with either the flatpak version or native RPM version of Yakuake simply results in the error "Profile name exceeded maximum allowed length (-9)."

STEPS TO REPRODUCE
1. Go to manage profiles
2. Create a new profile
3. Hit Okay
4. Error

OBSERVED RESULT
Unable to create new profile with a name of any length

EXPECTED RESULT
I can create a profile with a name of any reasonable length

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Comment 1 iamashwin99 2024-05-17 15:22:01 UTC
I have the same problem on fedora 40, Also what is surprising is that yakuake doesn't show up the profiles made on Konsole. If my memory serves me well, they both used to sync.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3500C with Radeon Vega Mobile Gfx
Memory: 7.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Google
Product Name: Morphius
System Version: rev6
Comment 2 iamashwin99 2024-05-17 15:23:23 UTC

*** This bug has been marked as a duplicate of bug 486475 ***
Comment 3 Christian Muehlhaeuser 2024-08-11 03:42:14 UTC

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