[neon] [Bug 480681] Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 --- Comment #2 from Aurélien COUDERC --- Created attachment 165438 --> https://bugs.kde.org/attachment.cgi?id=165438=edit French BEPO AFNOR layout preview The French (BEPO, AFNOR) layout seems to have some very funky UTF-8 emojis which I’m sure are not part of the norm. https://bepo.fr/wiki/Accueil -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480681] Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 --- Comment #1 from Aurélien COUDERC --- > STEPS TO REPRODUCE > 1. Boot the live image (tested on Neon Unstable image from 28/01/24) > 2. Launch the installer > 3. Select Français (French) language > 4. Click Next for the timezone This is missing step 5. which triggers the crash. :-) 5. Select the « French (BEPO, AFNOR) » layout -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480681] New: Installer crashes when selecting French BEPO, AFNOR keyboard layout
https://bugs.kde.org/show_bug.cgi?id=480681 Bug ID: 480681 Summary: Installer crashes when selecting French BEPO, AFNOR keyboard layout Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: couc...@debian.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot the live image (tested on Neon Unstable image from 28/01/24) 2. Launch the installer 3. Select Français (French) language 4. Click Next for the timezone OBSERVED RESULT Installer crash. See stack trace at the bottom. EXPECTED RESULT Installer not crashing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 6.5.0-15-generic / KDE Neon Unstable from 28/01/24 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Choosing the same keyboard layout from in the system settings from the live image works fine, so it seems to be a installer specific bug. Application: Calamares (_neon), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140528670030208) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140528670030208) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140528670030208, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fcf65525476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fcf6550b7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fcf65e326f3 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7fcf65e2e055 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7fffdb6c9d10) at ./src/corelib/global/qlogging.cpp:378 #12 0x7fcf65e3309f in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x7fcf65e03261 in qt_assert (assertion=, file=, line=) at ./src/corelib/global/qassert.cpp:68 #14 0x7fcf41825c11 in KeyBoardPreview::fromUnicodeString(QString) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #15 0x7fcf4182c3aa in KeyBoardPreview::loadCodes() () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #16 0x7fcf4182c761 in KeyBoardPreview::setVariant(QString) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #17 0x7fcf41814632 in ?? () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #18 0x7fcf65d827ae in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #19 doActivate (sender=0x55e9e510d2e0, signal_index=26, argv=0x7fffdb6ca210) at ./src/corelib/kernel/qobject.cpp:4021 #20 0x7fcf418009c2 in XKBListModel::currentIndexChanged(int) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #21 0x7fcf4180cdf7 in XKBListModel::setCurrentIndex(int) () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #22 0x7fcf418144a1 in ?? () from /usr/lib/x86_64-linux-gnu/calamares/modules/keyboard/libcalamares_viewmodule_keyboard.so #23 0x7fcf65d827ae in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #24 doActivate (sender=0x55e9e5159940, signal_index=4, argv=0x7fffdb6ca330) at ./src/corelib/kernel/qobject.cpp:4021 #25 0x7fcf65c3c00e in QItemSelectionModel::currentChanged (this=this@entry=0x55e9e5159940, _t1=..., _t2=...) at ./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qitemselectionmodel.cpp:667 #26 0x7fcf65c3fbbc in QItemSelectionModel::setCurrentIndex (this=0x55e9e5159940, index=..., command=...) at ./src/corelib/itemmodels/qitemselectionmodel.cpp:1403 #27 0x7fcf66e055ad in QAbstractItemView::mousePressEvent (this=0x55e9e513d110, event=) at ./src/widgets/itemviews/qabstractitemview.cpp:1829 #28 0x7fcf66fcd233 in QWidget::event (this=0x55e9e513d110, event=0x7fffdb6caa40) at ./src/widgets/kernel/qwidget.cpp:8979 #29 0x7fcf66f07fa6 in QFrame::event (this=0x55e9e513d110, e=0x7fffdb6caa40) at ./src/widgets/widgets/qframe.cpp:515 #30 0x7fcf65db7448 in QCoreApplicationPrivate::sendThroughObjectEventFilters
[Welcome Center] [Bug 466698] Welcome Center Page 1 shows incorrect description of Debian
https://bugs.kde.org/show_bug.cgi?id=466698 --- Comment #4 from Aurélien COUDERC --- 5.27.2 migrated to testing/bookworm so the bug should be fixed for everyone now. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466698] Welcome Center Page 1 shows incorrect description of Debian
https://bugs.kde.org/show_bug.cgi?id=466698 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #2 from Aurélien COUDERC --- Ah, yes my fault, sorry for that. :-( I was trying to make some additional customization to plasma-welcome and some experiments went into the package by mistake. Version 5.27.2 in unstable is already fixed, and I’ll try to get it migrating to testing/bookworm asap. Sorry for the breakage. -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 465195] konqi-modern card deck is under a non-free software license
https://bugs.kde.org/show_bug.cgi?id=465195 Aurélien COUDERC changed: What|Removed |Added Summary|konqi-modern card deck is |konqi-modern card deck is |under a non-free software |under a non-free software |licens |license -- You are receiving this mail because: You are watching all bug changes.
[libkdegames] [Bug 465195] New: konqi-modern card deck is under a non-free software licens
https://bugs.kde.org/show_bug.cgi?id=465195 Bug ID: 465195 Summary: konqi-modern card deck is under a non-free software licens Classification: Frameworks and Libraries Product: libkdegames Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-games-b...@kde.org Reporter: couc...@debian.org Target Milestone: --- The license of the konqi-modern carddeck found in ./src/carddecks/svg-konqi-modern/COPYRIGHT is an MIT-like license, unfortunately modified with the following condition : « Permission is hereby granted, free of charge, to any member of the KDE project (the "K Desktop Environment" http://www.kde.org) obtaining a copy of this "Konqi SDK" package and associated documentation files (the "Package"), to deal in the Package without restriction […] » The « to any member of the KDE project » makes it non FOSS, since FOSS requires that the software be usable by anyone for any purpose. For example, the Debian Free Software Guidelines [1] item 5. states : « 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. » The card deck should either be re-licensed if the original authors agree, or dropped from libkdegames. [1] https://www.debian.org/social_contract.en.html#guidelines -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 Aurélien COUDERC changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Aurélien COUDERC --- I understand this is the expected way to go for interacting with the Wayland compositor so closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 --- Comment #1 from Aurélien COUDERC --- The wayland symbols appear after this commit : https://invent.kde.org/frameworks/kguiaddons/-/commit/3984732e007e71632a525d89227fdfe94fa037ad -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 464571] New: Symbols from libwayland-server are published in the library’s ABI
https://bugs.kde.org/show_bug.cgi?id=464571 Bug ID: 464571 Summary: Symbols from libwayland-server are published in the library’s ABI Classification: Frameworks and Libraries Product: frameworks-kguiaddons Version: 5.102.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: couc...@debian.org Target Milestone: --- Dear upstream, while packaging kguiaddons 5.102 for Debian I noticed the following new symbols : wl_buffer_interface@Base 5.102.0 wl_callback_interface@Base 5.102.0 wl_compositor_interface@Base 5.102.0 wl_data_device_interface@Base 5.102.0 wl_data_device_manager_interface@Base 5.102.0 wl_data_offer_interface@Base 5.102.0 wl_data_source_interface@Base 5.102.0 wl_display_interface@Base 5.102.0 wl_keyboard_interface@Base 5.102.0 wl_output_interface@Base 5.102.0 wl_pointer_interface@Base 5.102.0 wl_region_interface@Base 5.102.0 wl_registry_interface@Base 5.102.0 wl_seat_interface@Base 5.102.0 wl_shell_interface@Base 5.102.0 wl_shell_surface_interface@Base 5.102.0 wl_shm_interface@Base 5.102.0 wl_shm_pool_interface@Base 5.102.0 wl_subcompositor_interface@Base 5.102.0 wl_subsurface_interface@Base 5.102.0 wl_surface_interface@Base 5.102.0 wl_touch_interface@Base 5.102.0 These symbols are also part of libwayland-server0 so I doubt they should be part of kguiaddons library. Am I missing something ? Is there a way to remove them ? Full build log here : https://people.debian.org/~coucouf/kguiaddons_5.102.0.build.log Thanks for your help -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 464137] New: No more recent files list since the UI overhaul
https://bugs.kde.org/show_bug.cgi?id=464137 Bug ID: 464137 Summary: No more recent files list since the UI overhaul Classification: Applications Product: dragonplayer Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: myr...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Since the UI overhaul, dragon has lost the list of recent files that it used to have on its welcome screen. I think that was a nice feature and would be worth keeping. Kate/Kwrite welcome screens come to mind as nice rewrites that implement this functionality. STEPS TO REPRODUCE 1. Launch dragonplayer 2. Play a file 3. Quit dragonplayer 4. Launch dragonplayer again OBSERVED RESULT No list of recent files in the UI. EXPECTED RESULT When starting dragonplayer the second time (step 4.), I’d expect to have a quick way to reopen the file played at step 2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2022-01-08, commit cb45215c. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 Aurélien COUDERC changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 Aurélien COUDERC changed: What|Removed |Added Version|unspecified |22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 --- Comment #2 from Aurélien COUDERC --- Also reproducible in 22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 --- Comment #2 from Aurélien COUDERC --- Not reproducible in 22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 --- Comment #1 from Aurélien COUDERC --- Also reproducible in 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 --- Comment #1 from Aurélien COUDERC --- Also reproducible in 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464070] New: filelight doesn’t register navigation down the tree for Back/Forward navigation
https://bugs.kde.org/show_bug.cgi?id=464070 Bug ID: 464070 Summary: filelight doesn’t register navigation down the tree for Back/Forward navigation Classification: Applications Product: filelight Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY When navigating down the tree of an analysed folder by clicking the pie chart elements or the folder names on the left panel, the action is not registered for the « Back » navigation and the Back button stays greyed. STEPS TO REPRODUCE 1. Start filelight and analyse your home folder. 2. Click any of the pie chart elements, or folders in the left pane. OBSERVED RESULT The Back button stays greyed and cannot be used. EXPECTED RESULT The Back button should be active and lead back to the previous location in the tree. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2023-01-07, commit 902a954. Other actions like « Up » or « Go to Overview » do register and activate Back/Forward navigation. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464067] New: filelight looses piechart depth levels when navigating back or up
https://bugs.kde.org/show_bug.cgi?id=464067 Bug ID: 464067 Summary: filelight looses piechart depth levels when navigating back or up Classification: Applications Product: filelight Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY When doing an initial analysis of a folder, filelight will display a 5-level depth analysis of the space use in the pie-chart view. However if clicking on one of the outer ring elements and navigating back with the « Up » button, you never get the 5-level depth. STEPS TO REPRODUCE 1. Start filelight and analyze your home folder 2. Click one of the elements in the outer/5th level ring to dive in 3. Click the « Up » button 5 times OBSERVED RESULT Single ring / single depth pie chart analysis of the home folder. EXPECTED RESULT 5-level deep analysis of the home folder, same as after the initial analysis. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.1 Qt Version: 5.15.7 ADDITIONAL INFORMATION Running the HEAD of the master branch as of 2023-01-07, commit 902a954. I have a big home with > 600k files and > 600 GiB, it’s not reproducible on a second smaller user home on this machine. The issue happens even when analysing as smaller folder down the tree in the big user’s home. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 --- Comment #2 from Aurélien COUDERC --- Any chance to get that fixed in the 22.12 branch we plan to ship for the next Debian release ? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463034] "Battery low" notification persists even if battery fully charged
https://bugs.kde.org/show_bug.cgi?id=463034 --- Comment #5 from Aurélien COUDERC --- I just had another weird behaviour : - My battery discharged to 10% and I got the notification. - I plugged my AC and the notification disappeared. - I unplugged it, while still at 10%. - The battery continued discharging below 10% and I didn’t get the notification again (I ended up plugging the AC anyway at 7%). There seem to be an issue with the interaction between the AC plugging / unplugging and being exactly at 10% or not. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463034] "Battery low" notification persists even if battery fully charged
https://bugs.kde.org/show_bug.cgi?id=463034 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #4 from Aurélien COUDERC --- Yes, I can confirm the bug on Debian unstable with the same software versions as the reporter. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 463409] New: Cannot close the context menu opened with right-click without choosing one of the actions
https://bugs.kde.org/show_bug.cgi?id=463409 Bug ID: 463409 Summary: Cannot close the context menu opened with right-click without choosing one of the actions Classification: Applications Product: filelight Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: couc...@debian.org CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY Cannot close the context menu opened with right-click without choosing one of the actions. STEPS TO REPRODUCE 1. Open Filelight, analyze a folder. 2. Right click on any of the pie chart areas. 3. Click (left or right) anywhere in the UI outside of the context menu. OBSERVED RESULT The context menu stays open. EXPECTED RESULT The context menu should close. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Graphics Platform: Wayland ADDITIONAL INFORMATION The Esc key does correctly close the menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462928] Copying a file after another copies the first file again
https://bugs.kde.org/show_bug.cgi?id=462928 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #4 from Aurélien COUDERC --- The same bug was reported on Debian unstable since the 22.12.0 upload : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025943 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #10 from Aurélien COUDERC --- For reference there’s an upstream bug referencing the FLAC stuttering issue in VLC/libvlc here : https://code.videolan.org/videolan/vlc/-/issues/27454 And a fix : https://code.videolan.org/videolan/vlc/-/merge_requests/2918/diffs That we’ve applied to the Debian sources on top of 3.0.18 with a minor fix here : https://salsa.debian.org/multimedia-team/vlc/-/commit/c5289e84e17421c1e40ef9f0953b6c0f96a20cb2 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #5 from Aurélien COUDERC --- After more testing it seems to be limited to some files and the stuttering is reproducible for the same file and timestamp with all VLC-based apps. Mplayer doesn’t choke on the same files. I will do more testing and report but I guess from an Elisa standpoint you can close the bug. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 Aurélien COUDERC changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||couc...@debian.org Ever confirmed|0 |1 --- Comment #3 from Aurélien COUDERC --- I’ve added the patch to the Debian package on top of 22.08.3 but it doesn’t solve the issue. It makes it less frequent but I still have occasional sound cuts on an otherwise idle modern machine. I’ve not looked at the code but if the stutter is due to the playback directly waiting for the data to load from the disk, the correct solution is not to make the buffer bigger, it’s only going to make it less frequent. Also loading complete files in memory is not the solution either. I have a couple of albums that are a single FLAC file of a couple hundres of MBs and it seems overkill to load these entirely into memory. If the issue is really the playback buffer becoming empty, the real fix would be to ensure the prefetch is done in the background so the playback never ends up waiting for the data to be there. Thanks for looking into this ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457340] New: Cyclic dependency between QML modules in notifications package
https://bugs.kde.org/show_bug.cgi?id=457340 Bug ID: 457340 Summary: Cyclic dependency between QML modules in notifications package Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: couc...@debian.org CC: k...@privat.broulik.de Target Milestone: 1.0 The following can be found in system logs: plasmashell[PID]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml" This must be due to applets/notifications/package/contents/ui/NotificationHeader.qml:21 import "global" and applets/notifications/package/contents/ui/global/Globals.qml:23 import ".." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjs] [Bug 457338] New: Migrate from obsolete pcre1 to pcre2.
https://bugs.kde.org/show_bug.cgi?id=457338 Bug ID: 457338 Summary: Migrate from obsolete pcre1 to pcre2. Product: frameworks-kjs Version: 5.96.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b.buschin...@googlemail.com Reporter: couc...@debian.org CC: kdelibs-b...@kde.org Target Milestone: --- Dear upstream, kjs uses the obsolete and now unsupported pcre library and it would be better to switch to the pcre2 implementation that is actively maintained and has been around for some years now. Debian has started the process of retiring the old pcre implementation (libpcre3-dev package) and ideally we would like to remove it from the next Debian stable release. The Debian bug report can be found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000112 Thanks, -- Aurélien -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #23 from Aurélien COUDERC --- (In reply to Nate Graham from comment #19) > Can affected folks test that patch? ^^ Works for me on top of the Debian package on an XPS 7390. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #9 from Aurélien COUDERC --- (In reply to Nate Graham from comment #6) > Are you using the slider in the Battery & Brightness applet? Does it work if > you click on a position in the track rather than dragging the handle? I’ve reverted the commits for some time now, but as far as I remember both the slider and the keys had the same effect. It was not only blocking at ~20 % but the brightness was also flickering between steps until it reached that level. So it would do something like 6%, 8%, 2%, 12%, 1%, 16%, 3%, 18% (not precisely these numbers but you get the idea). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Aurélien COUDERC --- Quick note to say that for me it’s a serious bug. The brightness I get with the bug is more around 20% and makes it barely usable during daytime. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #3 from Aurélien COUDERC --- Same issue on Debian unstable working on packaging 5.25 beta. Others (at least from Kubuntu) don’t have the issue so not sure if the hardware or kernel is involved. My kernel is 5.17.6, and the laptop an XPS 13 7390. The issue is linked to the following commit : Write brightness to all raw devices https://invent.kde.org/plasma/powerdevil/-/commit/761fc8a4bf4bd70bcd9aca63fc67382c94ecf884 Reverting it and its followup : Fix Commit 761fc8a4 https://invent.kde.org/plasma/powerdevil/-/commit/94f8186804d8a67459a11673b602c55e34db25ad fixes the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 448957] New: Symbols disappeared between 5.23.5 and 5.23.90 without soname bump
https://bugs.kde.org/show_bug.cgi?id=448957 Bug ID: 448957 Summary: Symbols disappeared between 5.23.5 and 5.23.90 without soname bump Product: KScreen Version: 5.23.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: couc...@debian.org Target Milestone: --- Dear upstream, while packaging Plasma 5.24 beta for Debian I noticed the following symbols disappeared from KScreen. +#MISSING: 4:5.23.90-1# _ZN7KScreen6Output14setLogicalSizeERK6QSizeF@Base 4:5.18.3 +#MISSING: 4:5.23.90-1# _ZN7KScreen6Output18logicalSizeChangedEv@Base 4:5.18.3 +#MISSING: 4:5.23.90-1# _ZNK7KScreen6Output11logicalSizeEv@Base 4:5.18.3 Wouldn’t that deserve a soname bump ? Thanks, -- Aurélien -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432586] Dead zone in the top left corner - cannot activate kickoff
https://bugs.kde.org/show_bug.cgi?id=432586 Aurélien COUDERC changed: What|Removed |Added CC||couc...@debian.org --- Comment #1 from Aurélien COUDERC --- In fact it depends on various factors like the scaling and the exact size of the panel. For example I’m using 125% and it’s broken when the panel height is in [30px,40px] but neither below or above. And for 100% it is broken in [44px, 54px]. What seems to happen is that: - the K menu icon is not scaled continuously but by by notches, I guess to use only available bitmap sizes and have it always crisp - when the panel is made taller than the immediately smaller icon size that can fit, padding is added around the icon - the padding is not clickable (neither on the left nor on the top side in fact) -- You are receiving this mail because: You are watching all bug changes.
